The hidden cost of too many software vendors, with a worksheet
The phrase “digital waste” gets thrown around as marketing copy. But it has a real, measurable shape. You see it in the software contracts you renewed last year that nobody actually uses. You see it when you have redundant tools that overlap with three other tools. You also see it in the zombie servers running a workload that you retired in 2023.
When your sales reps are jumping between six different apps just to pull a quote, your pipeline slows down. Every extra tool creates friction. We start every lean project with a thorough audit of your software setup. Here is the worksheet we use. We are making it public for the first time. You can use it to find out exactly where your money goes.
Step one: list every SaaS contract over $1,000/year
You need to pull this list from your accounts payable system. Do not pull it from the IT inventory. The IT inventory only shows what your tech team thinks you pay for. The accounts payable ledger shows what is actually leaving the bank.
The gap between these two lists is usually 20–30% on the first pull. These are the contracts the tech team did not know existed. Usually, a specific department signed up directly. A sales manager might buy a forecasting tool to help their reps track renewals. Nobody tells the central tech team.
For each contract, you must capture a few key details. Write down the vendor name and the contract end date. Note the annual cost. Find the owner whose name is on the contract. Identify the sponsor who decided to buy the tool. Finally, check the listed users according to the vendor admin panel.
Gathering this data takes time. But it highlights the tools that might be slowing down your sales process. When reps have too many tools, they spend less time selling.
Step two: get actual usage data per tool
This is the step that almost everyone skips. Do not accept guesses. Do not let someone say that marketing has 80 active users. You need to get the real number from the vendor admin panel itself. Most SaaS tools expose a 30-day-active count or a 90-day-active count.
You must look at these numbers. Then, give every contract a usage ratio. Here is the math you use:
Usage Ratio = (90-day active users) ÷ (paid seats)
This formula is simple but powerful. Anything below 0.4 is a prime candidate for a hard look. You should either renegotiate that contract or cancel it entirely. Anything below 0.1 is a zombie contract. You are paying for something that your team has abandoned.
In our last 12 audits, the numbers were striking. The median client had 22% of their SaaS spend tied up in contracts with usage ratios below 0.1. That is not a typo. One in five dollars is going to tools nobody uses. If a tool was meant to help reps manage quotes, but nobody logs in, it is not helping your pipeline.
Step three: map functional overlap
This step is where most of your savings will hide. You need to lay out every tool in a simple matrix. Map each tool against the function it serves for your team.
| 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 pay for two or three tools that do the exact same job. Picking one tool and migrating off the others is hard work. It is rarely cheaper than the contract spend in year one because migration costs hurt. However, this move pays for itself inside 18 months. It also reduces your operational complexity permanently.
The pattern we see most is always the same. Marketing bought Tool A in 2022. Then, sales bought Tool B in 2023 because they did not know about Tool A. Finally, the new vice president brought Tool C from her last company in 2024. All three tools are running in parallel. Nobody owns the consolidation effort. When sales reps have to check three different systems to find client notes, deals stall. Cleaning up this overlap directly helps your sales team move faster.
Step four: the zombie infrastructure pass
This step is the on-premise version of the SaaS audit. It focuses on your servers and heavy systems. For every server, virtual machine (a software computer), or persistent cloud resource, you need to ask three hard questions.
First, when was it last touched? This includes the last deploy, restart, or configuration change. Second, what workload does it run today? We do not care what it ran back in 2022. We only care about its current job. Third, if we shut it down right now, what would break?
Anything that has not been touched in 6 months is a red flag. If your team says they are not sure what it does, that resource is a zombie. The right answer is rarely to leave it running just in case. The right answer is to inventory the dependencies. You then schedule a controlled shutdown. Finally, you reclaim the resource. Less clutter means your systems run better.
What the typical first audit recovers
We track the results of our work carefully. Here are the composite numbers from our last twelve engagements:
- 18% of SaaS spend sits in zero-usage or near-zero contracts. You can cut this spend immediately.
- 12% of the cloud bill is tied up in zombie infrastructure.
- We find 3–6 functional overlaps. These have a consolidation potential of another 15–25% over 18 months.
- The total year-one savings are typically 25–35% of total IT spend. You get these savings with zero capability loss.
These numbers represent real money. You can take that money and invest it back into your team.
Next step
If this sounds like your team, we can look at it together. A free pipeline review takes thirty minutes and ends with a written list of what to fix first. Book a review.