SMB Software Renewal Calendars: Building a Single Source of Truth for UK Teams
Most small teams do not lose money on software because they bought the wrong tool. They lose it because they forgot a tool existed until the card statement arrived. A renewal that auto-renews at the wrong moment, a notice window that closed quietly, or a seat count that grew without anyone approving it can cost more than the original purchase decision. This article sets out a simple method for building a renewal calendar that works for lean UK operators, without assuming any particular vendor features or contract terms. It focuses on the questions you should ask and the records you should keep, so the calendar reflects what your contracts actually say rather than what you remember.
Start With an Inventory You Can Actually Trust
A renewal calendar is only as good as the list it is built from. Begin by gathering every place your business pays for software: company cards, direct debits, invoices sent to finance, expense claims and sign-ups made on personal accounts that later got reimbursed. Bank statements from the last twelve months are usually the most honest source, because they show what was really paid rather than what someone believes is in use.
For each entry, record the vendor, the product, the business owner, the billing frequency, the amount and the currency. Note whether the charge is per seat, per usage unit or flat. Many small teams discover at this stage that two tools perform the same job, or that a tool bought for a single project is still billing monthly for a team that disbanded months ago.
Do not try to make the inventory perfect on the first pass. A list that is seventy percent complete and updated every quarter beats an ambitious spreadsheet that is abandoned after a week.
Capture the Dates That Matter, Not Just the Price
The price is the least useful field in a renewal calendar on its own. What you need are the dates that control your options: the renewal date, the notice deadline, the end of any minimum commitment and the date a trial converts to paid. Notice deadlines are the most commonly missed. Some contracts require written notice a set number of days before renewal, and the window may be shorter than your team's normal review cycle.
Pull these dates from the actual order form, master subscription agreement or the terms you accepted online, not from memory or the sales conversation. If a date is unclear, record that as an open question with an owner and a deadline to resolve it, rather than guessing. An unknown notice period should be treated as a risk, not as a comfortable margin.
Also note how cancellation is performed. Some products need a request through a support channel, others through an account settings page, and some require a signed form. Recording the method saves the scramble of working it out at the last minute.
Assign an Owner and a Decision Rule for Each Line
Every renewal needs one named person who decides whether it continues. Shared responsibility tends to mean nobody acts. The owner is usually the person who uses the tool most or who is accountable for the outcome it supports, not necessarily the person who purchased it years ago.
Set a simple decision rule for each category before the renewal arrives. For example, a tool used weekly by the whole team might be kept if it has a named business owner and documented data exports, while a tool used by one person for a finished project might be cancelled at the notice deadline. Writing the rule down in advance makes the eventual decision faster and less emotional, and it creates a record you can revisit when you review the stack again.
Where a tool is critical to operations, note who holds admin access and whether a second person can act if the owner is unavailable. This is an ownership question, not a technical guarantee, and it is worth answering on paper.
Set Review Windows and Keep the Calendar Honest
Build reminders at three points: an early review, a decision point and the notice deadline itself. The early review, perhaps sixty days out, gives time to compare alternatives, gather usage data and talk to the owner. The decision point, around thirty days out, is when the owner commits to keep, change or cancel. The notice deadline reminder should fire with enough margin for the cancellation method you recorded to be completed in working hours.
Use a single shared calendar that the whole leadership group can see, not a private inbox reminder. Add a short note to each event stating the action required, the owner and where the contract lives. Store links to the underlying contract documents in a restricted shared folder so the reasoning can be checked later.
Finally, review the calendar itself each quarter. Remove cancelled tools, update prices after any known change and add new subscriptions as they appear. Ask whether any renewal happened that nobody expected. Each surprise is a signal that your inventory process has a gap.
A Short Checklist for Your First Pass
Work through these questions once you have your inventory: Is every paid tool listed, including those on expense claims and personal cards? Does each entry have a renewal date and notice deadline taken from the contract rather than assumption? Does each tool have one named owner? Is there a written keep, change or cancel rule? Is the cancellation method recorded? Are reminders set at sixty, thirty and at the notice deadline? Is the calendar visible to everyone who approves spend? Has anyone checked whether two tools duplicate the same job?
If you can answer yes to most of these, your renewal process is far stronger than the average small team's. If not, start with the items you cannot answer, because those are where the next unexpected charge is most likely to come from.