Budgeting for Broadcom pricing.

The Broadcom price increases that have rippled through enterprise IT budgets since the VMware acquisition closed are not a one-time event. They are a structural shift in the cost base of running virtualised infrastructure, and they affect the IT operating budget in ways that go beyond the obvious line item for VMware licences. The CIO and CFO who plan around the headline price increase alone consistently under-budget; the ones who model the full impact across software, services, capital, and operations land much closer to the actual cost.

This article walks through the IT budget impact of Broadcom pricing as we see it across the engagements we have worked in 2025 and 2026. The pattern is consistent enough across customers that the framework is portable, even though specific numbers vary by estate size, contract type, and product mix.

The headline cost increase

The Broadcom subscription pricing for VMware Cloud Foundation and the consolidated VMware SKUs prices materially higher than the perpetual-plus-support model it replaced, particularly for customers who held perpetual licences and were paying only annual support. The headline price increase customers see at first renewal under the new model typically lands between 200% and 400% of the prior annual cost.

The range depends on the prior entitlement structure, the bundle the customer migrates onto, and the negotiated discount. Customers on older Enterprise Plus perpetual entitlement, who would have continued paying maintenance only, see the largest percentage increase because the prior cost base was low. Customers on existing subscription contracts with broad VCF coverage see smaller increases because the prior cost base was higher.

Modelling the headline cost increase alone, however, misses much of the budget impact. The full picture requires looking at four other areas.

The bundle effect

Broadcom's SKU consolidation means many customers now pay for components of VCF they did not previously license — vSAN where they used third-party storage, NSX where they used third-party networking, Aria Operations where they used third-party monitoring. The customer is paying for these components whether they use them or not.

This creates a budget question with three answers depending on the customer's posture. The customer can absorb the bundle cost and continue using the third-party tools, paying twice for overlapping capability. The customer can rationalise the third-party tools and migrate onto the VCF-included components, eliminating the duplicate cost but absorbing migration cost. The customer can negotiate a different SKU mix with Broadcom that excludes the unused components, accepting a different commercial structure.

Each path has a different budget profile. Plans that assume the customer will simply absorb the bundle cost without changing the surrounding stack consistently under-budget the medium-term IT cost.

The audit settlement provision

The increase in Broadcom audit activity since the acquisition has driven enterprises to provision for audit settlements in the IT budget in ways they did not before. The provision should be sized to the realistic audit risk: the size of the VMware estate, the cleanliness of the entitlement record, the historical audit cadence, and the visibility of audit signals.

For most enterprise customers with material VMware estates, an annual provision of 5% to 15% of annual VMware spend, accumulated across the planning horizon, captures the realistic audit exposure. Some customers will not need to use the provision; the ones who do will be glad they accrued it. The CFO conversation about provisioning is easier when framed as a known, quantified risk than as a surprise that arrives mid-year.

The negotiation and advisory cost

Broadcom renewals require a level of negotiation preparation that previous VMware renewals did not. Enterprises that engage specialist advisory support for major renewals report consistently better outcomes than those that handle renewals through internal procurement alone. The advisory cost is a real line item, typically 5% to 15% of the negotiated savings, and it pays back as long as the savings outpace the cost — which, on substantive Broadcom renewals, it consistently does.

The audit defence cost is a separate provision. Where the audit settlement provision is the expected commercial outcome of an audit, the audit defence cost is the cost of mounting the defence that produces that outcome. Defence engagements typically cost $150K to $500K depending on the scale of the audit; the saving against an undefended audit is usually multiples of that figure.

The migration and alternative-architecture cost

Even customers who plan to stay on VMware should be modelling the cost of partial alternatives as part of the budget conversation. The point is not necessarily to execute the migration; the point is to know the costed alternative so the renewal conversation has the real walk-away number in hand.

Typical alternative-architecture costs to model include partial Hyper-V or Proxmox migration of non-critical workloads ($200 to $800 per VM migrated, depending on complexity), hyperscaler bare-metal repatriation for workloads that can run on AWS or Azure native services, and selected Citrix or Nutanix overlay for specific use cases. Even if none of these are executed, having them costed and ready informs both the renewal and the multi-year budget profile.

The operating expense vs capital expense shift

The shift from perpetual-plus-maintenance to subscription is also a shift from capital to operating expense. For many enterprises, this is a non-trivial accounting change with implications for the IT budget structure, the capitalisation policy, and the way IT cost is allocated across business units.

The CFO conversation here is about both the cash flow profile (subscription smooths the cash outflow but increases the total over five years) and the budget allocation (operating expense flows differently than capital expense across the management reporting framework). Many enterprises had not modelled this shift before encountering it as a Broadcom renewal reality. Plans that treat the shift as a non-event consistently produce surprises that affect the broader IT budget conversation.

The downstream estate cost

Broadcom pricing also affects costs that are not directly Broadcom line items. Customers who rationalise their VMware estate to reduce Broadcom exposure incur estate-rationalisation cost. Customers who migrate workloads to public cloud incur cloud migration cost and increased cloud run cost. Customers who diversify across hypervisors incur dual-skill, dual-tooling, and dual-operations cost.

Each of these downstream costs should be modelled explicitly. The customer who reduces VMware spend by $4M annually but spends $2.5M annually on the operations of the alternative is in a different position than the customer who reduces VMware spend by $4M without offsetting operations cost. The budget picture is the net, not the gross.

The three-year picture

The single most useful artifact in the Broadcom budget conversation is a three-year forward picture comparing the status-quo path to one or two alternative paths. The picture should include the headline subscription cost, the bundle effect, the audit provision, the advisory cost, the migration optionality cost, and the downstream estate cost.

Plans that include only the headline subscription cost produce conversations that swing between under-budgeting and over-conservative budgeting depending on which surprise hits in which year. The picture that includes the full set of cost components produces stable budgeting and credibility with the CFO.

What to do now

The budget impact of Broadcom pricing is large enough that the question is not whether to model it, but how completely. The CIO who walks the CFO through a complete picture — headline cost, bundle effect, audit provision, advisory cost, alternative-architecture cost, downstream estate cost — gets the budget authorisation needed to execute. The CIO who presents only the headline cost gets pressure on the headline number that produces worse tactical decisions.

The first step is to assemble the components. The second is to model them across three years with explicit scenarios. The third is to validate the model against current Broadcom practice with independent specialist input. The fourth is to present the picture to the CFO and the board with a clear ask for the authority needed to execute the plan that produces the best three-year outcome. Each of these steps is bounded; the cumulative effect is a much stronger position than the Broadcom situation initially suggests is possible.