IBM ELA renewal at a European bank, 25 percent saved.

Tier one European bank cut IBM ELA spend twenty five percent at renewal. Eighteen million euros saved across the next three years. The mechanics translate.

A tier one European bank with five thousand IBM hosts approached the next IBM ELA renewal facing a forty percent uplift. Db2, MQ, WebSphere Application Server, and Red Hat OpenShift were all in the bundle. Independent buyer side advisory came in nine months before the renewal date.

The outcome was a twenty five percent reduction on the previous term, locked in for three years, with swap rights on the bundle and a documented drop right at the next renewal. Eighteen million euros recovered across the term.

The client and the estate

The client is a tier one European retail and corporate bank. The IBM footprint covers five thousand hosts across mainframe, x86, and OpenShift.

IBM footprint

Db2 on Power and x86, MQ on Linux, WebSphere Application Server Network Deployment, Cognos Analytics, and Red Hat OpenShift Plus.

• Db2. Two thousand cores under PVU, sub capacity claim active.
• MQ. Six hundred cores on Linux under PVU.
• WebSphere ND. Eight hundred cores under PVU.
• Cognos Analytics. Authorised user metric, two thousand authorised users.
• OpenShift Plus. Three hundred cluster cores.

Regulatory context

Tier one bank, ECB direct supervision, strict audit and resilience requirements. The renewal posture had to satisfy operational resilience as well as commercial targets.

The starting position

The renewal landed on the procurement team in the middle of the prior fiscal year. The vendor opened at a forty percent uplift over the previous term.

The vendor ask

IBM proposed a three year term at forty percent uplift, OpenShift Plus locked in, and a tighter consumption clock on Db2.

Internal position

Budget allowed flat at best. The IT director and CFO required a renewal that held flat or below in cash terms across the next three years.

The gap

The gap between the vendor ask and the budget was approximately twenty four million euros across the term. The work was to close the gap and then move below flat.

The approach over nine months

The engagement followed a documented nine month sequence. Each phase built leverage for the next.

Months one to three. Discovery

Full consumption reconciliation across every product. ILMT report verification. Cognos authorised user audit. OpenShift cluster scoping.

Months four to five. Benchmarking

Benchmarked the ELA against three comparable tier one bank IBM deals. Built the OpenShift Plus exit case against the standalone OpenShift Kubernetes Engine.

Months six to seven. Counter proposal

Submitted a counter proposal at fifteen percent below the previous term. Tied to actual consumption plus a fifteen percent growth band. Included drop and swap rights.

Months eight to nine. Close

Final negotiation closed at twenty five percent below the previous term, three year lock, with swap rights and documented drop rights at next renewal.

The bank held flat in cash terms across the next three years. The vendor saw a credible exit option for the first time. The deal closed on terms procurement could defend to the CFO.

The result

The numbers translated into hard cash savings, plus strategic flexibility on the bundle.

Cash result

Twenty five percent reduction on the previous term ELA. Eighteen million euros saved across the three year term. Operational resilience certifications maintained.

Term improvements

Swap rights across Db2, MQ, and WebSphere consumption. Drop rights at next renewal for any component used below twenty percent of allocation. Uplift cap of three percent per annum on year two and year three.

Audit posture maintained

ILMT coverage, sub capacity claim, and quarterly report cadence all held through the engagement. The renewal did not weaken the audit posture.

Lessons for other banks

The mechanics here translate to any tier one bank with a multi product IBM ELA at renewal.

Start nine months out

Discovery, benchmarking, and counter proposal all need time. Three month renewals leave money on the table.

Benchmark against comparable banks

Without a tier one comparator, the vendor sets the reasonable range. With one, the range collapses.

Build a credible exit option

OpenShift Plus moves on price when the standalone Kubernetes Engine is on the table. The exit case has to be real, not theoretical.

Suggested reading

• IBM ELA renewal strategy guide. Cross vendor reading from the wider library.
• IBM audit defense playbook. Cross vendor reading from the wider library.
• Software licensing for financial services. Cross vendor reading from the wider library.

What to do next

1. Pull the IBM ELA composition and the latest consumption report.
2. Calendar the renewal date and back up nine months for engagement start.
3. Build the actual consumption view against the contracted commit.
4. Benchmark the ELA against tier one comparators.
5. Identify exit options on any bundled OpenShift or Cloud Pak commitments.
6. Engage independent IBM advisory before the vendor proposal lands.
7. Download the IBM Audit Defense Guide for the full IBM posture.

Frequently asked questions

Is this case study a real engagement?

Yes. Tier one European bank, five thousand IBM hosts, three year ELA renewal. The client name is confidential.

How was the twenty five percent calculated?

Against the previous three year ELA total cost. Eighteen million euros saved against a baseline of seventy two million across the prior term.

Was Red Hat OpenShift included?

Yes. Red Hat OpenShift Plus was a major component of the bundle. The credible exit case on OpenShift Kubernetes Engine drove a large part of the savings.

Did ILMT stay current through the engagement?

Yes. ILMT and BigFix Inventory coverage were already current on entry. The audit posture held through the renewal cycle.

How long did the engagement run?

Nine months end to end. Three months discovery, two months benchmarking, two months counter proposal, two months close.

Could a smaller bank replicate the result?

The mechanics translate. The percentages depend on the bundle composition and the vendor relationship. A smaller bank with a tighter ELA may see ten to twenty percent savings.

Did the bank change the audit posture?

No. The audit posture was maintained throughout. The savings came from price and terms, not from changing the compliance position.

Was a regulatory review required?

Yes. The renewal was reviewed against operational resilience requirements before signature. The vendor agreed to additional resilience commitments inside the contract.