Contents
Key takeawaysWhat you can negotiateWhat we saw in 2024 and 2025The platform credit poolThe legacy maintenance bridgeA scored alternativeWhen to startDigital access and exit termsAccount team linesWhat to do nextFAQThree parts of a RISE deal move a long way: the credit pool, the legacy maintenance bridge and the discount. Each needs different preparation (a document, a schedule or a parallel evaluation), and a request for a better rate wins none of them.
- The order form is less fixed than it looks. SAP presents one standard subscription fee, yet the pricing underneath it is sized deal by deal.
- Credits follow evidence. A use case list with named owners roughly tripled the credit pool as a share of annual contract value in our deals.
- The bridge needs a schedule. Full legacy maintenance for five years is the default, and a step down cap tied to migration milestones removed most of that cost.
- Scored alternatives move the discount. A competitor mentioned in a meeting changed little, while a live parallel evaluation with its own decision date widened the discount.
- Timing decides all three. Each ask depends on work that takes months, so it has to start well before SAP drafts the order form.
- Two terms belong in the same window. Settle the digital access document count and the exit terms before signature, when they cost the least to obtain.
A RISE with SAP order form reads as a flat per user subscription, and the account team will present it as standard. Three parts of it change a great deal in negotiation: the platform credit pool, the legacy maintenance bridge and the discount. Each is won by different preparation.
This guide explains what each ask is, what it is worth in a worked example, and when the work has to start. If you are still deciding whether RISE fits at all, begin with is RISE right for you and come back once the answer is yes.
Which parts of a RISE with SAP contract can you negotiate?
The rate, the platform credit pool and the bundle composition all flex, even though the order form shows one subscription fee. Underneath that fee sit five separate lines, each responding to different pressure. Treat them as one number and you end up negotiating only the rate.
| Component | What it is | Whether it changes |
|---|---|---|
| Core subscription | The ERP priced on the blended user metric | Changes with the count more than the rate |
| Platform credit pool | A consumption balance for extensions and integration | Roughly triples on documented use cases |
| Infrastructure layer | Hyperscaler compute, storage and network inside the bundle | Rarely separable; ask for the split at signature |
| Managed services | Operations, upgrades and support | Scope is negotiable, price largely is not |
| Legacy maintenance bridge | Maintenance on the old system during the transition | Falls sharply with a step down schedule |
Why does the user count matter more than the rate?
The core subscription is priced in Full Use Equivalents (FUE), and the weighting of each user type decides how many you buy. SAP counts 1 advanced user as 1 FUE, 5 core users as 1 FUE and 30 self service users as 1 FUE, while each developer costs 2 FUE.
Say the sizing reclassifies 500 people from advanced to core use: that cuts 400 FUE before any discount is discussed. That is why we size the user mix from real transaction usage first and argue the rate second. The RISE deep dive covers how existing licenses convert into FUE.
What should you ask about infrastructure and managed services?
Ask SAP to show the infrastructure cost as its own line at signature, even if it stays bundled. You rarely get it priced separately, but a visible split tells you what you are paying the hyperscaler layer for and gives you a reference at renewal.
For managed services, work from the roles and responsibilities section of SAP's service description guide for the private edition. Each task SAP does not own there lands on your team or your systems integrator, so settle the task list before you discuss the fee.
RISE with SAP Negotiations: Pricing a One-Way Door
What have we seen in 30 to 40 RISE negotiations since 2024?
Across roughly 30 to 40 SAP RISE negotiations we ran in 2024 and 2025, the order form read as standard, and the same three terms decided the outcome. None of them was won by asking for a better rate.
- The credit pool. It opened at 3 to 5 percent of annual contract value and closed at 8 to 12 percent once the customer tied it to documented use cases with named owners. Across the deals, that is a range of 3 to 12 percent.
- The legacy bridge. The default was full legacy maintenance for five years. A step down cap tied to the measured migration run down cut that tail by 50 to 75 percent over the term.
- The discount. Where a credible alternative was scored in parallel, the discount widened by 8 to 15 points. Where a competitor was only mentioned, it moved little.
The lesson we draw from those deals is that these are three different kinds of request. The credit pool needs evidence, the bridge needs a structure and the alternative needs a separate workstream. A procurement conversation about percentages produces none of them.
RISE with SAP cost analysis
How RISE compares with S/4HANA on premises, with the offsets worth negotiating.
Get the white paper →How do you get a larger platform credit pool in a RISE deal?
Give SAP a documented list of the extensions, integrations and services you will build, each with an owner and a consumption estimate, before the order form is drafted. The credit pool is a balance of SAP BTP consumption credits (CPEA credits) sized against annual contract value, and that list is what SAP sizes it against.
Without that list, the pool is a goodwill item and SAP sizes it low. With it, the pool becomes a sizing exercise, and SAP has a reason to fund what you have shown you will build.
What goes into the use case list?
- Extensions. The custom code and side by side apps you plan to move off the ERP core, with the BTP services each one needs.
- Integrations. Every interface to banks, carriers, CRM, payroll and data platforms that will run through SAP Integration Suite.
- Automation and analytics. Workflow, process automation and reporting use cases that the program has already approved.
- Owner and timing. A named person for each item and the quarter in which consumption starts.
Unused CPEA credits expire at the end of each contract year. A larger pool you cannot consume in year one is worth less than it looks, so phase the credits to your go live dates. Our guide to BTP capacity units and cloud credits shows how consumption is metered.
What is a larger credit pool worth next to a rate discount?
On a large agreement, the larger pool is worth more than several points of rate discount. The hypothetical below uses the midpoints of the opening and closing ranges on a $4,000,000 annual contract value.
| Item | Per year | Over a five year term |
|---|---|---|
| Opening credit pool at 4 percent | $160,000 | $800,000 |
| Closing credit pool at 10 percent | $400,000 | $2,000,000 |
| Gain from the use case list | $240,000 | $1,200,000 |
| Three extra points of rate discount on the same $4,000,000, for comparison | $120,000 | $600,000 |
Buyers often accept the credit pool as a throw in and spend their energy on the rate. In this example the use case list is worth twice as much as three hard won discount points, provided the credits are consumed.
How do you cut the legacy maintenance bridge during a RISE migration?
Replace the flat default with a step down schedule. Left alone, the bridge charges full maintenance on your old SAP system for five years while you migrate off it. A step down cap ties that maintenance to migration milestones you have already committed to.
During a transition you pay for two systems: the platform you are building and the one you are leaving. The standard bridge prices the old system as if it will still be fully loaded in year five, when the program exists to retire it. A step down schedule makes the maintenance curve follow the decommissioning curve.
What does a step down schedule look like in numbers?
Say your legacy maintenance runs at $1,200,000 a year and your migration plan has four dated milestones. The schedule below cuts the bridge by 57 percent across the term.
| Year | Milestone reached | Flat default | Step down |
|---|---|---|---|
| Year 1 | Build and test | $1,200,000 | $1,200,000 (100 percent) |
| Year 2 | Finance live on the new system | $1,200,000 | $840,000 (70 percent) |
| Year 3 | Logistics and manufacturing live | $1,200,000 | $420,000 (35 percent) |
| Year 4 | Legacy system read only for archive | $1,200,000 | $120,000 (10 percent) |
| Year 5 | Legacy system decommissioned | $1,200,000 | $0 |
| Total | $6,000,000 | $2,580,000 |
The saving here is $3,420,000. The schedule only holds if the milestones are dated in the program plan before you ask, because SAP will attach each step to something you are already committed to deliver.
Why a discount on the bridge is the weaker request
The usual advice is to ask for a percentage off maintenance during the migration. We think that sells the bridge short. A 20 percent discount on a flat five year line still pays for a legacy system you may have switched off, so ask for the declining schedule, with a clause covering milestones that slip because of SAP.
Does a competing option really improve the RISE discount?
Yes, when it is scored. In our deals the discount widened only where a credible alternative ran as a live evaluation alongside the RISE talks. SAP's team can tell a competitor named in a meeting from a comparison with its own timeline, scoring and budget owner.
Measured against a $4,000,000 annual list price, each point is $40,000 a year. Across the range we saw, that is $320,000 to $600,000 a year, or $1,600,000 to $3,000,000 over five years.
What makes an alternative credible to SAP?
- Same rigor on both sides. The same requirements, the same total cost model and the same scoring sheet for RISE and the alternative.
- A realistic option. S/4HANA on premises under a perpetual license, a different hosting route, or staying on ECC with third party support while the program matures. Our RISE versus S/4HANA on premises comparison sets out the cost lines.
- A decision date. A steering committee date that SAP can see, which keeps the comparison from reading as a bluff.
The calendar helps the alternative. SAP Business Suite 7 mainstream maintenance ends in 2027 and extended maintenance in 2030, so staying on ECC for a few more years is a real option for many companies and SAP knows it.
Why do you have to start RISE negotiation work before the order form is drafted?
Because each of the three asks depends on something you have to produce, and each takes longer than a live negotiation lasts. By the time the order form arrives, the use case list is usually missing, the migration run down is undated and no alternative has been scored.
At that point all three asks collapse into the only thing a buyer can do on the spot, which is ask for a lower rate. SAP's team is comfortable there. That conversation is bounded, and it is the one they prepared for.
Why we advise against leading with the headline discount
Standard advice says push the rate first and treat the rest as detail. We disagree for RISE. On large agreements the credit pool swing alone is worth more than several points of rate, and the pool and bridge are hard to reopen once rate talks set the deal's shape. Build the three documents first, then open the rate.
A buyer who only asks for a better rate usually walks away with none of the three.
| Before signature | What to have done |
|---|---|
| 12 months | Run the user mix analysis and start the alternative evaluation with its own budget owner |
| 9 months | Date the migration milestones with the program team; begin the use case list |
| 6 months | Complete the digital access document count; score the alternative against RISE |
| 3 months | Put the use case list, the step down schedule and the exit terms to SAP in writing |
| 1 month | Check every agreed term appears in the order form, not in a side letter or email |
What should you settle on digital access and exit terms before signing?
Settle both before signature, while SAP still wants the deal. Digital access sits outside the user metric and is licensed on document volume, so after the user count is agreed it gets priced as an add on. Exit terms cost nothing to obtain now and shape every later renewal.
How do you establish the digital access document count?
SAP counts nine document types, from sales and purchase documents to invoices, manufacturing and time management documents. Financial and material documents each count as 0.2 of a document. Only documents created through indirect or digital access count, and only at creation, so reads, updates and deletions add nothing.
Measure your current volume from system data before the order form is drafted and bring the figure to the table. Our guide to digital access measurement tools covers the options, and how digital access affects RISE contracts covers where it sits in the paperwork.
Which contract terms should you ask for?
- Credit pool schedule. The annual credit amount written into the order form for each year, matched to your use case timeline.
- Bridge step down. The declining maintenance schedule, the milestone definitions and what happens if SAP causes a delay.
- Infrastructure split. The infrastructure share of the fee shown at signature, as a reference for renewal.
- Digital access entitlement. A document quantity included at the agreed price, with the price for growth fixed in advance.
- Renewal price cap. A written limit on the increase at the first renewal, since a subscription you cannot easily leave will otherwise be repriced.
- Data egress. Your data returned in a usable format at no extra cost when the term ends.
- Transition support and an off ramp. Defined help from SAP if you leave, plus a published path to reduce or exit.
What will SAP's account team say, and how should you answer?
Expect the same few lines in most RISE deals. Each is an opening position that works on an unprepared buyer, and each has a reply that brings the talk back to your documents.
| What you will hear | What to say back |
|---|---|
| "The RISE order form is standard for every customer." | "The format is standard. The credit pool, the bridge schedule and the user mix are sized per deal, so we will size them with you." |
| "The BTP credits are a fixed allocation." | "Here is our use case list with owners and go live dates. Size the credits against it." |
| "Legacy maintenance runs until you have migrated." | "Then tie it to the migration. Here are our dated milestones; step the maintenance down at each one." |
| "This discount is only available if you sign this quarter." | "Our steering committee decides on the date we gave you, after the alternative is scored." |
| "Digital access can be sorted out after go live." | "We have measured our document volume. We want the entitlement and the growth price in this order form." |
What to do next
- Build the use case list first. Name every extension, integration and service, with an owner and rough consumption, before SAP drafts the order form.
- Date the migration run down. Get milestone dates from the program team and ask for a step down cap on the legacy bridge tied to them.
- Score an alternative in parallel. Give it a budget owner, a scoring sheet and a decision date that SAP can see.
- Count digital access documents. Measure volume before signature so the entitlement is priced inside the deal.
- Raise exit terms early. Ask for data egress, transition support and a published off ramp while SAP still wants the signature.
- Check the order form line by line. Every agreed term belongs in the contract documents. The SAP knowledge hub has the wider library, and our SAP practice can run these steps with you.
Frequently asked questions
Is the RISE with SAP price actually fixed?
No. The subscription fee is presented as standard, yet the rate, the credit pool and what sits in the bundle are all sized deal by deal. Buyers who move none of them have usually framed every ask as a discount request, which is the one format SAP's team is best prepared to handle.
How much does the platform credit pool move in a RISE negotiation?
In our negotiations it opened at 3 to 5 percent of annual contract value and closed at 8 to 12 percent once tied to documented use cases. Because unused CPEA credits expire each contract year, ask for the larger pool to be phased to your go live dates, so the extra credit is consumed.
What is the legacy maintenance bridge and why does it matter?
It covers maintenance on the SAP system you are leaving and defaults to full price for around five years. A step down cap tied to the measured migration run down cut that tail 50 to 75 percent over the term. The larger your legacy maintenance bill, the more the schedule is worth.
Does a competitive alternative really widen the SAP RISE discount?
By 8 to 15 points in our deals, where the alternative was scored in parallel. The evaluation has to be real: a budget owner, a scoring sheet and a steering committee date. It takes a separate workstream to produce, which is why it rarely exists when the order form arrives.
Why do most buyers win none of these RISE terms?
Each one depends on work that takes months: a documented use case list, a dated migration run down and a scored alternative. When the order form arrives without them, the only request left is a lower rate, a bounded conversation SAP's team has already planned for.
When should SAP indirect and digital access be settled in a RISE deal?
Before signature, with a measured document count in hand. Agree the included document quantity and the unit price for growth inside the RISE order form. Leave it until after go live and you negotiate it on its own, with no larger deal to trade against and no competing option on the table.
Which RISE contract terms decide the next renewal?
The exit terms: data egress, transition support and a published off ramp, plus a written cap on the renewal increase. SAP grants them most readily while it still wants the first signature, and a subscription you can credibly leave is priced differently at renewal from one you cannot.
How are users counted in RISE with SAP?
In Full Use Equivalents. Each user type carries a weight: an advanced user is a full FUE, a core user a fifth of one, a self service user a thirtieth and a developer two. The contract fixes a total FUE quantity, so how each person is classified, based on what they actually do in the system, drives the bill.