Custom software or off the shelf: an honest comparison

We build custom software for a living, which makes this an awkward article to write honestly. So: most of the time, buy something.

When off the shelf wins

If the process is one thousands of other companies also run — payroll, accounting, email, CRM at its most standard — someone has already built it better than a bespoke project will, and they maintain it for a fraction of what maintaining your own costs.

The temptation is to say "but we do it differently". Sometimes that difference is a genuine advantage. Far more often it is an accident of history that nobody has questioned, and the honest move is to change the process rather than build software to preserve it.

When building is the right call

The process is the advantage. If how you do it is why customers choose you, handing it to a product that flattens it into someone else's workflow is giving that away.

Nothing fits, and the gap is expensive. Not "no product is perfect" — every product is imperfect. Expensive: people spending hours a week on workarounds, or errors that cost real money.

Integration is the actual problem. Often the systems are fine and the joins between them are not. That is a smaller, cheaper build than replacing anything, and it is frequently the right answer.

The question that decides it

What does this cost us today, measured rather than estimated? If nobody can answer, the project has no way to prove it worked, and no way to stop if it is not working.

The answer that should worry you

If a supplier agrees that everything should be custom before asking what your process looks like, they are describing their invoice rather than your problem. A good number of our first conversations end with a recommendation to buy something, fix a process, or wait. That is a useful outcome for both sides, and it costs nothing to find out.