The Seat Audit: Turning SaaS License Cleanup Into a Quarterly Discipline
Photo: Adobe, Public domain, via Wikimedia Commons
Ask a mid-market IT director how many SaaS applications the company pays for and you will usually get a confident number that is wrong by a third. Ask how many seats are actually in use across those applications and the confidence evaporates entirely. The gap between the two figures is where license waste lives, and in a 1,500-person US enterprise it commonly runs into six figures annually.
The reason the gap persists is not laziness. It is that SaaS procurement is distributed. Departments buy their own tools, renewals scatter across the calendar, and nobody owns the aggregate view. The remedy is not a heroic one-time audit. It is a repeatable quarterly process—short, boring, and documented—that turns license optimization into ordinary IT operations.
Why the Cadence Matters More Than the Method
A single cleanup generates a spike of goodwill and a savings number that finance will remember for one fiscal year. A recurring harvest generates something more useful: a defensible baseline. After four quarters you can tell your CFO what the portfolio costs per active user, which applications are drifting upward, and which renewals habitually arrive with an above-market uplift. That is not cost-cutting. That is software asset management, and it is a visible, portable skill.
Step One: Build the Inventory and Assign an Owner
Start with the finance ledger, not the IT service catalog. Pull twelve months of software spend by vendor, normalize the vendor names, and produce a single list. Then assign an accountable owner to every application—a named human, not a department. Applications with no identifiable owner are the most likely to be over-licensed and the easiest to renegotiate, because nobody will defend them loudly.
Step Two: Pull Usage Telemetry in Three Layers
Usage evidence should come from more than one source, because each has blind spots.
- SSO sign-in logs. The strongest signal for applications behind your identity provider. A ninety-day lookback with a thirty-day recency flag catches most genuine inactivity.
- Vendor admin consoles. Necessary for anything outside single sign-on, and for validating seat counts against what you are actually billed.
- SCIM or provisioning data. Useful for spotting orphaned accounts tied to departed employees—a security finding as much as a financial one.
Where a tool is not integrated with single sign-on, treat the absence of telemetry as a finding in itself and put it on the integration roadmap. You cannot manage seats you cannot see.
Step Three: Publish a Rolling Renewal Calendar
List every contract with its term, auto-renewal notice window, uplift cap, and true-up clause. Sort by notice date rather than expiration date—the deadline that matters is the one after which you lose leverage. Most enterprise agreements require sixty to ninety days' notice; a calendar organized by expiration will consistently arrive too late.
Share the calendar with finance and with the department liaisons. Visibility alone changes behavior, because a manager who sees a renewal approaching is far more likely to answer an email about seat counts.
Step Four: Have the Conversation, Not the Confrontation
The politically loaded part is reclaiming seats from teams that insist they need every one. A few practices make this survivable.
Do not reclaim silently. Send a notice with the usage data attached, a two-week response window, and an explicit path to appeal. Offer downgrades and provisional reductions rather than cancellations wherever the tool is genuinely used. Frame the exercise as reallocation: seats recovered in one area can fund a request another department has been waiting on, which converts a cost conversation into a capacity conversation.
Expect two categories of pushback. Executives and their assistants will claim continuous need; verify rather than argue, and let the data do the talking. Contractors and seasonal staff will often have genuine spikes—a tax team in March, a retail support surge in November—so build a seasonal overlay into the analysis rather than treating a quiet quarter as proof of disuse.
Step Five: Prepare the Negotiation Before the Renewal Call
Arrive with four numbers: current seats, active users at the ninetieth percentile, the utilization percentage, and the per-seat price you are paying relative to comparable contracts. Vendors respond to specific, evidenced requests. "We are renewing at eighty-two percent of current seat count, and we would like the per-seat rate held flat" is a conversation. "Can you do better?" is not.
Where a vendor will not reduce seats, ask about tier restructuring, consumption-based terms, or multi-year pricing with a documented out clause. Where an application is used by fewer than a dozen people and duplicates a platform already licensed, the honest recommendation is consolidation, and saying so builds credibility for the renewals you do want to keep.
Step Six: Close the Loop in One Page
At the end of each quarter, publish a single page: seats reclaimed, spend avoided, uplift declined, and the two or three applications flagged for replacement. Send it to finance and to your CIO. This document is the difference between an initiative and a discipline. It also happens to be the strongest evidence you will ever have that you can run a program, not just a queue.
The Pitfalls Worth Naming
Do not reclaim seats from compliance, security, or audit tooling on the basis of login frequency alone; some systems are supposed to be quiet. Do not run the harvest during a major migration or an incident-heavy month, when nobody has bandwidth to respond and silence will be mistaken for consent. And do not let the process become an annual ambush. The credibility of a quarterly cadence depends on it being predictable enough that department leads plan for it.
Run it four times and the exercise stops being about licenses. It becomes the mechanism by which your organization finally knows what it owns.