How to Audit Your SaaS Stack Before Renewal Season

Auditing a SaaS stack is six steps: pull the real spend from AP and card statements, inventory owner and usage per tool, apply the four-features test, rank every tool kill / replace / keep, check the renewal and notice dates before anything else moves, and sequence the exits. The order matters — most failed audits die at step one because they started from the tool list in someone's head instead of the list in the money.

Renewal season is the deadline that makes this real. Annual contracts commonly auto-renew unless you give written notice 30 to 60 days ahead — miss the window and the decision is made for you, for another year. Work backwards from your renewal dates and the audit stops being a someday project.

Step 1: Pull the spend from the money, not from memory

Export twelve months of AP and credit card statements and flag every recurring software charge. Not the stack diagram, not the IT list, not what people remember subscribing to — the statements. Sprawl hides on secondary cards, in expense reports, and in annual charges that only appear once a year. The gap between "what we think we pay for" and "what the bank says we pay for" is your first finding, and it is rarely zero.

Step 2: Build the inventory — owner, seats, and last real use

For every tool on the money list, record four things: what it costs annually, who owns it internally, seats paid versus seats active in the last 30 days, and the last time it produced something the business used. Most admin panels show seat activity; where they don't, ask the owner to name the tool's last output. A tool whose owner left the company, or whose "owner" is a department that forgot it exists, has already scored itself.

Step 3: Run the four-features test

For each tool with real usage, list the features your team actually touches in a normal week. For most tools it's about four — while the plan tier prices you for forty. This is the single most clarifying question in the audit, because it splits "we use this tool" (true) from "we need this platform" (usually false). A tool you use four features of isn't a keep; it's a job description — and jobs that small are exactly what a lean agent replaces first.

Step 4: Rank every tool kill / replace / keep

Two rules keep the ranking honest. First, nobody scores their own tool — every subscription has an internal champion, and champions don't file kills. Second, when a tool lands on the kill/replace boundary, the tiebreaker is the keep criteria, applied skeptically: "we might need it" is not deep integration.

Step 5: Check the renewal calendar before you act

Now — before any migration starts — pull the renewal date and the notice requirement for every kill and replace. Put the notice deadlines on your actual calendar, with the cancellation email drafted. Kills with a near window get filed immediately. Replaces get sequenced so the side-by-side overlap finishes before the notice deadline, not after. A perfect audit that misses its windows saves you nothing until next year.

Step 6: Sequence the exits — kills first, then one replace at a time

Kills are easy: export the data, give notice, done. Replaces are engineering: each one gets a two-to-four-week side-by-side run where the lean agent works alongside the incumbent until the outputs match, then a trigger condition tells you it's safe to pull the plug — the full mechanics are in how to migrate off a SaaS tool without losing data. Run one replace at a time. The companies that turn an audit into a smoking crater are the ones that tried to swap five systems in a quarter.

What about the keeps?

A keep verdict isn't a pass on the price. Load-bearing tools usually carry ghost seats too, and your renewal conversation is the one moment of the year the vendor has to listen. Walk in with your seat-activity numbers and downgrade to what the audit says you actually use. Keeps are where renegotiation, not replacement, recovers the money.

Do you have to build this yourself?

No. This entire process is what the free kit packages: a twelve-question scorecard that returns the kill / replace / keep one-pager with dollar savings, a Google Sheet audit template you can hand your CFO, and a ready-to-run Auditor agent skill — brain-dump your stack out loud for two minutes and your agent returns the ranked audit for you. What it costs you to find out what your stack is hiding: about six minutes.

FAQ

How long does a SaaS stack audit take?

The scored version of it — this site's scorecard — is twelve questions and about six minutes per pass on your top tools. The full audit, including pulling twelve months of AP data and checking renewal dates, is a few focused hours. Against a five- or six-figure annual software line, it's the highest-paid afternoon on your calendar.

Who should run the audit — the founder or the CFO?

The CFO can pull the spend data, but the kill / replace / keep calls are architecture decisions, so the founder or whoever owns how work gets done should make them. What you should never do is let each tool's internal champion score their own tool — nobody rates their own subscription a kill.

What if I miss the renewal window?

Auto-renew clauses commonly require written notice 30 to 60 days before the renewal date, so a missed window can lock in another year. If that happens, don't shelve the audit: use the year to run the side-by-side replacement for anything in the replace bucket, renegotiate seat counts where the contract allows it, and file the cancellation notice now, dated for the next window.

Can I just hand this whole audit to an AI agent?

Yes — that's one of the two ways the free kit works. Brain-dump your stack out loud for two minutes, paste the ready-to-run Ditch Your SaaS Auditor skill into your agent, and it returns the ranked kill / replace / keep audit with dollar savings and a lean replacement for each tool. The agent does the sorting; the pull-the-plug decisions stay yours.