The most common framing of the RISE-versus-on-premise decision is a price comparison: the annual RISE subscription against the annual on-premise costs (maintenance, infrastructure, basis services). The framing is incomplete and typically favourable to the SAP business case. The correct framing is a structural TCO comparison across a defined horizon (five years is the standard frame), with the line items decomposed into the underlying drivers, and with the buyer-side inputs reviewed independently of the SAP-supplied business case. This article sets out the comparison frame, the principal line items, and the three inputs that most influence the answer. It is one of the engagement patterns underneath our contract negotiation service.
The line items
The RISE TCO comprises: the FUE subscription (the principal line); the BTP-credit cost; the implementation cost (services to migrate to RISE); the integration cost (rebuilding integrations to the new tenant); and the change-management cost (the operational transition). The recurring lines (subscription, BTP) are the bulk of the five-year cost; the one-time lines (implementation, integration, change) are concentrated in years one and two.
The on-premise TCO comprises: the maintenance fee on the existing licences (typically 22 per cent of net licence value annually); the infrastructure cost (compute, storage, data centre, networking); the basis-and-operations cost (internal team or outsourced); the hardware refresh cost (recurring every three to five years); and the upgrade cost (S/4HANA upgrades, hardware refreshes, periodic re-platforming). The on-premise TCO is dominated by the recurring lines, with the upgrade cost as a periodic spike. The RISE topic page sets out the structural detail.
The FUE subscription versus maintenance
The headline comparison is the FUE subscription versus the on-premise maintenance fee. The maintenance fee is calculated on the net licence value, which is the original purchase price net of negotiated discounts. The FUE subscription is calculated on the converted FUE quantity and the negotiated per-FUE rate.
For an estate carrying material historical discounts on the on-premise licences, the maintenance fee can be substantially lower than the FUE subscription would be. For an estate with limited historical discount or with a deeply over-classified user population, the relationship reverses. The buyer-side preparation that removes ten to twenty per cent from the converted FUE count (covered in the FUE conversion article) directly improves this comparison.
The infrastructure swing
The on-premise infrastructure line is a real cost that often does not appear in the on-premise budget as a discrete line. Compute, storage, data centre space, networking, backup, and disaster recovery: each is an enterprise cost typically allocated across all workloads. Carving out the SAP-specific portion is the buyer-side preparation; the on-premise comparison without the carve-out understates the on-premise cost.
The RISE infrastructure cost is embedded in the bundled subscription, with the T-shirt size determining the implicit infrastructure rate. The comparison is most accurate when the buyer-side carve-out is set against the implicit T-shirt cost. The RISE T-shirt sizing article covers the implicit-rate calculation.
The operations line
The on-premise operations line covers the basis team, the database administration, the OS-level operations, and the integration operations. The cost is either an internal team cost (with a defined headcount and burdened rate) or an outsourced cost (a managed-services contract). Either form is a recurring cost across the five-year frame, with annual escalation.
Under RISE the basis-and-operations function is performed by SAP and embedded in the subscription. The internal team is reduced (typically by 50 to 70 per cent of the on-premise team) but not eliminated, because the buyer retains responsibility for configuration management, release management, integration management, and the user-facing support functions. The TCO comparison should include the realistic post-RISE internal team rather than assume the internal team disappears entirely.
The three inputs that most move the TCO comparison are: the historical discount on the on-premise licences (which determines the on-premise maintenance line); the projected FUE quantity (which determines the RISE subscription line); and the realistic post-RISE internal team size (which determines the operational saving). All three are independently verifiable; the SAP-supplied business case typically uses optimistic assumptions on at least two.
The implementation cost
The RISE move requires implementation services: the conversion or re-implementation of the existing landscape onto the RISE tenant, the integration rebuild, the data migration, and the cutover. The cost is concentrated in years one and two of the five-year frame. The SAP-supplied business case typically presents the implementation cost as a one-time expense offset by the ongoing operational saving. The framing is correct in principle but the implementation cost is often understated.
A realistic implementation cost is twelve to twenty per cent of the five-year subscription value for a brownfield conversion, and twenty to thirty-five per cent for a greenfield re-implementation. The RISE conversion economics article covers the cost-structure detail. The buyer-side TCO should use a realistic implementation cost rather than the SAP-supplied figure.
The upgrade profile
The on-premise estate carries periodic upgrade costs: S/4HANA version upgrades on a multi-year cycle, hardware refreshes every three to five years, and operating-system or database-version upgrades on their own cadence. Each upgrade is a project with services, testing, downtime, and risk. The five-year TCO should include at least one full upgrade cycle.
Under RISE the upgrades are SAP-managed and the buyer-side cost is the testing-and-adoption effort rather than a full upgrade project. The reduction is one of the strongest economic arguments for RISE in estates with substantial customisation. The argument weakens in estates with light customisation, where the on-premise upgrades are themselves modest. The S/4HANA migration compliance pillar covers the broader upgrade frame.
The risk-adjusted view
The deterministic TCO comparison gives a point estimate. The risk-adjusted view recognises the variance around the point estimate. The on-premise scenario carries upgrade-risk variance, hardware-failure variance, and team-retention variance. The RISE scenario carries SAP-subscription-escalation variance, T-shirt-resize variance, and exit-risk variance. The two risk profiles are not the same.
The risk-adjusted view typically narrows the apparent advantage of whichever scenario the deterministic view favours. A 12 per cent deterministic advantage often becomes a 4 per cent risk-adjusted advantage. The implication is that close calls should be made on the qualitative factors (strategic fit, operational preference, vendor concentration) rather than on the small deterministic margin. The retailer RISE case file documents the risk-adjusted decision pattern in practice.
The three-input sensitivity
Across the engagements we have reviewed, three inputs explain the bulk of the variance in the TCO answer. First, the historical discount level on the on-premise contract: estates with deep historical discounts often retain a meaningful on-premise advantage. Second, the over-classification load in the named-user population: a population with twenty per cent over-classification produces a punishingly high FUE count if converted as-is. Third, the realistic post-RISE internal team size: an over-optimistic team reduction can flatter the RISE case by ten per cent of the on-premise operations line.
A buyer-side TCO that uses defensible figures for all three inputs typically arrives at a different answer than the SAP-supplied case. The arrival is the value of the buyer-side analysis. The RISE-versus-on-premise TCO white paper sets out the full input list.
Beyond year five
The five-year frame is the standard window but the decision is often longer-lived. Beyond year five the RISE escalators continue, the on-premise hardware-refresh cycles continue, and the comparison narrows or widens depending on how the inputs evolve. The buyer-side preparation should include a sensitivity view at years seven and ten, particularly for buyers whose five-year comparison is a close call.
The seven-and-ten-year view tends to reduce the RISE advantage relative to the year-five view (because the escalators compound) but to extend the operational advantages of the SAP-managed model. The decision becomes one of cost trajectory versus operational simplification, with the right answer turning on the buyer’s specific operating model rather than on a generic financial comparison.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
Where to start
Build the buyer-side TCO model before reviewing the SAP-supplied one. The model is the artifact that supports the route decision, not the SAP business case. The contract negotiation service brief sets out the engagement frame.