When SaaS stops scaling: 7 signs you've outgrown your stack.
The pattern is rarely a single failure. It's accumulation — small frictions that compound until you're paying the cost of misfit software without seeing it on any line item.
SaaS doesn't "break." It accumulates friction. Two or three of these signs on their own aren't a problem. Five or more means you're paying the cost of misfit software in time, headcount, and missed scale — and you don't see it on a line item.
1. Three SaaS tools doing the work of one
Each tool was bought to solve a specific gap. None of them quite fit on its own. Now there's a CRM, a separate quoting tool, a separate proposal generator, a separate signing tool, and a separate revenue tracker — and the deal goes through all five with a human copying data between them.
What it costs: hours of manual copy-paste per deal, plus the inevitable "I copied the wrong number" errors that surface at the worst possible time.
What to do: map the entire workflow end-to-end before adding tool #6. Often the right next step is a thin integration layer (custom-built or via Zapier-style tooling) that orchestrates the existing tools — not another tool.
2. Spreadsheet sprawl alongside the SaaS
The "real" workflow lives in Excel or Google Sheets. The SaaS is a passthrough — partial information goes in, certain reports come out, but the actual operational truth is the spreadsheet.
This is the single most common sign that the SaaS doesn't fit how your team actually works.
What it costs: the spreadsheet is fragile (one wrong formula), unauditable (no history), and uncollaborative (locked to whoever owns the file). The SaaS becomes performative work.
What to do: identify what the spreadsheet does that the SaaS doesn't. Usually it's 2-3 specific things. Those 2-3 things are your custom-build candidates.
3. "It's on the roadmap" — for 18 months
You've raised the feature you need with the vendor. They acknowledged it. It's on the roadmap. Eighteen months later, it still isn't there. Two enterprise features you don't care about have shipped in the meantime.
SaaS roadmaps are built around the vendor's largest customers and revenue priorities. If you're not one of those, you're waiting forever.
What it costs: the gap doesn't go away. Your team builds workarounds. Workarounds become institutional knowledge that nobody documents.
What to do: stop waiting. Either build the feature yourself as an add-on layer, or factor "we will never get this" into your tool selection criteria.
4. Workflows shaped by the tool, not the team
You're training new hires on the SaaS's quirks instead of how your organisation actually operates. "Click this even though it doesn't apply, because the next step won't appear otherwise." "Skip step 3 — we use that field for something else."
What it costs: your differentiation slowly erodes. The way your team does things — which is often what makes you good at what you do — becomes a workaround on top of a generic tool.
What to do: name the differentiation. If your way of working is a real edge, it deserves software that supports it. If it isn't, simplify your processes to fit the tool.
5. Reporting requires manual aggregation
Every board meeting, every monthly review, every quarterly check-in starts the same way: someone exports CSVs from 3-5 tools, stitches them in Excel, and produces the "real" report.
The reports themselves are useful. The fact that you need a human to make them isn't.
What it costs: typically 1-3 days per month of someone senior's time, repeated indefinitely. Plus the reports are out of date the moment they're made.
What to do: reporting automation is one of the highest-ROI custom builds. A small layer that pulls from your existing SaaS and presents a live dashboard often pays for itself in months.
6. Per-seat pricing that punishes growth
Adding the 50th user costs the same per month as adding the 5th. You think twice about giving people access they should have. Or worse, you start sharing logins.
Per-seat pricing was rational when seats were rare. For modern SMBs where 80%+ of staff need access to the customer record, it becomes punitive.
What it costs: the obvious bill, plus the less-obvious cost of restricted access. Decisions get delayed because the right people don't have visibility.
What to do: for high-headcount, high-access scenarios, the maths flips. Custom (no per-seat) often becomes cheaper at scale, even before counting the operational benefits.
7. The SaaS owns your data
Exporting your data would be a project. Migrating it would be a nightmare. The switching cost shapes your decisions — you stay with the vendor because leaving is too painful, even when the product no longer fits.
This is the most insidious one because you don't feel it day-to-day. You feel it the day you decide you need to change vendors.
What it costs: negotiating power. The vendor knows you can't leave. Pricing only goes up.
What to do: at minimum, schedule a quarterly data export. At best, design new systems where you own the data structure and the SaaS is a presentation layer — not the other way around.
How many of these apply?
- 0–2: your SaaS stack is probably fine. Don't fix what isn't broken.
- 3–4: you have specific friction. Look at which tools are causing it. Sometimes the right move is one tool change, not custom.
- 5+: you're paying the misfit tax. The cost is real even if it doesn't show on a line item. Worth a structured look.
The cheapest way to figure out what to do: our no-cost Discovery Program. We spend 3–5 days inside your operation and tell you honestly which combination of "fix the SaaS / replace the SaaS / build custom" makes sense for you.