The SaaS contract checklist: what to settle before you sign

Almost everything written about software contracts is about getting out of one. That is where the pain shows up, so that is where the attention goes: the deadline that passed, the term that rolled, the year of licences nobody wanted. But every one of those outcomes was decided earlier, in a document somebody skimmed on the afternoon they had already chosen the tool.

The asymmetry is the whole point. Before you sign, the vendor wants your signature and most terms are negotiable. After you sign, you are asking for a favour. The clauses below are the ones that determine what the contract costs you over its life, and they are far cheaper to settle now than to live with later.

The term, the renewal, and the two dates that matter

Start by establishing the shape of the agreement, because the rest of the contract hangs off it. Three questions settle it: how long is the initial term, what happens at the end of it, and how long is each term after that.

A contract that ends unless you renew is a very different commitment from one that renews unless you stop it, and both are common. If it renews by default, find out into what: another year, or another month. That single fact decides how much a missed deadline costs, and it is the difference between an inconvenience and a year of software you had decided to drop. Our guide to evergreen and rolling contracts covers both structures in detail.

Then separate the two dates people routinely conflate. The renewal date is when the contract rolls. The cancellation deadline is the last day you can give notice before it does, and it is the renewal date minus the notice period. Only the second one is a deadline you can miss. If the contract renews on 1 December and requires 60 days of written notice, your real deadline is 2 October, and everything after that date is already decided.

The notice period is the clause to negotiate hardest

Notice periods on business software commonly run to 30, 60 or 90 days, and longer clauses exist. It is the term teams pay least attention to and the one that most reliably costs them money, because it is the only clause that can silently remove your ability to act while the contract still looks live and healthy.

There is a specific trap worth naming, because it catches people who are otherwise organised. If the notice period is longer than the time remaining in your current term, the deadline for this renewal is already in the past on the day you sign. A 90-day notice clause on a contract renewing in 60 days means the coming term is committed before you have logged in once. The same thing happens to anyone who inherits a contract partway through its term. Check the arithmetic against the date today, not against the abstract length of the term.

Two asks are usually reasonable and often granted: shorten the notice period, and require the vendor to send a renewal notice a set number of days before the deadline. The second costs the vendor nothing and removes your single largest failure mode. If neither is granted, the clause is not fatal, but you now know it is the contract that needs the most careful tracking. Notice periods explained works through the arithmetic in full.

What the price does at renewal

The number on the order form is the price for the initial term. What it becomes afterwards is a separate question, and if the contract is silent the answer is whatever the vendor lists at the time.

Ask for a cap on renewal increases, expressed as a percentage or tied to an inflation measure. A cap is one of the easier concessions to win at signature and one of the hardest to win later, when the vendor already knows how embedded the tool is. If you agree to a discount for the initial term, establish in writing whether it survives renewal or whether year two returns to list price, because a large first-year discount sitting next to an uncapped renewal is a common and entirely legal shape.

Where a multi-year term is on the table, treat the discount as the price of giving up your options rather than as free money. Multi-year SaaS contracts works through when that trade is worth making.

Seats, usage and what happens when you grow

Most software contracts are priced on something that changes: seats, users, records, events, storage. Establish what the metered thing is, what happens when you exceed it, and whether you can go back down.

• Can you add seats mid-term, and at what price? A contract that lets you add only at list price penalises exactly the growth the vendor wants.
• Can you reduce seats at renewal, or is the committed quantity a floor for the life of the agreement? Clauses that only ratchet upwards are common and are worth challenging.
• What happens on overage: an automatic move to the next tier, a per-unit charge, or a hard stop? All three exist, and only one of them surprises your finance team.
• Is the commitment on quantity or on spend? A spend commitment is usually more flexible if your usage shifts between products.

Exit, data and the end of the relationship

The end of a contract is the moment you have least leverage, so the terms that govern it should be agreed while you still have some. Two are worth the time.

First, data. Establish that you can export your data in a usable format, that you can do it yourself rather than by raising a support ticket, and how long the vendor keeps it after termination. A tool whose data can leave only as a PDF is harder to replace than its feature list suggests, and that difficulty is itself a pricing lever at every future renewal.

Second, termination for cause. If the service is unavailable for extended periods, or the vendor materially changes what you bought, can you leave before the term ends? Service credits are the common remedy and they are usually small. The right to exit is the one that matters.

The checklist

Pulled together, these are the questions to have answered before signature. None requires a lawyer to ask, and the answers should all end up in the contract rather than in an inbox.

1. 1How long is the initial term, and what is the exact renewal date?
2. 2Does it renew automatically, and into a term of what length?
3. 3What is the notice period, and what is the resulting cancellation deadline in calendar terms?
4. 4Is that deadline already in the past, given the date today?
5. 5How must notice be served, and to whom?
6. 6Will the vendor send a renewal notice before the deadline?
7. 7Is there a cap on the renewal price increase, and does the initial discount survive renewal?
8. 8What is the pricing metric, and what happens above and below the committed quantity?
9. 9Can you export your own data, in what format, and for how long after termination?
10. 10Under what circumstances can you terminate early?

Record the answers the day you sign

The answers are only useful if they survive the person who obtained them. Most missed deadlines are not failures of negotiation, they are failures of memory: the terms were understood once, by someone who has since changed role, and the contract sat in a shared drive until the invoice arrived.

So write them down where the renewal will be looked for, not where the contract was filed. At minimum record the renewal date, whether it auto-renews, the notice period in days and a named owner, because those four fields are what turn a contract into a date somebody is warned about. The fields that matter on a software register covers the rest, and the renewal terminology glossary defines the vocabulary the contract will use.

StackTrackr exists for that last step. It stores those fields against each tool, derives the cancellation deadline from the notice period so nobody has to do the subtraction, rolls the renewal date forward each term, and emails the named owner before the window closes. The free Starter plan covers up to ten tools, which is generally enough to hold every contract that rolls into a long term. Create an account and record your next contract as you sign it, while the answers are still in front of you.