Every growing SME hits the same fork in the road: do we keep paying for the SaaS tool we've outgrown, or commission something bespoke that fits how we actually run?
It is rarely an obvious call. SaaS is fast to start and feels safe; bespoke feels expensive and risky right up until the day you realise you have been paying a per-seat tax for years to get 30% of what you needed.
This playbook is the framework we use to help SME owners decide honestly, one question at a time.
When SaaS is the right call
Buy SaaS, not bespoke, when all of these are true:
- Your workflow looks like everyone else's in your industry. You are not doing anything unusual; you are running a standard process at a standard scale.
- The tool is mature. People have been buying it for five years, the integrations exist, the bugs are fixed.
- Per-seat economics work for you. You can afford the licence cost at your current team size and the price doesn't make you wince when you add a person.
- You won't get a competitive moat from doing it differently. This is back-office, not your differentiator.
- The vendor's roadmap broadly aligns with yours. You don't fight the tool every week.
For accounting, generic CRM, payroll, email marketing, helpdesk basics, project management, SaaS is almost always the right answer. Buying time saved beats spending time building.
When SaaS quietly bleeds you
The case for bespoke is rarely a single big moment. It is a slow accumulation of three forces:
1. The per-seat tax compounds against your growth
SaaS pricing is designed so the bill grows when you grow. That is fine when you're small. It becomes painful when you have 25 people each paying £35/month for a CRM, £20/month for a project tool, £15/month for a knowledge base, £25/month for a dashboard tool, plus the integrations that connect them.
At a certain scale, usually somewhere between 15 and 50 people in operations-heavy roles, the annual SaaS bill for a specific tool starts to rival the one-off cost of building exactly what you need.
The difference is direction: SaaS bills go up forever. A bespoke build is paid once and the running cost is hosting plus optional maintenance.
2. You spend more time fighting the tool than using it
If your team has Notion pages explaining "how to make Salesforce work for our process," or a junior whose job is to maintain three integrations that keep breaking, the SaaS is no longer serving you. You are serving it.
Sign that you have crossed the line: the workaround documentation has grown big enough that onboarding a new hire takes longer than it should. Generic SaaS tools are sold on flexibility, but flexibility has a cost: every business that buys it has to bend their process to fit, then maintain the explanation of that bend.
3. The thing that would unlock real growth is the thing the SaaS won't let you do
You can describe, in one sentence, the workflow change that would meaningfully improve your business. You can show the cost of not doing it. And the SaaS roadmap has no plan for it, or it is sitting behind an enterprise tier that costs more than the build.
This is the moment bespoke pays for itself.
The honest TCO comparison
Most build-vs-buy debates fall apart because people compare the wrong numbers.
The fair comparison is total cost of ownership over 3 years:
- SaaS TCO = (per-seat × seats × 36 months) + integration tooling + the cost of the workarounds and the person who maintains them + the opportunity cost of features you can't have.
- Bespoke TCO = one-off build cost + hosting (usually £10–£50/month for an SME-scale app) + optional maintenance retainer + the cost of changes you'll request as you learn.
When we run the numbers honestly with SME owners, the crossover usually sits around the 18-month mark for a tool with 10+ users. Before 18 months, SaaS wins on cash flow. After 18 months, bespoke wins on everything: cost, fit, ownership, and roadmap control.
If the tool will outlive 18 months in your business, bespoke is the cheaper answer over its life. That is a much higher bar than most vendors will admit.
What you keep when you build bespoke
This part is invisible until you've experienced it.
When you commission a bespoke tool from a competent builder, you keep:
- The source code. You can hand it to another builder if we get hit by a bus.
- The infrastructure. It runs on your accounts, your domain, your data warehouse.
- The roadmap. You decide what changes, in what order. There is no quarterly product roadmap email telling you what's next.
- The data. No exports, no API quotas, no "Enterprise tier" gate.
- The shape. As your business changes, the tool changes. You are not waiting on a vendor's prioritisation.
SaaS rents you the right to use a tool. Bespoke gives you a software asset that compounds in value as your business changes.
When bespoke is the wrong call
Bespoke is not always the answer. We talk clients out of it regularly.
Walk away from a bespoke build when:
- The off-the-shelf tool actually does 80%+ of what you need and the missing 20% is a "nice to have."
- Your business is too young or too volatile to know what you want the workflow to be. Buy SaaS, learn what you actually do, then build.
- You don't have a senior person who can give the build clear feedback. Bespoke succeeds or fails on the quality of conversation with the builder.
- The workflow is genuinely identical to a thousand other businesses. Don't reinvent accounting software.
The decision in one sentence
Buy SaaS for the workflows that don't differentiate you. Build bespoke for the workflows that do, or for the SaaS tools that have become more expensive and more constraining than building. The fork is rarely about cost in the first year; it is about cost, fit, and freedom over three.
If you'd like a second opinion on a specific build-vs-buy decision in your business, the scoping call is free, 30 minutes, and honest either way.