📊 Full opportunity report: The Core Of SAP’s AI Plan: Building Own Record Systems Instead Of Renting AI Minds on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
SAP is shifting its AI approach by developing proprietary record systems instead of relying on external AI models. This move emphasizes owning structured enterprise data, aiming to improve control and reliability. The strategy could reshape how enterprise AI is deployed and adopted.
SAP has revealed a strategic shift in its AI approach, focusing on building and owning its own enterprise record systems rather than relying on third-party AI models. This move aims to leverage SAP’s extensive data assets to enhance AI reliability, control, and integration across its enterprise solutions, impacting thousands of large organizations worldwide.
Most of the world’s business transactions, including purchase orders, invoices, payroll, and supply chain data, are processed through SAP systems. SAP’s AI initiative, centered on its new layer called Joule, is designed to integrate deeply with these existing systems, positioning itself as the primary interface for enterprise AI. As of mid-2026, Joule is live across more than 35 SAP solutions, supporting over 30 specialized AI agents and 2,500 skills, with plans to expand further by Q3 2026.
SAP has committed €100 million to a partner fund aimed at enabling system integrators to develop custom agents using Joule Studio, its low-code-to-code agent builder. The company reports specific outcomes, such as a retailer reducing HR process times by 40-60%, an airport operator cutting operational costs by 16%, and developers achieving 20% productivity gains, emphasizing operational, not hypothetical, benefits.
The core of SAP’s architecture is built around a Knowledge Graph, which ensures Joule reads business metadata directly from SAP’s Business Technology Platform, understanding context-specific workflows and legal implications. This structured, permissioned data foundation distinguishes SAP from frontier labs, which rely on open internet models. SAP’s approach is model-agnostic, consuming external foundation models and orchestrating them within its own platform, aiming to own the data layer rather than the models themselves. This strategy aligns with SAP’s goal of becoming the orchestration and data layer for enterprise AI, making it less vulnerable to shifts in third-party model quality or access.
However, this approach faces risks. The variable, consumption-based pricing model for AI features complicates cost forecasting, potentially slowing adoption among cost-conscious clients. Additionally, dependence on external models remains a vulnerability if access, quality, or capabilities of those models change. SAP’s slow-moving, heavily regulated installed base also introduces challenges, requiring trustworthy, auditable AI that aligns with enterprise standards. Despite these hurdles, SAP’s strategy aims to position itself as the dominant enterprise AI infrastructure provider, leveraging its existing data assets and governance advantage.
Own the system of record.
Rent nobody’s brain.
SAP’s AI bet is the incumbent’s inversion of the frontier race: don’t build the smartest model — own the data smart models are useless without, and meter access through Joule, an orchestration layer indifferent to which model wins.
The stack — where SAP chose to stand
You can switch AI vendors in an afternoon. You cannot switch your general ledger.
Honest bull / bear
Bull
- Best data-layer position of any incumbent — the one place hyperscalers can’t reach
- Knowledge Graph is context no model scale substitutes for
- Model-agnostic: owns the layer above commoditizing models
- Named, operational customer outcomes (40–60% HR cycle time, 90% admin cut)
Bear
- Consumption pricing is hard for CFOs to forecast — adoption stalls
- “Activated” ≠ “adopted”: the €100M fund admits demand needs subsidizing
- Depends on frontier models it doesn’t control
- Innovation tax: everything must work across a regulated installed base
Managing Enterprise Content: A Unified Content Strategy
Used Book in Good Condition
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Why SAP’s Data-Centric AI Strategy Matters
This shift signifies a fundamental change in how enterprise AI is built and deployed. Instead of competing in the model-race frontier labs favor, SAP is focusing on owning the enterprise data substrate, which provides a more stable, secure foundation for AI applications. This approach could give SAP a competitive edge by offering more trustworthy, context-aware AI tools that integrate seamlessly with existing business processes. For large organizations, owning the data layer means greater control, compliance, and potentially lower long-term costs, making SAP’s strategy a notable divergence from the current AI hype cycle.
ENGINEERING PLANNING & ORCHESTRATION : The AI-Native Quartet: RAG · Knowledge Graphs · Context & Memory · Planning (The AI-Native Series)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
SAP’s AI Roadmap and Industry Positioning
Throughout 2026, SAP has emphasized its vision of the Autonomous Enterprise, where AI agents operate alongside humans as co-operators within enterprise systems. The company’s recent product launches, including Joule and its agent ecosystem, reflect a focus on integrating AI deeply into core business functions. SAP’s acquisition of Prior Labs and its €100 million partner fund further underscore its commitment to building a robust, enterprise-grade AI infrastructure. This strategy contrasts with the broader industry trend of developing large, open models, positioning SAP as a provider of a more controlled, governed AI environment rooted in its existing data ecosystem.
Historically, SAP’s strength has been its extensive installed base of mission-critical systems across industries, especially in large corporations and the German Mittelstand. Its strategy now aims to leverage this installed base by embedding AI directly into familiar workflows, reducing the need for organizations to adopt external models that may lack transparency or compliance.
“Joule is designed to be the primary interface to the enterprise, reading structured metadata directly from our platform to ensure trustworthy AI outcomes.”
— SAP spokesperson
AI Agent Builders: The Complete Guide to Building, Training, Deploying & Launching Your Own AI Agent
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Unresolved Challenges in SAP’s Data-Ownership Approach
It remains unclear how effectively SAP can scale adoption of Joule given the variable costs associated with consumption-based AI pricing. The actual ROI for customers, especially in complex, heavily regulated environments, is still being evaluated. Additionally, dependence on external foundation models introduces risks if model capabilities or access policies change unexpectedly. The pace of customer migration and real-world operational impact are still developing and will be clearer over the coming months.
Fundamentals of Metadata Management: Uncover the Meta Grid and Unlock IT, Data, Information, and Knowledge Management
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for SAP’s Enterprise AI Strategy
SAP plans to expand Joule’s capabilities and agent ecosystem, aiming for 50 assistants and 200 agents by Q3 2026. The company will likely focus on accelerating customer adoption through its partner fund and integration enhancements. Monitoring how clients operationalize Joule and manage AI costs will be critical. SAP may also continue acquiring or integrating third-party models to strengthen its platform’s capabilities, while addressing existing adoption barriers.
Key Questions
How does SAP’s approach differ from other enterprise AI providers?
SAP emphasizes owning and structuring its own enterprise data and metadata, rather than relying solely on external AI models. Its architecture integrates AI deeply into existing systems, focusing on trustworthiness and control, unlike frontier labs that focus on open, large models.
What are the main risks of SAP’s data-centric AI strategy?
The main risks include variable AI costs that complicate budgeting, dependence on external foundation models that could change, and slow adoption due to enterprise compliance and trust requirements.
Will SAP’s AI strategy reduce reliance on third-party models?
While SAP currently consumes external models, its long-term goal is to own the data and orchestration layer, reducing dependency and increasing control over AI capabilities within its ecosystem.
How soon will we see broader adoption of Joule in enterprises?
Adoption will depend on how effectively SAP can demonstrate ROI, manage AI costs, and address integration challenges. Expect gradual expansion over the next 12-18 months as client use cases mature.
Source: ThorstenMeyerAI.com
