The short answer
Buy off-the-shelf software whenever a tool already does roughly what you need, because it's cheaper, quicker and someone else maintains it. Build custom software only when your way of working is genuinely different from most businesses in your sector, when no combination of existing tools covers it, or when the process you'd be running on borrowed software is actually the thing that makes your business work. For most small businesses, that's a small minority of what they do, not most of it.
Why "buy" wins most of the time
Off-the-shelf tools like a CRM, a booking system or an accounting package have had thousands of businesses using them, reporting bugs and asking for features, for years. You get that maturity for a monthly fee instead of a development bill, and updates, security patches and new features arrive without you lifting a finger. If 80% of what a tool does is useful to you, it's usually still cheaper and less risky than building the 20% you're missing.
The honest downside of off-the-shelf software is that you adapt your process to fit the tool, not the other way round. For most admin, bookings and customer management, that's a fine trade. For the handful of things that actually set your business apart, it can be the wrong one.
When custom software earns its cost
Custom-built software is worth considering when one or more of these is true:
- No tool does the specific thing you need, even roughly. You've looked at several options and each one needs serious workarounds to fit.
- The process is your competitive advantage. If how you schedule staff, price a job, or manage stock is genuinely unusual and better than how competitors do it, forcing it into generic software flattens that advantage.
- You're stitching together three or four tools and still hitting limits. If you've reached the point in our guide on 7 signs your business has outgrown spreadsheets and tried a proper off-the-shelf system too, and it still doesn't fit, that's a real signal.
- Customers or staff need their own access. A portal where customers check their own orders, bookings or documents is rarely available off-the-shelf in a way that matches your branding and your exact data.
- You're paying for several subscriptions that each do one part of the job badly. Sometimes one well-built tool replaces four mediocre ones and pays for itself over a couple of years.
A practical checklist
Work through this before deciding either way:
| Question | If yes, lean towards... |
|---|---|
| Does an existing tool cover at least 80% of what you need? | Off-the-shelf |
| Is the remaining 20% something you can live without or work around? | Off-the-shelf |
| Is this process genuinely unusual for your industry? | Custom |
| Would a competitor copying your exact process be a problem for you? | Custom |
| Do customers or staff need a dedicated, branded place to log in? | Custom |
| Are you already paying for three or more tools trying to patch the gap? | Custom (or a proper audit first) |
| Is the budget available right now closer to hundreds than thousands of pounds? | Off-the-shelf |
The middle ground: automation first
Before committing to a custom build, it's worth checking whether connecting your existing tools properly solves the problem instead. A lot of businesses that think they need custom software actually need their current systems to talk to each other reliably, which is a much smaller job. Our guide to 10 admin tasks small businesses can automate this month and our comparison of Zapier vs Make vs a custom integration are worth reading first; they solve a surprising number of "we need custom software" problems for a fraction of the cost.
What custom software actually costs
This varies a great deal depending on scope, which is exactly why it's worth reading our dedicated guide on how much a custom app costs in the UK before committing to anything. As a general shape: a clickable prototype to prove the idea before building it properly is the cheapest way in, an internal tool or dashboard sits in the middle, and a customer-facing portal or booking system with logins, payments and ongoing support costs the most. Our own guide prices start from £750 for shaping an idea into a prototype, through to several thousand pounds for a full internal tool or portal; see pricing for the current ranges.
What to watch out for
- Don't skip the prototype stage. A clickable mock-up, reviewed before any code is written, is far cheaper to change than software that's already built.
- Ask who owns the code. You should own everything built for you, including source code and any accounts it runs on, not be locked into the company that built it.
- Budget for support, not just the build. Software needs occasional updates, security patches and small fixes; factor that into the decision, not just the upfront cost.
- Resist scope creep. Custom projects grow if every good idea gets added before the first version ships. Agree a first version, launch it, then improve it.
- Compare against doing nothing. Sometimes the honest answer is that the current spreadsheet or workaround, while annoying, is still cheaper than either option. It's fine to conclude that.
If you'd rather not do this yourself
We'll look honestly at what you're trying to solve and tell you if an off-the-shelf tool would do the job before we suggest building anything. Have a look at our custom apps and tools service, or tell us what you're trying to build for an honest view and a fixed quote after a free 30-minute call.
Frequently asked questions
Is custom software always more expensive than off-the-shelf?
Upfront, yes, almost always. Off-the-shelf tools spread their development cost across thousands of customers through a subscription. Custom software is built once for you, so the initial cost is higher, though there's often no ongoing licence fee once it's built, and it won't need you to adapt your process to fit someone else's assumptions.
How do I know if an off-the-shelf tool is "close enough"?
A good test is to list the handful of things that genuinely matter about how you work, then see how many of them the tool does natively versus needs a workaround for. If it's one or two workarounds, that's normal. If it's most of your process, it's probably not the right fit.
Can I start with off-the-shelf software and move to custom later?
Yes, and this is often the sensible order. Running on an existing tool for a year or two tells you exactly what you need from a custom build, which makes that build faster and cheaper when the time comes.
What's the biggest risk with custom software?
Scope creep and unclear ownership. A project that keeps growing before it launches, or one where you don't own the code and accounts at the end, causes more problems than the build itself.
Do I need to know exactly what I want before asking for a quote?
No. A short discovery conversation, sometimes followed by a prototype stage, is normally how the detail gets worked out. Coming in with a rough idea and the problem you're trying to solve is enough to start.
Is a custom app the same as a mobile app?
Not necessarily. "Custom software" covers internal dashboards, customer portals and booking systems that often run in a web browser, as well as dedicated mobile apps. Which one you need depends on who's using it and where, and it's worth discussing before assuming you need a mobile app specifically.