Your Broadcom renewal quote is not a bill, it is an opening position. For most mid-market VMware customers that opening position now lands somewhere between two and five times the old support-and-subscription line, and it tends to arrive with a short window to respond. This guide is about what to do between the quote hitting your inbox and the day you have to sign: when to start, what is genuinely movable, how to build a counter-position, and the point at which pricing alternatives becomes your strongest lever, whether or not you ever leave VMware.
The uncomfortable truth up front: Broadcom's mid-market discounting is thin, and no amount of relationship gets you back to 2022 pricing. But "thin" is not "zero," and the customers who do best treat the renewal as a procurement exercise with real alternatives priced, not a conversation with a vendor they hope will be reasonable.
Why your old renewal playbook no longer works
Before the Broadcom acquisition closed in late 2023, a VMware renewal was mostly a formality: pay roughly 20–25% of your perpetual license cost in annual Support and Subscription (SnS), maybe negotiate a few points, move on. Three changes broke that routine, and each one removes a lever you used to rely on.
- Perpetual and SnS are gone. Since December 2023 there are no new perpetual licenses and no SnS renewals to extend. "Just renew support" is no longer an option on the table. If you want patches and support, you are buying a subscription at today's per-core pricing.
- Pricing is per core, with minimums. The meter is now every physical core in every licensed host, with a published 16-core-per-CPU floor. Some quotes also apply a larger order floor, including a 72-core figure, which is a commercial term rather than published guidance. Either way, small environments hit a price floor that has nothing to do with what they actually run. (For the full mechanics, see the licensing changes guide.)
- The bundle is bigger than what you deployed. Most quotes are for VMware Cloud Foundation (VCF) or vSphere Foundation (VVF), which bundle products such as NSX, vSAN, and Aria that you may never have run. You are being quoted a platform, not the edition you used to buy.
Put together, the renewal is no longer a discount negotiation on a familiar line item. It is a first-time purchase of a new product, priced on a new metric, under a compressed timeline. That is why walking in with last cycle's expectations is how people get blindsided. If you are still working out which of these changes produced your specific number, why your VMware renewal went up takes the increase apart change by change, so you know how much of it is new pricing and how much is a quote you should be correcting.
Start earlier than the quote wants you to
The single most common renewal mistake is starting too late. Leverage is a function of time: every option that gives you negotiating power (a competing quote, a modeled 3-year scenario, decommissioning hosts to shrink the licensed base) takes weeks to assemble. Broadcom knows this, which is why quotes often land with only 30 to 60 days of runway.
- 6 to 9 months out: Confirm your exact expiry date and any auto-renew or price-protection clauses. Inventory hosts, CPUs, and physical cores so you know your own number before Broadcom quotes theirs.
- 4 to 6 months out: Request the renewal quote early, in both VVF and VCF tiers. In parallel, get at least one managed-provider (VCSP) number and one alternative-platform number so you have market context.
- 2 to 4 months out: Model 3-year total cost, not year-one price. Decide your walk-away position and your target. Decommission or consolidate any hosts you can before the final count is locked.
- Inside 30 days: This is where leverage goes to die. Negotiating here for the first time means negotiating without a credible alternative, and Broadcom's quote becomes your only data point.
If your renewal is genuinely close and you are not ready, a short bridge term (even at a worse rate) to buy evaluation time is often better than signing a multi-year deal against a deadline. A bridge is one of several levers that sit outside the negotiation itself, alongside partial migration and managed VMware capacity; the full menu of renewal cost-reduction levers ranks them by what each one saves and what it costs you in flexibility. See the migration timeline guide for how long a real move actually takes, so you can judge how much runway you need.
What is actually negotiable, ranked
Not everything on the quote moves, and the items that move most are not the ones customers reach for first. Ranked roughly by how much money they free up:
| Lever | How much it moves | Notes |
|---|---|---|
| Bundle tier (VCF → VVF) | Largest | Dropping to VVF when you do not use NSX or vSAN at scale beats any discount percentage. The rep will push VCF, so make them justify it against what you actually deploy. |
| Core count / order minimum | Large | Decommission before the count is locked. Challenge the 72-core minimum in writing, some accounts get it reduced toward actual deployed cores. |
| A priced alternative | Large | A signed managed-provider or Nutanix quote moves the number more reliably than argument alone. |
| Term length | Moderate | Multi-year buys single-digit to low-double-digit discounts, at the cost of locking in before you have evaluated options. A 1-year bridge preserves optionality. |
| Discount percentage | Small (mid-market) | Straight percentage-off is thin for mid-market accounts. Do not build your plan around it. |
| Per-core list price | Fixed | This is not moving. Plan around the metric, not against it. |
The pattern: the biggest levers are structural (which bundle, how many cores, what alternative you can credibly walk to), not the discount line most people fixate on. Working the top two rows means knowing exactly which lines on your quote are wrong, so if you have not been through it yet, the renewal quote review reconciles a Broadcom quote line by line against your real tier, core count, and add-ons, and benchmarks the total against estates your size.
Build your counter-position before the call
Four pieces of homework turn a renewal from a take-it-or-leave-it quote into a priced comparison:
- Audit your real core count. Reconcile the cores Broadcom wants to license against what you actually have deployed and running. Retire or consolidate what you can first. Do not pay to license cores you could decommission before the renewal date.
- Get a managed VMware (VCSP) number. This is the option most customers miss. Large VMware Cloud Service Provider partners license VCF at scale and rent it back as managed capacity, so you keep vSphere, your tooling, and your VMs while stepping out of Broadcom's direct pricing. Browse the provider directory to see who plays here.
- Get one alternative-platform number. Nutanix, Proxmox, Hyper-V, or a public-cloud VMware service. You do not have to want to migrate, you have to be able to price it. Start from the comparison guide.
- Model 3-year TCO. Compare the renewal, managed VMware, and at least one alternative on a 3-year basis including hardware refresh, data center, and staff time, not just license line items. Our cost calculator does this in minutes.
When to bring alternatives into the room
Here is the part that trips people up: you do not engage alternatives because you have decided to leave. You engage them because a priced alternative is the only thing that reliably moves a Broadcom quote, and because you owe it to your budget to know the real number either way.
Timing matters. Get your competing quotes before the negotiation call, not after the renewal is signed. A managed-provider or Nutanix proposal already on the table changes the conversation from "here is our price" to "here is how your price compares." Even customers who ultimately renew with Broadcom report that the credible alternative is what got the quote to move.
Whether you want to renew smarter or leave entirely, the move is the same: get competing numbers priced early. A free assessment matches you to managed-VMware and alternative-platform options in one step, so you walk into the renewal with a counter-position instead of a question.
Renewal prep checklist
- Confirm your exact expiry date and check for auto-renew or price-protection clauses.
- Inventory hosts, CPUs, and physical cores. Know your number before Broadcom tells you theirs.
- Decommission or consolidate hosts before the licensed count is locked.
- Request quotes in both VVF and VCF tiers, and make the rep justify VCF against what you run.
- Get at least one managed-provider (VCSP) quote and one alternative-platform quote.
- Challenge the 72-core order minimum in writing.
- Model 3-year TCO, not year-one price. The calculator does it in minutes.
- Start 6+ months out. If you are late, consider a 1-year bridge over a rushed multi-year lock-in.
VMware renewal negotiation FAQ
When should I start my VMware renewal negotiation?
Start 6 to 9 months before your subscription or support expiry. Broadcom's mid-market discounting is thin, and the leverage you do have (a competing quote, a modeled 3-year scenario, time to decommission hosts) takes weeks to build. Most of your negotiating power evaporates in the final 30 days before expiry, when you no longer have time to walk.
What is actually negotiable on a Broadcom VMware quote?
The bundle tier is the biggest lever: moving from VCF to VVF when you do not use NSX or vSAN at scale moves more money than any discount percentage. The licensed base shrinks if you decommission hosts before the count is locked, any order floor above the published 16-core-per-CPU minimum is worth challenging in writing, and multi-year terms buy modest discounts. The per-core list price and the subscription-only model are effectively fixed.
Does getting alternative quotes actually help my VMware renewal?
Yes. Broadcom's discounting moves when a signed managed-provider or Nutanix proposal is already on the table. Even if you decide to renew, a real competing number is the single most effective piece of leverage, because it turns the renewal from a take-it-or-leave-it quote into a priced comparison.
Can I negotiate an order minimum above Broadcom's published 16-core floor?
Ask for the basis in writing first. Broadcom's public core-count guidance verifies the 16-core minimum per physical CPU, so treat any order floor above that, including the 72-core figure that appears on some quotes, as a commercial term for your specific transaction rather than a published rule. Ask the seller to identify it as such and to show the calculation. Some accounts have negotiated that floor down toward actual deployed cores, but it is never volunteered.