Off-the-shelf vs. custom software: how to actually decide

"Should we build this or buy it?" sounds like a question about money, but it's really a question about fit — how close an off-the-shelf tool gets to the way your business actually works, and what it costs to close that remaining gap.

Off-the-shelf software wins when the problem you're solving isn't unique to you. Accounting, email, basic scheduling — thousands of other businesses have the exact same requirements, so someone has already built, and refined, a good answer.

Custom software earns its cost when the process itself is what makes your business run differently from a competitor — a specific booking flow, an inventory rule unique to your supply chain, a workflow that off-the-shelf tools force you to work around instead of through.

The number that actually matters isn't the sticker price — it's the total cost of ownership over several years. A 'buy' decision hides its real cost in licensing renewals, workarounds for the 20% it doesn't do, and the cost of integrating it with everything else you run. A 'build' decision hides its cost in ongoing maintenance, and in whoever built it eventually moving on.

A useful middle ground gets skipped too often: buy the parts that are genuinely commodity, and build — or extend — only the specific piece that's actually load-bearing for how you operate. Very few businesses need to build everything, and very few should try to buy everything either.

The honest version of this conversation starts with mapping what your team actually does today, exceptions included, before pricing either option. Most bad build-vs-buy decisions come from skipping that step, not from picking the wrong side.