Bundles ended line item negotiation by design, and opening quotes landed 2 to 3 times prior maintenance
Bundles raise the revenue floor per customer and make line item negotiation harder. That is the design intent rather than a side effect, and it means a buyer response built around removing SKUs from a quote has nothing left to remove.
Prepared by Redress Compliance · August 16, 2026 · Broadcom VMware advisory. 25 to 35 renewals advised, 2024 to 2025.
Executive summary
The catalogue collapsed on purpose. Dozens of standalone SKUs became VMware Cloud Foundation and vSphere Foundation, which raises the revenue floor per customer and removes the lines a buyer used to strike out.
Support stopped being a separate maintenance line, riding inside the subscription instead, which is why comparing a renewal against old maintenance looks so violent.
Opening quotes landed 2 to 3 times prior maintenance spend before any core scrub or tier review, in the renewals we advised.
The moves that survived all operate at estate level: core scrub, tier fit, and a funded exit for part of the footprint. A funded exit on even 20 percent of the estate closed deals 25 to 40 percent below the opening quote.
The old model against the Broadcom model
Every dimension changed at once, which is why a like for like comparison against the previous renewal is misleading in both directions.
| Dimension | Pre acquisition | Under Broadcom |
|---|---|---|
| Licence type | Perpetual plus support maintenance | Subscription term only |
| Metric | Per CPU, core caps varied | Per core, 16 core minimum per CPU |
| Portfolio | Dozens of standalone SKUs | VCF and vVF bundles plus few add ons |
| Support | Separate maintenance line | Rides inside the subscription |
| Renewal posture | Maintenance roll forward | Repriced commit at term end |
How the per core minimum actually computes. Subscriptions meter every physical core on hosts running the software, and each CPU bills at least sixteen cores even when it carries fewer. A two socket host with 12 core CPUs therefore licenses 32 cores, not 24. Hyperthreading does not change the count; sockets and cores do. Hosts in a cluster running VMware workloads license fully, including failover capacity, which is where oversized standby estates turn into a permanent line.
The levers that still work, and the one that stopped
- Line item negotiation stopped working, because there are no longer line items to negotiate. Bundles were designed to raise the revenue floor and make SKU level argument impossible, so a response built on striking products from a quote has nothing to strike.
- Scrub the core inventory before the quote. Counts ran 15 to 30 percent above the live footprint once decommissioned hosts, clusters no longer running VMware, and oversized failover capacity were removed. A pre quote scrub of the RVTools export against the live estate is the cheapest saving available.
- Fit the tier rather than chasing the discount, because paying VCF rates where vSphere Foundation covers the feature use wastes more than any discount recovers.
- Fund an exit for a defined portion of the estate. Buyers who tabled a funded, dated alternative for even 20 percent of the footprint closed 25 to 40 percent below the opening quote.
- Check who you are actually negotiating with. Channel economics changed, with smaller accounts moved to authorised partners for the Broadcom portfolio, so the counterparty can change even when the price list does not.
- Use licence portability to avoid double licensing during a migration, since the same subscription follows workloads to supported clouds. It does not lower the price, it removes one excuse for paying twice.
The VMware alternatives brief
The exit architecture, the tier by tier migration math, and the costed alternative that resets a Broadcom renewal.
Get the brief →The bundle is not packaging, it is a negotiation strategy
It is tempting to read the collapse from dozens of VMware SKUs into two bundles as portfolio tidying, and Broadcom presents it that way. It is more usefully read as a negotiation design. A long SKU list gives a buyer somewhere to go: strike the products you do not use, question the ones you barely use, and assemble a quote around the components that matter. Two bundles remove that entirely. There is no line to delete, no component to defer, and no partial purchase to propose, which means the revenue floor per customer rises without a single rate changing.
Folding support inside the subscription does the same work from the other direction. Under the old model, maintenance was a separate, visible, roll forward line, and the annual conversation was about its uplift. Now there is no maintenance line at all, and the renewal presents as a single repriced commitment. This is why the comparison looks so violent: buyers are measuring a full licence repurchase against what used to be a support renewal, and finding a 2 to 3 times gap that no discount conversation was ever going to close.
What follows is that the buyer response has to move up a level, from the SKU to the estate. Three moves survive the redesign and all three change the quantity rather than the rate. Scrubbing the core inventory works because counts ran 15 to 30 percent above the live footprint, carrying decommissioned hosts, clusters that no longer run VMware, and oversized failover capacity. Tier fit works because paying VCF rates for vSphere Foundation workloads wastes more than any discount recovers. And a funded exit works because it is the only input the account team cannot model from your footprint alone; buyers who tabled one for even 20 percent of the estate closed 25 to 40 percent below the opening number.
One quieter change deserves a place in the plan. Channel economics moved, with smaller accounts routed to authorised partners for the Broadcom portfolio, so who you negotiate with can change even where the price list does not. Establish the counterparty and their margin position before you build the strategy, because a partner and a direct team respond to different levers. The per core arithmetic is worked in the 2026 cost breakdown, the conversion economics in perpetual against subscription, and the wider library sits in the VMware practice.
- RVTools in, core sizing out: three pricing scenarios across discount bands
- Your quote benchmarked against real closed Broadcom deals, not survey data
- Exit and alternative scenarios priced so you negotiate with a credible walkaway
What the renewals showed, 2024 to 2025
Across roughly 25 to 35 VMware renewals advised, the first subscription quote was the shock event of the buyer's year:
How far core inventories ran above the live VMware footprint once decommissioned hosts and dead clusters were removed.
How far below the opening quote buyers closed when they tabled a funded, dated alternative for even a fifth of the estate.
Opening quotes landed 2 to 3 times above prior maintenance spend before any core scrub or tier review, which is the number that arrives before any of the work has been done. It is not the number the estate has to finish at.
The 2026 packaging moves tightened the structure further: VCF absorbed more of the advanced services, licence portability between on premises and supported clouds firmed up, and minimum commit expectations rose for direct enterprise accounts.
Watch the briefing · 4:29How Broadcom Sells: The Five Patterns to Expect at the TableThe bundle framing and the quote sequence that arrive with every Broadcom renewal.
Your first five moves
- Scrub the RVTools export against the live estate and remove decommissioned hosts, clusters no longer running VMware, and oversized failover capacity before any quote is drawn.
- Compute the licensed count properly, applying the 16 core minimum per CPU and counting failover capacity in clusters that run VMware workloads.
- Measure feature use against the vVF scope and only accept VCF where the components are genuinely deployed.
- Fund and date an exit for a defined 20 percent of the estate, because that is the input the account team cannot derive from your footprint.
- Establish who your counterparty is, direct team or authorised partner, before building the strategy. The Broadcom practice runs the scrub and the tier review with you.
Frequently asked questions
What changed in the VMware licensing model under Broadcom?
Broadcom ended perpetual licensing and sells subscription bundles priced per physical core with a 16 core minimum per CPU. The portfolio consolidated around VMware Cloud Foundation with vSphere Foundation as the smaller estate option, and support now rides inside the subscription rather than sitting as a separate maintenance line.
Why can we no longer negotiate line by line?
Because there are no longer meaningful lines. Bundles raise the revenue floor per customer and make SKU level argument harder, which is the design intent rather than a side effect. The buyer response has to work at estate level: core count, tier fit, and a funded alternative.
How does the 16 core minimum compute?
Every CPU bills at sixteen cores or its actual core count, whichever is higher. A two socket host with 12 core CPUs licenses 32 cores rather than 24. Hyperthreading does not change the count, sockets and cores do, and hosts in a cluster running VMware workloads license fully including failover capacity.
Where do core counts usually go wrong?
On decommissioned hosts still sitting in the inventory export, on clusters that no longer run VMware, and on oversized failover capacity. Counts ran 15 to 30 percent above the live footprint in the renewals we advised, which makes a pre quote scrub the cheapest saving available.
How big is the first quote likely to be?
Opening quotes landed 2 to 3 times prior maintenance spend before any core scrub or tier review. That gap is partly structural, because support used to be a separate line and is now inside the subscription, so the renewal compares a licence repurchase against what was a support renewal.
Does a partial exit really move the number?
Yes. Buyers who tabled a funded, dated alternative for even 20 percent of the estate closed 25 to 40 percent below the opening quote. It works because it is the one input the account team cannot model from your footprint, unlike core count and tier fit which they can already see.
Did the channel change who we negotiate with?
For many accounts, yes. Smaller accounts moved to authorised partners for the Broadcom portfolio, so the counterparty can change even when the price list does not. Establish whether you are dealing with a direct team or a partner before building the strategy, because they respond to different levers.
Does licence portability lower the price?
No, it removes an excuse. The same subscription can follow workloads to supported clouds, which helps hybrid estates and stops double licensing during a migration. Treat it as a constraint you no longer have rather than as a discount you have gained.
The VMware Estate After the Repackaging
Part 2 of the Negotiating Broadcom series. Two bundles, per core with a sixteen core floor, three year terms paid up front, and a support horizon in October 2027 that decides your timing more than your renewal date does. What the estate actually looks like now, and which numbers are real.
