SAP Q2 2026 Earnings: Reading Between the Lines

Cellphone with logo of German software company SAP SE on screen in front of business website. Focus on left of phone display. Unmodified photo

SAP’s Q2 2026 earnings call gave the market exactly what it wanted to hear: cloud backlog reaccelerating, a confident H2 pipeline, and an AI story with real commercial traction. Shares, sitting near a 52-week low going into the print, jumped over 8% the next day.

But for enterprise buyers heading into Q3 and Q4, the reaction glosses over a more calculated narrative: a profit miss explained away in five separate pieces, a regulatory concession dismissed as a footnote, and a CEO stating outright that AI pricing is designed to strip away customers’ historical negotiating leverage. Read closely, this call is less a story about SAP’s momentum than a preview of the commercial posture buyers should expect in their next negotiation.

Below are five things from the release worth reading closely, not just for what SAP said, but for what that framing is designed to do.

1. SAP Made Excuse After Excuse for the Q2 Profit Miss

Non-IFRS operating profit grew by just 9% in Q2, a sharp deceleration from Q1’s 24% growth. CFO Dominik Asam pointed to five factors: (1) marketing costs tied to the Autonomous Enterprise launch, (2) the end of a stock-based compensation benefit, (3) heavier R&D investment, (4) tougher year-over-year comps, and (5) dilution from the Reltio, Dremio, and Prior Labs acquisitions.

His conclusion: taken together, H1 combined still shows mid-teens operating profit growth, and he expects something similar in H2, since cost levers are “entirely under our control,” unlike revenue, which depends on customers signing contracts.

Management was candid that this was a deliberate trade-off. Asam stated plainly that the priority is to “drive the AI transformation forcefully and protect the top line,” even at the cost of near-term margin expansion. Also buried in Asam’s answer was a more candid admission that SAP is explicitly saying cost discipline is an easier lever to pull than actual revenue growth. If H2 comes in on guidance, that may reflect cost management more than demand strength, a distinction that matters a great deal for anyone trying to gauge SAP’s real commercial momentum.

UpperEdge Perspective: If H2 guidance rests on cost containment (hiring slowdowns, token optimization, discretionary cuts) rather than genuine acceleration in bookings, buyers may see SAP become more flexible during commercial negotiations. A vendor managing its way to guidance has more incentive to protect deal economics and close volume than to hold firm on pricing.

2. SAP Leaned on Positives to Squash “SaaS Apocalypse” Talk

Throughout the call, SAP’s leadership repeatedly returned to a short list of proof points to push back on investor anxiety that AI-native tools could erode demand for traditional enterprise software. This included a current cloud backlog reaccelerating to 26% growth, a H2 pipeline described as better-covered than the prior year following Sapphire, and enthusiastic early feedback on the Autonomous Enterprise beta programs, which management said were “immediately oversubscribed.”

These are real, legitimate data points, but they’re also the three easiest positives to point to, and notably softer than hard monetization numbers. Backlog is a forward commitment, not recognized revenue. Pipeline commentary is directional and unverifiable from the outside. Beta enthusiasm is not the same as paid adoption at scale.

None of this means the “SaaS apocalypse” narrative is wrong or right. It means SAP has assembled the most favorable available evidence to counter it, which is exactly what you’d expect on an earnings call under this much investor scrutiny.

UpperEdge Perspective: Don’t let SAP’s narrative pressure your core commercial terms. Software, not AI, is still the major source of SAP’s revenue. This means SAP has just as much incentive to protect your core RISE/GROW spend and renewal terms as it does to sell you on the Autonomous Enterprise or Business AI Platform capacity, and customers should expect SAP to continue to pursue growth across its cloud offerings.

3. Klein Admitted SAP is Leaning into an AI Pricing Reset

The most consequential comment on the call may have been Klein’s framing of AI as a chance to reset SAP’s pricing model entirely.  His logic: once agents replace the historical pricing anchor, per-user, per-transaction, system-of-record economics, customers have nothing left to benchmark against. In his words, there is “nothing that you can relate to when you come from the system of record pricing.”

He described this explicitly as a chance to move to outcome-based pricing untethered from prior discount levels and said he is instructing SAP’s sales organization not to reference legacy SaaS price points when quoting AI and agent deals. Without this historical anchor point, clients risk not carrying over leverage from their existing commercial relationship, baselines, or discount levels.

UpperEdge Perspective: Buyers currently negotiating or renewing AI agreements should lock in pricing structures, caps, and benchmarks now, before outcome-based pricing becomes standard practice with far less transparent unit economics. Once AI consumption and agent-based pricing displace license- and subscription-based comparisons, customers lose one of their most reliable tools for negotiating: apples-to-apples historical pricing data. Customers should also press SAP on what recourse will be available under “outcome-based pricing” if the AI fails to deliver the promised value.

4. APJ and EMEA Again Led Growth – Now with New Leadership

Regional performance followed a now-familiar pattern: cloud revenue was particularly strong in APJ and EMEA, with Western Europe, India, and South Korea called out as standouts, while the Americas region was described only as “solid.” This is the same unresolved imbalance SAP has reported for several quarters.

What’s notable is that this strong APJ performance comes amid a real leadership disruption in the region. Simon Davies, SAP’s Regional President for APAC, departed roughly 14 months after joining the company to take a position at Databricks. SAP went nearly ten weeks without naming a permanent successor before appointing Verena Siow, a 15-year SAP veteran most recently serving as Business Suite Leader for APAC, effective July 2, 2026.

That’s not the picture of continuity SAP’s regional growth numbers might otherwise suggest, and the fact that APJ still outperformed through the gap says more about underlying demand than it does about stability at the top. It is worth watching whether Siow, as a long-tenured internal promote, brings a different commercial posture than Davies, who came from outside the SAP ecosystem and therefore required additional support from leaders like Manos Raptopoulos.

UpperEdge Perspective: Customers in APJ with deals in flight or renewals coming up should confirm who their new executive sponsor is and get face time with Siow’s team early, rather than assuming continuity from the Davies era. Given the leadership gap and Davies’ quick exit to a competitor, buyers also have a reasonable opening to ask pointed questions about regional deal governance and account continuity before committing to multi-year terms.

5. SAP Casually Brushed Off the EU Maintenance Ruling

Asam addressed a recent agreement between SAP and the EU that formalizes additional flexibility on software maintenance terms for certain customers. He was careful to frame this as a limited concession: maintenance remains highly valued by most customers for its cyber, compliance, and legal patches, and the added flexibility applies mainly to customers prioritizing lower spend over those benefits. He also noted SAP is seeing a “nice pickup” in customers returning from third-party maintenance providers after finding the risk not worth the savings.

Critically, Asam pointed out that this ruling doesn’t change the fundamental ECC timeline. ECC maintenance revenue is on a path to effectively zero by 2030 regardless of the EU agreement, since it phases out as more customers convert to RISE and cloud.

UpperEdge Perspective: SAP’s “no big deal” framing understates what actually happened. As covered in our recent blog, this isn’t informal flexibility being formalized. Instead, it’s a binding, EC-enforced antitrust settlement that reshapes on-premise economics, including landscape-splitting rights, shelfware relief tied to specific triggers, and a much lower-risk path back from third-party support.

That gives customers a legitimate basis to slow down or reconsider RISE timelines rather than assume migration is still the default path, and the next 12-18 months are the highest-leverage window to formally build these rights into renewals before SAP recalibrates its commercial playbook. Customers should also scrutinize their cloud contracts for the same restrictive termination and assignment terms the EC just prohibited on-premise, since the ruling doesn’t extend to RISE or cloud agreements.

Closing Thought: Read the Framing, Not Just the Numbers

SAP’s Q2 print gave the market a reason to exhale, and several of the underlying metrics – backlog growth, pipeline commentary, regional cloud performance – are genuinely positive. But this call was also a case study in disciplined narrative management: a regulatory concession downplayed, a profit miss explained away piece by piece, and a CEO stating outright that AI pricing is designed to strip customers of their historical reference points.

For enterprise buyers, the lesson isn’t to distrust every number SAP reports. It’s to separate the data from the framing around it, and to use the moments where SAP is most candid about its own strategy, like Klein’s pricing comments, as a direct guide to how to protect your own negotiating position in the quarters ahead.

Don’t let SAP’s earnings narrative set the terms of your next negotiation. UpperEdge helps enterprise buyers separate vendor framing from commercial reality, whether that’s locking in AI pricing before outcome-based models displace your historical benchmarks, or building EU-ruling protections into your next renewal. Talk to our SAP Advisory Practice to get ahead of SAP’s next move.

 

Related Blogs