Deutsch

The SaaS Sprawl Problem: Signs You Have It and How to Fix It

The CEO didn't ask for an IT audit. The CFO had flagged that the software line in the P&L had grown 42% year-over-year, and the audit was meant to explain it.

It explained it. The company had eighty-seven active SaaS subscriptions. The CEO had heard of forty-seven of them. Of the remaining forty, some were tools that teams had bought and kept for years without anyone above the manager level knowing they existed. Some were free trials that had converted to paid without IT involvement. A few were tools provisioned for employees who'd left the company. One was a subscription to a tool nobody could identify at all — the original purchaser had departed and the contract had auto-renewed twice.

Total spend: $290,000 per year. Estimated waste: $90,000-130,000.

The sprawl hadn't happened because people were careless. It had happened because the company had grown from thirty people to two hundred without ever building a buying governance structure to match. When the team was thirty people, the CEO knew every tool. At two hundred, that was impossible, but no one had filled the governance gap.

The Signs You Have It

SaaS sprawl rarely announces itself. It accumulates. These are the signals:

The P&L signal: SaaS spend has grown faster than headcount. If your team grew 30% and your software line grew 60%, the excess is almost certainly sprawl. BetterCloud's State of SaaSOps report found that the typical mid-market company spends $5,000–$8,000 per employee per year on SaaS — and that organizations without formal SaaS governance spend 35–40% more per employee than those with structured oversight.

The audit signal: When you try to list your SaaS stack from memory, you consistently discover tools you forgot existed, and then find more when you look at the credit card statements.

The overlap signal: Teams in different departments are paying for tools that do substantially the same thing. Sales uses one project tracker. Marketing uses another. Operations uses a third.

The ghost user signal: Seats provisioned for employees who've left. This shows up in SSO logs as active accounts attached to former employees: still licensed, still billing, never used.

The shadow IT signal: IT discovers tools it didn't approve, often when a tool fails and the affected team asks IT for help. That's how IT first learns the tool existed.

The renewal surprise signal: Someone in finance flags a renewal they didn't expect, for a tool they didn't know was active, because the original purchaser left and nobody updated the ownership records.

If two or more of these describe your company, you have a sprawl problem. The diagnostic questions at the end of this guide help you assess severity.

Why This Happens at Mid-Market

The typical sprawl story follows the same arc: a company grows fast, teams find tools that solve their problems, each individual purchase makes sense, and nobody owns the aggregate picture. By the time the aggregate becomes visible (usually at an audit or a CFO review), the stack is complex enough that untangling it is a multi-month project.

Three structural factors accelerate sprawl at mid-market companies:

Product-led growth. Most modern SaaS tools have free tiers or freemium models designed to spread adoption before procurement is involved. By the time a team requests budget for a tool, they've been using the free tier for months and are already dependent on it. Forrester's research on product-led growth notes that PLG adoption patterns are intentionally designed to establish workflow dependency before IT or procurement visibility — a dynamic that accelerates sprawl in the absence of a parallel governance process. The SaaS buying decision tree is the pre-approval framework that inserts a structured review before any purchase — even small ones — rather than trying to claw it back post-adoption.

Team-level buying authority. Mid-market companies often have informal buying authority at the team level for purchases under a certain threshold: $1,000/month, $5,000/year. This is operationally sensible but creates fragmented visibility at the portfolio level.

The absence of a SaaS owner. Enterprise companies have IT asset management teams. Small companies have founders who know every tool. Mid-market companies often have neither: no dedicated owner for the SaaS portfolio and no visibility into the aggregate cost and overlap.

The Two-Track Remediation Approach

Fixing sprawl requires two parallel tracks: an immediate remediation to clean the current stack, and a structural fix to prevent the same outcome in eighteen months.

Running only the first track is the most common mistake. Companies do a great consolidation audit, cut $80K in waste, and then watch the stack grow back to the same size within two years because nothing about the buying process changed. For the governance structure that closes this loop, procurement vs operations ownership defines who should hold approval authority at each spend tier and how to enforce it without slowing down teams.

Track 1: Immediate Remediation

Step 1: Full Stack Discovery (Weeks 1-2)

Use the discovery sources covered in SaaS Consolidation: When to Cut a Tool vs. Keep It: AP records, corporate card statements, SSO logs, cloud marketplace billing, and a direct employee survey.

The employee survey is not optional. "What tools do you use that IT doesn't know about?" will surface the shadow IT layer. Anonymous surveys get more honest responses. Phrase it without judgment. You're building a picture, not auditing individuals.

SaaS Discovery Audit Template:

For each tool discovered, document:

Field Notes
Tool name and vendor Primary identification
Monthly/annual cost From finance records
How discovered AP, card statement, SSO, survey
Primary user or team Best guess from financial records
Contract status Known / unknown. If known, is there a renewal date?
Auto-renewal risk Is this in danger of renewing before the audit completes?

The auto-renewal risk column is critical. Any tool renewing in the next sixty days needs immediate action: either a conscious decision to keep it or a notice of cancellation submitted before the window closes. The SaaS contract red flags guide explains the auto-renewal notice window patterns to look for and how to calendar them proactively.

Step 2: Usage Audit (Week 3)

For every tool in the discovery list, pull three pieces of data:

  1. Active user count in the past thirty days
  2. Total contracted seats
  3. Primary use case (from the owner or user base)

You won't be able to get this from every tool, especially tools you didn't know existed. For unknown tools, the usage audit is: find who owns it, ask what it's for, and determine if it's being used.

Shadow IT Identification Checklist:

  • Employee survey completed and responses collected
  • SSO/IdP logs reviewed for connected apps
  • Corporate card statement reviewed (all cardholders)
  • AP records reviewed for recurring software charges
  • AWS/Azure/GCP marketplace reviewed
  • IT help desk tickets reviewed for tool mentions
  • Email domain analysis run (SaaS trial signups)
  • Direct outreach to department heads: "what tools does your team pay for?"

Step 3: Consolidation Decision (Week 4)

With the full stack visible and usage data in hand, run the keep-or-cut process. The utilization scoring matrix from SaaS Consolidation is the decision framework for this step.

For the remediation context, prioritize:

  1. Easy wins first: Tools with no active users, departed owner, or no identifiable use case. Cancel these immediately.

  2. Duplicate pairs second: Map overlapping tools in the same category. Decide which one survives, migrate data and users, cancel the other.

  3. Under-utilized tools third: Tools with active users but low utilization relative to cost. Decide whether the use case can be absorbed into a kept tool, or whether utilization can be improved enough to justify the cost.

Track 2: Structural Fix (Governance)

The Buying Governance Policy (1-page template)

The buying governance policy defines who can buy what, under what process, and with whose approval. It doesn't need to be complicated. A complicated policy that nobody follows is worse than a simple policy that sticks.

SaaS Buying Governance Policy — [Company Name]
Effective: [Date]

Scope: Applies to all software subscriptions, including SaaS tools, 
cloud services, and any recurring software cost.

Authority levels:
- Under $500/year: Team lead can approve, must register with IT
- $500-$5,000/year: Department head approval, IT registration required
- $5,000-$25,000/year: COO or CFO approval, diligence checklist required
- Over $25,000/year: Executive team approval, full diligence and legal review

Registration requirement:
All approved tools must be registered in the SaaS registry within 5 business days.
IT assigns an owner and renewal calendar alert for all registered tools.

Renewal process:
All renewals over $5,000 require 90-day advance review by the tool owner 
and IT before the renewal notice window closes.

Shadow IT:
Tools used without following this process must be registered retroactively 
or decommissioned. No exception for tools "already in use."

The Annual Review Cadence

Schedule a SaaS portfolio review once a year, ideally ninety days before the most common renewal cluster (many companies renew in Q4). The review covers:

  • Full stack audit update (additions since last review)
  • Utilization review for all tools above $5K/year
  • Overlap check across the stack
  • Renewal preview for upcoming twelve months
  • Consolidation candidates for the coming year

This review is a one-day exercise, not a six-week project, if you've kept the registry current throughout the year.

10 Diagnostic Questions for Self-Assessment

If you're not sure whether your company has a sprawl problem, these questions surface it:

  1. Can you name every SaaS tool your company pays for right now? Could your CFO?
  2. When did you last see a consolidated list of all SaaS subscriptions with costs?
  3. Do you have any tools provisioned for employees who've left in the past six months?
  4. Are there tools that multiple teams are paying for separately that do similar things?
  5. Has a contract ever auto-renewed because no one knew the notice window was approaching?
  6. How does a team member buy a new SaaS tool today? What's the actual process?
  7. Who owns the relationship with your top ten SaaS vendors? Is that in writing?
  8. Do you know the renewal dates for your top twenty contracts?
  9. Has IT ever discovered a tool by being asked to support something they didn't know existed?
  10. Has your SaaS spend grown faster than headcount in the past two years?

If you answered "no" or "I don't know" to five or more of these, the sprawl problem is likely significant.

Scoring guide:

  • 0-2 "no/don't know" answers: Governance is in reasonable shape; do a light audit to confirm
  • 3-4 "no/don't know" answers: Governance gaps exist; an audit will likely surface meaningful waste
  • 5+ "no/don't know" answers: Significant sprawl likely; run a full audit with the remediation approach above

What Success Looks Like

At six months post-remediation:

  • Tool count has decreased by 25-40%
  • SaaS spend has decreased by 20-35%
  • Every active tool has a named owner and a renewal date in the calendar
  • Shadow IT incidents have dropped (you're catching new tools in the approval process, not six months later)
  • The annual review cadence is on the calendar

At twelve months:

  • Second annual review runs in half the time of the first (the registry is current)
  • No renewal surprises in the past year
  • SaaS spend as a percentage of revenue is trending in the right direction
  • The team understands the buying process and follows it

SaaS sprawl is a governance failure. You can clean the stack once and feel the savings. But if the buying process doesn't change, the stack grows back. Deloitte's research on technology governance consistently identifies lack of a formal SaaS ownership structure as the primary cause of spend reversion after consolidation — companies that saved $100K in a one-time audit and then watched spend return to prior levels within 24 months. The structural fix is what makes the one-time savings permanent.

Learn More