The Software Renewal Audit Guides

How To Audit Your SaaS Renewals In An Afternoon

Pull every renewal due in the next 90 days into one list. Run each line through three questions: is there an AI-native version, can an agent roll our own, and is the job a rule or a judgment call. Write Keep, Swap, or Build next to each one. Then take the Swap column first, because those wins fund everything else. That is the whole afternoon. Here is how to run it without it turning into a quarter-long project.

Before you start: set the window

The mistake that kills most audits is scope. Owners open a spreadsheet, try to list every tool the company has ever paid for, and quit at line thirty. Do not audit the stack. Audit the renewals.

The next 90 days is the window. Those are the lines where a verdict actually changes the bill. A tool that renewed last month produces a decision you cannot act on for eleven months, and you will have forgotten the reasoning by then. Let the calendar hand you the list. Next quarter, it hands you the next one. This is how I got from roughly $6,000 a month in software down over two years: not in one heroic weekend, one renewal at a time. If you want the longer version of why that matters, start with what a renewal audit is.

Step 1: Build the list (30 minutes)

Three sources, in order.

  1. The card and bank feed. Filter the last twelve months to recurring charges. Anything that hits monthly or annually goes on the list with its amount and its next renewal date.
  2. The bookkeeper's prepaids. Annual contracts paid up front hide in a different account. Ask for anything coded as prepaid software or subscriptions.
  3. Department leads. Ask each one what they pay for on their own card or expense report. This pass finds the lines nobody knew about.

For each line, capture five things: tool name, what job it does in one sentence, monthly cost, next renewal date, and who on the team uses it daily. The job sentence matters more than the tool name. "Client reporting" is a job. "The dashboard thing" is not.

Step 2: Run the three questions (90 minutes)

Go line by line. Do not skip ahead to the ones you suspect are waste. Every line gets the same three questions, and the order matters.

Question 1: Is there an AI-native version? Same job, built after the models got good. Categories where the answer is often yes: reporting, slide decks, transcription, scheduling, first-line support, most dashboards. The rule of thumb from the agency owner in our mastermind who ran this across their whole stack: swaps came in at about a tenth of the cost. Treat that as a planning number, not a quote.

Question 2: Can an agent roll our own? Two sub-questions. Is the data reachable, meaning can you export it or hit it through an API? And can the daily user name the three features they actually use? If both are yes, the tool is a couple of hours of agent work with exactly those features and none of the 58 you never click. Rule of thumb: a tenth of the swap price again.

Question 3: Is it a rule or a judgment call? This does not decide whether you build. It decides how. Hard rules (if invoice is 30 days late, send reminder) go to code. Judgment calls (is this lead worth a call today) go to an agent. Get this wrong and you build the wrong thing in either direction.

If you cannot answer a question yourself, ask the daily user. If there is no daily user, that is your answer.

Step 3: Assign the verdict (30 minutes)

Each line lands in one of three columns.

VerdictWhenWhat happens next
KeepNo AI-native version, no clean data to build on, or the job is heavy judgment with no good agent path yetRenew. Put the three questions on the calendar for next renewal.
SwapAn AI-native version does the same job for a fractionTrial the swap before the renewal date. Migrate. Cancel the old one.
BuildData is reachable and you can name the three features you useHand an agent the job, the data source, and the three features. Run both in parallel for a cycle.

Some lines get two verdicts with a timeline. One of the agency's lines was "swap this year, build next year." That is the right shape for anything mission-critical. You are chipping away, not ripping out. The detailed logic for each column is in the Keep, Swap, Build decision framework.

Step 4: Take the Swap column first (the rest of the afternoon)

Sort by renewal date. For each Swap line due soonest, do three things before you leave for the day: start a trial of the AI-native alternative, put a calendar reminder two weeks before renewal to make the call, and tell the daily user what is happening. Swaps are the fastest wins and they are what fund the Build column. Do not start with Build. Build is cheaper over a year but it costs attention this week, and attention is the scarce thing in a five to fifty person company.

For Keep lines, do nothing except write down why. "Keep: judgment-heavy, no clean export, revisit at next renewal" takes ten seconds and saves you re-deciding in twelve months.

For Build lines, write a one-paragraph brief: the job, where the data lives, the three features. Hand it to whoever runs your agents. That paragraph is the entire spec. A member of our group built her own task board this way a couple of months after starting, with agents, without a developer. The first version of everything sucks, then it gets better.

What you should have at the end

That last number is the one that keeps you running the audit next quarter. If the gap is small, your stack is in good shape and you have the receipts to prove it. If the gap is large, you just found the money, and it was sitting in auto-renew the whole time. The mistakes that keep that gap large are covered in the seven renewal mistakes.

The scorecard that makes this a fill-in-the-blanks exercise, with worked examples from the call it came from, is free on the home page.

FAQ

Where do I find all my renewals in one place?

Start with the card statements and the bank feed for the last twelve months, filtered to recurring charges. Add anything billed annually that your bookkeeper has as a prepaid. Then ask each department lead what they pay for on their own card. Most owners find lines on that third pass they had forgotten existed.

What if I cannot answer the three questions for a tool myself?

Ask the person who actually uses it every day. They know which three features matter and whether the data can be exported. If nobody on the team uses it every day, that is your answer too, and the line goes to Swap or to the bottom of the Keep column with a note to revisit.

Should I audit the whole stack at once or just upcoming renewals?

Upcoming renewals. The next 90 days is the right window because those are the lines where a decision actually changes the bill. Auditing a tool that renewed last month produces a verdict you cannot act on for eleven months. Let the calendar hand you the list and run the audit as a habit, not a project.

Get the audit

The Software Renewal Audit is free: the three questions, the Keep / Swap / Build scorecard you can run on your own bill, and worked examples from the call it came from.

Send Me The Audit →