Cloud Reaccelerates to 27% and Margin Hits 30%, But Half the Margin Beat Came From the Share Price Falling

Results vs. Consensus

Year-over-Year Comparison

Quality of Beat/Miss

• Revenue: The 27% constant-currency cloud growth is genuinely above the 23 to 25% full-year guide, and it accelerated from 26% in Q4. Management immediately qualified it: cloud revenue "was positively impacted by several quarter-specific effects" that are "unlikely to reoccur," with Q2 deceleration explicitly expected. No figure was attached to the effects. Total revenue growth of 12% at constant currency is the first quarter above the 11% full-year 2025 rate, though one quarter does not establish the acceleration management has now formally deferred to 2027. Translation cost 600bp of reported growth, exactly the 8.0 percentage point cloud drag disclosed in January working through the numbers.
• Margins: This is where the quarter needs the most careful reading. Non-IFRS operating margin of 30.0% is a headline number and roughly half of the expansion is not operating. The statement discloses that operating profit "was supported by a decline of share-based compensation expenses of €135 million." Against €9,555M of revenue that credit is worth approximately 140bp. Removing it puts non-IFRS operating profit near €2,732M and margin near 28.6%, against 27.2% a year ago, so underlying expansion is roughly 140bp rather than 280bp. Note also that gross margin actually contracted: non-IFRS gross margin fell 20bp reported and 30bp at constant currency, and cloud gross margin fell 10bp at constant currency. Every point of margin expansion this quarter came below the gross profit line.
• EPS: Non-IFRS EPS grew 20% to €1.72 against non-IFRS operating profit growth of 17% reported, with the gap coming from the tax rate at 29.3% against 30.4% for full-year 2025 and from a share count reduced by the buyback. IFRS EPS grew only 9% to €1.66, a much wider divergence from non-IFRS than in prior quarters, because the prior-year IFRS figure carried a large tax-exempt income benefit that did not repeat. The non-IFRS line is the correct read, and it inherits the same €135M share-based compensation credit as the margin.
• Cash: Free cash flow fell 9% to €3,248M, the only line down year over year. The disclosed cause is a €408M payout settling the Teradata litigation. Adding that back gives roughly €3,656M, up about 2%. Against a full-year guide of approximately €10B and €3,248M banked, the remaining three quarters need roughly €6.75B versus €4.66B delivered in the last three quarters of 2025. That is a demanding shape and it is the least-discussed number in the release.

Segment Performance

Cloud ERP Suite — Seventeen Quarters Above 30%

Cloud ERP Suite grew 30% at constant currency to €5,214M, extending the streak above 30% to seventeen quarters and now representing 55% of total company revenue. Management sized its share of the cloud book precisely.

"Cloud ERP Suite revenue increased by 30% in Q1, now accounting for 87% of total revenue growth in cloud." — Dominik Asam, CFO

Two mix disclosures inside the quarter matter more than the headline. Public cloud order entry accounted for over 70% of quarterly volume, continuing an acceleration that began in Q4. And the indirect partner channel grew significantly faster than direct, reaching almost 30% of total order entry.

"Order entry from our public cloud solutions accelerated sharply in Q1, continuing the momentum from Q4. Public cloud order entry accounted for over 70% of our quarterly volume." — Christian Klein, CEO

Assessment: The public cloud and partner-channel mix shifts are the most economically significant disclosures in the segment detail and neither drew a question. Public cloud carries better unit economics and shorter deployment than private cloud, which cuts directly against the outer-year ramp problem that cost the stock 15% in January: public cloud deals convert to recognized revenue faster. A partner channel at 30% of order entry and growing faster than direct is operating leverage that shows up in sales and marketing expense rather than in revenue.

Software Support — The Decay, Now Visible

Support revenue fell 6% at constant currency to €2,469M and 11% as reported. At 26% of revenue this remains the counterweight that holds total growth at 12% while cloud compounds at 27%. Management has guided the decline rate to accelerate, and the forcing function behind it was laid out on the call with unusual specificity.

"But recall, the extended maintenance begins '28, end of 2030, extended maintenance is over. And then the only kind of way to cope with that is basically our famous SAP ERP, private edition, transition option, which is quite costly. So customers have a big incentive to accelerate, and there are now the tools available." — Dominik Asam, CFO

Assessment: The maintenance cliff is the single most durable element of the SAP investment case and it is now dated. Extended maintenance for the legacy ECC estate ends in 2030, with the alternative being an expensive transition option. That is a contractual deadline, not a sales argument, and it converts the support decline from a leaky bucket into a scheduled migration. The bear reading is that a scheduled migration is also a scheduled negotiation, and customers with a 2030 deadline and improving migration tooling have four years to shop the alternatives.

Services — A Deliberate Decline

Services revenue fell 6% reported and 1% at constant currency to €1,007M. This is the line that changed the full-year total revenue language, and management was direct about the choice behind it.

"You've seen the services revenues kind of slightly declining. And yes, we have made a deliberate decision to invest more in adoption support for our customers, and we're not kind of chasing every hour to bill in the environment where also the migration tools play more and more of a role." — Dominik Asam, CFO

Assessment: Trading billable hours for adoption support is the right long-run decision and an immediate cost to the top line, which is precisely why the 2026 total revenue language changed. It is also internally consistent with the AI migration tooling story: if SAP's own tools compress implementation effort, SAP's services revenue is among the first casualties. Management flagged the same dynamic for systems integrators, noting that falling implementation budgets are not evidence of stalled projects.

Regional Performance

Cloud revenue performance was described as particularly strong in APJ and EMEA and solid in the Americas, with Brazil, France, Germany, India, South Korea, Switzerland and the United Kingdom outstanding and the United States particularly strong. The notable absence from the outstanding list, relative to prior quarters, is Saudi Arabia, which had appeared in both the Q4 and full-year 2025 call-outs.

Assessment: The Americas descriptor has now been "solid" against APJ and EMEA's "particularly strong" for three consecutive quarters, which is a consistent pattern rather than a one-quarter effect. Saudi Arabia dropping off the list is the clearest regional footprint of the Middle East disruption management discussed at length, and it is consistent with the CFO's account of governments in the region reprioritizing.

Key Topics & Management Commentary

Overall Management Tone: The most candid call of the four we have covered, and candid in ways that cut against the company's own narrative. Management volunteered that its margin beat was partly an accident of its own share price collapse, that the maintained guidance leans on an acquisition rather than organic strength, that AI agents in mission-critical processes are only 85 to 90% accurate and that this is not good enough, and that a further escalation in the Middle East would be closer to binary than incremental. Where the posture was weakest was on timing: a great deal of the forward case was deferred to the Sapphire conference in Orlando in May, which was invoked repeatedly as the venue where fundamental portfolio and commercial-model announcements will be made.

1. The €135M Share-Based Compensation Credit

The single most important disclosure for anyone modeling SAP's margin came in a passage the CFO could easily have left in the footnotes.

"IFRS and non-IFRS operating profit growth was supported by EUR 135 million decline of share-based compensation expenses. The SaaS Apocalypse debate and the related 28% decline in our share price during the first quarter alone left its traces in that position. While we hedge lion's share of our cash-settled grants, the sheer magnitude of the move in the unhedged portion in combination with related social charges that are not hedged, provided this, I have to admit, unintended relief, adding to continued strong general cost discipline." — Dominik Asam, CFO

The mechanics are straightforward. SAP settles a portion of its equity awards in cash, so the expense marks to the share price. A 28% decline in the quarter reduced the liability, and the unhedged portion plus unhedged social charges produced a €135M credit that flowed straight to operating profit.

Assessment: Three consequences follow and none of them were pursued in Q&A. First, roughly half the reported margin expansion and a majority of the €157M consensus beat on operating profit trace to this item, so the underlying operating performance was good rather than exceptional. Second, the credit is symmetrical: a share price recovery reverses it, which means an improving stock creates a margin headwind, an unusual and underappreciated feature of this P&L. Third, the disclosure itself is to management's credit. A company inclined to flatter its numbers does not volunteer that its margin beat came from its own equity falling 28%, and the phrase "I have to admit" is not the language of a team managing the narrative.

2. Cloud Reacceleration, With an Asterisk Attached by Management

Cloud revenue grew 27% at constant currency, above the 23 to 25% full-year guide and up from 26% in Q4. Current cloud backlog held at 25%, which is materially better than the deceleration guided in January. Management refused to let either number stand unqualified.

"Cloud revenue grew by 27%. It was positively impacted by several quarter-specific effects. As these are unlikely to reoccur, we expect deceleration of cloud revenue growth in the second quarter." — Dominik Asam, CFO

On the backlog the framing was similar: growth "held up remarkably well" while the expectation of slight deceleration over coming quarters was reiterated, now with what the CFO called "a clearly wider range of possible outcomes given the current environment."

Assessment: The quarter-specific effects were not sized, which is the one place management chose opacity in an otherwise transparent call. Absent quantification, the honest treatment is to take the full-year guide of 23 to 25% as the run rate and treat the 27% as a timing benefit borrowed from Q2. What is not borrowed is the backlog holding at 25% against a guide to decelerate, and that is the number that matters for 2027, because backlog is what converts. After two consecutive quarters where this metric disappointed, holding flat is a genuine positive and it is the first evidence in three quarters that the deceleration trend has a floor.

3. The Guide Is Maintained, But Not Organically

The full-year 2026 outlook was reiterated on every line. The basis on which it was reiterated changed materially, and the release states the new conditions in its opening sentence: the outlook "is based on the assumption of a near-term de-escalation of the conflict in the Middle East and the imminent consolidation of Reltio."

The CFO then removed any ambiguity about what Reltio is doing in that sentence.

"For the time being, we expect these to have a limited impact on 2026 cloud revenue, but you should not expect us to raise the outlook upon the imminent closing of Reltio." — Dominik Asam, CFO

Pressed on why an inorganic contribution is needed if the Middle East de-escalates, management was equally direct.

"And also, frankly, we didn't want to kind of — we want to be honest about that we need to include the Reltio acquisition, which is nonorganic to kind of protect the range, so to speak, in light of the setback we just discussed. So this enables us to support the guidance for this year." — Dominik Asam, CFO

Assessment: This is a soft guidance reduction disclosed honestly rather than a maintained guide. The organic outlook weakened, an acquisition fills the gap, and management said so without being cornered into it. The consolation is scale: Reltio was disclosed as approximately $185M of annual recurring revenue at the end of 2025, of which roughly two-thirds of a year would contribute, so the amount required to "protect the range" is on the order of €100M against a €25.8 to 26.2B cloud guide. A range that needs 0.4% of inorganic help was not badly missed. The correct read is that the organic case is a little weaker than in January and the honesty about it is worth something.

4. The Total Revenue Language Changed in Writing

The outlook section now reads: constant-currency total revenue growth in 2026 "to remain at similar levels as in 2025 and to accelerate in 2027," with an explicit note that "the previous outlook assumed constant currencies total revenue growth to accelerate through 2027."

Management gave two reasons for continued confidence in 2027: the services investment decision is a one-year effect that will be lapped, and the backlog ramp contributes materially more in 2027 than in 2026.

Assessment: Correcting the language is the right thing to do and it removes a real ambiguity that had been sitting in the outlook since 2024. It also means the acceleration thesis is now entirely a 2027 story with two more quarters of evidence to accumulate before it can be tested. Investors should note that the 2027 case rests on the same outer-year backlog ramps that explained the Q4 backlog miss. The company has been consistent about the mechanism throughout, which is a point in its favor, but the mechanism has now been used to explain a miss, to justify a deferral, and to underwrite a future acceleration.

5. The Middle East Risk Is Binary, Not Incremental

The largest single risk in the quarter is macro and management treated it with more rigor than most companies bring to geopolitical commentary. The exposure is described as running through supply chains rather than through direct sales.

"Needless to say, a continuation or even further escalation of the conflict and most importantly, the continued closure of the Strait of Hormuz would have the potential to materially derail the supply chains of many industries that are important to SAP." — Dominik Asam, CFO

Asked to size it, the CFO refused and explained precisely why sizing is the wrong exercise.

"What we can say, though, is we don't think that any kind of additional week or months of shutting down the Strait of Hormuz will be a kind of x basis point impact on CCB. That's not how it works. It's a slippery slope where at some point in time, supply chains will be shut down and then we have a massive impact. So it's a little bit of a kind of more binary situation." — Dominik Asam, CFO

The observed impact so far is contained: governments and directly affected industries reprioritized into what the CFO called "immediate firefighting," with an effect on first-half pipeline and bookings visible from mid-March, roughly two weeks after the conflict began.

Assessment: This is the correct characterization and it is why we are holding conviction rather than raising it. A risk that is non-linear cannot be discounted by adjusting an estimate downward; it either does not bind or it invalidates the guide. Management's own scenario framing makes the outlook conditional on an event outside its control and outside any analyst's ability to forecast. The mitigating observation is that SAP's exposure is second-order, arriving through customer supply chains rather than through SAP's own operations, and that the CEO's historical claim, that customers turn toward SAP in crises to invest in resilience, is consistent with the supply chain conversations he described.

6. AI: An Unusually Honest Accuracy Disclosure

The most striking passage of the call was the CEO volunteering the accuracy ceiling on SAP's current AI agents and stating plainly that it is not sufficient for the workloads SAP runs.

"But they are — today, they are 85% accurate. They are 90% accurate. But is this enough when you are touching the payroll, the finance, the financial close, the supply chains of the customer. No, it's not enough. It's not that the customers don't see the value, they see the value, but we have to go the last mile, and that has a lot to do with the ontology." — Christian Klein, CEO

The technical framing behind the gap was specific: SAP's ERP contains 7.3 million data fields across more than 120 mission-critical business processes, and the work is building knowledge graphs that let agents correlate that data rather than merely access it. Management also acknowledged, in prepared remarks, that "large-scale adoption of enterprise AI is still in its early stages."

The customer proof points offered were quantified rather than illustrative: bid win rates at Daimler Truck North America rising from 10% to more than 40% for a €70M financial impact within twelve months; a Queensland transport department running statewide investment optimization across 33,000 kilometres in a day instead of a week; invoicing accelerated more than ninefold at an automotive supplier.

Assessment: Volunteering that your flagship product is 85 to 90% accurate and that this is not good enough is not a normal disclosure decision, and it is the strongest signal on this call that management is describing reality rather than managing a narrative. It cuts both ways for the thesis. It confirms the bear concern that enterprise agentic AI is further from production scale than the marketing suggests. It also frames the accuracy gap as an ontology and domain-knowledge problem rather than a model problem, which is the framing that favors SAP over the model providers, because the missing input is proprietary process data that SAP holds and they do not.

7. The Consumption-Model Question, Answered With a Number

The "SaaS Apocalypse" thesis that drove the 28% first-quarter decline holds that AI collapses seat-based software pricing. Management addressed it directly and produced the most useful defensive statistic of the call.

"Also, it is important to highlight that less than 40% of our 2025 cloud revenue was tied to named users. The remaining subscription cloud revenue is priced via non-seat-based metrics like revenues, memory used and other value-related metrics." — Christian Klein, CEO

The transition to consumption pricing was characterized as gradual and explicitly not analogous to the on-premise-to-cloud shift.

"Let me emphasize once again that the ramp of consumption-based cloud revenue will be a gradual evolution and by no means a disruption comparable with the transition from on-prem to the cloud." — Christian Klein, CEO

Assessment: If under 40% of cloud revenue is seat-based, the seat-collapse thesis can at most touch two-fifths of the cloud line, and even there it substitutes rather than eliminates revenue. This is the single most decision-relevant statistic in the release for anyone underwriting the sector-wide de-rating, and it had not been disclosed before. It does not fully answer the bear case, because the seat-based 40% is likely concentrated in the human capital and customer experience applications most exposed to agent substitution, and management did not break that out. It does establish that the maximum exposure is far smaller than a blanket application of the thesis implies.

8. The Buyback Executed Into the Decline

The first tranche of the €10B programme announced in January completed as of April 1: 16,280,097 shares repurchased at an average price of €161.16, approximately €2.6B deployed.

Assessment: Roughly 26% of the two-year authorization executed in the first two months, at an average price below where the shares trade after this print. That is both a meaningful per-share accretion, roughly 1.4% of shares outstanding retired in a single quarter, and the clearest possible statement of management's own view of the valuation. A board that authorizes €10B in January and deploys €2.6B by April into a 28% drawdown is not treating the de-rating as informative. We flagged the successor buyback as an open capital-allocation question at initiation; it has been answered emphatically.

9. Market Share: Two Independent Confirmations

Management cited external validation of share gains from both major industry research houses, upgrading the figure it had used in prior quarters.

"Gartner Research just announced that SAP grew 15 percentage points faster versus the global enterprise applications cloud market in 2025." — Christian Klein, CEO

The CFO added that the gains were "most recently confirmed by both the most prominent specialized independent research houses, namely Gartner and IDC for calendar year 2025," and described them as solidly sustained into the first quarter.

Assessment: The figure moved from 10 percentage points of outperformance quoted in the Q3 2025 call to 15 percentage points here, on a different research house's measurement. Two independent confirmations of double-digit outperformance against the enterprise applications cloud market is the strongest external evidence available that the core franchise pillar is intact, and it sits awkwardly against a share price down 40% over twelve months.

10. Internal AI: Quantified, and a Third-Party Toolchain

The €2B efficiency programme by end-2028 acquired specific operating evidence this quarter. Developer productivity is up over 30%, using SAP's own Joule for ABAP development alongside third-party tools including Claude Code and GitHub Copilot. AI now assists 100% of support cases with 20% of tickets resolved fully autonomously, delivering 12% higher support productivity. Across more than 80,000 services colleagues, consultants save roughly one day per week. Go-to-market automation saved over 83,000 hours and influenced €50M of pipeline.

Assessment: These are operating metrics rather than financial ones, but they are specific enough to be falsifiable, which is more than most companies offer on internal AI. The detail worth noting is that SAP is openly using third-party coding assistants alongside its own tooling. That is pragmatic and it is also a small concession on the "no apps, no data, no AI" thesis: for code generation, where business context is not the binding constraint, the commodity model providers are good enough, and SAP says so by using them.

11. Data Access, IP Protection, and Where the Line Sits

Asked whether SAP would restrict or charge for third-party access to customer data, the CEO drew an explicit distinction and repudiated SAP's own history on indirect access.

"Customers' data is customers' data and accessing those data, we are not going to charge. But there is a big, big difference now in the cloud world and in the AI world about just accessing the data, which we have no plans to monetize at all versus accessing the IP, the domain know-how sitting in our ERP." — Christian Klein, CEO

The one qualification offered was operational: APIs will be throttled where mass data egress or very high call volumes would degrade application performance.

Assessment: The distinction between customer data, which is free, and SAP's semantic and process IP, which is not, is the right commercial line and the right competitive one. It preserves the openness that makes Business Data Cloud attractive while fencing the asset that actually differentiates SAP. The throttling caveat is where this could quietly become contentious: performance-motivated rate limits are indistinguishable from competitively-motivated ones from the outside, and SAP already has open European Commission proceedings concerning its treatment of third parties.

Guidance & Outlook

Disclosed Currency Translation Impact

The sensitivity table assumes 1.15 USD/EUR against a 1.13 constant-currency planning rate. The headline here is how much smaller the translation drag has become: the full-year cloud revenue headwind is now 1.5 percentage points against the 3.0 points disclosed in January, and the quarterly drag falls from the 8.0 points that hit Q1 to 1.5 points in Q2. Reported and constant-currency growth rates will converge sharply from here.

Implied full-year shape: Q1 delivered 27% constant-currency cloud growth against a 23 to 25% full-year guide. If the guide holds at its midpoint of 24%, the remaining three quarters average roughly 23%, which is consistent with management's explicit warning of Q2 deceleration. On free cash flow, €3,248M is banked against an approximately €10B guide, leaving roughly €6.75B across the remaining three quarters versus €4.66B delivered in the equivalent period of 2025. That is a 45% step-up in second-through-fourth-quarter cash generation and it is the most demanding element of the guidance package.

Street at: Consensus entering the print had total revenue at €9.53B, cloud revenue at €5.88B and non-IFRS operating profit at €2.71B. All three were beaten, the last by 5.8%, though a majority of the operating profit beat traces to the share-based compensation credit rather than to operations.

The May catalyst: Management deferred an unusual amount to the Sapphire financial analyst conference in Orlando, promising "fundamental changes to our portfolio," commercial model announcements covering how subscription and consumption cloud revenue will both drive growth, an expanded addressable market framing, and further detail on the €2B efficiency programme. That is a dense agenda and it makes May the most important dated event in the SAP calendar between now and the July print.

Analyst Q&A Highlights

Separating Macro Disruption From Product-Cycle Slowdown

The opening question asked management to disentangle the geopolitical impact from any independent slowing in the migration cycle, which is the central question for anyone deciding whether the de-rating reflects a temporary shock or a structural one. The answer separated the two cleanly and conceded the macro half.

Q: "Can you perhaps sort of isolate the macro from also maybe more product cycle-specific factors and your visibility around that sort of second half and more broadly over the midterm around how that product cycle evolves?"
— Mohammed Moawalla, Goldman Sachs

A: "There is no doubt, obviously, that we are, of course, also at some point, also impacted by the geopolitical tensions. I mean, when you can't actually send your salespeople to customers in the Middle East, I mean, at a certain point, you will see extended deal cycles. And we have a few of those."
— Christian Klein, CEO

Assessment: The product-cycle half of the answer was the more informative one and it was affirmative: management pointed to supply-chain resilience conversations happening in real time and to a healthy pipeline, while separately acknowledging extended deal cycles in the affected region. The distinction matters because a macro-driven slowdown reverses and a product-cycle slowdown does not. Nothing in the disclosed metrics suggests the latter, with backlog holding at 25% and cloud accelerating.

Whether the AI Accuracy Gap Is an R&D Execution Problem

A question probed whether SAP's difficulty getting agentic AI to production accuracy reflects a pace-of-innovation deficit, and asked what is changing organizationally to fix it. The answer reframed the problem as one only SAP is positioned to solve and disclosed a structural response.

Q: "Could you just talk a little bit about what you're trying to do as you take over R&D? Is this a pace of innovation problem at SAP? Is this needing to get more people into the companies to understand where the pain points are to bring that back into the products?"
— Adam Wood, Morgan Stanley

A: "I never thought that 5 years later, actually, we are sitting here in front of 7.3 million data fields in our ERP where you now need to build knowledge graphs that correlate this data to actually solve some of the most complex tasks in the world… You need to have the best industry consultants and pair them with the data scientists. You need to have product managers who also then understand how these agents work in a real-life environment. And when you form these teams, and we call this the all-in on AI program within SAP and bring them together, great things can happen."
— Christian Klein, CEO

Assessment: The question contained a disclosure the release did not: the CEO has taken over R&D. That is a significant organizational move at a company whose central problem is precisely a product-engineering one, and it went unremarked afterwards. The substantive answer, that the constraint is cross-functional team composition rather than headcount or model capability, is consistent with the accuracy framing in prepared remarks and with the refusal to hire AI developers in bulk that management articulated two quarters ago.

Whether the AI Transition Repeats the Cloud Transition's Cost

A question asked whether any part of the AI journey will resemble the cloud transition in investment intensity or margin impact, and whether skills gaps require acquisitions. Management answered on all three and reaffirmed the operating leverage commitment.

Q: "Are there any parts of the AI journey that you think will be actually similar to the cloud transition, whether it's in terms of investment costs and maybe margin implications going forward or maybe the need to do M&A to onboard skills that you don't currently have?"
— Charles Brennan, Jefferies

A: "Maybe on the margin, first of all, I want to reiterate that as of today, we say no reason whatsoever to change the envelope we have given in terms of operating leverage… And don't forget, when we talk about foundation models and transformer models, we are not doing the supercompute-intensive LLM training on unstructured data with fluffy data where you have a lot of data to crunch to come to some results… So we're not expecting the same type of myriads of investments that other people need to spend on to get these models trained because we can build on these models being built."
— Dominik Asam, CFO

Assessment: The reaffirmation of the 80 to 90% operating leverage envelope is the answer that matters, and it was given without hedging on a call where management hedged freely elsewhere. The training-intensity argument is the financial expression of the "no gigafactories" strategy: SAP pretrains on highly structured data and consumes commodity models for everything else, which is a fundamentally cheaper posture than the model providers'. The M&A answer was that acquisitions will be tuck-ins in data and AI, explicitly "not meant to acquire revenue," which is a useful constraint to hold management to given Reltio is now doing exactly that for the guide.

Why the Maintained Guide Needs an Acquisition

The sharpest exchange of the call asked why an inorganic contribution is required if the base case assumes de-escalation. Management quantified the acquisition's contribution precisely enough to make the question answerable.

Q: "Number one is how much of the Reltio acquisition is actually included in your full year revenue guidance? And the follow-up is, if we are assuming a near-term deescalation in Iran, then what is the reason — like what is the main reason then for needing this extra inorganic buffer in order to hit your full year guidance?"
— Jackson Ader, KeyBanc Capital Markets

A: "Yes. I mean on Reltio, luckily, the company on February 10 in a press release, which was referring to $185 million ARR as of year-end 2025, that representing a significant growth acceleration… So we are now end of April, so that's 4 months out of 12 months. So 2/3 remain to do of $185 million. So if you just take that as a yardstick without being precise, I think you have a good feeling as to how little actually is included in that kind of uptick."
— Dominik Asam, CFO

Assessment: Answering "how much" with enough precision for the questioner to compute it, roughly $123M of a $185M annual run rate, is the correct response and it deflates the concern by scale. Against a cloud revenue guide of €25.8 to 26.2B, the inorganic contribution is on the order of 0.4%. The CEO added the more consequential point in the same exchange: bookings lost in March and April do not come back within the year for revenue purposes even if the pipeline recovers, which is the same ratable-recognition mechanic that drove the guidance cut two quarters ago.

Whether the Quarter Was Bought With Discounting

Given that the prior two quarters both disappointed on backlog, a question tested whether this one was purchased through discounting, contract duration or pull-forward. The answer was a categorical denial with a specific supporting metric.

Q: "Can you give us any sense for — other than the risk you've already discussed that there might be some pull forward to make that happen or anything that could create an impact on the future quarters other than again — other than the macro issues we've discussed? And also, have you had to do anything relating to discounting or contract duration or whatever in order to deliver the solid numbers?"
— Mark Moerdler, Bernstein

A: "I would say, I would call this a very clean quarter. So when I saw the gross margins of the deals we closed, I mean, there was — actually, it was just to — in contrast, actually, we saw a very healthy quarter also from the deals closed with regard to gross margins… And definitely, there were no further incentives, et cetera."
— Christian Klein, CEO

Assessment: Deal-level gross margin is the right metric to cite in answer to a discounting question and management volunteered it unprompted. The corroborating disclosure is that Q1 focus in the field was on building the Q3 and Q4 pipeline rather than pulling deals forward, which is consistent with the seasonal pattern and with the CFO's separate statement that the second half typically carries the bulk of bookings. Taken with the constant-currency cloud gross margin falling 10bp, there is no evidence of a bought quarter, though there is equally no evidence of gross margin expansion.

Whether Customers Are Building the Agent Layer Themselves

A question went at the core of the sector de-rating: whether customers are using data-export capabilities to build agents outside SAP, capturing the value layer. The answer conceded the behavior exists and argued it is self-correcting.

Q: "Do you see any companies reassessing their current migration road map because of new available tools using tools like BDC to extract SAP data and try to build agents outside of the SAP ecosystem? So there's a lot of concern, as you know, in the market that the agentic layer will capture a lot of value. I mean is this something you see some customers trying to implement already?"
— Frederic Boulan, Bank of America

A: "I mean the good news is also that we also talked to many customers, I would say, who also then said, hey, we build a few custom agents. But to Dominik's point, who then actually came back and said, 'Hey, when you are building for us this agentic AI use case, there is no reason for us to do this custom or to do this with a large language model provider.'… And so yes, of course, we see those examples, but nothing where I would say now I have tonight a sleepless night because now customers I see already forming a layer on top of SAP. This is clearly not the case."
— Christian Klein, CEO

Assessment: The supporting argument from the finance seat was the stronger one: SAP's domain is hard monetary transactions in end-to-end processes, where the assurance requirement is categorically different from content generation or a 95%-accurate support agent. That is a defensible moat argument and it is consistent with the CEO's own 85 to 90% accuracy admission, since the same accuracy bar that constrains SAP constrains a customer's home-built agent far more severely. The honest caveat is that this is management assessing its own displacement risk, and the evidence offered is anecdotal.

What They're NOT Saying

1. The size of the "quarter-specific effects" in cloud revenue: Management twice flagged that 27% constant-currency cloud growth was flattered by effects unlikely to recur, and never quantified them. Without a figure, the reader cannot tell whether the underlying rate was 26% or 23%, which is the difference between a beat and an in-line quarter against the full-year guide.
2. The margin path once the share-based compensation credit reverses: The €135M credit arose because the shares fell 28%. Nobody asked what happens to reported margin if the shares recover, and management did not volunteer it. The mechanic is symmetric and the reversal would be a headwind of comparable size.
3. How free cash flow reaches €10B from here: €3,248M is banked, leaving roughly €6.75B across three quarters against €4.66B in the same period last year. That is a 45% step-up in an otherwise unchanged guide, and it drew no questions despite free cash flow being the line the CFO built a formula around in January.
4. Which parts of cloud revenue are seat-based: Disclosing that under 40% of 2025 cloud revenue was tied to named users was genuinely useful. Not disclosing which applications make up that 40% leaves the most exposed cohort, likely human capital management and customer experience, unquantified.
5. The European Commission proceedings, for a third consecutive quarter: No mention in prepared remarks, no analyst question, seven months after formal proceedings opened. This quarter the CEO discussed API throttling and IP protection at length without any reference to the open regulatory file on exactly that territory.
6. Whether Reltio is the last of the "protect the range" acquisitions: Management described a constant search for tuck-ins in data and AI while simultaneously using one to support the current-year guide. The two framings are in tension and were not reconciled.
7. Customer NPS: The metric missed its target range for 2025 and received no update, despite management describing extensive customer engagement during a quarter in which its own share price fell 28% and an FT article on short-term pain circulated among customers.

Market Reaction

• Pre-print setup: The NYSE-listed shares closed at $163.25 on April 23, down 32.8% year to date against the S&P 500's +3.8%, down 39.9% over the trailing twelve months and down 4.5% over the trailing thirty days. The 52-week closing range entering the print was $163.10 to $311.93, meaning the stock entered the release sitting essentially on its 52-week low.
• After-hours move: US-listed shares traded up approximately 5.4% following the release, attributed to beats on total revenue, cloud revenue and non-IFRS operating profit alongside a maintained full-year outlook.
• Next-day session: Shares gapped up to open at $175.10, a 7.3% advance, traded between $171.56 and $175.83, and closed at $175.26, up 7.4% or $12.01.
• Volume: 6.8M shares against a 3.2M thirty-day average, roughly 2.2 times normal.
• Benchmark: The S&P 500 rose 0.8% on the session, so roughly 660bp of the move was company-specific.

The setup explains most of the reaction. A stock that has fallen 40% in twelve months and enters a print at its 52-week low requires very little good news to move sharply, and this print delivered three consensus beats, a backlog metric that held when guided to decelerate, and a maintained outlook. The CFO's own framing of the "SaaS Apocalypse debate" as the driver of the first-quarter decline makes clear that the de-rating was sector-narrative rather than SAP-specific, and a quarter that fails to confirm the narrative is sufficient to produce a relief rally.

What the session did not do is repair the damage. A 7.4% advance recovers roughly one-fifth of the year-to-date decline and leaves the shares 44% below their 52-week high. The close at $175.26, at the upper end of the day's range and above the open, is constructive, but the volume at 2.2 times average is materially lighter than the 5.6 times that accompanied January's decline. Buyers returned; they did not return in the size that left.

Street Perspective

Debate: Does AI Break Enterprise Application Software?

Bull view: The disruption thesis assumes seat-based pricing and substitutable functionality, and SAP disclosed this quarter that under 40% of cloud revenue is tied to named users. The workloads SAP runs require accuracy standards that current agents cannot meet, the missing input is proprietary process data and semantic context that model providers do not have, and customers who built their own agents are returning. Two independent research houses confirmed double-digit share gains against the enterprise applications cloud market in 2025.

Bear view: The de-rating is discounting a slower, more corrosive outcome than outright displacement: seat growth stalls, consumption pricing yields less revenue per unit of value delivered, and the agent layer captures the incremental margin while SAP retains the low-growth system of record. SAP's own admission that agents run at 85 to 90% accuracy cuts both ways, since customers may simply wait rather than pay.

Our take: The bull case gained substantially this quarter and the sub-40% seat-based disclosure is the reason. It bounds the maximum exposure to a minority of one revenue line, and the bear thesis has been applied to SAP as though the exposure were total. What the bear case retains is the timing argument: consumption transitions compress revenue during the transition even when they expand it afterwards, and management explicitly guided that the consumption mix rises gradually over years. That is a multi-year headwind of unknown size, and unknown size is exactly what a 40% de-rating prices.

Debate: Is the Maintained Guide Credible?

Bull view: Every line was reiterated after a quarter that beat on all three consensus metrics, with backlog holding at 25% against a deceleration guide. The CFO's cloud revenue forecasting record is demonstrably strong, landing within €75M of the 2025 midpoint. The inorganic help required is roughly 0.4% of the cloud range.

Bear view: The guide is now conditional on a geopolitical de-escalation nobody can forecast and on an acquisition management admits is needed to protect the range. Cloud revenue was flattered by unquantified one-offs with Q2 deceleration pre-announced, the free cash flow guide requires a 45% step-up in the remaining three quarters, and the total revenue language was quietly downgraded. Maintained is doing a lot of work.

Our take: The bear case is right that this is a weaker guide than the words suggest, and the transparency with which management said so is the mitigating factor. A CFO who volunteers "we need to include the Reltio acquisition, which is nonorganic to kind of protect the range" is not the profile of a team stretching to defend a number. The genuinely unresolved item is free cash flow, where the required back-loading is steep and went unexamined. We would rather own a conditional guide disclosed honestly than an unconditional one defended stubbornly, but the free cash flow shape is the thing to watch in July.

Debate: Was the Margin Beat Real?

Bull view: Even excluding the €135M share-based compensation credit, operating margin expanded roughly 140bp to about 28.6% while the company absorbed a deliberate services investment and continued funding an AI transition. Management reaffirmed the 80 to 90% operating leverage envelope without qualification, and internal AI productivity gains are quantified and specific.

Bear view: Roughly half the margin expansion and a majority of the consensus beat came from an accounting credit caused by the share price collapsing. Gross margin actually contracted, at both the total and cloud level, on a constant-currency basis. A margin story where the gross line declines and the operating line expands is a cost-cutting story, and cost-cutting stories have a floor.

Our take: The bear case is factually correct on the composition and this is the most important analytical point in the quarter. Underlying margin expansion of roughly 140bp is good, not exceptional, and the cloud gross margin declining 10bp at constant currency deserves more attention than it received, because cloud gross margin is the variable that determines whether the entire mix shift creates value. One quarter of flat-to-down cloud gross margin after years of steady expansion is not a trend. Two would be.

Model Update Needed

Valuation: At the reaction-day close of $175.26 and the FMP-verified 1.1719 USD/EUR spot on April 24, the implied price is approximately €150 per ordinary share. Share count of approximately 1,164M derives from Q1 non-IFRS profit after tax of €2,002M against basic non-IFRS EPS of €1.72, and is declining through the buyback. Market capitalization is therefore near €174B.

On those figures SAP trades at approximately 24x trailing FY25 non-IFRS EPS of €6.15 and approximately 21x our FY26 estimate of €7.20 to €7.35. Free cash flow yield on the €9.5 to 10B range is approximately 5.5 to 5.8%. The remaining €7.4B of buyback authorization is equal to roughly 4% of market capitalization.

Where this sits against our prior two notes: we initiated at Hold in October with the stock at roughly 39x forward earnings on a 2.9% free cash flow yield, upgraded in January at roughly 23x and 5.1%, and the shares have since fallen a further 12% to roughly 21x and 5.8%. The upgrade has been wrong so far in mark-to-market terms, by a wide margin. What has not changed is the direction of the underlying figures: FY25 beat both profitability guides, Q1 beat all three consensus lines, backlog stopped decelerating, and the buyback has retired 1.4% of the company in a quarter. Each successive quarter has made the earnings estimate higher and the multiple lower.

Thesis Scorecard Post-Earnings

Grading Last Quarter's Commitments

Overall: Thesis unchanged in direction with the balance shifting. Two bear points improved, one bull point was downgraded on margin quality, and a new macro bear point was added. The net is a business performing slightly better than the January guide implied, at a price that has fallen a further 12% since we upgraded.

Action: Maintaining Outperform, conviction unchanged. The case for owning SAP here is arithmetic rather than narrative: approximately 21x forward earnings and a 5.5 to 5.8% free cash flow yield for a business compounding cloud revenue at 24 to 25% at constant currency, retiring 4% of its shares, and holding double-digit market share gains confirmed by two independent research houses. We are not raising conviction, for two specific reasons. Half the margin beat was a share-price artifact that reverses if the stock recovers, and the outlook is now conditional on a geopolitical event the CFO correctly describes as binary rather than incremental.

What we are watching into July: the free cash flow shape, which needs roughly €6.75B across three quarters against €4.66B in the comparable period; cloud gross margin, where a second consecutive constant-currency decline would challenge the mix-shift thesis directly; the size of the Q2 cloud deceleration that management has pre-announced; and whether reported cloud growth in July, flattered by a translation drag falling from 8.0 to 1.5 percentage points, is read correctly rather than as reacceleration. The Sapphire conference in May is the nearest dated catalyst, and management has loaded it heavily.