Who approves a software renewal? Sign-off for small teams
Ask who approved a software renewal and you will usually get a pause. Not because somebody is hiding it, but because on an auto-renewing contract nobody approved anything. The term rolled, the invoice arrived, and the payment went through because it always had. The decision was made by the calendar.
That is the gap this covers: not a procurement policy, which a team of nine will route around by the second week, but the smallest arrangement that means every renewal has a named person who chose it and a date by which they had to choose. Two things, and neither of them needs a system to enforce.
Why renewals lose their decision-maker
A new purchase has natural friction. Somebody wants the tool, somebody agrees to pay for it, and a card gets entered. Whatever your process is, that moment has an owner because it cannot happen without one.
A renewal has the opposite property: it happens if everyone does nothing. There is no request to approve and no invoice to query, because the amount matches last year and the tool is genuinely in use. So the question never reaches anybody, and a year of spend is committed by default. That is also why renewals survive the departure of the person who bought the tool, because nothing about the rollover requires them to still work here.
The people who feel this first are usually the ones with no procurement function to fall back on. There is no purchasing team reviewing contracts, no approval workflow, and no single inbox the vendor writes to. What there is instead is a founder or an office manager who finds out at the bank statement.
Start with one named owner per tool
Before any sign-off rule, every tool needs one person's name against it. Not a department and not two people, because a renewal owned by a team is owned by nobody in particular. The owner is whoever would notice if the tool stopped working, which is usually the person who asked for it.
This is the load-bearing part of the whole arrangement, and it is worth doing before anything else. If you cannot name an owner for a tool, you have found something more urgent than an approval process: a subscription nobody is accountable for. Our guide on software nobody owns deals with that case directly.
The owner is not necessarily the approver. On a small estate they are frequently the same person, and that is fine. What matters is that the owner is who the question goes to, so it never has to be worked out from scratch three weeks before a deadline.
What sign-off actually means at a renewal
Approving a renewal is not signing a form. It is answering three questions in order, and the order matters because each one can make the next unnecessary.
- Do we still want this tool? Usage, not sentiment. If two people opened it this quarter, the other questions are moot.
- Is the price still right? Check what you are being asked for against what you agreed, including any renewal uplift the contract allows.
- Who is making it happen, and by when? A decision to cancel that nobody executes costs exactly the same as a decision to renew.
Written down, that is a two-minute conversation for most tools. The reason it feels heavier is that it usually happens in the week the invoice lands, when the answer to the second question can only be yes. Move it earlier and it stops being a negotiation you have already lost. The 90, 60, 30 and 7 day countdown sets out when each stage is worth doing.
Set a threshold, not a policy
Larger organisations route approvals by spend band, and the instinct is to copy that. Resist it at small scale: a policy that asks for a second signature on a tool costing a few pounds a month trains everybody to treat the process as noise, and the noise is what hides the renewal that mattered.
One threshold is enough. Pick an annual figure that is material to your business and split the estate on it:
- Below the line: the owner decides alone. No approval, no meeting. They are accountable for it and that is the whole control.
- Above the line: the owner brings it to whoever holds the budget, before the cancellation deadline, with an answer to the three questions.
- Multi-year, or anything with a long notice period: treat as above the line whatever the annual figure, because the commitment is a multiple of it. Multi-year contracts are where an unreviewed rollover gets expensive.
Note what this is not doing. It is not approval control, and it is not trying to stop people buying software, because heavier processes get routed around and unrecorded spend is worse than approved spend. It is making sure the expensive half of your estate has a person and a date attached to it.
Record the decision where the renewal lives
A decision that exists only in a thread is not recorded. The test is simple: if the person who made it left tomorrow, could the next person tell what was agreed and why? A capped uplift accepted by reply, or a plan downgrade agreed verbally with an account manager, both fail that test.
So keep the record in the same place as the renewal date and the notice period, rather than in a finance sheet that will disagree with it by the third quarter. What to keep is short: what was decided, who decided it, and what changed as a result, meaning the new price, the new term end and the new seat count. Attach the order form or the renewal email alongside it and the reasoning survives the person.
Running it without having to remember it
The process above has one weakness, which is that it depends entirely on the question arriving in time. That is the part worth automating, because it is the part memory is worst at across a few dozen contracts with unrelated dates.
In StackTrackr each tool carries its owner, so the name is attached to the record rather than to somebody's recollection, and reminders go to that named owner and to the account admins, rather than to a shared mailbox with nobody's name on it. Record the renewal date and the notice period and the deadline is calculated for you, which is the date the sign-off has to beat.
For the threshold, the reports give you the annualised cost per tool, so splitting the estate on a figure is a sort rather than an exercise. If you want the commitment view instead of the monthly one, the liability report totals what you are contractually on the hook for, which is the number that makes a multi-year rollover look different from its invoice.
If the vocabulary in a renewal email is the obstacle, the glossary covers the terms in plain English. Otherwise start smaller than a process: take your five most expensive tools, record when each one renews and how much notice it needs, and see which deadlines have already passed. The free Starter plan covers ten tools for a single user, which is enough to do that audit yourself; assigning tools to named colleagues needs a plan with more than one seat, so see the plans or create an account.