Bespoke software vs off-the-shelf: how to decide
Bespoke or off-the-shelf software? Here is how to decide, what each costs over time, and when a mix of both is the better answer.
Buy off-the-shelf software when a product already does what you need with little customisation. Build bespoke software when your process is how you make money, when you keep working around a tool, or when per-user fees would grow faster than a build would cost. If a product fits, a good developer will tell you to buy it.
Bespoke software, also called custom software, is designed and built for one business around its own processes. Off-the-shelf software is a packaged product you adapt your processes to. Neither is better in general. The right choice depends on a handful of questions.
Five questions that decide it
1. Does the process give you an advantage? If how you quote, schedule or deliver is part of why customers choose you, forcing it into someone else's template can weaken it. If the process is the same as everyone else's, a product is fine.
2. How much do you work around the tool? Spreadsheets kept beside the system, data re-keyed between tools and manual monthly reports are the signs. A little is normal. A lot means the product does not fit.
3. How will the cost grow? Subscriptions are charged per user or per feature, so the bill grows with the business. A build is a one-off cost plus hosting. Add up the licence cost over three to five years and compare it with a fixed quote.
4. Who owns the result? With a product, the vendor owns it and you rent access. With bespoke software, you own the code and IP on payment, so you can change it, move it or hand it to another team.
5. How stable is the process? If the workflow changes every month, build nothing yet. Write the process down first. Bespoke software suits a process you understand well.
Side by side
| Bespoke software | Off-the-shelf software | |
|---|---|---|
| Fit to your process | Built around how you work, including the edge cases | You adapt your process to the product |
| Upfront cost | Higher: a one-off build at a fixed price | Lower: a subscription or licence from day one |
| Running cost | Hosting and optional support, with no per-user licence fees | Recurring fees that grow with users and features |
| Ownership | You own the code and IP on payment | The vendor owns the product and you rent access |
| Time to first use | Weeks to months, with working software reviewed along the way | Days to weeks |
| Changing it later | You decide what gets built next | You wait for the vendor's roadmap |
| Main risk | Building the wrong thing, which a Discovery is designed to prevent | Paying for features you do not use and workarounds you do |
It is not either-or
The best answer is often a mix. Buy the parts that are the same for every business, such as accounting, email and payroll. Build the part that is specific to you, and connect it to the products through their APIs. That keeps the build small and puts the money where it gives you an advantage.
There is rarely any benefit in replacing a giant platform such as Salesforce or Oracle NetSuite. The better move is a small service that plugs into it and does the one thing the platform does not.
The test is cost against benefit. If building does not pay back for you, we will say so and suggest you buy.
When to buy
- A mainstream product covers nearly everything you need
- The process is still being worked out and will change month to month
- The budget only stretches to a template
- Speed matters more than fit
When to build
- Your process is a source of advantage and packaged tools force workarounds
- Staff re-key data between systems or run the business from spreadsheets
- Per-user licence fees keep growing
- You need to connect systems that no product integrates
How to test the decision cheaply
Before committing to a build, run a Discovery. It produces a written scope, a prototype and a fixed quote, so you compare a real number against the cost of the product. If the numbers favour the product, you have spent a small fee to learn that. See how Discovery works. For a longer side-by-side, see custom software vs off-the-shelf and bespoke SaaS.
A simple way to compare the cost
Take the licence price, multiply by the number of users and the number of years, and compare the total with a fixed build quote plus hosting. As an illustration only, not a quote: a product at $60 per user per month for 25 people costs $18,000 a year, or $90,000 over five years, and the fee rises as the team grows. A medium custom build is roughly $10k to $30k plus hosting. Your numbers will differ, but the exercise shows which side the cost falls on.
Count the hidden costs on both sides too: the time staff lose to workarounds on a product that does not fit, and the cost of running and changing a build.
Common mistakes
- Choosing from a feature list instead of a workflow. A product that ticks every feature can still be awkward for the way your team actually works. Test it against a real day of work.
- Underestimating integration. Whether you buy or build, the software has to connect to what you already run.
- Building before the process is understood. Writing the process down first is cheaper than rebuilding software around a process that was wrong.
- Treating the decision as permanent. You can start with a product and replace the part that does not fit later.
Frequently Asked Questions
What is bespoke software?
Software designed and built for one business, around its own processes, instead of a packaged product you adapt to. You own the code, and it does what you need.
Is bespoke software more expensive?
Upfront, usually. Over several years it can cost less for a team that would pay a per-user fee on a product.
Can I start with a product and move to bespoke later?
Yes, and it is often the sensible order. Use the product until its limits start costing you time, then build the part that does not fit.