Renewing a Transport Management SaaS Contract
A freight forwarder’s transport management SaaS contract costs £1.1 million a year. The three-year term ends in six weeks and auto-renews unless notice is given 30 days before expiry. The vendor proposes an 18% uplift, citing new AI routing modules. Usage data shows only 58% of licences are active, three of seven modules are unused, and API overage charges were £84,000 last year. A competitor has quoted £980,000 a year, but implementation would take five months and carries integration risk with the company’s warehouse system. The forwarder’s peak season starts in 10 weeks and downtime is unacceptable. The vendor’s account team is behind on its quarterly target. The internal sponsor wants a quick renewal and has asked procurement to “just get the price down”.
1. Prepare the negotiation: identify interests, BATNA, ZOPA and the information you still need.
Read the worked answer
Interests. The vendor needs a signed renewal before quarter-end and wants to protect recurring revenue. The forwarder needs uninterrupted service through peak season, integration stability and a lower cost base. The internal sponsor wants speed, but speed should not mean accepting an 18% increase.
BATNA. The forwarder’s short-term BATNA is weak: the competitor cannot implement in 10 weeks, and a switch during peak would be reckless. The medium-term BATNA is stronger: a five-month implementation could be complete before the next renewal, so the credible threat is “we will run a competitive implementation after peak”, not “we will switch next month”. Communicate that, not a bluff.
ZOPA. An 18% uplift is unlikely to be inside the zone. The vendor’s real economics are probably closer to a modest increase plus recovered overage revenue. A realistic zone is roughly flat to a 5% increase on a right-sized licence base, with the vendor gaining term certainty and a reference. At £1.1m, each 1% is £11,000; the competitor quote is 11% below current spend, so the vendor must explain why its value is higher.
Information needed: contract notice provisions and auto-renewal wording; licence metric definitions; API overage calculation; roadmap evidence for AI modules; benchmark pricing; implementation plan and exit costs; data ownership and portability; peak-season service credits. Also confirm who has authority to give notice - waiting until the 30-day deadline removes options.
2. Design a concession plan and negotiation sequence that protects peak-season service while reducing cost.
Read the worked answer
Sequence: first, give notice or secure a written extension to prevent auto-renewal on the vendor’s terms. Then separate the negotiation into commercial, scope and risk workstreams. Do not open with a single price demand; open with a data-led review of unused licences and modules.
Opening: present the usage evidence - 58% active licences, three unused modules, £84,000 API overage - and propose a right-sized subscription. Ask for a 12-month bridge at current price while a competitive evaluation runs, or a three-year deal at a lower unit price.
Concessions to trade:
- Term: offer three years for price stability, but only with a price cap and a break clause.
- Payment: offer annual upfront payment in exchange for a discount, subject to cash-flow approval.
- Reference: offer a case study or reference call in exchange for commercial improvement.
- Scope: accept a defined AI pilot, but not a mandatory paid module.
Concessions to seek: licence right-sizing; API overage cap or bundled allowance; implementation support at no cost; service credits for peak-season downtime; 3% annual cap; data portability and exit assistance; no automatic renewal without 60 days’ notice.
Walk-away: if the vendor insists on 18% and refuses usage-based pricing, sign a short interim extension at current terms, run the competitive process properly and prepare a transition plan after peak.
3. Recommend the contract terms and internal actions needed to prevent a repeat of the renewal problem.
Read the worked answer
Contract terms: replace auto-renewal with an affirmative renewal decision at least 90 days before expiry; define licences by named user or active use, not by a broad enterprise metric; cap annual increases; include an API usage allowance and transparent overage rates; require roadmaps and module retirement notice; add service credits, disaster recovery and security obligations; guarantee data export and transition assistance; include benchmarking or most-favoured-customer rights.
Internal actions:
- Create a renewal calendar with 120-day, 90-day and 60-day milestones; assign ownership to procurement, not only IT.
- Establish a licence management process: quarterly usage reports, reclamation of dormant accounts, module reviews.
- Align the internal sponsor before negotiations. Explain that “just get the price down” is weaker than a right-sizing and competitive-position strategy.
- Build a total-cost model including integration, training, overage and transition, not just subscription price.
- Run a post-peak competitive evaluation even if the incumbent is retained; this creates a credible future BATNA.
- Brief legal on the notice date immediately so the auto-renewal clause cannot silently bind the company.
The lesson is governance, not just negotiation: the vendor exploited a late start, weak usage data and an unclear decision date. Fixing those three issues is worth more than a one-off discount.