Polestar Solutions

Field Notes

SAP RISE: what a Functional User Equivalent really costs

RISE with SAP repackaged the largest ERP estate in the world into a subscription priced per FUE, and the role mix is the price. How the FUE works, where misclassification hides, and the five moves before you sign away your leverage.

Key points

  • On a $5M a year RISE subscription, an evidence-based classification that lands the FUE total just 10% below the vendor's draft is $500,000 a year, every year of the term, which no achievable discount on the rate will match.

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.

app.isvcosell.com/benchmarking/run

The quote against reality: net ACV per FUE placed in the cohort of modelled RISE cohorts.

THE SAME JOB, TWICE

TODAY, BY HAND

SAP's proposal arrives with the FUE count already built from your legacy license archaeology, classified upward at every ambiguity.

The deal team negotiates the rate, the smaller of the two levers, because nobody has usage evidence to contest the classification.

The quote gets compared to a discount off a list price SAP controls, not to what comparable RISE deals actually signed at.

Renewal caps, frozen FUE definitions, and true-down corridors go unrequested, and after migration the walk away is gone and they become favors.

Months of migration pressure, with the biggest lever never pulled

WITH ISVCOSELL

Build the role mix from actual usage data in the RISE playbook, so your own FUE classification answers the one SAP drafted.

Benchmark the quote as net annual contract value per FUE against modelled RISE cohorts, normalized for FUE volume and term.

Draft the term sheet with the playbook's protections: uplift cap, growth rate protection, frozen FUE definitions, true-down corridor, and SLA credits with teeth.

Generate the full dossier for the deal team, with the AI advisor grounded in how comparable RISE negotiations actually settled.

Days to a defensible classification and a benchmarked position

What changes: the negotiation moves from the rate to the count, which is where the money is. On a $5M a year RISE subscription, an evidence-based classification that lands the FUE total just 10% below the vendor's draft is $500,000 a year, every year of the term, which no achievable discount on the rate will match.

"Classify first, negotiate the rate second. In the other order, your outcome is capped before the negotiation starts."

PART TWO

The weekly licensing brief

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.

Get the brief

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.

app.isvcosell.com/tooling

The RISE playbook: role mix, benchmark, and the protections that must be written before the leverage cliff.

PART THREE

Five moves before you sign

1 Build the role mix from usage, not from licenses. Measure what each user actually does and draft your own FUE classification. Never negotiate from a count the vendor assembled.

2 Benchmark the quote per FUE. Net ACV per FUE against modelled RISE cohorts of your size and term. The percentile tells you whether you are negotiating for the last five percent or the first twenty.

3 Price the credit for what you already own. Your perpetual licenses and prepaid maintenance are the currency you bring. What SAP offers for them varies deal to deal far more than the headline rate does, and it is benchmarkable.

4 Write the renewal into the original deal. Uplift cap, growth rate protection, frozen FUE definitions, true-down corridor, and real SLA credits. Every one of these is cheap before signature and nearly unbuyable after migration.

5 Keep the alternative alive until the ink dries. A costed stay-and-maintain or third-party support scenario for the transition years is your only real walk away, and it evaporates the day you sign. Let the deal team see SAP's proposal priced against it to the end.

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.

MA

About the author

Morten Andersen, Cofounder, ISVCOSELL

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 ISVCOSELL to make that pattern recognition repeatable.

More posts by Morten Connect on LinkedIn →

See it in the product

How benchmarking works → Browse the use cases → Every feature → Calculate your time saved →

FREE TRIAL · FULL PLATFORM · NO CARD REQUIRED

Benchmark your RISE quote per FUE before you sign.

The free trial opens the benchmarking database, 1,483 vendors deep, plus the negotiation guides, playbooks, and talking points for your own renewals. No card needed, a corporate email is all it takes.

Start your free trial → Or decode a contract free, no account

Free for 30 days, no card needed. Your data stays isolated at the database, and you can export or delete it any time.

Watch it in action

ISVCOSELL: the three minute demo What discount should we expect? One question, every agreement

Browse the full demo library →

THE ISVCOSELL AI BRIEF · WEEKLY

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.

Subscribe

More in Field Notes

1,483 vendors, one method: how the benchmark library is built

A benchmark is only as good as the deals behind it and the honesty of how it is compared. How the library is built from modelled deal cohorts, normalized, placed in the right peer cohort, and graded by confidence.

Read

300 vendors, 52 weeks, one team: the renewal calendar problem

The average enterprise runs 300+ software vendors and every one of them renews. Why notice windows are where budgets quietly die, and how a renewal desk with AI agents turns the calendar from a threat into leverage.

Read

A calmer desk, and Main Apps where the work starts

The platform now wears the desktop look: warm paper, one interactive colour, and Main Apps folded into Home so your instruments live where you start.

Read

A live analyst in your ear: inside the call copilot

The vendor call is where prepared positions meet improvisation, and the rep does this every day. The live call copilot runs a whisper rail beside the conversation: live transcript, grounded prompts, and the exact fact you need at the moment the claim is made.

Read

Adobe ETLA vs VIP: seat reclaim, right-profiling, and the walk away

An Adobe ETLA renewal is decided before you discuss price, by how many seats sit idle and how many are over-profiled. How to reclaim the waste, right-profile the rest, and build the VIP walk away Adobe respects.

Read

Agent to agent: how the Agent Negotiation Protocol works

When a buyer's AI agent negotiates with a vendor's AI agent, someone has to keep the record straight. How the open Agent Negotiation Protocol handles identity, mandate, and a ledger neither side can rewrite.

Read

Want help putting this into practice?

Contact us to discuss your project.

Get in Touch