The Hidden Cost of Vendor Sprawl: A Lean IT Audit Worksheet
The phrase “digital waste” gets thrown around as marketing copy. It has a real, measurable shape: the SaaS contracts you renewed last year that nobody actually uses. The redundant tools that overlap with three other tools. The “zombie” servers running a workload that was retired in 2023.
We start every Lean-First engagement with a vendor-sprawl audit. Here’s the worksheet we use, public for the first time.
Step one: list every SaaS contract over $1,000/year
Pull this from your AP system, not from the IT inventory. The IT inventory is what IT thinks is being paid for. AP is what’s actually leaving the bank. The gap between the two is usually 20–30% on the first pull — contracts the IT team didn’t know existed because a department signed up directly.
For each contract, capture:
- Vendor name + contract end date
- Annual cost
- Owner (the person whose name is on the contract)
- Sponsor (the person who actually decided to buy it)
- Listed users (per the vendor’s admin panel)
Step two: get actual usage data per tool
This is the step everyone skips. Don’t accept “marketing says we have 80 active users” — get the real number from the vendor admin panel itself. Most SaaS tools expose a 30-day-active or 90-day-active count.
Every contract gets a usage ratio:
Usage Ratio = (90-day active users) ÷ (paid seats)
Anything below 0.4 is a candidate for renegotiation or cancellation. Anything below 0.1 is a zombie contract.
In our last 12 audits, the median client had 22% of their SaaS spend on contracts with usage ratios below 0.1. That’s not a typo. One in five dollars going to tools nobody uses.
Step three: map functional overlap
This is where most savings hide. Lay out every tool in a matrix against the function it serves:
| Function | Tool A | Tool B | Tool C |
|---|---|---|---|
| Project tracking | Jira | Asana | Linear |
| Diagrams | Lucidchart | Miro | Whimsical |
| Documentation | Confluence | Notion | Coda |
| Internal chat | Slack | Teams | — |
| Forms / surveys | Typeform | Google Forms | SurveyMonkey |
| …etc |
Most mid-market firms have 4–6 functional areas where they’re paying for two or three tools that do the same job. Picking one and migrating off the others is rarely cheaper than the contract spend in year one (migration costs hurt), but pays for itself inside 18 months and reduces operational complexity permanently.
The pattern we see most: marketing bought Tool A in 2022, sales bought Tool B in 2023 because they didn’t know about Tool A, and the new VP brought Tool C from her last company in 2024. All three are running in parallel; nobody owns the consolidation.
Step four: the “zombie” infrastructure pass
This is the on-prem version of the SaaS audit. For every server, VM, or persistent cloud resource:
- When was it last touched (deploy, restart, config change)?
- What workload does it run today (not what it ran in 2022)?
- If we shut it down right now, what would break?
Anything that hasn’t been touched in 6 months and “we’re not sure what it does” is a zombie. The right answer is rarely “leave it running just in case.” The right answer is to inventory the dependencies, schedule a controlled shutdown, and reclaim the resource.
What the typical first audit recovers
Composite numbers from our last twelve engagements:
- 18% of SaaS spend in zero-usage or near-zero contracts — immediately cuttable
- 12% of cloud bill in zombie infrastructure
- 3–6 functional overlaps with consolidation potential of another 15–25% over 18 months
- Total year-one savings: typically 25–35% of total IT spend, with no capability loss
What we’d do
If you’re not sure how much vendor sprawl you have, the audit takes about a week. The output is a written ledger you can take to your CFO with a recommended cut list and a phased consolidation plan.
This is the Value Mapping phase of our Lean-First Approach — the first thing we do on every engagement. Read the approach → · Book a discovery call →