The Challenge
The client, a New England community and commercial bank with approximately 1,800 employees and 60 branches across Connecticut, Massachusetts, and Rhode Island, operated a substantial IBM estate. The bank relied on IBM Db2 for core banking and loan origination systems, IBM MQ for payment messaging and transaction routing, and IBM Cognos for regulatory reporting and analytics.
The bank had entered an IBM ELA seven years earlier—a volume licensing agreement intended to provide cost predictability and pricing stability across the entire IBM software portfolio. At the time of the original ELA signing, the bank's IT infrastructure was predominantly on-premises. However, during the seven-year term, the bank's digital transformation strategy shifted significant workloads to cloud platforms. The on-premises IBM software footprint declined by nearly 40 percent as the bank migrated applications to AWS and Microsoft Azure.
Despite this material change in infrastructure, the ELA terms remained frozen. The bank continued to pay support and services (S&S) charges based on the original usage baseline—essentially paying for capacity the organisation no longer used. Annual S&S compounded at 4 percent per year, meaning the bank paid increasing fees for an increasingly irrelevant on-premises footprint.
The bank's CFO recognised the issue during a budget review and engaged Redress to conduct a comprehensive IBM estate analysis. The objective was straightforward: quantify the overpayment and renegotiate the ELA to reflect current usage and cloud migration reality.
The Approach
Redress began with a full IBM software estate review, mapping every IBM product deployed across the bank's infrastructure—both on-premises and cloud environments. The analysis encompassed Db2 instances, MQ deployments, Cognos licences, and emerging IBM tools the bank had acquired during the seven-year period.
The review revealed three critical findings. First, the bank had migrated core workloads to cloud-native alternatives, reducing the on-premises IBM Db2 footprint by 40 percent. Second, the bank had implemented cloud-based BI and analytics platforms that substantially superseded IBM Cognos for reporting and compliance use cases. Third, the bank's IBM MQ deployment remained relevant for legacy payment systems but no longer required the licence capacity the original ELA assumed.
Using the revised usage baseline, Redress quantified the overpayment. The bank had paid approximately $1.4M in excess S&S charges over the seven years because the ELA baseline no longer reflected reality. Additionally, the bank continued to license IBM Cognos at full ELA pricing despite having migrated 70 percent of regulatory reporting to cloud alternatives.
Redress then structured a renegotiation strategy focused on three components: recalibrating the S&S baseline to the bank's current on-premises footprint, removing legacy Cognos licences superseded by cloud analytics platforms, and restructuring the escalation clause to cap annual increases at CPI instead of the original 4 percent compound escalation.
The bank also required flexibility for future cloud migration and M&A scenarios. Redress negotiated a cloud migration clause allowing the bank to reduce on-premises licences proportionally without penalty as cloud adoption accelerated. Additionally, M&A provisions allowed the bank to acquire or divest subsidiary licences without forcing a full ELA renegotiation.
The Outcome
The renegotiated 3-year IBM ELA delivered $3.3M in total savings, comprised of three distinct components. The S&S recalibration to the current on-premises baseline yielded $1.4M in savings by eliminating charges for capacity the bank no longer used. The removal of legacy Cognos licences and replacement with cloud-based reporting tools generated $0.9M in additional savings. The restructured escalation clause, capped at CPI instead of 4 percent annually, protected against future cost creep and generated approximately $1.0M in additional savings relative to the previous trajectory.
The new ELA reduced the bank's annual IBM spending by 38 percent. Over the new 3-year term, the bank would pay approximately $5.2M annually for IBM software and support, compared to $8.4M annually under the legacy ELA terms.
The renegotiation included flexibility provisions designed to accommodate the bank's continued cloud adoption. The ELA allowed the bank to reduce on-premises licence commitments as cloud migration progressed without triggering penalty clauses or forced renegotiation. Additionally, the agreement provided M&A entitlement provisions—critical for a regional bank in a consolidation-prone sector—allowing acquisition or divestiture of subsidiary licences within defined parameters.
Is your IBM ELA as outdated as this bank's?
We've renegotiated 50+ IBM agreements. Request a confidential estate review.Key Takeaways
ELA agreements drift when infrastructure changes. The bank's ELA reflected 2019 infrastructure decisions. By 2026, the underlying technology landscape had shifted fundamentally. Cloud migration at 40 percent of the original footprint rendered the original terms obsolete. Many organisations renew ELAs reflexively without reconsidering whether the baseline assumptions remain valid.
Escalation clauses compound quietly. The 4 percent annual escalation clause added approximately $1.0M in excess costs over the three-year period relative to a CPI-based escalator. Escalation clauses that exceed market inflation rates accumulate significant costs over multi-year agreements and deserve explicit attention during renegotiation.
Legacy software licenses persist after migrations. The bank continued to license IBM Cognos at full ELA rates despite deploying cloud-based alternatives for 70 percent of use cases. Legacy software licensing often lingers in agreements because nobody explicitly decommissions or downgrades the old tools. Renegotiations are ideal moments to eliminate zombie licences.
Cloud migration flexibility matters. The bank's renegotiation included cloud migration clauses and M&A provisions. These flexibility provisions are not standard in vendor agreements and require explicit negotiation. Regional banks frequently consolidate; renegotiated agreements should accommodate both organic cloud adoption and M&A scenarios without forced renegotiation.
Volume agreements require periodic review. The bank's seven-year refresh cycle meant critical cost control opportunities were missed for over half a decade. Best practice suggests reviewing ELAs on a biennial cadence to detect infrastructure changes, technology migrations, and escalation impacts before they compound significantly.