SAP at Goldman Sachs Communacopia + Technology Conference: ai drives growth

SAP reported 26% Q2 cloud customer-base growth and reiterated its target for consumption revenue to reach 30% by the end of the decade, supported by an estimated 60% of its installed base still running on premises. The company plans to launch 400 AI agents in September, with Joule Work already used by roughly 80,000 employees and tested by 150 pilot customers. Management expects AI-driven productivity gains of 30%-35% in development and up to 20% in finance and HR, while redirecting sales incentives and consulting resources toward AI and data consumption; execution, monetization and margin delivery remain key risks.

Analysis

SAP’s valuation debate should shift from whether AI expands demand to whether management can convert pilots into metered usage without creating a revenue-recognition and sales-productivity air pocket. Moving quotas from bookings toward consumption makes near-term ACV less comparable and raises the risk that sales compensation changes slow deal closure before usage ramps; this is the principal 1-3 month execution risk. The September/fall product releases are therefore a catalyst only if SAP discloses attach rates, paid conversions and consumption per customer—not merely agent availability or pilot enthusiasm.

The more material 6-18 month upside is that AI can pull forward cloud migrations that otherwise would have been deferred, while enlarging wallet share through data, governance and workflow monetization. The key competitive advantage is not model access but control of write permissions and auditability in regulated finance, payroll and supply-chain workflows; that favors SAP over horizontal AI platforms in its core installed base. Conversely, ServiceNow (NOW) and Palantir (PLTR) remain credible at the orchestration/data layer, and SAP’s openness to third-party data platforms reduces displacement risk but also limits its ability to capture the entire data-stack economics.

A non-obvious beneficiary is Accenture (ACN): shifting implementation work from SAP’s internal services organization to partners can preserve migration throughput while creating a larger, higher-value agent-design and governance services pool. The contrarian concern is that management’s claimed model-switching economics may be true at inference level but does not solve customer-success, integration and support costs; sustained gross-margin protection must be evidenced in reported cloud margin and operating leverage. Weak paid adoption after launch, rising implementation intensity, or a downward revision to cloud/backlog guidance would falsify the bullish thesis.

Key Decisions for Investors

• Initiate a 6-12 month long SAP position only after the first post-launch disclosure of paid AI/consumption conversion metrics; target a 15-20% upside from multiple stabilization plus cloud-growth durability, with a 7-8% stop or exit on cloud backlog/guidance deterioration.
• Use SAP / NOW as a relative-value pair over the next 3-6 months: long SAP, short NOW in equal beta-adjusted dollars. SAP has greater migration-led revenue visibility if governed ERP agents gain traction, while NOW is more exposed to horizontal workflow-AI valuation compression; close the pair if SAP fails to show measurable paid consumption by the next earnings report.
• Add ACN on 6-18 month weakness rather than chase SAP-only exposure. Partner-led migrations and agent extensibility should shift spend toward consulting integration, but require ACN to demonstrate improving bookings and SAP-related demand in its next two earnings calls before sizing materially.
• Set an event alert around SAP’s fall launch and subsequent earnings: a disclosed conversion rate from pilots to paid deployments, AI/data consumption ACV, and cloud gross-margin trajectory are the three decision variables. Absent those metrics, treat conference claims as product positioning rather than an earnings upgrade.