Bespoke Software vs Off-the-Shelf SaaS: The Three-Year Cost for UK Businesses
Co-founder of Koseti, data analyst and business intelligence specialist
Bespoke software vs SaaS for UK businesses: build costs, per-user fees, a worked three-year comparison and when each option is the right choice.
Off-the-shelf SaaS is cheaper in year one and the right choice when your process is standard. Bespoke software usually becomes cheaper by year two or three when you pay per user, run a process no product fits well, or are paying for several tools stitched together. At Koseti, a focused bespoke tool typically costs £3,500 to £8,000 to build, and a full SaaS product £8,000 to £20,000.
Bespoke software vs SaaS at a glance
Off-the-shelf SaaS | Bespoke software | |
|---|---|---|
Upfront cost | Little or none | £3,500 to £8,000 for a focused tool at Koseti; £8,000 to £20,000 for a SaaS product |
Ongoing cost | Monthly fee, usually per user, rising as you grow | Hosting and maintenance, mostly flat as you add users |
Time to start | Same day | Weeks to a few months |
Fit to your process | You adapt to the product | The software follows your process |
Who owns it | The vendor | You own the code and the data |
Price changes | Set by the vendor | Set by your own roadmap |
What does bespoke software cost in the UK?
Bespoke software from Koseti typically costs £3,500 to £8,000 for a focused internal tool, such as a booking system, a job tracker or a client portal, and £8,000 to £20,000 for a full SaaS product with accounts, billing and an admin area. The main things that move the price are the number of user roles, the number of systems it connects to, and whether it handles payments. Larger agencies and enterprise projects cost much more; these figures reflect a small studio building in Laravel for small and medium-sized businesses.
After launch, bespoke software still has running costs: hosting, security updates, backups and small changes. Budget for these from day one. They are usually far lower than per-user subscription fees, but they are not zero.
What does SaaS really cost over three years?
The real cost of SaaS is the monthly fee multiplied by users and by months, plus the price rises and add-ons that arrive along the way. A tool that costs a few pounds per user looks cheap until the team grows, a feature you need sits on a higher tier, or you are paying for three tools and a connector service to make them talk to each other. The cost that rarely appears on an invoice is staff time spent working around a product that does not quite fit, re-keying data between systems or keeping a spreadsheet alongside the software.
A worked three-year comparison
The figures below are an illustration, not a quote. They assume a business with 15 staff using a SaaS tool at £40 per user per month, with no price rises and no extra add-ons, against a focused bespoke tool built for £6,000 with an assumed £150 a month for hosting and maintenance.
SaaS (15 users at £40) | Bespoke (£6,000 build, £150 a month) | |
|---|---|---|
Year 1 | £7,200 | £7,800 |
Year 2 | £7,200 | £1,800 |
Year 3 | £7,200 | £1,800 |
Three-year total | £21,600 | £11,400 |
In this example the SaaS option is slightly cheaper in year one, and the bespoke option pays for itself early in year two. Change the assumptions and the answer changes: with 3 users at £15 per user per month, the SaaS costs £1,620 over three years and bespoke would never catch up. That is why the useful question is not "which is cheaper" but "at what point does each option become cheaper for us".
What hidden costs should you budget for?
Both options carry costs that do not appear on the first quote.
With SaaS, watch for:
Price rises at renewal, which the vendor sets and you cannot negotiate as a small customer.
Features locked to a higher tier, which move every user onto the more expensive plan.
Connector services and add-ons needed to link the tool to the rest of your systems.
The cost of leaving: exporting data, retraining staff and rebuilding workflows if the product changes or closes.
With bespoke software, watch for:
Scope that grows during the build. Agree a first version that does one job well, then add to it.
Hosting, security updates and backups, which need a named owner and a monthly budget.
Changes after launch. Every business finds things to improve once real staff use the software, so keep some budget back for the first three months.
When is off-the-shelf SaaS the right choice?
SaaS is the right choice when:
Your process is standard, such as accounting, payroll, email or a basic CRM.
You have a small team and the per-user cost stays low.
You need it working this week.
The product's compliance work, such as payroll rules or tax filing, would be expensive to rebuild.
Koseti recommends SaaS in these cases, and often builds the connections between SaaS tools rather than replacing them.
When is bespoke software worth it?
Bespoke software is worth it when:
Per-user fees grow faster than the value you get as the team grows.
Your process is how you win work, and forcing it into a generic product makes you slower or worse.
You are paying for several tools and a connector service to do one job.
You want to sell the software to others, which means you need to own it.
Customers or staff need one login that shows exactly what they need and nothing else.
What about a hybrid approach?
Most businesses end up with a hybrid: SaaS for the standard jobs and a smaller bespoke layer for the part that makes them different. A bespoke client portal can pull invoices from Xero, bookings from a calendar and records from a CRM, so customers see one clear view while the business keeps the tools it already trusts. This is often the cheapest route, because you only build the part no product does well.
What Koseti has built
Koseti built Voco, a multi-channel AI front office for UK businesses, from an empty repository in Laravel. Voco is itself a SaaS product, and it works the hybrid way: rather than replacing the tools its customers use, it books into Google Calendar, Outlook and Cal.com, logs callers in HubSpot and Attio, and accepts requests from other apps through webhooks. Building a product like that is the clearest test of when bespoke is worth it: its owners needed to own the software, control its pricing and connect it to the tools their customers already use.
How to decide in five questions
How many people will use it now, and in three years?
What would the SaaS cost per month at that size, including the tier you actually need?
How much staff time goes on workarounds each week today?
Do you need to own the code, the data or the pricing?
Could a small bespoke layer on top of existing tools solve the problem instead of a full replacement?
If the answers point to bespoke, see Laravel development for how Koseti scopes and prices custom builds.
Frequently asked questions
Is bespoke software always more expensive?
No. It costs more upfront, but it often costs less over three years once per-user subscription fees grow with the team.
How long does bespoke software take to build?
A focused tool usually takes a few weeks to two months at Koseti. A full SaaS product with billing and multiple user roles takes longer, typically several months.
Who owns bespoke software?
With Koseti, the client owns the code and the data once the project is paid for. Check this in any contract, because it is not automatic with every supplier.
What happens if the developer disappears?
Koseti builds on Laravel, one of the most widely used PHP frameworks, so another Laravel developer can pick up the code. Insist on access to the code repository and hosting from day one, whoever you hire.
Can I start with SaaS and move to bespoke later?
Yes, and it is often the sensible route. Using SaaS first shows you which features you actually need. Make sure you can export your data before you commit.
Written by
Kosi Etimbuk-Udoekong
