Broadcom’s acquisition of VMware is driving a fundamental shift from suite-based licences to component-based subscriptions — often at significantly higher costs. This playbook provides CIOs with a detailed analysis of Broadcom’s packaging approach, pricing scenarios, negotiation strategies, and enterprise case studies to navigate the transition.
See also our Broadcom Advisory Services, Contract Negotiation Service, and Audit Defence Service.
For VMware customers, legacy bundles like vCloud Suite or vRealize Suite may no longer be offered. Each component — hypervisor, operations management, automation — may require separate licensing or inclusion in Broadcom’s new, limited set of bundles. Former CA Technologies products have similarly seen restructured pricing models with increased costs for existing customers.
CIOs need a proactive playbook to map current usage, evaluate criticality of each tool, anticipate pricing changes, and negotiate favourable terms.
Break down existing VMware and CA suite deployments into individual products and features. Know exactly what you have before anything changes.
Identify which components are mission-critical versus nice-to-have. Not every tool in a suite bundle delivers equal value.
Model the financial impact of subscription and per-component pricing versus legacy bundle costs. Prepare multiple scenarios.
Secure transitional discounts, lock in multi-year pricing, or preserve legacy terms wherever possible. Time is leverage.
Within weeks of the deal closing, Broadcom eliminated VMware’s perpetual licences and moved all offerings to subscription-only models. This was accompanied by a dramatic consolidation of VMware’s product portfolio into only a few high-level offerings. Instead of VMware’s myriad editions and suites, Broadcom now emphasises “component-based” subscriptions — requiring customers to licence each major product separately or as part of a new bundle.
Broadcom collapsed VMware’s catalogue into as few as four core offerings. VMware Cloud Foundation (comprehensive private cloud suite) is the primary option, alongside vSphere Foundation for core virtualisation with management tools. Many former standalone products (vSAN, NSX) are no longer sold à la carte — available only as part of bundles or add-on subscriptions.
This “simplification” means customers often buy a broader solution than they want, leading to overspending on unused components.
All licensing moved to subscription, measured on granular metrics. Broadcom introduced per-core licensing for VMware vSphere (replacing per-CPU), with a minimum of 16 cores per CPU. Software bundled in suites now has individual price tags. A new offering like vSphere Foundation bundles vSphere with operations management (elements of vROps/Aria) at a higher price.
Customers needing standard vSphere must subscribe to add-ons for operations tools — effectively separating vROps from vSphere.
Well-known VMware bundles (vCloud Suite, vRealize Suite) are being phased out in favour of Broadcom’s packages. Former CA Technologies product suites have likewise been re-examined. After acquiring CA, Broadcom swiftly restructured pricing models, leading to significant cost increases for existing customers and divested non-core products.
CIOs can no longer assume any bundle or enterprise licence will persist — every element may need to be licensed anew.
Nearly 75% of IT decision-makers expect VMware bills to at least double. Gartner has observed some clients’ costs have tripled. One enterprise faced an astonishing 1,050% increase. More commonly, 2–3× price hikes for similar usage are not uncommon. After acquiring CA and Symantec, Broadcom introduced higher fees and slashed discounts for smaller customers.
By bundling previously optional components into all-encompassing packages, customers must pay for the full banquet even if they only eat a few dishes. An organisation needing only vSphere and vSAN might still have to purchase entire Cloud Foundation (including NSX, Aria) because standalone vSAN and NSX licences have been discontinued.
Each product now comes with its own licensing terms, metrics, and renewal cycles — increasing administrative burden. Features once freely accessible as part of suites may now require specific licence keys. Broadcom enforces compliance strictly with willingness to trigger audits.
CIOs must budget for each component subscription, which may renew at different times and scale differently. TCO over 3–5 years will typically be higher. Some companies are paying 175% more for the same capabilities — and up to 10× more if they were on very favourable legacy contracts.
Broadcom has not hesitated to cut products that don’t align with its core focus. If tools in your VMware or CA suites are deemed non-strategic, they could be shelved or receive minimal investment. Watch for end-of-life or end-of-availability announcements for products once included in bundles.
You can’t manage what you don’t measure. The first critical step is to map out all components your organisation currently uses under suite or bundle licences — creating a clear picture of what you have and what you stand to lose or pay more for.
List every VMware and former CA Technologies product deployed. Include version numbers and licence type (perpetual vs subscription, bundle name). For VMware, identify bundles like vCloud Suite, vRealize Suite, vSAN+NSX bundles, or vSphere with Operations. For CA, list suites (APM suite, Security bundle) and individual tools under them. Distinguish core components from add-ons.
Break each suite licence into constituent components. For each, document: entitlement details (how it’s licensed in the suite — unlimited or specific capacity), current usage level (is the component actively used and how heavily?), and dependency/integration (which components work together — e.g. vRealize Automation feeding into vRealize Operations).
Some suite components may be so embedded they’re taken for granted. vRealize Operations might be feeding alerts into your enterprise monitoring dashboard, or a CA component might be embedded in a larger workflow. Talk to engineering and operations teams. A common oversight is assuming a component isn’t used just because it wasn’t separately installed — it may be leveraged via an integrated installer or feature toggle.
Correlate each legacy component to Broadcom’s new equivalent product or service. Create a mapping table: Legacy Suite Component → Broadcom New Product/SKU → Licence Metric (per core, per VM, per user). Example: vSphere + vRealize Operations could require both a vSphere subscription and an Aria Operations subscription, unless you opt for Cloud Foundation which includes both.
Mark any components with no direct one-to-one replacement in Broadcom’s catalogue. This doesn’t always mean immediate loss of use (you may continue using an older version temporarily), but it signals the need for an alternative plan for that function. Flag these for contingency planning.
Not every component in a suite delivers equal value. Broadcom’s unbundling presents an opportunity (albeit forced) to re-evaluate the necessity of each tool. Distinguishing mission-critical from nice-to-have helps identify where you can cut costs and where you must invest for continuity.
Systems without which major business operations would stop or be severely impacted. E.g. VMware vSphere hypervisor running production workloads, CA mainframe tools integral to core transactions. Fight hardest for favourable pricing on these.
Tools providing significant benefits but with workarounds or alternatives if needed. E.g. vRealize Operations (helpful for monitoring but could use basic vCenter alerts or another tool temporarily). Use as negotiation leverage — reduce scope if pricing unreasonable.
Components included in suites but seeing little use or providing marginal benefit. Reporting modules, niche automation features never fully adopted. Be ready to drop these to save costs — powerful signal to Broadcom that you won’t pay for everything.
Armed with inventory and criticality assessment, CIOs should now forecast the financial and operational impact of Broadcom’s new licensing scheme. Preparation is key — by anticipating changes, you can cushion your organisation from budget shocks.
Obtain indicative pricing from Broadcom for new subscriptions. Ask for a mapping of old SKUs to new SKUs with list prices. Pay attention to licensing metrics (per core, per VM, per user) and translate your usage. Inquire about transitional programmes — Broadcom has offered “trade-in” incentives and promotional discounts for early adoption.
Scenario A (Baseline): Legacy pricing — your comparison point. Scenario B (Full Usage): Continue everything under Broadcom’s pricing — likely shows 2–3× increase. Scenario C (Optimised): Drop Tier 3 components — still higher but moderated. Scenario D (Extreme Cut): Drop major portions or explore alternatives — for negotiation backdrop.
Compare scenarios to current IT budget and forecasts. If Scenario B shows a 50–100% increase, flag it internally early. Prepare a briefing for finance explaining vendor-driven changes. It’s easier to budget and save money through negotiation than to scramble for funds after the fact.
Determine if there will be any gap in coverage or support during the transition. If your support renewal is due soon and Broadcom won’t renew under old terms, you face the new model or risk being unsupported. Engage Broadcom to extend support on current terms temporarily.
Negotiate to co-term new subscriptions so they all renew at the same time. Secure a multi-year rate — a 3-year subscription with fixed pricing protects against annual increases. Multi-year deals may come with better initial discounts.
If Broadcom introduces new metrics (per-core instead of per-CPU), check if grandfathering is available for a transition period. Negotiate to treat 8-core CPUs as one unit for the first renewal to avoid a spike.
Broadcom may discount if you commit to broader portfolio usage. Be cautious — don’t buy unused components. But if you genuinely foresee adopting more products, bundling into negotiation could yield a package discount.
Check that you’re not automatically charged for premium support you don’t need. If enhanced support is included in the bundle, determine if it’s useful or if you can opt for a lower-cost tier instead.
Broadcom is known for its no-nonsense, profit-driven approach. Typical vendor negotiation playbooks need to be augmented with more assertive and creative strategies for this new era.
Start discussions 6+ months before contracts expire. Broadcom uses time pressure (last-minute ultimatums) to force acceptance. By initiating early with clear milestones, you remove that leverage. Broadcom reps facing a well-organised customer may work on details rather than risk a walkaway.
Active perpetual licences with support or unexpired ELAs are bargaining chips. Broadcom wants to convert these to subscriptions and has offered ~50% trade-in discounts. Insist on credit for remaining value — if you bought a 3-year ELA and are only 2 years in, don’t let that year go to waste. Negotiate reduced subscription prices for the first term reflecting years of support fees already paid.
Bake in safeguards — cap annual price increases at single-digit percentages or lock prices for multi-year terms. If Broadcom offers a steep first-year discount, ensure it’s not bait with a huge jump later. Specify Years 2 and 3 costs in the contract. The goal is avoiding unwelcome surprises.
Compare bundle price to the sum of individual components you actually need. If a bundle includes three things you won’t use, it might be cheaper to buy two components separately. Propose custom bundling — ask Broadcom to price a tailored set of components as a package, essentially recreating a mini-suite for you. You won’t know unless you ask.
Request phase-in pricing (smaller increase Year 1, step up to full rate Year 2–3) to absorb changes over multiple budget cycles. Ask to extend current terms for a short period while evaluating new options. Large customers who ask convincingly sometimes secure short-term extensions.
Broadcom has strong incentives not to drive away all customers. Market discontent is visible and some customers are exploring exits. Signal (subtly) that you’re considering “all options” — you don’t need to threaten to leave, but showing you’re not completely captive can increase flexibility.
Beyond price: negotiate audit relief (reasonable notice, once-per-year limit), licence flexibility (can you downgrade at renewal or transfer credits to cloud?), avoid severe early-exit penalties, and protect legacy perpetual licence rights from being nullified. Watch for “relinquishment” clauses that revoke perpetual rights when moving to subscription.
Consider independent licensing advisers (such as Redress Compliance) who specialise in VMware/Broadcom negotiations. They provide benchmarks (what discounts others are getting), identify contract gotchas, and help craft counterproposals. Their neutrality and experience help spot risks you might miss.
Keep detailed records of all communications. Get verbal promises in writing. This protects you during personnel changes, misunderstandings, or potential disputes. A paper trail is your friend — especially if Broadcom offers time-limited discounts or special conditions.
In negotiations with Broadcom, the key is to be firm, data-driven, and creative. Know your walk-away points for each component, know what a win looks like, and be prepared to escalate to VP or C-level at Broadcom if account reps reach an impasse. Sometimes a polite letter to Broadcom’s CEO can trigger a better account response team.
Consider a hypothetical enterprise with 100 CPU sockets of VMware vSphere, previously licensed via vCloud Suite Enterprise (including vSphere Enterprise Plus + vRealize Suite). They also use NSX on half those hosts and vSAN on 20 TB of storage.
| Scenario | Description | Annual Cost | vs Legacy |
|---|---|---|---|
| Legacy Suite (Pre-Broadcom) | VMware ELA covering vCloud Suite Enterprise for 100 sockets + NSX + vSAN 20 TB. Per-CPU pricing with unlimited cores. | ~$1.06M | Baseline |
| Option 1: VMware Cloud Foundation | Subscribe to VCF for all 100 hosts. Includes vSphere, vSAN, NSX, Aria. Even after Broadcom’s 50% list price reduction. | ~$2.0M | +89% (≈2×) |
| Option 2: Individual Components | vSphere by core ($1.5M) + Aria Operations ($600K) + NSX for 50 hosts ($400K) + vSAN 20 TB ($200K). Separate subscriptions. | ~$2.7M | +155% (≈2.5×) |
| Option 3: Optimised Usage | Drop vRealize Automation, forego Aria Operations (use basic vCenter), reduce NSX to 30 hosts, archive data to 15 TB. | ~$1.89M | +78% |
The way you slice it matters. Broadcom’s bundle (Option 1) might ironically be the “cheapest” way to get everything — but forces you to pay for all components. Picking and choosing separately (Option 2) can actually cost more because standalone pricing is punitive. The best financial approach (Option 3) is to trim usage and only pay for critical components — still higher than legacy, but the increase is moderated.
A company using CA’s IT monitoring and service management suite (CA APM + CA Service Desk + CA UIM) for $500K/year. After Broadcom: APM costs $300K standalone, Service Desk $250K, UIM $150K. All three would be $700K (40% increase).
By dropping UIM (partially replaced by another tool), they pay $550K (10% increase for less functionality). They negotiated a 3-year deal at $500K/year — keeping costs flat in exchange for a longer commitment and dropping one component.
Situation: Global financial services company with VMware vCloud Suite across thousands of VMs. ELA due to expire in 12 months. Broadcom’s initial communication indicated the ELA would not be renewed under old terms and à la carte pricing would triple their costs.
Actions: The CIO initiated executive-level talks within a month of the acquisition closing. Leveraging the bank’s strategic importance (top-50 VMware customer), they negotiated an early renewal — signing a new 3-year agreement carrying over much of the bundle pricing. In return, Broadcom got the bank to agree to transition all licences to subscription by term end and slightly increase coverage.
Result: Year-1 cost remained at legacy levels, with years 2 and 3 capped at single-digit percentage increases. The bank gained time and budget stability to plan for post-year-3.
Takeaway: Early, high-level engagement and willingness to commit longer can protect from the worst price hikes. Negotiate a bridge to Broadcom’s model rather than falling off a cliff.
Situation: Multinational manufacturer using VMware vRealize Suite and a legacy CA network monitoring tool. Faced 100% increase on VMware side and end-of-sale announcement for the CA tool.
Actions: Deep usage analysis revealed vRealize Automation was underutilised — only a few test/dev processes used it. Decided to drop vRA and retain vRealize Operations (critical for monitoring). For the CA tool, opted not to adopt Broadcom’s replacement — expanded NSX visibility features and an open-source tool instead. Negotiated Cloud Foundation bundle with 3-year commitment.
Result: Annual VMware spend increased only ~30% (instead of 100%). CA tool was sunset on their terms after a 1-year extension.
Takeaway: Selective adoption — understanding what you can live without and consolidating needs into one bundle — minimises cost impact and avoids paying for replacements you don’t need.
Situation: Large retail chain using vSphere, vSAN, Site Recovery Manager, and Log Insight (purchased à la carte historically). Under Broadcom’s model, vSAN and SRM were only in bigger bundles. Cloud Foundation quote was 2.5× current spend.
Actions: CIO took a hard line — said they’d forgo SRM and seek alternate DR solutions if Broadcom couldn’t meet budget. Pointed out they didn’t use NSX, so Cloud Foundation provided no value there. After multiple rounds, Broadcom offered a custom bundle: vSphere + vSAN + SRM + Log Insight (excluding NSX) for ~50% above current — not a standard SKU, but an accommodation.
Result: Avoided a 150% cost jump and settled for a 50% increase with a tailored 2-year bundle. Agreed to evaluate NSX during the period but not purchase it outright.
Takeaway: If a customer is ready to drop a product and has a credible plan, Broadcom may prefer a custom deal to keep the customer on their stack, even at reduced scope.
Situation: Mid-sized healthcare organisation with a modest VMware footprint and no large leverage. Post-acquisition, Broadcom’s only option was vSphere Foundation at 3× previous spend. “Take it or leave it.”
Actions: Lacked influence for flexible negotiation. Signed a 1-year subscription (instead of 3) at the high price — buying a year to decide on long-term strategy. Used that year to optimise VMware usage through consolidation and pilot an alternative virtualisation platform for non-critical workloads.
Result: Short-term budget hit (reallocated from other projects). Used the year to reduce host count by 20% and prepare an RFP for alternatives. At next renewal, Broadcom offered a modest discount to retain the smaller remaining business.
Takeaway: Even with little leverage, buying time and trimming costs internally improves your next negotiating position. Not every customer gets a friendly deal — contingency planning is necessary.
Document every VMware and CA product in use, especially those obtained via bundles. Know your current entitlements and usage in detail — this is the foundation for everything else.
Classify each component by criticality. Focus negotiations on protecting and securing favourable terms for Tier 1 critical tools. Be ready to drop or find workarounds for lower-tier items.
Communicate with finance about potential cost increases and with operations about possible toolset changes. Early transparency ensures support when tough decisions arise.
Don’t operate on assumptions. Request official documentation of product packaging changes relevant to you. If anything is unclear, press the vendor for answers in writing.
Model best-case, expected, and worst-case cost scenarios for the next 3–5 years. Use these to inform budgeting and establish negotiation targets. Include operational costs of workarounds.
If current contracts expire in the first wave, request transition assistance (discounts, credits, extensions). Broadcom may be more flexible early to avoid rash customer losses.
Gather all leverage — know your alternatives, align internally on must-haves and walk-aways, consider a licensing expert, and prepare to escalate within Broadcom.
Thoroughly review the final contract for accuracy and completeness of all negotiated points. After signing, do an internal post-mortem — this team and process will pay dividends at every future vendor renewal.
Broadcom’s unbundling and repricing strategy is a textbook challenge in vendor management. By following a structured playbook — inventory, assess, plan, negotiate, and adapt — CIOs can turn this challenging situation into an opportunity to clean up unused software, reinforce financial discipline, and ensure their organisation is only paying for the technology value it truly needs.