A SAP RISE quote is a configuration, not a fixed price. Buyers who fix the right nine terms before signing, who hold their own view of user categories and document volume, and who cap renewal up front routinely change the number SAP calls final. This playbook lays out how SAP builds a RISE quote, the nine contract terms to settle first, a 180-day preparation timeline, and the three places most money is lost: the FUE user count, the migration credit, and indirect access.
The reason RISE deals feel fixed is that SAP controls the metrics. Your account team knows your installed base, your conversion options, your maintenance stream, and your year-end pressure. You can close that gap. Everything below is about putting the buyer back in possession of the facts before the conversation starts.
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 tools into one private or public cloud edition. The commercial anchor is the Full Use Equivalent count, the consolidated user metric that replaces the old named-user price list.
SAP maps your users into categories, applies a conversion ratio to each, and sums the result into a 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. They carry 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. The first number protects margin and creates room to concede.
Private edition, public edition, 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.
The 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.
Facing a RISE decision or renewal in the next two quarters? Our advisors run this playbook with you.
SAP Licensing ExpertsFUE user 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 fix is a clean, evidence-based mapping built from actual transaction usage rather than role names or org charts.
| User category | Typical activity | Counting risk |
|---|---|---|
| Advanced Use | Full transactional work across modules | Light users wrongly mapped here drive the largest overcharge |
| Core Use | Defined operational tasks in specific areas | Borderline users may belong in Self-Service |
| Self-Service Use | Approvals, viewing, occasional entry | Often the largest group and the most under-claimed tier |
Build the mapping from real usage data, agree the category definitions in writing, and document the basis so a future measurement cannot quietly re-tier your users upward. Refer to SAP Software Use Rights for the current category definitions and confirm the ratios in your specific contract version.
The 180-day RISE preparation timeline
Position is built, not found. By the time SAP sends a RISE proposal, the buyers who do well have already done the work. This is the timeline we run.
| Days before decision | What to do | Why |
|---|---|---|
| 180 to 150 | Build an independent user, usage, and entitlement baseline | You cannot negotiate a 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 year end where possible | Timing pressure works in the buyer's favor |
What the subscription includes, and what it does not
The RISE subscription bundles the S/4HANA application, the cloud infrastructure, technical managed services such as patching and backups, and a set of foundation tools. That bundle is convenient, and it is also where scope creep hides. The price assumes a sizing of compute, memory, and storage, and that sizing is an assumption you can test.
SAP sizes the infrastructure from your projected system load. If the sizing is generous, you pay for capacity you never use. If it is tight, you face a mid-term increase when the system grows. Ask for the sizing basis in writing, compare it to your current production load, and agree how additional capacity is priced before you need it.
Several things sit outside the base bundle. Application managed services, the work of running your business processes rather than the platform, are usually separate. Line-of-business clouds such as Ariba, SuccessFactors, or Concur are priced on their own. Premium service tiers add cost. Map every component you actually need and confirm which sit inside the subscription and which are add-ons, so the quote you compare is complete.
Service levels deserve specific attention. A managed service without a meaningful availability commitment and real service credits is a promise without a remedy. Bind SAP to defined targets, define how downtime is measured, and make the credits material enough to matter. The managed service is part of what you are buying, so price it like one.
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.
Indirect 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 SAP digital access guide covers the counting mechanics.
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.
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.
Common RISE negotiation mistakes
The same errors recur across RISE deals, and each one is avoidable with preparation. Knowing them in advance is part of holding your position.
The first is accepting the FUE mapping as proposed. Buyers who treat the category assignment as a technical detail rather than the main price driver overpay from day one. Rebuild the mapping from real usage and challenge every Advanced Use classification.
The second is signing without a renewal cap. The subscription is easy to enter and hard to exit, so the renewal is where SAP recovers any early discount. An uncapped agreement hands that advantage away. Fix the cap before signature, not at the first renewal.
The third is ignoring indirect access until SAP raises it. Digital access exposure does not announce itself, and a quiet integration can create a large document volume. Scope it during the deal, when you still have room to negotiate the terms.
The fourth is comparing an incomplete quote. When add-ons, application managed services, and premium tiers are left out of the RISE number but sit inside your real requirement, the comparison to on-premise or a hosted option is wrong. Build a complete, like-for-like total cost before you decide. Our guide to SAP renewal mistakes covers the patterns that cost the most.
The fifth is negotiating alone against a team that does this every day. SAP's account and deal-desk staff run hundreds of these conversations a year. An independent advisor who has sat on the other side levels that gap. Our ranking of the top SAP negotiation consultants sets out the options.
Benchmarking the price and setting a walk-away
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 the benchmark from three inputs. The first is your own history, the effective rate you pay today across maintenance and any existing cloud lines. The second is market reference data for RISE deals at your scale, which an independent advisor can supply from recent engagements. The third is the cost of the alternative, whether that is staying on-premise, moving to a hosted private option, or delaying the move. Together these define a realistic target and a floor.
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. Even when RISE is the right destination, the option to wait or to choose a different path is what holds the price.
Timing reinforces the benchmark. SAP's quarter and year ends create internal pressure to close, and a buyer who is prepared to sign on the right terms at the right moment captures the best of that pressure. A buyer who is still measuring users in the final week captures none of it. Our RISE versus on-premise total cost guide gives the model behind a defensible walk-away.
Key takeaways
- A RISE quote is a configuration. Recompute the FUE count before you respond.
- Fix the nine terms in sequence and negotiate discount last.
- Build the FUE mapping from real transaction data, not role names.
- Model the migration credit inside a five-year total cost comparison.
- Scope indirect and digital access before it becomes a true-up.
- Cap renewal uplift and FUE true-up in the first agreement.
- Secure data return and exit rights so future renewals stay competitive.
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 callRelated reading: the SAP RISE negotiation guide, RISE versus GROW versus HEC, the SAP FUE counting guide, and the S/4HANA negotiation guide. See also our ranking of the top software negotiation consulting firms and the SAP vendor intelligence profile.