The SaaS renewal calendar: the 90/60/30 rule that ends surprise auto-renewals

Your vendor has a calendar. It says exactly when your contract renews, how many days before that you have to give notice, and what the price does next year. You have an inbox. That asymmetry is why most companies pay for at least one tool nobody uses anymore. A renewal calendar fixes it in an afternoon, if you build it around the notice deadline instead of the renewal date.

Why auto-renewals win by default

Almost every SaaS agreement signed since 2020 contains the same three sentences: the term renews automatically, cancellation requires written notice a fixed number of days before the renewal date, and the price may increase at renewal, usually by a stated percentage or "the then-current list price". None of that is hidden. It is simply recorded on the vendor's side and forgotten on yours.

The failure is structural, not personal. The person who signed the contract changes roles. The invoice goes to finance, who see a number that matches last year and approve it. The team that used the tool moved to something else in the meantime. By the time someone asks "are we still paying for this?", the notice window closed weeks ago and the answer is "yes, for another year".

The numbers we see in customer workspaces are consistent: between 15% and 25% of SaaS spend sits on subscriptions where seats are paid but inactive, and roughly a third of renewals happen without anyone having looked at usage first. Both are calendar problems before they are negotiation problems.

The 90/60/30 rule

The rule is simple: three checkpoints, counted backwards from the notice deadline, not from the renewal date. If a contract renews on 1 March with a 60-day notice period, the deadline is 31 December, and the checkpoints fall in early October, early November and early December. Anchoring on the renewal date instead is the single most common mistake, and it quietly turns a 90-day runway into 30.

90 days out: decide

• Pull actual usage: active users in the last 30 and 90 days versus seats paid. Not logins to the SSO tile, real activity inside the tool.
• Ask the owner one question in writing: keep, shrink, replace or cancel. "Keep" needs a reason and a seat count.
• List the overlaps. Two tools doing the same job is the most common reason to cancel one at renewal rather than mid-term.

60 days out: act

• If the answer was cancel or replace, send the written notice now, to the address named in the contract, and keep the acknowledgement.
• If the answer was keep or shrink, open the negotiation. Vendors quote better numbers when you can show usage data and you still have a month of runway.
• Check the escalator clause. A 7% uplift on a contract nobody re-read is real money, and it is negotiable before the deadline and non-negotiable after it.

30 days out: confirm

• Written confirmation of whatever was agreed: new seat count, new price, new term, or the cancellation. An email thread is enough; a verbal promise from a rep is not.
• Update the contract record: new renewal date, new notice period if it changed, new owner if the old one moved.
• Tell finance what the next invoice should say, so a wrong one gets caught on arrival instead of after payment.

The five fields every contract record needs

You do not need the whole PDF in a database. You need five fields, and you need them for every subscription, including the ones paid by card by a team lead.

Building the calendar in an afternoon

1. Collect the contracts. Finance has the invoices, which give you vendors and amounts. Search the shared mailbox for "order form", "renewal" and "your subscription" to find the agreements themselves.
2. Extract the five fields. One line per subscription. Do not skip the small ones; the small ones are where the forgotten seats live.
3. Assign an owner to every line. If nobody claims a tool, that is your first cancellation candidate.
4. Compute the notice deadline (renewal date minus notice period) and set three reminders at 90, 60 and 30 days before it, addressed to the owner and to whoever runs procurement.
5. Review the list for 15 minutes a month. The calendar only stays true if new subscriptions enter it when they are signed, not when they renew.

What usage data changes at each checkpoint

The 90-day decision is only as good as the numbers behind it. Seat counts on the invoice tell you what you pay for; activity data tells you what you use. The gap between the two is the negotiation. A 200-seat plan with 140 active users is a 30% reduction, and vendors will accept it far more readily 60 days out than the week before renewal. Duplicated categories, two project trackers, two e-signature tools, two password managers, are decided the same way: usage decides which one stays.

The same data protects you from the opposite mistake. Cancelling a tool that a small team relies on because it looked unused from the outside costs more in disruption than the subscription saved. Look at who is active, not only how many.

Where the spreadsheet breaks

A spreadsheet can hold the five fields. What it cannot do is notice that the owner left the company in June, that the reminder went to a mailbox nobody reads, or that the seat count in column F no longer matches the identity provider. Every one of those is how a well-built calendar quietly stops working after a year.

That is the gap InventorIA closes: contracts live in a vault next to the licenses and people they cover, renewal alerts fire 90, 60 and 30 days before the notice deadline to the current owner, and seat utilisation comes from your identity provider and the tools themselves, so the 90-day decision starts with the numbers already on screen. When an owner is offboarded, their contracts show up as unowned the same day.