Build vs buy: when custom software is the wrong answer

It would be convenient for us if every business needed custom software. Most do not, and pretending otherwise is a short-term trade that ends in a project nobody is happy with.

Here is the line we actually use.

Buy when the problem is not yours alone

If thousands of businesses have your problem, someone has already built the solution, priced it at a fraction of a build, and spent years finding the edge cases you have not thought of yet.

CRM, accounting, email marketing, helpdesk, payroll, project management, most e-commerce storefronts. The off-the-shelf options are mature and the gap between them and a custom build is measured in convenience, not capability.

Build when the process is the business

The case for building is strongest when the way you do something *is* your advantage. Then a platform forcing you into its assumptions is not a convenience, it is a tax on the thing that makes you money.

• Your pricing, fulfilment or scheduling logic cannot be expressed in any platform you have tried.
• You are paying several people to move data between systems by hand.
• Platform fees at your volume have grown past what a build and its upkeep would cost.
• The software is the product you sell.

The honest middle

Most good answers are neither. Keep the platform for what it is good at and build the thin layer that makes it fit — a custom front end on a commerce platform, an integration that ends the re-keying, a dashboard that assembles what four systems each know separately.

This is usually the cheapest real improvement available, and it is rarely what anyone asks for, because "replace the whole thing" is an easier idea to hold.

Run the numbers over five years

Subscription costs scale with headcount and time; build costs are largely up front, then maintenance. The two cross at some point, and where that point sits decides the argument.

Budget the whole picture, not just the build — hosting, maintenance, support and the iteration real usage demands. Our cost estimator shows discovery, QA and project management as separate lines precisely because those are what people leave out and then resent.

A question that settles most of it

If a competitor bought the same off-the-shelf tool tomorrow, would you have lost anything?

If the answer is no, buy it. If the answer is yes — if the way you do this is genuinely part of why customers choose you — that is the part worth building.

Should I build custom software or buy off the shelf?

Buy when thousands of businesses have your problem, because someone has already solved it, priced it at a fraction of a build, and found the edge cases you have not thought of. Build when the way you do something is itself your advantage, because then a platform's assumptions are a tax on the thing that makes you money.

What is the quickest way to decide build versus buy?

Ask whether you would lose anything if a competitor bought the same off-the-shelf tool tomorrow. If the answer is no, buy it. If the answer is yes — if how you do this is genuinely part of why customers choose you — that specific part is worth building, which is usually a much smaller scope than replacing the whole system.