New England Community Bank. IBM ELA resized to deployed reality.

A New England community bank cut its IBM ELA renewal materially by removing unused bundle products and resizing the agreement to deployed use before signature.

Why did the bank review its IBM ELA before renewal?

Because the renewal quote assumed the bundle was being used, and nobody inside the bank could say whether that was true. The ELA had been signed years earlier for convenience, and each renewal had rolled the full bundle forward without measurement.

Community banks are exactly the profile bundle bloat targets: a small licensing function, a stable IBM core, and a renewal that arrives as an administrative task rather than a negotiation.

• Scope: every product line inside the ELA against deployment evidence.
• Method: ILMT data, deployment scans, and the Passport Advantage record.
• Goal: a renewal priced on what runs, not on what was once bundled.

What did the ELA review actually find?

The review found that a material share of the ELA value mapped to no running workload anywhere in the bank. The core estate of Db2, WebSphere, and MQ was real and properly used; the products bundled around it largely were not.

How did the bundle get so far from the deployment?

Through convenience at signature and silence at renewal. Bundles price attractively on day one, and every subsequent renewal repriced the same scope because removal required evidence nobody had assembled.

How was the ELA renewal restructured?

The renewal was rebuilt from deployment evidence, with sub capacity reporting corrected so the retained products priced on measured use. Unused components left the agreement entirely rather than surviving at a discount.

1. Present deployment evidence per bundle component before price talk.
2. Remove components with no production workload from the renewal scope.
3. Resize retained products to measured sub capacity positions.
4. Negotiate the smaller agreement as a single event with caps in writing.
5. Document the baseline so the next renewal starts from evidence.

Did IBM resist the smaller agreement?

IBM defended the bundle economics, but evidence based scope removal is hard to argue against. A component with no deployment in five years is not a discount conversation, it is a scope correction.

What was the outcome for the community bank?

The bank signed a materially smaller renewal with every running workload fully licensed and supported. The saving recurred at each subsequent renewal because the removed scope never re entered the agreement.

• Recurring saving: removed components stopped billing permanently.
• Compliance: a clean, documented sub capacity position survived the process.
• Governance: bundle re measurement is now a standing pre renewal step.

What should other mid market IBM customers take from this?

That ELA convenience has a renewal tax. The bundle that simplified procurement five years ago is the line item nobody questions today, and re measuring it is the highest yield hour a small licensing team can spend.

Where the common advice on IBM ELAs is wrong

The standard advice tells mid market customers to keep the IBM ELA because the bundle discount beats itemized pricing. We disagree when nobody has measured the bundle. In roughly 20 to 30 IBM engagements Fredrik Filipsson advised in 2024 to 2025, ELA bundles carried 15 to 35 percent of value in products with no deployment, which means the headline discount was being applied to scope that should not exist. A discounted price on an unused product is a 100 percent loss, not a saving. The buyer side move is to re measure the bundle before every renewal and let the deployment evidence decide what stays.

What the engagement data shows

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

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. List every product inside the ELA bundle and its renewal value.
2. Match each component to production deployment evidence.
3. Correct ILMT and sub capacity reporting before the quote.
4. Remove undeployed components from the renewal scope.
5. Negotiate the resized agreement as one event with written caps.
6. Make bundle re measurement a standing pre renewal control.

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

What did the IBM ELA review find at the community bank?

That a material share of the ELA value mapped to products with no running workload. The core Db2, WebSphere, and MQ estate was active; the bundled extras largely were not.

How much can an IBM ELA review save at renewal?

In our 2024 to 2025 file, re measured bundles cut renewals by 10 to 25 percent, with 15 to 35 percent of bundle value typically traced to undeployed products.

Is removing products from an IBM ELA risky?

Not when deployment evidence is solid. The risk runs the other way: renewing unmeasured scope locks another term of spend on products nobody uses.

Why do ELA bundles drift from actual deployment?

Because bundles price attractively at signature and renew by default. Removal requires evidence, and small licensing teams rarely assemble it until a review forces the question.

Did the bank keep its ELA structure after the review?

Yes, at a smaller, measured scope. The agreement form stayed; the unused components and their renewal value left.