Broadcom ELA vs Separate Contracts – Which Model Fits Your Enterprise?

Broadcom ELA vs Separate Contracts

Introduction: The Enterprise vs. Individual Contract Decision

Broadcom aggressively promotes enterprise-wide agreements as a way to consolidate your spending under one umbrella.

As a CIO or procurement leader, you might be weighing a single Broadcom Enterprise License Agreement (ELA) against managing separate contracts for each product line. It’s a strategic decision with major cost and flexibility implications.

Broadcom’s default pitch is that an all-in-one deal gives you simplicity and maximum value, but savvy organizations remain skeptical. In reality, one big contract vs. many smaller ones is a trade-off between convenience and flexibility.

This introduction sets the stage for evaluating whether signing a Broadcom umbrella agreement or sticking with individual product contracts is the better fit for your enterprise. Read our comprehensive guide to Broadcom Enterprise License Agreements (ELA/PLA) and Framework Contracts.

Many enterprises are debating this exact choice. On the one hand, a Broadcom ELA can provide you with a unified agreement covering everything from VMware to Symantec security to mainframe tools. On the other hand, maintaining separate contracts per product might preserve negotiating leverage and avoid overcommitting. Broadcom often pushes the ELA route to increase its control and lock in customers, especially after it acquires VMware, CA, and Symantec.

The key is to cut through the sales messaging and objectively compare the models.

Below, we’ll break down what each approach entails, its pros and cons, and when each makes sense.

By the end, you should have a clearer idea of which contract strategy aligns with your enterprise’s needs and risk tolerance.

What Is a Broadcom ELA?

A Broadcom Enterprise License Agreement (ELA) is a comprehensive umbrella contract that encompasses multiple Broadcom software product lines under a single agreement. Instead of signing separate deals for VMware, Symantec (security), CA (mainframe/DevOps), and other Broadcom-owned products, an ELA bundles them into a single multi-year contract.

Typically spanning 3 to 5 years, a Broadcom ELA co-terms all included products to the same renewal date and provides a consolidated pricing structure.

In practical terms, you pay one fixed annual fee (or a set of scheduled fees) for the right to use a broad swath of Broadcom’s software portfolio. This includes licenses and usually support/maintenance for the term of the agreement.

Key characteristics of a Broadcom ELA include:

• Multi-Product Bundle: It can cover a wide range of Broadcom acquisitions and product families (e.g., VMware infrastructure software, Symantec security suites, CA mainframe tools, etc.) under one contract. You commit to a comprehensive bundle rather than selecting individual software licenses one by one.
• Co-Termed Multi-Year Term: All products in the ELA share the same end date. You might sign a 3-year ELA, and all VMware, security, and other licenses in it will renew together at year 3. This single renewal event is both convenient and high-stakes (more on that later).
• All-Inclusive Subscription Pricing: Broadcom ELAs have moved to a subscription model. After acquiring companies like VMware, Broadcom eliminated perpetual (one-time purchase) licenses. So an ELA is effectively a giant subscription covering all your software use and support. You pay annually (or upfront) for continuous access and updates. If you stop paying, your rights to use current versions end.
• Consistent Terms: The ELA establishes a single set of legal terms governing all included products. This can simplify compliance and legal review, as you don’t have to juggle different terms for different software. Broadcom’s ELA terms tend to be standardized and often stricter than those of legacy VMware contracts (for example, fewer carve-outs and more rigid compliance obligations).
• Broadcom’s Control Point: Strategically, Broadcom uses ELAs to deepen account control. By bundling everything, Broadcom gains leverage at renewal (since you’d have to potentially replace your entire software stack if you walked away). This is a key context: VMware’s legacy ELA programs were often more flexible with generous discounts and perpetual elements, whereas Broadcom’s new ELA framework is stricter, subscription-only, and designed to maximize Broadcom’s revenue.

In short, a Broadcom ELA is one big bet: you’re committing to Broadcom’s stack company-wide for several years, ideally in exchange for better pricing and simpler management. Now let’s contrast that with the alternative approach.

What Are Individual Contracts?

“Individual contracts” in this context means separate license agreements for each Broadcom product or product line your company uses.

Instead of one umbrella deal, you might have a VMware contract for virtualization, a Symantec contract for security software, a separate agreement for any mainframe tools, etc.

Each contract is negotiated and signed independently, possibly even by different business units or at different times. They can have different term lengths, end dates, and terms tailored to each product.

Characteristics of the individual contract approach include:

• Product-Specific Agreements: Each software product line (e.g., VMware) has its own contract, with its own pricing and scope. You’re essentially treating each Broadcom business unit’s products as a separate vendor relationship in terms of negotiation.
• Staggered Renewal Cycles: Since contracts are signed at different times, their renewal dates are likely spread out over time. You might renew VMware this year, the security software next year, and so on. This means continuous negotiation cycles, each focused on a single product family at a time.
• Flexibility to Treat Each Product Separately: You can scale up or down each agreement on its own merits. For example, if you decide to drop a certain tool (say, you switch away from one security product), you can let that one contract lapse without affecting others. There is no single bundled commitment tying them together.
• Separate Pricing & Discounts: Pricing is determined per product line. You might negotiate a 20% discount on VMware licenses based on their volume, and separately negotiate a discount on the Symantec product based on its competitive landscape. There’s no combined volume discount across all products, but you might gain leverage by pitting each Broadcom product against its direct competitors in the market individually.
• More Contracts to Manage: The obvious trade-off is administrative overhead. Multiple contracts mean multiple negotiations, multiple sets of terms, and careful tracking of each renewal. Procurement and vendor management become more complex compared to a one-and-done ELA (however, some organizations prefer this granularity for control).

In essence, the individual contract route is about keeping your options open and your commitments narrowly defined. It can be advantageous for flexibility, but you miss out on the “one bundle” discounts and simplicity.

Next, we’ll dig into the advantages and disadvantages of each approach to clarify these trade-offs.

Pros and Cons of a Broadcom ELA

Like any major decision, an enterprise agreement with Broadcom comes with both significant advantages and disadvantages. Below are the key pros and cons of signing a Broadcom ELA:

Pros of a Broadcom ELA:

• Bulk Discounts & Cost Savings: By committing to a large multi-product deal, you often unlock volume discounts that wouldn’t be available in smaller purchases. Broadcom is more willing to offer attractive pricing if you’re bringing them a multi-million-dollar, multi-year commitment. The ELA can result in a lower overall unit cost (per license or per user) compared to buying piecemeal, if you actually use everything in the bundle.
• Simplified Vendor Management: With an ELA, you consolidate dozens of separate contracts into a single master agreement. This means negotiating only every few years, rather than undergoing constant renewals. It simplifies procurement, legal review, and vendor relations – you deal with Broadcom in one consolidated manner. Co-terming everything to one date can reduce management headaches.
• Predictable Budgeting: An ELA’s fixed annual fee brings budget predictability. You know exactly how much you’ll spend on Broadcom software for the next X years. This helps avoid surprise costs or spikes from individual license add-ons. Many ELAs also include a degree of usage growth at no additional charge, providing a buffer in case your needs expand. (For example, you might negotiate the ability to add 10% more licenses/users annually without an immediate price increase.)
• Enterprise-Wide Coverage & Convenience: The umbrella agreement often grants broad usage rights. Your teams can deploy additional products or expand usage without having to procure new licenses each time, as long as it’s covered under the ELA. This “all-you-can-eat” style access can foster agility – you can try new tools in Broadcom’s portfolio on the fly since they’re prepaid. It also ensures all parts of your enterprise are on consistent terms and versions.
• One Renewal to Rule Them All: When the term is up, you renegotiate one contract. If you’ve had issues juggling different renewal dates and vendor quotes throughout each year, an ELA consolidates that into a single event. Some CIOs value the singular focus – it’s a big project to renew an ELA, but at least it happens infrequently.

Cons of a Broadcom ELA:

• Massive Commitment & Potential Shelfware: The flip side of “all you can eat” is buying more than you need. An ELA typically requires a large, upfront commitment to a bundle of products and volumes. If your usage forecasts are off, you might end up with “shelfware” – paid-for software that isn’t fully used. For example, you might commit to Broadcom’s full security suite but only actively use half of it, effectively wasting budget. The risk of shelfware is high with big bundles, especially if Broadcom convinced you to include products “just in case” you need them.
• Loss of Flexibility: Once you sign an ELA, you are locked into Broadcom’s ecosystem for the term. It’s very difficult (if not impossible) to drop a product or reduce licenses mid-term – you’ve bundled it all together. If a certain tool isn’t delivering value, you’re stuck paying for it until the ELA expires. This lack of flexibility can hinder your IT strategy; you may feel compelled to continue using a subpar solution because it’s already covered under the ELA. In contrast, separate contracts would allow you to terminate one product without affecting the others.
• High-Stakes Renewal (Vendor Leverage): Having “one negotiation to rule them all” can become a disadvantage at renewal time. Because all your eggs are in one basket, Broadcom knows you’re deeply dependent on its portfolio when the ELA expires. Without proper protections, you could face a steep price increase at renewal. Broadcom has been known to present renewal quotes with significant uplifts (20%, 50%, and even higher), especially when initial discounts were offered. If you’ve got no fallback for the entire suite, your leverage to push back is limited. In essence, the simplification of one renewal also means Broadcom can apply pressure all at once, putting your entire environment at stake.
• Upfront Costs & Payment Terms: Broadcom’s ELA deals often involve large sums, and Broadcom may insist on upfront payment or multi-year prepayment for the bundle. This can strain budgets. Unlike smaller annual contracts that you pay year by year, an ELA may require a substantial first-year payment (or even full-term payment), which could be a barrier for some companies. Additionally, you’re committing future budget years in advance, which reduces flexibility to adjust spending if economic conditions change.
• Opaque Value Allocation: When everything is bundled, it’s difficult to determine the cost of each product. Broadcom may offer an overall discount percentage, but it lacks transparency into individual product pricing. This opacity can hide the fact that you might be overpaying for certain components. If you wanted to remove one product, there’s no clear “price tag” on it in the bundle to know how much you’d save. This can make it challenging to accurately evaluate the true ROI of each component of the ELA.

In summary, a Broadcom ELA can yield cost savings and ease of management if you truly need and use all the included software.

But it comes with significant risks: you’re betting big on Broadcom, so you must manage the commitment carefully to avoid wasted spend and minimize Broadcom’s leverage over you.

Read about the support terms, Broadcom Subscription and Support Terms in Enterprise Agreements – What to Watch For.

Pros and Cons of Individual Contracts

Now let’s flip the coin and consider the pros and cons of keeping separate contracts for Broadcom product lines (VMware, security, etc.) instead of one enterprise agreement:

Pros of Individual Product Contracts:

• Maximum Flexibility: By negotiating each product contract separately, you maintain the ability to scale or exit each agreement on its own terms. If one software suite is no longer needed or a better alternative comes along, you can choose not to renew that one product without impacting your other tools. This flexibility is valuable for rapidly changing IT environments or if you’re not 100% committed to Broadcom’s entire portfolio.
• Smaller Commitments (Lower Risk): Each contract is a smaller commitment in scope and dollars compared to a mega-ELA. This can reduce the risk of overspending. You only commit to what you need for each product. There’s no obligation to pre-pay a giant bundle “just in case” – no paying for unused products that sounded good in theory. It’s easier to align spend with actual usage on a product-by-product basis.
• Product-Specific Negotiation Leverage: When dealing with one product at a time, you can leverage competition and alternatives more effectively. For instance, if you’re renewing your VMware contract and considering moving some workloads to a public cloud or another virtualization platform, you can use that as leverage to negotiate a better VMware price. Broadcom knows you could switch out that one piece. Similarly, for security software or mainframe tools, you can pit Broadcom’s offering against other vendors during each negotiation. This competitive pressure can drive better discounts for that product than you might get if everything were tied up in an ELA (where Broadcom knows you likely won’t rip out the entire stack).
• Tailored Terms per Product: Different software might require different terms. By keeping contracts separate, you can negotiate specific contract terms that make sense for each technology. For example, you might secure very favorable maintenance terms for your mainframe software, and separately negotiate a flexible user count model for your security software. In an ELA, everything is one-size-fits-all. Individually, you have more room to customize agreements to fit the needs and usage patterns of each area.
• Ongoing Renewal Leverage: With staggered renewals, you have multiple touchpoints to reevaluate vendors and pricing. Each time a contract comes due, it’s an opportunity to assess if you should stay with Broadcom for that product or consider alternatives. This continuous leverage can keep Broadcom on its toes, knowing they have to win your business repeatedly (for each product line) rather than one big win and then you’re locked in for years.

Cons of Individual Product Contracts:

• Missed Bundle Discounts: The most obvious downside is that you might miss out on the bulk discount that a larger, combined deal could bring. Your spend is fragmented, so each contract might only qualify for smaller volume discounts. Broadcom typically rewards larger commitments; separate deals might end up with higher per-unit costs. The total cost could be higher if you indeed use everything an ELA offers, but you’re buying it in pieces.
• More Complex Vendor Management: Managing several contracts is inherently more work. You’ll be juggling different renewal dates, possibly dealing with different Broadcom sales teams (e.g., VMware reps vs. Symantec reps), and handling multiple procurement processes. This can tax your sourcing and contract management resources. It’s a trade-off between flexibility and simplicity – you gain flexibility, but your team will spend more time keeping track of who needs to renew what and when.
• Staggered Renewals = Less Combined Leverage: While staggered renewals give you continuous options to negotiate, they also mean you’re never bringing your full buying power to the table at once. For example, if you spend $2 million on VMware and $1 million on security annually in separate deals, you negotiate those separately, and each is a moderate-sized deal to Broadcom. With an ELA, you’d be negotiating $3 million at once, which could give you more clout to demand concessions. Staggered timing can weaken your leverage, as each negotiation is isolated rather than a single, comprehensive approach. Broadcom might be less inclined to offer a significant discount on a smaller contract, whereas a larger, consolidated negotiation might have yielded a more favorable outcome.
• Inconsistent Terms: Each contract might have slightly different terms and conditions, which can create compliance or legal complexity. You may need to track various usage rights, auditing clauses, support levels, and other terms across multiple agreements. This is manageable, but it requires diligence to avoid accidentally breaching a term in one contract while assuming it is the same as another. With an ELA, terms are uniform; with separate agreements, you have a patchwork of agreements to administer.
• Renewal Timing Could Reduce Negotiation Focus: When you’re always in a renewal cycle for one product or another, your organization may never fully focus on a strategic licensing strategy. Some deals may be renewed automatically because the team is busy with others. In contrast, an ELA’s single renewal allows a major, focused negotiation effort. Multiple small renewals can sometimes slip through with less scrutiny, potentially yielding less optimal results if your team is stretched thin.

Both approaches have trade-offs. It often boils down to your enterprise’s priorities: Is flexibility and avoiding lock-in your top concern?

Then individual contracts shine. If cost savings and simplicity are paramount (and you have a stable, long-term need for Broadcom’s products), an ELA can be enticing. To clarify this, the next section presents a side-by-side comparison of key factors.

ELA vs. Individual Contracts: Comparison Table

To summarize the differences between a Broadcom enterprise agreement and separate product-level contracts, consider the comparison below:

This table highlights how an ELA centralizes and consolidates everything, while individual contracts decentralize and allow more fine-tuning.

Neither is inherently “better” in all cases; it depends on your situation. Next, we’ll discuss scenarios of when each approach tends to make sense.

When to Choose an ELA

Signing a Broadcom ELA makes the most sense in scenarios where the benefits of bundling outweigh the downsides.

Here are situations where an enterprise-wide agreement is likely the right choice:

• Extremely Large, Multi-Product Spend: If your organization is already spending a multi-million dollar amount annually across several Broadcom product lines, an ELA can unlock significant savings. Typically, if you’re in the Global 2000 size and rely on VMware, as well as other Broadcom-owned tools (such as security suites and mainframe software), bundling them can provide a better volume discount and price lock-in. There’s a practical threshold: enterprises with, say, $ 5 M or more in yearly Broadcom spend across their portfolios are prime candidates for an ELA.
• Using Multiple Broadcom Portfolios: An ELA shines when you have broad usage of Broadcom’s stack. For example, a large bank running VMware for virtualization, Symantec for cybersecurity, and CA for mainframe management would find value in a single, comprehensive deal. The more product lines involved, the more sense a single contract makes to reduce complexity. Broadcom itself will strongly encourage an ELA if you have several of their acquisitions in play – they’ll tout it as a one-stop solution (and indeed, it can simplify life when juggling three to four different product sets).
• Stable, Predictable Needs: If your software needs are relatively stable and you foresee consistent or steadily increasing usage, an ELA can be an efficient solution. For organizations that anticipate relying on Broadcom’s software in the long term, locking in a deal now can help hedge against future price increases. Additionally, if you can accurately forecast growth (e.g., a 10% increase in VMware capacity per year), you can negotiate this into the ELA (perhaps via a growth buffer). In a stable environment, the risk of overcommitting is lower, so the ELA’s predictability becomes a big plus.
• Value in Simplification (Co-terming): Consider an ELA if the administrative simplification itself brings value to you. Perhaps your IT procurement team is lean, and dealing with one contract is significantly easier. Or maybe having one renewal every few years allows you to put more effort into that negotiation and really optimize it, rather than being stretched across multiple talks. If your organization highly values co-terming for operational efficiency, the ELA is a compelling option. One CIO described it as “one contract to manage instead of twelve – that alone saved my team countless hours in vendor meetings and legal reviews.” This is particularly true if the internal cost of managing many contracts is high for you.
• Need for Broad Portfolio Access: In some cases, an enterprise may choose an ELA not only for cost, but also to gain access to a wide range of software on demand. Suppose you have initiatives that could benefit from experimenting with new tools (analytics, AIOps, security modules, etc.), and those are in Broadcom’s catalog. In that case, an ELA lets your teams try to use them without separate purchase processes. For an organization in innovation mode, the ability to access various products under a single agreement can accelerate projects. Essentially, if you see genuine value in having a buffet of Broadcom tech available, that’s a point in favor of an ELA.

In summary, choose an ELA when you are big enough to leverage it, using enough Broadcom software to bundle, and confident that you’ll utilize what you pay for.

It works best for large, committed Broadcom customers who can negotiate it smartly and avoid the worst pitfalls (like shelfware). Of course, even in these cases, negotiating the ELA’s terms carefully is critical – which we’ll touch on later.

When to Stick with Individual Contracts

While Broadcom will often advocate for the umbrella agreement, there are plenty of cases where maintaining separate contracts is wiser.

You should stick with individual product contracts in scenarios such as:

• Single-Product or Narrow Use: If your organization primarily uses only one major Broadcom product line (or very limited scope), an ELA likely isn’t worth it. For example, a mid-sized enterprise that relies heavily on VMware but doesn’t use Broadcom’s security or mainframe products has little reason to bundle into an enterprise deal. You’d be taking on extra products or contract complexity without a clear benefit. In this case, focusing on getting the best deal for your VMware contract alone (or whichever single product is key) is more sensible.
• Evaluating Alternatives or Migrating Away: Companies in a state of flux or considering moving away from certain Broadcom products should avoid locking into an ELA. Perhaps you’re unsure about staying with VMware in the long term due to cloud migration, or you’re evaluating alternative security vendors. If you’re in exploration mode, keep your contracts separate and short-term. An ELA would reduce your ability to pivot because it bundles everything for multiple years. It’s better to maintain flexibility until you decide on your future architecture. In other words, if you might drop or swap a product soon, don’t tie it into an ELA.
• Need Year-to-Year Flexibility (Budget or Scope): Some organizations are unable to commit to multi-year deals due to their budget processes or fluctuating needs. If you require the ability to adjust your spend annually, drop certain license counts, or cancel with shorter notice, individual contracts are a better option. For instance, maybe your company expects a divestiture or a downsizing that could reduce usage of a product – you’d want the option to scale down at renewal without being stuck in a long ELA term. Additionally, from a budgeting perspective, avoiding a large upfront commitment may align better with your annual fund allocation. Avoiding a multi-year upfront lock-in is prudent if your financial or operational situation might change drastically.
• Maintaining Negotiation Leverage: Some buyers prefer staggered negotiations to keep constant pressure on the vendor. By renewing one product at a time, you can continuously apply competitive leverage and avoid giving Broadcom the comfort of a long-term lock-in. If you fear that bundling everything will cause you to lose leverage at the big renewal, then stick to separate deals. This way, Broadcom has to “win” your business repeatedly and can’t take any single mega-contract for granted. Also, if one negotiation goes poorly, at least it only affects one area – you haven’t put all your eggs in one basket.
• Mid-Sized and Cost-Sensitive Organizations: Smaller enterprises or those with tight IT budgets often benefit from avoiding the grand ELA. Broadcom ELAs come with hefty minimum spends and sometimes aggressive terms that favor large enterprises. A mid-market company might find that a la carte contracts let them stay nimble and only pay for what they truly need. The complexity of an ELA might be overkill if your Broadcom footprint is modest. In such cases, the administrative burden of separate deals is manageable, and the safety of not overcommitting outweighs the downside of not bundling (a slightly lower discount).

In short, if you value flexibility, have uncertainty in your tech roadmap, or only use a slice of Broadcom’s offerings, then individual contracts likely serve you better. You retain the freedom to make course corrections and avoid being tied into a package that doesn’t fit snugly.

Negotiation Strategies for Both Paths

Whether you decide on a Broadcom ELA or opt to keep individual contracts, strong negotiation is essential to get a fair deal.

Broadcom is known for tough sales tactics, so you’ll want to enter any agreement with eyes open and key protections in place. Here are strategies tailored to each approach:

If You Pursue an ELA (Enterprise Agreement):

• Define the Scope Rigorously: Be very clear about what products and quantities are included. Avoid the temptation (or pressure) to throw in “extra” products that you aren’t sure you’ll use. The tighter the scope is aligned to your actual needs, the less likely you’ll overpay for shelfware. Make sure the contract lists exactly which product suites or modules you’re getting – no vague language.
• Negotiate Price Protections: One of the biggest risks is the potential for a renewal cost spike. Insist on uplift caps or pricing protections for renewals. For example, negotiate a clause that limits annual renewal price increases to a certain percentage or ties them to an index, such as the Consumer Price Index (CPI) inflation. If possible, secure a cap (e.g., no more than a 3-5% increase per year at renewal). Also consider locking in discount levels for the renewal term in the contract. Having these terms in writing will prevent nasty surprises when the ELA expires.
• Include a Growth Buffer: It’s wise to build in some “headroom” so you don’t get penalized for reasonable growth. Try to include a growth allowance – e.g., the contract could allow you to add up to 10% more users or licenses annually at no additional cost, or at the same discounted rate. This way, if your company grows or acquisitions happen, you aren’t immediately pushed into an out-of-band purchase or a larger ELA mid-term. Essentially, plan for success by having extra capacity pre-negotiated.
• Ensure Co-Termination (Already a Feature) Works for You: Co-terming is inherent in an ELA, but use it to your advantage. Align the ELA to a timeframe that makes sense (for instance, after a major project or budget cycle). Also, if you’re rolling some existing contracts into the ELA, ensure they all truly co-term – sometimes Broadcom might leave a few straggling licenses outside the ELA. Insist that everything you care about is synchronized, so you genuinely have one single negotiation point at renewal.
• Secure Renewal Options or Flexibility: While Broadcom standard ELAs don’t allow dropping products mid-term, you can negotiate certain flexibility clauses. For example, you might negotiate the right to eliminate one product from the bundle at renewal or get credits if you choose not to renew a particular component. It could be a long shot, but even a clause like “Customer may remove up to 1 product category at renewal without penalty, with equivalent value reduction” can give you some future out. At minimum, try to incorporate performance/consumption reviews annually – formal check-ins where you can discuss adjusting the deal if things have radically changed (even if not binding, it flags the concern early).
• Get Everything in Writing: Broadcom reps might make promises verbally about “oh yes, you can use as much as you want of X product” or “we’ll be reasonable at renewal.” Don’t accept verbal assurances. Document every understanding in the contract. If unlimited usage of something is claimed, put it in the contract. If the discount is based on a certain baseline, document that baseline. Treat an ELA negotiation as if you’re pre-negotiating the divorce terms at the marriage – assume whatever can go wrong or be misinterpreted will, so get it clarified now.

(Example of protective wording for an ELA: “Growth Buffer: Customer may add up to 10% additional licenses/users per year under this agreement at no additional charge, to accommodate natural growth.”)

If You Stick with Individual Contracts:

• Leverage Competitive Alternatives: In each product negotiation, remind Broadcom that you have options. For VMware, mention that you’re evaluating other virtualization or cloud solutions; for security, mention other security vendors, etc. Even if you strongly intend to stay, signaling that you’re not captive can help you extract better discounts. Broadcom is more likely to concede on price or terms if it fears losing the entire business of that product. Essentially, play one product line off against the competitive market on its own merits.
• Negotiate Product-Specific Discounts and Terms: Don’t Accept a Boilerplate Quote. Explore each product’s value and usage to suit your needs. If one Broadcom product is less critical, push for a steeper discount to justify keeping it. Conversely, if one product is mission-critical but has viable alternatives, use that as leverage. Structure each deal to fit the product’s context – for example, you might negotiate a shorter term for something you’re unsure about (such as a 1-year renewal instead of 3) to maintain flexibility. In contrast, for a stable product, you opt for a longer term at a favorable rate. Use your knowledge of each domain’s pricing norms to challenge Broadcom’s quotes.
• Staggered Renewal Strategy: Embrace the staggered renewals strategically. You might plan renewal dates such that they don’t all align in the same quarter, which prevents Broadcom from tying them together. Some customers intentionally avoid coterminous dates on separate contracts so that they can tackle them one at a time. Also, consider the sequence – for instance, renew the easier/cheaper contract first or last, depending on whether you want to set a tone or wrap up low-hanging fruit. Staggering can also allow you to pilot an alternative in between: e.g., if your security software contract ends in 18 months, you have that time to test a competitor’s product before deciding on renewal.
• Maintain Internal Leverage: Keep your stakeholders (and Broadcom) a bit uncertain by not committing all products at once. If Broadcom’s team knows you’re only renewing one product and the others are separate decisions, they have to earn each renewal. Internally, communicate that Team A can consider product alternatives independently of Team B’s contracts. This mindset ensures you evaluate each renewal on its own ROI, rather than just out of habit.
• Aggregate Where It Makes Sense: Just because you’re not doing an all-in ELA doesn’t mean you can’t bundle similar things. For instance, within Broadcom’s portfolio, maybe you use two VMware-related products – those could still be under one contract for convenience and discount purposes (that’s more like a mini-ELA for just VMware’s suite). Or, if you have multiple security products from Broadcom, consider negotiating them together as a security bundle, separate from, for example, VMware. Smart sub-bundling can strike a balance: you’re not putting everything in one contract, but you are combining related items to drive a better bargain. This way, you avoid a one-size-fits-all deal but still reduce the number of contracts slightly.
• Keep Renewal Increases in Check: Just as with an ELA, fight for renewal caps in individual contract,s too. If you sign a three-year VMware deal, for example, have it say that the year-over-year maintenance or subscription increase cannot exceed a small percentage. Each contract can have its own protection so that Broadcom doesn’t nail you with a huge jump on a product simply because you’re not in an ELA. You might find Broadcom more willing to agree to modest caps on smaller deals, since each is less revenue for them than an entire portfolio – use that to your advantage.

(Example of wording for individual contracts: “Price Protection: Upon renewal of this agreement, any increase in license/subscription fees shall not exceed 3% of the then-current price.”)

In both approaches, the common theme is proactive negotiation. Broadcom’s standard terms will favor Broadcom – it’s up to you to insert customer-friendly provisions, whether in one big contract or several small ones.

Don’t be afraid to push back; Broadcom does expect savvy customers to negotiate hard, especially in the current climate.

FAQs (Frequently Asked Questions)

Q: Does Broadcom force all customers into an ELA?
A: No, Broadcom cannot force you to sign an enterprise license agreement, but they strongly encourage it if they see an opportunity. Broadcom’s sales team often pitches ELAs to large customers using multiple Broadcom products because it benefits Broadcom to lock those in. That said, plenty of customers continue on individual product contracts, especially if they only use one major product line (like VMware alone). Smaller and mid-sized clients, in particular, are not typically pushed as hard for ELAs. Ultimately, it’s your choice – Broadcom might offer incentives (or sometimes threats of higher prices) to corral you into an ELA, but you have to agree to it. If an ELA doesn’t make sense for you, you can and should decline it. Be prepared for Broadcom to continue suggesting it if you’re a large account.

Q: Do ELAs always save money compared to separate deals?
A: Not necessarily. While ELAs are marketed as money-savers through bulk discounts, the actual savings depend on your usage. If you truly use most of the products and capacity in the ELA, you could save compared to buying each piece à la carte (thanks to volume pricing and avoiding incremental purchases). However, many companies end up with shelfware in an ELA – paying for software they don’t fully utilize. In those cases, the “savings” are illusory because you spent money on unused licenses. Additionally, Broadcom might give a great discount initially, but if that ELA forces you to maintain a higher spend than you would have otherwise, you could be overspending in aggregate. Separate deals enable you to optimize spending for each product, potentially reducing your overall spend if your needs are lower in some areas. In short, an ELA can save money if it’s well-tailored and you avoid over-commitment; if not, individual contracts could actually be cheaper because you’re only buying what you need. It’s essential to perform the calculations for your specific situation.

Q: Can I negotiate good discounts on individual contracts if I avoid an ELA?
A: Yes, you can still negotiate discounts on individual Broadcom product contracts – though it requires a deliberate strategy. Broadcom’s willingness to discount will depend on factors like the competitive landscape and the size of the deal. If you’re not taking an ELA, emphasize the competition: for each product, there are alternatives, and you might switch. This pressure can lead Broadcom to offer a more competitive price to keep that portion of your business. You might not get the same ultra-steep discount that a huge multi-product deal could yield, but you can often get reasonable (or even strong) discounts by showing Broadcom you have options. Use benchmarks from the market, leverage your reseller or advisor insights, and don’t accept the first quote you receive. Additionally, if you have a history with the product (such as VMware), reference the discounts you received in the past under VMware’s previous regime and push to maintain something comparable. While Broadcom has tightened discounting, they do make concession,s especially if they fear losing the account entirely. Every separate contract can be negotiated on its own merits – so yes, with effort, you can achieve fair pricing outside of an ELA. Be prepared to negotiate each one and possibly stagger your efforts.

5 Actionable Tips for Choosing Between an ELA and Individual Contracts

Choosing the right model for your Broadcom software agreements is a strategic decision. Here are five concrete tips to guide your thinking and ensure you make the best choice for your enterprise:

1. Benchmark Your Broadcom Spend and Usage: Evaluate how much you’re spending across all Broadcom products today and forecast the next few years. If the combined spend reaches a level where Broadcom will offer an ELA (typically in the multi-millions annually), consider whether the volume discount outweighs the risk. If your spend is relatively low or concentrated in one area, an ELA might not bring enough extra value. In short: know your numbers – an ELA usually only makes sense above certain spend thresholds and when usage is broad.
2. Audit Your Actual Needs Before Committing: Do a thorough audit of what Broadcom software your teams actually use and need. Identify any products that are shelfware or non-critical. This is vital before signing an ELA so you don’t include unnecessary components “just because.” If you proceed with an ELA, scope it tightly to real needs to avoid waste. Conversely, if staying with individual deals, use the audit to possibly eliminate or downsize contracts for underused products. Make data-driven decisions rather than relying on sales promises. A realistic understanding of usage will prevent over-committing in an ELA or even in smaller contracts.
3. Beware of Shelfware – Scope Enterprise Deals Tightly: If you lean toward an ELA, one of your top priorities is to avoid shelfware at all costs. Negotiate the ELA’s product scope and quantities so that you’re not paying for hypothetical future needs that never materialize. It’s often better to sign a smaller ELA and later expand if needed (Broadcom will always take more money later) than to sign a huge ELA and under-utilize it. Ensure every product in the bundle has a clear stakeholder and expected use case internally. If something is included “for potential use,” scrutinize that heavily. By scoping tightly, you not only save money but also make renewal easier because you can show that value was realized.
4. Use Staggered Contracts to Your Advantage: If you opt for individual contracts, plan the renewals in a way that maintains leverage. Stagger them so you’re never up against renewing everything at once, which could overwhelm your negotiation resources. With staggered timings, you can also experiment: for example, this year you might trial an alternative product in one area. At the same time, another Broadcom contract runs its term, keeping the vendor on its toes. Staggering can also prevent Broadcom from coordinating its pricing strategy across your contracts (less chance of a unified front from them). The goal is to preserve leverage and optionality – each renewal presents an opportunity to improve terms or pivot if needed. Manage the timeline so that you’re not backed into a corner with multiple critical contracts expiring simultaneously unless by design.
5. Always Negotiate Protections – No Matter the Model: Whichever path you choose, don’t accept Broadcom’s first offer as-is. For an ELA, negotiate growth buffers, price caps, and clearly documented entitlements. For individual deals, negotiate renewal caps, favorable payment terms, and ensure you have exit ramps if needed. Never assume that a friendly relationship will protect you later – get it in writing. If you’re a smaller customer, you might think you have little power, but even so, ask for things like a reasonable notice period for any price changes or a right to reduce licenses at renewal without penalty. For larger deals, definitely incorporate the protections we discussed earlier. These negotiated safeguards can save you millions or at least prevent headaches down the road. It’s much easier to negotiate upfront when Broadcom wants your signature than to fix a bad deal mid-term or at renewal.

By following these tips, you’ll be better prepared to choose the contract structure that fits your enterprise and to negotiate terms that mitigate risks.

The key takeaway: an informed, well-planned approach is your best defense against unfavorable outcomes.

Broadcom’s contracts are complex and can be skewed in their favor. Still, with due diligence, you can strike a deal that serves your organization’s interests, whether that’s through an all-encompassing ELA or a set of tailored individual agreements.

Read about our Broadcom Negotiation Service.

Do you want to know more about our Broadcom Negotiation Services

Please enable JavaScript in your browser to complete this form.

Name *

Email *

Company

Message *

Submit