Ask a CIO how many SaaS applications the company runs and the answer is usually half the real number. Discovery scans at most enterprises surface two to four hundred subscriptions, a meaningful share of which were never reviewed by IT. Renewals auto-charge, seats sit idle, and overlapping tools do the same job in parallel. SaaS sprawl is not an accounting curiosity – it typically represents 30-40% of software spend that could be recovered or redirected. Here is how to run an audit that actually shrinks the stack.
Inventory everything, then find what the inventory missed
Start with the sources you have: finance’s subscription ledger, expense-card feeds, procurement records, and the SSO provider’s application list. Then cross-reference with discovery data – SSO logs, CASB or expense-management tooling, and firewall or DNS logs that reveal tools people use without logging in through the front door.
The expense-feed pass alone usually surfaces a third more tools than the official ledger: departmental subscriptions bought on corporate cards, monthly plans that never went through procurement, and free trials that quietly became paid.
Score every application on usage and overlap
With the full inventory in hand, score each application on three axes:
- Active usage: monthly active users, seats actually assigned versus purchased, and usage depth (daily work versus monthly login).
- Functional overlap: how many tools provide video conferencing, e-signature, project management, or BI? Overlap is where the quick wins live.
- Business criticality: what breaks tomorrow if this tool disappears – and is that documented anywhere?
The output is a simple matrix. High usage and unique function: keep. High overlap and low usage: consolidate or cancel. Unknown usage: investigate before the next renewal date, because inaction is a purchase decision too.
Attack the renewal calendar
Rationalization moves at the speed of the renewal calendar. Sort applications by renewal date and start negotiations ninety days out for the biggest spend items. For each, the options are consistent: renegotiate seats to actual usage, downgrade the tier that nobody exercised, consolidate two overlapping tools into one enterprise agreement, or cancel with a data-export plan.
One discipline makes this stick: no renewal proceeds without a named business owner confirming the value received in the last twelve months. The owner’s name on the line changes renewal conversations more than any dashboard.
Fix the intake, or the sprawl returns
An audit without process change buys you one clean year. Sprawl is a symptom of intake failure – departments buy tools because the official path is slow or does not exist. Stand up a lightweight request process: a short form, a two-week evaluation track for low-risk tools, a security review gate, and a public catalog of approved software with negotiated pricing.
Then measure the number that matters: new subscriptions entering the stack outside the process. When that hits zero for two consecutive quarters, the sprawl problem is actually fixed – and the next audit becomes a routine health check instead of an archaeology project.
Read next: Building AI-Powered Workflows in n8n: A Practical Starting Point