SaaS Sprawl: Why the Average Company Pays for 130+ Apps

The Data on How Many Apps Companies Really Have

The 130-app figure is not an outlier - it is the median for companies with 100 to 500 employees, according to research from multiple SaaS management vendors. The number is higher than most executives estimate because it includes tools that are not formally approved, tools that individuals use on personal cards, and tools that were adopted for a specific project and never cancelled.

The breakdown by company size is illuminating: companies with 50 employees average 40 to 60 tools. Companies with 200 employees average 100 to 150 tools. Companies with 500 employees average 200 to 300 tools. The growth is faster than linear - it tracks with the number of employees who have independent purchasing authority, not just total headcount.

How SaaS Sprawl Happens

SaaS sprawl is not a single event - it is an accumulation of individually rational decisions that create a collectively irrational outcome. Each of the three main drivers makes sense from the perspective of the person making the decision. The problem emerges when hundreds of people make similar decisions independently over years.

Decentralized Buying

In most modern companies, department heads have significant purchasing autonomy for tools under a certain threshold - typically $500 to $2,000 per month. This is by design: it allows teams to move fast and avoids bottlenecking every software decision through a central committee. The unintended consequence is that each department builds its own sub-stack of tools, with no visibility across departments.

Marketing buys a stack of content, analytics, and automation tools. Sales buys a stack of prospecting, enrichment, and outreach tools. Engineering buys a stack of development, deployment, and monitoring tools. Each stack is optimized for that department's needs - but the stacks often overlap significantly, and the total is a portfolio that nobody manages holistically.

The Freemium-to-Paid Pipeline

SaaS vendors have perfected the art of converting free users to paid customers without requiring any human approval. The pattern is consistent: free trial with generous limits, gradual reduction of limits as usage grows, a well-timed upgrade prompt. An employee who started using a free tool for a specific task finds themselves on a $49/month plan within 90 days.

At the individual level, $49/month is trivial. At the company level, if 30 employees each have two or three tools that followed this path, the monthly tab is $3,000 to $4,500 - often submitted as small expense reimbursements that nobody scrutinizes at the line-item level.

Shadow IT and Unapproved Purchases

As discussed in our guide on what is shadow IT, a significant fraction of company software spending happens completely outside the approved purchasing process. Employees buy tools on personal cards, use tools in free tiers that technically belong to the employee rather than the company, and introduce tools that bypass security reviews entirely.

Why It Gets Worse Over Time

SaaS sprawl has a self-reinforcing quality that makes it naturally get worse rather than better without active intervention. Several dynamics drive this:

The Cancellation Friction Asymmetry

Adding a SaaS tool is extremely easy - a credit card and an email address, and you have access within minutes. Cancelling a SaaS tool requires finding the cancellation settings, potentially submitting a cancellation request, waiting for confirmation, and updating any internal tracking. The asymmetry of effort strongly favors accumulation over rationalization.

Tool Advocates Protect Their Tools

Every tool has at least one internal champion who advocated for it. When the tool comes up for review, that person pushes back. Even if only 20% of the licensed users are actually using the tool, the 20% who use it are motivated advocates, while the 80% who do not are indifferent. This asymmetry of motivation means that tools rarely get cancelled at review - they get renewed by default.

Organizational Memory Fades

The person who originally understood why a tool was purchased often leaves the company or moves to a different role within 18 to 24 months. Once that organizational memory is gone, the tool persists on auto-renewal because nobody knows enough about it to make a definitive case for cancellation. Uncertainty defaults to renewal.

How to Get Back Under Control

Reversing SaaS sprawl requires addressing the structural drivers, not just doing a one-time cleanup. Three interventions have the most impact:

Visibility Before Everything Else

You cannot rationalize a portfolio you cannot see. The first step is always building a complete inventory - ideally from financial data, which captures shadow IT and informal purchases that no self-reported survey will surface. SubScrub automates this by connecting to your bank feed and building your SaaS inventory from transaction data.

A Lightweight Approval Gate

Most SaaS sprawl happens because adding a tool is frictionless. Adding a single point of lightweight friction - a Slack form, an email to ops, a simple request template - captures the majority of new purchases and creates the visibility needed to prevent duplicate buying. The gate should not be slow or bureaucratic; it should be fast enough that routing around it is not worth the effort.

Owner-Based Accountability

Every subscription should have a named owner who receives the renewal notification and must actively affirm continuation. This one change - moving from passive renewal to active reaffirmation - is enough to reduce SaaS sprawl by 20 to 30% over a two-year period, as tools without engaged owners get cancelled at renewal rather than defaulting to auto-renewal.