The SaaS Subscription Audit Checklist: Find, Classify, Cut, Renegotiate
Run a SaaS subscription audit for your small business: where to find every subscription, how to spot zombie seats and duplicates, and when to negotiate.
Subscriptions 6 min read
Software subscriptions are the fastest-growing line in most small-business overheads and the least examined. Nobody signs off a $40-a-month tool with the scrutiny they would give a $480 invoice, yet that is what it is. This checklist walks you through a subscription audit from scratch: where to find every subscription you are paying for, how to classify what you find, how to spot zombie seats and duplicate tools, when to negotiate, and how to make the exercise a quarterly habit rather than an annual panic.
Step 1: Build the inventory from more than one source
The reason audits miss things is that no single source is complete. Subscriptions are bought on company cards, personal cards that get expensed, through resellers, inside app marketplaces, and by invoice. Pull from all of these:
- Card and bank statements for the last twelve months, not three. Annual plans only show up once, and the ones you have forgotten are the annual ones.
- Expense claims. Search for recurring merchants in your expense system or in the accounts-payable ledger.
- Single sign-on and identity provider logs (Google Workspace, Microsoft Entra, Okta). The list of apps users have authorised reveals tools that were never purchased centrally.
- Accounts-payable invoices for larger contracts billed directly.
- App store and marketplace billing: Apple, Google Play, Shopify, Atlassian, Salesforce AppExchange and similar all bundle add-ons into one line.
- Ask the team. A two-question survey — “what do you pay for?” and “what do you log into weekly?” — usually surfaces three or four tools nobody in finance knew about.
Expect the final list to be 30–50% longer than whatever finance believed it was. That is normal and is the point of the exercise.
Step 2: Record the same facts for every subscription
An audit is only reusable if every entry carries the same fields. The table below is the minimum; add columns for cost centre or department if you allocate costs.
| Field | Why it matters |
|---|---|
| Tool name and vendor | Vendors rename products; the invoice name and the login name often differ. |
| Owner (a person, not a team) | Someone must be able to answer “do we still need this?” |
| Purpose in one line | Forces the question of what business function it serves. |
| Plan tier and seat count | Over-tiering is as common as over-seating. |
| Price, currency and billing cycle | Normalise to an annual figure so tools can be compared. |
| Payment method | Which card, which account, or invoice. Needed when cards expire or staff leave. |
| Renewal date and notice period | The date the decision has to be made, not the date the money leaves. |
| Contract or auto-renewal terms | Monthly rolling, annual auto-renew, or fixed term with notice. |
| Active users in the last 30 days | From the tool’s admin console; the single best signal of value. |
| Data held and integration dependencies | Cancelling a tool that feeds three others is a project, not a click. |
Step 3: Classify what you found
Sort every subscription into one of four buckets:
- Core — the business stops without it (accounting, email, the main product stack). Audit for tier and seat count, not for existence.
- Productive — clearly used, clearly valuable, could be replaced with effort. Audit for price and for overlap.
- Marginal — used by one or two people, low cost, unclear value. Ask the owner to justify it in a sentence; if they cannot, it goes.
- Zombie — nobody owns it, nobody logs in, it is still billing. Cancel.
The classification matters more than the total. Businesses that do this for the first time typically find that a fifth of their subscriptions are marginal or zombie, and that the money involved is smaller than the attention they have been consuming.
Step 4: Hunt for zombie seats and duplicate tools
Within the tools you keep, the waste is in the seats. Three checks:
- Leavers. Compare the user list in each tool’s admin console with the current employee list. Every departed employee still holding a paid seat is money and, more seriously, a security exposure.
- Inactive seats. Most admin consoles show last login. Anyone inactive for 60 days is a candidate for downgrade to a free or viewer seat.
- Tier creep. A plan that was upgraded for one feature during a project rarely gets downgraded when the project ends.
Duplicates are the other side. Group your list by function — project management, file storage, video calls, e-signature, design, password management — and look for two or more tools in the same group. The usual pattern is that two teams each adopted a tool independently. Pick one, migrate, and set a decommission date for the other.
Step 5: Negotiate before the renewal date, not after
Vendors have almost no incentive to discount a customer who has already auto-renewed. Leverage exists only in the window before the renewal, and only if you know when it is. For each contract worth negotiating (as a rule of thumb, anything over a few thousand a year):
- Open the conversation 60–90 days before renewal. Ask for the renewal quote in writing.
- Have your usage numbers ready. “We are paying for 40 seats and using 26” is a stronger opening than “can you do better?”
- Ask about annual prepayment discounts, multi-year price locks, and removal of automatic price escalators.
- Be willing to walk, and have a credible alternative identified. This is where the duplicate-tool work pays off.
- Get the notice period confirmed and diarised. If notice must be given 30 days before term end, your last day to cancel is a date you should know by heart. Our guide to auto-renewal notice periods covers the date arithmetic.
Step 6: Make it quarterly
A one-off audit decays within six months as new tools arrive and people leave. The sustainable version is light and regular:
- Monthly: any new recurring merchant on the card statement gets added to the inventory with an owner.
- At offboarding: the leaver checklist includes removing them from every tool on the list.
- Quarterly: a 30-minute review of renewals falling in the next quarter, and a seat-count check on the five most expensive tools.
- Annually: the full inventory rebuild from statements and SSO, as described in Step 1.
The quarterly review is where the renewal dates earn their keep. If every subscription has a renewal date and a notice period recorded, the quarterly meeting is simply the list of decisions due in the next 90 days.
How Trackords helps
Trackords is a free tracker built for exactly this kind of recurring deadline. Set up a “Subscription” record type with the fields in the table above as custom fields — owner, plan tier, seats, payment method, notice period — and import your audit spreadsheet by CSV in one go. Each subscription record can carry up to three email reminders at a chosen number of days before renewal (say 90, 45 and 10), plus an optional alert on the renewal day, so the negotiation window never passes unnoticed.
Reminders reach every active user in the workspace plus an optional extra address per record, so the tool owner and the finance lead both hear about it. Attach the contract and the latest renewal quote to the record, and the audit log records who changed the seat count or price. Viewer, editor and admin roles let department heads see their own tools without editing the master list. There is no credit card and no trial period; see the subscription tracker page, or compare the approach with running it in a spreadsheet.
Frequently asked questions
How often should a small business audit its SaaS subscriptions?
Do a full inventory rebuild once a year and a light review every quarter covering the renewals due in the next 90 days. Add new recurring charges to the inventory monthly as they appear on card statements.
What is a zombie subscription?
A subscription that is still billing but has no owner and no active users, usually left behind by a leaver or a finished project. They are found by comparing card statements with admin-console login data.
What should I record for each subscription?
At minimum: vendor, owner, purpose, plan tier and seat count, annualised price, payment method, renewal date, notice period, auto-renewal terms and active users in the last 30 days.
When is the best time to negotiate a SaaS renewal?
Open the conversation 60 to 90 days before the renewal date, before any auto-renewal notice deadline passes. After the contract has renewed the vendor has little reason to offer a discount.
Track these dates in Trackords — free
Your own record types, up to three email reminders per record, and everyone on the team notified before the deadline.
Related guides
Contracts
Contract Auto-Renewal Notice Periods: How to Calculate the Date That Matters
Auto-renewal clauses: how notice periods work, how to calculate the last day to give notice, a worked example with dates, and what to do if you missed it.
Domains & IT
Domain and SSL Certificate Expiry: Why It Happens and How to Prevent It
Why domains and TLS certificates lapse and how to prevent it: inventory, auto-renew pitfalls, 90-day certificates, registrar locks and a monitoring checklist.
Using Trackords
How to Set Up Expiry Reminders in Trackords
Step-by-step: create a Trackords account, set up record types, set three reminders and an expiry alert, pick recipients, import CSV and read the dashboard.