RISE with SAP is SAP’s integrated cloud-subscription package combining infrastructure, S/4HANA software, application management services, BTP credits, and a defined service-level agreement, sold as a single subscription priced in Full Use Equivalent (FUE) units. The model is presented as simple. Beneath the simplicity sit four pricing levers that materially affect total cost of ownership and that most buyer-side teams under-negotiate at the contract event. This article walks through the headline pricing structure, the four levers in detail, and the buyer-side preparation that converts an apparently fixed price into a negotiable structure. It is one of the engagement patterns underneath our contract negotiation service.
The headline structure
RISE pricing is structured around three principal components. The FUE subscription, which is the licence and software-rights component, priced per FUE per year. The infrastructure component, priced by T-shirt size (S, M, L, XL with sub-grades), which determines compute, storage, and HANA capacity. And the service component, which covers application management, basis services, and the SLA-backed operations. The three are bundled into a single price expressed per FUE per year, with the T-shirt size and the service tier driving the per-FUE rate.
Behind the bundled price the components are computed separately. Buyer-side teams that treat the bundle as a single price under-negotiate. Teams that disaggregate the components into the underlying drivers identify the four levers that move the total. The RISE topic page covers the architectural detail.
Lever one — the FUE quantity
The FUE quantity is the first and largest lever. The contracted FUE quantity is derived from a conversion of the buyer’s pre-RISE named-user position into FUE units, applying the contract’s ratio table. The conversion ratios vary across contract generations and across negotiation rounds. The same pre-RISE user position can yield meaningfully different FUE quantities depending on the ratios applied.
The buyer-side preparation here is twofold. First, the pre-RISE classification rebuild that reduces the named-user input to the conversion. Second, the negotiation of the ratio table itself, which is a commercial point and not a SAP-defined constant. Together, these two preparations can reduce the contracted FUE quantity by fifteen to twenty-five per cent against the as-is unprepared baseline. The cumulative value across a multi-year subscription is substantial. The licence optimisation pillar covers the classification rebuild methodology.
Lever two — the T-shirt size
The T-shirt size determines the infrastructure component. The sizes are defined by SAP and correspond to specific compute, storage, and HANA capacity ranges. The recurring buyer-side error is over-sizing: choosing a T-shirt size with headroom against the projected workload, paying the higher price across the contract life, and never reaching the headroom utilisation that would justify the sizing.
The mitigation is the sizing exercise applied to the actual workload profile before the contract event. The exercise reviews the historical compute, storage, and HANA consumption from the source environment (where the estate is converting from on-premise or from another cloud) and projects forward to the post-RISE environment. The projection should include the conversion-period transient peak and the steady-state run rate. The right T-shirt size is the smallest size that accommodates the steady-state run rate plus a defined growth allowance, with the conversion-period peak handled by short-term capacity arrangements rather than by a permanent T-shirt upgrade.
The sizing-review evidence
Workload data extracted from the existing environment is the strongest input to the sizing review. Where the conversion is from on-premise, the data is from the HANA system itself. Where the conversion is from another cloud, the data is from the cloud provider’s metering. In both cases the data is independently verifiable and supports the buyer-side sizing position against the SAP-recommended sizing.
Lever three — cloud-credit structure
The RISE contract typically includes a cloud-credit component covering BTP services. The credits are issued annually and are subject to use-it-or-lose-it rules unless negotiated otherwise. The recurring buyer-side error is treating the credit allocation as a free benefit rather than as a paid-for entitlement. The credits are paid for inside the bundled subscription price; unused credits are unused entitlement, not a cost-saving choice.
The mitigation is twofold. First, the credit allocation should match the buyer’s realistic BTP consumption forecast rather than a SAP-recommended allocation that the buyer cannot consume. Where the buyer has no immediate BTP requirement the credit allocation should be minimised. Second, the carry-forward rules should be negotiated. SAP’s standard position is annual use-or-lose; the negotiated outcome can include multi-year carry-forward, mid-term reallocation, or conversion to other entitlement at defined ratios. The RISE contracts pillar covers the credit-structure mechanics.
Lever four — the exit terms
The exit terms are the fourth lever and the most under-negotiated. RISE contracts include termination provisions, data-extraction provisions, and end-of-term transition provisions. The recurring buyer-side error is treating the exit terms as theoretical, signing the SAP standard, and discovering at contract end that the standard provisions favour SAP’s position materially.
Specific exit provisions to negotiate include: the data-extraction format and timing requirements; the post-termination access window for data retrieval; the transition assistance scope; the obligations of SAP under a buyer-initiated termination; and the residual rights after the subscription ends. Each provision is consequential at end of term, and the negotiation leverage exists only at contract sign. The RISE contract checklist sets out the full provision list.
The headline RISE price is what SAP wants the negotiation to focus on. The four levers are where the actual cost is set. A buyer-side team that disaggregates the bundle and negotiates the levers individually typically achieves between twelve and twenty per cent better economics than a team that negotiates the headline price.
The T-shirt trap in practice
Across our RISE engagements, the T-shirt sizing decision recurs as the single largest source of overspend. Estates choose Large where Medium would have been adequate. The reasoning is usually conservative: build in headroom against future growth, avoid the disruption of a mid-term resize, simplify the procurement decision. The result is a five-year overspend equal to the price differential between sizes, which can be eight to fifteen per cent of the bundled subscription value.
The mitigation is the sizing review applied at the contract event, with explicit contractual provisions for mid-term resize if the projection proves wrong. Most RISE contracts permit mid-term upsize; few permit mid-term downsize. The buyer-side leverage at contract sign includes the negotiation of bilateral resize provisions, which transform the T-shirt selection from an irreversible decision into a managed one. The retailer RISE case file documents the pattern.
How hyperscaler choice fits in
RISE includes a hyperscaler infrastructure layer (AWS, Azure, GCP, or Alibaba). The hyperscaler choice affects the underlying infrastructure cost, the latency profile, the geographic data residency, and the integration topology with the buyer’s other cloud estate. SAP’s standard position is to recommend a specific hyperscaler per region; the buyer-side position can include hyperscaler choice as a negotiation point.
The economic implication of hyperscaler choice varies by region. In some regions the hyperscaler cost differential is material; in others it is small. The non-cost factors — data residency, integration topology, the buyer’s existing cloud strategy — can be the deciding ones. The decision should be made on a full assessment rather than on the SAP-recommended default, and the contract should include the chosen hyperscaler as a defined provision rather than as a SAP-discretionary selection.
The renewal trajectory
The RISE pricing structure compounds across renewals. The contract typically includes annual escalators (often three to five per cent CPI-linked) and renewal pricing that ratchets to a higher base after the initial term. The renewal negotiation is the second-largest commercial event in the RISE life cycle after the initial sign, and the buyer-side leverage at renewal depends on the credible alternative position the buyer can demonstrate. The alternative position includes the threat of migration to another cloud, the threat of unwinding the RISE bundle into separate components, or the threat of a competitor environment.
The preparation for renewal begins eighteen to twenty-four months before the renewal date. The components are the same as for the initial contract: classification refresh, sizing review, credit-allocation review, exit-provision review. Estates that prepare systematically achieve renewal pricing materially below SAP’s initial proposal. Estates that arrive at renewal without preparation accept the SAP proposal and lock in the escalation.
— 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
Begin with the FUE conversion review and the T-shirt size selection. Both are early-stage decisions that compound across the contract life. The contract negotiation service brief covers the engagement frame; the retailer RISE case file shows the pattern in practice.