$19.6M RISE commit, settled at $12.2M.

The client brief

The asset manager ran a focused ECC estate licensed for 4,800 Named Users alongside six production engines covering FI, CO, asset accounting, treasury, BW for regulatory reporting, and Solution Manager. The estate had grown organically over the prior decade with no significant M&A activity, and the entitlement structure was relatively clean.

The board had approved a RISE with SAP Private Cloud conversion with a target go-live twelve months out. SAP's account team had quoted a 36-month RISE commitment of $19.6M, structured as a baseline FUE plus a year-three growth floor of approximately fifteen per cent above the conversion baseline.

The Head of Technology Procurement engaged us with a brief that reflected the firm's investment-process discipline: the conversion economics had to be model-defensible. The cost case had to be auditable against a documented baseline and the assumptions had to survive an internal investment-committee review.

SAP's opening position

SAP's FUE baseline was built on a one-to-one conversion of the existing Named User and engine entitlement. The 4,800 Named Users converted to 5,800 FUEs at SAP's published ratios, with engine charges layered at approximately 1,200 FUEs. The total baseline was 7,000 FUEs at the public RISE Private Cloud price point.

The year-three growth floor was set at 8,050 FUEs, a fifteen per cent uplift above the conversion baseline to account for projected organic growth. The contractual escalator was capped at six per cent per annum and the proposal carried a multi-year prepay discount of approximately eight per cent against the no-prepay alternative.

The framing of the opening proposal was technically clean but commercially aggressive. The conversion ratios, the growth floor, and the escalator combined to crystallise an entitlement structure approximately twenty-five per cent above the firm's actual run-rate consumption — an entitlement that, once contractually committed, would have been irreversible.

The defence tactics

We worked the conversion as a documentation problem. Four reconstructions carried most of the reduction; a fifth — the growth-floor rebuttal — closed the remaining gap.

Named User population audit

We rebuilt the Named User population against twelve months of transaction history. Of the 4,800 users, 620 had no transactional activity over the window and could be retired. Another 480 had activity confined to ESS workflows. The reclassified baseline was 3,700 chargeable users against the opening 4,800.

Treasury engine reconciliation

The treasury engine was quoted at the standard tier with all sub-modules active. Actual deployment covered three of seven sub-modules. We rebuilt the treasury entitlement against deployed scope and removed approximately $1.8M from the conversion baseline.

BW engine right-sizing

The BW engine was carried at named-developer count with a population estimate of 80 developers. Actual usage was 22 developers with no broader analyst population. The right-sized BW baseline reduced the conversion cost by approximately $0.6M.

Growth-floor rebuttal

The year-three growth floor at 8,050 FUEs was set against a projection of organic growth at five per cent per annum. We presented twelve months of headcount and transaction-volume data showing flat-to-marginal trajectory. SAP retracted the floor in favour of an annual true-up with capped escalators.

The settled position

The RISE conversion closed at a 36-month commitment of $12.2M against the opening $19.6M, a thirty-eight per cent reduction. The FUE baseline was set at 4,800 against the opening 7,000, with the year-three floor removed.

Contractually, we secured a per-sub-module treasury entitlement schedule with documented deployment scope, a BW engine right-sizing clause with biennial reconciliation, and an annual true-up mechanism with escalators capped at three per cent per annum.

The firm's investment-committee-level documentation now includes the SAP entitlement baseline as a standing audit-defence file. The same documentation supports the SAP licence audit response and the firm's broader vendor-management governance.

Five takeaways

1. RISE conversions in financial services are particularly susceptible to over-entitlement through under-documented sub-module deployment. The treasury and asset-accounting engines are typical contributors.
2. Investment-committee-grade documentation strengthens both internal governance and SAP negotiations. The same evidence carries both.
3. Growth-floor clauses are negotiable through trajectory evidence. The flat case is straightforward to make with twelve months of data.
4. Sub-module treasury entitlements are routinely over-provisioned in conversion proposals. The deployed-scope rebuild typically removes one to two million dollars of conversion value.
5. BW engine right-sizing is among the simplest and highest-leverage reductions in a financial services RISE conversion. The named-developer count is rarely as high as estimated.