📊 Full opportunity report: SAP’s AI Move: Prioritizing System Ownership To Strengthen Data Sovereignty on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
SAP is shifting its AI approach to focus on system ownership and data control with Joule, its enterprise AI layer. This move aims to reinforce data sovereignty and defend against competitors relying on open models. Key developments include new product launches, strategic investments, and a focus on structured enterprise data.
SAP has confirmed that it is now prioritizing system ownership and data sovereignty as core elements of its AI strategy, emphasizing control over enterprise data rather than building the most advanced models. This shift is reflected in the deployment of Joule, its enterprise AI layer, across numerous solutions and a new €100 million partner fund aimed at accelerating customer adoption.
Most of the world’s business transactions—such as purchase orders, invoices, payroll, and supply chain data—are processed through SAP systems, giving the company a significant positional advantage in enterprise data. SAP’s AI initiative, Joule, is positioned as a new interface to these systems, integrating deeply with SAP’s existing solutions like S/4HANA Cloud, SuccessFactors, and Ariba. As of mid-2026, Joule is active in over 35 solutions, with more than 30 specialized agents and 2,500 skills, and a roadmap to expand further.
At the SAP Sapphire conference in May, the company announced a €100 million partner fund to develop custom agents using Joule Studio, a low-code agent builder. SAP claims customer success stories include a global retailer reducing HR cycle times by 40–60%, and an Argentine airport operator cutting costs by 16% and administrative effort by 90%. The company’s strategic framing is ‘the Autonomous Enterprise,’ where agents are considered as critical as human operators in enterprise systems.
The architecture emphasizes the Knowledge Graph, which allows Joule to read business metadata directly from SAP’s Business Technology Platform, ensuring context-rich, permissioned data. SAP’s approach is model-agnostic, consuming third-party frontier models rather than training its own, and orchestrating them through its platform. This positions SAP as a neutral layer, indifferent to underlying models, competing on data ownership and integration rather than model IQ.
However, there are risks: AI consumption costs are variable and difficult to forecast, which could hinder adoption; dependence on external models introduces potential vulnerabilities; and SAP’s slow pace due to legacy systems and regulatory constraints may limit rapid innovation. Despite these, SAP’s strategy aims to secure its position at the core of enterprise data and AI integration.
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

The Israeli Solution: A One-State Plan for Peace in the Middle East
a one-state plan for peace in the Middle East from the Israeli viewpoint
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Why Data Ownership and Sovereignty Are Critical for SAP
This shift matters because most enterprise data remains within SAP systems, giving the company a unique advantage in controlling AI-driven insights and automation. By focusing on system ownership, SAP aims to defend against hyperscalers and frontier labs that rely on open models, positioning itself as the essential layer for enterprise AI. This strategy could redefine how organizations approach data governance, AI deployment, and vendor lock-in, with potential implications for the broader enterprise software industry.

The Agentic AI Bible: The Complete and Up-to-Date Guide to Design, Develop, and Scale Goal-Driven, LLM-Powered Agents that Think, Execute and Evolve
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
SAP’s Enterprise Data Dominance and AI Evolution
As of 2026, SAP processes a significant share of global enterprise transactions, making its systems central to business operations in many large organizations. Historically, SAP’s AI efforts have focused on augmenting existing solutions with models trained or sourced externally. The new strategy, announced in mid-2026, marks a deliberate pivot towards owning the data substrate that underpins AI, with investments in structured data management, the Knowledge Graph, and third-party model orchestration. This approach responds to industry trends where data sovereignty and control are becoming key differentiators amid increasing regulation and data privacy concerns.
“Our goal is to enable enterprises to own their data fully and harness AI in a way that is secure, compliant, and deeply integrated into their existing systems.”
— SAP spokesperson

Understanding SAP BTP: Architecture, Services and Use Cases for Clean Core-Strategies in Industry and Service
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Unresolved Questions About SAP’s Data Strategy
It is still unclear how effectively SAP can scale this approach across its vast installed base, especially given the slow pace of legacy system integration and regulatory hurdles. The long-term impact of dependence on third-party models and variable AI costs remains uncertain, as does the company’s ability to sustain innovation pace while maintaining trust and compliance.

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.
Next Steps for SAP’s Enterprise AI Ecosystem
SAP plans to expand Joule’s capabilities, increase partner ecosystem engagement via the €100 million fund, and accelerate migration to standardized data structures. Monitoring how organizations operationalize Joule, manage AI costs, and address integration challenges will be key to assessing the success of this strategy in the coming months and quarters.
Key Questions
How does SAP’s focus on data ownership differ from competitors?
SAP emphasizes controlling and understanding structured enterprise data via its Knowledge Graph and platform, rather than relying on open models or external AI providers. This approach aims to secure data sovereignty and reduce dependency on external AI models.
What are the main risks associated with SAP’s AI strategy?
Risks include unpredictable AI consumption costs, reliance on external models that could change or become unavailable, and slower innovation due to legacy system constraints and regulatory compliance.
Will SAP’s AI move impact existing customers?
Yes, existing customers will need to adapt their data structures and workflows to align with Joule’s architecture, which could involve migration efforts and changes in how they manage enterprise data.
What is the significance of the €100 million partner fund?
The fund aims to accelerate development of custom AI agents and solutions, encouraging system integrators and developers to build on Joule and expand its enterprise use cases.
When will we see broader adoption of Joule in enterprises?
Adoption is expected to grow through 2026, with SAP actively promoting new features, partner programs, and migration initiatives, but large-scale operational deployment may still take months or years.
Source: ThorstenMeyerAI.com