RISE with SAP: Contractual AI Commitments From 2026

At SAP Sapphire 2026 in Orlando, SAP communicated a series of contract changes with immediate consequences for existing and new RISE with SAP customers. The central change, embedded in the keynote announcements around the "Autonomous Enterprise", is this: the updated RISE with SAP package now contains a contractual commitment to activate three Joule assistants within the first contract year.

This requirement is not a recommendation or a best-practice hint from an adoption campaign. It is part of the contract. Anyone signing a new RISE with SAP contract or renewing an existing one is explicitly agreeing to this activation commitment. The Max Success Plan extends the requirement further: the Joule adoption commitment expands to the entire organisation.

In parallel, GROW with SAP customers receive immediate access to the full agent portfolio at onboarding, with no staged activation requirement. SAP is pursuing a clear differentiation strategy between the two cloud entry paths.

Why this matters for contract owners

The Joule activation commitment hits companies at a point that often only becomes visible late in negotiations: the interface between technical readiness and commercial obligation. Joule has technical prerequisites that are not automatically satisfied at contract signature. These include configured entitlements on SAP BTP, set-up Cloud Identity Services (IAS/IPS) and a working SAP Build Work Zone. Anyone who does not meet these prerequisites in the first year is in arrears against a commitment that is already locked in the contract.

Add to that the billing logic of AI capacities. With AI Units, SAP introduced a new dimension into pricing: Joule Premium is billed at 1 to 8 AI Units per user per month. This dimension is already priced into many 2026 renewal offers, even when concrete usage is not yet defined at the time of signing. Analysts report that AI components account for 15 to 25 percent of total volume in individual renewal offers, without this being addressed explicitly in commercial preparation.

Forrester picked up the theme of "concentration risk" in its assessment of SAP Sapphire 2026: consolidation onto a single platform concentrates dependencies on several layers at once. Security posture, pricing model and innovation path sit with the same vendor. This is not an argument against SAP, but a signal that contract design should actively account for this concentration.

Further factors from the Sapphire context complete the picture. The SAP ERP Private Edition Transition Path, enabling ECC operations through 2033, is only available for signature in 2026. And migration credits lose around 10 percent in value per year according to current market observation. At the first S/4HANA renewal after migration, a pricing uplift of 20 percent should be assumed in planning.

What you can do

1. Review the Joule activation clause in the contract

Request from your SAP account executive a written clarification of which three Joule assistants must be activated contractually and within what window. Clarify what applies if the requirement is not met: contract breach, back payment or SLA adjustment. This point is negotiable as long as the contract is not yet signed.

2. Assess technical prerequisites before signing

Joule activation requires BTP configuration, Identity Services and Build Work Zone. A gap analysis between your current technical state and these prerequisites gives clarity on what the commitment really demands in the first contract year. That effort can be brought into the contract negotiation.

3. Steer AI Units as an explicit budget dimension

AI Units are not a standard component of classic RISE calculation. Before signing, define which Joule functions are to be used under which billing model, and document the AI Unit allocation in the contract. That keeps the cost trajectory plannable.

4. Actively assess the migration window and transition options

The SAP ERP Private Edition Transition Path is only available in 2026. Anyone running ECC systems who wants to keep the option of a staged migration open should evaluate this window before year-end. That does not require an immediate decision but does require an informed view.

5. Check the Max Success Plan for organisational scope

If the Max Success Plan is part of your RISE package or proposed in an offer, check explicitly which Joule adoption commitments come with it and which organisational units they cover. Extending to the "entire organisation" is a material difference compared to the base RISE package.

Conclusion

SAP signalled at Sapphire 2026 that AI adoption is no longer optional but built into the contract. The requirement to activate three Joule assistants in the first contract year is a concrete example. For contract owners this means: anyone signing or renewing a RISE with SAP contract is at the same time agreeing to a technical implementation commitment, whose feasibility depends on the company’s own infrastructure and BTP readiness.

The commercial layer and the technical layer can be deliberately aligned during preparation. The window for that sits before signature.

Sources:
SAP News Center (2026): SAP Unveils the Autonomous Enterprise
SAP News Center (2026): SAP Sapphire Keynote 2026
SAP Community (2026): Max Success Plan at SAP Sapphire 2026
Forrester (2026): SAP Sapphire 2026: The Autonomous Enterprise Is Credible, But It Comes With Concentration Risk
Redress Compliance (2026): RISE with SAP in 2026: What Changed
SAP Licensing Experts (2026): SAP AI Licensing 2026
SAP Community (2026): Joule Prerequisites and Activation