Full narration of the briefing. Click a section heading to jump the player to that moment.
Everything so far has been context. This is the episode where we sit down at the table. And the first thing to understand about a VMware deal is that you are not signing one agreement, you are signing a stack of them, and most buyers negotiate only the top one. I am Tom, Daniel is with me, and we are going to go through what governs, what to ask for, the order to ask in, and what to give away on purpose.
Because in this deal, what you concede deliberately is worth more than what you resist.
So, the stack. There is a base end user licence agreement. Underneath it, a Specific Program Documentation for each product, which sets out what that product may actually do and where. Then the order form terms, which is where the commercial specifics live.
Then service descriptions for anything delivered as a service. Four layers at least, sometimes more. And the critical point is the order of precedence: in this structure the lower, more specific documents generally override the general one above them. So the protections you negotiated into the master agreement can be quietly undone by a product document nobody read.
Four asks, in this order. First, verify the core count, per processor, against the sixteen core minimum, because that number is the entire basis of the price and it is wrong more often than anyone admits, on both sides. Second, the cure period we talked about last episode: thirty days to correct a reporting failure before any penalty or product degradation applies. Third, a cap on the renewal increase at the end of this term, expressed as a percentage, because there is no default protection whatsoever.
Fourth, flexibility to reduce, whether that is a step down right or a true down at anniversary.
Now, what to trade. Broadcom wants three things badly, and you should know their relative value. It wants term length, because that fills the backlog it reports to the market. It wants payment up front, because that is cash.
And it wants the commitment to be non cancellable, because revenue recognition depends on it. Those are all expensive for you to give and valuable for them to get, which is exactly what makes them good currency. So do not resist a three year term for free. Sell it, for the cap and the cure period.
The mistake is fighting every point and therefore being paid for none of them.
Two dates decide how this goes. Theirs is quarter end, and CA's own filing confirms a substantial portion of agreements are executed in the last month of a quarter. Yours is the support horizon, with vSphere 8 general support ending around October 2027, which is very likely earlier than the renewal you are planning around. Work backwards from that horizon, and if you can, land the negotiation in the last weeks of their quarter rather than the first.
Those two facts together are worth more than any argument you can make about fairness, because one of them is their constraint and the other is a real deadline rather than an invented one.
Three traps to check before signature. The renewal anniversary date, because missing it carries a twenty percent surcharge that is still in force, so the date itself needs to be diarised at board level rather than in somebody's inbox. The audit and compliance reporting terms, including who pays for an audit and what triggers one, which should sit with the vendor unless a material shortfall is found, with material defined in numbers. And every Specific Program Documentation for every product you are buying, because that is the layer where use rights get narrowed and where the protections above it get overridden.
So the sequence. Establish your position before you ask for a number: know your cores, know your deployment against your entitlement, and know your support horizon. Then negotiate the paper, the cure period, the cap, the flexibility and the product documents. Only then negotiate price, because a discount on a contract with no cap and no cure period is a discount you will hand back at the next renewal with interest.
Position, paper, price, in that order. Next time, Claire and I do the same thing for the mainframe deal, where the mechanics are different and the stakes compound faster.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Broadcom negotiator