This case study is part of our IBM Licensing Case Studies series. A prominent New England financial bank engaged Redress Compliance to conduct a comprehensive review of its IBM Enterprise Licence Agreement ahead of renewal. The bank's IBM estate supported core banking transactions, customer relationship management, regulatory compliance, and fraud detection across retail, commercial, and wealth management divisions. For broader guidance, see our IBM Licensing Knowledge Hub and the IBM ELA Renewal Service.
1. The Challenge: A Complex IBM Estate Approaching ELA Renewal
The bank was one of New England's leading financial institutions, operating retail banking, commercial lending, wealth management, and insurance services across the northeastern United States. Its IBM technology estate had grown over 18 years through successive ELA renewals, acquisitions, and technology refreshes, each adding products and entitlements without a corresponding rationalisation of what was no longer needed. The result was a licensing portfolio that bore little resemblance to the bank's actual technology requirements.
Db2 powered the core banking system, customer data platform, and regulatory reporting databases. WebSphere Application Server supported the online banking portal, mobile banking platform, and API gateway for third-party integrations. MQ messaging connected the CBS to downstream systems including ATM networks, card processing, SWIFT interfaces, and the Federal Reserve's FedLine system. IBM Security products (Guardium, QRadar, Identity Governance) provided the data protection, threat monitoring, and access management required by federal banking regulators. IBM SPSS and Cognos supported risk modelling, regulatory stress testing, and management reporting.
With the ELA renewal approaching in six months, the bank faced several interconnected challenges. The existing ELA included products the bank no longer used, products that had been replaced by third-party alternatives, and entitlements misaligned with actual deployment levels. There were unidentified compliance gaps that could trigger audit exposure. And IBM's renewal proposal would almost certainly attempt to lock the bank into a larger, more expensive agreement without addressing the underlying waste.
Leading Regional Bank
One of New England's largest financial institutions with retail banking, commercial lending, wealth management, and insurance services. Regulated by the OCC, FDIC, and Federal Reserve with stringent technology governance requirements.
18-Year IBM Relationship
Multiple ELA renewals, acquisitions, and technology refreshes had accumulated an IBM estate of 40+ products and product variants across Db2, WebSphere, MQ, Security, SPSS, Cognos, and legacy middleware. Many no longer aligned with the bank's actual technology strategy.
Significant Annual IBM Spend
The bank's annual IBM expenditure exceeded USD 18 million across ELA fees, Passport Advantage maintenance, and subscription services, making it one of IBM's larger financial services accounts in the Northeast.
Six-Month Renewal Window
The ELA renewal deadline created urgency. IBM was already engaging the bank's procurement team with renewal proposals that assumed continuation of the existing product portfolio at increased pricing, before the bank had established its actual requirements.
2. Understanding IBM ELA Dynamics in Banking
IBM Enterprise Licence Agreements in the financial services sector follow predictable patterns that consistently favour IBM's revenue objectives over the customer's actual needs. Understanding these dynamics is essential to achieving a renewal outcome that reflects genuine business requirements rather than IBM's sales targets.
Portfolio Accumulation Without Rationalisation
Each successive ELA renewal adds products to address the bank's evolving needs, but rarely removes products that are no longer required. Over 18 years, this accumulation creates an agreement stuffed with legacy middleware, obsolete analytics tools, and products that have been replaced by third-party or open-source alternatives. IBM benefits from this bloat because the bank's annual maintenance and ELA fees include support for products it no longer uses.
Entitlement Misalignment Masked by ELA Coverage
ELAs provide unlimited deployment rights for covered products during the agreement term. This unlimited deployment masks underlying entitlement problems: if the bank deploys significantly more than the ELA's certified quantity, the excess becomes a compliance exposure at renewal. Conversely, products that the bank barely uses are included at full cost. Without an independent deployment assessment, the bank cannot determine which products are genuinely needed.
Renewal Proposals That Anchor High
IBM's standard renewal approach presents a proposal based on the existing ELA footprint plus anticipated growth, typically 10 to 20% above the current agreement cost. This high anchor creates a negotiation dynamic where the bank feels it is "winning" by negotiating IBM down to a 5 to 10% increase, when the correct starting point might be a 25 to 30% reduction based on actual usage.
3. Our Approach: Comprehensive ELA Review and Renewal Strategy
We structured the engagement across four phases designed to establish the bank's actual IBM licensing position, identify every optimisation opportunity, remediate compliance risks, and negotiate a renewal from a position of complete information rather than IBM's framing.
Licensing Review and Compliance Assessment (Weeks 1–4)
Full audit of the bank's IBM licensing position: every agreement, entitlement, deployment, and configuration across all environments. Analysed 18 years of ELA agreements, amendments, and Passport Advantage records. Deployed ILMT-based measurement across all virtualised environments to establish accurate PVU consumption. Mapped every IBM product installation to its corresponding entitlement and identified compliance gaps where deployments exceeded entitlements.
Optimisation and Shelfware Identification (Weeks 4–7)
Mapped the bank's actual usage against its licensed portfolio to identify every category of waste, overprovisioning, and misalignment. Identified products with zero or minimal active usage (shelfware), products replaced by third-party alternatives but remaining in the ELA, entitlements exceeding actual deployment by significant margins, and product editions that could be downgraded to lower-cost alternatives.
ELA Scope Definition and Strategy (Weeks 7–9)
Working with the bank's CIO, CTO, and procurement leadership, defined the target ELA scope: which products were mission-critical and required continued coverage, which could be excluded, and what future licensing needs the bank should plan for based on its technology roadmap. Developed a detailed negotiation strategy with specific pricing targets, contractual terms, and fallback positions for every product category.
ELA Negotiation (Weeks 9–12)
Led the negotiation with IBM, presenting the bank's optimised position backed by independently verified deployment data. Combined the licensing review findings (demonstrating IBM's over-bundled proposal), the optimisation analysis (quantifying shelfware costs), competitive market intelligence (documenting available alternatives), and compliance remediation (framing the bank's proactive approach as a reason for favourable terms).
4. Eliminating Unused Licences: USD 4.5 Million Annual Savings
The licensing review revealed that a substantial portion of the bank's IBM estate was shelfware: products included in the ELA that the bank was paying for but not using, or using at a fraction of the licensed capacity. Eliminating this waste was the single largest source of savings.
Legacy Analytics and Reporting: USD 1.8 Million
IBM SPSS Modeler and SPSS Statistics were licensed across 200+ seats but actively used by only 35 analysts. The bank's data science team had migrated to Python and R-based toolchains three years earlier. Cognos Analytics was licensed enterprise-wide but used only by a small regulatory reporting team; the bank's primary BI platform had shifted to Tableau. These unused analytics entitlements accounted for approximately USD 1.8 million in annual ELA costs.
Middleware Overprovisioning: USD 1.6 Million
WebSphere Application Server Network Deployment was licensed at 8,400 PVUs, but actual sub-capacity consumption was 3,200 PVUs, a 62% overprovisioning driven by the previous ELA's uncritical rollover of historical entitlements. MQ Advanced was similarly overprovisioned at 2,800 PVUs versus 1,600 actual usage. Rightsizing middleware to actual consumption freed approximately USD 1.6 million annually.
Security Product Duplication: USD 1.1 Million
The bank had acquired a dedicated SIEM platform (Splunk) two years prior but retained QRadar SIEM entitlements in the ELA. Similarly, the bank had implemented CyberArk for privileged access management alongside IBM Security Identity Governance. Both IBM Security products were being maintained at full ELA cost despite having been operationally replaced. Removing these duplicated security products saved approximately USD 1.1 million annually.
Shelfware Elimination: USD 4.5 Million Annual Savings. Before review, the bank's ELA included 40+ IBM products and product variants, many accumulated over 18 years without rationalisation. Our analysis mapped every product against actual usage data: ILMT sub-capacity measurements, server deployment scans, user access logs, and application monitoring data. The analysis revealed that approximately 35% of the bank's IBM licensing spend was directed at products with zero or minimal active usage. Legacy analytics (USD 1.8M), middleware overprovisioning (USD 1.6M), and duplicated security products (USD 1.1M) were excluded from the renewed ELA.
5. Retiring Redundant Solutions: USD 1.2 Million Annual Savings
Beyond outright shelfware, the review identified IBM products that were still technically in use but performed functions that were better served by existing third-party investments or could be consolidated into other IBM products the bank was retaining.
IBM DataStage Replaced by Cloud-Native ETL: USD 480K
The bank had begun migrating data integration workloads to AWS Glue and Informatica Cloud as part of its cloud transformation programme. DataStage remained licensed for legacy batch ETL processes that were being decommissioned. Accelerating the migration timeline and excluding DataStage from the renewed ELA saved approximately USD 480,000 annually.
Lotus Domino/Notes to Microsoft 365: USD 320K
Approximately 1,200 users remained on Lotus Notes for legacy workflow applications that had not yet been migrated to the bank's Microsoft 365 environment. A 90-day migration plan moved these workflows to SharePoint and Power Automate, enabling the exclusion of Domino/Notes from the renewed ELA at approximately USD 320,000 annual savings.
IBM Content Manager to Box: USD 240K
The bank had adopted Box for enterprise content management but retained IBM Content Manager for legacy document archives. These archives could be migrated to Box at minimal cost, removing the Content Manager entitlement at approximately USD 240,000 annual savings.
Tivoli Monitoring Consolidated: USD 160K
Several Tivoli Monitoring components were still licensed despite the bank's adoption of Dynatrace as its primary APM platform. Removing the remaining Tivoli entitlements saved approximately USD 160,000 annually.
6. Compliance Remediation: Closing Gaps Before IBM Found Them
The licensing review also identified compliance gaps that, if left unaddressed, would have exposed the bank to significant audit risk. Remediating these gaps proactively, before the ELA renewal and before IBM could discover them in a future audit, was both a risk mitigation measure and a negotiation advantage.
Db2 Sub-Capacity Shortfall
The bank's core banking Db2 deployment had grown beyond the ELA's certified PVU quantity through organic expansion. Actual sub-capacity consumption was approximately 15% above the licensed level, a gap that would have resulted in an IBM audit claim of approximately USD 2.8 million at list pricing. We incorporated the true-up into the ELA renewal at negotiated pricing, resolving the compliance gap at a fraction of the audit exposure cost.
MQ Deployment in Acquired Entity
A 2021 acquisition had brought additional MQ deployments into the bank's environment that were not covered by the existing ELA. These deployments supported the acquired entity's payment processing and were operationally integrated but never formally added to the bank's IBM licensing. The gap represented approximately USD 1.4 million in audit exposure. We included these deployments in the renewed ELA at a fraction of standalone licensing cost.
Proactive Remediation as Negotiation Leverage
By identifying and resolving compliance gaps before renewal, the bank demonstrated to IBM that it was approaching the relationship with full transparency and commitment to compliance. This proactive posture, combined with the bank's significant ongoing investment in IBM core products, provided the commercial context for IBM to offer favourable renewal terms rather than treating compliance remediation as an incremental cost event.
7. ELA Renewal Negotiation: 28% Cost Reduction
Armed with a complete picture of the bank's actual IBM position, optimised deployment data, identified shelfware, retired redundancies, and remediated compliance gaps, we entered structured negotiations with IBM over three weeks. The negotiation was built on information asymmetry reversal: the bank now understood its IBM position better than IBM's own account team did.
IBM's initial renewal proposal had increased the ELA cost by 12% above the existing agreement, citing "market pricing adjustments" and "expanded product access." Our counter-position, backed by independently verified data, demonstrated that the correct starting point was a 28% reduction based on the optimised product portfolio.
Data-Driven Product Scope
We presented our deployment analysis showing exactly which products the bank used, at what levels, and which could be excluded. IBM could not credibly argue for the inclusion of products we had demonstrated the bank was not using. This shifted the negotiation from IBM's "everything-in" renewal proposal to a surgically defined product portfolio matching actual requirements.
Competitive Alternatives Documentation
For every product category where credible alternatives existed, analytics (Python/R, Tableau), security (Splunk, CyberArk), ETL (AWS Glue, Informatica), content management (Box), we documented the bank's existing investments and migration readiness. This was not a bluff; the bank had already begun migrating several workloads. IBM understood that aggressive pricing on retained products was essential to preventing further attrition.
Scalable Terms for Regulatory Growth
The bank's Db2, MQ, and Guardium deployments would likely grow due to regulatory requirements (enhanced stress testing, expanded transaction monitoring, new data privacy mandates). We negotiated growth bands that allowed the bank to expand capacity for these mission-critical products at pre-agreed pricing, 25% below IBM's standard incremental pricing, eliminating the risk of mid-term cost surprises driven by regulatory compliance.
| Category | IBM Proposal | Negotiated Outcome | Impact |
|---|---|---|---|
| Shelfware Elimination | Included at full cost | Excluded from ELA | USD 4.5M savings |
| Redundant Solution Retirement | Included at full cost | Excluded from ELA | USD 1.2M savings |
| Compliance Remediation | USD 4.2M at list | Included in ELA renewal | ~75% below list |
| ELA Renewal Pricing | +12% above existing | −28% below existing | 40-point swing |
| Growth Bands | Standard incremental | Pre-agreed at 25% discount | Cost predictability |
"Redress Compliance's IBM ELA review was a transformative experience. Their insights helped us ensure compliance, optimise our licensing, and secure a cost-effective agreement. Their support has positioned us to navigate the future with confidence."
CIO, New England Financial Bank
8. Governance Implementation: Sustaining the Optimised Position
The renewed ELA represented a fundamentally restructured IBM relationship. To sustain the optimised position and prevent the gradual accumulation of shelfware that had characterised the previous 18 years, we implemented a governance framework designed for the bank's specific operational and regulatory context.
Continuous Usage Monitoring
Deployed ILMT-based monitoring integrated with the bank's CMDB and application portfolio management tools. Real-time visibility into IBM product usage at the PVU level, automated alerting when consumption approached licensed thresholds, and quarterly usage-versus-entitlement reports for procurement and technology leadership. The monitoring framework ensured that new compliance gaps could not develop undetected.
ELA Product Review Process
Established an annual IBM product portfolio review linked to the bank's technology strategy planning cycle. This review assessed every licensed product against actual usage, evaluated whether third-party alternatives had made any IBM product redundant, and maintained an up-to-date roadmap of products to exclude at the next renewal. This process ensured the bank would never again accumulate 18 years of unreviewed product bloat.
Acquisition Integration Protocol
The 2021 acquisition's MQ licensing gap demonstrated the risk of bringing new IBM deployments into the bank's environment without licensing reconciliation. Established a 60-day integration protocol requiring IBM licensing assessment for any acquired entity, immediate entitlement mapping against the existing ELA, and formal true-up or ELA amendment if additional products exceeded coverage.
Procurement and Technology Training
Delivered training for the bank's procurement, enterprise architecture, and infrastructure teams covering IBM licensing models, sub-capacity rules, ELA terms and obligations, and the relationship between deployment decisions and licensing costs. This training ensured that future technology decisions were made with licensing cost awareness from the outset.
9. Key Lessons: What Every Bank Should Learn Before an IBM ELA Renewal
Shelfware Is the Largest Hidden Cost
Approximately 35% of this bank's IBM spend was shelfware, products accumulated over 18 years of renewals that nobody was using. Without an independent usage assessment, this waste is invisible because ELA coverage masks it. Every bank approaching an IBM ELA renewal should commission an independent licensing review at least six months before the renewal deadline.
Third-Party Migrations Create ELA Opportunities
Banks continuously adopt new technologies that replace IBM products: Splunk for QRadar, CyberArk for Identity Governance, Tableau for Cognos, AWS Glue for DataStage. Each migration creates an opportunity to remove the replaced IBM product from the ELA. However, most banks fail to translate their technology migrations into ELA cost reductions because the procurement team managing the IBM relationship is not connected to the technology decisions being made elsewhere.
Compliance Gaps Hide Under ELA Coverage
ELA coverage provides unlimited deployment rights during the agreement term, masking underlying compliance gaps. When the ELA expires or is restructured, these gaps become exposed. Identifying and remediating them before renewal transforms a potential audit liability into a negotiation advantage, demonstrating the bank's proactive compliance posture and incorporating remediation into the renewal economics.
IBM's Renewal Proposals Always Anchor High
IBM's initial proposal increased the ELA cost by 12% in this engagement. The actual correct position was a 28% reduction. This 40-point gap between IBM's anchor and the optimised outcome is typical. Banks that negotiate without independently verified deployment data are negotiating blind, and IBM's account teams are trained to exploit that information asymmetry.
Acquisitions Create Licensing Liabilities
The 2021 acquisition brought USD 1.4 million in unrecognised IBM licensing exposure. Every bank with an active M&A programme should include IBM licensing assessment in its integration protocol. The cost of proactive assessment is negligible compared to the audit exposure from undocumented deployments.
Independent Advisory Reverses the Information Asymmetry
IBM's account team has deep knowledge of the bank's licensing position, historical agreements, and commercial leverage. Without independent advisory, the bank negotiates with less information about its own position than IBM has. Our review gave the bank complete visibility for the first time in 18 years, transforming the negotiation from IBM's framing to the bank's verified requirements.
10. Why Independent Advisory Transforms IBM ELA Renewal Outcomes
IBM ELA renewals for financial institutions involve tens of millions of dollars in annual spend, decades of accumulated entitlements, and licensing complexity that spans virtualisation, cloud migration, security compliance, and regulatory growth. IBM's account teams are incentivised to maximise renewal value; the bank's procurement team, however skilled, rarely has the specialised IBM licensing expertise needed to counter this incentive structure effectively.
In this engagement, the bank's internal teams lacked the specialised expertise needed to conduct a product-level usage assessment with ILMT-based verification, identify which ELA products were shelfware versus genuinely required, detect compliance gaps that ELA coverage had been masking, quantify the specific cost impact of each optimisation opportunity, and negotiate from independently verified data rather than IBM's framing. The difference was a 40-point swing: from IBM's +12% renewal proposal to our −28% outcome.
IBM Licensing Expertise for Banking
Redress Compliance's team includes former IBM licensing professionals who understand ELA structures, sub-capacity rules, product bundling, and the specific IBM products used in banking, from Db2 core banking deployments to Guardium regulatory compliance monitoring. This expertise enables a depth of licensing analysis that general IT advisory firms cannot replicate.
Negotiation Intelligence
We bring current market intelligence on IBM commercial terms, pricing benchmarks, and the specific negotiation strategies IBM deploys during ELA renewals for financial institutions. This intelligence ensures the bank negotiates with full awareness of what IBM is willing to concede and where its real pricing floors lie, not the artificial floors presented in IBM's initial proposals.
Complete Vendor Independence
Redress Compliance has no commercial relationship with IBM: no partner status, no resale revenue, no referral commissions. Our recommendations on which products to retain, which to exclude, and what commercial terms to target are based exclusively on the bank's interests. This independence is particularly important in ELA renewals, where advisory firms with IBM partnerships may recommend retaining products that serve their vendor relationship rather than their client.
"Most financial institutions are overpaying for their IBM ELAs by 25 to 40%. The combination of accumulated shelfware, undetected third-party replacements, compliance gaps masked by ELA coverage, and IBM's high-anchor renewal strategy means that banks negotiate renewals based on IBM's framing rather than their own verified requirements. Independent ELA review reverses this dynamic entirely."
Redress Compliance IBM Advisory Team
Frequently Asked Questions
An IBM ELA is a multi-year licensing agreement that provides an organisation with deployment rights for a defined portfolio of IBM products, typically at a bundled price lower than purchasing each product individually. ELAs are structured around certified quantities and usually include maintenance and support. Banks use ELAs to simplify procurement and achieve volume pricing. However, ELAs accumulate products over successive renewals, and without regular review, organisations frequently pay for products they no longer use.
In our experience with financial services ELA reviews, banks typically identify savings of 20 to 40% of their annual IBM spend. The primary sources are shelfware elimination, redundant solution retirement, middleware rightsizing, and improved renewal pricing through data-driven negotiation. This bank achieved USD 5.7 million in annual savings and a 28% ELA cost reduction, well within the typical range for a comprehensive review.
We recommend beginning an independent ELA review at least 6 to 9 months before the renewal deadline. This allows time for a thorough licensing assessment (3 to 4 weeks), usage analysis and optimisation (3 to 4 weeks), scope definition and strategy (2 to 3 weeks), and negotiation (2 to 4 weeks). Starting later compresses the timeline and reduces the bank's ability to implement product retirements before the renewal, limiting achievable savings.
The most common sources we identify are: legacy analytics tools (SPSS, Cognos) where the bank has migrated to Python/R, Tableau, or Power BI; security products (QRadar, Identity Governance) replaced by Splunk, CyberArk, or SailPoint; legacy middleware (Lotus Notes, Content Manager, Tivoli) replaced by Microsoft 365, Box, or Dynatrace; and middleware overprovisioning (WebSphere and MQ licensed at quantities 40 to 60% above actual sub-capacity consumption). In aggregate, these typically account for 25 to 40% of a bank's total IBM ELA spend.
Yes, and this is one of the most valuable aspects of conducting a pre-renewal review. Compliance gaps discovered proactively can be incorporated into the ELA renewal at negotiated pricing, typically 60 to 80% below the list pricing IBM would demand if the same gaps were discovered during a formal audit. Additionally, demonstrating proactive compliance provides commercial goodwill that strengthens the bank's overall negotiating position.
If an ELA expires without renewal, the bank retains entitlements to the certified quantities established at the most recent ELA certification. However, the bank loses the unlimited deployment rights that ELA coverage provides, meaning any deployments above the certified quantities become compliance gaps. The bank would also transition to Passport Advantage maintenance pricing, which is typically more expensive than ELA-bundled support. This is why pre-renewal review is critical: it ensures the bank understands its true licensing position regardless of whether it renews or exits the ELA.
No. Redress Compliance is a 100% independent advisory firm with no commercial relationship with IBM or any other software vendor. We do not resell IBM licences, hold IBM partner status, or earn referral commissions. This complete independence ensures our ELA review findings and negotiation recommendations are exclusively aligned with the bank's interests, not influenced by any IBM partnership obligations.