A FTSE 100 industrial conglomerate with £4.2 billion in annual revenue engaged specialist advisory to rationalise its enterprise software estate across six major vendors simultaneously. The 18-month programme delivered $22 million in verified savings through coordinated negotiations, licence optimisation, and strategic cross-vendor leverage.
This is what structured advisory looks like.
Start 9 months out. Every week of lead time is leverage recovered.
A FTSE 100 industrial conglomerate operating across manufacturing, energy, and infrastructure sectors had an enterprise software estate that had grown organically over 15 years through organic expansion and acquisitions. The organisation's annual software spend exceeded $76 million, with Oracle, Microsoft, SAP, Salesforce, AWS, and VMware representing the six largest vendor relationships. The CIO had initiated a cost reduction programme and identified enterprise software as a priority, having received renewal proposals that collectively represented a $8.3 million increase on the prior year's spend.
Rather than running six separate procurement exercises, the CPO commissioned a coordinated multi-vendor advisory engagement. The objective was to treat the enterprise software estate as a portfolio — where leverage in one vendor negotiation could be amplified by decisions made in another — rather than as a series of disconnected transactions. The organisation engaged a multi-vendor negotiation specialist through the BestNegotiationFirms advisory process.
Editorial note: All client details have been anonymised. Savings figures represent the difference between vendor renewal proposals and executed contract values, verified by the client's finance team. For context on multi-vendor negotiation frameworks, see our IT contract negotiation strategy guide.
The advisory team structured the engagement as an 18-month programme with three overlapping phases and a dedicated programme management function coordinating all six vendor workstreams:
A full inventory of all software contracts, licences, usage data, and renewal dates was compiled across all six vendors. A renewal calendar was constructed identifying optimal negotiation timing, and cross-vendor dependencies were mapped — particularly where decisions on Oracle cloud migration, SAP S/4HANA, and Azure commitments interacted.
Six vendor workstreams were run simultaneously, with information from each negotiation informing the others. Oracle's pricing benchmarks were used in SAP renewal discussions. AWS EDP negotiations were timed to coincide with Azure MACC discussions, creating genuine multi-cloud optionality that neither hyperscaler could ignore.
Post-negotiation, the advisory team established a software asset management framework and renewal governance calendar to ensure the savings were maintained and the organisation was positioned for subsequent renewal cycles. A vendor management office structure was designed to preserve the institutional knowledge built during the programme.
The programme delivered savings across all six vendor relationships, with the distribution reflecting both the size of each vendor's spend and the specific optimisation opportunities identified:
| Vendor | Annual Spend | Key Levers | 3-Year Savings | Reduction |
|---|---|---|---|---|
| Oracle | $18.4M | ELA restructure, Java SE, ULA exit, support reduction | $7.2M | 13% |
| Microsoft | $14.2M | EA true-up correction, E5 rightsizing, Azure MACC, AHB | $5.1M | 12% |
| SAP | $12.8M | Named user audit, indirect access remediation, TPS leverage | $4.4M | 11% |
| AWS | $11.6M | Savings Plans, RI optimisation, EDP negotiation, Spot migration | $2.8M | 8% |
| Salesforce | $5.4M | Shelfware reclamation, edition rightsizing, escalation cap | $1.6M | 10% |
| VMware | $4.8M | Broadcom transition extension, VCF scope reduction, AHB migration | $0.9M | 6% |
| Total | $67.2M | $22.0M | ~11% |
The most distinctive aspect of a coordinated multi-vendor programme is the ability to create leverage that single-vendor negotiations cannot access. Three cross-vendor dynamics were particularly valuable in this engagement.
First, Oracle's OCI push was used against Oracle itself. When Oracle's renewal team proposed significant OCI committed spend as a condition of the most favourable ELA discount tier, the advisory team responded with a detailed Azure equivalent architecture analysis showing that Microsoft Azure offered better economics for the conglomerate's specific workload profile. Oracle withdrew the OCI condition within two negotiating rounds. See our Oracle negotiation guide for the full OCI leverage playbook.
Second, the SAP S/4HANA migration timeline was used to create leverage in both the SAP renewal and the AWS EDP negotiation. SAP's motivation to close the renewal quickly (to secure renewal revenue before a potential S/4HANA migration decision) gave the advisory team additional flexibility on maintenance rates and indirect access remediation terms. AWS, aware that a future SAP workload migration was a possibility, made a more aggressive EDP proposal to secure the conglomerate's cloud commitment.
Third, the VMware exit planning created leverage in the Microsoft negotiation. By demonstrating that VMware workloads were being assessed for Azure VMware Solution migration, the advisory team was able to accelerate Microsoft's MACC offer and increase the Azure Hybrid Benefit commitment, which in turn reduced the net Azure cost materially.
We had been managing each vendor relationship in a silo for years. The moment we started treating our $76 million software estate as a portfolio, the vendors started treating us differently too. The coordination was the strategy.
Beyond the immediate financial outcomes, the programme established a software procurement governance framework that the organisation had not previously had. A renewal calendar with 18-month lead times across all major vendor relationships, a quarterly SAM review process, and a vendor scorecard system were all implemented as outputs of the advisory programme. The vendor management guide covers the full framework for organisations looking to build these capabilities in-house.
The conglomerate also established an internal negotiation competency, with two members of the procurement team trained as lead negotiators for future cycles — reducing dependency on external advisory over time. For organisations at similar scale, our software negotiation team structure guide and our enterprise negotiation playbook provide the frameworks for building this capability.
Managing multiple vendor renewals? Coordinated advisory typically outperforms single-vendor negotiations by 2–3×.