Bespoke software vs off-the-shelf: how to choose
When to buy a ready-made product, when to build your own, and the questions that settle it. A plain guide for UK small businesses.
Bespoke software is built for one business and owned by it. Off-the-shelf software is a ready-made product that many businesses rent, usually by the month. Neither is better in general. The right choice depends on how closely a ready-made product fits the way you work, and what it costs you as you grow.
We sit on both sides of this. We build bespoke software for clients, and we also sell off-the-shelf products of our own. So this is the comparison as we would give it to a friend.
The short version
| Off-the-shelf | Bespoke | |
|---|---|---|
| Cost to start | Low | Higher |
| Cost over time | Rises with users or usage | Mostly fixed once built |
| Time to start using it | Days | Weeks to months |
| Fit to how you work | You adapt to it | It is built around you |
| Who owns it | The vendor | You |
| Who maintains it | The vendor | You, or whoever built it |
| If the vendor changes price or closes | You move | Not applicable |
When off-the-shelf is the right answer
Buy a product when the job is a common one done in a common way. Accounting, email, payroll and card payments are solved problems, and a good product will do them better than anything built for one business.
It is also the right answer when you are still working out how the business runs. Software built around a process that is about to change is money spent twice.
When bespoke earns its cost
Building your own makes sense in three situations.
Your way of working is the advantage. If the thing customers value is how you schedule, quote or deliver, software that forces you into everyone else’s process removes what makes you different.
You are stitching products together by hand. When staff spend hours moving information between tools that do not connect, you are already paying for the missing software, in wages.
Per-user pricing is punishing growth. A product that charges for every person you add gets more expensive exactly when the business is doing well. Owning the software turns that rising bill into a fixed one. We wrote about this in the real cost of per-seat software.
Five questions that settle it
- Does a product exist that does at least most of what you need, the way you need it?
- What does it cost at twice your current size?
- How many hours a week go on working around its gaps?
- If the vendor doubled the price, could you leave?
- Is the process stable enough to build around?
If the answers are “yes, fine, few, yes, not yet”, buy the product. If they are “not really, a lot, many, no, yes”, it is time to price a build.
The middle path
It does not have to be all or nothing. The most sensible projects we see keep the ready-made tools that work (accounts, email, payments) and build only the piece that is specific to the business, connected to the rest. That keeps the build small and the cost down.
Who looks after it
The weakness of bespoke software is what happens after launch. A product has a company behind it. A bespoke system has whoever built it, if they are still around. Ask any developer what happens in year two: who hosts it, who fixes it, and what that costs.
This is the part we care about most. We run our own platforms every day, so we build client software expecting to operate it for years, and we price the running of it up front. Read more about how we build custom software, or start a conversation about what you need.