How user growth assumptions change RISE TCO outcomes.

Every seven year RISE with SAP TCO model has a hidden lever that, more than any other single variable, dictates the final number. That lever is the user growth assumption. A model built on three percent annual user growth produces a different answer than a model built on five percent annual growth, and the spread between the two often exceeds the entire negotiated discount on the headline price. The growth assumption is the variable the SAP account team will let the buyer set without challenge, because the account team understands that the higher the growth assumption, the higher the seven year contract value. The buyer side discipline is to set the growth assumption with care, to test it with sensitivity bands, and to bind it inside the contract on terms that protect the buyer if growth runs differently to plan.

Why the growth assumption dominates the seven year curve

The FUE entitlement on a RISE contract scales linearly with the named user count across most of the bands. The compute capacity scales with the user count plus the transaction profile. The BTP credit consumption scales with the integration count plus the user driven workload. The support coverage scales with the named user count. A one percentage point change in the annual user growth assumption produces, across seven years, a compounded change in the FUE total of approximately seven percent, in the compute total of approximately five percent, and in the BTP total of approximately four percent. The compounded effect on the seven year total runs at four to six percent per percentage point of growth assumption.

Across the firm engagement base, the median user growth assumption that arrives inside the SAP supplied business case sits at five percent annually. The median actual user growth across the same client base sits at two point three percent annually. The spread between the SAP assumption and the actual outcome is the structural reason RISE deals close at headline numbers that look reasonable and produce seven year totals that overshoot the plan. The buyer side discipline is to set the growth assumption to the actual growth profile of the business, not to the SAP supplied assumption.

The actual growth profile is sourced from three independent inputs. The five year hiring forecast from HR. The five year revenue forecast from finance. The five year SAP user growth from the existing SAP estate. The three inputs are reconciled against each other, with the SAP user growth typically running thirty to fifty percent below the revenue growth and twenty to thirty percent below the headcount growth, because not all new hires receive SAP access. The reconciled output is the growth assumption that the seven year TCO model uses, with a documented sensitivity band on either side.

Setting the assumption against historical SAP estate growth

The single most reliable input to the growth assumption is the historical SAP estate growth across the prior five years. The SAP user log captures the named user count by month, by role profile, and by FUE band, with audit grade accuracy. The buyer side leads pull the prior sixty months of named user count from the SAP estate, compute the compound annual growth rate by band, and use the result as the central case in the seven year model. The historical growth is the most defensible input because it captures both the headline growth and the role drift inside the bands.

The historical growth across the firm engagement base sits between one point eight and three point four percent annually for the named user count, across all bands. The same historical growth across the higher FUE bands, the GA and Advanced bands, sits between two point four and four point two percent annually, because the higher bands grow with the executive and management headcount, which grows faster than the operational headcount. The two growth rates have to be modelled separately, because the GA and Advanced bands are priced at a multiple of the Core band, and the differential growth amplifies the cost impact.

The historical growth schedule also captures the band recategorisation drift, which is structurally upward across the SAP estate. The same user role that sat in the Core band three years ago may sit in the Advanced band today, because the FUE band definitions have shifted in the intervening SAP releases. The historical drift across the firm engagement base shows approximately four percent of named users moving upward by one band annually, against an effective downward movement of less than one percent annually. The net upward drift is between three and four percent annually, and it has to be carried in the seven year model alongside the headline growth.

Sensitivity bands tell you which contract clauses to negotiate

A point estimate growth assumption is enough for the business case, but it is not enough for the negotiation. The negotiation work is driven by the sensitivity bands around the growth assumption, because each band corresponds to a contract surface that the buyer side leads can negotiate. The firm builds the sensitivity at three points for every model. A low case at zero percent annual growth, a central case at the historical growth rate, and a high case at the upper bound of the revenue and headcount forecast.

The low case captures the downside scenario, where the business divests, restructures, or shifts users off SAP. The contract surface that responds to the low case is the true down mechanism on the FUE bands, which is rarely present in the standard RISE template and has to be negotiated in. Without a true down mechanism, the buyer is paying for FUE entitlement that the business is not consuming, and the cost runs for the remainder of the seven year term. The negotiation work on the low case targets the true down clause, with a defined quarterly review cadence, an agreed reduction trigger, and a cap on the maximum annual reduction.

The high case captures the upside scenario, where the business grows faster than the historical baseline, where new entities are added through acquisition, or where additional SAP modules are deployed. The contract surface that responds to the high case is the growth band schedule, which dictates the per band uplift price at each growth threshold. The negotiation work on the high case targets the growth band schedule, with wider bands, lower per band uplifts, and a documented review trigger if growth runs above the upper band. The sensitivity work is the bridge between the model and the contract.

Binding the growth assumption inside the contract

The growth assumption is not just a TCO input. It is a contract surface, and it has to be bound inside the RISE contract on terms that protect the buyer if growth runs differently to plan. The standard RISE template does not bind the growth assumption. The buyer side discipline is to negotiate the growth mechanism into the contract, with three components that together define the boundary of the buyer obligation across the term.

The first component is the growth band schedule. The schedule defines the FUE entitlement uplift price at each growth threshold, with bands sized wide enough to cover the central case plus the upper bound of the sensitivity. Wide bands reduce the frequency of per band uplift events, which compresses the SAP recovery mechanism. The standard SAP template uses narrow bands that trigger uplift events frequently. The buyer side counter is to widen the bands, typically to twenty or twenty five percent above the entry FUE allocation, with the per band uplift priced at the entry rate plus a defined uplift.

The second component is the recategorisation clause. The clause defines the process by which SAP can recategorise named users from one band to a higher band. The standard SAP template leaves the recategorisation criteria unbound, which gives SAP discretionary latitude to drift users upward across the term. The buyer side counter is to document the criteria, agree a quarterly review cadence with both parties at the table, and add a true down mechanism that mirrors the true up. The third component is the growth ceiling. The ceiling caps the cumulative growth that can be priced at the in contract rate, beyond which the buyer has the option to renegotiate. Without the ceiling, the SAP rate continues to apply at the in contract level for whatever growth the business produces, with no buyer side leverage to test the market mid term.

How the wrong assumption distorts the comparison

The growth assumption distorts not just the RISE TCO total but the RISE versus brownfield comparison. A high growth assumption inflates the seven year RISE total disproportionately, because the RISE side scales linearly with the FUE growth. The same growth assumption applied to the brownfield side inflates the on premise total at a lower rate, because the brownfield side scales with the named user uplift schedule rather than with the FUE bands, and the per user uplift is typically priced at a lower multiple of the entry rate.

The structural effect of a high growth assumption is to make brownfield look cheaper than RISE in the seven year comparison. A low growth assumption produces the opposite distortion. The RISE side benefits more from low growth than the brownfield side, because the bundled RISE pricing carries a fixed component that does not scale down with low growth, while the brownfield side scales down more closely with the actual user count. The growth assumption is the variable that, more than any other single input, decides which side of the comparison wins.

The buyer side discipline is to run the comparison at three growth points, with the central case at the historical growth rate, the low case at the downside scenario, and the high case at the upper bound of the forecast. The output is three comparisons, one for each growth scenario, with the optimum option in each scenario identified. The decision turns on the scenario the buyer regards as most likely, with the contract surfaces in each scenario negotiated to limit the downside if the actual growth runs against the central case.

The boardroom version of the growth conversation

The board level conversation around RISE turns on the growth assumption more than on any other input. The CFO will ask the question first. What growth assumption is in the model. The buyer side leads need to answer with the central case, the low case, and the high case, with the corresponding seven year totals for each scenario, with the contract surfaces that protect the buyer in each scenario, and with the source of the central case assumption. Without all four answers, the board level conversation runs into a parametric debate that does not resolve.

The discipline of the growth assumption is the discipline of the seven year RISE TCO model in microcosm. The assumption is sourced from independent data. The sensitivity is run at three points. The contract surfaces are identified. The negotiation work targets the surfaces. The board level conversation closes on the central case with the surfaces in place to bound the downside and to test the upside. The growth assumption set with this discipline produces a contract that compounds value across the term. The growth assumption set without this discipline produces a contract that overshoots the plan inside the first eighteen months and continues to overshoot for the remainder of the seven years.

Set the growth assumption with the same care as the headline price

The user growth assumption is the lever inside the seven year RISE TCO model that most violently changes the answer, and it is the lever that the SAP account team will let the buyer set without challenge. The buyer side discipline is to set the assumption from the historical SAP estate growth, to reconcile the assumption against the HR and finance forecasts, to test the assumption with three point sensitivity bands, and to bind the assumption inside the contract through the growth band schedule, the recategorisation clause, and the growth ceiling.

Across the firm engagement base, the discipline of the growth assumption is consistently worth between fifteen and twenty eight percent of the seven year contract value. The discipline is also the leading indicator of how the post signature relationship will run. A RISE deal that closes with a tight growth assumption and a documented growth schedule will compound value across the term. A RISE deal that closes with an inflated growth assumption and an unbound growth schedule will overshoot the plan inside the first eighteen months, and the renegotiation conversation will arrive earlier than the buyer expects.