A North American insurance group entered the engagement with an IBM Enterprise License Agreement up for renewal and an Account team proposing a flat carry-forward at the same product set. After eleven weeks the group renewed at materially reduced scope, exited two product families that had moved to alternatives, and locked sub-capacity PVU rules into the contract instead of leaving them as policy.
The client's IBM ELA had grown over three renewal cycles. Two product families — an integration suite and a legacy data product — had been replaced over the previous eighteen months. Internal owners for those products had moved on. ILMT compliance had drifted in the same period.
The proposal preserved the full product mix at a 7% uplift and offered to convert one product family into a Cloud Pak entitlement at favourable internal rates.
A Cloud Pak conversion that is funded by the carry-forward of two retired product families is not a saving. It is a re-priced commitment to something the client has already decided to move away from.
The work split into four parallel tracks, all converging on the position paper for round three.
We worked with the IBM SAM team and platform engineering to close the ILMT reporting gap before round one. Without ILMT compliance, sub-capacity was off the table and the negotiating position was weaker.
We documented the two retired product families with deployment evidence, replacement-platform contracts and an internal decommissioning record. The evidence package became the basis for exiting them at renewal.
We modelled the proposed Cloud Pak conversion against actual workload roadmap. Three of the five included products were not in the workload plan. The Cloud Pak became a smaller, scoped commitment rather than a carry-forward of legacy.
The sub-capacity rules sat in IBM policy, not in the contract. We negotiated them into the renewed ELA as contractual terms with a defined remediation window if reporting gaps recur.
An IBM ELA renewal is rarely a price negotiation. It is a scope and structure negotiation, with ILMT compliance as the floor underneath. Once the scope is right, the price follows.
The renewed ELA carried three product families instead of five, included a scoped Cloud Pak entitlement tied to a documented workload roadmap, brought sub-capacity terms inside the contract, and replaced the policy-based ILMT remediation language with a contractual window.
Tell us the renewal date and the product families in scope. We will respond within one business day with the lead and the most relevant precedent.