Contract Season: Seven Questions That Reshape Vendor Renewals Before You Sign
Photo by Photo by Pawel Chu on Unsplash on Unsplash
Vendor renewals follow a predictable script. The contract lands in your inbox thirty days before expiration, the discount is framed as urgent, and the signature happens under time pressure that the vendor's calendar created. The result is that most enterprises renew on terms they never examined — and discover the expensive clauses eighteen months later, mid-incident.
The antidote is a standing list of questions asked well before renewal season, when you still have leverage. Here are seven that consistently change the conversation.
1. What does it cost to leave?
Egress and export fees are the quiet backbone of vendor lock-in. Ask for the total dollar cost of extracting 100% of your data and configuration on the day after renewal. Vendors who hesitate here are telling you something. A strong answer is a specific number and a documented export path; a weak answer is 'there's an API for that.'
2. Is the renewal discount a price lock or a lure?
Many promotional discounts apply to year one only, with renewal-year pricing reverting to list — plus an escalator. Demand multi-year pricing in writing, including the annual uplift percentage. Anything above 5% annually deserves negotiation; anything unstated deserves suspicion.
3. What happens to our data when the contract ends?
Data portability guarantees should specify format, completeness, and timeline. 'Machine-readable export' is not a guarantee — ask whether associated metadata, relationships, and history are included, and how long the vendor retains access after termination. US data-residency and deletion obligations belong in this answer, not in a follow-up email.
4. What exactly does the SLA cover — and what is the actual remedy?
A 99.9% uptime commitment is meaningless without knowing how it is measured (which regions? which endpoints? whose monitoring?) and what you receive when it is missed. Service credits capped at 10% of monthly fees are common and nearly worthless for a revenue-critical dependency. Ask for escalating remedies and, for critical systems, termination-for-cause rights tied to repeated SLA misses.
5. What is excluded from support?
The support tier matrix hides its value in the footnotes: response times measured in business hours, exclusions for 'custom configurations,' and severity definitions the vendor controls unilaterally. Ask for the last quarter's actual median response times at your tier — reported numbers, not promised ones — and whether severity-one pages reach a human or a queue.
6. What did you ship this year, and what is deprecated next year?
Feature deprecation is a hidden renewal cost: capabilities you depend on today may sit on a sunset list you have not seen. Ask for the deprecation roadmap and the notice periods promised for breaking changes. Vendors with a disciplined deprecation policy will answer quickly; the rest will reveal their roadmap discipline by their silence.
7. What is our actual usage, and does it match our contract?
This question is for you as much as for them. Before any renewal, reconcile contracted entitlements against real consumption. Most enterprises discover 15–30% shelfware — licenses for seats, nodes, or tiers that went unused. Rightsizing before negotiation is worth more than any discount a vendor will volunteer.
Leverage Comes From the Calendar
The common thread is timing. Every one of these questions is weaker asked ten days before expiration and stronger asked six months out, ideally alongside a documented alternative. You do not need to actually migrate off a vendor to negotiate like you could — but you do need to know what leaving would cost, and so should they.
Vendors hope renewals stay administrative. The moment they become evaluations, the terms improve.