Bespoke software or off the shelf?
Buy off the shelf when your process is ordinary and the software is cheap enough to be disposable. Build bespoke when the way you work is the thing that earns you money, and nothing on the market will bend to it. Most businesses end up with both, and the skill is knowing which job belongs in which column.
The question behind the question
People rarely ring us and ask whether to build or buy. They ring and say that something has stopped working. The spreadsheet has forty tabs and only one person understands it. Two systems hold the same customer and disagree about the address. Someone spends Thursday afternoon copying numbers from one screen into another.
That is the useful starting point, because it is specific. Before you compare products, write down the job that is going wrong, who does it, and how long it takes them each week. If you cannot describe the job in a paragraph, you are not ready to buy or build, and any quote you get will be a guess.
When off the shelf is the right answer
Buy when the job is one that thousands of other businesses do in more or less the same way. Payroll. Accounting. Email. Video calls. Card payments. These are solved problems, the products are mature, and no customer has ever chosen a supplier because of the accounting package behind the invoice.
Buying is also right when you are not yet sure what you need. A subscription you can cancel in a month is a cheap way to learn what the job actually requires. Plenty of our clients ran on an off-the-shelf product for a year first, and arrived with a much clearer brief because of it.
The honest test is this: if the software vanished overnight and you replaced it with a competitor, would your customers notice? If the answer is no, buy it.
When bespoke earns its keep
Build when the process is the product. A swim school that runs missed-class credits differently from every other swim school cannot buy that difference. A waste company whose pricing depends on postcode, skip size and access can either find a product that models all three or spend forever working around one that does not.
Three signals that bespoke is worth costing up:
- You are paying people to be the integration. Someone re-keys data between two systems every week. That salary is the real price of the off-the-shelf setup, and nobody puts it in the comparison.
- You are paying per seat for features you never open. Growth makes this worse, not better. Per-seat pricing punishes you for hiring.
- The workaround has become the process. New staff are trained on the workaround. It is now institutional knowledge, and it is fragile.
None of these on its own justifies a build. Two or three together usually do.
The two options, side by side
Neither column is the good one. They fail differently, and the failure modes are what you are really choosing between.
| Off the shelf | Bespoke | |
|---|---|---|
| Time to first use | Days | Weeks to months |
| Cost shape | Ongoing, per seat or per month | Larger up front, then hosting and support |
| Fit to how you work | You adapt to the product | The product is built around you |
| Who fixes a problem | A support queue, on their timetable | The team who built it, on yours |
| If your process changes | Wait for the roadmap, or work around it | Change the software |
| If you stop paying | Access ends, data export varies | You own it and it keeps running |
| Biggest risk | Outgrowing it, or a price rise you cannot refuse | Scoping it badly at the start |
The middle path most people miss
The choice is rarely all or nothing. The most useful thing we build is often not a replacement for the products a business already pays for. It is a thin layer that makes them talk to each other.
Keep the accounting package. Keep the payment provider. Build the bit in the middle that knows your rules, and let it push and pull data through the interfaces those products already publish. It is a smaller build, it carries less risk, and it removes the re-keying that was costing you a salary.
If an agency's first answer is to replace everything, ask why the smaller version will not work.
How to decide in about a week
You do not need a consultancy exercise. You need five things written down.
- Time the job. Ask the person who does it how many hours a week it takes. Not an estimate from above, an actual number from them.
- Add up what you already pay. Every subscription touching that job, every seat, and the hours from step one at a real hourly cost.
- Try to buy it. Shortlist two products and book demos. Take your awkward case, the one your business always trips over, and ask them to do it live. Most demos fall apart at exactly that point, and that is the answer.
- Get one build quoted. Not the whole system. The single worst job. A fixed price for a small piece tells you more than an estimate for a big one.
- Compare three years, not one. Subscriptions win year one almost every time. The interesting question is where the lines cross.
If the products handle your awkward case, buy. If they cannot, and the job is costing you real hours, cost up the build. If it is close, buy now and revisit in a year with better information.
Common questions
Not over the life of the system. Off the shelf is almost always cheaper in year one, because you are renting rather than buying. Bespoke tends to win later, and it wins sooner if you are paying per seat for a growing team or paying someone to move data between systems by hand. Compare three years rather than one, and include the hours people spend on workarounds.
It depends on scope. A focused tool that does one job well can be a matter of weeks. A full platform is usually three to six months. We agree a written scope, a timeline and a fixed price before any code is written, so the answer is specific to your project rather than a range.
Yes. You own what we build, handed over cleanly, with no lock-in. If you later want another team to take it on, they can. We think that is the only honest arrangement, and it is also what keeps us useful to clients years after launch.
That is usually the better project. Most businesses do not need their accounting package or payment provider replaced. They need a layer in the middle that knows their rules and moves data between the tools they already pay for. It is a smaller build and it carries less risk.
Say so on the call. We will tell you if an off-the-shelf product does the job, and we have told plenty of people exactly that. A discovery conversation costs nothing and it is a much better use of an hour than a proposal for something you do not need.
Where to go next
If you want a straight answer about your own situation, tell us what you are trying to do and we will say what we would do, including when the answer is that you do not need us. Start a conversation.