The Vendor Who Owns the Roadmap
A manufacturing group spends 22% of its software budget with one vendor across ERP, analytics and a middleware layer that connects them. The contract auto-renews in 8 months with a 6% uplift and a 60-day notice period. The vendor has proposed a three-year enterprise agreement with a 12% discount on list, bundled support, and a 'true-up at the end of term' clause. Internally, the group is planning a cloud migration that may retire the middleware within 24 months, and a merger with a smaller competitor is under regulatory review. The vendor account team knows about neither the migration nor the merger.
1. What is the SAM lead's negotiation strategy, and what should not be conceded?
Read the worked answer
The strategy is to convert a vendor-favourable renewal into a term that matches the group's uncertain future.
Leverage to build:
- Quantify actual consumption against entitlement across all three product areas. Bundled enterprise agreements often price on assumed growth; if consumption is flat, the discount may still be a price rise.
- Model the 6% uplift against the 12% discount: a discount on a list price the group does not pay is not a saving. Compare total cost of ownership over three years, not headline discount.
- Establish alternatives: competing analytics and middleware options, and whether the middleware can be retired earlier than 24 months.
Do not concede:
- The end-of-term true-up as drafted. It lets the vendor charge retroactively for growth at undefined prices. Cap it, define the measurement, and set the price per unit in advance.
- A three-year lock with no exit. The migration and merger make a long term risky. Seek a shorter initial term, a termination-for-convenience right with defined cost, or a merger/divestiture clause.
- Auto-renewal on the current notice period. Diarise the 60-day date now and seek a longer notice window.
Do not disclose the migration or merger to the vendor before the group has decided how to use them. Disclosure is a lever; giving it away early strengthens the vendor's hand.
2. How should the merger and cloud migration be handled in the contract, and what is the risk if they are not?
Read the worked answer
Both events change the licensing footprint, and a contract silent on them transfers the risk to the buyer.
Merger:
- Seek a change-of-control and affiliate clause that lets the combined entity use licences across the group without a new charge, or with a defined and pre-agreed adjustment.
- Confirm whether the target's existing licences can be retained or must be re-purchased. Double-paying for the same capability is a common post-merger loss.
- Address divestiture too: if the group must sell a business, it needs a right to split licences.
Cloud migration:
- Confirm the licensing metric survives the move: per-core, per-user and per-server terms can behave very differently in cloud, and some vendors require a separate cloud price list.
- Get written confirmation of the permitted deployment model and any bring-your-own-licence rules.
- If the middleware may retire, avoid minimum commitments that outlive it.
Risk if unaddressed: a three-year commitment signed on the current footprint could require payment for capability the group no longer runs, plus a true-up for the merged estate, plus re-purchase of the target's licences. That is three separate overpayments from one signature.
Judgement being tested: the SAM lead's value in negotiation is anticipating structural change and pricing it into the terms before it happens, not negotiating the discount.