Every autumn, give or take, a stack of renewal proposals arrives on my desk — PDFs, DocuSign links, the occasional printed binder from a vendor who still believes that weight confers authority. Most of them are dressed up to look like formalities, like the kind of paperwork you sign at a car dealership while someone hovers with a pen. And most of the people I work with, across sectors as different as mid-size logistics companies and regional NHS trusts, treat them exactly that way: a quick scan, a signature, done. What I've come to understand, after years of auditing these agreements after the fact — after the price increase has landed, after the seats have ballooned, after the auto-renewal has quietly fired — is that a SaaS renewal proposal is not a formality. It is, in the driest possible sense, a negotiation that one side has already prepared for and the other hasn't. This piece is about changing that.
Start with the renewal date, not the price ¶
The first thing I look for is not the headline price. It is the effective renewal date and, more importantly, the notice period required to cancel or renegotiate. These two numbers — buried, almost always, in a clause labelled something like 'Term and Termination' — define the entire shape of your negotiating window. A vendor who requires 90 days' written notice before the renewal date has, in practice, narrowed your meaningful decision window to whatever falls between 91 days and 120 days before expiry. I have seen contracts where that window was four days wide — the notice period was 60 days and nobody had flagged the date until 64 days out. The organisation signed, at a 22% uplift, because the alternative was a service interruption. Read the notice clause first. Write the notification deadline in your calendar the day the proposal arrives.
The auto-renewal mechanism and what 'evergreen' actually means ¶
Auto-renewal, sometimes called an evergreen clause, means the contract rolls forward automatically under its existing — or updated — terms unless you actively intervene. Vendors love this, and reasonably so: it is structurally excellent for their revenue forecasting. What organisations miss is that 'existing terms' sometimes includes a price escalation that was buried in the original agreement, not introduced in the renewal. I reviewed a contract last year for a manufacturing firm in the East Midlands in which the original 2021 agreement contained a clause permitting annual price increases tied to the higher of UK CPI or 5%. By 2024, compounded, this had moved their per-seat cost from £34 to just over £47 — without a single renegotiation conversation ever taking place. The renewal proposal simply confirmed the new figure as if it were obvious. They had signed the permission three years earlier and forgotten it.
Licence counts, true-ups, and the seat inflation problem ¶
The second structural trap is seat count, or more precisely the gap between the seat count you are being billed for and the seat count you are actually using. SaaS vendors typically provision generously on the way in — 'we'll give you 200 seats to start, you can always scale down' — but the contracts rarely make scaling down easy. True-up clauses, which require you to pay for peak usage over the contract term rather than average usage, are particularly punishing. I audited a professional services firm whose Salesforce instance had been provisioned at 180 licences; active monthly users averaged 94. Their renewal proposed 180 seats again, citing a true-up audit that had recorded 163 users logging in at least once during the prior 12 months. Once a month, for one session, apparently counts. Before any renewal conversation, pull your actual utilisation data — most enterprise SaaS platforms expose this in an admin dashboard — and present your own numbers rather than accepting the vendor's.
Price escalation clauses, index-linking, and what to negotiate ¶
Not all price increases are disclosed as price increases. Some come dressed as 'tier adjustments,' 'platform investment contributions,' or my personal favourite, 'value-based pricing realignment.' What you are looking for, specifically, is any clause that links future pricing to an external index (CPI, RPI, a proprietary vendor index), any clause that grants the vendor unilateral right to revise pricing with notice, and any clause that ties your price to your organisation's own growth metrics — revenue, headcount, transaction volume. That last category is rarer but increasingly present in fintech and HR platforms, and it means that if your business grows, your software costs grow automatically, regardless of whether you are using more features. The negotiation lever here is almost always the cap: ask for an explicit annual price increase cap — 3% is achievable with most vendors, 5% is common — written into the renewal terms, not just offered verbally.
What the SLA and support terms actually say now versus what you signed originally ¶
Vendors revise their standard terms between contract cycles, often quietly, through updates to a 'Master Services Agreement' or 'General Terms' document that is referenced but not reproduced in the renewal proposal. This matters because the renewal proposal you are being asked to sign typically incorporates those updated terms by reference. I have seen uptime SLA commitments drop from 99.9% to 99.5% between renewal cycles — a change that sounds small but represents a tripling of permitted downtime, from roughly 8.7 hours per year to 43.8 hours. I have seen support response time commitments for critical issues move from 2 hours to 4 hours. Request the current version of the MSA or General Terms as a standalone document, compare it to the version you signed previously, and flag any changes to SLA commitments before signing.
Data portability, exit rights, and the cost of leaving ¶
A renewal is also a moment to read your exit terms with fresh eyes, because the cost of leaving a platform is often invisible until you try. Data portability clauses specify what format your data will be exported in, how long after termination the vendor will make it available, and whether extraction assistance is included or billed separately. I have worked with organisations who discovered, post-termination, that their data export would be delivered as a series of CSV files with no relational keys — technically compliant with the contract, practically unusable without significant transformation work. Some vendors charge professional services fees for data extraction that can run to tens of thousands of pounds. Read the termination and data portability clauses as if you are already planning to leave, because the moment you are actually planning to leave is exactly the wrong time to discover what they say.
The conversation to have before you sign anything ¶
After all of this reading, there is a conversation worth having — not an adversarial one, but a specific one. Ask your account manager four questions directly: what is the effective price per seat or unit this renewal versus last year, expressed as a percentage change; what flexibility exists on the notice period for future renewals; what the process is for reducing seat count mid-term if utilisation drops; and whether the current MSA terms differ materially from those in your original agreement. The answers, and the speed and precision with which they are given, tell you a great deal about how the vendor thinks about the relationship. Most account managers are reasonable people constrained by reasonable processes. The ones who cannot answer the third question — mid-term seat reduction — without escalating to their legal team are the ones whose contracts are worth reading most carefully.
None of this is adversarial, or at least it shouldn't be. The vendors building software that organisations depend on are not, in most cases, trying to trap anyone — they are trying to grow predictable revenue, which is a legitimate goal. But the asymmetry of preparation is real: they have drafted these documents, refined them across thousands of renewals, and optimised them for their own outcomes. Reading carefully, asking specific questions, and knowing what you are actually agreeing to is not aggressive procurement practice. It is just basic due diligence, and it is worth the two hours it takes before you reach for that pen.