
SaaS Sprawl: How to Find It, Cut It and Keep It Gone
SaaS sprawl is what happens when software subscriptions multiply faster than anyone tracks, approves or uses them. You fix it in four moves: find every tool you pay for, learn the job each one does, merge the overlaps, and give teams a fast, approved way to buy so the sprawl does not grow back. This guide walks through each move, with the numbers that show why it matters and the mistakes that make cleanups fail.
RaremindFind the Cost Behind SaaS SprawlRaremind’s Money Map helps identify lost revenue, excessive costs and process inefficiencies, with independent advice that does not push unnecessary technology.Explore Raremind’s approach
TL;DR
SaaS sprawl is first a visibility problem and only second a cost problem. You cannot cut what you cannot see.
Check credit card statements, expense reports and single sign-on logs, not just IT purchase records. Spend is often well above what leadership believes.
Cancelling tools without understanding the job they do just pushes people toward new unapproved ones.
Unmanaged apps are also a security and offboarding risk, especially OAuth “Connect with Google” grants.
Start with how your business makes money, then decide which tools earn their place.
Table of Contents
What SaaS sprawl actually looks like
Why it costs more than the invoices
How to reduce SaaS sprawl in five steps
Mistakes that make cleanups fail
A worked example
Our perspective: start with the money, not the stack
Where outside help pays off
How Raremind can help
Sources
What SaaS sprawl actually looks like
Nobody plans it. A sales manager signs up for a proposal tool on a company card. Marketing starts a free trial that quietly converts to paid. Finance adds a second expense app because the first one lacked one feature. Each purchase is reasonable on its own. Together they become a pile of overlapping subscriptions that nobody owns.
The pattern is common enough to have numbers. One LastPass analysis describes sprawl as adopting a growing number of SaaS applications without formal approval and oversight, often with no centralized procurement process. The same piece reports that organizations use well over a hundred apps while IT is aware of only about a third of them, and that an estimated 52.7% of licenses go unused or underused.
For a small or mid-sized company, the symptoms are easy to recognize:
Two or three tools that do roughly the same thing, such as project boards, e-signature or form builders.
Invoices on company cards that nobody can explain.
Seats still billed for people who left months ago.
Data scattered across apps, so reports never match.
A new hire who needs eleven logins on day one.
Sprawl is not a sign of a careless team. Cloud software is sold to be easy to start and easy to forget. The low entry price and monthly billing are the very features that let subscriptions slip under the radar.
Why it costs more than the invoices
The subscription line is the visible part. The larger costs sit around it.
Wasted licenses and duplicate tools
The LastPass analysis puts average SaaS spend at about $4,830 per employee per year. Even if your own figure is a fraction of that, a license bought and never used is money gone every month. Duplicate tools also split your team’s attention, because people follow different workflows depending on which app they happen to prefer.
Hidden spend
If you only count what procurement or IT approved, you undercount. A write-up by an IT services firm in Australia reports that audits often find operational spend 30% to 80% higher than leadership expected. That is one practitioner’s observation from its own client work, not a universal rule, but it matches what many owners find the first time they read twelve months of card statements line by line.
Security and offboarding gaps
Every unmanaged app is a place where company data lives without anyone watching it. The same LastPass piece cites estimates that shadow IT can account for close to 38% of IT spend in some organizations, and that breaches involving it take longer to identify and contain. The figures come from broad industry estimates, so treat them as direction, not as a forecast for your business.
The practical issue is simpler. When someone leaves, you can only revoke access to the systems you know about. As one governance FAQ puts it, governance only works on systems you can see, so reviews and deprovisioning can miss real access paths.
One risk is easy to overlook: OAuth grants. Each time someone clicks “Connect with Google” or “Sign in with Microsoft” to try a new tool, they may be granting that app standing access to company data. Those grants pile up for years. Federal guidance on identity management, such as the CISA reference architecture for identity, credential and access management, treats access control as the foundation here, which is why a simple list of apps is not enough. You also need to know which apps hold access to your accounts.

Slower work
The cost that rarely shows up on a spreadsheet is friction. Handoffs between tools that do not talk to each other, manual copy and paste, and inconsistent data all slow the people who bring in revenue. This is the real reason we treat sprawl as an operations problem, not an IT housekeeping chore.
How to reduce SaaS sprawl in five steps
The approach below works for a company of 15 people or 500. The scale changes; the sequence does not.
Step 1: Build a complete inventory
Start wider than you think you need to. Procurement records catch only the tools someone formally approved. Layer several sources:
Card and bank statements for the last 12 months, including personal cards that employees expense.
Expense reports, where tools hide in reimbursements.
Single sign-on and identity provider logs, which show which apps people authenticate into.
OAuth consent lists in your Google Workspace or Microsoft 365 admin console.
Short conversations with team leads. People will usually tell you what they use if they trust you are there to help them keep a working tool, not to take it away. Sigma’s guide to reducing sprawl makes the same point: no single discovery method catches everything, so layer them.
For each tool, record the name, owner, department, monthly or annual cost, renewal date, number of paid seats, number of active users and the data it holds.
Step 2: Find out what job each tool does
This is the step most cleanups skip, and it is why they fail. Before you decide whether to keep a tool, write down the job it does for the person who chose it. “Gets proposals signed in one day” is a job. “We use Tool X” is not.
Sigma’s guide recommends cataloging the need behind each tool before consolidating. The reason is practical. If you simply cancel an app, the people who relied on it will find another one to do the same job, and you are back where you started with a new unapproved tool.
Step 3: Tie each tool to revenue or cost
Here we depart from the usual advice. Most guides tell you to rank tools by usage. Usage matters, but a tool that three people use daily to send invoices may be worth more than a dashboard fifty people open once a month.
Ask of each tool:
Does it help win, deliver or collect on a sale?
Does it reduce a cost that is larger than the tool’s price?
Is it required for compliance?
If it disappeared next week, what would break and how fast?
Tools that answer “nothing” to all four are your first cancellations. Tools that sit close to revenue deserve protection, and often better integration.
Step 4: Consolidate in order of impact
Work through the list in this order:
Priority | What to look for | Typical action |
|---|---|---|
1 | Unused seats and ex-employee accounts | Remove seats at the next renewal, or sooner if the contract allows |
2 | Exact duplicates (two tools, same job, same team) | Pick one, migrate, cancel the other |
3 | Partial overlaps (features of one tool covered by a bigger platform you already pay for) | Move the workflow, then cancel |
4 | Tools with no owner | Assign an owner or cancel |
5 | Annual contracts renewing soon | Calendar every renewal 60 to 90 days ahead |
Retire tools in phases, not all at once. Give each team a migration date, export their data first, and keep the old tool read-only for a short period in case something was missed.
Step 5: Make the right path the easy path
Sprawl returns when buying approved software is slower than buying unapproved software. Gartner analysts advise against pursuing sprawl reduction at the expense of business agility, and favor governance with a fast, governed route to acquiring tools that serve a business outcome, rather than a culture that just says no.
A workable version for a small company is light:
One named person approves new software, and answers within two business days.
A one-paragraph request: what job, which team, expected cost, what data it will touch.
A check against the existing inventory before anything is bought.
A rule that every tool has an owner and a renewal date on a shared calendar.
Offboarding that includes a review of app access, not only email and laptop.
Mistakes that make cleanups fail
Treating it as an IT project. If the people who chose the tools are not part of the decision, the tools come back under new names.
Cutting by price alone. The cheapest subscriptions are often the ones nobody notices, while a single expensive platform may be doing real work. Look at value, not just cost.
Counting only apps, not access. Governance paperwork can look complete while real access paths remain unmanaged, particularly when onboarding and offboarding are done by hand. Check OAuth grants and service accounts alongside the app list.
Consolidating onto one giant tool by default. Fewer tools is not automatically better. A bundle that does ten jobs poorly can cost more in lost time than three focused tools cost in fees.
Doing it once. An inventory goes stale in a quarter. Put a review on the calendar, twice a year for most small companies.

A worked example
To show how the math tends to go, here is an illustration, not a client case. Imagine a 40-person company that thinks it pays for 35 tools. A twelve-month card review turns up 52. Of those:
9 have no active users in the last 90 days.
6 pairs overlap in function, for example two e-signature tools and two project boards.
11 are billed for more seats than people who log in.
The team cancels the nine idle tools, merges the six pairs into six, and trims seats on the rest. The list falls from 52 to 37, and the company now has a named owner and renewal date for each. Nothing dramatic happened to the work itself. People kept the tools they needed, and the leftover spend simply disappeared. That outcome is typical of what a careful inventory can do, though your numbers will differ.
Our perspective: start with the money, not the stack
Most advice about this topic begins with the software. Pull a list of apps, rank them, cut the bottom. We think that starts at the wrong end.
At Raremind we begin by looking at how a business makes money, and where it loses it. Our Money Map lays out the path from a lead to a paid invoice and marks the places where revenue leaks, costs pile up or work gets repeated. Only then do we ask which tools support that path. A subscription that sits on the path and removes manual work is an asset. A subscription that sits off the path is a candidate for cancellation, however popular it is internally.
We also have a structural reason to say this plainly: we do not sell software and we take no vendor commissions. When we recommend dropping a tool, merging two, or not buying a new one, nobody pays us for the opposite answer. For owners who have been pitched a new platform every month, that independence is often what makes the advice usable.
One more view we hold firmly: the goal is not the smallest possible stack. It is a stack your team will actually use, that costs less than the problems it solves, and that you can describe on one page. If cutting a tool makes people slower, the cleanup has cost you money, not saved it.
— Mirko
Where outside help pays off
Many owners can run steps 1 to 3 themselves with a spreadsheet and a free afternoon, and you should if your stack is small. Help becomes worthwhile when:
Nobody has the time to chase down every subscription and owner.
The tools are tangled into workflows that touch sales, billing or customer delivery.
You are weighing automation or AI tools and want to avoid adding another layer on top of an untidy base.
You want a neutral second opinion that is not tied to a vendor.
If you are considering AI tools, our guide to an AI readiness assessment shows how to map revenue workflows before buying anything. If your concern is overall spend, our list of cost reduction strategies for small businesses puts operations first and software second.
How Raremind can help
Our plan, Your Digital & AI Office, is a flat €995 per month. It gives you ongoing, independent advice on your operations, including mapping current workflows with the Money Map, assessing vendor and tool consolidation, and advising on automation and AI. For larger, hands-on initiatives we scope fixed-fee projects separately. Because we sell no software, the recommendation on your stack is based only on what suits your business.
FAQ
What is SaaS sprawl in simple terms?
It is the uncontrolled growth of software subscriptions inside a company. Teams buy tools on their own, many overlap, and nobody has a full picture of what is paid for, who uses it or what data it holds. The result is wasted spend, scattered data and security blind spots.
How do I manage SaaS sprawl without slowing my team down?
Give people a fast approval path instead of a blanket ban. One accountable approver, a short request form and an inventory check are enough for most small companies. Gartner’s analysts recommend governed speed over a culture of refusal, since refusal tends to push purchases out of sight.
How often should we review our software subscriptions?
For most small and mid-sized businesses, twice a year is a sensible rhythm, plus a check 60 to 90 days before any annual renewal. Also review app access every time someone leaves, so their accounts and OAuth grants do not linger.
Is the answer to put everything on one platform?
Not automatically. Consolidation helps when overlapping tools do the same job, but a single large platform can be slower or more expensive for specific tasks. Decide by the job each tool does and its link to revenue, then merge where it makes sense.
Sources
Visibility and the SaaS Sprawl Problem: How Did We Get Here? (LastPass)
SaaS Sprawl: What It Costs Australian SMBs and How to Control It (Epic IT)
Why do shadow IT and SaaS sprawl break access governance? (NHIMG)