VMware Bundle Negotiation: How to Avoid Over-Paying for VCF and VVF

The Bundle Problem: What You Are Paying For That You May Not Need

Broadcom eliminated all standalone VMware product sales in 2024. Every enterprise customer is now required to purchase either VMware Cloud Foundation (VCF) or VMware vSphere Foundation (VVF) — and in most cases Broadcom's account teams push towards VCF, which is the more expensive of the two. VCF bundles together vSphere, vSAN, NSX, Aria Suite (previously vRealize), and Tanzu components. The list price in 2026 is $140 to $180 per core per year, versus $80 to $120 for VVF which covers vSphere, vSAN, and basic lifecycle management without NSX or Aria.

The problem is structural: the bundle was designed to capture revenue from customers who previously paid only for vSphere. If your organisation does not use NSX for software-defined networking — and the majority of enterprises outside hyperscaler-scale deployments do not — you are paying for it anyway under VCF. If you have not deployed Aria Suite for operations management and automation, you are paying for it. Broadcom cannot unbundle these components in the current commercial model, but the choice between VCF and VVF is real, and many enterprises that Broadcom defaults to VCF actually qualify for and benefit from VVF.

The first tactical question in any Broadcom bundle negotiation is therefore: should we be on VCF or VVF? Getting this wrong costs a typical enterprise with 1,000 licensed cores an additional $20,000 to $60,000 per year for components that serve no business purpose. Read the full context in our Broadcom VMware Negotiation Playbook, which includes specific qualification criteria and contract language guidance.

VCF vs VVF: The Qualification Test

VVF (VMware vSphere Foundation) is the right bundle for organisations that meet all of the following criteria: their networking strategy does not involve NSX for micro-segmentation or software-defined networking at scale; they do not use Aria Suite for operations, automation, or log analytics; and they do not plan to adopt Tanzu Kubernetes workloads within the contract term. In practice, most enterprise IT teams running traditional VM-based workloads without a cloud-native transformation programme on the Broadcom stack meet these criteria.

Broadcom's account teams default to positioning VCF because of the higher revenue per core. They will often argue that VCF provides "future-proofing" — that the additional components will be needed as the organisation's infrastructure evolves. Treat this as a commercial argument, not a technical one. If NSX, Aria, and Tanzu are not in your roadmap for the current three-year contract term, they provide zero value and should not be in your licence agreement. Challenge Broadcom to document specifically which VCF-only components your team uses and intends to use, within a defined timeframe. If that documentation cannot be produced, the VCF premium is indefensible.

For organisations that do use NSX or Aria, VCF remains the appropriate bundle. The negotiation then shifts to price, term, and scope rather than bundle selection. Enterprise buyers in 2025–2026 are seeing VCF discounts of 15–30% from the initial proposal when they come to the table with competitive alternatives evaluated and documented.

The Core Count Trap: Right-Sizing Before You Renew

Since April 2025, Broadcom requires a minimum of 72 cores per CPU socket, regardless of the physical core count of that processor. An organisation running servers with 32-core CPUs must licence and pay for 72 cores per socket — more than double the physical count. This rule applies to both VCF and VVF, and it dramatically distorts the economics for organisations running modern high-density servers where per-socket physical core counts have increased substantially over the past generation of hardware.

The right-sizing exercise before any Broadcom renewal should begin with a complete inventory of your licensed estate. Using VMware RVTools or PowerCLI, extract the total number of licensed sockets, their physical core counts, and — critically — which servers are still in active production use and which are dormant, decommissioned, or scheduled for retirement within the contract term. Broadcom charges for all licensed sockets, not just those running VMs. Enterprises routinely enter renewals with 20–30% of their licensed estate no longer in active use, simply because no one cleaned up the entitlement record before the renewal was processed.

If you have hardware nearing end-of-life, negotiate the right to remove those sockets from the licensed count at no penalty rather than carrying them through a three-year term. This is a commercially reasonable request — Broadcom's account teams will resist it, but it is achievable with appropriate documentation of the decommission schedule. Similarly, if your organisation is consolidating servers through hardware refresh and your total physical core count will increase (because newer CPUs carry more cores per socket), model the impact of that consolidation on your Broadcom cost before agreeing to a per-core subscription price.

Negotiation Tactics That Work in the Current Broadcom Environment

The Broadcom negotiation dynamic has changed fundamentally since the acquisition. Channel competition no longer drives discounts: Broadcom reduced its authorised VMware partner network from over 4,500 organisations to fewer than 400, eliminating the competitive pricing pressure that historically kept renewal quotes in check. Discounts now come from four sources: volume commitment, term length, documented alternative credibility, and transition accommodation for customers still converting from perpetual to subscription agreements.

Volume and term. A three-year commitment at higher core count consistently yields better per-core pricing than a one-year agreement. If your organisation is comfortable with a three-year horizon — which requires a degree of confidence that VMware will remain in your environment through the term — negotiate the per-core rate at year three consumption levels even if you plan to reduce scope over the period. The discount from committing to volume upfront typically outweighs the cost of slight over-commitment in early years. However, ensure that any co-term or ramp provision allows you to add cores at the committed rate rather than the then-current list price, as Broadcom's standard terms include annual escalators.

Alternative credibility. The negotiators who achieve the largest discounts are those who have completed meaningful evaluation of Nutanix AHV, Azure VMware Solution, or other alternatives before walking into the renewal conversation. "We are actively evaluating Nutanix and have a proof of concept running in our non-production environment" is a different statement from "we might look at alternatives." Broadcom's account teams have seen both. The former changes the negotiation. The documentation that matters is a migration cost model with realistic professional services quotes, a POC report, and ideally board-level programme approval. See our VMware Alternatives Guide for the framework to build this credibly.

Transition accommodation. Organisations that were still on perpetual licences when Broadcom ended them may have valid claims for accommodation — extended support timelines, price normalisation in the first year, or conversion credits. Broadcom has granted these in some cases, though they are not offered proactively. Documenting the gap between your legacy contract value and the proposed subscription cost — and presenting it as a formal negotiation position rather than a complaint — is more likely to move the conversation than an informal objection.

What to Include in Your Counter-Proposal

A well-structured counter-proposal to Broadcom should address five elements: bundle selection (VCF vs VVF with documented justification), licensed core count (with decommission schedule and right-to-reduce language), term and pricing (three-year commitment at a specified per-core discount off list), escalator cap (annual price increase capped at a specified percentage, not open-ended), and alternative evaluation statement (confirming that the organisation has evaluated Nutanix and Azure VMware Solution and that the counter-proposal represents the threshold for choosing to stay with VMware). The final element is particularly important — it signals that the counter-proposal is not posturing. Broadcom's account teams respond differently to documented credibility than to verbal signals.

Redress Compliance has managed over 100 Broadcom and VMware engagements since the acquisition, achieving an average saving of 35% against Broadcom's initial proposals. We work exclusively on the buyer side — no commercial relationships with Broadcom, Nutanix, Microsoft, or any cloud provider — and our advisory fee is not contingent on which outcome you choose. Explore the full range of Broadcom resources at our Broadcom / VMware Knowledge Hub, or book a call with our team to discuss your specific renewal timeline and current exposure.