The tolerated pain: renewing the requirements of three years ago
When a business first buys a piece of software, it usually thinks hard about what it needs. How many users. Which modules. Which plan. Whether to pay monthly or commit for a year. Those decisions are based on the business as it was at the time.
Then the subscription renews. And again. Each year the software provider charges the card or sends the invoice, and each year the business pays for the same users, modules and plan it chose when it first signed. In the meantime the team has changed, the work has changed, a newer tool has taken over half the job, and nobody uses the reporting module that tipped the original decision. The renewal does not ask whether the purchase still makes sense. It simply repeats it.
This is what paying for yesterday's requirements looks like. It is not one bad decision. It is a good decision that was never revisited.
Mellorca has written about the wider problem of supplier contracts renewing without review, which focuses on notice periods, exit terms and supplier performance. This article focuses on software specifically, and on the gap between what the business bought and what it now needs.
Why automatic renewal goes unchallenged
- Renewal is the default. Microsoft's documentation, for example, states that recurring billing is turned on by default for business subscriptions paid by card or billing profile, so the subscription is billed again at the end of each term unless someone acts.
- The decision window is short. Microsoft explains that for its newer billing account type, a subscription can only be cancelled for a prorated refund within seven days after it starts or renews. After that, turning off recurring billing only stops the next renewal; an annual subscription paid monthly continues to be charged for the rest of the term.
- Nobody is asked to decide. Renewal notices go to whoever signed up, who may not be the person who knows whether the tool is still needed. We explore this in why software renewals need a confirmed business owner.
- Change feels risky. Reducing users or downgrading a plan might break something, so leaving it alone feels safe.
How requirements drift
Requirements change quietly. Typical drift includes:
- Headcount: a team that had 25 people now has 18, but the subscription still has 25 seats.
- Usage: a module bought for one project is no longer used.
- Overlap: a newer platform now does the same job, so two tools are paid for one need.
- Plan fit: a premium tier was chosen for one feature that is now handled elsewhere.
- Commitment: an annual commitment made sense for stable use but now locks in a tool that may be replaced mid-year.
None of this shows up on the invoice. The invoice shows the price, not the fit.
How the pain becomes money
- Technology waste: seats, modules and plan levels paid for but not used.
- Lost negotiating leverage: without a review, there is no point at which the business asks for a better price or terms.
- Locked-in commitment: missing the renewal window can commit the business to another full year of spend.
- Opportunity cost: budget tied up in old requirements is not available for tools that would fit the business today.
An illustrative cost model
The figures below are illustrative assumptions for an unnamed South African logistics business. They are not benchmarks; the point is the method.
| Subscription | What was bought | What is needed now | Annual overspend |
|---|---|---|---|
| Fleet tracking add-on | 40 vehicles at R180 per month | 32 vehicles | R17,280 |
| Accounting software | Plan with a payroll module at R1,200 per month extra | Payroll now outsourced | R14,400 |
| Collaboration suite | 30 seats at R420 per month | 22 active users | R40,320 |
| Reporting tool | Annual licence at R36,000 | Replaced by built-in dashboards | R36,000 |
| Total | R108,000 |
Checking the arithmetic: 8 × R180 × 12 = R17,280; R1,200 × 12 = R14,400; 8 × R420 × 12 = R40,320; R17,280 + R14,400 + R40,320 + R36,000 = R108,000.
Against that, a structured review of these four renewals might take, say, three hours each at an illustrative R450 per hour: 4 × 3 × R450 = R5,400. The review does not guarantee the saving, but without it the saving is not available at all.
Secondary consequences
The cost of renewing old requirements is not only the invoice. Every seat that stays assigned is another account to secure and manage. Every module that stays switched on is another set of settings, permissions and updates for someone to look after. Tools kept "just in case" also make the software estate harder to understand, which slows down the next decision about what to buy. And because each renewal that passes without review makes the tool feel more permanent, the business gradually loses the habit of asking whether its technology still matches the way it works.
What a value review actually checks
A value review is not a cost-cutting exercise. It asks whether the subscription still fits the business. For each renewal:
- Who uses it, and how much? Usage data is often available. Microsoft's admin center usage reports, for instance, show activity over the last 7, 30, 90 and 180 days, and Microsoft describes them as a way to see who barely uses a service and might not need a licence. Most business software has an equivalent.
- What job does it do today? Ask the people who use it, not only the person who bought it.
- Does anything else already do this job? Check for overlap with tools the business already pays for.
- Is the plan right? Compare the features you use with what each plan level includes.
- Is the commitment right? Monthly flexibility may be worth a higher price if the need is uncertain.
- What would leaving cost? Check data export, integrations and notice periods before you need them.
Our guide on how to decide which software to remove covers the remove-or-keep decision in more depth, and why software portfolio decisions need business value, not only licence counts explains why usage figures alone are not enough.
When it becomes commercially urgent
- Headcount has fallen or been restructured since the last renewal.
- A new platform has been introduced that overlaps with older tools.
- Several large annual renewals fall in the same quarter.
- Finance cannot say which department owns each subscription.
What better looks like
- A renewal calendar showing every subscription, its renewal date, term, value and business owner.
- A review triggered 60 to 90 days before each renewal, so changes can be made before the window closes.
- Usage evidence attached to each renewal decision.
- An explicit decision recorded for every renewal: renew as is, renew with changes, or exit.
Practical first steps
- List all software renewals due in the next six months, largest first.
- Assign a business owner to each and ask them to confirm current need.
- Pull usage data for the top five by value.
- Decide seat counts, plan levels and term before each renewal date.
- Diarise the cancellation or reduction window, not just the renewal date.
Bottom line
Automatic renewal is convenient, and convenience is the problem. Each renewal repeats a decision made for a business that no longer exists in the same form. A short value review before each renewal costs a few hours and gives the business the one moment in the year when it can pay for what it needs today instead of what it needed then.
Sources and further reading
- Manage recurring billing in the Microsoft 365 admin center (last verified 10 October 2026)
- Cancel your Microsoft business subscription in the Microsoft 365 admin center (last verified 10 October 2026)
- Microsoft 365 Admin Center Usage Reports Overview - Microsoft 365 admin (last verified 10 October 2026)
Related Mellorca reading
- Subscriptions That Outlive the Employee: The Cost of Orphaned Software
- Paying for Tools You Already Own: The Cost of Underused Software Platforms
- Premium Plans for Basic Work: The Cost of Overbuying Software