The exit plan that changes the renewal.
The seller's strongest position on a Broadcom renewal is the same position they had at acquisition. There is nowhere else for you to go in the timeframe you have. The reason that position works is that almost no buyer arrives at the renewal table with the migration math actually done. Vague references to alternatives count for nothing against a quote on the table and a deadline on the calendar. A written, costed, time bounded exit plan, signed off internally, changes the conversation completely. Even if the buyer never uses it.
The work is five weeks. Week one is target selection. We map the realistic alternative pathways for the specific product in scope, by workload, by region, by integration footprint. Week two is the actual migration economics. The cost of moving, the cost of running parallel, the residual liability on the existing contract, the time to first benefit. Week three is the timeline. The phasing, the dependencies, the resourcing model. Week four is the internal sign off. The plan goes through CFO and CIO review and becomes a real document, not a slide. Week five is posture. We tell you exactly how to use the plan in the renewal conversation, and how not to.
The seller can usually tell the difference between a buyer who is posturing and a buyer who has the work done. The posture talks about alternatives in general terms. The buyer with the work done can cite the year one cost, the cutover date, the residual liability number, the workloads moving first. The seller's pricing model assumes the second buyer needs a much smaller concession to stay than the first buyer does to leave. The economics of the renewal restructure to reflect that, and the buyer captures the value whether or not they actually exit.
Most of the exit plans we have built have not been executed. They were not designed to be. They were designed to change the renewal that came back. Read the case below for one example on a VMware exit that became a renewal.