Why the annual review is too late
Subscription creep works in monthly increments. A tool you stopped using in February is still billing in November, and by the time an annual review surfaces it you have paid for nine months of nothing. A quarterly pass costs 15 minutes and catches the same problem when it is three months old instead of nine. The full stack audit from our full stack audit is the deep version — something you do once and act on. This checklist is the maintenance pass that keeps the work from decaying. Run it four times a year, same week every quarter, and subscription creep stops compounding before it starts.
What the 15-minute audit covers
Four zones, in order: seats and billing (what you pay and whether you’re paying for people who no longer need access), overlap (whether two tools in your stack are doing the same job), usage (whether tools are being used at all), and automation candidates (whether any repeated manual work is now worth automating). These are the same four questions from the full stack audit, compressed into a triage pass rather than a full investigation.
The checklist — run this quarterly
Zone 1 — Seats and billing
- Open your company card statement and list every recurring SaaS charge from the last 30 days — tool name, amount, billing date. This list is the audit’s input; without it you are working from memory, which is how tools stay on the stack invisibly.
- For every per-seat tool on that list, open the admin panel and count active users against paid seats. Flag any gap of two or more — that is money leaving for capacity nobody uses.
- Check for any tools billed annually that are renewing in the next 90 days. Calendar a decision point at least 30 days before the renewal date. Deciding after the charge hits is not deciding — it is accepting.
- Confirm every seat belongs to a current team member. Remove accounts for departed employees and inactive contractors. This step alone recovers money at a majority of agencies the first time they run it.
Zone 2 — Overlap check
- For each tool in your stack, write one sentence describing what you actually used it for in the last 30 days. Not its feature list — what you did with it.
- Flag any pair where the one-sentence descriptions overlap. These are the pairs covered in our tool overlap guide — Dropbox and Google Drive doing the same storage job, Loom and Zoom both recording video, Calendly and Google Calendar both booking meetings.
- For each flagged pair, check whether the cheaper or already-included tool can cover what you actually do — not the full feature list, just the one sentence from step 1. If it can, you have a cut candidate. Add it to the decision list for the following week, not the audit itself.
Zone 3 — Usage check
- Open the admin dashboard for your three most expensive tools and check last-login dates for each seat. Most admin panels surface this in a Users or Members section. Flag any seat with no activity in the last 30 days.
- For each flagged seat, have a direct two-minute conversation: is this person actively using the tool or has their work moved elsewhere? The answer determines whether you downgrade or reassign the seat.
- ► Check your Make.com or n8n execution logs — are any scenarios consuming credits or executions but producing no visible output? A scenario that runs daily and generates no downstream action is a candidate for review, either to fix or to turn off.
Zone 4 — Automation candidates
- List the three manual tasks your team repeated most this week. Not the biggest tasks — the most repeated ones.
- For each task, ask three questions: is it triggered by a predictable event, does it always follow the same steps, and does it involve moving data between tools? If yes to all three, it is an automation candidate.
- Note one candidate per quarter for the next automation build. One per quarter is enough — trying to automate three things at once means none of them get done well.
How to run it without it taking 90 minutes
Set a 15-minute timer before you start. The timer is not a constraint on how much you can find — it is permission to stop when it runs out. When the timer goes off, write down what you found and stop. Action items go on a separate list for the next available hour.
The audit and the action are two separate activities. The audit is triage: identify, flag, list. The action is execution: cancel, downgrade, configure. Conflating them is why people avoid the audit — it starts feeling like a project instead of a check. Keep them separate and the 15-minute audit stays 15 minutes.
What to do with what you find
Small findings get actioned immediately — an unused seat to remove, a billing date to calendar, a Zap to toggle off. Each takes under two minutes and the list should be clear within the same hour as the audit.
Larger findings go on a decision list for the following week: an overlap pair to investigate, a tool to evaluate for removal, a workflow to document before the next renewal. The quarterly audit is a triage pass, not a project. If it becomes a project every time you run it, you will stop running it.
When 15 minutes becomes 2 hours
If you have never run a full audit before, the first quarterly pass will take longer than 15 minutes. You will find things that need immediate attention and the action list will be long. That is expected and correct — do the full work once, document what you find using our workflow documentation guide, and the second quarter’s audit genuinely takes 15 minutes because most of the heavy lifting is already done.
The 15-minute target applies to a maintained stack, not a neglected one. The first pass is an investment; every subsequent pass is the return on it.
The honest limitations
This checklist gives you a clear view of what is visible from billing statements and admin dashboards. It does not catch shadow IT — tools individual team members pay for on personal cards and expense later. It does not surface annual contracts that do not appear on monthly statements until the renewal arrives. And it does not account for switching costs: a tool flagged as overlapping may be worth keeping because the migration cost exceeds several years of subscription fees. The full stack audit from our full stack audit is the place to catch those nuances, investigate them properly, and make the call with the full picture in view.
