One lever is won with a document, one with a schedule, and one with a parallel process
The order form reads as a flat per user subscription and the account team frames it as standard. Three levers move it materially, and the reason most buyers get none of them is that they treat all three as discount conversations. They are not the same kind of ask, they are not won in the same way, and only one of them is about price at all.
Prepared by Redress Compliance · August 10, 2026 · SAP advisory. Based on 30 to 40 SAP RISE negotiations run, 2024 to 2025.
Executive summary
The platform credit pool roughly triples when it is tied to documented use cases. It opened at 3 to 5 percent of annual contract value and closed at 8 to 12 percent once the buyer brought a list of named extensions, integrations, and services with owners attached.
That is won with a document rather than with a negotiating position, and on a large agreement the swing is worth more in absolute terms than several points of rate discount, which is exactly the line buyers tend to accept as a throw in.
The legacy maintenance bridge defaults to five years at full price for a system you are actively decommissioning. Left alone, the bridge line carries full legacy maintenance across the transition, which means paying the old run rate while the estate migrates off it.
A step down cap tied to a measured run down cut that tail by 50 to 75 percent over the term. This one is won with a schedule rather than a rate: the ask is a declining commitment matched to migration milestones, not a discount on a flat one.
A credible alternative scored in parallel widened the discount by 8 to 15 points. Not referenced, not threatened, scored: run the comparison as a live evaluation with the same rigour applied to both, and the discount moves.
This is the only one of the three that behaves like a conventional price lever, and it is won by a process running alongside the negotiation rather than by anything said inside it.
The practical consequence is that a buyer who only asks for a better rate gets none of the three. The credit pool needs evidence, the bridge needs a structure, the alternative needs a parallel workstream, and none of those is produced by a procurement conversation about percentage.
Bring the use case list, the migration run down, and the scored comparison to the table, and the negotiation stops being about the number on the order form.
The five lines inside one subscription
| Component | What it is | Whether it moves |
|---|---|---|
| Core subscription | The ERP priced on the blended user metric | Moves on the count, more than on the rate |
| Platform credit pool | A consumption balance for extensions and integration | Triples on documented use cases |
| Infrastructure layer | Hyperscaler compute, storage, and network inside the bundle | Rarely separable, ask for the split at signature |
| Managed services | Operations, upgrades, and support | Scope is negotiable, price is largely not |
| Legacy maintenance bridge | The old estate's maintenance during transition | Cuts 50 to 75 percent with a step down schedule |
The bridge line is the one that rewards structural thinking rather than commercial pressure, and it is worth understanding why the default is so expensive. During a transition you are running two estates: the target platform you are paying to build and the legacy platform you are paying to leave.
The standard bridge charges full legacy maintenance for the whole term, which prices the old system as though it will still be fully loaded in year five, when the entire point of the programme is that it will not be.
A step down cap replaces that flat assumption with a declining schedule tied to migration milestones you are already committed to hitting, so the maintenance curve follows the decommissioning curve. Ask for the schedule, not the discount. The conversion mechanics sit in the RISE deep dive.
What each lever actually costs you to obtain
- The credit pool costs you a document. A list of named extensions, integrations, and services with owners and rough consumption estimates, produced before the order form is drafted rather than after.
- The bridge costs you a plan. A migration run down with dated milestones, because the step down schedule has to attach to something the programme is already committed to delivering.
- The alternative costs you a parallel workstream. A genuine scored evaluation rather than a reference, since the discount responds to the credibility of the process rather than to the existence of a competitor.
- Indirect and digital access scope costs you an audit. Establish the document count before signature, because it sits outside the user metric and prices as an add on once the shape is set.
- Exit terms cost you nothing except the willingness to raise them early, and they decide the posture at every subsequent renewal: data egress, transition support, and a published off ramp.
RISE with SAP against on premises
The conversion arithmetic, the offsets worth negotiating, and where the private edition case genuinely holds against a tuned estate.
Get the white paper →Why the levers have to be raised before the draft
Each of the three levers depends on an artefact the buyer has to produce, and each artefact takes time that a live negotiation does not contain.
That is the practical reason they are so rarely won rather than any reluctance on the seller side: by the time the order form arrives, the use case list has not been assembled, the migration run down has not been dated, and the alternative has not been scored.
So all three asks collapse into the one thing a buyer can do instantly, which is ask for a lower rate.
The seller is entirely comfortable with that conversation, because it is bounded and it is the conversation they prepared for. Start the three artefacts before the commercial process opens and the shape changes.
The use case list turns the credit pool from a goodwill item into a sizing exercise, and the pool roughly triples as a share of contract value once it does.
The dated run down converts the bridge from a flat five year assumption into a schedule, which is where 50 to 75 percent of the legacy tail lives.
And the scored alternative widens the discount by 8 to 15 points, not because anyone threatens to leave, but because the seller can see the evaluation is real. Two further terms belong in the same early window.
Fix the digital access scope before signature, since it sits outside the user metric and becomes an unnegotiated add on afterwards.
And settle exit terms, data egress, transition support, and a published off ramp, while the vendor wants the deal, because those clauses determine your posture at every renewal that follows and cost nothing to obtain now. The fit question that should precede all of it sits in is RISE right for you.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across RISE negotiations, 2024 and 2025
Across roughly 30 to 40 SAP RISE negotiations run between 2024 and 2025, the order form read as standard while a small number of levers quietly moved the outcome:
Where the platform credit allocation opened and closed as a share of annual contract value, once tied to documented use cases with named owners.
Legacy maintenance saved across the term by replacing the flat five year default with a step down cap tied to migration milestones.
Three patterns recurred: the credit pool opening at 3 to 5 percent of annual contract value and closing at 8 to 12 percent once tied to documented use cases, the legacy bridge defaulting to full maintenance for five years until a step down cap cut the tail 50 to 75 percent.
And the discount widening 8 to 15 points where a credible alternative was scored in parallel.
The buyer side move is to recognise that these are three different kinds of ask. Bring the use case list, the dated migration run down, and the scored comparison, and negotiate each lever explicitly and in writing before the order form is drafted. The wider library sits in the SAP practice.
Your first five moves
- Build the platform use case list before the order form is drafted, with named extensions, integrations, owners, and rough consumption, because that document is what roughly triples the credit pool.
- Date the migration run down and ask for a step down cap on the legacy bridge, since the flat five year default prices a system you are actively decommissioning at full rate.
- Score an alternative in parallel rather than referencing one, as the discount responds to the credibility of a real evaluation and widened 8 to 15 points where one existed.
- Establish the digital access document count before signature, because it sits outside the user metric and prices as an unnegotiated add on once the commercial shape is set.
- Raise exit terms early: data egress, transition support, and a published off ramp, which cost nothing while the vendor wants the deal and set your posture at every renewal after it. The SAP practice runs the levers with you.
Frequently asked questions
Is the RISE price actually fixed?
No. The order form reads as a flat per user subscription and the account team frames it as standard, but the rate, the platform credit pool, and the bundle composition all flex.
The reason most buyers move none of them is that all three get treated as discount conversations when only one of them behaves like a price lever.
How much does the platform credit pool move?
It opened at 3 to 5 percent of annual contract value and closed at 8 to 12 percent once tied to documented use cases in our negotiations.
That is roughly a tripling, and on a large agreement it is worth more in absolute terms than several points of rate discount, which is why treating it as a throw in is expensive.
What is the legacy maintenance bridge and why does it matter?
It is the line covering maintenance on the estate you are migrating away from, and it defaults to full price for around five years. That prices the old system as though it will still be fully loaded at the end of the programme.
A step down cap tied to the measured migration run down cut that tail 50 to 75 percent over the term.
Does a competitive alternative really widen the discount?
By 8 to 15 points where it was scored in parallel rather than merely referenced. The distinction matters: the discount responds to the credibility of a genuine evaluation running alongside the negotiation, not to the existence of a competitor being mentioned in a meeting.
It requires a real workstream to produce.
Why do buyers usually get none of the levers?
Because each depends on an artefact that takes time a live negotiation does not contain: a documented use case list, a dated migration run down, and a scored alternative.
By the time the order form arrives, none exists, so all three asks collapse into a request for a lower rate, which is the bounded conversation the seller prepared for.
When should indirect and digital access be settled?
Before signature. It sits outside the user metric entirely and is licensed on document volume, so once the commercial shape is framed it prices as an add on rather than as a negotiated term. Establish the document count while the deal is still open, not after the user count has been agreed.
Which terms decide the next renewal?
Exit terms, meaning data egress, transition support, and a published off ramp. They cost nothing to obtain while the vendor wants the deal and they set your posture at every renewal that follows, because a subscription you cannot credibly leave prices differently from one you can.
