Structuring Ramp-Up Pricing in Broadcom Contracts
Introduction – Why Ramp-Up Pricing Matters
Broadcom’s software contracts (from VMware to Symantec to CA) often push customers toward large upfront commitments. However, savvy procurement teams know that paying for tomorrow’s licenses today is a recipe for overspending. Read our guide to Maintaining License Flexibility with Broadcom: Co-Termination, True-Downs, and Ramp-Up Pricing.
Ramp-up pricing – a phased pricing model where license volumes and costs increase gradually in line with actual deployment – is a crucial strategy to align spending with usage. This approach prevents budget shock and shelfware by phasing license costs with real adoption.
Broadcom is familiar with ramp-up structures (inherited from CA and VMware’s legacy practices), but they won’t volunteer it. Buyers must proactively introduce ramp-up pricing in negotiations to avoid paying for 100% of licenses on day one when only a fraction are in use.
In short, ramp-up pricing protects you from overpaying upfront and ensures Broadcom’s revenue is tied to your deployment timeline, not an aggressive sales target.
How to Define a Ramp Schedule
Defining a clear ramp-up schedule is the first step in proposing phased deployment pricing. Start by mapping out your expected growth curve: for example, Year 1 as the baseline deployment, Year 2 for expansion, and Year 3 for full rollout. Be realistic – use project plans or migration timelines to justify these figures. Once you have a projection, lock in the unit pricing across all ramp years.
If a license costs $X per unit, that price should remain $X in Year 1, Year 2, Year 3, and so on. This fixed unit price ensures you’re not hit with cost escalations in later years. Broadcom might attempt to raise prices for future years or apply separate discounts per phase – resist this. Instead, build the explicit volume and pricing schedule into the contract early in negotiations.
For instance, specify that you will purchase 500 licenses in Year 1, 800 in Year 2, and 1,000 in Year 3, all at the same per-unit rate. By defining the ramp-up plan clearly and early, you set expectations that your spend is tied to actual usage milestones.
Read about aligning contracts, Aligning Global & Division Broadcom Contracts for Flexibility.
Contractual Protections
Simply having a ramp schedule isn’t enough; you need contractual safeguards to ensure Broadcom adheres to it. Insist on an explicit ramp-up schedule in the contract that details the license quantities, dates of ramp increases, and the fixed pricing. The contract should state that future-year license commitments cannot be billed or demanded upfront – you only pay when each phase begins.
This prevents Broadcom from invoicing Year 3 licenses in Year 1 “by mistake” or pressuring you to accelerate purchases. Another protection to negotiate is a delay clause or cushion.
Projects slip for countless reasons, and if your deployment is delayed, you don’t want to be forced to buy licenses you won’t use on the original schedule. Try to include language that states if a phase is delayed by, say, 3-6 months, the ramp schedule can be adjusted without incurring penalties. (Admittedly, Broadcom may resist this, but it’s worth attempting, especially if your rollout has known risks.)
Also, ensure any volume discount or pricing deal applies across the entire ramp. The discount you negotiate for the full volume should not reset annually or disappear in later phases.
For example, if you got a 20% discount based on the commitment to reach 1,000 licenses, you should be getting 20% off in Year 1 on 500 units, not just when you hit the final volume. All these protections boil down to one theme: align payment with performance – you pay as you go, not in advance.
Read about How to Negotiate True-Down Provisions in Broadcom Contracts.
Example Ramp-Up Pricing Table
To visualize the benefits of ramp-up pricing, consider a simple three-year example:
Year | License Count | Unit Price | Total Cost |
---|---|---|---|
Year 1 | 500 licenses | $X per license | $500 * X |
Year 2 | 800 licenses | $X per license | $800 * X |
Year 3 | 1,000 licenses | $X per license | $1,000 * X |
In this illustration, the unit price $X remains constant across all three years.
The organization doesn’t pay for the full 1,000 licenses until Year 3, when they actually reach that usage level.
Key points: The per-unit price is locked from the start, so there are no surprises or price hikes in later years. The total cost grows as the deployment grows, aligning budget spend with actual adoption.
It’s also wise to confirm that the cumulative total cost over the 3-year ramp matches what was agreed (e.g., 2,300 licenses * $X in total across all years, in this example).
This ensures Broadcom doesn’t slip in hidden costs or exceed the expected budget over the term. A ramp-up table, similar to the one above, can be included in the contract or as an exhibit, making the agreement crystal clear.
Negotiation Tactics for Ramp-Up Pricing
Convincing Broadcom to accept a ramp-up pricing model requires positioning it as a win-win.
Here are tactics to strengthen your case during negotiations:
- Frame Ramp-Up as Risk Sharing: Emphasize that ramp-up pricing is a fair compromise. You, the customer, commit to a growth plan (guaranteeing Broadcom’s future revenue), and in return, Broadcom agrees to earn that revenue in step with your actual implementation. This shared risk/reward shows good faith from both sides.
- Leverage Deployment Realities: Bring Hard Data to Justify the Ramp. If you’re migrating data centers or rolling out in phases (e.g., a VMware Cloud migration across multiple sites), please provide Broadcom with the timeline. For example, “We won’t even have servers ready for those 500 extra licenses until Q3 next year.” When you tie the ramp to real project milestones, it’s a logical ask, not an arbitrary delay.
- Offer a Larger/Longer Deal: Broadcom loves big numbers. If you need to sweeten the pot, consider offering a longer contract term or a higher total license commitment – but only in exchange for the ramp-up structure. For instance, agree to a three-year term (instead of one year) if they allow phased purchasing, or commit to a slightly larger end-state volume if they let you pay as you grow. This can turn the ramp ask into an opportunity for Broadcom to secure a bigger long-term deal.
- Be Prepared for Pushback: Broadcom sales representatives may initially push for full deployment licensing from day one (to maximize immediate revenue). Stand firm and reiterate that paying for unused licenses is a non-starter for your organization. If needed, share internal policies or budget constraints that prohibit spending on shelfware. Sometimes, simply making it clear that you cannot do the deal without a ramp schedule will prompt the representative to seek exceptions or approvals to accommodate it.
- Use Competition and Alternatives: If Broadcom senses that you have no choice, they’ll be less flexible. Casually mention that you’re evaluating phased approaches with other solutions or that the project could be re-scoped if costs are too front-loaded. Without making direct threats, let Broadcom wonder if inflexibility might jeopardize the deal. The possibility of losing the deal entirely can make ramp-up pricing more palatable to them.
Risks Without a Ramp-Up Provision
Failing to secure ramp-up pricing can have serious downsides for your organization:
- Paying for Shelfware: The most obvious risk is financial waste. If you commit to 100% of licenses on day one but only use 50% in the first year, the rest sit idle as “shelfware.” You’ve effectively donated money to Broadcom for nothing in return (until later, if ever).
- Budget Overruns and Shock: Upfront licensing for full deployment can significantly exceed your Year 1 budget. It concentrates what should be three years of spending into the first year. This not only causes budget strain but also can lead to unpleasant surprises in financial reviews. CFOs hate seeing huge outlays for software that isn’t being utilized yet.
- No Flexibility for Delays: If your project slips or priorities change, without a ramp-up, you’re locked into a rigid payment schedule. Imagine a rollout planned for six months that ends up taking eighteen. With no ramp clause, you would have already paid for the final phase long before it’s actually implemented – and Broadcom won’t be keen to give that money back. You lose leverage once the contract is signed and paid.
- Pressure to Deploy Faster: Ironically, paying upfront for all licenses can pressure IT teams to rush deployments to “get their money’s worth.” This can lead to sloppy implementations or misaligned priorities (deploying features not because you need them now, but because you already paid for them). Ramp-up removes that artificial urgency, letting the deployment proceed at a sensible pace.
- Overcommitting to Volume: Without a phased approach, you might also overestimate needs. Locked into a high-volume contract, you could end up with more licenses or capacity than you ever actually require. In contrast, ramp plans often allow a course-correction in later phases if actual usage trends are lower than initial forecasts (via smaller true-ups or simply leveling off at the final phase).
Fallback Strategies if Broadcom Refuses Ramp-Up
Despite your best efforts, there’s a chance Broadcom simply refuses to incorporate a ramp-up schedule. If that happens, don’t surrender – consider these fallback approaches:
- Shorter Contract Term: If Broadcom insists on all licenses up front, counter by limiting the contract term. For example, opt for a 1-year deal for the initial phase only. This way, you pay for what you need now and retain the option to negotiate the next phase later. Broadcom won’t like a short-term (they prefer multi-year commitments), which might pressure them back to the table to discuss a phased approach. However, if they won’t budge, a 1-year contract limits your exposure and allows you to reassess after Year 1.
- Price Caps on Future Expansion: Another compromise is negotiating a price cap or fixed discount for future purchases. If they won’t agree to a pre-scheduled ramp, at least have them commit to purchasing any additional licenses in Years 2 or 3 at the same unit price (or discount %) as the initial purchase. Essentially, you’re securing the option to buy later at a predictable cost. This isn’t as good as not paying upfront, but it prevents Broadcom from price-gouging you on future true-ups or expansions.
- Stage the Project with Alternatives: Explore whether you can phase your implementation using alternative solutions or interim measures to reduce reliance on a full Broadcom commitment. For instance, if Broadcom won’t ramp up the VMware licenses, you may consider keeping a portion of your workloads on existing infrastructure or a different platform for an extra year, then integrating them later. In the security space (Symantec), you may initially migrate only a subset of users and use another tool for the rest until Broadcom’s terms are acceptable. These approaches can be complex, but they give you leverage – you show Broadcom that you have a plan B for phased adoption if they won’t cooperate.
- Escalate or Bundle Deals: Sometimes, vendor reps have limited approval authority. If a sales representative flatly refuses to ramp up, consider escalating the issue to their management or Broadcom account leadership. Present your case that a phased approach is the only viable path. You might bundle the ask with other negotiations – for example, “We’ll consider expanding the scope to include another Broadcom product if you allow a ramp on this one.” Broadcom’s broad portfolio can be a bargaining chip; just be careful not to over-commit elsewhere as a trade-off.
Sample Contract Clause Language (Plain English)
When you get Broadcom to agree to ramp up terms, ensure the contract language is unambiguous.
Here are some plain-English clause examples that capture the intent:
- Ramp Schedule: “Customer will license 500 units in Year 1, 800 units in Year 2, and 1,000 units in Year 3. The per-unit price is fixed at $X for the duration of this agreement.” – This clause lays out the phased quantities and locks the price. It ensures that both parties are aware of the timeline and cost.
- No Early Billing: “Broadcom will invoice each year’s licenses no earlier than 30 days before the start of that year’s deployment phase. Unused future-phase licenses will not be billed in advance.” – This prevents Broadcom from charging everything upfront or too early. It ties payment timing to deployment timing.
- Delay Flexibility: “If deployment of a planned phase is delayed by more than 3 months due to Customer’s business needs or project issues, the parties may mutually agree to defer the ramp schedule for that phase by up to 6 months without penalty.” – While getting this clause might be challenging, it gives you some breathing room if things go off schedule, without being in immediate breach.
- Pricing Lock: “Unit pricing shall remain fixed across all ramp years regardless of volume increases or inflation. No annual price escalators shall apply to the committed units.” – This explicitly states that even in later years, Broadcom can’t tack on inflationary increases or claim the discount expired. The price you agreed on is the price you pay, period.
- Discount Consistency: “Any discount percentage off list price negotiated for Year 1 shall apply equally to the units in Years 2 and 3.” – If your deal is structured around a discount off list, this ensures the same level of discount in subsequent purchases. It’s another way of saying the same thing as a fixed price, but in terms of a discount rate.
Ensure that clauses like these are reviewed by your legal team and clearly understood by both parties. Vague language is the enemy of a good ramp-up deal – you want precise numbers, dates, and commitments.
Checklist – Ramp-Up Must-Dos
Before finalizing your Broadcom contract, run through this checklist to ensure your ramp-up pricing is rock solid:
- ✔ Deployment Timeline Defined: The contract includes a clear timeline (by date or by contract year) for each phase of license deployment.
- ✔ Fixed Unit Pricing: The per-unit license cost is locked for all phases. You won’t face price hikes in later years.
- ✔ Documented Ramp Schedule: The exact quantities for each phase are written in the contract, not left to a verbal understanding.
- ✔ Delay Cushion: There’s provision for schedule flexibility if your project is delayed (even if it’s just the right to discuss adjustments without immediate penalty).
- ✔ No Front-Loading Charges: Language confirms that future phase licenses will only be billed at the time of that phase (or just before), not all upfront.
- ✔ Consistent Discount or Cap: If using a discount percentage, it’s consistent through all years; if not, there’s a cap on any future pricing to avoid surprises.
- ✔ Total Cost Cap: Ensure the total cost over the full term is either stated or can be calculated from the schedule, and it aligns with your budget expectations (no hidden fees).
- ✔ Management Buy-In: Internally, all stakeholders (finance, CIO, project manager) are aware of the ramp terms and are prepared to stick to the deployment plan or communicate if plans change.
This checklist serves as your safeguard – if any one of these items is missing, you risk Broadcom exploiting that gap later.
FAQs
Q: Does Broadcom allow ramp-up pricing in contracts?
A: Broadcom won’t advertise it, but they do allow ramp-up structures if you negotiate firmly. Many legacy CA and VMware contracts had flexible deployment terms. You need to bring it up early and make it a condition of the deal. Expect pushback – Broadcom’s default stance is to generate revenue sooner – but they understand what a ramp-up entails and have agreed to it for strategic customers.
Q: How much of a delay or cushion can I negotiate for the ramp?
A: It varies. Broadcom is generally reluctant to grant long delays. A modest cushion, like 3-6 months, is more achievable than an open-ended delay. For example, you might obtain a clause allowing for a one-time 3-month extension of a phase if implementation is running behind schedule. Use specific justification when asking (e.g., “Our data center build got postponed by a quarter; we need a matching license ramp delay”). The key is to ask – if you don’t include any cushion, there’s zero flexibility.
Q: Can the unit price increase in later years of a ramp?
A: Not if you negotiate correctly. Your goal is a flat unit price throughout the term. Broadcom might suggest a small uplift in years 2 or 3 (citing “standard” annual increases or inflation). Don’t accept that. In a true ramp-up deal, you’re earning them guaranteed future business, so the price should remain constant (or even decrease if you hit higher volumes). Lock it in writing. If Broadcom absolutely insists on an increase, treat it as a major concession and push for something in return (like a bigger discount to start with, or an extended term).
Q: What if our rollout is delayed by a year or more?
A: If you anticipate significant uncertainty, be upfront about it. Without any contract protections, a year-long delay would mean you’re stuck paying for resources you’re not using. In such a scenario, try to negotiate phase commitment windows rather than fixed dates (e.g., “Year 2 licenses to be delivered anytime between Month 13 and Month 24 at the customer’s request”). If the wheels completely come off (resulting in a 12+ month delay) and you lack specific clauses, you might be forced to renegotiate the contract midstream or face paying for the idle licenses. Neither is a great outcome, so it’s crucial to incorporate as much flexibility as possible from the start. In extreme cases, a partial termination right for unused portions could be explored, but Broadcom is likely to resist that vigorously.
Q: Will ramp-up pricing reduce the overall cost of the deal?
A: Indirectly, yes. Ramp-up itself is more about payment timing than a discount; you’re committing to buy the full amount eventually. However, by not front-loading the purchase, you avoid waste and improve cash flow. You may also be able to negotiate a better discount by committing to a larger volume over time. The total over 3 years in a ramp deal should be equal to or less than a one-shot purchase when you factor in the time value of money and avoided maintenance on shelfware. So while Broadcom might claim you’re paying the same total, the reality is you’re optimizing your spend and reducing risk – which is a financial win.
5 Tactical Recommendations for Negotiating Ramp-Up Pricing
To wrap up, here are five tactical recommendations to remember when structuring ramp-up pricing in your Broadcom contract:
- Tie Ramp to Your Roadmap: Anchor the ramp schedule to your real deployment roadmap or migration plan. A ramp-up deal should have credibility – Broadcom is more likely to agree if the phased approach clearly mirrors how you will actually roll out the technology.
- Lock the Price Upfront: Nail down the per-unit price (or discount %) at the very beginning. Do not assume you can “sort out Year 2 pricing later.” If it’s not fixed on day one, you’ll have no leverage when Year 2 arrives. Include the fixed price in the initial proposal.
- Put the Schedule in Writing: Verbal promises won’t cut it. Ensure the final contract explicitly lists the ramp schedule (volumes and timing). This document should serve as your safety net in case personnel change or memories fade regarding what was agreed upon. Without it, you’re at Broadcom’s mercy later.
- Negotiate a Delay Safety Net: Even if it’s a small one, get some form of project delay protection. Having the ability to push back a phase if needed can save your budget if things go wrong. It’s better to have it and not need it than to need it and not have it. Broadcom won’t volunteer this – you must request it.
- Refuse Front-Loaded Deals for Phased Needs: Be willing to say no to a deal that forces 100% upfront if your usage is clearly phased. It can be tempting to take the path of least resistance, but caving in can cost your organization dearly. Stand your ground that any phased deployment must have phased pricing. Broadcom will respect a well-reasoned stance if you stick to it.
By following this playbook, procurement teams and IT leaders can structure Broadcom contracts that align costs with actual adoption.
Ramp-up pricing requires determination and savvy negotiation, but the payoff is huge: you protect your budget, avoid paying for unused licenses, and maintain flexibility as your organization grows into the new solution.
In the face of Broadcom’s aggressive sales tactics, a ramp-up pricing strategy is a powerful tool to keep the vendor honest and your deployment on track. Enjoy the phased journey without the financial hangover!
Read about our Broadcom Negotiation Service