SAP Joule Work: The AI Workspace Bringing Agentic AI to On-Premise ECC and S/4HANA Customers

The Announcement That Surprised the SAP Community

For the past three years, SAP's AI strategy was unambiguous: Joule AI capabilities are cloud-first, cloud-only. When SAP CEO Christian Klein made that position clear in mid-2023, it created a significant dilemma for the tens of thousands of organizations still running SAP ECC or on-premise S/4HANA — either accelerate cloud migration to access AI, or accept falling further behind the AI adoption curve.

At SAP Sapphire 2026, SAP Chief Strategy Officer Sebastian Steinhaeuser announced a notable policy reversal: Joule Work — SAP's new intent-driven AI workspace — will be made available to on-premise ECC and S/4HANA customers. The announcement generated more debate in SAP community forums than perhaps any other item at the event, because it comes with a significant commercial condition attached.

This post explains what Joule Work is, what the reversal actually means in practice, the commercial requirements, and what SAP customers on ECC and on-premise S/4HANA should now be thinking about.

What is SAP Joule Work?

SAP Joule Work is SAP's next-generation AI workspace, announced at Sapphire 2026. Unlike the earlier Joule chatbot model — which answered questions and generated text — Joule Work is designed as an intent-to-execution system. Users state what they want to achieve, and Joule Assistants coordinate teams of Joule Agents to execute the work across SAP and non-SAP systems.

The key distinction SAP draws is between conversational AI (answering questions) and agentic AI (taking actions). Joule Work sits firmly in the latter category. The practical implication: rather than asking Joule "what is my cash position?" and reading an answer, a finance user says "close June's accounts payable exceptions" and Joule Work coordinates agents to retrieve the exception list, match vendor invoices, flag unresolvable items for human review, and post the resolvable ones — all within a governed, auditable workflow.

Joule Work is available across multiple form factors:

• Web client: Browser-based access, generally available now
• Mobile app: Available now on iOS and Android, enabling on-the-go task execution with Joule agents
• Desktop app: In Early Adopter Care from Q2 2026, full general availability planned for H2 2026
• Microsoft Teams and Slack integration: Joule Work surfaces directly in collaboration platforms, so employees do not need to switch context

SAP is also offering free design-time access to Joule Work through end of 2026 for customers and partners under fair-use limits, enabling organizations to begin building custom Joule assistant configurations before committing to full production deployment.

The Policy Reversal: AI for On-Premise ECC and S/4HANA

Approximately 20,000 SAP customers currently run SAP ECC, and industry analysts estimate that as many as 40% of SAP's installed base may still be on ECC or on-premise S/4HANA by 2030 — a cohort that represents an enormous portion of SAP's revenue and one that had effectively been excluded from the AI narrative.

SAP Steinhaeuser's Sapphire 2026 statement — "Joule assistants and agents are designed for cloud, but we want to meet customers where they are" — is a commercial and strategic acknowledgement that the cloud-only AI message was creating friction with a large segment of the customer base. The reversal gives on-premise customers a credible AI adoption path without requiring immediate full cloud migration.

The Joule Work capabilities that will be extended to on-premise customers include:

• Access to Joule Assistants covering finance, HR, procurement, and supply chain workflows
• Task execution via Joule Agents connected to on-premise SAP system APIs
• The Joule Work unified workspace interface (web, mobile, Teams/Slack)
• Agent building capabilities through SAP Joule Studio for custom process automation

The Catch: Commercial Requirements for On-Premise Joule Access

The announcement's fine print generated considerable discussion in the SAP community. On-premise customers cannot simply activate Joule Work — they must meet two commercial conditions:

Condition 1: 50% cloud spend commitment. Customers must commit at least 50% of their SAP maintenance and subscription spending to cloud services to qualify for Joule access on-premise systems. This is a significant commercial threshold — for a large enterprise with €5M in annual SAP maintenance, it requires €2.5M redirected toward SAP cloud products before on-premise Joule access is unlocked.

Condition 2: SAP Max Success Plan. Customers must be enrolled in SAP's Max Success Plan commercial agreement — SAP's premium success management tier that includes dedicated success managers, proactive health monitoring, and upgrade support. The Max Success Plan represents an additional commercial commitment above standard support contracts.

SAP's framing of these conditions is that on-premise Joule deployment requires significant integration and configuration support, and the Max Success Plan ensures that infrastructure is available. Critics in the SAP community have noted that the conditions effectively require on-premise customers to be in active commercial transition toward cloud — which may serve SAP's migration incentive objectives as much as it serves technical necessity.

For Cloud ERP Private Edition customers (on-premise S/4HANA deployed on SAP-managed infrastructure through RISE with SAP), the terms are more favorable: SAP will activate up to three Joule Assistants at no additional cost during cloud onboarding, covering finance, HR, and supply chain workflows.

What Joule Work Means for SAP's Autonomous Enterprise Vision

Joule Work is not a standalone product — it is the user-facing layer of SAP's Autonomous Enterprise architecture, the overarching strategic vision SAP unveiled at Sapphire 2026. In this architecture:

• Joule Work is the workspace where business users state intent and monitor execution
• Joule Assistants are domain-specific coordinators (Finance Assistant, HR Assistant, Supply Chain Assistant) that interpret intent and orchestrate agents
• Joule Agents are task-level executors that interact directly with SAP applications, APIs, and data sources to complete specific steps
• SAP AI Agent Hub is the governance and orchestration layer connecting the agent ecosystem — including third-party agents from SAP partner ecosystem companies

By extending this architecture to on-premise customers (under the commercial conditions), SAP is effectively arguing that the Autonomous Enterprise is not a destination requiring full cloud migration — it is a capability layer that can be progressively adopted from wherever you are in the SAP landscape.

What SAP Customers on ECC and On-Premise S/4HANA Should Do Now

1. Assess your current commercial position: Calculate your current split between SAP maintenance spend and SAP cloud subscription spend. If you are already above 50% cloud, you may qualify for Joule access with only the Max Success Plan requirement to address. If you are below 50%, model what cloud products would need to be adopted to reach the threshold — and whether those products deliver independent business value.
2. Evaluate the Max Success Plan ROI: Request a proposal from your SAP account team that details the Max Success Plan cost and coverage. The plan may offer value beyond Joule access — dedicated success management and proactive upgrade support are genuinely useful for organizations managing complex SAP landscapes.
3. Identify your top 3 Joule use cases: Before optimising for access, clarify which specific Joule capabilities would deliver measurable business value in your context. Finance exception resolution, HR query deflection, and procurement agent automation are the most mature and widely deployed Joule use cases. Starting with a defined use case makes the commercial conversation more grounded.
4. Consider the free design-time access offer: SAP is offering free Joule Work design-time access through end of 2026. Even if your organisation is not ready for production deployment, this is an opportunity to start building familiarity with the Joule Studio environment and prototype custom assistant configurations without commercial commitment.
5. Review your ECC migration timeline in light of this announcement: For some organizations, the on-premise Joule announcement may reduce the urgency of immediate S/4HANA migration. For others — particularly those where full AI capability (not just partial access) is strategically important — it may clarify that cloud migration remains the faster path to full Joule capability and continuous SAP innovation.

SAVIC's Perspective on the Joule Work Announcement

At SAVIC, we believe the Joule Work announcement is strategically significant — both for what it enables and for what it reveals about SAP's commercial strategy. The on-premise AI access pathway is genuine, but the 50% cloud spend condition means it is most accessible for organizations already meaningfully invested in SAP cloud products.

For customers earlier in their cloud journey, the most practical near-term path to full Joule capability often remains RISE with SAP Private Edition — which provides on-premise S/4HANA deployment with cloud managed infrastructure, the most favorable Joule activation terms, and a clear path toward the full Autonomous Enterprise feature set as it is released.

SAVIC's SAP transformation practice helps organisations assess their SAP AI readiness, model the commercial pathways to Joule access, and build the business case for S/4HANA and cloud adoption. Contact our team to discuss a Joule readiness assessment for your organisation.