When a Tier-1 global bank approached us, they had five major technology renewals falling due within a six-month window: Oracle, Microsoft, SAP, Salesforce, and AWS. Their internal procurement team had begun managing each as a separate workstream. We told them that was leaving substantial money on the table — and proposed a coordinated portfolio negotiation instead.
The insight behind portfolio negotiation is straightforward but underutilised. Every major technology vendor has a commercial relationship with the others. Oracle knows you run Azure. Microsoft knows you run Salesforce. SAP knows you're evaluating cloud migration. When you negotiate these vendors sequentially, each one operates with incomplete information and limited pressure. When you negotiate them simultaneously, each vendor knows you are evaluating the entire market, commitments are being made, and the window for their deal is finite. The competitive dynamic changes.
Over twenty-two weeks, we ran five parallel negotiation tracks — one per vendor — while feeding cross-vendor intelligence into each track. The Oracle negotiation was informed by the AWS cloud migration timeline. The Microsoft negotiation was informed by the SAP roadmap. The Salesforce negotiation was informed by a ServiceNow evaluation that we had specifically structured as a competitive alternative. The cumulative savings across all five vendors: $22 million over three years, on a combined annual technology spend of approximately $24 million.
Portfolio negotiation is not just running five negotiations at once. It is engineering the competitive dynamic so that each vendor feels the presence of the others.
When Oracle's account team knows that the client is simultaneously in commercial discussions with AWS, Microsoft, SAP, and Salesforce — and that all agreements will be signed within a defined window — Oracle's account team faces genuine competitive pressure. The buyer's attention and commitment are finite. Sequential negotiations don't create this dynamic.
In this engagement, the AWS cloud migration roadmap was used directly in the Oracle negotiation: Oracle's account team knew that on-premises database workloads would migrate over three years, reducing Oracle's addressable footprint. That knowledge made Oracle willing to offer meaningful concessions to protect the remaining relationship — concessions they would not have offered if the AWS track had not been running simultaneously.
Five simultaneous negotiations requires discipline and coordination. We ran a single negotiation hub — one team, one data room, one benchmarking database — across all five tracks. The client's procurement team interfaced with us as a single point of contact, rather than managing five separate vendor relationships in parallel.
We structured all five agreements to co-terminate within a two-week window, three years out. This means the next renewal cycle can be managed as another coordinated portfolio — giving the client permanent advantage in the recurring negotiation dynamic.
"We had budgeted for four of the five renewals to be difficult and expected significant cost increases across at least two of them. The final outcome across all five — $22 million in savings against our renewal budgets — was not something any member of our team would have predicted was achievable. The coordinated approach was the difference."Group Chief Procurement Officer — Tier-1 Global Bank
Our 40-page guide to portfolio negotiation methodology: sequencing strategy, cross-vendor leverage, co-termination design, and the internal governance model for managing multiple simultaneous negotiations.
A coordinated portfolio approach consistently outperforms sequential negotiation. We identify the cross-vendor leverage points and execute all tracks simultaneously.
Tell us which vendors are due for renewal and when — we will provide an initial view of your portfolio negotiation opportunity.