A VMware renewal quote under Broadcom is a starting position, not a fixed cost. The model changed, but the negotiation did not disappear. Buyers who count their own cores accurately, choose the right bundle, and bring a costed alternative to the table reset the number Broadcom calls best and final. This playbook lays out the per-core subscription math, the bundle decision between VMware Cloud Foundation and vSphere Foundation, the core count audit, a 150-day renewal timeline, and the exit options that keep your costs honest.
The reason these renewals feel immovable is that the seller controls the framing. Broadcom presents the bundle, the core count, and the multi-year term as a package. You can take that package apart. Everything below is about putting the buyer back in possession of the facts before the conversation starts.
How Broadcom builds a VMware quote
Broadcom acquired VMware in late 2023 and rebuilt the commercial model within months. Perpetual licenses are gone for new purchases. Most standalone products, including standalone vSphere editions and many add-ons, were folded into two main bundles. Pricing moved from per-CPU to per-core subscription, billed annually across a one, three, or five year term.
The quote you receive is assembled from three numbers: the bundle edition, the total core count Broadcom attributes to your hosts, and the term. Each of those is negotiable or correctable, and each is usually set in Broadcom's favor on the first pass. The account team works to its own quarter and fiscal-year targets and has more room to move than the opening figure suggests.
The minimum commitment and the channel shift
Two changes beyond pricing reshaped how VMware is bought. Broadcom narrowed the partner program and introduced minimum purchase thresholds that affect smaller estates more than large ones. A buyer who once held a modest deployment through a familiar reseller may now face a higher floor and a different route to purchase.
The minimum subscription size matters because it sets the smallest deal Broadcom will write. Estates below that floor are pushed to buy more cores than they run, to consolidate, or to look elsewhere. If your true need sits under the threshold, that gap is itself a negotiation point, and in some cases a reason to evaluate a different platform for part of the estate.
The channel change also affects who carries your account. Confirm early which partner or Broadcom team owns your renewal, because the relationship and the discount authority may have moved since your last purchase. A buyer who assumes continuity can lose weeks discovering that the contact and the process changed.
Plan for both. Know your true core requirement against the current minimum, and confirm the purchase route before the renewal window opens. Surprises in either area cost time you would rather spend on the commercial terms.
Per-core subscription mechanics
VMware subscriptions are now priced per physical core, with a minimum of 16 cores charged per physical CPU. A processor with fewer than 16 active cores is still counted as 16. A processor with more than 16 cores is counted at its actual core count. This single rule reshapes which hardware is economic to license.
The practical effect is that older, low-core-count servers carry a hidden penalty, while consolidating workloads onto fewer, denser hosts can lower the licensed core total. The table below shows how the minimum changes the effective count for common configurations.
| Host configuration | Physical cores | Cores charged | Effect |
|---|---|---|---|
| 2 CPUs, 8 cores each | 16 | 32 | Minimum doubles the charge |
| 2 CPUs, 16 cores each | 32 | 32 | No penalty at the threshold |
| 2 CPUs, 24 cores each | 48 | 48 | Charged at actual cores |
| 2 CPUs, 12 cores each | 24 | 32 | Minimum adds 8 phantom cores |
Before you accept any core total, confirm it against your own configuration management data. Decommissioned hosts, lab clusters, and disaster recovery nodes that no longer run production are commonly left in the count. Each removed host with two CPUs saves at least 32 charged cores.
The minimum also changes hardware refresh economics. When a server reaches end of life, replacing two low-core sockets with newer high-density CPUs can hold the same compute capacity on fewer licensed cores once the per-CPU floor is taken into account. Model the licensed core total alongside the hardware cost rather than treating them as separate decisions. A refresh that looks neutral on capacity can lower the subscription, and a refresh that adds sockets can quietly raise it.
The levers that move a Broadcom deal
Discount is one lever among several. Buyers who negotiate only on the headline percentage leave the structural value on the table. Use these in sequence, starting with the ones that cost Broadcom the least to give and protect you the most.
| Lever | What it does | When it works best |
|---|---|---|
| 1. Core count accuracy | Strip inactive hosts and phantom cores from the quote | Always, before any pricing talk |
| 2. Bundle right-sizing | Move from VCF to VVF where the full stack is unused | When vSAN, NSX, and Aria are not deployed |
| 3. Term length | Trade a longer commit for a deeper discount and price hold | When your roadmap is stable for three years |
| 4. Price cap | Cap renewal uplift for the full term in writing | Always; uncapped uplift is the quiet cost |
| 5. Ramp and co-termination | Align contracts and phase growth into the commit | When multiple agreements renew apart |
| 6. Migration alternative | Bring a costed exit to reset the anchor | When a second platform is viable |
| 7. Support continuity | Protect support for licenses during transition | When you plan a partial migration |
| 8. Discount | The headline percentage, last | After every structural term is set |
The order matters. If you spend your negotiating room on discount first, you have nothing left to trade for the price cap or the bundle change, which are worth more over a three-year term than a few extra points off list.
Facing a VMware renewal in the next two quarters? Our advisors run this playbook with you.
Software Licensing AdvisoryVCF and VVF: choosing the right bundle
Broadcom sells VMware mainly through two bundles. VMware Cloud Foundation, or VCF, is the full private cloud stack: compute, storage through vSAN, networking through NSX, and management through Aria. VMware vSphere Foundation, or VVF, is the smaller bundle aimed at compute and basic management, with a capped vSAN entitlement rather than the full software-defined storage layer.
The account default leans toward VCF because it carries the higher per-core price. Many estates run vSphere for compute, use external or array-based storage, and have never deployed NSX or the full Aria suite. Those estates are paying for capability they do not use when they accept VCF.
| Capability | vSphere Foundation | Cloud Foundation |
|---|---|---|
| Compute virtualization | Included | Included |
| vSAN storage | Capped per-core entitlement | Full entitlement |
| NSX networking | Not included | Included |
| Aria management suite | Limited | Full |
| Best fit | Compute estates on external storage | Full private cloud stack in use |
The core count audit
The fastest saving in most VMware renewals is an accurate core count, not a discount. Broadcom prices on the cores you license, so every host you remove and every workload you consolidate reduces the bill directly. Run this audit before you respond to a quote.
Start from your own inventory rather than the vendor's figure. Pull the physical CPU and core layout of every host in every cluster, then separate production from non-production, retired, and standby capacity. Identify low-core-count hosts that trigger the 16-core minimum and model whether consolidation onto denser servers lowers the licensed total. Confirm which clusters genuinely need the bundle and which could move to a smaller edition.
The outcome is a defensible core number you own. When Broadcom quotes a higher figure, you can show the difference line by line rather than arguing in the abstract.
The 150-day renewal timeline
A negotiating position is built, not found. By the time Broadcom sends a renewal quote, the buyers who do well have already done the work. This is the timeline we run.
| Days before renewal | What to do | Why |
|---|---|---|
| 150 to 120 | Build an independent host, core, and feature inventory | You cannot negotiate what you cannot measure |
| 120 to 90 | Decide the bundle and model the right-sized core count | Set the configuration before pricing starts |
| 90 to 60 | Cost at least one migration alternative end to end | An alternative is the source of real bargaining power |
| 60 to 30 | Open the commercial talk with your structure first | Anchor on your terms, not the quote |
| 30 to 10 | Press for the price cap, term, and support continuity | Protect the terms that compound over the deal |
| 10 to 0 | Close at quarter end where the timing helps you | Timing pressure works in the buyer's favor |
Exit options and migration alternatives
An exit option you have actually costed is the strongest lever a VMware buyer holds. You do not need to migrate to benefit from it. A credible, board-ready alternative changes the anchor of the conversation, because Broadcom prices differently against a customer who can leave than against one who cannot.
The realistic alternatives vary in maturity, operational fit, and migration cost. Hypervisor choice is only part of the picture; management, storage, networking, and backup integration all carry switching cost. Scope a representative cluster, not the whole estate, to produce a defensible number.
| Alternative | Profile | Main consideration |
|---|---|---|
| Microsoft Hyper-V | Mature, often already licensed via Windows Server | Feature parity for advanced storage and networking |
| Nutanix AHV | Hyperconverged platform with built-in management | Hardware and licensing model change |
| Proxmox VE | Open source, low licensing cost | Enterprise support and operational maturity |
| Red Hat OpenShift Virtualization | Container and VM platform on Kubernetes | Skills and architectural shift |
Sequence the alternative properly. A migration that targets the easiest workloads first, such as test, development, and non-critical production, builds operational confidence and a real cost record without betting the core estate. That phased path is also the most credible thing to put in front of Broadcom, because it shows a route you have already started rather than a threat you cannot execute.
Most enterprises that run this analysis decide to stay on VMware for a defined period while building optionality. That is a reasonable outcome. The value is in arriving at the renewal with a number that proves you could move, which is what disciplines the quote.
Want an independent read on your VMware renewal and a costed alternative? Talk to our advisors.
Book a 30 minute callContract terms that protect the deal
The pricing number is not the whole negotiation. The terms around it decide what the deal costs in years two and three. Three terms deserve attention on every VMware subscription.
First, the renewal price cap. Subscription pricing makes year-end uplift the quiet cost of the deal, so cap the increase in writing for the full term and at the first renewal. Second, the term and ramp. A longer term can earn a deeper discount, but only commit to growth you can foresee, and phase increases rather than buying ahead of need. Third, support continuity for any perpetual licenses you still run, since those lose support when the contract lapses, which is the pressure point Broadcom uses at renewal.
Two further clauses repay the effort to negotiate them. A reduction right, even a limited one, lets you lower the committed core count at renewal if your estate shrinks through consolidation or migration, so growth is not the only direction the contract allows. And clear definitions matter: confirm exactly how cores are counted, how the bundle entitlements are measured, and what triggers a true-up, so a later disagreement turns on agreed language rather than the vendor's reading. Precise terms today prevent an expensive interpretation fight in year two.
Reading a Broadcom quote line by line
Most VMware buyers receive the quote as a single price and react to the total. The buyers who do well break it into its parts and test each one. A quote has four components worth checking before any negotiation begins: the bundle edition, the core count, the term, and the support and uplift terms attached to it.
Start with the bundle line. Confirm whether you are being quoted VMware Cloud Foundation or vSphere Foundation, and whether any add-on SKUs sit on top. If the quote assumes VCF, ask what in your estate requires the full stack. If the answer is nothing concrete, the bundle line is your first correction.
Move to the core count. The quote should name the hosts and the cores per host. Match that against your own inventory. Look for retired hosts, standby capacity that no longer runs production, and any CPU counted at the 16-core minimum that could be consolidated. The core count is usually where the largest correction lives.
Then read the term and the uplift language. A three-year term may carry a deeper discount, but check whether the per-core price is held flat across all three years or whether year two and year three carry an increase. An uncapped uplift in the contract is a future cost that the headline discount hides.
Common mistakes that inflate a VMware renewal
The same errors recur across renewals, and each one adds cost that a buyer could have avoided. Knowing them in advance is part of the preparation.
The first mistake is accepting the vendor core count without an independent check. Inventory drifts, hosts are retired without being removed from records, and the quote often reflects the estate as it was at the last true-up rather than today. A current count almost always comes in lower.
The second mistake is buying VMware Cloud Foundation by default. The full stack is the premium product, and many estates that run only compute and basic storage are paying for vSAN at full entitlement, NSX, and Aria capabilities they never enabled. The edition should follow usage, not the account team's preference.
The third mistake is starting late. A renewal opened 30 days before expiry leaves no time to audit cores, model a bundle change, or cost an alternative. The buyer arrives with no position and accepts the quote because the clock has run out. The fourth mistake is negotiating discount first and spending the available room before the cap and the term are settled.
The fifth mistake is ignoring perpetual licenses still in the estate. Those licenses keep running, but they lose support when the contract lapses, and Broadcom uses that gap as pressure to convert everything to subscription at once. Knowing which workloads can run unsupported for a defined period preserves choice.
What a good outcome looks like
A strong VMware renewal is not only a lower headline number. It is a deal where the configuration matches real usage, the price is protected across the term, and the buyer keeps the freedom to change course later. Several outcomes signal that the negotiation went well.
The core count on the contract reflects the estate as it actually runs, with retired and standby capacity removed. The bundle matches the features in use, so you are not paying for the full private cloud stack to run compute. The per-core price is held flat for the full term, and the first renewal carries a capped uplift rather than an open increase.
The term fits your planning horizon, with growth phased rather than bought in advance. Support continuity is protected for any perpetual licenses you keep, so a partial migration stays possible. And a costed alternative sits in your file, ready to inform the next renewal even if you chose to stay this time.
Across more than 500 enterprise engagements, the buyers our firm advises have negotiated over $2.4 billion in software contracts, with average savings of 38 percent. The durable value in a VMware renewal usually comes from the structure, the cap, and the right-sized configuration, not from the discount alone.
Want these outcomes on your VMware renewal? Start with an independent review.
Software Licensing AdvisoryKey takeaways
- The first Broadcom quote is built to be moved. Prepare 150 days out.
- Audit your own core count before discussing price. Remove inactive hosts.
- Choose VVF over VCF when the full stack is not in use.
- Watch the 16-core-per-CPU minimum on low-core-count hosts.
- Cost a migration alternative even if you intend to stay.
- Win the price cap and term flexibility before the discount.
- Protect support continuity for any perpetual licenses still running.
Frequently asked questions
Why did our VMware renewal increase so much under Broadcom?
Broadcom retired perpetual licenses and most standalone products, moving customers to per-core subscriptions sold mainly as VMware Cloud Foundation and vSphere Foundation bundles. The bundle plus a per-CPU core minimum often raises the effective price even when your usage is unchanged.
What is the per-core minimum on VMware subscriptions?
Broadcom applies a minimum of 16 cores per physical CPU for subscription licensing. A CPU with fewer than 16 active cores is still counted as 16, so low-core-count hosts inflate the subscription unless you consolidate onto denser servers.
Should we buy VMware Cloud Foundation or vSphere Foundation?
Choose VMware Cloud Foundation only when you use the full stack, including vSAN, NSX, and Aria. Many estates run compute and storage that vSphere Foundation covers at a lower per-core price. Map enabled features before accepting the larger bundle.
Can we still buy perpetual VMware licenses?
No. Broadcom moved VMware to subscription only and stopped selling new perpetual licenses. Existing perpetual licenses still run, but they no longer receive support once your support contract lapses, which is the pressure point at renewal.
What are the realistic alternatives to VMware?
Common alternatives include Microsoft Hyper-V, Nutanix AHV, Proxmox VE, and Red Hat OpenShift Virtualization. Migration cost and operational risk vary, but a costed alternative is what resets a Broadcom quote even when you choose to stay.
Get this playbook applied to your contract. Confidential assessment within one business day.
Book a 30 minute callRelated reading: our software licensing advisory service, our cloud contract negotiation practice, and the VMware and Broadcom vendor profile. See also our ranking of the top software negotiation consulting firms.