SAP's first quote falls 20 to 40 percent before signature, and most of that movement happens in two of the six rounds
Across reviewed RISE and S/4HANA proposals, negotiated savings against the opening number average 25 to 35 percent, and buyers who arrive with benchmark evidence land 45 to 55 percent off list versus 30 to 40 percent for list-price negotiators. The drop is not linear: the FUE count round and the infrastructure and BTP decomposition round produce more movement than every discount conversation combined. Knowing which round you are in tells you whether to push or hold.
Prepared by Redress Compliance · August 23, 2026 · SAP advisory practice. RISE, S/4HANA, and ECC renewal engagements, 2024 to 2026.
Executive summary
The opening quote is padded by design, and SAP expects to concede 20 to 40 percent of it.
Advisory reviews of 50-plus RISE proposals show average negotiated savings of 25 to 35 percent against the first number, which means a buyer who accepts anything inside 15 percent of the opening has left money on the table by SAP's own internal expectation.
The largest single lever is the FUE count, not the rate, and it is the one most buyers never touch.
SAP builds the first quote from legacy license archaeology and classifies every ambiguity upward, so a 10 percent reduction in FUE count on a $5M annual subscription outperforms a 5-point rate concession while costing SAP nothing it can point to as a discount.
Preparation moves the number more than deal size does. List-price negotiators land 30 to 40 percent off list; benchmark-anchored negotiators land 45 to 55 percent, a 15-point spread that has nothing to do with spend tier and everything to do with what the buyer walked in holding.
The last 10 points come from contract structure, not price, and they are worth more over seven years.
Seven contract rewrites across uplift caps, FUE recategorisation, renewal terms, and exit rights preserve 15 to 30 percent of seven-year value that standard SAP template language would otherwise recover, which is why signing a good headline rate under a bad template is a loss.
How SAP builds the opening number, and where the padding sits
The first quote is a construction, not a calculation.
SAP's deal desk builds the FUE count from license archaeology against your legacy estate, and every ambiguous user is classified upward: the approver who touches three transactions a quarter arrives as Core Use rather than Self-Service, and the difference is a 6x conversion swing (1 FUE = 1 Advanced.
5 Core, 30 Self-Service).
Then a rate lands on top of that count, described as "list" for a product with no published rate card at all. SAP's own private edition packaging material contains no prices, which means the discount percentage in your proposal is measured against a number SAP invented for the occasion.
Around the subscription line sit three more constructions: hyperscaler infrastructure at SAP's markup rather than your own negotiated cloud rate, application managed services you may already buy elsewhere, and BTP credits calculated at 1 percent of net ACV.
Floored at EUR10,000 and capped at EUR20,000, then routinely proposed well above actual consumption.
Edition choice (Base, Premium, Premium Plus) and the volume tier ladder (60 to 550, 551 to 4,000, 4,000 to 12,000, 12,000 to 25,000, 25,000-plus) are selected by SAP, not by you, and the selection almost always parks you at the bottom of a tier where the next unit of volume buys nothing.
| Decomposed line | Typical opening padding | Lever that attacks it |
|---|---|---|
| FUE count and classification | 10 to 25% over evidenced usage | Transaction-level usage evidence per user; force reclassification before rate talk |
| Infrastructure (hyperscaler) | 20 to 30% over direct cloud cost | Counter-model: one deal showed AWS-equivalent at $2.1M vs SAP's $3.2M |
| AMS / managed service | Bundled, rarely itemized | Demand a standalone price; test against incumbent SI quote |
| BTP credits | Allocated at 100% when 25 to 35% is consumed | Year 1 at 70% of SAP's number with a 12-month true-up |
The headline rate is the line SAP expects to defend, which is exactly why it is the line least worth attacking first.
Reviewed proposals show the concentration of padding in count and bundled services: one healthcare RISE proposal opened at $1,125,000 annually, benchmarked 18 percent above peers at $920k to $980k.
And $30k of that gap came from BTP credits alone (right-sized from $80k to $50k) without touching the per-FUE rate.
Volume tier placement is worth checking before anything else. If SAP has you at 560 FUE, you are one seat into the 551 to 4,000 band and paying the band's entry economics. If your evidenced count is 540, you are in a different tier with different pricing and SAP will not volunteer that.
Our spend-tier benchmark work shows tier boundaries are the most consistently exploited blind spot in first quotes.
The fall by deal size: what 20 percent and 55 percent actually look like
Locate your deal before you set a target, because the bands diverge sharply by model and spend. Enterprises above $50M annual SAP spend land 40 to 55 percent off list; the $10M to $50M mid-market lands 30 to 45 percent.
By deployment model the spread is wider still: 40 to 60 percent on-premise, 10 to 30 percent on RISE, and only 5 to 20 percent on pure SaaS subscriptions where SAP has the least room and the least competition.
Scaled by FUE, 300 to 500 FUE typically closes at 40 to 50 percent, while 500-plus FUE reaches 50 to 65 percent, though that upper band is bought with five-year commitments and professional services bundling rather than won on price argument alone.
The distribution's tails run from roughly 20 percent on small standalone software purchases to 75-plus percent on large S/4HANA transformation deals.
Preparation moves you further than size does: list-price negotiators land 30 to 40 percent, benchmark-anchored negotiators land 45 to 55 percent, and that 15-point gap costs nothing but evidence.
The RISE band deserves a warning. Because SAP publishes no private edition list price, a "35 percent discount" on a RISE proposal is arithmetic against a figure SAP set the previous week.
The only defensible measurement is movement from opening proposal to signature, and across 50-plus reviewed RISE proposals that movement averages 25 to 35 percent, with 20 to 40 percent the working range.
Treat any off-list claim as unverifiable and insist the negotiation record tracks absolute annual cost, five-year total, and cost per evidenced FUE. Those three numbers survive contact with SAP's pricing changes; percentages do not.
This is the same discipline that shapes where leverage actually sits before the table: measure what you control.
SAP Discount Bands by Spend Tier: What Good Looks Like at $1M, $5M and $20M
The buyer side playbook for SAP Discount Bands by Spend Tier: What Good Looks Like at $1M, $5M and $20M, free behind a work email.
Get the white paper →Round-by-round: where the number actually moves
A RISE negotiation runs six rounds whether you plan them or not, and the money is not evenly distributed across them.
Round one produces zero price movement and is the most important thing you will do: force the single all-in number into four lines (subscription, infrastructure, managed service, BTP), because the leverage lives in the lines and SAP quotes the bundle precisely so you cannot see them.
Round two is the FUE classification challenge, and it is the largest single drop available.
SAP builds the count from legacy license archaeology and classifies upward at every ambiguity, so 500 light approvers arrive priced as 500 users when the ratios (5 Core Use per FUE, 30 Self-Service per FUE) allow as few as 17.
Round three is infrastructure and disaster recovery posture, where in our experience across reviewed proposals a shift from hot standby to warm standby moves the infrastructure line 30 to 60 percent.
And where you demand the hyperscaler line-item breakdown SAP would rather keep folded into managed service.
Round four right-sizes BTP against industry consumption of 25 to 35 percent: propose Year 1 at 70 percent of SAP's allocation with a 12-month true-up on actual usage. Round five is term structure, two years firm with renegotiation rights in years three through five.
Round six is contract language, where seven targeted rewrites preserve 15 to 30 percent of seven-year value that SAP's standard paper otherwise recovers. Note what is absent: the discount conversation buyers rehearse for weeks is round five or six, and it moves the least.
Our discount bands by spend tier benchmarks should be used to validate round five, not to open round one.
| Round | Lever | Expected movement on the line |
|---|---|---|
| 1 | Decompose into four lines | 0% price, unlocks rounds 2 to 4 |
| 2 | FUE classification challenge | Largest single drop; 10% count reduction on a $5M subscription is material |
| 3 | Infrastructure and DR posture | 30 to 60% off the infrastructure line (warm vs hot DR) |
| 4 | BTP right-size to 25 to 35% consumption | $80k allocation to $50k in reviewed cases |
| 5 | Term structure and discount | Modest; 2 years firm plus years 3 to 5 renegotiation rights |
| 6 | Contract language rewrites | 15 to 30% of seven-year value preserved |
Why the quote falls further when you never mention discount
SAP administers its concession budget through two separate mechanisms with two separate approval paths, and buyers who lead with a discount request are drawing on the scarce one. A percentage ask goes to deal desk.
It is logged, capped, visible to regional management, and measured against the account team's quota attainment.
Every point you extract there is a point the rep must defend upward, which is why the answer comes back slowly, arrives smaller than asked, and gets traded for a longer term or a broader commitment.
You are competing for a finite, politically expensive resource, and you are competing for it in the open.
A FUE reclassification is not a discount. Neither is a BTP right-size, nor a change from hot to warm DR standby. These are scope corrections. They do not touch the discount approval ladder because they do not change the rate, they change what is being counted.
A rep can concede that 380 of your 450 named users are Core Use rather than Advanced Use without asking anyone's permission, because on paper the price per FUE never moved. The economics moved by a fifth.
Understanding which currency you are spending is the difference between a 30 percent outcome and a 50 percent one.
This is exactly the mechanism behind the two most instructive reviewed deals. The $1,125,000 annual proposal that sat 18 percent above healthcare peers (comparable estates at $920,000 to $980,000) did not come down through a discount fight.
It came down through decomposition: the BTP credits were right-sized from $80,000 to $50,000, and the FUE and support assumptions were rebuilt against evidence. The $3.2M five-year quote was not met with a counter-offer at all.
Procurement built an AWS S/4HANA cost model at $2.1M annually, 26 percent cheaper, and put the infrastructure line under a competitive reference rather than under a percentage request.
SAP's commercial teams overstate the bundle premium for a reason. On a 1,700 FUE estate over five years, bundled RISE Premium is worth roughly 10 percent versus buying comparable scope directly.
Real, but a fraction of what account teams claim, and it is traded against the loss of your right to swap AMS provider, change hyperscaler, or right-size BTP inside the term. The bundle is not primarily a savings vehicle.
It is the mechanism that hides the decomposable lines, and the premium narrative exists to discourage you from opening it.
One trap sits in your own file. The July 2025 SKU repackaging, confirmed by DSAG, raised the per-FUE base above the old RISE Premium rate.
A customer who signed RISE Premium in 2023 pays less per FUE than the same customer signing Cloud ERP Private Edition in 2026, even at an identical discount percentage. Your renewal baseline is therefore a decaying benchmark.
Adjust it for the repackaging before you cite it, or you will negotiate hard against a number that flatters SAP.
The sequencing conclusion is straightforward. Spend rounds one and two correcting scope, round three and four correcting infrastructure and BTP, and only then open the discount conversation.
A modest percentage applied to a corrected base beats an impressive percentage applied to a padded one, and the discount you are eventually offered will be larger anyway, because you will not have spent your deal desk capital arguing about a rate attached to the wrong quantity.
The tell that you are in the wrong currency: SAP responds to your discount ask within 48 hours with a small number, and responds to your FUE evidence with a request for a workshop. Speed signals a pre-approved concession.
Delay signals a line SAP has to actually recalculate, which is where the money is. Track the two budgets separately in your own file.
If you reach round five having spent nothing at deal desk, you arrive with the full discount envelope intact on top of a base that is already 15 to 25 percent lower than the opening quote.
What SAP does when you decompose the quote
The moment you ask for a line-item split, the account executive's script changes. Expect five countermoves, in roughly this order, and price each one before you hear it.
First, "RISE is a packaged offering and the components are not separately priced." That is a commercial posture, not a contractual fact.
Reviewed proposals move 20 to 40 percent off the opening number precisely because the subscription, infrastructure, managed service and BTP lines carry different margins.
Hold the position that you cannot approve a number you cannot audit, and that internal finance requires infrastructure spend to be identifiable for capitalization treatment. Second, SAP will refuse the split but offer to "show the value build" verbally. Decline.
Require the hyperscaler infrastructure breakdown in writing, then price it independently against an AWS or Azure model.
One reviewed deal opened at $3.2 million annually on a five-year term with uncapped CPI escalation and a 90-day exit clause; the buyer's AWS equivalent came in at $2.1 million, 26 percent cheaper, and that document did more work than any discount request.
Third, when price will not move, SKUs will. Signavio, SAP Build, Business AI and inflated BTP credits arrive as "added value" because they preserve the per-FUE rate in SAP's internal benchmark files, which is what the deal desk is actually defending.
Take the SKUs if you want them, but insist they are additive to a reduced rate, not a substitute for one. Fourth, SAP re-anchors on a five-year commit as the price of the discount.
Five years is worth paying for only with a capped uplift, a documented exit, and a mid-term right to re-tier FUEs downward. Fifth, quarter-end and fiscal-year timing pressure. That pressure is real and it is yours, not theirs, provided you have a credible alternative model on the table.
Compare how the same mechanics play out across SAP discount bands by spend tier before you decide which quarter to close in.
The most under-used counter is not a price argument at all. If you hold an AWS EDP or Azure MACC, insist the RISE infrastructure component is billed through the hyperscaler marketplace so that spend retires an existing commit.
That converts a cost line into a commitment you already owe, and it forces SAP to expose the infrastructure figure it spent three rounds refusing to isolate.
Expect the reflex answer that marketplace billing is "not supported for this deal shape." It is supported; it is simply not offered. Ask for the exception in writing and escalate one level above the account executive, because the decision sits with the region, not the rep.
The evidence base: what reviewed proposals show
Measured against SAP's own opening number, not list, so it sits on top of any headline discount already quoted.
A healthcare proposal opened at $1.125M annually where comparable peers were signing at $920k to $980k.
That healthcare deal is instructive because every element of the padding was visible once decomposed: 22 percent support against a negotiable base, 4 percent annual escalation with no cap, 450 NUPs carried forward without usage evidence.
And $80,000 of BTP credits against consumption patterns that supported roughly $50,000, worth $30,000 a year on its own.
None of those lines were presented as adjustable. All of them adjusted.
The recurring pattern across reviewed proposals is that the padding lives in the FUE count, not the rate, and buyers spend their energy on the wrong lever.
The conversion ratios do the damage quietly: one Advanced user, five Core users or thirty Self-Service users each consume one FUE, and a Developer consumes two. Five hundred light approvers can legitimately land at 17 FUEs.
Every opening quote examined classified upward at the point of ambiguity, and no quote reviewed classified downward. That is not an error rate; that is a design choice, and it survives because the buyer rarely brings usage evidence to contest it.
The same logic underpins the per-unit FUE benchmarking, uplift cap and migration credit work we run on live deals: the FUE benchmark tells you whether the rate is defensible, the cap tells you what year three costs, and the credit tells you who is funding the move.
Buyers who arrive with all three land 45 to 55 percent off list. Buyers who negotiate against list alone land 30 to 40 percent, and the difference is preparation, not spend tier. The broader pattern is documented in our enterprise software negotiation leverage report.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
Your first five moves
- Refuse to quote a target price until the number is split into four lines. Send one email: subscription, infrastructure, managed service, and BTP credits, each priced separately, and tell the account executive no counter comes back until those four figures exist, because the leverage lives in the lines and never in the all-in figure.
- Run FUE reclassification against actual usage evidence before anyone mentions rate. Pull transaction logs and role assignments, apply the 1:5:30 conversion ratios (Advanced, Core, Self-Service), and target a 10 to 15 percent count reduction; on a $5M subscription that beats a rate concession SAP will offer more readily and price back into year three.
- Build the hyperscaler counter-model and the peer range so you can name a number. One reviewed deal used an AWS S/4HANA equivalent at $2.1M against SAP's $3.2M (26 percent cheaper), which is how you justify asking 25 to 35 percent off the opening rather than pleading for it; cross-check against discount bands by spend tier.
- Right-size BTP to 70 percent of SAP's allocation with a 12-month true-up. Industry consumption runs 25 to 35 percent, so credits are routinely over-allocated; one reviewed proposal cut $80k to $50k. Check EDP or MACC eligibility in parallel so hyperscaler spend counts twice.
- Hold the final 10 percent of concession for contract language, not price. Trade it for an uplift cap of 3 to 5 percent, written FUE recategorisation protection, and renegotiation rights in years four and five. Price moves once; language moves every year, a point developed in the 2026 leverage report.
Sequence matters more than aggression. Buyers who open with a discount demand hand SAP the rate conversation, which is the lever SAP most wants to trade.
Buyers who spend rounds one and two on decomposition and FUE evidence arrive at the rate discussion with the count already 10 to 15 percent lower, and the percentage then applies to a smaller base.
Expect the account executive to resist line-item pricing, cite "packaged" commercial terms, and escalate to a regional director. That escalation is the signal you are on the right lever, not the wrong one.
Frequently asked questions
How much should I expect SAP's first quote to drop before signature?
Across reviewed RISE and S/4HANA proposals, movement from the opening number to signature runs 20 to 40 percent, with an average of 25 to 35 percent. Anything inside 15 percent of the first quote means you stopped negotiating early.
The spread within that band is driven mostly by preparation, not deal size.
Is SAP RISE pricing actually negotiable, or is it packaged?
It is negotiable. SAP positions RISE as a packaged offering with a fixed per-FUE rate, but reviewed deals move 20 to 40 percent off the opening proposal.
The movement often comes through FUE count, infrastructure, AMS and BTP lines rather than the headline rate, which lets SAP preserve the rate in its own benchmark files while still conceding value.
Why does SAP not publish a list price for RISE private edition?
SAP publishes no rate card for the private edition, so any per-FUE figure you see is a third-party benchmark. Third-party bands vary widely, from roughly $140 to $220 per FUE per month in one source to $190 to $360 in another, and EUR220 to EUR280 in a third.
Because there is no published list, an off-list discount percentage on RISE is unverifiable and only movement off the opening proposal is measurable.
Which negotiation round produces the biggest price drop?
The FUE classification round. SAP builds the count from legacy license archaeology and classifies upward at every ambiguity, so a 10 percent count reduction on a $5M annual subscription outperforms several points of rate concession.
Round one, decomposition of the all-in number into subscription, infrastructure, managed service and BTP, produces no price movement itself but is what makes every later round possible.
How much difference does having a benchmark make?
About 15 points. Negotiators anchoring on SAP's list achieve 30 to 40 percent off; negotiators anchoring on peer benchmark evidence achieve 45 to 55 percent. That gap holds across spend tiers, which means a well-prepared mid-market buyer can beat an unprepared enterprise on percentage terms.
Should I take extra SKUs instead of a price reduction?
Usually not. SAP offers Signavio, Build, Business AI and similar additions to protect the per-FUE rate, and the bundle premium is smaller than SAP's commercial teams claim: roughly 10 percent on a 1,700 FUE five-year estate.
You also give up flexibility to swap AMS provider, change hyperscaler, or right-size BTP credits inside the term.
How much BTP credit should I accept in the first year?
Benchmark against typical industry consumption of 25 to 35 percent of allocation. A workable counter is Year 1 at 70 percent of SAP's proposed allocation with a 12-month true-up on actual usage.
In one reviewed deal, right-sizing $80,000 of BTP credits to $50,000 produced $30,000 in annual savings with no operational impact.
