Full narration of the briefing. Click a section heading to jump the player to that moment.
For thirty years, an SAP negotiation meant one thing: fight the list price for a percentage. That era is closing. On S/4HANA and Cloud ERP, SAP has moved away from ad-hoc discounting toward tier-based pricing, where your volume band largely sets your rate and the old fifty-percent-off theater is retired. Buyers who show up to fight for a percentage are fighting the last war.
The tier is the deal now. Here is how to negotiate it.
Section one. Understand the new machine. S/4HANA subscription pricing runs on Full Usage Equivalents, banded into volume tiers, roughly 60 to 550, then to 4,000... to 12,000, to 25,000, and beyond, and the band you land in largely determines your unit rate.
SAP designed this deliberately: standardized tiers resist the discount spiral that eroded its license business for decades. The rep who once had thirty points of discretion now has a rate card and a tier table. Which means the leverage did not disappear. It moved, and most buyers have not followed it.
Section two. Follow the leverage to the band edges. When the tier sets the rate, the negotiation becomes volume architecture: where does your FUE count sit relative to the next band, and what would move it. Aggregating group entities under one agreement, consolidating regional contracts, and timing committed growth into the initial order can carry you across a boundary where the unit price genuinely drops.
where the unit price genuinely drops. The tier crossing is the discount now. It is engineered before the proposal, not begged from the rep after it.
Section three. Fight hardest where nobody is looking: the user-type mapping. Different user categories convert to FUEs at very different ratios, and SAP's default mapping works from your historical ECC classifications... which are almost always heavier than actual usage.
The same ten thousand employees can map to materially different FUE totals depending on how honestly advanced users are separated from functional and occasional ones. In a tier-based world, classification is pricing. Audit the mapping line by line, because a corrected mapping is a permanent saving that no rate card records. Audit the mapping line by line, because a corrected mapping is a permanent saving that no rate card records.
Section four. Spend your capital where discretion still exists. Even in the tier world, four things remain genuinely negotiable. The annual escalator, which compounds and deserves a hard cap.
Conversion credits for the licenses and maintenance you already own, which SAP grants unevenly and prepared buyers maximize. The multi-year structure, where term length and payment schedule still move economics. And the services envelope... migration funding, discretionary credits, roughly ten percent richer this year than next, and implementation support.
The rate card froze the percentage. It did not freeze the deal.
Section five. Make the tier durable. A tier-based agreement has tier-based risks: a modest headcount decline that drops you below a band edge and reprices everything upward... a renewal-time remapping of user types that inflates the count you spent months correcting, and growth priced at whatever the future rate card says.
Write the protections now: your tier held if volume dips within a defined range, the user-type mapping frozen contractually... growth rates pre-agreed, and the escalator capped across the renewal, not just the term. In the old world you defended a discount. In this one you defend a band.
Same fight, new ground.
One last point. At Redress Compliance we negotiate S/4HANA and Cloud ERP agreements on a pure contingency basis. Our fee is 25 percent of what we save you. If we save you nothing, you pay nothing.
Before you accept your tier, let us check which one you actually belong in. com.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded.
Talk to a SAP negotiator