SAP SE (SAP) Presents at UBS Global Technology and AI Conference 2025 Transcript

SAP CEO Christian Klein told investors the RISE transformation has been successful and that the cloud pipeline and AI-enabled use cases underpin confidence in Q4 and revenue acceleration through 2027; he reiterated that exiting the year at only 25% cloud CCB growth would be disappointing and said the company will push to hit stronger numbers. Klein highlighted BTP and the Business Data Cloud (now integrated with partners such as Microsoft Fabric, Snowflake and Databricks) as critical to AI agent deployment, cited internal efficiency gains from AI (roughly 40,000 developers using code agents with ~20% productivity improvement and 'triple‑digit million' euro efficiencies), and signaled M&A and tooling investments focused on data/AI and migration automation. Management emphasized monetization discipline for AI (Dominik’s EUR 1bn AI revenue target in 3–4 years could be conservative, CEO sees potential for ~EUR 2bn while prioritizing market share), protection of semantics/IP via BDC, and continued margin and cash‑flow focus.

Analysis

Market structure: SAP emerges as a primary winner — its software+data+BTP strategy and recent partner endorsements (MSFT, SNOW, Databricks) give it asymmetric pricing power in AI-infused ERP; expect 12–24 month revenue mix shifts toward higher-margin cloud/AI (CCB re-acceleration potential if CCB >25% annualized). Losers: pure-play HR SaaS (WDAY) and aftermarket SI services that rely on migration billables; migration services demand will stay elevated near-term, sustaining services pricing but compressing long-term SI margins as SAP builds AI migration tooling.

Risk assessment: Tail risks include a major data/IP lawsuit or a large production AI failure leading to client churn (single-event revenue hit >€500m possible), or a macro-driven capex pause reducing cloud bookings by >15% YoY. Time horizons: immediate (days–weeks) volatility around Q4 close; short-term (3–9 months) hinge on deal conversion and migration tooling delivery; long-term (2–5 years) depends on AI monetization (management bands €1–3bn). Hidden dependencies: SI ecosystem capacity, partner contract terms for BDC semantics, and regulatory scrutiny on data portability. Catalysts: large RISE closures, GA of agent tooling, or adverse catalysts: breach/negative legal rulings.

Trade implications: Tactical long SAP (2–3% NAV) into Q4 with hedged upside using a 6–9M call spread (buy ~10% OTM, sell ~30% OTM) to capture re-acceleration while capping cost; pair trade long SAP / short WDAY equal notional (1–3% NAV) for 3–12 months to exploit HR share shift. Buy modest exposure to SNOW and MSFT (each 0.5–1% NAV) for 6–18 months to play BDC network effects; deploy protective puts if SAP volatility spikes >30% IV or guidance falls below 20% CCB growth.

Contrarian angles: Consensus underprices SAP’s IP protection via BDC semantics — loss of semantics access creates stickiness that could lift SaaS multiples by 200–400 bps over 2 years. Conversely, the market may be underestimating migration cost friction; if SAP’s AI migration tooling fails to materially cut SI spend within 12 months, expect CCB deceleration and a 15–25% downside re-rate. Historical parallel: Oracle’s slow cloud transition shows durable incumbency despite multi-year drag — SAP could replicate upside if execution on agentic AI is clean; hedge where legal/regulatory signals turn negative.

Key Decisions for Investors

• Establish a 2–3% NAV long in SAP (SAP) equity within 2 weeks ahead of Q4 close; simultaneously buy a 6–9 month call spread (buy ~10% OTM, sell ~30% OTM) to lever upside on pipeline conversion while limiting premium outlay; trim/close position if CCB growth guidance <20% or FY margin guidance cut >150 bps.
• Enter a pair trade: long SAP (as above) and short Workday (WDAY) equal notional (target combined exposure 1–3% NAV, short side 1:1) for 3–12 months to express relative share gain in HR/agentic AI; cover short if WDAY beats enterprise deal cadence for two consecutive quarters or if SAP reports material legal impairment.
• Buy selective platform exposure: allocate 0.5–1% NAV to Snowflake (SNOW) and 0.5–1% NAV to Microsoft (MSFT) over 6–18 months to capture BDC ecosystem demand; initiate on <8% pullbacks from current levels or immediately if portfolio underweights platform exposure.
• Risk-control rule: monitor SAP SEC filings and court dockets for material adverse events (MAE) and set automated reduce-to-0.5% NAV if a court rules against SAP or if SAP issues a profit warning within 30 days; until that trigger, buy 3–6 month protective puts equal to ~20% of the SAP position notional to cap tail loss.