The support tier lever most Broadcom buyers leave on the table.

Every Broadcom renewal carries a line for support. On most quotes that line is a percentage of the licence total: 22 percent for the standard tier on perpetual paper, 25 to 28 percent for the enhanced tier on subscription. On a $20M VCF subscription the support line is a $5M annual cost. The buyer rarely opens it. The buyer rarely tests whether the tier the contract was placed in still matches the operational reality. The buyer almost never moves the contract to a different tier at renewal. That last failure is the lever this article is about.

The Desk's working number, across more than 30 Broadcom renewals we have measured, is that 74 percent of buyers are paying for a support tier that is meaningfully richer than their operational consumption requires. The buyers we are describing are not under supported. They are over supported. They bought the tier their seller recommended at signature, they have not revisited the tier since, and the seller has had no commercial reason to recommend they revisit. Moving the contract to the correct tier at renewal is a single line edit on the order form. The recovery on the renewal commercial total runs between 6 and 14 percent.

Why the tier rarely moves

The seller's incentive structure is clear. The support attach is part of the seller's quota credit, the support margin is high, and the support tier is the place on the order form where the seller can grow the deal without changing the licence count. At signature, the recommendation is always the higher tier. The recommendation is presented in operational terms (faster response, named technical account manager, premium escalation) rather than commercial terms (an extra 6 percent of the deal size for the life of the contract).

The buyer's side has equally clear reasons not to revisit. Internal IT operations rarely surface the support tier as a renewal issue because the operational benefits, even if marginal, are real. Procurement does not have the operational data to challenge the recommendation. Finance treats the support line as a fixed overhead because that is what it looks like on the page. The conversation about whether the tier is right never gets initiated by anyone on the buyer side. The seller has no reason to initiate it either. So the tier sits.

How to test whether the tier is right

The test is mechanical and the data exists inside the buyer. Pull the actual support cases opened against the contract in the last 24 months. Count them. Bucket them by severity. Bucket them by resolution time. For each case bucket, look at what the lower tier would have promised in service level. The Desk's standing recommendation is that any contract where fewer than 8 percent of cases required the response promise of the enhanced tier is a contract paying for a tier it does not need.

"The support tier is the largest single line of soft margin in the Broadcom portfolio. It is also the easiest line to test. Three weeks of internal case data work, and the buyer knows whether the tier is right."Operations Lead, The Desk

On a Symantec endpoint renewal we worked through the first quarter of FY26, the buyer's case data showed that across 24 months of operation, only 4 percent of opened cases had required the response window that the enhanced tier delivered. The standard tier would have met the buyer's operational need on the remaining 96 percent. The buyer moved the contract to the standard tier at renewal. The annual saving was $1.4M on a $13M total. Three weeks of internal case data work, paid back at multiples.

The negotiation, when the tier moves

The seller will resist the move. The resistance comes in a predictable shape. First, the seller will claim that the tier change requires a re scoping of the entire renewal. It does not. The tier change is a single line edit on the order form. Second, the seller will warn about operational risk. The warning is genuine in the abstract and almost never material in the specific. The buyer's case data is the answer. Third, the seller will offer to hold the higher tier at a small discount as a compromise. The discount is rarely worth the difference between the two tiers. The Desk's standing recommendation is to decline the compromise and move to the lower tier cleanly.

The seller's final fallback is to suggest that the lower tier comes with response windows that the buyer's existing operational SLAs to internal stakeholders cannot meet. This is often true on paper and almost always negotiable in practice. Internal SLAs to stakeholders can be adjusted. The cost of adjusting them is a conversation with the stakeholder. The cost of staying on the wrong tier is six or seven figures a year for the life of the contract. The conversation is the cheaper option in almost every scenario we have run.

When the buyer should stay on the enhanced tier

The enhanced tier is the right answer in three scenarios. First, regulated environments where the documented response window is itself a compliance requirement. Second, deployments where the application is in the customer's revenue path and an outage above a defined duration causes a financial loss that exceeds the tier price difference. Third, deployments where the buyer's own internal support function is not sized to handle first line response and the named technical account manager is, in effect, a piece of the buyer's operational team. Outside those scenarios, the enhanced tier is almost always a place the buyer can recover money at renewal.

The case data work distinguishes the three scenarios from the general pattern cleanly. If the actual case mix shows a meaningful share of cases that hit the enhanced tier window and would have failed the standard tier window, the tier is right. If the share is below 8 percent and the buyer is not in a regulated environment, the tier is wrong. The data does the work the conversation cannot.

What we have seen on live deals

Across the last 10 Broadcom engagements the Desk has closed, the support tier was tested as a named lever on six of them. In five of the six, the case data supported moving the contract to a lower tier. In the sixth, the case data supported staying where the contract was, which is itself a useful answer because it removed the question from the rest of the negotiation. On the five tier moves, the average recovery against the renewal commercial total was 9.6 percent. On a $40M VCF renewal that is $3.8M a year. Verified against signed contracts.

The four engagements where the tier was not tested as a named lever were, in retrospect, the engagements where the largest single piece of soft margin on the renewal was left on the seller's side of the table. None of those four buyers were satisfied with the final commercial outcome. All four said, at debrief, that the tier was a place they should have looked and did not. The work is real. The work is not difficult. The work needs to be done before the first commercial meeting, not during it.

The pattern is identical across the Broadcom portfolio. We have seen the same tier oversizing on Carbon Black, on CA, on mainframe, and on Brocade. The product changes. The shape of the lever does not. The buyer who runs the case data exercise on every product line in the portfolio recovers, on the aggregate, the largest single line of soft margin available in a Broadcom commercial relationship. The buyer who runs it on no product line leaves that margin on the seller's side of the table for the life of every contract in the estate. The cost of the exercise is the same in both cases. The outcome is not.

The takeaway

• Pull 24 months of support case data before the renewal opens. Bucket cases by severity and by what response window each one required.
• If fewer than 8 percent of cases required the enhanced tier window and you are not in a regulated environment, the tier is the lever. Move the contract.
• Expect the seller to resist in three predictable shapes. The case data is the answer to all three. Decline the compromise. Move to the lower tier cleanly.