SaaS sprawl is the slow pile-up of software tools, accounts and subscriptions that nobody decided on as a whole. Each one arrived for a good reason: a free trial, a team's favorite tool, one project's purchase. It stays after the reason has gone, and the cost shows up as wasted seats, accounts nobody owns, and offboarding that takes an afternoon.
You can't stop people finding useful tools, and you shouldn't try. You can know what you have, cut the duplicates, and make new tools come in through one door. This post shows how sprawl builds up, what it costs, and how to get it back under control. It's part of our guide to SaaS management for small businesses.
How sprawl happens
Nobody chooses a hundred tools. The count is just arithmetic. Take an imaginary 15-person company and count the ways a tool gets in:
| Where tools come from | How they arrive | Count in this example |
|---|---|---|
| Company-wide tools | Email, chat, video, docs, storage, password manager | 12 |
| Team tools, 4 teams | Each team picks its own tracker, CRM, design or dev kit | 28 |
| Individual sign-ups | Trials, AI tools, extensions, one-off converters | 45 |
| Leftovers | Tools from an old project or a previous team lead | 15 |
| Total | 100 |
Those numbers are made up to show the mechanism, not taken from a survey. Your mix will differ. What carries over is how each row grows.
Signing up is free and instant. Anyone with a work email can start a trial and invite colleagues, with no purchase order and no IT ticket. "Sign in with Google" removes the last bit of friction: one click, and the tool now has an account tied to your company's domain.
Free plans turn paid quietly. A tool goes on someone's company card when the trial ends, or when the team hits a free-plan limit. From then on it renews without anyone deciding again.
Nobody removes anything. Adding a tool solves a problem today. Removing one solves a problem nobody is looking at.
People leave, tools stay. The person who chose a tool moves on, and with them goes the knowledge of why it exists and who's in it.
How many SaaS tools does a small business use? We haven't found a reliable public count for a company of 5 to 50 people, so we won't quote one. Your own inventory is the only number that matters anyway.
What it costs
Sprawl costs in three currencies.
Money. Seats for people who left or never log in. Two tools doing one job. A plan upgraded for one feature. A small example at list price: Notion's pricing page lists its Plus plan at $10 per seat a month billed yearly, as we read it on 27 October 2026. If a 15-person company pays for Notion Plus for everyone while two teams keep their notes somewhere else, those seats are $1,800 a year for a wiki half the company doesn't open. SaaS spend goes through where the money leaks.
Risk. Every tool is a place company data lives and a place a former employee might still have an account. Tools nobody knows about don't get MFA turned on, don't get reviewed, and don't get a step in the offboarding checklist. That last bit is how orphaned accounts happen: logins that belong to nobody still at the company.
Time. Each tool is one more admin page to open when someone joins or leaves. At ten tools, offboarding is ten minutes. At sixty, it's an afternoon of guessing, and something gets missed.
Doesn't SSO fix sprawl?
Not on its own. Single sign-on puts one login in front of the tools connected to it, which helps with the risk column: suspend someone in your identity provider and they can't sign in to those tools through it. But the tools that sprawl are mostly the ones nobody connected. A trial someone started with a password never sees your SSO. And the tools you could connect usually charge for the privilege, with SSO on a higher plan per seat; SSO for small business works through whether that is worth it at your size.
SSO also leaves the accounts in place. The seat keeps billing until someone removes it, which is a deprovisioning job, not a login job. Sprawl is a counting problem first: what you have, who is in it, and what it costs. Login is one column in that list.
Taking a SaaS inventory
You can't consolidate what you can't see. Build a SaaS inventory, one row per tool, from four sources.
Start with card and bank statements, twelve months back, so annual renewals show up. Every recurring charge is a tool. Then open your Google Workspace or Microsoft 365 admin console. Apps people have connected with their work accounts, including "Sign in with Google" apps, are listed there. Then search email for "welcome to", "your invoice", "trial ends" and "invited you to". Finally, ask each team for the tools they use that aren't on your list, and make it clear nobody is in trouble.
For each tool, record the owner, what it's for, the plan, monthly cost, renewal date, seats paid, how people log in, and whether it holds customer data. The SaaS management guide has a ready-made sheet with these columns.
Expect surprises. Free tools with dozens of company accounts. A paid tool whose owner left a year ago. Shadow IT, the tools bought or used without anyone in charge knowing, is the bulk of most first inventories; the post on finding shadow IT covers the discovery sources in detail.
Keep the inventory alive. An inventory is accurate the day you finish it and wrong a month later. Give it one owner, put the renewal dates in a shared calendar, and add a row the same day anyone puts a new tool on a card. The "whether it holds customer data" column is the one to keep honest, because it decides which tools need MFA, an admin review and a line in offboarding.
Consolidating
With the list in front of you, group tools by the job they do. Then work through each job.
Pick one tool per job, by default. One video tool, one wiki, one project tracker. Exceptions need a reason, such as engineering's issue tracker being different from sales' task list.
Keep the one most people already use, unless it fails a requirement. Migration is the real cost of consolidating, and moving the fewest people is usually cheapest.
Check renewal dates before deciding. Cancelling an annual plan two weeks before it renews saves a year. Cancelling it the day after saves nothing until next year.
Export the data before cancelling. Then remove every account, so nobody keeps working in a tool you no longer pay for, or worse, one you still do.
Cancel free tools too. They don't cost money, but they hold company data and accounts.
Don't aim for the smallest possible list. Aim for a list where every tool has an owner and a reason.
A worked consolidation
Say the inventory shows three note-taking tools: a paid wiki for everyone, a free notes app used by design, and a second paid tool that sales bought for meeting notes. The wiki has the most users, so it stays by default. Design's free app holds two years of research notes, so the team exports them, imports what matters into the wiki, and then each design account in the free app is deleted. Sales' tool renews in five months on an annual plan; they keep it until a month before renewal, move their templates, and cancel before the date. The result is one tool, one owner, and two fewer places a leaver can keep access.
Common mistakes
Cancelling the subscription but not the accounts. Many tools fall back to a free plan instead of disappearing, with every account and every document still there.
Consolidating onto the tool with the best demo. The tool most people already use costs least to keep. Switching everyone has a price that never shows on an invoice.
Treating sprawl as a one-off project. The first clean-up feels great. Without a rule for how new tools arrive, the count creeps back within a year.
Banning sign-ups. People will use tools anyway, just on personal accounts you can't see. A fast way to say yes beats a slow way to say no.
Keeping it in check
Consolidation is a one-off. Sprawl comes back unless something changes in how tools arrive.
Give new tools one door. Anyone can suggest a tool. It goes on the inventory, with an owner, before it goes on a card.
Give every tool an owner. The owner approves seats, reviews who has access, and decides at renewal.
Give each role a starter set. Write down which tools a new salesperson, engineer or designer gets on day one. New hires then arrive with the right tools instead of copying whatever their predecessor had, and anything outside the set is a deliberate request. Role-based access control shows how to define the sets without overthinking them.
Make offboarding cover every tool on the list, not just email. The employee offboarding checklist has the steps.
Take a quarterly look. Fifteen minutes per quarter: new charges on the card statement, renewals coming up, seats paid against seats used. A software license audit turns that into a one-day routine the first time, and an hour after that.
Where SmashSSO fits
SmashSSO handles the access side of sprawl. Once you add your tools to it, from its catalog or by hand, it reads each tool's members and roles, matches them by email against your Google Workspace directory, and shows who has what in one grid. Accounts that match nobody in the directory are flagged, which is where former employees and stray contractors show up. From there you invite, change and remove people across tools by role.
It won't find tools for you: it doesn't read card statements, and it does no spend tracking, so the inventory and the money columns stay in your sheet. It needs Google Workspace as the directory. It costs a flat fee from $199 a month billed annually, however many tools you end up with (pricing).