SaaS Displacement

In Q1 2026 Salesforce's third pricing iteration in eighteen months — the AELA flat-fee bundle replacing consumption metering for enterprise accounts — invalidated the core assumption of the EMEA CRO function: that software revenue grows in proportion to licensed headcount. CROs who had built quota structures on seat-expansion targets entered Q2 2026 renegotiating commission plan mechanics with compensation committees who had not yet modelled outcome-based ACV.

By Q2 2026, ServiceNow's disclosure that 50% of net new business was no longer seat-originated, corroborated by Workday listing headcount reduction as a direct revenue risk in its 10-K, provided board-level evidence that the EMEA CRO's traditional pipeline model was structurally unsound. At the same time, EU AI Act procurement reviews began extending deal cycles by four to eight weeks as buying teams added AI conformity diligence to their standard vendor assessments.

Q3 2026 brings the August 2 EU AI Act enforcement deadline as an active deal variable: CROs must now position AI Act compliance readiness as a commercial differentiator or accept that procurement delays will persist. The definitive market signal is that the CRO who cannot articulate outcome SLA structures and credit-based ACV will be outcompeted by peers who can, making the traditional EMEA SaaS CRO profile a diminishing asset in the market.

Q1 2026 saw the CSA's enterprise readiness gap assessment (March 2026) expose a systemic failure in how EMEA SaaS vendors had embedded AI into their products without conducting the Annex III high-risk classification reviews required by the EU AI Act. VP Product functions that had shipped AI features under pre-Act governance frameworks found themselves in technical non-compliance with obligations that became binding on 2 August 2026.

During Q2 2026, the June Microsoft Copilot Studio Licensing Guide introduced Copilot Credits as the billing unit for agentic interactions, creating a new design constraint for VP Product functions across every Microsoft-integrated SaaS platform. Product roadmaps that had been planned around per-feature or per-seat assumptions required material revision to accommodate credit-consumption profiles as first-class product requirements alongside performance and reliability.

Q3 2026 demands that VP Product functions own the conformity assessment process end-to-end, not delegate it to legal. Vendors operating agentic products embedded in high-risk categories — HR screening, creditworthiness assessment, education — must have documented technical files ready for submission to national supervisory authorities by August 2. The VP Product function that survives this transition will be architecturally literate, compliance-native, and capable of leading cross-functional conformity working groups.

Throughout Q1 2026, the customer success teams operating under EMEA CCOs continued to report NPS and seat-activation metrics to executive committees that were simultaneously watching agentic pricing experiments erode the relevance of those measures. The Salesforce AELA bundle, announced in late Q4 2025 and operationalised across EMEA enterprise accounts in Q1 2026, meant that a customer could deploy unlimited Agentforce actions under a fixed annual fee — rendering seat-activation counts meaningless as a health signal.

In Q2 2026, ICONIQ Growth's inference-cost data ($230,000 per $1 million AI product revenue) became a reference point for CFOs conducting renewal reviews. CCOs who could not demonstrate workflow-level ROI — cost per resolved support ticket, time saved per Copilot action — found renewal negotiations reopened on commercial terms rather than closed on relationship grounds. The shift from a relationship-centric to an outcomes-centric customer success function is now measurably underway across EMEA.

Q3 2026 adds EU AI Act compliance advisory as an unplanned but urgent CCO responsibility: enterprise customers in regulated EMEA industries are deploying AI systems that fall under high-risk obligations, and they are looking to their SaaS vendors for guidance that CCO teams were not hired or trained to provide. The CCOs who invest in compliance advisory capacity in this quarter will differentiate on retention; those who do not will see churn accelerate as customers seek vendors who can serve as compliance partners rather than software suppliers.

Q1 2026 established the scale of the hyperscaler capex supercycle that is reshaping the EMEA cloud architecture talent pool. Microsoft's 1GW of new capacity online in Q2 2026, Alphabet's $190 billion full-year capex guidance, and AWS's 28% Q1 growth are drawing the most senior multi-cloud architects into hyperscaler infrastructure roles, thinning the supply of cloud architects available to enterprise SaaS vendors for internal cloud strategy roles.

During Q2 2026, the practical implications of the EU AI Act for cloud architecture began to crystallise: Article 12 requires that high-risk AI systems maintain logs sufficient to identify the system's output throughout its entire lifecycle, and Article 9 requires a documented risk management process. For VP Cloud Architecture functions at EMEA SaaS vendors, this means data lineage, immutable audit logs, and model versioning are no longer optional architectural concerns but binding technical requirements.

Q3 2026 places the VP Cloud Architecture function at the intersection of two competing demands: supporting the hyperscaler-accelerated migration of EMEA enterprise workloads to scalable AI infrastructure while simultaneously designing the audit, lineage, and oversight architecture mandated by the EU AI Act before the August 2 enforcement date. The role survives with material redefinition; the version of the VP Cloud Architecture that was primarily a migration orchestrator does not.

Q1 2026 was the quarter in which the structural redundancy of legacy SaaS pricing function design became undeniable. Salesforce's move through three pricing models in eighteen months, Bloomberg's forecast of per-seat pricing falling from 60% to 30% of SaaS revenue over the coming decade, and the emergence of Flex Credits and AELA as the de facto enterprise commercial motions for agentic software all arrived simultaneously. Heads of Pricing whose teams were modelled on seat-count optimisation had no functional map for the terrain they entered.

By Q2 2026, ICONIQ Growth's inference-cost data had introduced COGS variability as a live pricing consideration that the legacy pricing function was structurally unsuited to model. The Head of Pricing and Monetisation function that survived Q2 was building credit-consumption forecast models, designing outcome-based contract structures, and collaborating with Cloud Architecture teams on inference-cost optimisation. Those that did not adapt were being bypassed by cross-functional commercial teams reporting directly to the CFO.

Q3 2026 is the defining quarter for this role. The August 2 EU AI Act enforcement deadline adds a transparency obligation: vendors of high-risk AI systems must not obscure the cost-of-AI in their pricing in ways that would prevent customers from fulfilling their own compliance obligations. The Head of Pricing and Monetisation who can architect credit models that are simultaneously commercially optimised and AI Act transparency-compliant will be the scarcest and most strategically valuable profile in EMEA SaaS through 2027.

For the EMEA CISO, Q1 2026 was characterised by the recognition — via the CSA's March 2026 readiness assessment — that existing information security frameworks were not mapped to EU AI Act obligations. ISO 27001 and SOC 2 certifications, the standard CISO credentialling suite, do not address Annex III high-risk classification, fundamental rights impact assessments, or the Article 73 incident reporting obligations for serious incidents involving high-risk AI systems.

Q2 2026 brought the Holland and Knight April advisory warning US-headquartered SaaS CISOs in EMEA-facing roles that the August 2 deadline applied equally to non-EU companies deploying or operating high-risk AI systems in the EU. This triggered an urgent reclassification exercise across CISO functions: which of our AI features are high-risk under Annex III, what documentation do we already hold, and what technical measures — logging, human oversight, access controls — are we missing?

Q3 2026 transforms the EMEA CISO from a risk manager into an active AI governance officer. The August 2 enforcement date is not a future planning horizon; it is a present operational deadline. CISOs who successfully lead conformity preparation will emerge with expanded mandates covering AI audit, regulatory liaison with national supervisory authorities, and cross-functional AI incident response — making this the most expansively redefined role in the EMEA SaaS landscape despite carrying the sector's lowest displacement risk.

Q1 2026 introduced the first serious commercial tension into the EMEA developer ecosystem: the proliferation of Copilot Credits and Agentforce Flex Credits as the pricing units for agentic development meant that developers building on these platforms could no longer treat API access as a free or flat-rate resource. Head of DevRel functions that had built their community programmes around generous free-tier access and unlimited API experimentation found those commercial assumptions revised unilaterally by platform vendors.

During Q2 2026, the EU AI Act's General Purpose AI provisions — requiring model providers and embedders to publish technical documentation, copyright summaries, and usage policies — created a new transparency obligation that sits directly in the DevRel communication channel. The Head of DevRel became the most likely internal owner of GPAI model card publication and developer-facing compliance communication, a responsibility for which no existing DevRel job description had been written.

Q3 2026 presents a bifurcated outcome: DevRel leaders who build sovereign-aware, AI-Act-compliant developer programmes — communicating credit economics clearly, publishing model cards, and establishing agentic workflow certification communities — will retain and expand their developer base. Those who continue to operate pre-agentic DevRel playbooks will find their communities migrating to platforms that offer both economic clarity and regulatory compliance support, accelerating the displacement of the traditional DevRel function as constituted.