RISE with SAP is sold as savings through modernization. The realized number is a full term TCO that depends on what the bundle excludes and on how the ECC runway is priced. This report reads both sides honestly so the negotiation starts from the right baseline.
RISE with SAP is sold as savings through modernization. The realized number is a full term TCO that depends on what the bundle excludes and on how the ECC runway is priced. Read the real cost first, then negotiate.
About this report
This report reads SAP RISE economics from three angles. None alone settles a decision, but together they bound the real number.
We report bands and directions, not precise discounts. Outcomes vary widely with estate size, industry, customization depth, and timing. Where a single number appears, treat it as the middle of a range.
The honest answer is that RISE costs more than the headline SAP quote suggests once the excluded scope is priced in.
It also costs less than the worst case stay model the account team uses as the comparison. The truth sits between, and only a full term model surfaces it.
The line item that goes 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.
A typical RISE proposal anchors to a three to five year subscription with bundled hosting and basic operations. The cash impact over that horizon depends as much on the program around the contract as it does on the contract itself.
The FUE count and the Industry Engine attach decide most of the bundle base. A clean entitlement review before the proposal almost always trims both.
Both have grown silently since the original SAP signature. Mergers add user populations that were never reconciled, projects spin up engines that never retired, and consultancies leave behind license footprints that nobody owns.
Right sizing FUE in the proposal phase typically takes 10 to 20 percent off the bundle base. That saving compounds every year of the term rather than appearing once and fading. A smaller bundle base also lowers the absolute size of any renewal uplift.
Three lines reliably surface inside the first 12 months on RISE. Each is small in isolation and material in aggregate.
They are the reason the realized TCO sits above the pitched one. Each can be modeled in advance with reasonable accuracy, which is why surfacing them before signature is the highest value step in the program.
SAP delivers the software. Partners deliver the program. In every full term RISE model we have built, partner fees are the swing line between a defensible TCO and a punishing one.
They rarely appear in the SAP led comparison. The proposal carries the subscription number and a small line for SAP services, but the body of the migration sits with a system integrator and a functional partner.
Treat partner fees as a first class budget line. Fix the deliverables and the day rate before signature, and the full term number stabilizes. Leave them as a residual, and they fill whatever space the SAP saving creates.
Most full term models stop at the end of the first RISE term. That is the wrong horizon. The renewal is where lock in pays for itself.
Any honest comparison runs at least through the first renewal cycle. A five plus five model, with explicit assumptions about the second term, separates buyers who are pricing convenience from buyers who are pricing risk.
Both are valid, but they are different decisions. The buyers who model only the first term often discover the second term in a way they would have preferred to avoid.
A move to RISE almost always carries a window where the buyer pays for both the old and the new. ECC continues to run while the migration completes, and the new RISE tenant is live in parallel for testing and cut over.
That window can run from three to twelve months depending on program complexity. The cost is real and is rarely in the SAP proposal.
Model the overlap explicitly, fund it from the program budget, and the surprise disappears. Ignore it, and the first year on RISE looks worse than the model predicted.
The pitched saving is a directional figure, not a contract commitment. It is built against a worst case stay scenario and a hand picked comparable.
Both are chosen to make the move look inevitable. The realized saving is almost always smaller.
In the RISE proposals we have modeled, the pitched saving rarely survives a disciplined comparison. Once a credible ECC stay path or an S/4HANA on premise model is on the table, the saving narrows or flips into a premium.
That is the point at which the conversation becomes a negotiation rather than a confirmation.
The number that makes RISE look most attractive is the one built against an ECC estate that nobody is actually planning to run. Replace it with a disciplined, supported stay path and the saving usually halves or vanishes.
The defensible move is to insist on a like for like comparable in the proposal. The vendor will resist, because the comparable is where the pitch lives.
The buyer who holds firm sees the real number first. Subsequent rounds of negotiation then anchor to that number rather than to the SAP framing.
Pitched savings of 20 to 30 percent are common in the first proposal. Once integration, custom code remediation, archive, partner spend, and indirect access are layered in, the realized saving narrows materially.
For mid size estates the realized saving typically lands between zero and 10 percent. For large global estates with moderate customization, it narrows to low single digits.
For highly customized estates, the realized result usually flips into a premium of low single digits over a disciplined stay path. The pattern is consistent enough to be predictive.
RISE does deliver cash savings in specific shapes. Smaller estates running on aged infrastructure, programs that would otherwise rebuild a data center, and buyers who genuinely want a bundled operations contract often see a defensible saving.
The honest sales motion would lead with these cases. The actual sales motion leads with every account. Separating the two is the buyer side job.
A buyer in one of these shapes can negotiate from a position of fit, not of pressure, and usually signs a better deal as a result.
SAP publishes its product list at the RISE product page, but the price book itself sits behind the proposal. The pitch deck simplifies that price book into a single headline.
The simplification is where the saving lives. Asking SAP to walk through the underlying price book, line by line, is one of the highest value meetings a buyer can hold. It almost always exposes assumptions that the pitch deck hid.
The bundle is narrower than the pitch implies. It covers the SAP application stack, the underlying cloud infrastructure, and basic operational management.
Anything that touches the business, the data, or the existing estate sits outside. That is the boundary line most program budgets miss.
The lines outside the bundle do not go away, they migrate from the SAP order form to the partner statement of work and the internal program. The total bill is the sum.
RISE with SAP, included and excluded scope, the practical view
| Scope area | Inside the bundle | Outside the bundle | Where the cost lands |
|---|---|---|---|
| SAP application licenses | S/4HANA Cloud private edition entitlements | Indirect access beyond the included design | Bundle base, plus risk on indirect |
| Infrastructure | Hyperscaler hosting, system images, monitoring | Network ingress, egress beyond fair use, dedicated lines | Bundle base, plus network on the buyer |
| Operations | Basis, OS patching, S/4HANA upgrades | Functional managed services, application support | Partner statement of work |
| Integration | Standard adapters in scope | Bespoke integrations, middleware, APIs | Partner and internal program |
| Migration | S/4HANA technical conversion tooling | Custom code remediation, data cleansing, archive | Partner statement of work |
| Support | Bundled Enterprise Support equivalent | Extended business support, custom SLAs | Bundle uplift or separate contract |
Indirect access risk does not move with a RISE migration. The contractual model changes, but the underlying digital document and consumption rules persist.
The scope of integration tends to widen on a modern platform. Settle the indirect access design inside the RISE contract, not after it.
The cost of leaving it open is a true up conversation in a future audit, which is exactly the surprise the bundle is supposed to avoid. Buyers who fold the indirect access model into the proposal stage almost always pay less than those who treat it as a follow on conversation.
RISE runs on hyperscalers. That means the residency, the data processing terms, and the sovereignty rules of the chosen region apply.
Regulated estates need this drafted carefully, because a default region is rarely the right one. Cross border data flows that worked on premise can fail audit on a non aligned region.
Fix the region, the certification surface, and the data processing addendum before signature. After signature these become change orders rather than negotiating points.
The bundle covers hyperscaler hosting and standard monitoring. It does not cover the dedicated network connections most large estates use to keep SAP traffic predictable.
Direct connections, ExpressRoute or Interconnect class links, and egress beyond fair use are buyer side lines in every RISE model we have built.
This is a line item most buyers underestimate. A clean estimate from the network team before signature avoids the unpleasant surprise of a six figure annual surcharge.
RISE bundled operations cover the Basis layer, the OS, and S/4HANA upgrades. Application support, the functional help that business users actually call when something breaks, sits outside the bundle.
This is a common source of confusion in the first quarter on RISE. The technical platform is humming, but the functional support model is no clearer than it was on ECC.
Decide before signature whether the functional support stays in house, moves to a partner, or extends through an SAP managed service. Each has a real cost. None is included by default.
SAP has set the runway carefully. Standard support for SAP Business Suite 7, the ECC line, steps down after 2027.
SAP extended maintenance is available through 2030 at a published uplift near 2 percentage points above the standard rate. The path beyond 2030 is a commercial conversation rather than a published policy.
The runway is the lever. It does not force the decision in 2026, but it sets the negotiating window for buyers who want a calm move.
The decision in 2026 is not binary. Three options sit on the table, and each has a defensible shape depending on estate size, customization depth, and program appetite.
The 2030 ceiling matters for buyers who cannot move by 2029. For most large estates, the program runs about 24 to 36 months end to end.
That means the planning conversation belongs in 2026 or 2027 even where the cut over does not.
The cost of starting late is not the missed deadline. It is the loss of negotiating posture. A buyer with a credible stay path keeps SAP honest. A buyer without one signs the proposal as written.
Third party support is not the right answer for most large SAP estates, but it is a useful posture lever. The existence of providers like Rimini Street and Spinnaker Support reframes the SAP support fee as a price, not a requirement.
A buyer who has modeled third party support credibly, even without intending to use it, walks into the RISE conversation with a number to anchor against.
Used carefully, the option stays in the room as a counterweight. Used as a bluff, it loses force. The discipline is to model it as a genuine option, not to threaten it.
SAP has not removed the on premise edition of S/4HANA. Buyers who want to keep architecture control can still move to S/4HANA on their own infrastructure or on a hyperscaler of their choice.
The trade off is partial. They keep architecture control, they avoid the bundle commitment, but they take on the integration and operations work that RISE would otherwise wrap.
For estates with strong internal SAP capability or with regulatory constraints on managed services, this is often the cleanest answer. It rarely makes the SAP shortlist of recommendations.
The standard pitch is that RISE with SAP saves money through modernization and a single bundled subscription, so the move should happen as early as the program can absorb it. We disagree that the headline saving is the real number. In roughly 35 to 45 RISE proposals we have modeled, the realized TCO depends heavily on what the bundle excludes and on how the ECC runway is priced to make the migration look inevitable, and the saving narrows or flips once the excluded lines are restored. The buyer side move is to model the full term cost of RISE against the full term cost of a disciplined stay path, then negotiate from the cheaper baseline rather than from SAP's framing.
RISE concentrates the SAP relationship into a single bundled contract on a hyperscaler chosen with SAP. That concentration is the source of the convenience and the source of the lock in.
Both are real. The lock in is not absolute. It is shaped by clauses that decide whether the buyer can shrink, swap, or exit the contract on terms it can live with.
Negotiated well, the bundle is competitive. Negotiated as written, it is captive. The difference sits in five or six lines of contract language, not in the headline price.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Four clauses do most of the work. They are unglamorous and decisive, and SAP will resist each in turn.
Buyers who hold the line on all four protect the renewal far more than they protect the first term price. A small concession on the headline rate in exchange for a stronger clause set is almost always the right trade.
Lock in is also technical, not just contractual. The integration decisions made in the first 18 months on RISE decide whether the renewal is competitive or captive.
A buyer who builds heavily inside the SAP managed boundary has fewer renewal options three years later.
Treat integration architecture as a renewal lever. Keep the boundary clear between SAP managed components and buyer owned ones, and the renewal stays competitive even when the contract is large.
SAP describes portability in technical terms. The portability that matters for negotiation is the clause that gives you the data, the configurations, and a defined transition window if you decide to leave.
Without that clause, the technical portability of the platform is academic. With it, the renewal conversation tilts back toward the buyer.
Negotiate the portability clause early. It is the slowest clause to draft and the easiest one to leave to the last round, which is exactly where it usually gets cut.
RISE runs on AWS, Azure, or Google Cloud. The choice of hyperscaler is more than a deployment decision, it is a strategic one that affects the rest of the cloud estate.
A buyer with deep Azure investment may rationally pick a different RISE region than one with an AWS first stance. SAP will accommodate the choice, but it will not lead with it.
Bring the hyperscaler decision into the conversation early, with the cloud architecture team in the room. Late changes to the hyperscaler choice are expensive and slow.
The pitch is savings. The reality is a full term TCO that depends on what the bundle excludes. Model both paths first, then negotiate.
The bundle is the same. The estate behind it is not. The buyers who see the biggest swing in realized TCO are the ones whose estate sits at the extremes.
Either very lean and standard, where RISE delivers close to the pitched outcome, or very large and bespoke, where the excluded scope swamps the saving.
Smaller estates running close to vanilla SAP often see RISE deliver close to the pitched outcome. The integration burden is light, the partner spend is modest, and the bundled operations replace an in house team that was struggling to keep up.
This is the case that the SAP pitch was built for. It is also the case that least needs a hard negotiation, because the headline number is close to the truth.
The discipline for these buyers is to verify the fit honestly, then sign on terms that protect the renewal rather than fight the first term price.
The mid market is where the swing widens. A typical mid size estate carries enough custom code, integration, and Industry Engine attach to fill the excluded scope.
The pitched saving narrows materially across the term. Mid market buyers benefit most from the disciplined comparison, because the cost of doing it is small against the size of the contract.
Most mid market estates also have a real choice between RISE, S/4HANA on premise, and a planned stay. The leverage is in the choice itself, not in the negotiation that follows.
Highly customized estates, especially in regulated industries, are the buyers most likely to see a pitched saving flip into a premium. The custom code, the bespoke integrations, and the regulatory overhead almost always sit outside the bundle.
For these buyers, RISE can still be the right answer, but only after a hard look at the excluded lines, the sovereignty design, and the partner statement of work.
The proposal is the start of the conversation, not the end. The buyers who get the best outcomes are the ones who treat the first proposal as the opening of a six to nine month negotiation.
Industry shape matters as much as size. Manufacturing estates with heavy Industry Engine attach see the largest swing in the bundle base after a clean review.
Public sector estates carry sovereignty and procurement constraints that often shift the answer toward S/4HANA on premise. Financial services estates need the data processing and audit clauses drafted with unusual care.
Each sector has a typical pattern, and recognizing it early shortens the negotiation. The SAP account team knows the patterns too, which is why the buyer who reads them first sets the agenda.
The conversation has a shape, and the buyers who follow it pay less. The shape is not aggressive. It is disciplined, sequenced, and patient.
Two or three months of preparation before the first SAP meeting is the highest leverage time a procurement team can spend on this decision.
The first move is internal. Build a clean entitlement baseline, cleanse FUE, map Industry Engines to real use, and identify shelfware. Do this before SAP enters the room.
This step alone often trims 10 to 20 percent off the bundle base. It also reframes the conversation from a sales motion to a fact based negotiation.
A buyer who walks in with the cleansed baseline already on the table has changed the negotiating position before anyone has talked about price.
The second move is analytical. Build the full term RISE model and the full term stay model in parallel, on the same period, on the same scope, with the same partner assumptions.
The two models will not agree, and that is the point. The gap between them is the negotiating space.
The buyer side number to anchor against is the cheaper of the two, not the pitched RISE saving. Refresh the models with each round of negotiation, and the position stays current even as the proposal evolves.
SAP will lead with a worst case stay model. Counter it with a disciplined one. That is not adversarial, it is the buyer side equivalent of the seller side comparable.
Buyers who do this consistently move the conversation onto comparable terms in the first two meetings. Buyers who do not spend the rest of the process negotiating from the SAP framing.
The most important slide in a buyer side counter is the like for like stay model. Without it, the conversation never leaves the SAP comparable.
Timing matters. SAP, like most enterprise vendors, prices to its fiscal calendar, with quarter end and year end being the windows where discounting opens up.
A renewal that lands in a slow quarter usually settles for more than one that lands at year end. Plan the conversation to surface the signature decision at the moment SAP needs it most.
This is a small lever individually and a large lever in aggregate, especially across a multi year program with several sign offs.
The right buyer side team is small and senior. Procurement leads, finance models, the SAP architect owns the technical truth, and a buyer side advisor holds the comparable.
Large negotiating teams dilute focus and slow decisions. SAP is patient enough to outwait a team that cannot align. The smaller, faster team usually settles for less.
Decide who is in the room and who is informed before the first meeting. Stick to the structure. Change it only when the negotiation has stalled, never to add another voice.
RISE pricing depends on FUE count, Industry Engine attach, the cloud region, and the term length, with a meaningful add for excluded scope like integration and partner spend.
In our engagement file the realized RISE price typically lands at 40 to 60 percent of the SAP opening ask once a clean baseline and a credible stay path are in the room.
Sometimes, in specific shapes. Smaller estates on aged infrastructure and buyers who want a bundled operations contract often see a defensible saving.
Larger and more customized estates frequently see the pitched saving narrow or flip into a premium once the excluded lines are priced in. The honest answer comes from your own full term model.
Inside the bundle: the S/4HANA Cloud private edition entitlements, the hyperscaler hosting, basic operations, and standard support.
Outside the bundle: custom code remediation, bespoke integration, archive and decommissioning, dedicated networking, functional managed services, and most partner program work.
Standard support for SAP Business Suite 7, which includes ECC, steps down after 2027. Extended maintenance is available through 2030 at a published uplift near 2 percentage points above the standard rate.
Past 2030 the runway is a commercial conversation rather than a published policy, so buyers who want a calm move plan inside the 2027 to 2030 window.
It is a paid extension of SAP standard support that keeps ECC on supported maintenance through the end of 2030 in exchange for an annual uplift on the support fee.
The uplift sits near 2 percentage points above standard support and is intended to bridge buyers who cannot complete a move by 2027. Use the window to set the timing of the move, not to defer planning it.
RISE concentrates the SAP relationship into a single bundled contract on a hyperscaler chosen with SAP, and it shapes the integration architecture for the term.
The lock in is bounded by four contractual clauses: a capped uplift on renewal, swap and reallocation rights, exit and portability terms, and a benchmarking reference. Negotiated together, the bundle is competitive.
The decision is not binary, and the right answer depends on estate size, customization depth, regulatory posture, and program appetite.
Model three options: a move to RISE, a move to S/4HANA on premise or BYOC, and a planned stay into the extended maintenance window. Negotiate from the cheapest defensible baseline.
Start with a cleansed SAP entitlement baseline, then restore the excluded scope to the RISE quote line by line. Integration, custom code remediation, partner spend, archive, data egress are usually missing from the proposal.
Build a parallel full term stay model on the same period and the same scope, then compare. The right comparable is the same scope, not a worst case estimate.
Indirect access does not disappear with a move to RISE. The contractual model changes, but the underlying digital document and consumption rules persist.
The integration surface tends to widen on a modern platform. Settle the indirect access design inside the RISE contract rather than leaving it to a future true up conversation.
Most RISE programs need a system integrator for the technical move, a functional partner for application work, and often a buyer side advisor for the commercial and contractual layer.
Partner fees are the swing line in most full term TCO models, so fix the deliverables, the day rate, and the acceptance criteria before signature rather than treating them as a residual.
The full term RISE versus stay model, the excluded scope checklist, the FUE and Industry Engine cleanse pattern, and the renewal clause set that bounds the lock in. Used across more than five hundred enterprise engagements.
Independent. Buyer side. Built for SAP procurement, finance, and program leaders sizing the next renewal cycle.
The SAP account team models the worst case stay. Buyers who model both honestly stop comparing the move to a number nobody planned to live with.
