"We can't afford bespoke software" is something we hear regularly. And in a narrow sense, it's often true — a custom-built application costs more upfront than signing up for a SaaS product.
But most businesses comparing options aren't making an apples-to-apples comparison. They're comparing the full cost of building something against the monthly fee for one subscription — not the true cost of the SaaS approach over three to five years.
When you work through the numbers properly, the gap is often smaller than it looks. Sometimes it disappears entirely.
The real cost of SaaS
A single SaaS subscription is cheap. The problem is that most businesses don't use a single SaaS product — they use several, often with overlapping functionality, and none of them quite fits the way the business actually works.
The real cost of SaaS includes:
- Monthly fees, per user, at the tier you actually need. Basic plans often don't include the features you need. The plan that does what you need is three times the price, per seat, and you're paying it every month indefinitely.
- Multiple tools that don't talk to each other. Moving data between systems manually — or paying for an integration tool to do it — is a cost that compounds quietly over time.
- The workaround tax. Every workaround your team maintains costs time. Time costs money. It's rarely tracked, but it adds up.
- Vendor risk. SaaS products get repriced, discontinued, or acquired. You don't control the roadmap, and you can't stop a vendor from doubling their prices or removing a feature you depend on.
- Data portability friction. Getting your data out of a SaaS platform cleanly — if you ever need to move — is often harder than it sounds.
The real cost of bespoke
Custom software has a higher upfront cost. That's real, and it shouldn't be ignored.
But it's also worth being clear about what you get for that cost:
- Software built around your process. Not a generic workflow you've adapted to — your actual workflow, captured in code.
- An asset you own. The software doesn't disappear if a vendor folds. There are no per-seat fees that scale with your headcount. You own the codebase.
- Integration by design. Rather than bolting together systems that weren't built to talk to each other, a custom application can be designed to handle your full workflow in one place.
- A platform that evolves with you. When your needs change — and they will — you can add to the software without waiting for a vendor to put it on their roadmap.
Running the numbers
The comparison that matters is total cost of ownership over a realistic time horizon — three to five years is usually sensible.
For SaaS: add up all the subscriptions you're currently using (or would need to use) to cover the same ground. Include the admin time for workarounds and data management. Project that forward over five years, including likely price increases.
For bespoke: the build cost is a one-time capital expense. There are ongoing hosting costs (typically modest), and ongoing development costs for maintenance and new features (typically a fraction of the build cost per year).
In our experience, businesses spending more than around £500–£800 per month across SaaS tools to manage a core operational workflow often find that bespoke is cost-competitive at the three-year mark — and clearly cheaper by five years.
It's not always bespoke
This isn't an argument that custom software is always the answer. For many needs, SaaS is absolutely the right call — it's faster to get started, the software is maintained by someone else, and if your needs are well-served by what's available, there's no good reason to build.
The point is that "SaaS is cheaper" isn't automatically true — particularly when the workflow you're trying to support doesn't map neatly onto what any existing product does.
If you're trying to work out which side of this your situation falls on, we're happy to work through it with you. Get in touch and tell us what you're currently running on.