Every growing UK business hits the same fork in the road: buy an off-the-shelf software product, or build something custom. Vendors will tell you their product does everything. Developers will tell you custom is the only way. Both are selling something, so here's the honest version — the trade-offs, the real costs, and a decision framework you can actually use.
What "off-the-shelf" really means
Off-the-shelf covers a wide range: SaaS subscriptions (Salesforce, Xero, Shopify), licensed software you install, and industry-specific packages. The defining trait is that the software exists already — you're configuring someone else's product, not creating your own.
Where it wins:
- Speed. You can be live in weeks, sometimes days. For standard needs — accounting, email marketing, basic CRM — this is unbeatable.
- Lower upfront cost. A subscription at £50–£500/month beats a £40,000 build when the need is standard.
- Someone else maintains it. Security patches, updates, uptime — the vendor's problem, not yours.
- Proven at scale. Thousands of users have found the bugs before you. Mature products are battle-tested in ways a new build can't be.
- Ecosystem. Integrations, plugins, consultants, community support, and staff who already know the tool.
Where it hurts:
- Fit is approximate. You adapt your processes to the software, not the other way round. Sometimes that's healthy discipline; sometimes it means abandoning the process that made you competitive.
- Recurring cost compounds. £200/month feels trivial; over five years with price rises and seat growth, it's £15,000–£25,000 — and you own nothing.
- You're on their roadmap. Features you need may never arrive; features you rely on may be deprecated. Your business depends on someone else's priorities.
- Differentiation is zero. Your competitors can buy the same tool tomorrow. Software can't be a competitive advantage when everyone has it.
- Integration limits. APIs have boundaries, and "customisation" often means configuration within narrow lanes. Truly unusual workflows don't fit.
Our guide to the real cost of CRM shows how the subscription maths plays out in one category — the pattern repeats across all SaaS.
What "custom" really means
Custom software is built for your specific requirements: a bespoke CRM, a client portal, an internal operations system, a product that's core to your business model. You own it, it fits exactly, and it costs real money to create.
Where it wins:
- Exact fit. The software matches your processes instead of forcing you to match its. For businesses whose operations are their advantage, this matters enormously.
- Competitive differentiation. Nobody else has it. If software is part of how you win customers, custom is the only route.
- No per-user tax. Licence fees don't scale with headcount. For larger teams, this alone can justify a build — see the cost comparison below.
- You control the roadmap. Features get built when you need them, in the order you need them.
- Integration on your terms. Built to connect with your specific stack, your way.
Where it hurts:
- Upfront cost is real. A meaningful business system typically costs £30,000–£150,000+ to build properly in the UK market. "Cheap custom software" is usually expensive software with the quality removed.
- Time. Weeks become months. A proper build takes 3–9 months for most business systems.
- You own the maintenance. Hosting, security updates, bug fixes, improvements — budget 15–20% of build cost per year, ongoing.
- Requirements risk. If you can't articulate what you need, a custom build will faithfully construct the wrong thing. Vague requirements are the top cause of custom project failure — see our piece on software development problems.
- Partner dependency. You're trusting a development team with a critical asset. Choose badly and you're locked into a bad codebase. Our vetting guide exists for exactly this decision.
The honest cost comparison
Five-year total cost of ownership, illustrative UK market ranges:
| Off-the-shelf SaaS | Custom build | |
|---|---|---|
| Year 1 (10 users) | £8,000–£20,000 (licences + setup) | £40,000–£80,000 (build) |
| Years 2–5 per year (10 users) | £6,000–£15,000 | £6,000–£16,000 (maintenance) |
| 5-year total (10 users) | ~£32,000–£80,000 | ~£64,000–£144,000 |
| 5-year total (50 users) | ~£160,000–£400,000 | ~£70,000–£160,000 |
Notice the crossover: at small scale, SaaS usually wins on cost. At larger scale, per-user licensing makes custom cheaper — and that's before accounting for fit. These are broad market ranges for illustration, not quotes; your numbers will differ, but the shape of the maths holds.
The decision framework
Work through these five questions in order. The first "no" usually decides it.
1. Is this software core to how you compete?
If the system is part of your customer offering or operational advantage — a client portal clients choose you for, a logistics system that's faster than competitors' — build it. Competitive advantage can't be bought off a shelf. If it's back-office plumbing (accounting, HR, email), buy it. Nobody ever won a customer because of their accounting software.
2. Do existing products actually fit?
Not "could we make it fit" — do they fit? Run a proper evaluation: list your must-have requirements, trial the top two or three products with real data and real users, and score honestly. If you're compromising on more than 20–30% of must-haves, or the workarounds are getting creative, that's a build signal. For guidance on evaluating properly, our choosing a web development company piece covers the selection discipline, which applies to software vendors too.
3. What's the true five-year cost of each option?
Price SaaS honestly: licences at realistic seat counts in year three (not today), implementation, integrations, admin time, and renewal increases. Price custom honestly: build cost, 15–20% annual maintenance, hosting, and the internal time for requirements and testing. Compare five-year totals, not year-one stickers.
4. Can you live with the vendor's roadmap?
If the product is missing a feature you need in the next 18 months, will the vendor build it? Check their changelog and public roadmap for evidence, not promises. If the answer is no and the feature matters, that's a build signal — or a different vendor.
5. Do you have the stomach for a build?
Custom software needs an internal owner with real authority, time for requirements and feedback, and tolerance for a project measured in months. If the business can't commit that, buy the best-fit product and adapt. A half-committed custom build is the worst of both worlds: custom cost with off-the-shelf fit.
The hybrid answer most businesses actually need
The real world is rarely either/or. The pattern that works for most UK SMEs:
- Buy the commodity layer. Accounting, email, standard CRM, HR — proven SaaS, configured well.
- Build the differentiating layer. The client portal, the quoting engine, the operations system that reflects how you actually work — custom, integrated with the commodity layer via APIs.
- Integrate ruthlessly. The value is in the connections: the custom portal pulling data from the SaaS CRM, the bespoke quoting tool feeding the accounting package. Integration is where hybrid setups succeed or fail.
This is the architecture behind most of our application development work — custom systems that sit on top of, and talk to, best-of-breed SaaS, giving clients differentiation where it matters and reliability where it doesn't.
The bottom line
Buy what makes you standard; build what makes you different. Run the five questions honestly, price five years not one, and don't let either camp's sales pitch do your thinking. The right answer is the one that fits your business — not the vendor's quota or the developer's preference.
If you're leaning towards custom and want an honest assessment of what it would take, talk to us — including telling you when you'd be better off buying.
FAQs
Is custom software better than off-the-shelf?
Neither is universally better. Off-the-shelf wins on speed, upfront cost, and maintenance for standard needs. Custom wins on exact fit, differentiation, and long-term cost at scale. The right choice depends on whether the software is core to how you compete.
How much does custom software cost in the UK?
A meaningful business system typically costs £30,000–£150,000+ to build, plus 15–20% of build cost per year for maintenance and hosting. Broad market ranges — the actual figure depends entirely on scope and complexity.
When should a business build custom software?
When the software is core to your competitive advantage, when no existing product fits more than 70–80% of your must-have requirements, when per-user licensing makes SaaS more expensive over five years, or when you need control over the roadmap.
What are the risks of custom software development?
The main risks are vague requirements leading to the wrong build, choosing the wrong development partner, underestimating maintenance costs, and under-committing internal time. All are manageable with proper scoping, vetting, and ownership.
Can you combine off-the-shelf and custom software?
Yes — and most UK SMEs should. Buy proven SaaS for commodity functions (accounting, email, standard CRM) and build custom for differentiating processes, integrating the two via APIs. This hybrid approach is usually the best value.
