Meet Vera AI VendorBenchmark is now Vera AI, the platform named after your analyst. Same buyer side numbers, same team. See what changed →
Broadcom VMware: surviving the per-core repricing | VendorBenchmark Blog
← All posts
Vendor desk · Broadcom VMware

Broadcom VMware: surviving the per-core repricing.

Broadcom retired perpetual VMware licenses, consolidated the catalog into per-core subscription bundles, and let renewal quotes land where they may, which for many estates has been multiples of the old bill. The negotiation is winnable, but only from your own numbers. Here is how to build them, and what to do when the vendor knows you are locked in.

By , Cofounder
July 11, 2026 · 10 minute read · LinkedIn
BROADCOM VMWARE PLAYBOOK

The VMware acquisition rewrote the rules of one of enterprise IT's most entrenched relationships, and it did so on the vendor's terms. Perpetual licenses stopped being sold. The sprawling product catalog collapsed into a handful of subscription bundles, priced per core, whether or not you used everything in the bundle. Customers who had budgeted maintenance renewals discovered they were now negotiating a subscription for software they thought they owned.

It is worth being clear-eyed about why this works. Virtualization is the layer everything else stands on, migrations take years, and Broadcom knows both facts. The strategy is not subtle and does not need to be: concentrate on the largest accounts, price the bundles at what dependence will bear, and let the long tail decide whether to pay or leave. Complaining about it is a press release. Negotiating it requires the two things the strategy assumes you lack: an independent price position and a credible exit.

PART ONE

Start from your RVTools file, not their quote

The renewal quote prices the estate Broadcom thinks you have, sized generously and bundled upward. Your first move is to price the estate you actually run. The platform's VCF calculator takes the RVTools export every VMware admin can produce in minutes and does the work that turns it into a position: the real core counts by cluster, the licensing minimums applied correctly, and three priced scenarios, the estate as it is, the estate consolidated onto fewer denser hosts, and the estate after the workloads that never needed vSphere have left.

The consolidation scenario deserves emphasis because per-core pricing changed the physics of hardware planning. Under the old model, spreading workloads across many modest hosts was harmless. Under per-core subscription, every idle core on every socket is a line item, and a hardware refresh onto fewer, denser, newer hosts routinely takes a meaningful bite out of the licensable base before the negotiation even starts. You are no longer negotiating the discount alone. You are negotiating the discount times the core count, and the core count is yours to shrink.

The scenarios then get benchmarked. The library tracks the post-acquisition reality, per-core subscription net ACV from modelled VCF cohorts, against known discount bands by deal size, so you can see where quotes like yours have actually been landing rather than negotiating against a rumor.

app.vendorbenchmark.com/tooling
The optimization tooling desk, including the VMware VCF calculator that turns an RVTools export into priced scenarios
The tooling desk: RVTools export in, core sizing and three priced scenarios out, before the first Broadcom call.
THE SAME JOB, TWICE
TODAY, BY HAND
The renewal quote lands at a multiple of the old maintenance bill, pricing the estate Broadcom thinks you have, sized generously and bundled upward.
The VMware admin produces an RVTools export, and an analyst spends weeks in Excel turning it into core counts with the licensing minimums applied by hand.
The discount conversation runs on rumor, because nobody knows where per-core VCF deals like yours have actually been landing.
The walk-away is attitude, we might leave, which every Broadcom rep has heard and priced at zero.
Weeks of spreadsheet work under a renewal deadline
WITH VERA
Upload the RVTools export to the VCF calculator and get real core counts by cluster with licensing minimums applied correctly.
Read the three priced scenarios: the estate as it is, consolidated onto fewer denser hosts, and after the workloads that never needed vSphere have left.
Benchmark the quote against per-core subscription net ACV from modelled VCF cohorts and the known discount bands by deal size.
Build the funded walk-away in the credible alternative builder, migration costs attached, and run the five-move sequence from the playbook desk.
An afternoon to three priced scenarios and a benchmark
What changes: you negotiate the discount times the core count, and the core count becomes yours to shrink. Every core removed before signature is removed at 100 percent: consolidation that cuts the licensable base 20 percent on a $1.5M a year quote is $300,000 a year before the discount conversation even starts, and the funded alternative moves the rate on the cores that remain.
"You are negotiating the discount times the core count, and the core count is yours to shrink."
PART TWO

The walk away is real, partial, and slow. Price it anyway.

The uncomfortable truth is that full migration off VMware is a multi-year program, and Broadcom prices as if it knows that. The useful truth is that the walk away does not need to be total to work. It needs to be credible at the margin: the next tranche of renewal cores has somewhere else to go.

In practice that means segmenting the estate. Some workloads genuinely need vSphere's operational maturity, and paying for those is rational. But most estates carry a long tail that does not: the dev and test clusters, the stable single-purpose appliances, the workloads a hyperscaler or an alternative hypervisor would run without drama. Pricing that tail on the alternatives, with migration cost and timeline included, produces the number that changes the renewal conversation: not "we might leave," which every rep has heard, but "these 2,000 cores have a funded destination if the price does not move."

This is exactly what the credible alternative builder produces, an alternative with arithmetic instead of attitude. And because the term you sign locks the exposure, term strategy is part of the walk away: a shorter term costs more per year and buys you optionality at exactly the moment the alternatives mature. Whether that trade is worth it is a modelable question, not a gut call.

PART THREE

The renewal, in five moves

1
Measure before they do. RVTools export, real core counts, and the three scenarios, done months before the quote arrives so the quote lands on your numbers instead of defining them.
2
Fight the bundle, not just the rate. The quiet expense is paying VCF prices for estates that need a smaller bundle. Matching the bundle tier to what you actually deploy is often worth more than the discount conversation.
3
Shrink the licensable base. Host consolidation, cluster cleanup, and retiring the workloads that already left. Every core removed before signature is removed at 100 percent, which beats any discount you will negotiate.
4
Bring the funded alternative. The segmented walk away with migration costs attached, for the tranche where it is true. Credibility at the margin moves per-core rates in a way that frustration never has.
5
Protect the next cycle in writing. Renewal caps, price holds, and reduction rights at anniversary. This market's list prices have already moved once without warning. The contract is the only instrument that stops it happening to you twice.

The playbook desk packages all of it, the calculator, the benchmark, the scenario math, and the negotiation sequence, into one guided workspace, with the brief ready for the CFO who is about to ask why the virtualization line tripled.

The honest close: some estates will simply pay more than they used to, because the dependence is real and the vendor priced it. What preparation changes is how much more, on which bundle, for which cores, and with what protection at the next cycle. In a repricing this aggressive, the gap between the prepared and unprepared outcome is not a rounding error. It is the largest single saving most infrastructure budgets will see this decade.

About the author
, Cofounder, VendorBenchmark

Morten brings two decades of enterprise and software procurement, with stints across Oracle, IBM, SAP, and Salesforce shaping how he reads a deal. He has led sourcing through hundreds of renewals, from mid market order forms to nine figure global agreements, and learned that the buyers who win are the ones who walk in knowing the market. He built VendorBenchmark to make that pattern recognition repeatable.

See it in the product
How benchmarking works → Browse the use cases → Every feature → Calculate your time saved →
FREE TRIAL · FULL PLATFORM · NO CARD REQUIRED

Price your VMware renewal from your own RVTools file.

The free trial opens the benchmarking database, 1,341 benchmarks across 1,140 vendors, plus the negotiation guides, playbooks, and talking points for your own renewals. No card needed, a corporate email is all it takes.

Start your free trial → Or decode a contract free, no account
Free for 30 days, no card needed. Your data stays isolated at the database, and you can export or delete it any time.
Watch it in action
Vera AI: the three minute demo Vera AI: the three minute demo What discount should we expect? What discount should we expect? One question, every agreement One question, every agreement
Browse the full demo library →
THE VERA AI BRIEF · WEEKLY

The week in enterprise software buying, in one email.

What shipped on the platform, and the pricing and licensing moves worth knowing before your next renewal. One email a week, to your work address. Unsubscribe any time.