RISE costs more than the quote and less than the scare, and the model decides
RISE with SAP is sold as savings through modernization, and the pitched saving is framed against a worst case stay scenario rather than a disciplined ECC or S/4HANA on premise model: the honest comparison shifts the answer, because RISE costs more than the headline quote suggests once the excluded scope is priced in, and less than the account team's stay model claims. The truth sits between, and only a full term model, run through the first renewal, surfaces it.
Prepared by Redress Compliance · August 8, 2026 · SAP advisory. Based on 35 to 45 SAP RISE evaluations and negotiations supported 2024 to 2025.
Executive summary
The proposals carried a 15 to 30 percent effective premium, and realized pricing landed at 40 to 60 percent of the ask. Opening RISE proposals carried an effective premium of 15 to 30 percent above a disciplined stay model once excluded lines were priced in.
And realized pricing landed at 40 to 60 percent of the opening ask once a clean estate baseline and a credible stay path were on the table: the bundle includes the SAP application stack, the underlying cloud, and basic operations, and excludes the integration, customization, archive.
And partner work that drive most real cost.
Scope is the cost, and right sizing cut 10 to 20 percent that compounds.
The FUE count and the Industry Engine attach decide most of the bundle base, both having grown silently since the original signature.
Mergers adding unreconciled populations and projects leaving engines that never retired: right sizing FUE and engines before the proposal cut 10 to 20 percent off the bundle base, and the saving compounds every year of the term while also shrinking the absolute size of every future uplift.
The single largest swing factor in the file was scope, not rate.
Three hidden lines surface in the first twelve months, and partner spend is the swing.
Integration and middleware, the data flows needing adapters once SAP runs in the RISE tenant; custom code remediation, the ECC to S/4HANA adjustments deferred into the program budget.
And archive and decommissioning, the real path to retire ECC that rarely sits in SAP's scope: each is small alone and material together, and partner fees are the swing line between a defensible TCO and a punishing one in every full term model we built.
Fixed in deliverables and day rates before signature or filling whatever space the SAP saving created.
The ECC runway prices the alternative, and the model runs through the renewal.
Standard ECC support steps down after 2027 with extended maintenance through 2030 at a published uplift near 2 percent, and past 2030 the runway is a commercial conversation, which bounds the stay path without closing it: the honest comparison runs at least through the first RISE renewal.
A five plus five model with explicit second term assumptions, because multi year commitments deliver a meaningful first term price and then face an open ended renewal, with the protection in the cap, the swap, and the exit clauses rather than the term length.
And the architecture choices of the first eighteen months deciding whether that renewal is competitive or captive.
What the bundle includes, and what it leaves out
| Line | In the RISE bundle | The reality |
|---|---|---|
| The SAP application stack | Included | The order form number, the smaller one |
| Cloud infrastructure and basic operations | Included | The hosting the subscription wraps |
| Integration and middleware | Excluded | Adapters and replatforming inside twelve months |
| Custom code remediation | Excluded | The ECC to S/4HANA work deferred into the program |
| Archive, decommissioning, and partner delivery | Excluded | The swing lines that decide the real TCO |
The line on the order form is the smaller number.
The line items that hit the budget over the term are integration, archive, custom code remediation, and partner spend.
Each modelable in advance with reasonable accuracy, which is why surfacing them before signature is the highest value step in the program: SAP delivers the software and partners deliver the program.
The proposal carrying the subscription plus a small services line while the body of the migration sits with the integrator, and the partner fees left as a residual fill whatever space the pitched saving created.
The full term model, both paths priced
- The disciplined stay path: ECC on the published runway, standard support to 2027 and extended near 2 percent to 2030, against the worst case model the account team compares to.
- The RISE path, fully loaded: the subscription plus the excluded lines, integration, remediation, archive, and the partner program at fixed deliverables.
- The scope pass first: FUE and Industry Engines right sized before the proposal, the 10 to 20 percent that compounds every year.
- The horizon through the renewal: five plus five with explicit second term assumptions, because the first term price is real and the renewal is where lock in pays for itself.
- The clause set: the uplift cap, the swap right, and the exit terms, the protection that the term length alone never provides.
The SAP RISE negotiation brief
The full term model, the excluded line surfacing, the FUE right sizing pass, and the clause set worked end to end.
Get the white paper →Lock in, real but bounded
The lock in question resolves into an architecture question: the choices made in the first eighteen months on RISE, how deeply the estate binds to tenant specific services against portable patterns, decide whether the first renewal is competitive or captive.
And the buyers who priced convenience at signature discovered at renewal that they had priced captivity.
The renewal itself repeats the pattern every SAP report in this family measures, the year four cliff and the open ended second term, which is why the model runs through it rather than stopping at the first term's edge.
The negotiation mechanics run in the deployment models analysis, where the RISE bundle priced 10 to 20 percent above the unbundled parts; the digital access exposure that follows the estate into RISE in the indirect access liability report; the audit posture in the audit defense framework.
And the support alternative bounding the stay path in the third party support comparison.
- 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 engagements, 2024 to 2025
Across roughly 35 to 45 SAP RISE evaluations and negotiations our team supported between 2024 and 2025, the gap between the pitched saving and the realized TCO was the most consistent finding:
Of opening proposals above a disciplined stay model, once the excluded lines were priced.
Off the bundle base from right sizing FUE and engines before the conversation.
The report's framing holds the middle deliberately: RISE costs more than the quote and less than the scare, the pitched saving is an artifact of the worst case comparison, and the effective premium is an artifact of the excluded lines.
So the only number that decides anything is the full term model of both paths, scope right sized, exclusions priced, partner program fixed, and the horizon run through the first renewal.
The buyers who built that model negotiated the residual against a smaller defensible scope and landed at 40 to 60 percent of the ask; the buyers who compared the order form to the scare story signed whichever number frightened them less.
Your first five moves
- Right size FUE and Industry Engines before any proposal, the 10 to 20 percent that compounds every year.
- Price the excluded lines before signature: integration, remediation, archive, and the partner program at fixed deliverables.
- Build the disciplined stay model on the published runway, not the account team's worst case.
- Run the model through the first renewal, five plus five, because the first term price is not the cost.
- Negotiate the cap, swap, and exit clauses, and keep the first eighteen months portable. The SAP practice runs the model with you.
Frequently asked questions
Does RISE with SAP actually save money?
Against the worst case stay scenario the account team presents, yes; against a disciplined ECC or S/4HANA on premise model, opening proposals carried an effective premium of 15 to 30 percent once excluded lines were priced in.
The truth sits between the pitch and the scare, and only a full term model of both paths, run through the first renewal, surfaces it.
What does the RISE bundle exclude?
The lines that drive most real cost: integration and middleware adapters once SAP runs in the RISE tenant, custom code remediation for the ECC to S/4HANA move, archive and decommissioning to actually retire ECC, and the partner delivery program that carries the body of the migration.
The bundle includes the application stack, the cloud, and basic operations, and the order form number is the smaller one.
How much can RISE proposals be negotiated down?
Realized pricing landed at roughly 40 to 60 percent of the opening ask once a clean estate baseline and a credible stay path were on the table.
And the single largest swing factor was scope: right sizing the FUE count and Industry Engine attach before the conversation cut 10 to 20 percent off the bundle base, a saving that compounds every year and shrinks every future uplift.
How long can you stay on SAP ECC?
Standard support steps down after 2027, extended maintenance is available through 2030 at a published uplift near 2 percent.
And past 2030 the runway is a commercial conversation: the runway bounds the stay path without closing it, which is what makes the disciplined stay model a credible alternative rather than a bluff.
Third party support extends the boundary further for stable estates.
What is the biggest hidden cost in a RISE migration?
Partner spend, the swing line between a defensible TCO and a punishing one in every full term model we built: SAP delivers the software while the integrator and functional partner deliver the program, and the proposal carries only the subscription plus a small services line.
Fix the deliverables and day rates before signature, or the partner fees fill whatever space the pitched saving created.
How locked in is RISE with SAP?
Really but boundedly: the architecture choices of the first eighteen months, tenant specific services against portable patterns, decide whether the first renewal is competitive or captive, and the protection lives in the uplift cap, the swap right, and the exit clauses rather than the term length.
The honest model runs five plus five with explicit second term assumptions, because the renewal is where lock in pays for itself.
