How Much Does SaaS Sprawl Really Cost Your Business?

SaaS spending has grown at a compound annual rate of roughly 18% for the past five years. The average mid-size enterprise now pays for between 150 and 500 SaaS applications, depending on how aggressively department heads have been able to self-procure outside IT channels. And the average organization wastes between 25% and 40% of that spend on licenses that are either entirely unused or heavily underutilized.

Those are averages from industry research. Here's what we see in the field: the numbers are often worse than averages suggest, particularly in organizations that grew quickly, went through acquisitions, or made a rapid shift to remote work over the past few years.

The Real Cost of SaaS Sprawl — By Category

When we talk about "the cost of SaaS sprawl," most people think about wasted license fees. That's real — and it's directionally large — but it understates the total impact significantly. SaaS sprawl has at least four distinct cost categories:

1. Direct License Waste

This is the most visible cost: licenses you're paying for that nobody is using. Industry research from Zylo, Torii, and Productiv consistently finds that between 30% and 45% of SaaS licenses are either completely inactive or used by fewer than one in five assigned users on a monthly basis.

For an enterprise spending $10M annually on SaaS, that's $3M–$4.5M in direct waste. Most organizations we work with don't have precise data on this figure because they've never pulled their utilization reports across all applications simultaneously. When they do, the number is almost always surprising — and often alarming.

2. Duplicate Capability Cost

Redundancy is a separate cost category from underutilization. An organization might have two project management tools, both with high utilization, that serve the same function for different departments. Neither shows up as "waste" in a simple utilization analysis, but one of them is redundant — and its cost is recoverable.

In our engagements, functional redundancy typically represents an additional 10–15% of SaaS spend beyond the direct license waste number. In organizations that have gone through acquisitions without portfolio integration, this can be significantly higher.

3. IT Support and Overhead Cost

Every application in your portfolio requires IT resources: provisioning access, handling support tickets, managing integrations, maintaining security configurations, and responding to incidents. The more applications in the portfolio, the higher this overhead.

IT support and overhead averages approximately 15–20% of direct software spend across mid-to-large enterprises. This is harder to quantify precisely because it's embedded in IT labor costs rather than appearing as a line item, but it's real. Organizations that reduce their application count by 30% typically see meaningful reductions in IT support burden — often 10–15% — within the following year.

4. Security and Compliance Risk Cost

Every application you pay for but never use is a potential security exposure: stored credentials, active API integrations, data residency obligations, and vendor access to your systems that continues even after actual usage has dropped to zero. Dormant applications are a particularly attractive target for attackers, precisely because nobody is monitoring them closely.

Quantifying security risk as a dollar cost is imprecise, but regulatory fines under GDPR, CCPA, and HIPAA — which can reach into the millions for data incidents involving insufficiently monitored vendor access — make the risk real. Eliminating dormant applications is one of the fastest ways to reduce your attack surface.

"We had a SaaS vendor with access to our customer data management system that we had stopped using 18 months earlier. We were still paying for it, they still had an active integration, and nobody had flagged it. The audit caught it."

SaaS Spend by Company Size: What the Benchmarks Show

Industry benchmarks from Zylo's 2025 SaaS Management Index provide useful reference points:

• Companies with 1–99 employees: Average 40 SaaS apps. Average annual spend: $1.2M. Average waste: 38%.
• Companies with 100–999 employees: Average 185 SaaS apps. Average annual spend: $5.4M. Average waste: 33%.
• Companies with 1,000–4,999 employees: Average 420 SaaS apps. Average annual spend: $18.2M. Average waste: 30%.
• Companies with 5,000+ employees: Average 650+ SaaS apps. Average annual spend: $60M+. Average waste: 28–35% (varies widely based on M&A history).

The waste percentage tends to decrease slightly with company size — partially because larger organizations are more likely to have formal software asset management processes — but the absolute dollars at risk increase dramatically. A 30% waste rate on $60M in SaaS spend is $18M annually.

Shadow IT: The Hidden Multiplier

SaaS sprawl is amplified by shadow IT — applications adopted by business units without IT visibility or approval. Estimates of shadow IT as a percentage of total application count range from 15% to 40%, depending on company size, industry, and how permissive the organization has been about self-procurement.

Shadow IT creates specific risks beyond the standard sprawl costs:

• Data security: Business users storing company or customer data in applications that haven't gone through a security review
• Compliance risk: Data residency or processing obligations (GDPR, HIPAA, etc.) that apply to the data being stored in an unapproved system
• Integration complexity: Ad-hoc integrations built without IT knowledge that create fragile dependencies
• Audit exposure: Applications that should have been considered on HR or financial system audits but weren't because IT didn't know they existed

How to Calculate Your Organization's SaaS Waste

You don't need a formal audit to get a directional sense of your SaaS waste exposure. Here's a quick methodology:

1. Pull your total SaaS spend for the past 12 months from accounts payable and corporate card data.
2. Apply the 30% industry average waste rate to get a baseline estimate of your waste exposure.
3. Adjust upward if your organization has gone through any of: an acquisition in the past 3 years, rapid headcount growth (>30%) in the past 2 years, a shift to remote work without portfolio review, or a history of departmental self-procurement.
4. Adjust downward if your organization has formal software procurement gates, a recent SAM implementation, or a history of IT-driven license audits.

The resulting number is your directional waste estimate. It's almost certainly directionally accurate, even if the precise figure requires a formal audit to pin down.

What to Do With This Information

If your directional estimate suggests meaningful waste, the next step is a formal software portfolio audit. The audit quantifies the opportunity precisely, identifies which applications are the retirement and consolidation targets, and produces a concrete action plan with prioritized steps.

The payback on a well-executed audit is typically 10:1 or better in Year 1. Organizations that engage with us typically recoup the cost of the engagement within 60–90 days of beginning execution on Wave 1 recommendations.