SAP sells RISE on a TCO story. The model that survives buyer side scrutiny usually tells a different one. Here is the five year math and the terms that decide it.
RISE with SAP rarely beats a well run on premises estate on raw five year TCO; it wins, when it wins, on exit from hosting contracts, upgrade debt, and capital cycles, and the contract terms decide which story you get.
RISE with SAP bundles the S/4HANA license, hyperscaler infrastructure, technical managed services, and standard support into one subscription priced per Full User Equivalent. The official scope is published on the SAP RISE product page, and what it excludes matters more than what it includes.
Application management, functional support, integrations, testing, and most migration work stay with the customer or a partner. The subscription replaces the license and hosting lines, not the SAP operating cost.
Full User Equivalents convert named user categories into one metric: one advanced user equals one FUE, while core and self service users convert at published ratios. The conversion table you sign, not the headcount, sets the bill.
On a like for like five year model, an already licensed on premises estate carrying only maintenance and infrastructure usually beats RISE subscription pricing. The RISE case improves when a hardware refresh, a hosting exit, or a major upgrade lands inside the window.
Five year TCO components, RISE vs on premises
| Component | On premises | RISE with SAP |
|---|---|---|
| License | Sunk, paid maintenance ~22 percent | Inside subscription per FUE |
| Infrastructure | Own or hosted contracts | Inside subscription |
| Technical ops | Internal or outsourced | Inside subscription |
| Application management | Customer cost | Customer cost, unchanged |
| Upgrade and migration | Periodic project capex | Conversion project at entry |
| Exit position | Keep perpetual licenses | Repurchase or stay subscribed |
RISE wins when the counterfactual includes a funded hardware refresh, an expiring hosting deal at above market rates, or an S/4HANA migration the business has already committed to. Without one of those, the subscription premium buys convenience, not savings.
Integration rework, regression testing, retained basis skills, and parallel run periods. In our 2024 to 2025 file these added 20 to 35 percent to the customer side of the model once counted.
Four terms separate a defensible RISE deal from an expensive one: the renewal cap, the FUE conversion table, the exit and data egress language, and the credit treatment of existing licenses. SAP publishes its general terms through the SAP agreements library, but the order form is where these four live.
Perpetual licenses survive a failed strategy; subscriptions do not. Whatever the five year model says, the year six position, renew under a cap, renegotiate, or repurchase, is where RISE economics are actually decided.
Treat RISE as a conversion negotiation, not a product purchase. SAP's cloud revenue targets make signed conversions valuable, and that value is your discount budget.
Yes for most estates. Mainstream maintenance for S/4HANA on premises runs into the next decade, and ECC deadlines have repeatedly proven negotiable. The burning platform is a sales narrative; your timeline should come from your own roadmap.
The standard analyst framing treats RISE versus on premises as an infrastructure TCO question. We disagree. In roughly 25 to 35 RISE evaluations Fredrik Filipsson advised in 2024 to 2025, infrastructure was never the deciding cost; the contract terms were. An uncapped renewal clause moved more money than any hosting efficiency, and a weak exit clause converted a five year decision into a permanent one. The buyer side move is to negotiate RISE as a terms problem, with the TCO model as the walk away evidence, not as a spreadsheet contest SAP's proposal team is trained to win. The cheapest RISE deal is the one with the strongest year six position.
Three cuts of our advisory engagement file frame the size of the opportunity.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Five moves turn this analysis into a lower invoice on the next renewal.
Usually not on raw five year TCO. In roughly 7 of 10 models we built in 2024 to 2025, an already licensed, stable on premises estate was cheaper. RISE wins when a hardware refresh, hosting exit, or committed S/4HANA migration sits inside the window.
Application management, functional support, integration builds, testing, and most migration effort stay with the customer. These omitted costs added 20 to 35 percent to the customer side in our engagement file.
Their value converts into a subscription credit or discount. Negotiate that credit as a durable percentage, because perpetual rights generally terminate at conversion and the credit is what survives.
Uncapped renewals. RISE contracts without renewal caps took 15 to 30 percent uplifts at year four in our file. The renewal cap and the exit terms decide the real cost more than the entry price.
No. Indirect use is repriced into the RISE bundle rather than eliminated. Settle your digital access position before conversion so it cannot be used as negotiation pressure.
Against SAP's quarter end, with a credible stay on premises model on the table. SAP's cloud conversion targets make signed RISE deals valuable, and that urgency is the buyer's discount budget.
The five year TCO model, the FUE conversion math, and the four order form terms that decide RISE economics.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The five year spreadsheet is the opening argument. The year six clause set is the verdict.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Pricing moves, audit signals, and the levers that work. No vendor spin.