The Seat Audit That Actually Finds Wasted SaaS Spend
Nobody signs off on wasted software spend on purpose. It accumulates one unrenewed offboarding step at a time: a contractor's access never gets pulled, a team switches tools and forgets to cancel the old one, a manager buys five seats for a project that shrinks to two people.
Finding it requires comparing two lists that almost never get compared: who's actually logging in, and who's still being billed for.
Vendors Covered in this Article
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
Why seat waste hides in plain sight
Approval happens once, at purchase, when someone justifies the seat count against a real need. Nobody owns the opposite question afterward, whether that need still exists three, six, or twelve months later, because it's nobody's job to ask it on a schedule. The seat just keeps renewing until someone happens to notice. Multiply that pattern across every tool your company has bought in the last few years and the accumulated waste is rarely a single dramatic contract, it's dozens of small ones that never individually looked worth chasing.
Which two lists do you need to pull for a seat audit?
Pull the tool's own usage or login report, which most vendors will provide even without an enterprise contract, and your current HRIS roster of active employees and contractors. Cross-reference the two: anyone licensed but not active in the login report in the last 60 to 90 days is a candidate for reclaim, and anyone active in your HRIS who left the company but still shows a license is an immediate one. Say two tools both show ten inactive seats, at $150 a seat that's worth chasing immediately, and at $10 a seat it can wait for the regular quarterly pass instead of an urgent one.
Running the reclaim without breaking anyone's workflow
Deactivate rather than delete a license on the first pass, since a false positive, someone on leave or using the tool less that particular month, is far cheaper to undo than a deleted account with lost data. Give a short grace period, and notify the person's manager before the license actually lapses, so anyone who genuinely still needs it can say so before you've already reassigned the seat. Document the reclaim policy itself, in writing, before you run it the first time, so nobody can argue later that a specific removal was arbitrary.
Here is the reclaim sequence in order:
- Pull the tool's own usage or login report and your HRIS roster of active employees and contractors.
- Flag anyone licensed but inactive for 60 to 90 days, plus anyone who left the company but still holds a license.
- Deactivate rather than delete on the first pass, so a false positive is easy to undo without losing data.
- Notify each affected person's manager and allow a short grace period before the license actually lapses.
- Record the reclaimed amount as a named line in your monthly spend review so the win stays visible.
Who should own a seat audit, and how often?
This works best as a shared job between finance and IT, run quarterly, not as a one-time cleanup project that nobody repeats. Finance has the invoice and the incentive to care about the number; IT has the access to actually run the reclaim without breaking anyone's login. Neither side alone tends to keep the cadence going past the first pass. Put a specific date on the calendar for the next round before you close out the current one, since planning to do it again sometime is exactly how the first cleanup effort quietly became the only one.
Give the process an owner by name, not by department, since a task that belongs to finance in general or IT in general is a task that belongs to nobody in particular once the person who ran it the first time moves to another project.
Where automation actually helps here
If your HR system already tracks who's active and which tools they're provisioned for, a platform like Rippling can flag the mismatch between active headcount and licensed seats automatically instead of you running a manual pull every quarter. That doesn't replace the judgment call on borderline cases, the person on leave, the seat kept for a project restarting next quarter, but it removes the tedious part that's the real reason most teams only do this once.
What to do with the money you actually reclaim
Reclaimed seats are worth tracking as a specific, named line in your monthly spend review, not folded quietly back into the general software budget where the win disappears. Naming the number, even a modest one, is what keeps the next person willing to run the audit again instead of treating it as a thankless one-off.
What Good Looks Like
The standard is that every licensed seat can be tied to a specific active person with a specific current use, checked on a repeating schedule, not verified once at purchase and never again.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
Frequently Asked Questions
How often should we actually run this?
Quarterly is the sweet spot for most companies: frequent enough to catch waste before it accumulates into a large number, infrequent enough that it doesn't become a constant, resented process for the team running it. Monthly makes sense only for your handful of highest-cost, highest-headcount-churn tools.
What if a manager pushes back on a seat we flagged?
Ask them to state, specifically, who's using it and for what, rather than accepting a general objection. A real, current use case should keep the seat; a vague sense that it might be needed later is exactly the answer this process exists to catch, and it's fine to require a name and a reason.
Does this only work for big companies with lots of tools?
No, a ten-person company with fifteen SaaS subscriptions can waste a meaningful share of its software budget just as easily as a five-hundred-person one. The audit also takes less time with fewer tools and fewer people to cross-reference.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
Is Your Copilot Seat Actually Paying for Itself?
A practical way to measure whether AI coding tool seats are worth their cost, beyond adoption rate, using output and review metrics you already track.
Budgeting for an AI Security Audit Before It Surprises You
Plan the AI-specific scope of a security audit: what changes, where audit hours go, and how to budget for evidence and vendor paperwork in advance.
Per-Seat or Consumption Pricing: Which AI Vendor Contract Actually Fits
How to tell whether a per-seat or usage-based AI software license actually fits your team's real usage pattern, and what to negotiate either way.
Why AI-Native Software Runs Lower Gross Margins Than SaaS
How variable inference cost changes gross margin for an AI-native product versus classic SaaS, and how to explain the gap to a board without a red flag.
What Evaluating Your AI Agent Actually Costs to Run
See where AI agent evaluation cost comes from: judge-model calls, human review and test set upkeep, with a worked run example and ways to keep spend in check.
Build Your Own AI Inference Cost Model in Three Tabs
How to structure a spreadsheet that turns token usage into a real cost per customer, so you can see GPU and API spend before the invoice arrives.