There is a specific moment in every growing company when the software bill stops making sense. Finance pulls a quarterly report, notices the line item for SaaS subscriptions is up 40 percent year over year, and starts asking who owns what. The answer, with embarrassing consistency, is that a third of the tools on the list have no active owner, no clear purpose, and usage numbers that would not justify the price tag of a single-user plan. This is not a failure of procurement. It is a failure of visibility, and it happens to almost every company that grows past 50 employees.
The interesting question is not "how did this happen." The interesting question is why the pattern is so consistent across companies in completely different industries. Understanding that is the key to fixing the problem without installing another layer of governance that everyone will resent.
The Accumulation Is Structural
A new company starts with a small software stack because someone has to make every purchasing decision personally. The founder picks the CRM, the first engineer picks the code editor and the deployment platform, and the first designer picks the design tool. That initial stack is coherent because one person held all the context.
Every subsequent hire changes the math. A new sales leader arrives with opinions about prospecting tools. A new product manager brings preferences from their last company. A contractor introduces a tool for a specific project and nobody removes it when the project ends. The stack grows by accretion, and the people who make the individual additions have neither the visibility nor the incentive to audit the whole.
Photo by Mizuno K on Pexels
Productiv's State of SaaS report tracks this pattern in detail and has found that the average mid-market company now runs more than 200 applications, with roughly half of them unknown to central IT. The report is worth reading in full because it breaks down the accumulation by department and by company size, which helps target the audit conversation.
The Cost Is Not Just the Subscription
When finance tallies the damage, they usually focus on the monthly bill. That is the visible half of the cost. The less visible half is what the proliferation does to the engineering and operations teams that have to integrate, maintain, and troubleshoot the tools.
Every additional SaaS tool adds a new login, a new integration point, a new permission model, a new data export path, and a new vendor contact. None of those are expensive individually. In aggregate, they consume real hours. Atlassian's team collaboration research has found that knowledge workers switch between an average of 10 tools per day and lose measurable productivity to context switching. A smaller, more deliberate stack is not just cheaper on the invoice. It is cheaper on every metric that matters to a growing company.
Why Unused Seats Are the First Place to Look
Before touching any tool evaluations or considering replacements, start with unused seats on the tools you already pay for. This is the highest-leverage move in any software audit because the savings come without any workflow disruption.
Run an export of active users on your top 10 most expensive tools. Compare that list to your current employee roster. The gap is almost always larger than anyone expects. It is not unusual to find 20 to 30 percent of paid seats belonging to former employees, former contractors, or accounts that were provisioned during an onboarding push and never deactivated. Canceling those seats is immediate money.
"I have never done a software audit where we did not find at least five paid seats belonging to people who left the company more than six months ago. It is almost universal. The good news is it takes about an hour to fix once you have the data." - Dennis Traina, 137Foundry
Okta's Businesses at Work report publishes benchmarks on per-employee software costs that make this easy to audit at the company level. If your per-employee software spend is more than 20 percent above the median for your company size, you almost certainly have unused seats hiding in the top five most expensive tools.
Photo by Andrey Kirsanov on Pexels
The Seven-Tool Rule
A practical rule of thumb that has held up across a number of audits: any department running more than seven distinct SaaS tools probably has at least two redundant ones. Seven is not magic, but it is the point where the cognitive load of maintaining the stack exceeds the benefit of specialization for most mid-market teams. When sales, marketing, or operations crosses that threshold, it is worth asking which tools could be consolidated onto a single platform without meaningful capability loss.
The conversation should not start with "what can we cut." It should start with "what job is each of these tools doing, and where do the jobs overlap." Almost every multi-tool department has two tools that cover substantially the same capability, with one being the current preferred tool and the other being a holdover from a previous team. The holdover is almost always safe to remove.
The Part Nobody Wants to Hear
The hardest category to address is the tools that are used, but used badly. A $2,000-per-month platform that three people log into weekly and use for five percent of its feature set is not a clear win for cancellation. The usage is real. But the cost per active user is absurd relative to what the team is actually getting, and the feature set is often overlapping with something your primary platform already includes.
Addressing this category requires a harder conversation than pulling unused seats. The people who use the tool are usually the ones who introduced it, and they tend to defend it. The right framing is not "we are canceling your tool." It is "we are asking every tool in this category to justify its cost on a per-use basis, and here is the data." That framing makes the conversation about the business case rather than personal preference, which is the only way these decisions get made cleanly.
For teams that want a repeatable framework for running this kind of audit, our complete guide to reducing business software costs without losing critical functionality covers the full process, including the scoring model we use to rank tools for review.
The Hidden Cost of Not Acting
Companies that postpone this work pay twice. They pay the direct cost of the subscriptions they should not be carrying, and they pay the indirect cost of a stack that is harder to integrate, harder to secure, and harder for new hires to learn. The indirect costs are the ones that eventually force the audit anyway, usually during a funding crunch or a new CFO's first month, which are the worst possible times to make thoughtful decisions.
The better time to run the audit is now, when the decisions can be made without pressure. The Gartner research on software rationalization has consistently found that companies that run audits proactively save significantly more than those that wait for a forcing event, because proactive audits have the time to consider workflow impact and run proper parallel periods during migrations.
None of this requires buying a SaaS management platform. A spreadsheet, a couple of SQL queries, and two afternoons of department interviews are enough to get the first audit done. The hard part is starting, which is usually blocked less by capacity than by the assumption that someone else owns the problem. In most companies, nobody does, which is why the bill keeps growing. If you want a second set of eyes on your stack or help thinking through a specific consolidation decision, 137Foundry has worked with a number of growing companies on exactly this kind of rationalization.
Top comments (0)