On the surface, Sapphire 2026 in Orlando was a celebration of SAP’s AI advancements and vision. But if you looked beyond the keynotes and paid close attention to their Financial Analyst conference, also held during the event, you could see what SAP is really up to: rewiring how its customers will buy, deploy, and pay for SAP solutions for the next five years.

At Sapphire, SAP laid out a vision for the “Autonomous Enterprise.” This is a future powered by Joule AI assistants, specialized agents, and tighter integration across SAP’s applications, data, and AI platforms. Their roadmap was bold, and the message to customers was clear: the next era of SAP runs on AI.

SAP wanted the spotlight on its partnership and product announcements. Buried beneath them were the changes that actually matter. These included the shift from seat-based to consumption- and outcome-based licensing, the careful framing of “free” AI access through 2026, and the conditions attached to on-prem AI. All point in the same direction. SAP is accelerating customers’ journey to the cloud and expanding its own revenue generation along the way.

For SAP customers, the biggest takeaways from Sapphire aren’t in the product roadmap. They’re in the long-term implications behind it. Five themes in particular deserve scrutiny before the next renewal, the next pilot, or the next phase of migration.

1. SAP’s AI Vision Isn’t Supported by Today’s Reality

The centerpiece of Sapphire was SAP’s push toward what it calls the “Autonomous Enterprise.” SAP introduced a multi-layered AI strategy built around:

• A unified SAP Business AI Platform that consolidates SAP BTP, Business Data Cloud, and Business AI into a single stack
• Joule Assistants and AI agents designed to automate end-to-end processes
• “Joule Work,” an intent-based engagement layer that becomes the primary way users interact with SAP across desktop, mobile, web, and, eventually, voice

SAP positioned this strategy as the future operating model for enterprises, where AI agents help drive workflows, business decisions, and operational efficiency across the organization.

The vision is compelling on paper, but SAP has openly acknowledged that its AI ambition is running ahead of its ability to deliver measurable outcomes at scale. The reality on the ground is that most customers are still trying to figure out where to pilot AI, and very few are running SAP’s Business AI in production.

Until SAP can prove measurable outcomes, the “Autonomous Enterprise” remains a strategic bet, not a proven operating model. Customers should be careful not to get pulled into AI adoption beyond what they are ready for and should hold SAP accountable for identifying specific use cases that deliver tangible customer value and prove the ROI behind them.

2. Free Access Now Means Pricing Leverage Later

One of the most customer-friendly headlines from Sapphire was that Joule Studio 2.0 design-time access, Joule agent runtime, and agent-to-agent interoperability will be free through the end of 2026. It’s a smart adoption play by SAP, but it’s also a setup.

At last week’s Financial Analyst conference, SAP made it clear that meaningful cloud revenue acceleration does not begin until 2027, a stance the market picked up on and punished sharply when SAP guided to slower 2026 cloud growth earlier this year.

Part of the reasoning behind this has become clearer: the free access in 2026 is designed to seed dependency before the meter turns on. Customers who build workflows, agents, and integrations against Joule today will be far less willing, and far less able, to walk away when pricing arrives.

The implication is straightforward: do not treat the free period as a free trial. Obtain transparency on what downstream pricing will look like for these features and lock in post-2026 pricing commitments before deploying anything material into production. Once your teams are building on it, SAP holds the cards at the next negotiation.

3. Licensing Model Shifting in SAP’s Favor

Behind the AI vision, SAP also made clear that it is rewriting how customers will pay for the platform going forward. SAP is moving away from predictable, seat-based licensing toward consumption-based pricing, including a stated near-term goal to grow consumption-based revenue to more than 30% of total cloud revenue by 2030. SAP is also restructuring sales compensation to reward growing customer consumption rather than closing the initial deal, meaning the account team’s incentives will be aimed at expanding your bill year over year.

More aggressive still, SAP introduced early concepts around outcome-based pricing: models in which SAP would capture a percentage of the savings or value generated through AI efficiencies, migration improvements, or operational gains.

In practice, SAP is positioning itself to participate directly in the financial outcomes its customers achieve. How any of this gets rolled out contractually, however, is still an open question as SAP has acknowledged that it cannot yet reliably tie its AI capabilities to measurable customer outcomes. In other words, SAP wants to be paid based on results it has already admitted it cannot measure.

Without strong contractual guardrails, SAP costs could escalate significantly over the life of these new models. Hold SAP accountable to provide the contractual details around these new license metrics and pricing structures and negotiate cost containment measures before your usage takes off.

4. SAP’s AI Announcement is an Illusion for On-Prem Customers

After years of cloud-exclusive AI innovation, SAP announced that Joule and other AI capabilities will be made available to on-premise ERP customers. This is a notable reversal, but one with strings attached. To access these capabilities, on-prem customers must begin their migration journey through RISE with SAP and commit to transitioning the majority of their current landscape to SAP Cloud ERP.

Pair this with the December 2027 end of mainstream maintenance for ECC and the strategy is hard to miss. SAP is offering on-prem customers AI if they migrate, pulling support if they don’t, and routing them through RISE either way. SAP is using both levers to compress the migration timeline onto a window that works for SAP and not their customers.

Customers shouldn’t mistake the on-prem AI offer for a favor. It’s a migration incentive, and the timing lines up with SAP’s revenue plan, not with what’s realistic for most customers.

5. Conflicting Messages on Recent API Policy Update

One of the most revealing moments at Sapphire wasn’t on the main stage. It was the disconnect between what SAP’s leadership said publicly and what the company has signaled behind the scenes.

In his keynote, CEO Christian Klein leaned hard into an “open ecosystem” message, framing SAP AI as collaborative, interoperable, and welcoming of third-party agentic partners. SAP went so far as to claim that its AI agents will integrate with third-party agents at no additional cost and backed the openness message with a €100 million AI ecosystem investment aimed at accelerating partner-led AI development.

Yet that messaging sits in direct tension with SAP’s recent API policy positioning, which has pushed in the opposite direction: tighter controls, restricted access, and a posture less friendly to third-party integration than the keynote suggested. Behind the scenes, customer accounts indicate SAP effectively acknowledged the API announcement was fumbled and inconsistent with the openness narrative being sold from the keynote stage.

This matters for two reasons. First, customers building multi-vendor AI strategies cannot rely on what SAP says about openness. They need it written into the contract: documented API rights, integration guarantees, and protections against policy changes SAP makes on its own.

Second, the gap between what SAP says publicly and what it does in practice is the real warning. When the keynote message doesn’t match the terms in the contract, the trust gap widens. Challenge SAP on the disconnect, don’t take their word at face value, and negotiate knowing that what’s written in policy is what holds, not what was promised on stage.

The Bottom Line

Sapphire 2026 was more than a technology conference. It was a signal that SAP is redefining both its product strategy and its business model around AI, and that the next several years of any SAP relationship are likely to be shaped as much by commercial structure as by technology choices.

Taken together, the five themes point in the same direction. SAP’s AI vision is ambitious but unproven. Free access today is designed to create paying dependency tomorrow. Licensing is moving from seats to consumption to outcomes, with SAP increasingly participating in customer-side value. On-prem customers are being routed to cloud through a narrowing RISE-and-EOS funnel. And the gap between Klein’s open-ecosystem message and SAP’s actual API posture is a reminder that the contract, not the keynote, is where strategy is enforced.

Reinforcing all of this is a recurring problem with how SAP rolls these shifts out: its own field teams struggle to explain how new commercial models actually work. Last year’s Cloud ERP packaging rollout was a clear example. SAP reps couldn’t articulate the new entitlement flavors and tiers because the commercial framework hadn’t caught up to the announcement.

Customers should expect the same uncertainty this time and insist on seeing the contractual pricing structures and terms in writing before meaningfully evaluating what SAP announced at Sapphire.

For customers, the path forward requires balancing innovation opportunities with careful commercial scrutiny. While SAP spent Sapphire selling the future of their Business AI, the decisions customers make today on pilots, contracts, and renewals will shape their SAP costs, leverage, and flexibility for years to come.

As SAP’s AI and commercial strategies continue to evolve, customers need a clear plan to protect flexibility, control costs, and maximize value. Learn how UpperEdge’s SAP Advisory Practice helps organizations navigate SAP negotiations, RISE, AI adoption, and transformation initiatives.