Most software decisions are made exactly once. Someone compares a few options, signs up, sets up a debit order or a card payment, and the tool becomes part of the business. After that, the decision renews itself every month or every year without anyone making it again. The tool may have been a good choice three years ago. Whether it is still a good choice is a question that nobody is scheduled to ask.
Renewal dates are the obvious place to ask it. They are the one moment in a software relationship when the business has real choices: renew as is, change the plan, reduce the number of users, negotiate, move to something else or stop. Miss the date and most of those choices disappear for another term. Used deliberately, a renewal calendar becomes one of the cheapest management disciplines a business can adopt.
Why renewals pass without a decision
There are a few reasons renewals slip by unnoticed, and they are worth naming because each one suggests its own fix.
- Nobody owns the date. The person who signed up may have moved roles or left. Finance sees the charge but not the purpose. The team using the tool assumes someone else handles the commercial side. The discovery note on why software renewals need a confirmed business owner describes how this gap forms.
- The notice period is earlier than the renewal. Many agreements require notice weeks or months before the term ends. By the time the invoice arrives, the window to change anything has already closed.
- Cancellation windows are short. Some subscriptions can only be changed in a narrow period. Microsoft's documentation for its new commerce licensing, through which products such as Microsoft 365 are bought from partners, states that these subscriptions can only be cancelled in the first seven days of their term, while changes can be scheduled to take effect at the end of a term. A business that wants to reduce licences has to plan for the end of the term, not react after the renewal has gone through.
- Nobody sends a reminder. Business owners sometimes assume suppliers must warn them before a contract rolls over. Section 14 of the Consumer Protection Act does require a supplier to notify a consumer before a fixed-term agreement expires, but the section states that it does not apply to transactions between juristic persons, regardless of turnover or asset value. A company or close corporation buying software should assume that the contract terms, not a reminder, decide what happens at the end of the term.
The result is predictable. The impact of this pattern is set out in supplier contracts renewing without review: costs creep up, unused seats are paid for again, and tools that were meant to be temporary become permanent.
Build a renewal calendar that is actually used
A renewal calendar does not need special software. It needs to be complete, owned and early. For each paid tool, record:
- the tool and the supplier or reseller you pay;
- the business owner who decides whether it renews;
- the term (monthly, annual or multi-year) and the renewal date;
- the notice date, which is the last day on which you can change or cancel without being committed to another term;
- the current cost and the number of users or units;
- a review date, set comfortably before the notice date.
The review date is the important one. For annual contracts, a review six to eight weeks before the notice date gives time to gather usage information, talk to the team that relies on the tool and, if needed, approach alternatives. Monthly subscriptions can be reviewed in batches each quarter, because the cost of a wrong decision is smaller and the exit is easier.
If you do not yet have a complete list of what the business pays for, start there. Card statements, debit orders and supplier invoices for the last twelve months will show most of it. The impact page on unknown software subscriptions explains why the first list is usually longer than people expect.
What to review before each renewal
A renewal review should be short and should end in a decision. These questions cover most cases.
Is the tool still doing the job it was bought for?
Ask the people who use it, not only the person who pays for it. Has the work changed? Has another tool started doing part of the same job? Is the tool central to a process, or has it drifted to the edge?
How many people actually use it?
Compare paid seats with active users. Most platforms show last sign-in dates or activity reports. Seats assigned to people who have left, or to people who log in twice a year, are the easiest saving available.
Is the plan still the right plan?
Businesses often move up a tier for one feature, then stop using that feature. Others stay on a basic tier and work around missing controls by hand. A renewal is the moment to check which features are in use and whether the tier matches.
What does the tool connect to?
Before deciding to cancel or replace, list the integrations, reports and automations that depend on it. A tool with low direct usage may still feed an important process.
Is it still supported and secure?
For installed software, check the vendor's support timeline. The UK National Cyber Security Centre's asset management guidance notes that knowing when systems will no longer be supported helps you plan upgrades and replacements and avoid running vulnerable legacy systems. A renewal review is a natural point to check this.
What has changed in price or terms?
Compare the renewal quote with the current price. Check for changes to user minimums, storage limits, support levels or contract length. Price changes are easier to negotiate before the notice date than after.
Five decisions a renewal can produce
| Decision | When it fits |
|---|---|
| Renew as is | The tool is used, fits the work and the price is reasonable |
| Renew and right-size | The tool is needed, but seats or the plan tier are larger than the work requires |
| Renew short | A replacement or consolidation is likely but not ready; move to a shorter term if available to keep the exit open |
| Replace | The tool no longer fits and an alternative has been tested, with data and integrations planned |
| Stop | The capability is no longer needed or is covered elsewhere, and data retention has been handled |
"Renew short" is underused. When a business is not ready to move but suspects it should, committing to another full year removes the option. A shorter term costs a little more per month but protects the decision. Where to go from there is covered in how to decide which software to remove, and the broader options are set out in what keep, fix, integrate, automate, replace or remove means in practice.
An illustrative example
Consider an illustrative Durban logistics firm with 45 staff. Its finance manager pulled twelve months of card and debit order statements and found 19 software subscriptions, four of which had no clear owner. She added each to a shared calendar with a review date eight weeks before notice.
The first quarter's reviews produced modest but real outcomes. A project tool renewed annually was found to have 30 paid seats and 11 regular users; it was renewed with fewer seats. A form builder was being used for one internal request form that the main office suite could handle; it was stopped once the form was rebuilt. A route-planning tool that the operations team depended on was renewed as is, but the team was asked to name an owner and document its integration with the accounting system. None of these was a dramatic change. Together they turned a list of automatic charges into a set of decisions someone had made.
Make the review a routine, not a project
The value of renewal reviews comes from repetition. A single clean-up exercise produces savings for a year and then the old pattern returns. A calendar with named owners and review dates keeps the question alive.
A few habits help:
- Require a named business owner before any new subscription is paid for, and record the renewal and notice dates at the time of purchase.
- Review monthly subscriptions in quarterly batches and annual contracts individually.
- Record the decision and the reason, even when the answer is "renew as is". Next year's review will start from that note.
- Treat a missing owner as a finding in itself. If nobody will own the tool, ask whether the business still needs it.
Renewals will happen whether or not anyone is paying attention. The only question is whether each one is a decision or a default. The same list is also the natural starting point for a wider digital systems audit, because it shows what the business actually depends on and pays for.
Sources and further reading
- New commerce license-based overview - Partner Center (last verified 10 October 2026)
- Consumer Protection Act, 2008 (Act No. 68 of 2008) > Chapter 2 : Fundamental Consumer Rights > Part C : Consumer's right to choose > 14. Exp (last verified 10 October 2026)
- Asset management (last verified 10 October 2026)
Related Mellorca reading
- How to Decide Which Software to Keep
- What to ask about APIs before buying business software
- When a Spreadsheet Is a Useful Tool—and When It Becomes Infrastructure