When custom software is the wrong choice

We build custom software for a living, so take this seriously: sometimes you should not. A custom build is the right answer more rarely than the people selling custom builds tend to admit, and knowing the difference protects your budget.

Buy the commodity, build the difference

Accounting, payroll, e-mail, document storage: these problems are solved, and the off-the-shelf tools are excellent because thousands of organisations fund their improvement. Custom software earns its cost where your process is genuinely yours, the part of how you work that gives you an edge or that no standard tool will ever fit.

The real cost arrives in the years after

A custom build is not a purchase, it is ownership. It needs maintenance, security updates, and evolution as your organisation changes, and that ongoing cost is part of the honest calculation. If the budget only covers the build, the build is the wrong plan.

The hybrid answer

Most of the time the right shape is neither pure standard nor pure custom: a standard core for the solved problems, with a thin custom layer where your process genuinely differs, connected through integrations instead of replacements. You get the maintenance economics of off-the-shelf where it is commodity, and ownership only of the part that earns it.

An honest test

Three questions do most of the work:

• Does this genuinely differentiate you, or is it plumbing?
• Would an off-the-shelf tool force a process change that actually harms you, or just a change?
• Are you ready to own software long term?

If custom loses that test, we will say so and point you to the boring option, because a recommendation you can trust on the small decision is the one you can trust on the big one.