How much can you realistically save by auditing your SaaS stack?

Do not start with a percentage target. Calculate savings line by line: removed inactive seats, the quoted difference for a lower plan, subscriptions eliminated after a workflow review, and the vendor's actual annual discount. Subtract migration cost and prepaid commitments before calling the result a saving.

What is a good SaaS spend per employee?

There is no universal good number. Spend per active user is useful because it normalizes for team size, but engineering, sales, support, and regulated teams have different requirements. Track your own trend and investigate increases that are not explained by headcount or approved capability.

Should I switch my SaaS subscriptions to annual billing to save money?

Only when the vendor's actual annual discount beats the value of cancellation flexibility. Calculate the breakeven month from the current quote and consider prepaid cash, expected use, and non-refundable terms before committing.

What are ghost seats and how do I find them?

Ghost seats are paid licenses still being billed for people who have left, changed roles, or never used the tool — the single largest silent leak in most stacks, because per-seat tools keep charging whether or not anyone logs in. Find them by exporting each tool's user list and reconciling it against your current headcount or an active-directory roster, then checking last-login or last-active dates. Anyone inactive for 60–90 days is a candidate for removal. Deprovisioning at offboarding, not at audit time, is the permanent fix.

How often should a company audit its SaaS subscriptions?

A full stack audit once or twice a year, plus a lightweight per-renewal check that's far more effective: review each subscription 30 days before its renewal date, when cancellation is still possible and you have leverage. The recurring discipline beats the occasional purge, because SaaS waste re-accumulates continuously as people add tools and headcount changes. Assigning an owner to a renewal ledger turns a one-time cleanup into a standing control.

How to Audit Your SaaS Stack From Invoices (2026)

A credible SaaS audit does not begin with a promised saving. It begins with evidence: invoices, active-user exports, plan features, renewal dates, and a map of which job each tool performs. That evidence finds inactive seats, unnecessary plan tiers, overlapping workflows, and billing commitments that cost more than their flexibility is worth.

1. Stop looking at total spend. Per-seat is the diagnostic.

Total SaaS spend does not account for team size. A more useful internal trend is spend per active seat, because it normalizes across company size and turns "is this a lot?" into a question you can actually answer.

There is no universal good figure because requirements vary by function and industry. Use the calculator's bands only to prioritize review. The stronger signal is your own per-active-user trend: when it rises, document which new capability or contract explains the increase.

Get your per-seat score in two minutes — list your tools and seats in the SaaS Subscription Audit and it grades your stack lean → critical and surfaces the annual billing you're leaving on the table.

2. The three wastes that actually compound

"Unused subscriptions" is one kind of waste, and the least interesting. Three others compound silently and account for most of the recoverable spend:

Ghost seats (orphaned licenses). The single biggest leak. Per-seat tools keep billing for people who left, changed teams, or never logged in — because deprovisioning rarely happens at offboarding. A 10-seat plan where 3 seats belong to former employees is a 30% overpay on that one line, invisible until you reconcile the user list against current headcount.
Tier inflation.Vendors design pricing so that one feature you need sits one tier above the plan that covers everything else you use. You end up on Enterprise for a single SSO requirement or a seat threshold, paying for a dozen capabilities you'll never touch. Auditing which tier-defining feature you actually use frequently reveals you can drop a level.
Functional overlap. Because SaaS adoption is bottom-up, teams accrete redundant tools: Notion and Asana and Linear all managing projects; Zoom, Google Meet, and Slack huddles all doing video; two analytics tools, three places to store files. Nobody chose the redundancy — it grew. Mapping tools to jobs rather than to vendors exposes where one could replace three.

3. Calculate recoverable spend line by line

Do not assign a generic percentage to the stack. Build a recoverable spend schedule with evidence for each line:

Inactive seats: seat price multiplied by licenses confirmed inactive and eligible for removal.
Plan right-sizing: the current quote minus the lower-tier quote, after confirming required features remain.
Overlap: the removable subscription cost minus migration, retraining, and termination costs.
Annual billing:the vendor's actual monthly versus annual quote, adjusted for the period you expect to retain the tool.

Sum only the lines that survive this check. The result may be small or large; its value is that it can be reconciled to invoices.

4. The annual-vs-monthly arbitrage — and its trap

Annual billing may reduce the quoted monthly equivalent, but "switch everything to annual" can be expensive. The saving may be real on your corestack — the tools you'd bet money you'll still run next year. But prepaying twelve months on a tool you abandon in month four is a negativesaving: you've converted a cancellable monthly cost into sunk, unrecoverable spend.

So the rule is conditional, not blanket: annualize the keepers, keep the experiments monthly.Run each tool through a one-line test — "will we still be using this in twelve months?" If the honest answer is yes, take the annual discount. If it's "probably" or "we're still evaluating," the flexibility of monthly is worth more than the discount. Use the current vendor quote rather than a generic discount assumption.

The SaaS Subscription Audit flags exactly how much each line would save on annual billing, so you can annualize the keepers without doing the math by hand.

5. The renewal ledger — the leverage moment nobody owns

Here is why SaaS waste re-accumulates no matter how thoroughly you purge it once: subscriptions auto-renew, and the only moment you have real leverage — to cancel, downgrade, or renegotiate — is the narrow window before the renewal date. When no named owner tracks that calendar, the renewal can pass without a usage or pricing review.

The fix is structural, not heroic: a renewal ledger— a simple table of every subscription with its renewal date, owner, seat count, monthly cost, and a "still needed?" column, reviewed 30 days before each renewal. That review is where the audit stops being an annual event and becomes a standing control. It's also your negotiating window: vendors discount far more readily 30 days out from a renewal you're visibly willing to walk from than they do mid-term.

6. Two audit lenses: seat-based vs usage-based

A subtlety that trips up otherwise-careful audits: not all SaaS bills the same way, and the two models need different scrutiny.

Seat-based tools (Slack, Figma, Notion, most CRMs) — audit the seats. Ghost seats and tier inflation are the targets. The bill scales with headcount, so the user list is your battlefield.
Usage-based tools (Datadog, Twilio, cloud infra, LLM APIs) — audit the consumptionand the commitment tier. There's no "unused seat" to find; the overspend hides in unthrottled usage, over-committed reserved tiers, or inefficient configuration. A "cancel what you don't use" frame misses this entirely, because you are using it — just more expensively than you need to.

If your AI and infrastructure lines are a meaningful share of spend, they deserve their own consumption audit rather than being lumped into the seat review. The LLM API cost calculator is built for that side of the ledger.

7. The consolidation trap: compute the payback period

Eliminating overlap is the most satisfying cut and the easiest to get wrong. Collapsing three tools into one platform looks like obvious savings — until you account for the migration: data export and import, workflow rebuilding, retraining the team, lost features you only discover you depended on, and the productivity dip during the switch. Those costs are real even though they don't appear on an invoice.

Before consolidating, do the unglamorous arithmetic: how many months of the saved subscription does the migration cost consume? If killing a $200/month overlap takes a two-week migration and a month of reduced output, the payback period might be most of a year — and if you'd have re-evaluated the surviving tool by then anyway, the cut wasn't worth it. Consolidate where the payback is short and the surviving tool is one you're committed to. Leave overlaps that are cheap to keep and expensive to merge.

The playbook

Compute spend per active seat first. It tells you whether you have a problem and how big, before you touch a single subscription.
Reconcile every user list against current headcount. Remove licenses only after confirming inactivity and contract terms.
For each tool, name the feature that sets your tier. If you can't, you're probably one tier too high.
Map tools to jobs, not vendors. Where one job has three tools, plan a consolidation — but check the payback period before pulling the trigger.
Annualize the keepers, keep experiments monthly. Use the quoted discount only where retention exceeds breakeven.
Build a renewal ledger and assign an owner. Review each line 30 days before renewal. This is what stops the waste from growing back.

Start with step one. The SaaS Subscription Audit scores your per-seat spend and finds your annual-billing savings in one pass. For the payments side of your stack, the Stripe True Fee Calculator does the same for processing costs.

FAQ

Isn't cutting tools just going to slow the team down?

A bad audit does; a good one doesn't. Confirmed inactive seats, unused paid features, and favorable billing changes can remove spend without removing capability. Consolidation touches workflows, so apply the payback-period test rather than cutting reflexively.

What's the difference between a SaaS audit and just cancelling things?

Cancelling is a one-time reaction to obvious dead weight. An audit is a method: record invoice spend, classify findings into ghost seats, tier inflation, and overlap, decide each line on evidence, and install a renewal ledger so the result holds. The cancellation captures maybe a third of what's recoverable; the structural work captures the rest and keeps it captured.

Who should own SaaS spend in a small company?

One named person — usually whoever owns finance or operations — even if buying stays decentralized. The owner doesn't approve every tool; they hold the renewal ledger, run the per-seat number, and schedule review early enough to meet each contract's cancellation deadline.

Are these per-seat benchmarks the same for every business?

No — they're a starting reference, not a universal target. Engineering- and data-heavy organizations legitimately run higher per-seat tooling than sales- or ops-led ones. Use the benchmarks to locate yourself roughly and, more importantly, to watch your own trend over time. A rising per-seat figure is the signal, whatever your baseline.

Pricing benchmarks current as of 2026-06-09. General operational guidance, not financial advice — confirm current plan pricing on each vendor's page before making changes.

How to audit your SaaS stack from invoices