SAP License Optimization
Named-user and engine mix. We rebuild the user model against transaction evidence, reclassify against the contract definitions, and fix the conversion ratios before they are written into the schedule.
Read the brief →A global industrial manufacturer consolidated five overlapping SAP licence agreements into a single FUE-denominated bundle, eliminating $4.1M in duplicated entitlements and capping future growth at the contract level.
Every result on this site is anonymised at the client’s request. Specific figures are real and verifiable through a confidentiality-protected reference call arranged on request.
The client is a global industrial manufacturer with revenue of approximately seven billion dollars, sixty-eight thousand employees, and a long-tenured SAP estate accumulated over fifteen years of growth and acquisition. The relationship with SAP was governed by five separate master agreements: an original ECC contract from 2009 covering the parent group, a 2013 acquisition contract retained on its original terms, a 2017 BW/4HANA agreement, a 2019 SuccessFactors agreement signed regionally, and a 2022 RISE pilot agreement for a single business unit.
The five contracts had grown to a combined annual contract value of twenty-two point eight million dollars. The engagement was triggered six months before the largest of the contracts came up for renewal. The Chief Financial Officer’s direction to procurement was unambiguous: consolidate the estate, eliminate duplicated entitlements, and build a single forward-looking contract aligned to the FUE-denominated S/4HANA target architecture.
At stake was approximately eighty million dollars in five-year licence spend if the renewal were taken on existing trajectory, set against a target of consolidating into a single master with negotiated tier breaks and growth caps.
SAP’s opening position on the consolidation discussion was to offer a five-year RISE conversion on indicative pricing, with credits applied against the existing licence pool calculated at a baseline conversion ratio of approximately seventy-two named users to one Full Use Equivalent. The proposal carried a twelve per cent annual price uplift, a minimum-commitment floor across the five years, and a transitional support arrangement on the legacy contracts.
The headline number on the proposal showed a five-year total contract value of approximately one hundred and forty-five million dollars, framed as a saving against the on-trajectory five-year spend of approximately one hundred and seventy million. Beneath the headline number sat four structural problems: the conversion ratio was applied uniformly across every user category, ignoring the substantial Limited Professional and Employee Self-Service populations that should convert at far higher ratios; the minimum-commitment floor included growth assumptions that the manufacturer’s headcount plan did not support; the duplicated entitlements across the five contracts were not netted; and the engine metric estimates for BW/4HANA, Process Orchestration, and the warehouse management engines were carried forward unchanged from the original measurements.
We took the engagement under a confidentiality agreement and put a twenty-two-week clock on the consolidation.
The work proceeded along four parallel tactics, each owned by a separate workstream lead and reconciled weekly against the master commercial model.
The internal USMM had classified users on the basis of role-collection assignment, producing approximately fourteen thousand Professional users across the estate. We re-ran the classification against transaction-history evidence over a twelve-month window. The corrected position was approximately eight thousand four hundred Professional users, with the balance reclassified into Limited Professional, Employee Self-Service, or removed entirely as dormant accounts. The corrected Professional figure changed the FUE conversion ratio by approximately twenty-eight per cent in the client’s favour.
Reading the five contracts side by side surfaced approximately four point one million dollars in duplicated entitlements that the consolidation had not netted. The 2013 acquisition contract carried Professional licences that overlapped with the parent group’s 2009 contract for users who had migrated to the parent’s instance years earlier. The 2017 BW/4HANA contract carried HANA runtime entitlements duplicated against the parent agreement. The duplicates were itemised and removed from the consolidated baseline before conversion ratios were applied.
The BW/4HANA, Process Orchestration, and warehouse management engine measurements were re-run independently. Two of the three were materially overstated. The Process Orchestration measurement counted internal system-to-system traffic that the contract definition excluded. The warehouse management engine was measured against a unit definition that the client’s WMS configuration did not produce. The corrected engine baseline came in approximately twenty-two per cent below the figures carried in the SAP proposal.
The minimum-commitment floor was renegotiated to align with the manufacturer’s actual five-year headcount plan rather than a notional growth assumption. The annual price uplift was reduced from twelve to four point five per cent. A growth-cap clause was added providing for annual true-up at predefined unit prices, eliminating the open-ended pricing risk that the original proposal would have carried.
The five contracts were collapsed into a single master agreement at an annual contract value of eighteen point seven million dollars, against a pre-consolidation ACV of twenty-two point eight million. The eighteen per cent annual saving represents approximately twenty point five million dollars in cumulative spend reduction over the five-year term, before considering the protection against the original twelve per cent uplift.
Five protections were written into the master. The FUE conversion ratio for each user category was fixed in the contract schedule, removing the risk of SAP applying a different ratio at the next true-up. The duplicated entitlements were netted out of the baseline before the conversion. The engine measurements were carried at the corrected figures rather than the original SAP positions. A growth-cap clause set the unit price for annual true-up additions for the duration of the contract. An audit-rights clause was narrowed to a two-year cycle with sixty days’ notice and a defined data-exchange scope.
The matter closed twenty-two weeks from the start of the engagement, in time for the renewal-cycle close and the financial-year planning calendar.
The eighteen per cent on the headline was the easy number. The growth cap and the fixed conversion ratios are what we’ll be measuring in 2030.
Named-user and engine mix. We rebuild the user model against transaction evidence, reclassify against the contract definitions, and fix the conversion ratios before they are written into the schedule.
Read the brief →Settlement and remediation. We translate the optimised position into a signed master with growth-caps, fixed unit pricing, and narrowed audit-rights clauses.
Read the brief →The topic-page reference on FUE conversion ratios, RISE pricing structure, and the seventeen clauses to renegotiate at each renewal.
The analyst paper on the optimisation sequence: USMM rebuild, role rationalisation, engine reconciliation, and FUE modelling.
The reference article on consolidating multiple SAP contracts into a single FUE-denominated master, with the five most common entitlement duplications.
A parallel conversion matter where a multi-entity manufacturer rationalised its RISE conversion ratio and saved 22% over the original SAP proposal.
A named-user rebalancing matter recovering nine per cent of contract value from over-classified Professional licences.
The cluster index for thirty long-form articles on dormant cleanup, role rationalisation, bundle conversion, and engine remapping.
It is the rebuild of a multi-year commitment. Speak with a specialist before the conversion ratios are written into the contract schedule. The first conversation is at no cost and under privilege.
Contact Us →Every Wednesday. Field reports from active matters, decoded SAP communications, and what to look for in the next audit cycle. Work email only.