Section I · The Brief
The fragmented portfolio
The client, a diversified conglomerate with twenty-four operating entities across financial services, real estate, infrastructure, and consumer goods, ran twenty-four separate SAP licence contracts inherited from successive acquisitions and entity formations over fifteen years. The contracts varied in size from $200,000 annual maintenance to $1.4M annual maintenance, in counter-party from SAP Singapore to SAP India to SAP Australia, and in scope from ECC-only to S/4HANA-plus-SuccessFactors-plus-Ariba.
Aggregate SAP spend across the portfolio was approximately eleven point two million dollars annually, with substantial duplication of entitlement: 28,000 named users were distributed across the entities but the contractually-purchased entitlement totalled 34,000 because no entity could draw on another’s headroom. Engine and module entitlements were similarly fragmented, with five entities holding HANA Enterprise Cloud entitlements that had been substantially under-consumed.
The brief was to design and execute a pooled-framework consolidation that consolidated the twenty-four contracts into a single conglomerate-level master agreement with entity-level adoption schedules. The objective was to release the stranded entitlement, normalise the band mix across entities, and establish a single negotiation interface with SAP for all future commercial conversations.
Section II · The Opening Claim
The stranded entitlement
The opening position was the sum of twenty-four contracted commitments. The stranded entitlement was the difference between contracted entitlement and consumed entitlement across the portfolio, with the strand spread unevenly across the entities and across the entitlement categories.
The strand broke down by category as follows.
- 6,000 stranded named users across the entity contracts (34,000 contracted, 28,000 consumed).
- 2.1 HANA Enterprise CPU cores stranded across five HANA-licensed entities.
- 4 engine modules duplicated across entities (BW, PI, Solution Manager, GRC).
- 1,200 stranded SuccessFactors employee-central seats across the HCM-licensed entities.
- $0.9M stranded annual support and maintenance against unconsumed entitlement.
Section III · The Defence
The pooled framework
We took the engagement on a strategic-renegotiation footing with explicit board-level authorisation for the consolidation. The design phase modelled the pooled framework as a master agreement with entity-level adoption schedules, allowing each entity to draw entitlement from the conglomerate pool against its operational consumption while preserving the entity-level operational autonomy.
The negotiation with SAP ran across three layers. The first layer was the contractual consolidation: SAP’s preference would have been to retain twenty-four separate contracts, and the conglomerate’s position was that pooled-framework licensing was a documented SAP product offering under the Enterprise Agreement structure. The contractual framework was negotiated against the SAP-published Enterprise Agreement template with conglomerate-specific schedules.
The second layer was the entitlement-pool migration. The 34,000-named-user contracted entitlement was rebased to a single pooled commitment of 30,000 users, with the 4,000-user reduction reflecting the elimination of the entitlement strand and a 2,000-user buffer for organic growth. The pooled HANA Enterprise CPU entitlement was rebased from a fragmented five-entity total to a single conglomerate commitment with cross-entity reallocation rights.
The third layer was the commercial structure. The pooled framework was negotiated at a blended unit cost below the prior fragmented average, reflecting the volume and the consolidation premium. The three-year cost across the pooled framework was modelled at four point eight million dollars annually against the fragmented baseline of eleven point two million dollars — a fifty-seven percent reduction.
- Master agreement structured on SAP’s published Enterprise Agreement template
- Twenty-four entity-level adoption schedules with cross-entity reallocation rights
- Pooled named-user entitlement of 30,000 against 34,000 fragmented baseline
- Pooled HANA Enterprise CPU with cross-entity reallocation across five legacy entities
- Single-signature governance with conglomerate-level negotiation interface
Section IV · The Settlement
The signed framework
The pooled framework was signed at a three-year total commitment of fourteen point four million dollars against the prior fragmented three-year total of thirty-three point six million dollars — a six point four million dollar annual saving and a fifty-seven percent reduction. The pooled entitlement was assigned to the conglomerate parent with adoption schedules executed at each operating entity.
The contract language secured three forward protections. First, the cross-entity reallocation rights were contractually documented, allowing entities to draw entitlement from the conglomerate pool against operational consumption without renegotiation. Second, the pooled entitlement included an annual reconciliation methodology that prevented the strand from re-accumulating at entity level. Third, future M&A activity was provided for under a new-entity adoption clause that allowed acquired entities to join the pooled framework on the contractual unit cost.
Total elapsed time from design to single-signature was twenty-eight weeks. The pooled framework now governs the full SAP estate across the twenty-four operating entities with a single negotiation interface for all future commercial conversations.
Section V · Lessons Applicable
What others can use
Five takeaways from the matter that apply to any organisation with a fragmented SAP licence portfolio.
- The Enterprise Agreement template is a documented SAP product offering. Conglomerates with multiple entity contracts can consolidate to a single master agreement under the published EA framework.
- The strand is the saving. The difference between contracted and consumed entitlement across a fragmented portfolio is typically fifteen to twenty-five percent of the total contracted commitment.
- Cross-entity reallocation rights are negotiable. The default Enterprise Agreement template restricts reallocation; the conglomerate-specific schedules can document broader reallocation rights as a commercial term.
- Annual reconciliation prevents re-strand. The pooled framework releases the strand at consolidation; only the reconciliation methodology prevents it from re-accumulating at entity level.
- M&A adoption clauses preserve the unit cost. A new-entity adoption clause locks the contractual unit cost for acquired entities and removes the negotiation-overhead drag on future acquisitions.
