When Custom Software Is Worth It (And When It Isn't)

Custom software is expensive to build and expensive to maintain. That's not a reason to avoid it — it's a reason to be certain before you start.

The honest default is off-the-shelf. If an existing tool does eighty per cent of what you need for a monthly fee, adapting your process to it is almost always cheaper than building the missing twenty per cent yourself.

Custom becomes worth it when the process you're automating is the thing that makes your business distinctive, when the manual work is large and recurring enough that the maths clearly favours automation, or when you're paying for several tools that don't talk to each other and the glue between them is costing more than the tools.

A useful test: write down the process by hand, step by step, before anyone writes code. If you can't describe it clearly on paper, software will not clarify it. It will encode the confusion and make it harder to change.

And budget for the second year. Software isn't a purchase, it's an ongoing commitment — hosting, updates, dependency changes, and the small fixes that keep it useful.