The SaaS Sprawl Audit: A Simple Way to See What You're Really Paying For

Every software subscription an organisation has ever bought made sense on the day it was bought - somebody had a problem, found a tool, and got the green light. Multiply that by years of teams, projects, and individual decisions, and you end up with something nobody designed on purpose: a sprawling, overlapping, half-forgotten technology estate that quietly drains budget every month. We saw this clearly during a recent tech landscape assessment we ran in partnership with a sports and entertainment organisation, and it's a picture that will feel familiar to almost any mid-sized organisation that has grown organically over the past decade.

What the numbers revealed

The assessment identified over 70 distinct technology providers, representing roughly $460,000 in annual spend. Around 75% of that sat with a handful of core, well-understood vendors. The remaining 25% was spread across a long tail of smaller subscriptions - tools bought for a specific project or moment, then simply left to renew. That long tail is where clear, category-level duplication showed up: five-plus overlapping storage and file-sharing tools, multiple overlapping CRM platforms, and several overlapping content and media tools, each adopted by a different team without knowing the others existed.

The deeper issue was ownership: for many smaller tools, nobody had a clean, current answer to "whose responsibility is this renewal?" That gap meant simple questions - is this still used? is it duplicated elsewhere? - were never asked.

Why this matters, and how to fix it

The obvious win here is cost savings. The bigger one is risk and visibility. An organisation that can't say with confidence which tools are active, how deeply they're integrated into company data and systems, who's using them, and whether they overlap can't accurately assess its exposure to vendor changes. Nor can it make informed consolidation decisions. The $460K is the visible cost; the risk underneath it is the invisible one.

A one-off audit - mapping every tool, cost, owner, and usage level - is a quick and necessary first step. But it doesn't fix the conditions that created the sprawl, so without structural change, it will simply regrow. The recommendation here was a Tech Investment Board: a small, standing group owning periodic portfolio reviews, approving new purchases against the existing stack to catch duplication early, and tracking usage so "is this still being used?" always has a ready answer.

Conclusion

Tech debt isn't always a legacy codebase. Sometimes it's a stack of forgotten subscriptions, each small, collectively worth hundreds of thousands a year, renewing quietly because no one was positioned to ask the obvious questions. The diagnostic step is simple and fast; the higher-leverage step is building the governance that makes asking those questions routine.

Key takeaways

• Sprawl is rarely the result of bad decisions - it's an emergent effect of growth without a central view.
• The biggest hidden cost often sits in the group of smaller, half-forgotten subscriptions, not the big vendors.
• Unclear ownership is usually what lets renewals go unchecked.
• A one-off audit creates clarity; only standing governance, like a Tech Investment Board, keeps it accurate over time.

If your software estate has grown through years of individually sensible decisions, there's a good chance it looks more like this than you'd expect. Get in touch for an independent technology assessment to develop a governance framework that works for you.