SAP Is Rolling Out AI Agents to Every Customer. Its Own Numbers Show How Slowly They're Catching On.
On October 6, at SAP's Connect event, Joule Work — the conversational layer SAP built to let employees delegate tasks to AI agents across its software — moved from an early-adopter program into general availability for all SAP customers. SAP said 110,000 of its own employees are already running the tool internally and that it's seeing roughly 20% productivity gains in finance, HR and procurement. Two weeks later, on SAP's Q3 earnings call, CEO Christian Klein pointed to that internal usage as evidence that what SAP calls the "Autonomous Enterprise" strategy has moved past demos: "it is being adopted," he said.
On that same earnings call, SAP added AstraZeneca and Infineon to its list of new cloud customers for the quarter — though the company did not detail which of those customers, if any, are actually running Joule agents in production rather than just SAP's broader cloud suite.
A Rollout Running About a Year Late
The October general-availability push looks less triumphant next to SAP's own timeline. At Sapphire 2025, SAP had promised Joule Studio — the low-code tool for building agents — would reach broad customers by the end of that year. It didn't. By Sapphire 2026, SAP's own chief product officer for the Business Suite, Manoj Swaminathan, told CIO.com that "Joule Studio adoption has been minimal compared to what we'd like," and the company pushed general availability back to the third quarter of 2026 — about a year behind the original promise. SAP's chief AI officer, Jonathan von Rüden, said the holdup was that customers wanted more control than the original low-code design allowed: "people wanted to see more pro-code flexibility." At that point, as of that May 2026 status check, SAP could only name three customers running Joule agents in production — Ericsson, Mercado Libre and Siemens.
Independent analysts who watched the October announcements weren't convinced SAP had closed the gap. Thomas Randall of Info-Tech Research Group called the event underwhelming: "SAP Connect is not giving us any breakthrough moments," he said, arguing SAP was fast-following rivals like Microsoft, Salesforce and ServiceNow that already ship comparable agent tooling. Moor Insights & Strategy's Jason Andersen took a more generous view, saying SAP was delivering on what it promised at Sapphire. Independent analyst Carmi Levy flagged a different concern — that SAP's announcements didn't address agent-specific security risks like model injection, warning that "agentic AI is already rewriting the cybersecurity playbook for all enterprises."
What the Earnings Call Didn't Dwell On
SAP's Q3 numbers were genuinely strong: revenue crossed €10 billion for the first time, up 13% to €10.3 billion; cloud revenue rose 26% to €6.67 billion; and cloud backlog grew 26% at constant currency to roughly €24.1 billion ($27.1 billion), beating a UBS forecast of 24-25% growth. But CFO Dominik Asam added two caveats that got less airtime than Klein's AI framing. First, SAP itself noted that some of the cloud growth reflected a "multi-quarter revenue catch-up from customers returning from financial distress" — unrelated to AI uptake. Second, he warned that the fourth quarter, which typically carries about half of SAP's annual bookings, faces a tougher macro backdrop of rising oil prices and U.S. interest rates that he said "start to develop teeth." Asam also acknowledged a structural tension: SAP is leaning on its own services arm to drive AI adoption among customers, which he said will likely depress services revenue and billable hours next year as the work AI does displaces the work consultants used to bill for.
The most direct outside read on actual usage came earlier in the year from SAP's own customer base. A survey by DSAG, the German-speaking SAP user group, found that just 3% of respondents were using SAP Business AI productively — and that among companies at those firms that had adopted some form of AI, 77% were running non-SAP tools, chiefly Microsoft Copilot, instead of SAP's own stack. Part of the gap is structural: Joule is built around SAP's cloud subscriptions and is unavailable to the roughly 10,000-plus customers still running on-premise ECC 6.0, whose SAP support ends in late 2027. That makes Joule less a standalone product than a lever SAP is using to push its remaining on-premise base toward the cloud migration it has wanted for years.
None of this means SAP's agent push is failing — the Q3 numbers suggest customers are at least paying for the option. But the distance between SAP's language ("being adopted," ~20% internal productivity gains, 110,000 internal users) and the evidence of actual customer-side usage (only three named production customers as of the most recent status check, a one-year schedule slip on its core agent-building tool, and a user survey showing single-digit production adoption) is the real story in this rollout. The fourth quarter — which Asam says will decide how the year, and arguably the AI pitch, turns out — is where that gap either closes or widens.