SAP Sapphire 2026 was a major platform announcement, a competitive shot at ServiceNow, a coherent acquisition story across Reltio, Dremio and Prior Labs. It featured an Anthropic partnership that puts Claude at the center of the SAP Business AI Platform. For anyone who cares about customer experience, it was also a missed opportunity dressed up as ambition.

If you watched only the keynote, you concluded SAP barely talks about CX. Klein did finance with JP Morgan. Herzig demoed pharma pricing. Industry AI showcased RWE wind turbines. The named flagship was the Autonomous Close Assistant. CX got line items.

That reading is incomplete. Here is what actually happened for CX at Sapphire 2026, what it means competitively, and what SAP and SAP CX customers should do about it.

What SAP actually shipped for CX

On the same day as the keynote, Balaji Balasubramanian, SAP's CX President and Chief Product Officer, published a substantive announcement listing ten named Joule Assistants for CX. Marketing gets Content and Campaign Assistants. Commerce gets Merchandising, Shopping and Order Management Assistants. Sales gets Sales, Deal Qualification and Deal Closing Assistants. Service gets Case Management and Service Management Assistants.

The supporting announcements are the part most analyst coverage missed. A Google partnership brings Gemini into SAP CX, plus adoption of the open Universal Commerce Protocol. Vercel handles storefront development. SAP Unified Payment runs on Adyen, with Checkout.com and PayPal configurable. Expanded Parloa and Amazon partnerships cover voice and digital service. A new SAP Commerce Cloud, cloud ERP edition targets mid-market. Two Industry AI scenarios for CX: Autonomous Revenue Growth Management and Unified Commerce.

All of it planned for general availability in Q3 2026.

For a category the keynote treated as a sub-bullet, that is a substantial product agenda. SAP Commerce Cloud has been a Gartner Magic Quadrant Leader for Digital Commerce for eleven consecutive years and the customer base is real. Adidas, Coca-Cola, Allianz, large utilities and banks all run on it.

The Cinderella problem

Despite all this, the keynote did not put CX in the same tier as Finance, Supply Chain or Industry AI. No flagship CX customer on stage opposite JP Morgan. No Autonomous Service Resolution Assistant matched to the Autonomous Close. No CX product head with mainstage time. The CX story subsists in a blog post by the CX CPO. The Autonomous Close gets prime time in the Sapphire keynote.

This is the Cinderella problem. SAP CX has the product. SAP CX has the customers. What SAP CX lacks is executive air cover. The product team shipped. The C-suite did not promote.

The signal is clear. Adobe Summit features Anil Chakravarthy championing CX Enterprise Coworker. Marc Benioff personally champions Agentforce Service at Dreamforce. The market – and analysts, too – reads those vendors as doubling down on CX. When Klein does finance and supply chain and CX gets a blog post, they read SAP as deprioritizing CX. The signaling problem makes the purchasing budget harder to defend, even where SAP CX has the better product.

The E2E story breaks at the customer interface

The bigger structural problem is what this does to SAP's own Autonomous Enterprise pitch. SAP says the autonomous enterprise runs on Joule across finance, supply chain, procurement, HR and customer experience. That is the E2E argument. It is a strong argument. It claims SAP can orchestrate cross-application, cross-department processes because SAP owns the system of record and the agentic platform on top of it.

Like each chain, it breaks at the weakest link. CX is this weakest agentic; the pitch breaks right there. And it breaks where it hurts most. Customers do not experience companies through CFO close cycles. They experience companies through service tickets, sales conversations, commerce checkout flows and marketing engagement. An enterprise that can compress financial close from weeks to days but still routes every service case to a human is not autonomous. It is back-office automation with a CX problem.

The Cinderella treatment of CX hurts SAP more than SAP appears to recognize. The cost is not just lost CX deals. It is the credibility of the Autonomous Enterprise narrative itself.

Where SAP CX sits competitively

Adobe is the most credible CX competitor in the marketing and commerce arenas. CX Enterprise Coworker launched at Summit on the same NVIDIA OpenShell runtime SAP uses, with multi-model interoperability across Anthropic, AWS, Google, Microsoft and OpenAI. AEP Agent Orchestrator, Brand Concierge, Real-Time CDP and the Magento commerce stack form a consistent CX agentic story. Adobe does not compete in ERP, so the two only collide in marketing, commerce and customer data. Adobe is winning the visibility fight there easily.

Salesforce with Agentforce 360 plus Operations is at $540M ARR with Service Agent, Personal Shopper and Buyer Agent shipping is the 800-pound-gorilla. Headless 360 makes Salesforce CX accessible through any MCP front end. Salesforce wins front-office. SAP wins back-office. They collide in customer-to-cash.

Microsoft Dynamics 365 Copilot for Service and Sales are generally available. Microsoft Agent 365 hit GA on May 1 at $15 per user per month. SAP wins ERP depth. Microsoft wins productivity surfaces and developer mindshare.

ServiceNow Autonomous CRM processes 100M+ customer cases monthly. AI Control Tower with 30 enterprise connectors positions ServiceNow above the application layer. This constitutes a real threat to SAP Service Cloud in enterprise customer service, particularly where ServiceNow ITSM already runs.

Mid-market matters more than enterprise watchers want to admit. HubSpot Breeze has shipped Customer, Prospecting, Content and Data Agents for years. Zoho Zia ships 100+ pre-built agents at $40 per user per month. SugarAI rebranded around precision selling and ERP signals last month. Creatio went seat-free with Unlimited on May 1. Freshworks Freddy and Zendesk AI Agents are GA. The new SAP Commerce Cloud, cloud ERP edition signals SAP wants to compete here. The pricing model will be the test.

What the platform actually does for CX

The platform announcements help SAP CX in tangible ways. Reltio gives Service Cloud a customer golden record across SAP and non-SAP systems with MCP support. Dremio lets agents reason on commerce and customer data without moving it. Prior Labs brings frontier tabular foundation models for the propensity scoring, churn prediction and lifetime value modeling LLMs are bad at. Free Joule Studio through 2026 lets SAP CX customers build custom agents without the per-seat AI surcharges Salesforce stacks on top. AI Agent Hub on LeanIX governs SAP and non-SAP CX agents at no charge.

No doubt, these are useful pieces. But they are not enough to offset the signaling problem.

Three recommendations for CX buyers

Audit the ten Joule Assistants for your modules with GA dates, not roadmap dates. All ten are planned for Q3 2026. Plan is not GA. Push SAP for module-specific commitment dates before signing renewal or expansion contracts. The free Joule Studio through 2026 is a real negotiating lever and a good opportunity to evaluate SAP as a credible CX alternative.

Run a real CX agent bake-off across the relevant vendors. SAP Service Management Assistant against Salesforce Service Agent. Adobe Brand Concierge against SAP Content Assistant. Test agent quality on your actual customer data, using your actual intent. The winner is the one whose agents resolve your cases or convert your shoppers, not the one with the best slide deck.

Take the CX orchestration plane decision deliberately, and not by accident. If your non-SAP CX estate is substantial (Salesforce Sales Cloud, Adobe Experience Manager, ServiceNow Customer Service Management, Zendesk, Freshworks, HubSpot), the question of where CX agent governance lives is now architectural. SAP AI Agent Hub, ServiceNow AI Control Tower, Salesforce Agent Fabric and Microsoft Agent 365 are not interchangeable. Test which one actually governs your non-SAP CX agents in production today. Loyalty is not a strategy.

Three recommendations for SAP

Ship an Autonomous Service Resolution Assistant or another relevant CX agent with the same visibility as the Autonomous Close. These agents exist. The flagship treatment does not. The Autonomous Close got JP Morgan, a named customer arc and Klein keynote time. CX deserves a named flagship agent with a named customer reference. Adidas, Coca-Cola, Allianz are sitting right there. Use them. The cost of doing this is a quarter of marketing investment. The cost of not doing it is another lost year as Cinderella does not get found by her prince, aka the customer.

Put the CX CPO on the next Sapphire mainstage with a named customer, or two. Balaji Balasubramanian wrote a substantive blog post. This is good, necessary – but insufficient. The mainstage signals priority. Service Cloud, Commerce Cloud, Emarsys and Customer Data Cloud are competitive products with reference customers and Magic Quadrant placement. They need keynote time, not blog time. SAP's bench can match Adobe's Chakravarthy and Salesforce's Benioff. The question is whether the C-suite decides to.

Decide whether CX is core or peripheral to the autonomous enterprise pitch, and commit visibly. Either invest with budget, headcount, roadmap parity and executive time equal to Finance and Supply Chain, or stop including CX in the E2E story. The Cinderella position helps no one. As said before, an autonomous enterprise that can close books in days but routes every service case to a human is not autonomous. It is back-office automation with a CX problem. Either fix the CX side of the story or shrink the story to fit what is real.

My PoV

SAP Sapphire 2026 shipped more for CX than the keynote let on. Ten named Joule Assistants. Partnerships with Google, Vercel, Adyen, Parloa and Amazon. A mid-market commerce edition. Two Industry AI scenarios. The product is more substantive than the press and analyst coverage suggests.

What is missing is the executive championing. The product team did its part. The C-suite did not do theirs. That asymmetry is the structural problem Sapphire 2026 did not fix, after I had some hope last year.

Let’s see when Cinderella finally gets to dance.

The news

SAP just held its annual Sapphire event in Orlando, FL. It is totally under the theme of uncertainty and how technology, in particular SAP’s technology, can help businesses steer through poorly charted waters, to use a nautical metaphor. Uncertainty is caused by evolving regulatory situations, tariffs and shipping delays with their impact on the supply chain, waning consumer confidence in the light of all of this, and of course, the big gorilla in the room: AI. SAP’s response to this is the “SAP Flywheel”, which consists of three components

• Applications, of which SAP commands the broadest portfolio amongst all business applications vendors
• Data, which all these applications create, which in turn gives SAP extensive access to semantically rich business data
• AI, which analyses all this data, makes it actionable and, in turn feeds it back to the applications, closing the loop to establish the flywheel.

SAP demonstrated how this works in a scenario that showed how a C-suite consisting of a CFO, CRO, COO and CHRO use the integrated SAP suite with embedded AI to rapidly respond to new tariffs, managing compliance, assessing financial impact, developing strategies, adjusting supply chain plans, and aligning people strategy, all based on unified data.

Key announcements are based on the concept that AI is changing how businesses, and therefore its business applications, operate. Supporting this, is the purpose of SAP’s business AI, which has its foundation in SAP’s Business Technology Platform, BTP. A centerpiece of this change in how businesses – and users – operate is Joule, which is embedded (or will be soon) in all SAP applications and being expanded into non-SAP applications with the help of SAP’s recent WalkMe acquisition to support tasks. On a process level, SAP announced the availability of and the fast delivery of a big number of new Joule Agents. To support businesses and users, all this is underpinned by the AI Agent Hub which is powered by LeanIX to control and govern the deployment of agents.

On the partnership side, SAP announced cooperations with

• Palantir to develop new real-time analytics use cases,
• Adobe, which builds an intelligent application to combine SAP ERP Data with Adobe Experience Cloud data to enable more accurate financial planning and marketing activities
• Not Diamond, to eliminate prompt engineering by automating it (NB: gen AI is eating its own children already)
• And most notably, Neurobotics and Nvidia to connect Joule Agents to the physical world by combining it with (humanoid) robots.
• Functionally, SAP committed to aggressive innovation in all application domains,  including Finance, Spend, Supply Chain, HCM, and Customer Experience, aiming to be best in class, “second to none”, as Muhammad Alam put it.

The bigger picture

AI, in particular agentic AI is in every vendor’s messaging, these days. This is an inevitable consequence of the hype that we are still in. AI-based technology may or may not help businesses navigate the treacherous waters that the current economic uncertainties are, but then all business action creates data, and AI is able to speed up the process of making sense out of this data and to come to informed decisions. This is the most visible reason why many vendors now change the narrative to also include a “data cloud” and/or a “data fabric” as a fundamental part of their software stack.

The other big topic, connected to the first one, is the “death of SaaS” and the degradation of ERP systems to mere data repositories with the business logic being overseen, orchestrated and executed by interacting AI agents. This is essentially the narrative of businesses that are strong on agentic and/or workflow but weak on ERP and it will be interesting how this narrative pans out in the next months.

My point of view and analysis

Let’s start with the keynote itself. I always have a challenge with artificial handovers between speakers or repeating the term “amazing” in a kind of unimpressed tone of voice, and frankly, we have seen more than our share of both in the approximately 2 hours that the keynote lasted – which in itself is pretty much on the long side. Don’t believe me? Watch the slightly edited version on YouTube for yourself (btw, why is there a need to edit it at all? This only reduces authenticity). From a delivery side, I think that Dr. Philipp Herzig performed best, showing mostly credible excitement. And delivery is a thing. Look at other keynotes of enterprise software vendors, like Salesforce or ServiceNow. I agree with Paul Greenberg and Brent Leary, when they say that the keynote is the one opportunity that a company has to excite the attendees. The other thing that struck me is the nearly total absence of topics like sustainability (mentioned in brief as part of the product name Sustainability Tower) or other non-monetary values that have been expressed by SAP in earlier years. While this is understandable to an extent, it raises the question whether these values have been merely lip service. To be sure, SAP is in good company with this – which doesn’t make it better.

Functionally, nearly everything revolved around AI and AI agents in one shape or another. Like most vendors, SAP positions the AI as a helper to employees, developers and consultants, that drives their productivity. SAP’s objective is thirty percent, which I consider low for some SAP user groups – like developers and consultants. Still, I caution about positioning of a tool as a helper and how it is going to be used by buyer organizations. This is something that is beyond any vendor’s control.

Still, I think that SAP has what it takes to help businesses become far more efficient. The innovation behind all that SAP showed during Sapphire is nothing short of mindblowing. And, it is credible, too, as it all relies on business data, which are abundantly available via the whole, often SAP driven, enterprise value chain. The data platform, given by the SAP Business Data Cloud and SAP Graph, can bring the unified data that is necessary for effective agent deployments to life.

More interestingly, SAP launched a full-fledged counterattack on the “SaaS is dead” and “the ERP is only a data repository” narratives of some vendors by demonstrating the ubiquitousness of its own agent, Joule and emphasizing on application logic being just that – logic – combined with already built-in privacy, security, integrations, compliance etc., that are on top of the data and give the necessary business context. Emphasizing on this while showing the ability to orchestrate Joule agents across platforms is quite a powerful message. Yes, orchestration is necessary in a process automation world that is increasingly dominated by agents (whether this is useful or not). With SAP demonstrating this capabilities, other vendors need to have very good arguments if they want to sell an agentic automation platform that has the same already built in.

SAP’s ambition to be best in class in all application domains is probably already achieved in many areas. One of them where it is not, is CX, although SAP put a huge investment into its new Sales- and Service Clouds, which technologically probably are the most modern apps around. And then, there is commerce, where SAP seemingly has lost its edge and marketing that was notably absent during the keynote – apart from the partnership with Adobe. Summing it up from a CX perspective – SAP has a long way to go before being recognized as a key CX player, let alone being “second to none”. And this recognition starts with C-level executives speaking more about it, which is another chance that SAP missed out on during this keynote. The CRO persona in one demo was about analytics and how management can be supported, which is not what CRM/CX is – or at least should be – about. And everything else was about finance, HR and supply chain.

Having said this, SAP’s CX solutions probably are amongst the best – but what is that worth if SAP doesn’t proudly position them? In addition, not doing this weakens the – else incredibly strong – end-to-end story that SAP justifiably tells. So, the easiest way to bolster this story is to leave the impression that CX is SAP’s Cinderella behind by incorporating more of it in the messaging.

All in all, SAP delivered quite a strong positioning a suite vendor. The moat around its ERP solution got far stronger, also considering commitments around becoming easier to deal with. The remaining piece seems to be to prove how SAP is or becomes “second to none” in the CX market or a subset of it.