The RISE conversion, rebuilt at the FUE line.

The client brief

The manufacturer ran an ECC 6.08 estate licensed for 11,400 SAP Professional and Limited Professional Named Users alongside eight production engines: SD, MM, PP, FI/CO, PI/PO, HCM, BW and Solution Manager. The estate had grown via acquisition over a six-year window, with three carved-in business units retaining legacy SAP entitlements that had never been reconciled into the master contract.

RISE with SAP was the strategic direction. The conversion clock was running against the ECC 2027 mainstream maintenance horizon and the board had approved an S/4HANA Private Cloud Edition migration. SAP's account team had quoted a 36-month RISE commitment of approximately $37.6M based on the manufacturer's reported Named User and engine population on the most recent USMM.

The procurement leadership engaged us six weeks before the proposed conversion signing date with a brief to test the FUE baseline before commercial commitment. The exposure was not theoretical; signing the RISE conversion at the opening figure would have crystallised the inflated baseline as a contractual minimum for the next three years.

SAP's opening position

SAP's FUE calculation rested on a one-to-one conversion ratio from existing Named User entitlements. Every Professional User in the source contract converted to one FUE on the destination. The 11,400 Named Users plus the eight engine charges converted to a baseline of 14,800 FUEs at the public RISE price point, with a contracted floor at year three of 16,200 FUEs to account for projected growth.

The engine-to-FUE conversion was carried at SAP's published ratios with no allowance for the contractual variance the manufacturer had on three of the eight engines. The HCM engine was carried at active-employee count where the contracted definition was payroll-bearing employee count. The BW engine was carried at named-developer count where actual usage was sub-fifty developers. The PI/PO engine was carried at message volume estimated from a 2021 baseline, not actual production traffic.

The account-team framing positioned the conversion as a benefit migration. The contractual analysis showed a substantial entitlement uplift baked into the conversion ratios — an uplift that, once signed, would have been irreversible without renegotiation under the new RISE master agreement.

The defence tactics

We worked four reconstructions in parallel. None of them required commercial concession from SAP; all of them required documentary evidence and a contractual rebuttal.

USMM rebuild and population audit

We re-ran the USMM measurement against twelve months of transaction history. Of the 11,400 Named Users, 1,840 had no transactional activity beyond logon over the prior twelve months. Another 1,250 had activity confined to ESS workflows that supported a downgrade from Professional to Employee Self-Service. The reclassified baseline was 8,310 chargeable users against the originally reported 11,400.

Engine reconciliation

We rebuilt the engine measurements against the contractual definitions. HCM dropped from active-employee at 14,200 to payroll-bearing at 9,800. BW dropped from named-developer at 280 to verified at forty-six. PI/PO message volume was re-baselined from the 2021 estimate to current production traffic and reduced by sixty-one per cent. The combined engine reduction removed approximately 2,400 FUEs from the conversion baseline.

Acquired-entity entitlement consolidation

Three carved-in business units carried legacy SAP entitlements with overlapping rights. We consolidated the entitlements into the master contract under the manufacturer's existing M&A clause, eliminating $1.2M of duplicated FUE billing across the three legacy lines.

Growth-floor renegotiation

The opening proposal carried a contractual floor at year three of 16,200 FUEs to account for projected organic growth. We presented twelve months of actual user-growth data showing flat-to-negative trajectory on the chargeable population. SAP retracted the floor in favour of a true-up mechanism with capped escalators.

The settled position

The RISE conversion closed at a 36-month commitment of $25.8M against the opening $37.6M, a thirty-one per cent reduction. The FUE baseline was set at 10,200 against the opening 14,800, with the year-three floor removed.

Contractually, we secured a per-engine measurement audit right with thirty days of advance notice, a continuous reconciliation clause permitting annual baseline adjustment downward without commercial penalty, and a cap on FUE escalators at four per cent per annum across the contract term.

The manufacturer's SAM function adopted a quarterly USMM-equivalent measurement cadence under RISE, with documentation maintained continuously rather than rebuilt at audit. The reconciliation framework is now part of the SAM team's standing operating model.

Five takeaways

1. RISE conversion baselines crystallise the inflated Named User and engine population if not rebuilt before signing. The pre-conversion FUE audit is the most leveraged work in the entire RISE programme.
2. Conversion ratios are negotiable when documentary evidence supports a lower baseline. SAP's published one-to-one ratios are a starting point, not a contractual floor.
3. Acquired-entity entitlements are routinely double-counted in RISE conversions. The consolidation work removes one to three per cent of conversion value in most multi-business-unit estates.
4. Growth-floor clauses are aggressive in opening RISE proposals. The flat-trajectory case can be made with twelve months of evidence; the floor is then removable in favour of a true-up.
5. Continuous measurement governance under RISE is necessary, not optional. The contract gives more reconciliation rights than most customers exercise.