SAP RISE: what a Functional User Equivalent really costs.
RISE with SAP repackaged the world's largest ERP installed base into one subscription: software, infrastructure, and services, priced per FUE. The metric sounds technical and is actually the entire negotiation, because the FUE count is built from a role classification that most customers let SAP draft. Here is how the metric works, and the five moves to make before signing away the leverage a migration only grants once.
Every SAP customer is having the same conversation right now, because SAP arranged for it. Mainstream maintenance on the old ECC estate has an end date, S/4HANA is the destination, and RISE is the vehicle SAP wants you in: a single subscription bundling the software, the hosting, and a services layer, replacing licenses you owned with a contract you rent. The deadline pressure is real, the strategic logic is defensible, and the commercial structure deserves far more scrutiny than the migration timeline usually leaves room for.
The scrutiny starts with the metric. RISE is priced per Full User Equivalent, the FUE, and unlike a seat or a core, an FUE is a derived number. Different roles convert at different weights: a heavyweight functional user counts fully, lighter operational roles convert at several to one, and self service users at dozens to one. Your annual cost is the FUE total times the rate, which means the price has two levers, and the one everybody negotiates, the rate, is frequently the smaller of the two.
The role mix is the price
Because the FUE is derived, the classification exercise that produces it is where the money moves. A user classified as advanced costs many times what the same user costs classified as self service, and in a proposal built from your old license counts, the drafting side has every incentive to classify upward. Legacy professional licenses map comfortably to advanced FUEs whether or not the humans behind them ever do more than approve a purchase requisition and check a report.
The counter is evidence. Actual usage data, what each user touches, how often, and how deeply, supports a role mix that reflects reality rather than license archaeology. On estates of tens of thousands of users, moving a realistic fraction of the population from advanced to core or from core to self service routinely changes the FUE total by double digit percentages, which no achievable discount on the rate will match. Classify first, negotiate the rate second. Doing it in the other order caps your outcome before the negotiation starts.
Then benchmark what remains. The platform prices RISE positions as net annual contract value per FUE against modelled RISE cohorts, normalized for FUE volume and term, so the quote in front of you gets compared to what deals shaped like yours actually signed at, not to the discount theater of a list price SAP controls.
Want to be updated when major licensing and pricing changes land? One analyst brief a week: the price rises, metric changes and audit campaigns that move software costs. Work email only.
The leverage cliff: everything is negotiable exactly once
RISE has a property that makes it unlike an ordinary renewal: the negotiation happens while you still own an alternative, and then the alternative expires. Before signature, you hold perpetual licenses, a running estate, and the option to move slower, host elsewhere, or stay put and pay maintenance. After migration, the estate lives in SAP's bundle, and the first renewal arrives with your walk away amputated. Whatever protections you did not write into the original agreement, you will be requesting later as favors.
So the contract has to do the work up front, and three clusters of terms matter more than the launch rate. Renewal economics: a hard cap on the renewal uplift, and rate protection on growth, so added FUEs price at your negotiated level rather than resetting the deal. Metric stability: the FUE definitions and conversion ratios frozen for the term and through renewal, because a quiet reweighting of roles is a price increase wearing a metric costume. Downside rights: a true-down corridor at renewal for the divestiture or the headcount reduction you cannot foresee, and service credits with teeth for the operational layer you are now renting.
This is exactly the sequence the RISE playbook runs: the role mix analysis, the per-FUE benchmark, the term sheet with these protections drafted, and an AI advisor grounded in how comparable RISE negotiations actually settled, with the full dossier generated for the deal team.
Five moves before you sign
The honest close: for most SAP estates, some version of this migration is coming, and RISE will often be the rational answer. That is precisely why the commercial work matters. You are not deciding whether to have a relationship with SAP for the next decade. You are deciding, once, on what terms, and the FUE arithmetic you walk in with is the difference between renting your ERP at market and renting it at whatever the migration deadline made you accept.
Morten brings two decades of enterprise and software procurement, with stints across Oracle, IBM, SAP, and Salesforce shaping how he reads a deal. He has led sourcing through hundreds of renewals, from mid market order forms to nine figure global agreements, and learned that the buyers who win are the ones who walk in knowing the market. He built VendorBenchmark to make that pattern recognition repeatable.
The week in enterprise software buying, in one email.
What shipped on the platform, and the pricing and licensing moves worth knowing before your next renewal. One email a week, to your work address. Unsubscribe any time.