SAP / RISE
RISE with SAP. The buyer deep dive.
RISE with SAP folds S/4HANA private cloud, infrastructure, and tooling into one subscription on the FUE metric. Read the deep dive before the next RISE proposal lands on your desk.
RISE with SAP folds S/4HANA private cloud, infrastructure, and tooling into one subscription on the FUE metric. Read the deep dive before the next RISE proposal lands on your desk.
RISE with SAP bundles S/4HANA Cloud private edition, hyperscaler infrastructure, and SAP BTP credits into one subscription priced on the Full User Equivalent metric. This deep dive covers what is inside, how it is sized, and where the buyer side leverage sits.
RISE with SAP launched in January 2021 as SAP's packaged route to S/4HANA in the cloud. SAP markets it as business transformation as a service. In commercial terms it is a bundle.
The bundle folds software, infrastructure, and a set of transformation tools into one subscription with one order form and one throat to choke. That convenience is real. It also reduces your visibility into what each component costs.
RISE is not a single product. It is a contract that aggregates several SAP and partner components under one subscription line.
The anchor is S/4HANA Cloud private edition, the single tenant managed version of S/4HANA. You get the ERP, the HANA database runtime, and the managed service wrapper.
SAP runs the system on a hyperscaler you nominate, typically AWS, Microsoft Azure, or Google Cloud. SAP holds the infrastructure contract. You do not pay the hyperscaler directly under the standard model.
The bundle adds SAP BTP credits, SAP Business Network starter packs, and transformation tooling such as the SAP Signavio process tools and the readiness check suite. Credit volumes vary by deal size.
RISE is priced on the Full User Equivalent. The FUE blends your different user types into one weighted number.
Each SAP user category carries a conversion ratio. Heavy professional users count as one FUE each. Lighter categories convert at a fraction, so several light users equal one FUE.
SAP groups users into bands such as Advanced Use, Core Use, and Self Service Use. The band you assign each user to changes the FUE total directly.
The table below shows how a mixed user base converts. The ratios are illustrative and vary by contract, so treat them as a model, not a price list.
Illustrative FUE conversion across a mixed user base
| User category | Named users | Conversion ratio | FUE contribution |
|---|---|---|---|
| Advanced Use | 200 | 1 to 1 | 200 |
| Core Use | 600 | 5 to 1 | 120 |
| Self Service Use | 3,000 | 30 to 1 | 100 |
| Developer | 40 | 1 to 1 | 40 |
| Blended total | 3,840 | weighted | 460 |
The leverage point is obvious once the math is visible. Move users into the correct lighter band and the FUE total falls without removing a single person.
Sizing is the single largest swing factor in a RISE deal. Get it wrong and you pay for capacity and users you never use.
Build your own FUE model from real usage data first. Pull transaction frequency and role data for the trailing twelve months. Assign each user to the lowest defensible band.
SAP sizing tools tend to recommend headroom. Size to your real steady state load with a documented burst plan, rather than carrying permanent peak capacity.
BTP credits look free in the bundle. They are funded inside your subscription. Forecast real consumption and trade unused credit volume for a lower base price.
The standard SAP account team pitch is that RISE simplifies everything, so you should accept the proposed FUE count and infrastructure sizing to avoid risk. We disagree. In roughly 8 of 10 RISE estates we have modeled, the proposed FUE count sat 18 to 30 percent above the defensible number once we remapped users to real usage. The buyer side move is to build your own FUE model from trailing usage data before the first sizing workshop, then negotiate against that anchor. SAP sizes for its revenue, not your run rate, and the convenience of the bundle is not a reason to skip the remap.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
RISE is sold as simplicity. The simplicity is real on day one and expensive by year three if you signed the first FUE count without a remap.
SAP offers migration credits to ease the move from ECC to RISE. The credits offset part of the bridge cost while both systems run in parallel.
Credits typically discount the RISE subscription for a defined window while you complete the move. They are time boxed and expire on a schedule.
SAP maps your existing ECC named user and engine licenses into the FUE model. The software use rights that apply differ from your old contract, so read the conversion clause closely.
Mainstream maintenance for SAP Business Suite 7 runs to 2027, with extended maintenance to 2030. That deadline is the lever SAP uses to push RISE timelines. Treat it as a planning input, not a reason to rush a weak deal.
Indirect and digital access sit outside the FUE count. They are licensed separately by document volume.
SAP digital access charges for documents created in S/4HANA by third party systems. Sales orders, invoices, and similar documents each count.
Run a document estimation before the RISE deal closes. Discovering exposure after signature removes your leverage and turns a negotiation into a compliance fee.
The headline discount fades. The contract terms decide what you pay at renewal and what happens if you leave.
Negotiate a fixed renewal uplift cap. Without it, SAP resets to list at renewal and the discount you fought for evaporates.
Define data export format, timing, and assistance in the contract. A managed service that holds your data without a clean exit clause is a lock in.
Cap how often and how aggressively SAP can true up the FUE count. Annual measurement with a defined process beats an open ended audit right.
White Paper · SAP
SAP RISE vs On Premises TCO 2026
RISE with SAP rarely beats a tuned on premises estate on raw TCO; it wins on exit from hosting and upgrade debt. Read it free.
RISE with SAP is a single subscription that bundles S/4HANA Cloud private edition, hyperscaler infrastructure, and SAP tooling under one SAP contract priced on the Full User Equivalent metric. It is SAP's packaged route to S/4HANA in the cloud.
The bundle includes S/4HANA Cloud private edition, managed infrastructure on a hyperscaler you nominate, SAP BTP credits, a Business Network starter pack, and transformation tooling. SAP holds the infrastructure contract, so you do not pay the cloud provider directly.
RISE is priced on the Full User Equivalent, or FUE. The metric blends your different user types into one weighted number using conversion ratios, where heavy professional users count as one FUE and lighter users convert at a fraction.
A Full User Equivalent is SAP's blended user metric for RISE. It converts named users in categories such as Advanced Use, Core Use, and Self Service Use into one number using per category ratios, so several light users can equal one FUE.
Yes. You nominate AWS, Microsoft Azure, or Google Cloud as the underlying infrastructure for RISE. The commercial relationship still sits with SAP under the standard model, and SAP manages the infrastructure contract on your behalf.
Migration credits discount the RISE subscription for a defined window while you move from ECC and run both systems in parallel. They are time boxed and expire on a schedule, so the year three run rate is higher than the credited year one cost.
No. Indirect and digital access sit outside the FUE count and are licensed separately by document volume. SAP digital access charges for documents created in S/4HANA by third party systems, so estimate that exposure before signing.
Cap the renewal uplift, define a clean data exit, and limit the FUE true up process. These terms decide what you pay at renewal and what happens if you leave, and they often matter more than the headline first year discount.
Mainstream maintenance for SAP Business Suite 7 runs to 2027, with extended maintenance available to 2030 at a higher fee. SAP uses that deadline to push RISE timelines, so treat it as a planning input rather than a reason to rush.
No. SAP's first FUE proposal typically runs 18 to 30 percent above the defensible count once users are remapped to real usage. Build your own FUE model from trailing usage data first, then negotiate against that anchor.
SAP RISE pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
RISE bundles software, infrastructure, and tooling into one number. Your job is to make sure that number is built on your usage data, not SAP's revenue target.
