The first Broadcom quote is built on your worst-case footprint
Broadcom rebuilt the VMware commercial model within months of closing: perpetual licensing ended, the catalog of point products collapsed into a few subscription bundles, and pricing moved to a per-physical-core subscription with minimum core counts per processor. The first quote routinely assumes every core in the estate rather than the cores actually running VMware, and it arrives 2 to 3 times prior cost. No VMware customer is powerless; the leverage just moved from the license type to the core count and the exit plan.
Prepared by Redress Compliance · August 9, 2026 · Broadcom advisory. Based on roughly 20 to 30 post-acquisition VMware renewals advised 2024 to 2025.
Executive summary
Perpetual ended, the catalog collapsed into bundles, and pricing moved to a per-physical-core subscription with minimum core counts.
Existing perpetual licenses keep running but Broadcom no longer sells new support on the old model, so most customers move to subscription at renewal to stay supported, and the unit is the physical core.
Not the socket or the virtual machine, with a minimum core count per processor that charges for capacity on every populated processor even on lightly used hosts.
Standalone products such as vSAN or NSX folded into VMware Cloud Foundation and vSphere Foundation, so a customer who only used vSphere is steered toward Cloud Foundation and its added storage and networking software, and the bundle, not the core rate, often drives the spike.
The first quote overstates real need by 20 to 40 percent, because it assumes the entire core estate.
Core counts in the first offer overstated the real VMware footprint by 20 to 40 percent, because per-core minimums charge for capacity on every populated processor even where VMware runs light, and estates sized for perpetual peaks now pay subscription on cores they barely use.
The counter is to measure the physical cores actually running VMware host by host, not the whole estate, and per-core pricing rewards consolidation, so a host-density project can pay for itself in licensing alone: fewer, denser hosts lower the licensed core count.
Treat the first quote as a starting position built on your worst-case footprint, then negotiate from measured reality.
Untouched renewal quotes ran 2 to 3 times prior cost, and the jump is bundling plus core counting, not just the core rate.
A perpetual estate that paid only annual support now pays a full subscription on every core, inside a bundle, at a core minimum, so opening quotes ran 2 to 3 times the prior perpetual support spend before any negotiation.
Two forces combine: per-core minimums charge for capacity on lightly used hosts, and being moved toward Cloud Foundation adds software you may already cover elsewhere.
So the two levers that reprice the baseline are counting the real cores and right-sizing the bundle to genuine need, both done before the discount conversation opens.
The credible exit moves a quote more than any volume argument, and buyers who built one cut 15 to 30 percent.
Credible alternatives now exist, Nutanix, Proxmox, Microsoft Hyper-V and public-cloud migration are genuine options for many workloads, and a costed migration plan, not a threat, is what moves a Broadcom quote.
Customers who measured actual VMware cores, right-sized the bundle and built a costed migration option cut the final number 15 to 30 percent against the opening quote.
Structure the term accordingly: shorter terms preserve flexibility while alternatives mature, and where you commit longer, secure price protection and a defined core true-down so a consolidation actually lowers cost.
The VMware commercial model, before and after Broadcom
| Dimension | Before | After Broadcom |
|---|---|---|
| License type | Perpetual plus support | Term subscription |
| Pricing unit | Per processor | Per physical core |
| Catalog | Dozens of products | Few bundles |
| Core minimum | None | Minimum per processor |
| Renewal trend | Flat support | Two to three times higher |
Broadcom closed its VMware acquisition and rebuilt the commercial model within months: perpetual ended, entitlements now renew as term subscriptions, and standalone products folded into VMware Cloud Foundation and vSphere Foundation.
Pricing moved to a per-core subscription with minimum core counts per processor, and the unit is the physical core, not the socket or the virtual machine, so estate density directly affects cost.
VMware Cloud Foundation is the full-stack bundle covering compute, storage, networking and management, the premium tier; vSphere Foundation is the lighter bundle for core virtualization and management without the full software-defined stack, the step-down when VCF is more than you need.
You can keep running existing perpetual licenses, but Broadcom no longer sells new support on the old model, so most customers move to subscription at renewal to stay supported.
The pricing mechanics sit in the Broadcom VMware pricing guide, and why the model changed in why Broadcom killed perpetual licenses.
Why the quote spikes, and the levers that cut it
- Are you paying for unused cores? Per-core minimums charge for capacity on every populated processor, even on hosts that run light VMware workloads, so estates sized for perpetual peaks now pay subscription on cores they barely use.
- Are you buying a bundle you do not need? If you only used vSphere, being moved toward Cloud Foundation adds storage and networking software you may already cover elsewhere, and the bundle, not the core rate, often drives the spike.
- Count real cores: measure the cores actually running VMware, host by host, not the whole estate, because the first offer overstates the real footprint by 20 to 40 percent.
- Right-size the bundle: match VCF or vSphere Foundation to genuine need, dropping the premium tier where the full software-defined stack is not used.
- Consolidate hosts: per-core pricing rewards density, so fewer, denser hosts lower the licensed core count and a host-density project can pay for itself in licensing alone. The perpetual options sit in the perpetual license options guide.
The Broadcom VMware negotiation guide
The core subscription math, the bundle pushback, the exit options, and the levers that move a post-Broadcom renewal.
Get the white paper →How the alternatives and the term structure work
The model is harder, but leverage returned once credible alternatives matured, so use them.
Nutanix, Proxmox, Microsoft Hyper-V and public-cloud migration are now genuine options for many workloads, and a costed migration plan, not a threat, is what moves a Broadcom quote, because Broadcom prices the renewal against the cost and risk of you leaving rather than against last year's invoice.
The credibility of the plan, not its execution, is the lever: a named platform, a funded pilot and a migration date for a defined cluster set is what changes the conversation.
Structure the term to match: shorter terms preserve flexibility while alternatives mature, and where you commit longer, secure price protection and a defined core true-down so a consolidation actually lowers cost rather than stranding a commitment.
The buyer-side sequence is to measure the physical cores actually running VMware host by host, map current product use against VCF and vSphere Foundation to pick the right bundle, model a consolidation that raises host density and lowers licensed cores.
Cost a credible migration option for at least one workload tier, challenge the opening core count and bundle in writing before discussing price, negotiate price protection and a core true-down into any multi-year term, and time the renewal so an alternative is technically proven before you commit.
The first Broadcom quote is built on your worst-case footprint, so negotiate from measured reality instead, because in our file the combination of a named platform, a funded pilot and a migration date moved quotes 25 to 40 percent while sentiment and analyst slides moved nothing.
The alternatives detail sits in Hyper-V versus VMware, Proxmox versus VMware, and the Red Hat subscription pillar.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across Broadcom VMware renewals, 2024 to 2025
Across roughly 20 to 30 VMware renewals we advised after the Broadcom acquisition between 2024 and 2025, the first quote routinely assumed every core in the estate, not the cores actually running VMware, and the common advice concedes the point.
The common advice since the acquisition is that VMware customers have no leverage and must simply absorb the increase. We disagree:
How far the first offer overstated the real VMware footprint, by assuming the entire core estate and the premium bundle rather than measured usage.
How far customers who measured actual cores, right-sized the bundle and built a costed migration option cut the final number against the opening quote.
The opening quote almost always assumed the entire core estate and the premium bundle, overstating real need by 20 to 40 percent, and untouched quotes ran 2 to 3 times prior cost before any negotiation.
Three patterns recurred: opening quotes at 2 to 3 times prior perpetual support spend, first-offer core counts overstating the real footprint by 20 to 40 percent, and customers with a credible exit plan cutting the final number 15 to 30 percent.
The buyer-side move is to treat the first quote as a starting position built on your worst-case footprint, then negotiate from measured reality with a real exit in your pocket, because the alternatives are now mature enough to be credible.
The sequence is to measure the physical cores actually running VMware, map current product use against VCF and vSphere Foundation to pick the right bundle, model a consolidation that raises density and lowers licensed cores, cost a credible migration for at least one workload tier.
Challenge the opening core count and bundle in writing before discussing price, negotiate price protection and a core true-down into any multi-year term, and time the renewal so an alternative is technically proven before you commit.
The wider library sits in the VMware practice.
Your first five moves
- Measure the physical cores actually running VMware, host by host, not the whole estate, because the first offer overstates the real footprint by 20 to 40 percent.
- Map current product use against VCF and vSphere Foundation to pick the right bundle, dropping the premium tier where the full stack is not used.
- Model a consolidation that raises host density and lowers licensed cores, because per-core pricing rewards density and a host-density project can pay for itself in licensing.
- Cost a credible migration option for at least one workload tier, a named platform, a funded pilot and a migration date, the combination that moved quotes 25 to 40 percent.
- Challenge the opening core count and bundle in writing before price, and negotiate price protection and a core true-down into any multi-year term. The VMware practice runs the renewal with you.
Frequently asked questions
What changed for VMware customers after Broadcom?
Broadcom ended VMware perpetual licensing and moved customers to term subscriptions priced per physical core, with a minimum core count per processor, while collapsing the product catalog into a few bundles led by VMware Cloud Foundation and vSphere Foundation.
Existing perpetual licenses keep running, but Broadcom no longer sells new support on the old model, so most customers move to subscription at renewal to stay supported. The unit is the core, not the socket or the virtual machine, so estate density directly affects cost.
Why did my VMware renewal quote jump so much?
Two reasons usually combine. Per-core minimums charge for capacity on every populated processor, even on hosts running light VMware workloads, and customers are often steered toward a premium bundle with software they do not need.
A perpetual estate that paid only annual support now pays a full subscription on every core, inside a bundle, at a core minimum, so untouched opening quotes ran 2 to 3 times the prior cost. The bundle and the core counting, not just the core rate, drive the spike.
How is VMware priced now?
On a per-physical-core subscription with minimum core counts per processor. The unit is the core, not the socket or the virtual machine, so estate density directly affects cost, and per-core pricing rewards consolidation because fewer, denser hosts lower the licensed core count.
VMware Cloud Foundation is the full software-defined stack at the premium rate, and vSphere Foundation is the lighter bundle for core virtualization without the full stack, the step-down when VCF is more than you need.
Are there real alternatives to VMware now?
Yes. Nutanix, Proxmox, Microsoft Hyper-V and public-cloud migration are credible for many workloads, and a costed migration plan is now a genuine negotiation lever rather than an empty threat.
Broadcom prices the renewal against the cost and risk of you leaving, not against last year's invoice, so a named platform, a funded pilot and a migration date for a defined cluster set moved quotes 25 to 40 percent in our file, while sentiment and analyst slides moved nothing.
The plan has to be real, but it does not have to be executed.
Can I keep my perpetual VMware licenses?
You can keep running them, but Broadcom no longer sells new support on the old perpetual model, so most customers move to subscription at renewal to stay supported.
Plan the estate around subscription economics and treat the perpetual base as transition leverage rather than a long-term position, because without new support the perpetual estate accrues risk over time.
The renewal is the decision point where the subscription move, the core count and the bundle are all set together.
Should I sign a multi-year Broadcom term?
Only with price protection and a defined core true-down. Otherwise a shorter term preserves flexibility while you prove an alternative and keep leverage for the next renewal.
Where you do commit longer, the price protection locks the unit rate and the core true-down means a consolidation actually lowers cost rather than stranding a commitment.
Time the renewal so an alternative is technically proven before you commit, so the multi-year term is signed from a position of measured reality and a credible exit.
