Should you build custom software or buy off the shelf?

The default answer is buy. Off-the-shelf software is cheaper, available today, and someone else maintains it. A company that builds custom software telling you to buy first should tell you something about how often custom is the right call.

But the default is not always right, and the cases where it is wrong are reasonably easy to identify.

Buy when the process is standard

Accounting, payroll, email, CRM, e-commerce, scheduling. These are solved problems. Thousands of businesses need the same thing, so a product exists and it is better than anything you would commission, because it has absorbed a decade of edge cases you have not encountered yet.

Paying $50 a month for something that would cost $30,000 to build is not a compromise. It is the correct decision.

Build when the process is your advantage

If the way you do something is genuinely different, and that difference is why customers choose you, off-the-shelf software will force you to work like everyone else. That is the strongest argument for building.

The tell is when you are paying for a product and then maintaining a spreadsheet alongside it to handle what it cannot. That spreadsheet is a specification for software that does not exist yet.

The costs each option hides

Buying hides: per-seat pricing that scales badly as you grow, the cost of exporting your data if you leave, integration work to connect it to everything else, and the process changes you make to fit the tool.

Building hides: maintenance, which is the big one. Software is not a purchase, it is a commitment. Budget 15 to 20 percent of the build cost annually for keeping it working. Also hosting, and the risk that the person who built it becomes unavailable.

A build quote without a maintenance conversation attached is incomplete.

The middle option most people miss

You rarely have to choose. The strongest setup for most small businesses is buying the standard components and building only the thin layer that is genuinely yours.

Use the established accounting package. Use the established CRM. Build the piece that connects them and encodes the way you actually work. That thin layer is often a few thousand dollars rather than tens of thousands, and it delivers most of the benefit of a custom system without the maintenance burden of one.

A decision test

Build only if you can answer yes to all four:

1. Is this process genuinely different from how others in your industry do it?
2. Is that difference worth money to you or your customers?
3. Have you actually trialled the off-the-shelf options, rather than assumed?
4. Can you fund maintenance for the next three years, not just the build?

A no to any of them means buy, or wait.

If you do build

Insist on owning the code outright, in your own repositories. Insist on documentation. Start with the smallest version that is useful rather than the complete vision, because the complete vision is always partly wrong and you will discover which parts only by using it.

And be suspicious of anyone who agrees to build without first asking whether something already exists.

If you are weighing this up, describe what you are trying to do and you will get an honest read, including a recommendation to buy something off the shelf when that is the right answer.