Boardroom review of an enterprise software renewal outcome
IBM

IBM ELA renewal. 25 percent saved.

The quote opened 12 percent up. The close landed 25 percent down. Every point of the swing was created before the first meeting.

Contact Us IBM Advisory
500+Enterprise clients
$2B+Under advisory
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

A European bank facing an IBM ELA renewal quoted above prior spend closed 25 percent below it, and the entire saving traced to work done before the negotiation started.

Key takeaways

  • The quote opened high: the renewal proposal landed 12 percent above prior annual spend, justified by growth and audit risk language.
  • The baseline was wrong: a PVU baseline rebuild found 18 percent of licensed volume tied to decommissioned or refreshed hardware.
  • Shelfware funded the cut: module level usage analysis surfaced sub 20 percent adoption across three product families.
  • ILMT closed the threat: remediating sub capacity gaps removed the audit pressure IBM had positioned against the renewal.
  • The close: 25 percent below prior spend on a three year term with a capped uplift and reduction rights.
  • The method generalizes: baseline rebuild, usage evidence, and audit gap closure work on any IBM ELA.

What was the bank's starting position?

The bank entered the renewal window with an ELA covering MQ, WebSphere, Db2, and security products, a quote 12 percent above prior spend, and seven months of runway. IBM's positioning paired the increase with references to estate growth and unresolved sub capacity questions.

Internally the picture was typical: entitlements scattered across Passport Advantage sites from two past acquisitions, an ILMT deployment with known gaps, and no module level usage data.

  • Scale: an eight figure annual IBM relationship across retail and investment banking units.
  • Pressure: audit language in the renewal conversation, aimed at the ILMT gaps.
  • Constraint: regulatory change programs depending on the IBM middleware estate.

Why did the bank not just negotiate the rate?

Because the quote's volume assumptions were untested. Negotiating rate on an unverified baseline would have conceded the largest variable before talks began, with IBM's own licensing terms setting the counting rules.

How did the PVU baseline rebuild change the numbers?

The rebuild compared entitlements, the quote's assumed deployment, and a fresh discovery pass, and found the quote licensed 18 percent more PVU volume than the live estate supported. Decommissioned hardware, completed consolidation, and double counted acquired entity deployments explained the gap.

  1. Entitlement reconstruction across all Passport Advantage sites, including acquired entities.
  2. Independent deployment discovery run by the bank, not waiting on IBM's data request.
  3. PVU rating verification against the current processor inventory after two refresh cycles.
  4. Module level usage measurement across the three families suspected of shelfware.

What did usage measurement add?

Three product families showed adoption under 20 percent of licensed volume. That evidence converted renewal scope from a roll forward into a redesign, worth 9 points of the eventual saving on its own.

How did the negotiation actually unfold?

The negotiation opened with the bank tabling its corrected baseline and usage evidence before responding to the quote, which reframed the conversation from a 12 percent increase to a scope redesign. ILMT remediation, completed quietly during the baseline work, removed the audit pressure in the same move.

Position movement across the negotiation

StageIBM positionBank position
OpeningPrior spend plus 12 percentCorrected baseline, minus 18 percent volume
Mid pointPlus 4 percent, audit language droppedScope redesign, three families cut
CloseMinus 25 percent, 3 year termCapped uplift, reduction rights added

What did the bank concede?

A three year commitment and a defined subscription transition for two product families IBM wanted moved. Both concessions cost little against the baseline and cap protections received.

What can other IBM customers take from this renewal?

The transferable lesson is sequence: baseline first, usage evidence second, audit gap closure in parallel, and rate negotiation last. Every point of the 25 percent saving was created before the first negotiation session, and the same sequence applies to any ELA with the ILMT conditions in play.

  • Never negotiate on the vendor's count: rebuild the PVU baseline independently, every cycle.
  • Measure adoption before renewing scope: shelfware evidence is the cheapest concession currency.
  • Close audit gaps before they are pointed at you: remediation done quietly is leverage; remediation under audit is cost.
  • Trade what the vendor values: term and transition stories bought protections worth multiples of their cost.

How long did the program take?

Seven months end to end: three for the baseline and usage work, two for remediation and strategy, two for the negotiation itself. The calendar was the budget; starting at 90 days would have surrendered most of the outcome.

Where the common advice on ELA renewals is wrong

The standard advice on big vendor renewals is to focus energy on the negotiation itself: the meetings, the escalations, the year end pressure. We disagree. In this engagement, and in roughly 12 of the 15 plus IBM renewals Fredrik Filipsson advised in 2024 to 2025, the outcome correlated with the quality of the baseline and usage evidence, not with negotiation theatrics. The buyer side move is to spend two thirds of the runway on data and one third on talking. The bank's 25 percent did not happen in a meeting room; it happened in the discovery pass that found the 18 percent volume gap.

Bank executives reviewing renewal figures in a boardroom meeting
The decisive 18 percent volume gap was found in discovery, months before IBM and the bank ever sat at the same table.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

25%
Saved against prior annual spend
18%
Quote volume above the live estate
9 pts
Of the saving funded by shelfware cuts

Source: Redress Compliance advisory engagement file, 2024 to 2025.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

  1. Reconstruct IBM entitlements across all Passport Advantage sites, including acquisitions.
  2. Run independent deployment discovery before any vendor data collection.
  3. Verify PVU ratings against the current processor inventory.
  4. Measure module level adoption across every licensed family.
  5. Remediate ILMT gaps quietly, before the renewal conversation references them.
  6. Table your corrected baseline first, and negotiate rate last.
Cover of the IBM ELA Renewal 2026 White Paper white paper from Redress Compliance

White Paper · IBM

IBM ELA Renewal 2026 White Paper

White paper for IBM ELA renewals in 2026. Read it free.

Read the white paper

Frequently asked questions

How much did the bank save on its IBM ELA renewal?

The bank closed 25 percent below prior annual spend against a quote that had opened 12 percent above it, a 37 point swing. The saving came from a corrected PVU baseline, shelfware removal, and audit gap closure completed before negotiation.

What is a PVU baseline rebuild?

A reconciliation of IBM entitlements, deployed software, and current hardware PVU ratings, run independently of the vendor. In this case it found the renewal quote assumed 18 percent more volume than the live estate supported.

How did ILMT affect the negotiation?

IBM had paired the renewal with sub capacity audit language aimed at known ILMT gaps. The bank remediated the gaps during the baseline phase, which removed the audit lever before the first negotiation session.

What did the bank give up to get the saving?

A three year term and a subscription transition for two product families. Both concessions carried low real cost against the capped uplift and seat reduction rights received in exchange.

How long should an IBM ELA renewal program run?

Seven to twelve months. This program used three months for baseline and usage work, two for remediation and strategy, and two for negotiation. Compressing the calendar surrenders the data work that creates the outcome.

Does this approach work outside banking?

Yes. The sequence, baseline rebuild, usage evidence, quiet audit remediation, rate last, is vendor specific rather than sector specific, and it transfers to any IBM ELA of material size.

Free Download

The full IBM ELA Negotiation Recommendations framework from the IBM Advisory.

The baseline rebuild method, usage evidence framework, and negotiation sequence from the engagement file.

Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.

No spam. We will only email you about this download. Privacy.
Run a software spend health check against your IBM estate in under five minutes.
Open the Tool →
25%
Saved against prior annual spend
18%
Quote volume above the live estate
9 pts
Of the saving funded by shelfware cuts

The 25 percent did not happen in a meeting room. It happened in the discovery pass that found the volume gap.

Fredrik Filipsson
Co Founder and Group CEO. Ex Oracle, IBM, SAP.
Deep Library

More on this topic.

IBM Advisory →
Enterprise agreement reference review
IBM
IBM ELA: The Buyer Guide
The full ELA structure and negotiation reference.
12 min read
Energy sector control room systems
IBM
IBM Audit Defense for Energy
The sector defense sequence against IBM audits.
8 min read
Enterprise IT office weighing support options
IBM
Third Party Support for IBM
When leaving IBM support makes sense.
8 min read
Editorial boardroom interior

The advisor your vendors do not want.

500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.

Stay ahead of IBM licensing changes.

One buyer side briefing a week. Pricing moves, audit signals, and the levers that work. No vendor spin.