The software renewal countdown: what to do at 90, 60, 30 and 7 days
Most renewal advice stops at a single instruction: set a reminder. That is better than nothing, and it is also why so many renewals still go badly. One reminder arrives at one moment, usually too late to do anything except pay or panic. The work that produces a good renewal is spread across the three months before it, and each stage of that period asks a different question.
What follows is the countdown itself: what to do at 90, 60, 30 and 7 days out, why each stage exists, and what it costs you to skip one. It assumes an annual contract that renews automatically, because that is the shape that catches teams out most often.
Why a countdown beats a single reminder
A renewal is not one decision. It is three, and they have to happen in that order: do we still want this tool, what should we be paying for it, and who is going to make that happen before the deadline. Compressing all three into the week before the renewal date guarantees the answer to the first is yes, the answer to the second is whatever the vendor asked for, and the answer to the third is nobody.
Spacing them out changes the outcome, because each stage feeds the next. The usage question at 90 days tells you whether it is worth negotiating at all. The evidence you gather at 60 days is what gives the conversation at 30 days any weight. And the only reason the 7 day stage is calm is that everything before it already happened.
90 days out: decide whether you want it at all
The first stage is not about price. It is about whether this tool still earns its place, and it is the only stage where the honest answer can be no while there is still time to act on it.
- Compare the seat count you pay for against the people who actually sign in. Seats bought during a hiring plan that never happened are the easiest saving available, and renewal is when you can take it.
- Ask the owner, not the buyer. The person whose name is on the invoice often has no idea whether the team still uses it. The named owner does.
- Check for overlap. If two tools have grown into the same job, the renewal date of the weaker one is your natural moment to consolidate.
- Write down what breaks if you drop it. If nobody can describe the consequence, that is your answer.
If the answer is that you are dropping it, you are now running an offboarding rather than a renewal, and you have three months to export data and move people across instead of three days. That difference is the entire value of starting here.
60 days out: build the position you will negotiate from
You are keeping the tool, so the question becomes what you should pay for it. This stage is evidence gathering, and it is deliberately separate from the conversation itself, because walking into a renewal call and improvising is how list price wins.
- Establish what you pay today, annualised. Monthly and quarterly billing hide the real number, and the real number is the one you are negotiating.
- Find out what the price is contractually allowed to do on renewal. The clause you signed will say whether any uplift is capped, and that changes what you can push back on.
- Price one credible alternative properly, including the cost of migrating to it. An alternative you have not costed is not leverage, it is a bluff.
- Decide your walk away number before anyone quotes you one.
Then open the conversation. Sixty days is early enough that you are negotiating rather than pleading, and close enough to the vendor's own quarter for the timing to matter to them too. The mechanics are covered in negotiating a software renewal.
30 days out: commit to a decision internally
By this stage the decision has to stop being a discussion. Thirty days out exists to convert an intention into a named action with a named owner, because the failure mode here is not disagreement, it is drift: everyone assumes the renewal is handled, and nobody has done the thing that handles it.
- Record the decision somewhere that is not a chat thread. Renew at the agreed price, renew unchanged, or serve notice.
- If the decision is to leave, find out exactly how notice must be served. Some contracts name a postal address or a specific contact, and an email to your account manager does not satisfy that.
- If the decision is to stay, get the new price in writing before the date rather than discovering it on the invoice.
- Name the person who will do it, and the date they will do it by.
For a multi year term this stage carries more weight than usual, because the commitment runs well past the next budget cycle. If that is what you are about to sign, work out the total liability first.
7 days out: execute and get confirmation
The last stage is deliberately small, because if the earlier stages happened there is very little left to do. Its job is to catch the case where the decision was made and then quietly never executed.
If you are leaving, this is when notice goes out in the format the contract demands and when you ask for written acknowledgement. Notice you cannot prove you served is notice you did not serve, which is why serving notice of non renewal is worth doing carefully rather than quickly. If you are staying, check that the agreed price is what appears on the renewal invoice.
If you have arrived here and none of the earlier stages happened, the honest first move is to check whether the notice window has already closed. If it has, you are not renewing a contract, you are dealing with a missed deadline, and the options are different ones.
After the date: close the loop
The renewal is not finished when the date passes. Whatever you agreed has to go back into the record, or next year's countdown starts from stale information and every stage above degrades quietly.
- Update the cost to what you actually agreed, not what you were originally quoted.
- Update the next renewal date, and re check the notice period, which a negotiation sometimes changes.
- Record what you conceded or won, so next year's conversation starts where this one ended.
When the notice period is longer than 90 days
A 90 day countdown assumes the deadline falls at most 90 days before the renewal. Plenty of larger agreements ask for six months, and a rolling contract can require notice measured from a date that has nothing to do with the anniversary in your calendar.
The fix is to stretch the countdown rather than abandon it. The stages keep the same order and the same jobs, they just start earlier: with 180 days notice, the usage review happens at 180 days and the negotiation at around 120. If your contract rolls month to month, or renews on a term you did not choose, read evergreen and rolling contracts before you set any dates at all.
Running the countdown without having to remember it
None of the above is difficult. It is simply impossible to sustain from memory across a few dozen tools with different dates, which is the part StackTrackr removes. Record the renewal date, the notice period and whether it auto renews, and the cancellation deadline is worked out for you.
Reminders then run this exact cadence by default. Every tool starts on 90, 60, 30 and 7 days, and those offsets apply to the renewal date and to the cancellation deadline, so a contract with a notice period generates the countdown twice over: once towards the date you must act by, and once towards the date it rolls. The deadline also alerts on the day itself whatever offsets you set. You can change the numbers per tool, which is how a six month notice period gets a six month countdown. The detail is in how reminder alerts work.
If you would rather see the whole estate at once than wait to be told, the reports show what is renewing over the coming months and what is sitting inside a notice window right now. Either way the point is the same: the countdown runs whether or not anyone remembers that it exists.
You can track your first tools free on the Starter plan. See the plans or create an account and start with the contract whose renewal date is nearest.