Automation & AI, Web

SaaS sprawl: Why the tool count keeps growing even after you cut it

By Published On: September 23, 20265.2 min read

SaaS sprawl keeps coming back because cutting subscriptions treats the symptom

SaaS sprawl is what happens when every team solves its own problem with its own tool, and nobody is ever assigned to notice the overlap. MediaCutlet’s Ripcord traces sprawl back to why each tool got bought in the first place, because the software rarely caused the problem. It usually got purchased to cover for one, and the tool stays long after the original problem has changed shape.

Most SaaS sprawl conversations start and end with a spending review. Zylo’s research puts the average company’s SaaS portfolio in the hundreds of applications, with a large share of licenses sitting unused, and the waste keeps recurring even at organizations that ran a cleanup the year before. Cutting a list of tools once does not fix whatever kept generating new ones, which is why so many companies find themselves running the same exercise on a two-year cycle.

MediaCutlet is four senior operators who embed with leadership teams, so the person tracing the sprawl back to its cause is the person who fixes it. No account managers, no junior handoffs, no subcontracted outcomes. We measure the work in dollars rather than impressions on the results page: more than $500 million in client revenue runs through operations we have touched, on budgets that do not have room for software nobody opens. Every dollar recovered from an unused license is a dollar that can fund something the business actually needs.

MediaCutlet works out of Red Bank, New Jersey, with clients nationally, and Strato Doumanis leads the digital, AI and automation practice. A typical Ripcord engagement runs $100,000 and returns more than $500,000 over three years, and retired software is usually enough on its own to cover a meaningful share of that cost before the automation work even starts paying back.

Why does SaaS sprawl happen even at well-run companies?

Because buying software is easy and nobody owns un-buying it. A team hits a problem, finds a tool, expenses it and solves the immediate pain. Multiply that by every team, every quarter, for years, and the portfolio grows even when the company is being run well by every other measure. No single purchase looks unreasonable in the moment, which is exactly why the pattern is so hard to catch.

What does SaaS sprawl actually cost beyond the subscription price?

The license fee is the visible part. The larger cost is the time spent logging into six places to answer one question, the duplicate data that drifts out of sync between overlapping tools and the security exposure of nobody knowing exactly what has access to what. None of that shows up on the invoice, which is precisely why it gets ignored for so long. By the time it surfaces, it usually shows up as a customer complaint rather than a line item anyone can point to.

Is cutting subscriptions the same as fixing sprawl?

No. Cutting subscriptions removes cost for a quarter or two. Fixing sprawl means understanding why each tool got added and closing the gap it was covering for, usually a manual process or a system that never got connected. Skip that step and the tool count creeps back within a year, often carrying a higher price tag the second time around.

How do you know if your stack has outgrown itself?

The clearest signal is an argument nobody can settle: two systems disagree on a number, and someone has to reconcile it by hand before anyone trusts a report. If that happens more than once a month, the stack has already outgrown what any one person can hold in their head, and the fix stops being a spreadsheet problem. At that point the reconciliation itself has quietly become someone’s part-time job.

Signs SaaS sprawl has become an operating cost, not just a budget line

  • Two systems give different numbers for the same thing
  • Nobody can name every tool a given department pays for
  • The same task gets done differently by different teams
  • A new hire needs a week just to get access to everything
  • Renewals get auto-approved because nobody has time to review them

MediaCutlet’s Ripcord Audit maps the manual work behind the sprawl before recommending what to cut, connect or keep, so consolidation actually holds instead of drifting back within a year. The map usually surfaces redundant subscriptions worth enough on their own to offset a meaningful share of the engagement.

Bring your software renewal list. Contact MediaCutlet to see what’s actually driving it before the next round of renewals locks in.

Frequently asked questions

How many software subscriptions counts as “too many”?

There is no universal number. The better question is whether anyone can name what every tool is for and who still uses it. If the answer is no, the count already matters less than the visibility problem underneath it.

Will consolidating our stack disrupt our team’s workflows?

It can, briefly, which is why sequencing matters. A good consolidation plan replaces a tool only once its replacement is running, rather than cutting first and figuring out the gap afterward.

Can AI tools make SaaS sprawl worse?

Often, yes, in the short term. New AI features and AI-native apps are one of the fastest-growing categories of new subscriptions, and they get added with even less oversight than traditional software usually does.

Do we need a dedicated SaaS management platform to fix this?

Not necessarily. A management platform helps track what already exists, but it does not fix the underlying reason new tools keep getting added faster than old ones get retired.

What if a team pushes back on losing a tool they like?

That resistance is usually a sign the tool is covering for a real gap, not that the team is being difficult. Understanding what the tool is actually being used for is part of the assessment, not an obstacle to it, and it often points straight at the manual process worth fixing.

How fast does sprawl come back after a cleanup?

Within a year in most organizations that only cut and did not address why tools kept getting added. Sprawl that gets traced to its cause and closed at the source tends to stay fixed, because the gap the old tools were covering for no longer exists.

About the Author: Griffin Whitmer

Think your stack is working harder than your team should?

Start with a conversation. We will tell you straight whether there is something worth fixing.

Keep Reading

More from MediaCutlet

  • AI implementation services team connecting an AI model to existing business systems and data

    AI Visibility, Automation & AI, SEO

    AI implementation services: from pilot to everyday use

  • SEO services NJ dashboard tracking local rankings, calls and leads for a New Jersey business

    AI Visibility, Automation & AI, SEO, Web

    SEO services NJ: What New Jersey businesses should expect

  • Brand visibility in AI search report comparing how often AI assistants name a brand against competitors

    AI Visibility, Automation & AI, SEO, Web

    Brand visibility in AI search: Why being named beats a click