A 4 to 7 percent stepped uplift compounds to 17 to 31 percent by year five, and four in five buyers deferred the cap

RISE is the largest single commercial commitment most SAP customers make this decade, and it is presented on one cover sheet while it bills on five meters. The escalation clause is the one that compounds, and it applies to whatever pool you agreed on day one.

Prepared by Redress Compliance · August 16, 2026 · SAP advisory. 20 to 30 RISE proposals, conversions, and first cycle renewals, 2024 to 2025.

RISE bundles the application, the infrastructure, the managed services, and a portion of the platform credits into one contract with one signature. The exclusions matter as much as the contents.

A stepped uplift of 4 to 7 percent sounds modest stated annually. Compounded across a five year term it is the largest single price movement in the contract, and it applies to the pool agreed at signature rather than to consumption.

Now stack the pool error on top, because the two multiply rather than add. Take a contract priced at $10m in year one where the proposed FUE count sat 30 percent above the defensible number. The defensible year one price is $7.7m. Across five years at a 5 percent step, the inflated contract totals roughly $55.3m and the defensible one roughly $42.6m. The gap is about $12.7m, and only part of it is the FUE error. The rest is escalation charged on cores of the pool that were never justified.

Buyers describe a year four price cliff, and the language is telling because it implies something arrived unexpectedly. Nothing arrives. A stepped uplift of 4 to 7 percent is written into the contract at signature and applies mechanically every year, so by year four the subscription sits 12.5 to 22.5 percent above where it started and by year five between 17 and 31 percent. What makes it feel like a cliff is that the increases are small enough to absorb individually and the cumulative number is never presented as a total. Nobody models a five year sum on a cover sheet designed to show an annual figure.

That framing matters because it changes when the negotiation has to happen. Roughly four in five buyers who deferred the cap negotiation met the cliff, and the reason is structural rather than tactical: an escalation clause is cheap to shape while the deal is open and effectively impossible to retrofit once signed, because reopening it requires SAP to give up value it already holds. The cap is a signature moment lever, and treating it as something to revisit at the first renewal is the single most common sequencing error in the RISE file.

The compounding also explains why the FUE conversation is worth more than it appears. Proposed counts sat 22 to 38 percent above what could be defended from transaction logs, routinely including terminated users, dormant integration accounts, and double counted approval roles. A rebuild from transaction logs returned 15 to 28 percent of the application tier envelope on every proposal benchmarked. But the saving is not a one time correction. Every dollar removed from the year one pool is a dollar the escalation never multiplies, so the FUE work compounds at the same rate the uplift does, in your favour rather than SAP's.

Three leaks sit outside the headline and each has its own gate. BTP credits stranded 22 to 41 percent of the bundled pool at end of cycle, closed by consolidating credits across the estate and running quarterly burn down reviews. Hyperscaler region lock clauses cost 14 to 22 percent to unwind if you needed to move mid term, avoided entirely by negotiating region portability at signing. And indirect access sits outside the bundle in most variants, running two to four times the buyer's internal estimate on integrated landscapes, which makes it the largest mid term surprise in the contract. The FUE benchmark itself is worked in the RISE pricing benchmarks, the five year model in the TCO reality report, and the wider library in the SAP practice.

• BTP credits stranded 22 to 41 percent of the bundled pool at end of cycle. Consolidate credits across the SAP estate and run a monthly draw review so overage and stranding are both visible before the anniversary.
• Hyperscaler region lock averaged a 14 to 22 percent uplift where a buyer needed to migrate region mid term. Negotiate region portability rights at signing, since the clause costs nothing to include and a great deal to unwind.
• Indirect and digital access sits outside the bundle in most variants, and ran two to four times the buyer's internal estimate on integrated landscapes. It is the largest mid term surprise risk in the contract.
• Infrastructure bills at SAP rates, not your own. Region, environment count, and the right to bring your own hyperscaler discount are negotiable but never default.
• The conversion credit against on premise licence value is negotiable, not fixed, which is the point in the deal where the largest single number moves and the one most often accepted as published.
• Add ons are not in the base bundle. Signavio, Concur, SuccessFactors, Ariba, and Sustainability each price separately, so a bundle comparison that omits them is not comparing the same estate.

RISE is a program rather than a contract event, and the buyer side counter motion is to disaggregate the bundle and operate each line on its own gate across the year rather than only at anniversary.

Across roughly 20 to 30 RISE proposals, conversions, and first cycle renewals, three patterns recur:

The proposed FUE count sat 22 to 38 percent above the count defensible from transaction logs, routinely including terminated users, dormant integration accounts, and double counted approval roles. And the year four price cliff caught roughly four out of five buyers who deferred the cap negotiation to a later cycle.

FUE is not a headcount. User types convert at published ratios and the ratios are asymmetric, so a small change in workforce shape moves the total materially. That asymmetry is why a pool sized on an organisation chart rather than on transaction logs is almost always wrong in SAP's favour.

Watch the briefing · 4:24RISE with SAP Negotiations: Pricing a One-Way DoorWhat the subscription bundles, what you surrender to get it, and the clauses that decide the five year cost.

What does a RISE contract actually bundle?

S/4HANA Cloud Private Edition run as a managed service, hyperscaler infrastructure provisioned by SAP, SAP managed services covering Basis and lifecycle, a bounded BTP credit allocation, and standard ITSM. Add ons such as Signavio, Concur, SuccessFactors, and Ariba are not included in the base bundle.

How much does the stepped uplift actually cost?

A 4 to 7 percent annual escalation compounds to between 17 and 31 percent above year one by year five. Across a five year term the total paid runs roughly 5.4 to 5.8 times the year one figure rather than 5 times, and the difference is the compounding nobody models on the cover sheet.

Why is it called a year four cliff?

Because the increases are small enough to absorb individually and the cumulative total is never presented. By year four the subscription sits 12.5 to 22.5 percent above where it started. Nothing arrives unexpectedly; the clause was written at signature and applies mechanically every year.

When should the cap be negotiated?

At signature, without exception. An escalation clause is cheap to shape while the deal is open and effectively impossible to retrofit once signed, because reopening it asks SAP to surrender value it already holds. Four in five buyers who deferred it met the cliff.

How wrong is the proposed FUE count?

It sat 22 to 38 percent above the count defensible from transaction logs across the proposals benchmarked, routinely including terminated users, dormant integration accounts, and double counted approval roles. Rebuilding from logs returned 15 to 28 percent of the application tier envelope.

Why does the FUE work compound?

Because the escalation applies to the pool agreed at signature. Every dollar removed from the year one pool is a dollar the uplift never multiplies, so a correction made before signing grows at the same rate the increase does, in your favour rather than SAP.

What happens to unused BTP credits?

They strand. Between 22 and 41 percent of the bundled credit pool went unused at end of cycle across the estates reviewed. Consolidating BTP credits across the SAP estate and running quarterly burn down reviews closed the leak.

Is the hyperscaler region negotiable?

The region itself is set at signing and moving later is expensive. Region lock clauses averaged a 14 to 22 percent uplift where a buyer needed to migrate mid term. Region portability rights cost nothing to negotiate at signature and avoid the lock entirely.

Is indirect access included in RISE?

In most variants, no. Digital and indirect access sits outside the bundle and prices separately, and exposure on integrated landscapes ran two to four times the buyer internal estimate. It is the largest mid term surprise risk in the contract.

Is the conversion credit fixed?

No. The credit applied against your on premise licence value is negotiable rather than published, and it is the point in the deal where the largest single number moves. It is also the number most often accepted as presented.