A tier-one European bank was approaching five major renewals — Oracle, Microsoft, SAP, IBM, and Salesforce — within an eighteen-month window. The CIO suspected that negotiating each one in isolation was leaving leverage on the table. We ran the five tracks as a single coordinated programme, sequenced the renewals to amplify pressure, and documented $22M of saving against status-quo trajectories.
The bank's vendor management team had a problem of arithmetic. Within an eighteen-month window, Oracle's database ULA, the Microsoft EA, the SAP ECC support extension, IBM's mainframe MLC, and a Salesforce Service Cloud renewal would all hit signature. Five different sourcing leads, five sets of account teams, five timing trajectories — each well-handled in isolation, but no one was looking at the portfolio.
When we mapped the renewals against the bank's overall IT operating budget, the answer was sobering. The five vendors together accounted for 61% of software spend. Each renewal contained at least one ratchet clause indexed to the same compliance or true-up signal. And four of the five had bundled product attaches that the previous renewal cycle had introduced quietly. Nobody was running a portfolio view because nobody was being measured on one.
In our experience across 340+ engagements, vendor account teams are trained to defend share-of-wallet against a single counterparty's renewal calendar. They are not built to defend it against a customer running a portfolio programme. The same person who negotiated the Oracle ULA is comparing Oracle's terms against IBM's, the Microsoft EA against Salesforce's, and the SAP run-rate against everything. The vendor cannot see the comparisons. The customer can.
You probably have more leverage than you are using.
We restructured the certification position before exit. Three product families excluded, ULA converted to a sized perpetual entitlement at 64% of Oracle's proposed conversion value. $7.4M saved.
Modelled the bank's E5 footprint against actual feature usage on 18,400 seats. Negotiated a structured step-down of 2,200 over-licensed E5 seats at the first anniversary, plus Copilot pricing locked at pre-list rates. $4.8M saved.
Held ECC support through year three of the extension at 2.5% maintenance index rather than the proposed 4.5%. Negotiated S/4HANA migration credits as right-to-buy not commitment. $3.6M saved.
Replaced peak monthly licence charge with a tailored fixed-monthly licence charge structure across the workload portfolio. Sub-capacity pricing aligned to actual MSU consumption. $3.9M saved over the three-year term.
Removed Data Cloud bundle the bank had never activated. Renewed flat across 6,800 seats. Step-down on overprovisioned licences scheduled at month 24. $2.3M saved.
Most enterprises run renewals as ten or twenty separate procurement projects in a year. Each has a different sponsor, a different deadline, a different team. The vendors know this — their account plans are built around the customer's fragmentation. The single most under-used lever for any large enterprise is portfolio coordination: stop one or two renewals from going dormant; sequence the others; share data across the negotiation team; force the vendor account directors to compete with each other for the customer's renewal budget.
If you are approaching two or more major renewals within twelve months, the work to coordinate them needs to start before any individual conversation. The Multi-Vendor Negotiation Strategy paper walks through the sequencing logic in detail.
The sequencing framework used on this programme.
Our partners have led portfolio programmes for nine of the world's twenty largest banks. We can scope a single coordinated track across your vendor estate.
Weekly compliance intelligence for IT leaders.
