Look at how software renewals reach a finance team. An invoice arrives for a tool someone bought years ago. The notice period to cancel has already closed.
The person who chose the tool has moved on. The renewal goes through, because there is no time to do anything else.
Repeat that across every tool in the business and the renewal calendar starts making the software decisions. Nobody wrote it as a strategy. It works like one anyway.
The thesis: every renewal is the cheapest moment to change your mind about how a piece of work gets done. After the date passes, the choice is made for another term.
This piece is for the CFO who signs the renewals and wants each one to be a decision.
Start with one list
Before the questions, write one list of every tool the business pays for. Each line has four facts: the renewal date, the date the notice period opens, who owns the tool, and the job it does. Sort it by notice date, not renewal date. The notice date is when your options end.
The hard part is the last column. Writing down the job is where the method starts.
The five questions
Ask them for each tool, in time to act on the answers.
- What job does this tool do, in one sentence? Name the work, not the features. "Captures expense claims, checks them against policy and sends them for approval" is a job. "Expense management" is a category. If the sentence needs "and also", the tool may be doing two jobs, and each one deserves its own answer.
- Who does the work in it, and who only looks? Split the users into two groups: people who do the job inside the tool, and people who log in only to view, approve or pull a report. A large second group is a signal. The work and the information may be in the wrong place, and you are paying for access to see them.
- Where does the work leave the tool? Follow the job to its end. If people export, re-type or copy the output into another system, the tool finishes only part of the job. The rest is done by hand, and it never shows up on the renewal invoice.
- What would it take to leave? Find out the contract term, the notice period, the format your data comes out in, and who knows how the tool is set up. The cost of leaving decides your real options. Learn it while there is still time to use it.
- Who decides, and by when? Name one owner for the decision and set a date before the notice period opens. A renewal with no owner and no date renews itself.
Three answers, not two
A renewal review is not a choice between "keep" and "cancel". There are three answers.
- Renew as it is. The tool does a clear job, the people in it do the work, and little of it leaves by hand.
- Renew smaller or shorter. The job is still needed, but fewer people need access, or the business wants room to move the work within a shorter term.
- Move the job. The work itself is changing. Some of it, such as routine capture, matching and routing, can move to AI agents on one platform that connects the business. The tool's term ends when the work has a new home.
The third answer only makes sense when someone has a plan for the work. Cancelling a tool without one doesn't remove the job. It hands the job to whoever is nearest.
One review, worked through
Here is how the review might run for an expense-claim tool in a mid-sized business. It illustrates the method; it is not taken from a client.
- The job: capture expense claims, check them against policy and send them to a manager for approval.
- Who does the work: employees submit claims and one finance administrator checks them. Most of the other seats belong to managers who log in only to approve.
- Where the work leaves: approved claims are exported once a month and typed into the accounting system by the same administrator.
- What it takes to leave: the data comes out as a spreadsheet, the notice period opens well before renewal, and only the administrator knows how the policy rules are set up.
- Who decides: the finance manager, by a date set a month before the notice period opens.
The finance manager chooses to renew for a shorter term. In that time, the business decides whether capture and the policy check move to AI agents, with managers approving from where they already work and the administrator handling only the exceptions. The policy rules get written down either way, because one person holding them is a risk whatever happens to the tool.
Where the method breaks
The review starts when the invoice arrives. By then the notice period has closed and the answer is already "renew". Run the review from the notice date, not the renewal date.
Logins are counted instead of work. A login count says how often people open a tool, not whether it does the job. A tool that people open every day to re-type its output elsewhere is busy, not useful.
The review happens without the people who do the work. Finance sees the contract; the administrator sees the job. Ask both.
Cheaper is mistaken for better. Removing a tool moves the work; it doesn't remove it. If the job has no new home, the cost moves into people's weeks, where it is harder to see.
What stays with people
The owner decides whether to renew, and a person agrees any change to a contract. AI agents can keep the list current and gather the facts for each review: the dates, the users and where the work leaves the tool. Choosing what happens to the work, and committing the business to a supplier, stays with the people accountable for it.
The date is the decision
A renewal review moves the decision back to the business: one list, five questions and one owner per tool, in time to choose. Run it once, and the next renewal is a decision instead of an invoice.
At Futuvara, we build, implement and run AI platforms where AI agents do defined work under rules your business sets. If your next renewal is a chance to rethink the work behind it, start a conversation.
