When your vendor changes — bankruptcy, acquisition and the contracts that survive.

The VMware lesson — for every vendor.

The Broadcom acquisition of VMware compressed three normally distinct risks into one event: perpetual-licence discontinuation, partner-programme restructuring, and bundle-based pricing reset. Customers who had perpetual licences found themselves without optional support paths. Customers in multi-year deals found their renewals reshaped. Customers reliant on the VMware partner ecosystem found their reseller relationships disrupted. None of these outcomes were unprecedented; what was unprecedented was the speed.

In our experience across 340+ engagements since the transition completed, the customers who fared best had two things in common: contractual continuity language that survived assignment to a successor entity, and a documented Plan B that they could begin executing inside 90 days. Neither was specific to Broadcom or VMware. The same disciplines apply to Salesforce (Slack, Tableau, MuleSoft acquisitions), Adobe (Figma attempted acquisition), and every other vendor in the enterprise stack.

Three vendor-event scenarios

Vendor disruption arrives in three patterns. Acquisition by a financially-motivated buyer is the most disruptive — the buyer extracts value through repricing, simplification and customer-segmentation. Broadcom-VMware, Thoma Bravo on multiple targets, Vista on multiple targets. Bankruptcy is rarer but more abrupt — the vendor enters administration and contracts are honoured or rejected on a court-approved basis. Strategic pivot or product end-of-life is the slowest but most common — the vendor stops investing in the product line and customers face migration costs without a forcing event.

What to negotiate before the event.

Contingency negotiation happens at the moment the contract is signed, not at the moment the disruption occurs. The clauses below are the ones that materially change customer outcome in a successor-vendor scenario, in our experience across the post-VMware, post-Slack and post-Tableau renegotiations.

• Survivorship of perpetual licences. Explicit language that perpetual licences and the right to maintain them on a security-only support tier survive any change of control or product discontinuation. This is the single most important clause and is routinely conceded by vendors at signing if asked.
• Escrow of source code or critical IP for business-critical software where alternatives are scarce. Costs $5K–25K per year; pays for itself in a single dispute.
• Data extraction rights on SaaS in standard formats, with a 12-month post-termination window. Without these, switching costs are de facto switching prohibition.
• Most-favoured-customer pricing on renewals through a defined window. Limits the post-acquisition price-reset risk.
• Assignment restriction on the customer's side — requiring vendor consent for the vendor to assign the contract without customer approval. Few vendors will accept this in full, but partial language constrains the worst outcomes.
• Step-in rights for sub-processors on critical SaaS — the customer may invoke a substitute sub-processor if the existing one becomes unavailable.
• Termination-for-convenience window on multi-year deals — typically a 30-day window 12 months in. Becomes the option-value lever during disruption.

Plan B before you need it.

Contractual protection slows the bleeding; technical contingency stops it. The disciplines below are what we ask CIO clients to fund preemptively against material vendor risk. The cost is typically 3–6% of the vendor relationship; the optionality value is asymmetric and large in the disruption scenario.

Maintain a credible alternative architecture

For every business-critical vendor, the architecture team should maintain a documented alternative design — not a working alternative, just a documented one with estimated migration cost and timeline. Reviewed annually. The discipline keeps the alternatives current and creates real optionality at renewal. VMware customers with documented Nutanix, Proxmox or hyperscaler-native designs negotiated meaningfully better Broadcom terms than those without.

Phase out single-vendor dependencies

Where two functionally equivalent vendors exist, run both at scale. Identity (Okta + Entra ID), observability (Datadog + New Relic), CDN (Cloudflare + Akamai), data warehouse (Snowflake + Databricks). The 10–15% TCO overhead buys substantial renewal leverage and disruption resilience. Single-vendor dependencies are renewable leverage points; multi-vendor postures are not.

Pre-staged migration runbooks

For top-5 vendor relationships, a one-page migration runbook stating: alternative vendor, data extraction approach, integration impact, regulatory implications, 90-day plan, 12-month plan. Refreshed annually. The runbook does not need to be detailed; it needs to be current and executable.

When the event happens — the first three months.

When a vendor disruption announcement lands, customer reaction tends to oscillate between paralysis and panic. The 90-day playbook below produces a controlled response that maximises leverage. We have run it across the VMware transition, multiple Thoma Bravo events, and post-acquisition repricings.

1. Days 1–7: Read the contracts. Pull every active contract with the disrupted vendor. Identify change-of-control language, assignment language, termination rights and renewal windows. This is fact-finding, not negotiation.
2. Days 8–21: Stop the bleed. Pause any pending true-ups, renewals or expansion orders. Communicate to the disrupted vendor that the customer is in a 90-day evaluation hold; do not commit to anything.
3. Days 22–45: Refresh the alternatives. Engage the documented alternative architecture vendors for a refreshed quote and timeline. Their pricing is at its most aggressive in this window.
4. Days 46–70: Bench the proposal. Receive the disrupted vendor's revised commercial proposal. Bench it against the alternative architecture cost. Quantify the optionality value.
5. Days 71–85: Negotiate from optionality. Use the alternative architecture quote as the floor for renewal terms. Vendors disrupted by their own ownership change are typically more flexible in the first 90 days than they will be at any subsequent point.
6. Days 86–90: Commit or move. Either land the renegotiated terms or commit to the alternative architecture migration. Indecision past 90 days transfers the leverage back to the disrupted vendor.