SAP Joule is SAP's AI assistant and agent layer, embedded inside SAP's cloud applications, where it answers questions, drafts content and runs a growing set of prebuilt agents. At Lleverage we think Joule is genuinely useful inside a clean, current, cloud SAP estate, and close to irrelevant outside one.
Most of the manufacturers, wholesalers and logistics operators we talk to are not inside that estate. They run ECC alongside a Business Central site from an acquisition, an AFAS payroll system, a warehouse system nobody wants to touch, and a shared mailbox where the actual orders arrive. Joule is real, it works, and it draws a hard line around SAP. This piece explains what falls inside that line, what falls outside it, and how to decide which side your operation is on.
That view comes from building agents for companies whose order desks and finance teams look much like yours, often on top of the same SAP tables Joule reads. Our order-to-cash agents are the closest comparison if you want to see an agent layer that sits across systems rather than inside one. Book a demo to put your own documents through them.
What is SAP Joule?
Joule is SAP's generative AI assistant, embedded across SAP's cloud portfolio and reachable from inside the applications a user already works in. It answers questions about business data, navigates to transactions, drafts text such as supplier communications and job descriptions, and increasingly executes multi-step work through agents rather than only responding to prompts.
The 2023 version was a copilot in the ordinary sense: a chat box that knew where things lived. What shipped through 2025 and 2026 is different in kind. According to SAP's Q1 2026 Business AI release, Joule now spans 35 SAP solutions with 40 specialised agents and more than 2,400 Joule Skills. Those cover finance, supply chain, procurement and HR. A multi-agent protocol lets them hand work to each other.
Alongside the prebuilt agents sits Joule Studio, SAP's builder for custom agents and skills, which reached general availability in early 2026. Studio is the part that matters most to an operations team, because it is the only route to an agent that does something SAP has not already shipped.
What does SAP Joule do well?
Joule is strongest where the work is entirely inside SAP and entirely inside SAP's own definition of a process. It handles an open-items summary, a jump to the right transaction, a supplier email drafted from a purchase order, or a prebuilt dispute or sourcing agent. None of that needs integration work, because there is nothing to integrate.
Three advantages are real and worth stating plainly. Authorisations come for free, since Joule inherits the user's existing SAP roles rather than needing a parallel permission model. The data is already clean by definition, because it is the master data SAP is holding. And the whole thing is SAP's problem to run, which for a lean IT team is a genuine consideration.
There is a fourth that gets less attention. SAP has built bidirectional integration between Joule and Microsoft 365 Copilot, so a user can reach SAP data from Teams without leaving the conversation they were already in. For organisations that live in Microsoft, that removes a real friction, and it is the sort of thing only the vendor itself can ship.
Here is where we land. If your whole operation runs on current-release SAP cloud, staffed by people in SAP screens all day, Joule is the obvious first thing to switch on. The argument for anything else starts where that sentence stops being true.
Which SAP systems does Joule require?
Joule is cloud-only. It runs on S/4HANA Cloud in both public and private editions, SuccessFactors, Ariba, Concur and SAP Analytics Cloud. According to ERP Research's 2026 assessment, it is not available on SAP ECC or on on-premise S/4HANA, and it expects customers to be on current release versions rather than a comfortable two-year-old one.
There is a second gate that is easier to miss and harder to pass. Joule assumes a clean core. Most SME estates that have run for a decade have been heavily modified. Where that is true, the standard agents reason about a process that no longer matches the one the business runs. The assistant is not wrong so much as it is describing a different company.
Put those two gates together and a large part of the European mid-market is excluded before the pricing conversation starts. That is not a criticism of SAP. It is a deliberate product decision that pulls customers towards clean-core cloud migration, which is SAP's strategy stated out loud. It just means the answer to "should we use Joule" is often decided by your migration roadmap rather than by anything about AI.
What does SAP Joule cost?
Joule's baseline conversational features are included with the underlying cloud subscription, and the premium scenarios, which is where the agents live, run on consumption. Customers buy AI Units up front and burn them as agents work. Forecasting that consumption before you have run the agents is the part finance teams find uncomfortable.
According to ERP Research's 2026 pricing breakdown, AI Units are priced at roughly €7 each, with a minimum purchase around 100 units. Joule Studio capacity sits in a very different band. That analysis puts it between $42,000 and $96,000 per unit annually, with agent-action overages of $0.08 to $0.18. The same analysis puts SAP AI at between 3% and 12% of total RISE contract value.
| SAP Joule | Cross-ERP agent layer | |
|---|---|---|
| Runs on ECC or on-premise S/4HANA | No | Yes |
| Works across non-SAP systems | Limited | Yes |
| Needs a clean core | Yes | No |
| Reads order documents from a shared mailbox | Limited | Yes |
| Pricing model | AI Unit consumption | Contracted per process |
| Owned by | SAP | You and your implementation partner |
| Available before an S/4HANA migration | No | Yes |
The table is our framing, not SAP's, and the right-hand column describes the category rather than any one vendor. The point of it is that the two options are not really competing for the same budget line. One is part of an ERP modernisation programme. The other is something an operations team can run this quarter regardless of where that programme stands.
Where does SAP Joule stop?
Joule stops at the edge of SAP. That sounds obvious and it is the single most consequential thing about it, because the work that costs an SME the most is rarely inside one system. An order arrives as a PDF in a shared inbox. It references a customer article code that only exists in a spreadsheet, and needs a unit conversion that lives in someone's head. Then it has to land in an ERP that may not be SAP at all.
Three specific gaps show up again and again in our own deals. The first is inbound documents. Email, PDF and Excel order intake sits outside the SAP boundary until someone has typed it in, which is precisely the work that needed automating. The second is heterogeneous estates, where a group has SAP at one site and something else at three others, and a Joule agent cannot reason across that. The third is customer-specific business rules, the accumulated exceptions that make a real order desk work and that no standard agent ships with.
That last one is worth dwelling on. At Xpol, one agent codifies 25 separate customer rulesets covering unit conversions, weekday-specific label text and multi-depot splits, which had previously lived with individual senior staff. That is not a feature request SAP could have anticipated. It is the shape of the business, and something has to hold it.
"It's a matter of building trust in the organisation with these kinds of initiatives. You can't just throw something like this over the fence." Cees Maaskant, General Manager, Xpol
What are the alternatives to SAP Joule?
For companies that cannot use Joule, or that need work done outside SAP, the practical options fall into three groups. Document and order-intake specialists read inbound paperwork and push it into an ERP. General automation and agent builders wire services together for whoever will maintain them. Cross-ERP agent layers, where Lleverage sits, run defined operational processes inside whichever systems the customer already has.
Choosing between them comes down to a question that has nothing to do with model quality: who owns the thing on the Tuesday after go-live. A document specialist gives you a very good extraction engine and leaves the exceptions with your team. A general builder gives you a canvas and expects an engineer. An agent layer that ships with forward-deployed implementation is the option where the first process runs in production before anyone signs off on a roadmap.
In our opinion, for SMEs that make, move and sell physical goods, the deciding factor is whether the work clears inside the ERP without a person retyping it. That is why our own proof is stated in those terms. At Topa Bathroom Products, over 90% of incoming orders now land directly in Business Central with no manual entry, and four FTEs moved to after-sales and service planning. At Xpol, roughly 20 minutes of manual handling per large order disappeared across 150 orders a week, which absorbed both a retiring specialist's workload and volume growth without a hire.
If your estate is SAP-heavy but not clean-core cloud, the more useful reading is our guide to filling SAP gaps without customising SAP, which covers the integration patterns in detail. For the mechanics of connecting to any ERP, our integration layer lists what is already supported.
How should an SME running SAP decide?
Start with three factual questions before any vendor conversation. Are you on S/4HANA Cloud on a current release, is your core close enough to standard that SAP's own process definitions describe your business, and is the work you want automated actually inside SAP. Three yes answers point at Joule, and the rest of the decision is a consumption forecast.
A single no changes the question entirely. If you are on ECC, Joule is not available and no amount of interest will change that before a migration. If your core is heavily modified, Joule Studio can still build against it. But that is bespoke agent development inside a consumption pricing model. It is a different project from the one the sales conversation described. If the work starts in a mailbox, nothing SAP-internal reaches it.
The honest answer for a lot of SMEs is both, in sequence. Run an agent layer over the estate you have now to stop the manual handling, and switch Joule on for the SAP-internal work when the migration lands. Those two decisions do not block each other, and treating them as one choice is how automation gets postponed for two years. That is where we land, and it is the recommendation we give even when it means we are not the whole answer.
Frequently Asked Questions
Is SAP Joule available on SAP ECC?
No. Joule runs on SAP's cloud applications, including S/4HANA Cloud public and private editions, SuccessFactors, Ariba, Concur and SAP Analytics Cloud. According to ERP Research's 2026 assessment, it is not available on SAP ECC or on on-premise S/4HANA, so ECC customers need a migration before Joule becomes an option at all.
How much does SAP Joule cost?
Baseline Joule features are included in the underlying cloud subscription, and premium agent scenarios consume prepaid AI Units. ERP Research's 2026 breakdown puts AI Units at roughly €7 each, with a minimum around 100 units. It puts Joule Studio capacity between $42,000 and $96,000 per unit annually, and SAP AI overall at 3% to 12% of RISE contract value.
Can SAP Joule read orders from an email inbox?
Not in the way an order desk needs. Joule operates on data already inside SAP applications, so an emailed PDF or Excel order remains outside its reach until a person or another system has entered it. Inbound document intake is handled by document processing products or a cross-ERP agent layer sitting in front of the ERP.
What is the difference between Joule and Joule Studio?
Joule is the assistant and the prebuilt agents SAP ships and maintains. Joule Studio is the builder that lets customers create their own agents and skills against SAP and non-SAP systems, generally available since early 2026. Studio is the route to anything SAP has not already built, and it is priced separately from baseline Joule.
Does Joule work alongside Microsoft Copilot?
Yes. SAP has built bidirectional integration between Joule and Microsoft 365 Copilot, so users can reach SAP data from Teams and Office surfaces and reach Microsoft content from Joule. For a comparison of what each assistant actually executes rather than drafts, see our Copilot Studio comparison.
See what runs outside SAP
Some work starts in a mailbox, spans more than one ERP, or lives in the exceptions your senior staff carry in their heads. Joule will not reach it, whatever your migration timeline says. That work is what our agents are built for, and the fastest way to test the claim is with your own documents. Book a demo and bring a week of real orders.