Subscription software adds up: auditing what you pay for

A saas subscription audit is a recurring inventory that compares every billed seat, plan tier and auto-renewal with actual login activity and feature use. The mechanism is simple: gather the invoices, map each licence to a named user, and cut or downgrade anything not earning its keep. You will usually find more waste than you expect.

Key Takeaways

• An audit is a recurring discipline, not a one-off spreadsheet: usage changes every quarter.
• Seat-level data — last login, role and feature use — is the only signal that matters.
• Unused licences, duplicated tools and tier creep are the three biggest findings.
• Rank cancellations by monthly recurring cost first, not by how irritating a tool is.
• Assign a named owner to every subscription so renewals do not default to nobody's job.
• Security offboarding and cost audit are the same pass: one list, two outcomes.
• Keep the cadence quarterly, or the drift comes straight back.

Why does subscription spend keep creeping up on its own?

SaaS spend creeps upward because renewals are automatic, seats are added for every new hire and rarely removed, and no single person owns the full list. Each individual decision feels small — an extra plugin here, a premium tier there — but the compounding effect is what a saas subscription audit is designed to expose. Usage drift is the norm, not the exception.

There are three compounding forces. First, seats accumulate with every onboarding and almost never leave with every offboarding. Second, tools overlap: a design tool, a file-sharing tool and a project tool can all do a slice of the same job, and each one is billed separately. Third, vendors move features between tiers, so a plan you chose two years ago may no longer match what you actually use. None of these requires anyone to make a bad decision. They just require someone, eventually, to look.

What does a saas subscription audit actually cover?

A saas subscription audit covers four layers: the full invoice list, the people and seats on each tool, the features actually used, and the renewal terms attached to each contract. The deliverable is a single reconciled register — one row per subscription — that marks every line as keep, downgrade, consolidate or cancel. Without that register, you are guessing.

The register is where the audit lives or dies. Each row needs the vendor name, plan tier, billed seats, active seats, monthly recurring cost, renewal date and a named owner. You can hold it in a shared spreadsheet. What matters is that it exists in one place and that someone re-checks it. When tools are connected to each other, the register also shows integration points you must unpick before cancelling — something we cover in more depth in our guide to software integration before you cut a tool.

When do you actually need an audit, and when can you skip it?

You need a saas subscription audit when your company passes roughly ten paid tools, after any hiring surge or layoff, before a budget cycle, or whenever someone says they are not sure who owns a subscription. Skip it if you run two or three tools that everyone uses every day — the audit overhead would exceed the likely saving. Most teams pass ten tools faster than they think.

The trigger is not company size; it is the gap between who pays and who uses. A five-person team with nine subscriptions needs an audit as much as a fifty-person team with forty. If you are deciding between another subscription and custom software, the trade-off usually comes down to how much of the tool you genuinely use — see our comparison of custom software versus off-the-shelf before you add another line to the register.

How do you run the audit, step by step?

The audit runs as a five-pass process: inventory, usage check, tier match, action and renewal scheduling. Each pass produces a deliverable you can hand to a colleague, and each pass is cheap to re-run next quarter. Do not try to do all five in one sitting; the data is rarely ready for that.

1. Export every invoice and card statement from the last twelve months, and list each SaaS vendor once. Include anything billed through app stores as well as direct invoices.
2. For each tool, pull the admin console's user list and last-login date. If the console lacks usage data, query your SSO logs or ask the vendor for an activity export.
3. Tag every seat: active (weekly), occasional (monthly), dormant (60 or more days since login) or unknown. Unknown is a finding, not a pass.
4. Record the plan tier, per-seat cost driver and renewal date for every subscription. Note whether billing is monthly or annual.
5. Compare the tier against the features actually used. Mark obvious downgrades, and flag anything kept only because a leaver once needed it.
6. Assign a named owner and schedule the cancellation, downgrade or negotiation task on a renewal calendar at least thirty days before each renewal date.

Which findings should you act on first?

Prioritise by recurring monthly cost, not by how annoying the tool is. A dormant enterprise plan with twenty unused seats can outweigh fifty small browser extensions in saving. Rank every finding by monthly recurring cost first, then by how reversible the decision is. Cancellations are easily reversed; data migrations are not.

A common mistake we see: teams cancel the one obviously unused tool and feel done, while a duplicated product with overlapping licences keeps billing quietly in the background.

How do you verify the audit is working?

Verification is simple: watch cost per active seat fall, and watch the renewal calendar fill with owners. Re-run the register after one quarter and compare the number of dormant seats. A working audit cuts dormant seats each cycle and catches new subscriptions within weeks, not years. If the drift comes straight back, the ownership model has failed.

Track three numbers, not fifty. Cost per active seat should fall as you cut dormant licences. Dormant seat count should shrink each quarter. Owner coverage — the share of subscriptions with a named decision-maker — should rise toward one hundred per cent. If the first number drops but the second does not, you are cutting the wrong things.

What breaks if you skip the audit, and how do you debug the drift?

Skipped audits fail quietly, and the failure looks like a finance surprise rather than a crash: a charge you cannot trace, a licence you cannot reclaim, a leaver whose account still bills. Debug the drift by pulling the last ninety days of invoices, then walking each unrecognised line back to its admin console. The root cause is almost always the same: no owner and no renewal calendar.

The same ownership gap that lets subscriptions drift also shows up when software projects fail: nobody owns the outcome, so nobody notices the warning signs until renewal day. That pattern is one of the reasons a software rollout fails in ways that look unrelated at first. Fix the ownership habit in your subscription register and you fix part of it everywhere else too.

What does the audit cost in effort and overhead?

The cost of a saas subscription audit is mostly engineer or operations time, not software. A first pass across twenty to forty tools typically takes several focused days spread over two weeks; each quarterly re-run takes a few hours once the register exists. Where you store the register matters more than what you store it in — a shared spreadsheet beats an expensive platform you will not maintain.

The main cost drivers are the number of tools, how usable their admin consoles are, whether SSO gives you one login log to query, and who currently holds the card details. If the register feels like a burden after two quarters, the problem is usually that too many people can approve purchases. If you would rather not own the register yourself, our team can help you set it up and keep it current — see how we approach ongoing software maintenance.

Security and access considerations during the audit

An audit doubles as an offboarding pass. Every dormant seat is an account that can still authenticate, and a leaver's licence is a standing credential unless the SSO provider is in sync. While you are in each admin console, check who holds administrative rights and whether access revokes cleanly. Tie the cancellation list to the HR offboarding list and you fix two problems with one pass.

Check for tools that bypass SSO entirely — browser extensions, design apps and standalone utilities often sit outside your identity provider. Those are the accounts most likely to linger after someone leaves, because nothing automatically deactivates them. Treat any tool without an obvious owner and without SSO as a higher-risk cancellation candidate.

Common mistakes that make the audit fail

The most common mistakes are audit-only-once thinking, comparing tools by brand instead of use case, and letting the person who bought a tool decide whether it stays. Owners defend their purchases; that is human. Separate the data-gathering from the decision, rank by cost, and record the decision against the renewal date. Those three habits prevent most failed audits.

• Treating it as a one-time cleanup instead of a quarterly rhythm.
• Ranking tools by sentiment rather than recurring cost and usage.
• Letting the original buyer be the only voice in the keep-or-cut call.
• Recording decisions without a renewal date, so they never fire.

A realistic scenario: what a typical audit actually finds

Picture a thirty-person agency that has grown for three years without an audit. The register shows forty-one paid tools, four of which are duplicates for design or file-sharing, nine seats belonging to people who left, and six plans on a tier nobody uses. The first pass removes roughly eighteen per cent of monthly recurring spend, and the quarterly re-run keeps it down. That is a typical finding, not an outlier.

Alternatives compared

You have four realistic options: do nothing, run a manual register, adopt a SaaS management platform, or bring in outside help for the first pass. The right choice depends on tool count, team discipline and how much time the people who already carry the work can spare.

In short: a saas subscription audit is a small recurring discipline that pays for itself the first time it finds a dormant enterprise plan. Build the register once, assign owners, and review renewals quarterly. The alternative is paying quietly for years.

People also search for

• How often should we run a SaaS subscription audit?
• How do we consolidate overlapping business tools?
• SaaS or custom software: which costs less long-term?
• What makes a software rollout fail?
• How much does web software really cost?
• When does shared hosting stop making sense?
• What should we check before buying business software?

If you want a clean register and a renewal rhythm your team can actually hold, our team can help you run the first pass and set up the cadence. We work in your accounts, hand you the register, and leave the decisions with you. Start with a conversation at our contact page, or see how we approach custom software and system builds.