Broadcom Support Contract Analysis

Broadcom's restructuring of VMware support contracts has been one of the more contentious aspects of the post-acquisition transition. Enterprises that previously held perpetual support agreements at predictable annual rates now face support pricing that has been re-engineered around the new subscription model, with implications that often dwarf the underlying licence cost.

This article walks through what Broadcom has done with VMware support contracts, the specific traps that catch enterprises during renewal, and the analysis framework that helps customers separate genuine support value from manufactured cost increases.

The pre-Broadcom support model

Under VMware, support was sold as Production Support or Basic Support, priced as a percentage of the perpetual licence (typically 20-25% for Production, lower for Basic). Customers paid for support annually, separately from the underlying licence, with relatively predictable year-over-year increases. The model gave enterprises clear visibility into what support cost and clear leverage to drop or downgrade support at renewal if value didn't justify cost.

Many enterprises ran sophisticated support optimisation programmes under this model: dropping support on non-critical product editions, downgrading from Production to Basic on lower-criticality workloads, or even running selected systems on a "self-support" basis using third-party providers like Spinnaker, Rimini Street, or Origina.

What Broadcom has changed

The Broadcom subscription model has bundled support into the subscription itself. There is no longer a meaningful distinction between "the licence" and "the support" — both are components of the subscription, and both are paid for through the subscription fee. Several second-order consequences follow:

Support cannot be dropped independently. Under perpetual VMware, enterprises could choose to drop support to save money while continuing to use the software (with the obvious risk of running unsupported versions). Under Broadcom subscription, dropping "support" effectively means terminating the subscription and losing the right to use the software. This removes a significant cost optimisation lever that many enterprises previously relied on.

Support tier choices have narrowed. The granular choices between Basic, Production, Premier, and Mission Critical support that VMware offered have been consolidated into a smaller number of subscription support tiers. Broadcom's default tier is functionally equivalent to old Production Support; the higher tiers are more expensive and offer marginal additional value for most customers.

Third-party support is harder. Third-party support providers — Rimini Street and similar — built their business on supporting perpetual VMware deployments. Under subscription, the underlying licence terms typically prohibit third-party support, and Broadcom has been more aggressive about enforcing those terms than VMware was. Enterprises that previously used third-party support for VMware face a more constrained set of options.

Pricing has been re-baselined. Effective support cost as a percentage of total VMware spend has increased materially. Many customers calculate that their effective support cost has gone from 20-25% of perpetual licence value to 35-45% of subscription value, even after accounting for the elimination of separate maintenance line items.

The contract analysis

Broadcom support contracts now arrive as part of the broader VMware Cloud Foundation or vSphere Foundation subscription agreement. The support terms are buried in service description documents that few customers read carefully. Several specific clauses warrant attention:

Response time commitments

Broadcom's default response time commitments are generally less stringent than VMware's were. Severity 1 response is typically still under one hour, but Severity 2 and below have been relaxed. For enterprises running mission-critical workloads on VMware, the response time degradation is a real operational risk that may justify upgrading to the higher support tier.

Escalation paths

The escalation paths within Broadcom support have changed. The named technical account manager (TAM) relationship that many enterprise VMware customers relied on is now positioned differently — it's available, but at additional cost, and the TAM resourcing model has been adjusted in ways that reduce TAM continuity.

Geographic coverage

Some Broadcom support contracts have narrower geographic coverage than the equivalent VMware contracts. Customers with global operations should verify that support coverage matches their actual operational geographies, particularly for "follow-the-sun" requirements.

Patching and version rights

The right to receive patches, security updates, and version upgrades is now coupled to active subscription status. This is consistent with the broader subscription model but has implications for enterprises that previously stayed on older VMware versions for stability reasons — those enterprises now need to maintain active subscriptions to receive critical security patches.

The renewal traps

Several renewal traps are catching enterprises during Broadcom support contract renewals:

The "co-term" trap

Broadcom is aggressively pushing co-termination of support contracts, where all VMware support across the enterprise renews on a single date. This sounds operationally convenient, but it concentrates negotiation leverage on a single annual event and makes it harder to phase renewals based on actual contract terms.

The "auto-renew" trap

Broadcom support contracts often include auto-renewal clauses with short opt-out windows. Enterprises that miss the opt-out window can find themselves locked into another full year of support at the new pricing, even if they intended to renegotiate.

The "minimum tier" trap

Broadcom has minimum support tier requirements for certain product editions. Enterprises that want to downgrade support to manage cost may find that the downgrade isn't available for their current product mix without also changing their underlying subscription, which is a much bigger commercial decision.

The "credit" trap

If your VMware support was prepaid under the old perpetual model, the credit treatment in the transition to Broadcom subscription is contractually specific. Some customers have credits that materially offset early subscription costs; others have credits that have effectively been written off in the transition. The contract terms determine the answer, and the analysis is worth doing carefully.

Negotiation strategy

The effective negotiation strategy for Broadcom support contracts has shifted. Under VMware, support was negotiated largely as a percentage of licence value. Under Broadcom, support is negotiated as part of the broader subscription commercial conversation — total contract value, term length, payment terms, ramp commitments, and bundled product mix all interact with the effective support cost.

The customers who achieve the best support outcomes negotiate the subscription holistically, with explicit attention to the support tier and escalation rights, rather than treating support as a separate downstream conversation. Multi-year commitments with locked pricing, particularly when bundled with growth commitments, produce the best effective support economics.

Working with independent advisors

Broadcom support contract analysis is exactly the kind of work where independent advisors add disproportionate value. The contract language is dense, the commercial implications are non-obvious, and the analysis benefits from comparison against a large reference base of similar engagements. — the firm we most often recommend for Broadcom defence work — runs structured support contract analysis as part of their broader engagement model, and the support-specific savings often justify the engagement cost on their own.

The third-party support question

For enterprises with significant remaining perpetual VMware deployments, third-party support remains a viable option — though more constrained than it was. Rimini Street, Spinnaker, and a small number of regional providers continue to offer VMware support for perpetual deployments. The economics can be compelling (typically 40-60% lower than Broadcom Production Support pricing), but the model only works for environments that are no longer evolving and where Broadcom-supplied patches are not strictly necessary.

For environments actively migrating to subscription or to VCF, third-party support is generally not viable. The decision is binary: stay on perpetual with third-party support and accept the limitations, or transition to Broadcom subscription with Broadcom support.

The forward view

Broadcom's commercial model for support is unlikely to liberalise. The bundling of support into subscription is structural — it eliminates a category of customer optimisation that previously reduced Broadcom's recurring revenue. Customers should plan on the basis that support cost will continue to grow in line with subscription pricing, and that the levers available to reduce support cost will continue to narrow.

The strategic response is to actively manage the subscription relationship — negotiate hard on term length, payment terms, and bundle composition; verify support tier choices against actual operational needs; and engage independent advisory support whenever the renewal value is material. Passive renewal is the most expensive option in this market.

Final thought

Support has shifted from a tactical annual decision to a strategic component of the broader Broadcom subscription relationship. Enterprises that recognise this shift early and adjust their negotiation approach accordingly are achieving meaningfully better outcomes than those who continue to treat support as a downstream renewal exercise. The work of understanding what Broadcom is actually selling — and what it is worth — is now an essential part of the VMware commercial relationship.

Frequently asked questions

Can I drop support to reduce cost under the Broadcom subscription model?

Not in the way you could under the VMware perpetual model. Under perpetual licensing, support was a separate annual contract that could be dropped while continuing to use the underlying software (with the obvious risk of unsupported running). Under the Broadcom subscription model, support is bundled into the subscription, and dropping "support" effectively terminates the right to use the software. Cost optimisation now requires reducing the subscription scope itself rather than dropping support on a maintained subscription.

What is the difference between the Broadcom support tiers?

The default subscription support tier is functionally equivalent to the historical VMware Production Support tier — 24x7 support with documented response time commitments by severity. The higher tier (variously branded as Premier or Mission Critical depending on the product family) adds named technical account manager resourcing, faster escalation paths, and additional advisory services. For most enterprises, the default tier is appropriate; the higher tier is typically warranted only for genuinely mission-critical deployments where the marginal cost is justified by operational risk reduction.

Is third-party support still viable for VMware?

For perpetual VMware deployments, third-party support providers like Rimini Street continue to offer support services at meaningful discount to Broadcom pricing. The economics work for environments that are no longer evolving and where Broadcom-supplied patches and feature updates are not strictly necessary. For subscription deployments, third-party support is generally not viable — the subscription terms typically prohibit third-party support, and Broadcom enforces those terms more actively than VMware did. The decision becomes binary: stay on perpetual with third-party support or transition to subscription with Broadcom support.

How should support credits from prepaid VMware maintenance be handled?

The credit treatment is contractually specific to each customer's situation. Some customers transitioning from VMware perpetual to Broadcom subscription have received material credits against early subscription invoices; others have had credits written off in the transition. The contract terms — specifically the transition clauses negotiated at the time of the perpetual-to-subscription conversion — determine the outcome. Customers with significant prepaid maintenance balances should have those credits explicitly addressed in any new commercial conversation with Broadcom.

What is the typical price increase from VMware support to Broadcom subscription support?

Effective support cost as a percentage of total VMware spend has increased materially in the transition. Many customers calculate that their effective support cost has gone from 20-25% of perpetual licence value to 35-45% of subscription value, even after accounting for the elimination of separate maintenance line items. The absolute number depends on the specific subscription mix and the support tier chosen, but the upward direction is consistent across most customers we have analysed.