Should you build custom software or buy off the shelf?

Most of the time, you should buy

Let me start where the honesty is a little uncomfortable for someone who builds software for a living. For most jobs, the ready-made tool is the right answer. Someone has already spent millions building a booking system, an accounts package, a CRM, and they spread that cost across thousands of customers. You get the benefit for a few pounds a month. No custom build competes with that on price for a common problem.

So the first question is never 'what should we build'. It is 'has someone already built this well enough'. If they have, buy it, and put your money and your attention somewhere that actually sets you apart.

When off-the-shelf starts to hurt

Bought tools stop being cheap the moment they nearly fit but not quite. You know the feeling. The software does eighty per cent of what you need, and the other twenty per cent is a daily tax of workarounds, exports, copy-paste and the words 'the system cannot do that'.

That tax is invisible on the invoice and very real in your week. When your team is bending how they work to suit the tool, paying for five overlapping subscriptions, or keeping a secret spreadsheet on the side to make the 'system' usable, the off-the-shelf option is no longer the cheap one. You are just paying for it in hours instead of pounds.

When a build genuinely pays off

Custom software earns its price in a few specific situations, not as a general upgrade.

• The thing you do differently is the thing that makes you good. If your way of working is your edge, bending it to fit generic software throws that edge away.
• You are losing more in workarounds than a build would cost. Once the wasted hours add up to more than the price of fixing it properly, the maths has flipped.
• The tools you already use will not talk to each other, and joining them by hand has become a job in itself.
• You have outgrown the ready-made tool, and the only way up is a plan you do not control, priced per user, forever.

If none of those is true, you probably do not need custom software yet, and I will say so.

The mistake people make in both directions

Buying when you should build looks like a low bill and a slow bleed: years of workarounds and per-user fees that quietly grow past what a build would have cost.

Building when you should buy is the opposite, and more painful: a big cheque for something you could have rented for a few pounds a month, that you now also have to look after. Nobody should build their own email or their own accounts software. Those problems are solved.

The skill is not preferring one or the other. It is knowing, honestly, which side of the line your particular problem sits on.

The cheap way to find out

You do not have to guess. A short, fixed-price look at the actual problem will tell you whether to buy, build, or simply change how one process works. Often the answer is 'buy this tool and automate the one bit it misses', which costs a fraction of a full build.

The right answer is whichever one solves the problem for the least total cost over the next few years, not the one that flatters whoever you asked. Bring me the problem and I will tell you straight which way I would go.