You are registered. Your playbook is ready. Read the full 2026 edition of the SAP RISE Negotiation Playbook below.
Prepared by Atonement Licensing · buyer-side advisory · last reviewed June 2026. Figures are list-level or clearly labelled indicative ranges. The 5,000-user estate used below is a representative benchmark scenario for illustration, not a quote.
Executive summary
A SAP RISE quote is a configuration, not a fixed price, and SAP assembles it from the metrics SAP controls. The account team knows your installed base, your conversion options, your maintenance stream, and your fiscal-year pressure, so the first proposal is built to protect margin and leave room to concede. The buyers who change the number SAP calls final are the ones who arrive holding their own view of the user mapping, the document volume, and the alternative to signing.
On a representative 5,000-user estate converting from ECC to RISE private edition, an opening proposal that maps users heavily into Advanced Use models near $7.6M per year. The same headcount, mapped from real transaction usage and paired with a trimmed scope and a capped renewal, models near $5.0M per year — a Year 1 difference of roughly $2.6M on the same people. The gap is typically 15 to 30 percent of contract value, and it lives in the Full Use Equivalent mapping, the digital access scope, and the renewal terms, not in the headline discount.
This playbook explains how SAP builds a RISE quote, how the edition choice sets the ceiling on cost, the nine contract terms to settle in sequence, the FUE counting that drives the largest single line, the migration credit, indirect and digital access, the renewal caps that hold the later years, and the 180-day preparation timeline that puts the buyer back in possession of the facts. Read it before SAP tables a number, not after.
How SAP builds a RISE quote
RISE with SAP S/4HANA Cloud is sold as a bundled subscription. It packages the S/4HANA application, the underlying infrastructure, technical managed services, and a set of foundation tools into one private or public cloud edition. The commercial anchor is the Full Use Equivalent count, the consolidated user metric that replaced the old named-user price list.
SAP maps your users into categories, applies a conversion ratio to each, and sums the result into an FUE total. A small population of heavy users can cost more than a large population of light ones, because the ratio for Advanced Use is far higher than the ratio for Self-Service Use. The base subscription, the FUE tier, and any line-of-business cloud add-ons together set the number you see.
The account team works to SAP's fiscal year ending December 31, with quarter ends that shape discounting. It carries a quota, a strong incentive to move you off on-premise maintenance into the subscription, and authority to discount far more than the first quote suggests. Treat the opening number as the start of a configuration exercise, not a price.
The first FUE mapping SAP proposes is rarely the cheapest correct one. Sellers are measured on subscription conversion and cloud growth, so the default classification leans toward Advanced Use and toward add-ons you may not deploy. Ask for the quote decomposed by category, ratio, and add-on line, then price your own mapping against it before you respond.
Action. Recompute the FUE count yourself before you respond to a quote. The category mapping, not your headcount, drives the price.
2Choosing the edition: private, public, and GROW
RISE is not one product. The private edition runs a dedicated S/4HANA Cloud instance that supports custom code and a managed conversion of your existing system. The public edition runs a standardized, multi-tenant S/4HANA Cloud with a fixed release cadence and limited customization. GROW with SAP is the packaged route into the public edition aimed at new and mid-market adopters.
The choice changes both the price and the terms. Private edition costs more and gives you control over custom code, the upgrade timeline, and a closer match to an existing ECC footprint. Public edition costs less per FUE but constrains how far you can tailor processes and forces you onto SAP's release schedule. The wrong edition is an expensive mistake to reverse after signature.
Decide the edition on process fit and customization need, not on the headline subscription price alone. A public edition that forces costly process redesign can exceed the total cost of a private edition that fits your operation. Our comparison of RISE versus GROW versus HEC sets out the trade-offs by scenario, and the premium tiers are covered in the RISE Premium Plus pricing guide.
Action. Classify the workload's customization and process-fit need first, then let the edition decision set the cost ceiling you negotiate within.
3The nine RISE terms to fix first
Discount is one term of nine. Buyers who negotiate only the headline percentage leave the structure on the table. Fix these in sequence, starting with the ones that protect you across the full term and cost SAP the least to grant.
| Term | What it does | When it matters most |
|---|---|---|
| 1. FUE category mapping | Sets which users count as Advanced, Core, or Self-Service | Always; this is the largest single cost driver |
| 2. Renewal uplift cap | Fixes the maximum price increase at renewal | Always; uncapped uplift is the quiet cost |
| 3. Migration credit terms | Defines value, conditions, and the window to use it | When converting existing on-premise licenses |
| 4. Digital access scope | Sets how indirect document use is counted and priced | When third-party systems touch SAP |
| 5. FUE true-up rules | Caps mid-term increases and defines measurement | When user growth during the term is likely |
| 6. Service levels and credits | Binds SAP to availability targets with real remedies | Always; the managed service is part of the price |
| 7. Data and exit rights | Guarantees return of your data and an exit path | When lock-in risk needs a defined off-ramp |
| 8. Scope and add-ons | Removes line-of-business clouds you will not use | Before signing, checked against the roadmap |
| 9. Discount | The headline percentage, last | After every structural term is set |
The order matters. If you spend your position on discount first, you have nothing left to trade for the uplift cap or the digital access scope, which are worth more over a five-year subscription than a few extra points off list.
Action. Settle terms one through eight before the discount conversation opens. The percentage is the last lever, not the first.
Facing a RISE decision or renewal in the next two quarters? Our advisors run this playbook with you.
SAP Licensing ExpertsFUE counting and the categories that inflate it
The Full Use Equivalent model converts named users into a single number. SAP defines user categories with different consumption ratios, so the same person can cost very different amounts depending on the category assigned. Advanced Use, the heaviest category, carries the highest ratio. Core Use sits in the middle. Self-Service Use, for occasional and light activity, carries the lowest ratio.
The common error is over-classifying. Users who only approve a request, view a report, or enter a timesheet do not belong in Advanced Use. When the initial mapping pushes light users up a tier, the FUE total inflates and the subscription follows. The table below shows the same 5,000-user estate under an over-classified opening map and a usage-led map, using illustrative conversion ratios you should confirm against your own contract.
| User category | Indicative ratio | Opening map (users → FUE) | Usage-led map (users → FUE) |
|---|---|---|---|
| Advanced Use | 1 user = 1 FUE | 2,000 → 2,000 | 700 → 700 |
| Core Use | 5 users = 1 FUE | 2,000 → 400 | 2,300 → 460 |
| Self-Service Use | 30 users = 1 FUE | 1,000 → 33 | 2,000 → 67 |
| Total | ≈ 2,433 FUE | ≈ 1,227 FUE |
The FUE count is the largest line in the gap, but it is not the only one, so the blended subscription reduction is smaller than the raw FUE delta once the partly-fixed base subscription, infrastructure, and managed services are included. The bar below shows where the opening-to-counter gap comes from on the benchmark estate.
The drop between the opening and usage-led mapping on the 5,000-user benchmark estate, the single largest line in the gap (indicative).
Share of the opening FUE total that traces to light users mapped into Advanced Use, recoverable with an evidence-based remapping (indicative).
Build the mapping from real transaction data, agree the category definitions in writing, and document the basis so a later measurement cannot quietly re-tier your users upward. Refer to the SAP Software Use Rights for the current category definitions and confirm the ratios in your specific contract version, because they change between agreement generations.
Action. Rebuild the FUE mapping from activity, not org charts, and challenge every Advanced Use classification. It is the highest-return hour you will spend on the deal.
A RISE quote is a configuration SAP controls. The buyer's job is to arrive already holding the user mapping, the document volume, and a credible alternative.5
The migration credit and S/4HANA conversion
When you move from ECC or an existing S/4HANA on-premise contract into RISE, SAP can grant a conversion credit that offsets part of the subscription. The credit recognizes the value of licenses you already own. It is real money, and it is also a lever SAP uses to make the subscription look cheaper than continued ownership.
Three things decide whether the credit helps you. First, the value: confirm how SAP calculates it against your current contract, not a generic formula. Second, the window: credits expire, and a migration that slips past the deadline can lose the offset entirely. Third, the trade: accepting the credit usually means giving up perpetual rights and the option to run on-premise or with a hosted private edition later.
Model the full five-year cost of RISE with the credit against the cost of staying on-premise or moving to a hosted private option. The credit changes the early years, but the renewal uplift and FUE growth change the later ones. A clear total cost comparison keeps the credit from masking a worse long-term position. Our guide on SAP RISE versus on-premise total cost walks the model in detail.
Action. Quantify the credit inside a five-year total cost model that also prices the on-premise and hosted-private alternatives, then write its expiry into the agreement.
6Indirect and digital access
Indirect access is the use of SAP data or processes through a non-SAP system, and it remains one of the most expensive surprises in any SAP relationship. SAP moved most customers to the document-based digital access model, which counts the SAP documents that third-party systems create rather than the users behind them. Sales orders, invoices, purchase orders, and similar documents each carry a defined weighting.
Under RISE, digital access does not disappear. A connected commerce platform, a third-party logistics system, or an integration that creates SAP documents at scale can generate meaningful charges. The exposure is easy to miss because it sits outside the named-user conversation, and SAP may price it only after the subscription is signed.
Scope it early. Inventory every integration that creates or changes SAP documents, estimate annual document volume by type, and negotiate the digital access terms inside the RISE agreement rather than as a later true-up. Reference the current SAP digital access policy and confirm the document categories and weightings that apply to your contract. Our companion SAP Indirect Access Playbook and our SAP digital access guide cover the counting mechanics.
Reducing unnecessary document creation before measurement is a legitimate, often substantial, cost lever. The same business event can generate one document or several depending on how an integration is designed, so an integration review ahead of the count can lower the chargeable volume before any number reaches the contract.
Action. Inventory every integration that creates SAP documents and settle the digital access basis inside the RISE agreement, not as a post-signature true-up.
Unsure where indirect access exposure sits in your estate? Get an independent read before SAP prices it.
Book a 30 minute callRenewal caps, true-up rules, and exit
The subscription model moves the risk to renewal. Without a cap, SAP can raise the price when the term ends, and a multi-year platform is hard to walk away from on short notice. The default is uncapped uplift, so the cap has to be negotiated into the first agreement. On the benchmark estate, an uncapped renewal could carry an indicative annual uplift in the 7 to 12 percent range, compounding across a five-year term into a figure that dwarfs any opening discount.
Three protections matter. A renewal uplift cap fixes the maximum increase at the end of term. FUE true-up rules limit how mid-term user growth is measured and priced, and cap the increase you can face before renewal. Data and exit rights guarantee the return of your data in a usable form and define a path off the platform if the relationship ends. Without that off-ramp, every future renewal is negotiated from a weaker position.
| Protection | What it fixes | Default if omitted |
|---|---|---|
| Renewal uplift cap | Maximum percentage increase at end of term | Uncapped; priced at renewal from a weak position |
| FUE true-up rules | How and how much mid-term growth is charged | Open-ended measurement on SAP's terms |
| Data and exit rights | Usable return of data and a defined off-ramp | Lock-in that weakens every future renewal |
Action. Negotiate the uplift cap, the true-up rules, and the exit rights into the first agreement; they are far cheaper to obtain at signature than at the first renewal.
8Benchmarking, the walk-away, and the 180-day timeline
A discount percentage means nothing without a reference point. SAP frames the offer against its own list price, which is the number it controls. The buyer needs an independent benchmark: what comparable organizations of similar size and FUE profile actually pay, not what the price list says. Build it from your own effective rate today, market reference data for RISE deals at your scale, and the costed alternative of staying on-premise or moving to a hosted private option.
The walk-away is the discipline that makes the benchmark useful. Decide, before the final conversation, the terms and price at which RISE stops being the right answer. A credible alternative gives that walk-away weight, SAP knows whether you have one, and the conversation changes when you do. Position is built, not found: by the time SAP sends a proposal, the buyers who do well have already done the work, on the timeline below.
Baseline and model
Build an independent user, usage, and entitlement baseline, recompute the FUE count, and model the migration credit against the on-premise alternative.
Scope and benchmark
Map digital access exposure, trim the add-on scope to the roadmap, benchmark target pricing, and set a defensible walk-away.
Anchor and close
Open with your structure first, settle the nine terms in sequence, and close on a SAP quarter or fiscal year end.
| Days before decision | What to do | Why |
|---|---|---|
| 180 to 150 | Build an independent user, usage, and entitlement baseline | You cannot negotiate an FUE count you have not measured |
| 150 to 120 | Model the migration credit and the on-premise alternative | Know what RISE must beat to win the decision |
| 120 to 90 | Map indirect and document-based access exposure | Price digital access before SAP raises it |
| 90 to 60 | Benchmark target pricing and define your walk-away | Set the number before SAP sets it for you |
| 60 to 30 | Open the commercial conversation with your structure first | Anchor on your terms, not the proposal |
| 30 to 0 | Close at quarter or fiscal year end where possible | Timing pressure works in the buyer's favor |
Action. Start at day 180, set the benchmark and walk-away before SAP tables a number, and time the close to a SAP quarter or fiscal year end.
Rebuild the FUE mapping from real usage, trim the scope to the roadmap, settle the nine terms in sequence with discount last, and write the uplift cap, true-up rules, and exit rights into the first agreement. Treat the migration credit as one line in a five-year total cost model rather than a discount, scope digital access before signature, and hold a credible alternative in view throughout. The gap between SAP's first quote and a defensible deal lives in the mapping and the clause set, and that is where a prepared buyer recovers it.
Key takeaways
- A RISE quote is a configuration. Recompute the FUE count before you respond to any number.
- Pick the edition on process fit and customization need before negotiating price; it sets the cost ceiling.
- Fix the nine terms in sequence and negotiate discount last.
- Build the FUE mapping from real transaction data, not role names; over-classification is the largest single line in the gap.
- Model the migration credit inside a five-year total cost comparison, with its expiry in writing.
- Scope indirect and digital access before it becomes a post-signature true-up.
- Cap renewal uplift and the FUE true-up, and secure data and exit rights, in the first agreement.
Frequently asked questions
What is a Full Use Equivalent in SAP RISE?
The Full Use Equivalent, or FUE, is the consolidated user metric in RISE. Named users are mapped to categories such as Advanced Use, Core Use, and Self-Service Use, then converted to FUE using SAP ratios. The category mix, not raw headcount, drives the cost.
How does the SAP RISE migration credit work?
When you convert existing on-premise SAP licenses, SAP can grant a conversion credit against the RISE subscription. The credit carries conditions and a time window. Model its value and write the expiry and terms into the contract before you sign.
Is indirect access still a risk under SAP RISE?
Yes. RISE uses the document-based digital access model for indirect use. Third-party systems that create SAP documents can generate charges. Scope your document volume and define the digital access terms before signing.
Can I cap SAP RISE renewal increases?
Only if you negotiate it up front. Uncapped uplift is the default. Push for a fixed percentage cap on renewal pricing and on any mid-term FUE true-up, and tie both to the original contract.
Should we move to SAP RISE or stay on-premise?
Choose RISE when you want SAP to run the platform and you can commit to a multi-year volume. Stay on-premise or with a hosted private option when you need control of the stack or carry heavy customization. Model total cost both ways before deciding.
Get this playbook applied to your contract. Confidential assessment within one business day.
Book a 30 minute call