TotalTek Blog | SAP, PMO, Maritime & AI Insights

Joule vs. Claude? Wrong Question. Here's What SAP Is Really Doing.

Written by Ray Kowalski | Nov 18, 2026, 9:23:18 PM

I've been asked some version of this a lot lately, by customers, by colleagues, and even by people at ASUG TechConnect: “Why is SAP pushing Joule when everyone’s already using Claude?” With 2027 AI roadmaps getting locked in right now, it deserves a straight answer.

It’s a fair question, but it rests on a false choice. Joule and Claude aren’t competitors. They sit at different layers of the same stack, and SAP has chosen to use both.

Joule is the front door. Claude is in the engine room.

At Sapphire 2026 in May, SAP and Anthropic SAP and Anthropic announced that Claude will be "a primary reasoning and agentic capability embedded across SAP's AI-enabled solution portfolio."

That means agents coordinating across S/4HANA, SuccessFactors, Ariba, and connected non-SAP systems through the Model Context Protocol.

The flow works like this. A user asks Joule a question. Joule enriches it with business context, roles, and authorizations. Then it hands the request to the model to reason through and act on.

Why does SAP put Joule out front instead of letting customers go straight to the model?

After 13 years inside SAP, I see four reasons, and none of them is an accident.

The first is context. The model is becoming a commodity input. The real moat is the business semantics: what a cost center, a delivery block, or a period-end close actually means in your system. Joule is how SAP keeps that layer under its own roof.

The second is governance. CFOs and auditors want AI that acts inside existing controls, approvals, and audit trails. SAP says agent actions will follow "the same controls that govern human decisions." That only works if SAP's layer sits between the model and the data.

The third is the gate. Shortly before Sapphire, SAP updated its API policy.Section 2.2.2 now prohibits using SAP APIs with AI systems that "plan, select, or execute sequences of API calls," except through SAP-endorsed architectures.SAP says that's about routing, not blocking. Forrester calls it gatekeeping.

The fourth is optionality. Branding the experience as Joule lets SAP mix or swap models underneath without changing what the customer sees.

Why Claude underneath?

SAP wants agentic, multi-step work: closing the books, rerouting a delayed supplier order, handling a complex employee request. SAP and Anthropic alsoplan to build industry-specific agents for regulated sectors like public sector, healthcare, life sciences and utilities. The integration work that customers would otherwise carry now lives inside SAP’s platform.

The part nobody puts on the slide

Not everyone sees this as openness. Gartner's Christian Hestermanntold The Register that SAP is "closing the door to third-party AI environments, especially agentic environments," and described Claude inside SAP as a "walled garden." Deeper integration also means deeper dependence on one model provider’s roadmap and pricing. And in practice, the line between what Joule does and what Claude does is still blurry.

What this means for SAP customers: my rule of thumb

That blurry line is where the real decisions live. Here's how I help customers sort agent use cases:

  • The agent lives inside one SAP process and needs SAP roles and authorizations → build it in Joule Studio. You inherit SAP's context, controls, and audit trail for free.
  • The agent orchestrates across SAP and non-SAP systems → build it on the model or your own agent platform, but route every SAP call through an SAP-endorsed path. Under Section 2.2.2, a direct API connection is off the table.
  • The agent never touches SAP data → SAP's policy doesn't apply. Choose freely but govern it the same way you govern the rest.

Where the rule breaks: cross-system agents that write back to SAP. Now you have two audit trails, two sets of permissions, and a clean-core strategy to protect. Those aren't technology questions. They're architecture, governance, and change questions.

Joule is only as good as what sits underneath it

Whichever layer you build on, there's one the stack diagram makes look simple: your systems. Joule brings the context and Claude does the reasoning, but both depend on the code and data underneath. In my experience, that's where most customers aren't ready.

Two gaps come up again and again. The first is custom code. Most SAP landscapes run on years of custom ABAP, Fiori apps, and integrations that few people fully understand anymore, and you can't govern an agent acting on processes you can't explain. The second is master data. In Order to Cash, customer, pricing, and tax fields decide whether an order ships and an invoice clears. An agent that releases an order against a broken ship-to record or a stale pricing condition just makes the wrong decision faster.

We built two tools at TotalTek for exactly this layer, on one principle: no tool can test, or act on, what it doesn't understand. Z-Cortex inventories and documents a customer's custom code, then generates regression test cases traced to its logic, so you know what you have before agents start acting on it. OTC DataBridge Copilot cleanses, maps, and validates Order to Cash master data and flags duplicates and discrepancies, with data stewards in control of every decision. That way Joule is reasoning on data your people trust.

Get the foundation and the architecture right before you build

TotalTek'sAI advisory andSAP consulting teams help customers get both the architecture and the foundation right before agents go live.

Two ways to start:

  • Deciding where your agents should live? Book time with me:Book time with Ray Kowalski: Discovery/Info Call with TotalTek - 20min and we'll run your 2027 use cases through the rule above.
  • Worried about what's underneath? Bring us one real custom-code challenge: a custom object, a failed test, or an unresolved remediation issue. Our senior team will trace the dependencies, find the likely root cause, and document the fix in one to two weeks. No cost, and you keep the analysis. Email sales@totaltek.com or message me to set it up.