A Reddit post went viral last week. A 4-person company discovered they were paying $180,000 annually for software. Not a typo. Four employees, 180 grand in SaaS subscriptions.
The thread exploded with 857 comments, mostly from people sharing their own horror stories. Turns out, tool sprawl isn't a big company problem. It's an everyone problem.
How a 4-Person Team Ends Up With $180K in Software
The breakdown from the original post was painful to read. Multiple project management tools because different team members preferred different platforms. Three separate analytics subscriptions that all did roughly the same thing. A CRM nobody used. Design tools, communication tools, documentation tools. Each one made sense when someone signed up for it. None of them made sense together.
This is how tool sprawl works. It's not one bad decision. It's dozens of reasonable-sounding decisions that compound into chaos.
Someone needs to manage tasks, so they grab Asana. Someone else prefers Notion, so now you have both. Marketing wants HubSpot. Sales wants Salesforce. Engineering wants Linear. Everyone gets their tool. Nobody gets a system.
The Real Cost Isn't the Subscription Fee
The $180K number is bad enough. But the subscription cost is actually the smallest part of the problem.
Context switching. Every time someone moves between tools, there's a cognitive tax. Studies suggest it takes 23 minutes to fully refocus after switching contexts. If your team is bouncing between Slack, email, Asana, Notion, and three other platforms throughout the day, you're not paying for productivity software. You're paying to destroy productivity.
Data fragmentation. Customer information lives in the CRM. Project status lives in the PM tool. Conversations live in Slack. Documents live in Google Drive. Or Notion. Or both. When you need a complete picture of anything, you're hunting across six platforms to assemble it.
Onboarding hell. Every new hire needs accounts on every platform. They need to learn the quirks of each tool. They need to figure out which tool is the "real" source of truth (spoiler: nobody agrees). A process that should take days takes weeks.
Security surface area. Every tool is another potential breach point. Another set of credentials to manage. Another vendor with access to your data. Another integration that might have vulnerabilities you'll never audit.
The Five Patterns That Create Tool Sprawl
After auditing dozens of small business tech stacks, we've seen the same patterns repeatedly:
1. The "Free Trial That Stuck" pattern. Someone signs up for a free trial. It works well enough. The trial converts to paid. A year later, nobody remembers why you have it, but the charge keeps hitting the card.
2. The "New Hire Brought Their Favorite" pattern. Every new employee has tools they swear by from previous jobs. Instead of adapting to existing systems, they bring their own. Now you have three project management tools because three people have three preferences.
3. The "We Needed It For One Project" pattern. A specific client or project required a specific tool. The project ended. The subscription didn't.
4. The "This Solves Everything" pattern. Someone finds a tool that promises to replace five others. You add it to the stack. But nobody actually migrates off the old tools. Now you have six tools instead of five.
5. The "Nobody Owns This Decision" pattern. Without a clear owner for the tech stack, anyone can add tools but nobody removes them. Entropy wins.
The Audit Process: How to Fix It
Here's the framework we use with clients who are drowning in subscriptions:
Step 1: Inventory everything. Pull credit card statements, check with accounting, search email for subscription confirmations. You will find tools you forgot existed. One client discovered they'd been paying for a social media scheduler for two years after switching to a different one.
Step 2: Map actual usage. For each tool, answer: Who uses this? How often? What for? Be honest. "We use it for everything" usually means "We use it for one specific thing and could probably do that elsewhere."
Step 3: Identify overlap. How many tools do project management? How many handle communication? How many store documents? List every tool by function and you'll see the redundancy clearly.
Step 4: Pick winners. For each function, choose one tool. The best tool isn't always the most powerful. It's the one your team will actually use consistently. Adoption beats features.
Step 5: Execute the cut. This is where most audits fail. Knowing what to cut is easy. Actually canceling subscriptions and migrating workflows is hard. Set a deadline. Assign an owner. Make it happen.
What a Healthy Stack Looks Like
For a small team (under 10 people), you probably need six tools, not sixty:
- Communication: One platform. Slack or Teams, not both.
- Project/Task Management: One platform. Pick based on how your team actually works.
- Documents: One platform. Google Workspace or Notion, not a mix.
- CRM: One platform. Even a spreadsheet beats three half-used CRMs.
- Accounting: One platform. QuickBooks, Xero, whatever. Just one.
- Industry-Specific: Whatever your actual work requires.
That's it. Everything else is probably costing you more than it's worth.
Warning Signs You Have a Problem
If any of these sound familiar, you're probably due for an audit:
- You can't list all your software subscriptions from memory
- New hires ask "which tool do we use for X?" and get different answers
- You have multiple tools that do the same thing "for different use cases"
- Your monthly software spend surprises you when you actually add it up
- Important information is "somewhere" but nobody can find it quickly
The Bottom Line
That Reddit post resonated because it's not an outlier. It's an extreme version of what's happening at most companies. The $180K number is shocking, but plenty of 10-person teams are quietly spending $50K on tools they barely use.
The fix isn't complicated. Inventory, evaluate, consolidate, execute. The hard part is actually doing it instead of adding another tool to your stack.
Tuscan Agency helps small businesses audit and optimize their tech stacks. If you're not sure what you're paying for or whether it's worth it, let's talk.

