Every SME we talk to has the same three options on the table and almost none of them have a framework for choosing between them. They pick by vibe — by what a peer recommended, what the founder saw on LinkedIn, or what the cheapest quote suggests.
The result is predictable. SaaS subscriptions that nobody fully adopted. Half-built in-house tools that one developer understood and then left. Bespoke projects scoped at twice what the business actually needed. Months lost, budget burned, and the original problem still on the list.
Here's the test we use.
Buy off-the-shelf when
You should buy when all four of these are true:
- The workflow is industry-standard and your business doesn't compete on it
- A well-known tool already covers 80% or more of the requirement out of the box
- The integration surface is small — one or two systems, no exotic data flows
- Your team has the slack to adopt someone else's process rather than bend a tool to yours
If all four hold, buy. Pay £30 to £300 a month and move on. We will tell you this and step aside — there's no value in us building something a SaaS product already does well.
The trap is the third and fourth conditions. Most failed SaaS rollouts fail not because the product was bad, but because the business had a non-standard workflow and tried to force the tool around it. Two months in, the team is back to spreadsheets and the subscription is renewing on autopilot.
Build in-house when
You should build when all three of these are true:
- You have a competent technical lead who can own the system for at least three years
- The system is genuinely strategic — it's part of how you differentiate, not just important
- You have the runway to absorb a twelve to eighteen month build with no commercial output
Most SMEs fail the second condition. They think the system is strategic because it's important. Important is not the same as differentiating. Your accounts system is important. It is almost certainly not strategic. Your candidate-ranking algorithm, your pricing engine, your underwriting workflow — those might genuinely be differentiators.
The third condition is where good intentions go to die. Twelve months of build time means twelve months in which the system produces nothing for the business. Most SMEs cannot absorb that, and the project either ships late and scoped down, or it doesn't ship at all.
Compose a bespoke system when
You should compose a bespoke system when:
- The workflow is yours — your terminology, your approval chains, your data shape, your edge cases
- Off-the-shelf tools each solve 30% of the problem and none solve 80%
- You need it live in weeks, not quarters
- You want to own the system and the data without hiring a full engineering team
- You want the option to extend it as you learn, without rewriting from scratch
This is the gap 444 builds for. Bespoke doesn't mean writing everything from scratch — it means composing the right modules around your business, using proven building blocks where they fit, and stopping the moment the system earns its keep.
A composed bespoke system typically ships Phase 1 in four to eight weeks. It costs a fraction of a from-scratch build because most of the underlying components already exist. It belongs to you — the data, the logic, the IP. And it's extensible because each module is independent.
The honest verdict
About a third of the businesses that run the diagnostic should buy SaaS. We tell them so and recommend the tool. A small minority — typically those competing on a genuinely technical differentiator — should hire engineers and build in-house. The rest, the majority, sit squarely in the bespoke gap.
That's the population we serve. Not because bespoke is always the right answer, but because for businesses with their own shape and no appetite to wait quarters for results, it's the only one that actually fits.
A quick sanity check
If you can answer yes to all of these, you're probably in the bespoke gap:
- We've tried at least one SaaS tool for this problem and it didn't stick
- We can describe the workflow in terms our team uses, not in terms the SaaS uses
- We need the system live this quarter, not next year
- We want to own the data and the logic, not rent them
If yes to most but not all, the diagnostic will tell you which of the three pathways to take and why.