A ten thousand employee technology company rebaselined its IBM estate: Db2, WebSphere, and MQ entitlements matched against ILMT deployment data, sub capacity discipline restored, and the renewal negotiated on the corrected position.
A San Francisco technology company carried IBM Db2, WebSphere, and MQ entitlements accumulated through a decade of growth and one acquisition. Nobody could say how entitlements mapped to deployments.
A licensing review rebuilt that map before the renewal. The corrected position delivered a material saving and removed a latent audit exposure at the same time.
The company cut its IBM renewal materially by rebuilding the entitlement to deployment map across Db2, WebSphere, and MQ, restoring sub capacity discipline, and renewing only what the corrected baseline supported.
The estate ran under Passport Advantage with PVU and VPC metrics. The renewal proposal assumed the historical record was still true. It was not.
A renewal quote arrived with growth priced in, while engineering insisted half the middleware fleet had been containerized away. Both could not be right.
Deployment discovery showed migrated workloads still licensed, decommissioned clusters still under support, and virtualized hosts where ILMT coverage had lapsed after an infrastructure refresh.
IBM sub capacity licensing requires eligible virtualization, ILMT deployment, and retained quarterly reports. Where the tooling had lapsed, the contractual default is full capacity counting across the physical hosts. Restoring ILMT coverage collapsed that exposure back to actual consumption.
Matching entitlements to deployments left a clear surplus tranche: licenses with no workload attached, renewing support year after year. Surplus support came out of the renewal; license rights were retained where redeployment was plausible.
Three levers moved the number: surplus support removed from the renewal, sub capacity counting restored by ILMT remediation, and the renewal negotiated on the corrected baseline with the compliance posture documented.
Review findings by product family
| Product family | Finding | Action |
|---|---|---|
| Db2 | Entitlements above deployed footprint after migration | Surplus support removed at renewal |
| WebSphere | Containerized workloads double covered | Metrics rebaselined to actual deployment |
| MQ | ILMT gaps on refreshed virtual hosts | ILMT restored, sub capacity recovered |
| Estate wide | Vendor record ahead of reality | Renewal negotiated on corrected baseline |
Every correction was packaged with evidence: discovery output, ILMT reports, and entitlement records. The renewal conversation never became an argument because the baseline was not arguable.
The closing sequence was discovery, entitlement matching, ILMT remediation, surplus identification, then a renewal counter built entirely on the documented baseline.
The standard advice is to renew the IBM estate as priced and avoid drawing attention, because a licensing review might surface compliance gaps that trigger an audit. We disagree. In roughly 25 to 35 IBM licensing reviews we advised across 2024 and 2025, the estates that quietly renewed their drift carried both the surplus cost and the unmeasured exposure forward, while the estates that rebaselined first cut support 15 to 30 percent and entered later audits with evidence instead of hope. The buyer side move is to find your own gaps before IBM does, fix the cheap ones, and let the documented baseline price the renewal. Ignorance is not a defense strategy; it is deferred spend with interest.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The renewal quote priced a company we stopped being two years ago. The review introduced IBM to the company we are now.
More IBM cost analysis lives in the IBM knowledge hub and the IBM ELA renewal strategy guide.
White Paper · IBM
IBM ELA Renewal 2026 White Paper
White paper for IBM ELA renewals in 2026. Read it free.
A material renewal saving and a closed compliance gap. Surplus Db2 and WebSphere support came out of the renewal, ILMT remediation restored sub capacity counting on MQ hosts, and the renewal was negotiated on the corrected baseline.
Sub capacity licensing depends on ILMT deployment and retained quarterly reports. Without them, IBM terms default to full capacity counting across physical hosts, which can multiply the licensable footprint several times over.
Almost always. In our 2024 to 2025 reviews, 15 to 25 percent of supported entitlements showed no matching deployment, and a third of estates had ILMT gaps that created full capacity exposure on first inspection.
No. The review produces the same evidence an audit would demand, but on your timeline and with time to fix gaps cheaply. Estates that rebaselined first entered later audits with documentation instead of estimates.
Remove surplus support from the renewal, but retain license rights where redeployment is plausible. Rights without support cost nothing annually and preserve flexibility; support without deployment is pure waste.
We expected the review to find risk. It found risk and budget in the same spreadsheet, and the budget paid for everything.
Confidential consultation. No follow up sales call unless you ask for one.
PVU and VPC benchmarks, ILMT discipline patterns, renewal signals, and the buyer side moves across the IBM estate.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
