Build vs Buy for Small Business Software

We build custom software, and we start most conversations by trying to talk people out of it. Not out of modesty — because buying is usually cheaper, faster, and lower risk, and a custom project sold to somebody who should have bought a product ends badly for everyone.

Here is the test we actually use.

Start by assuming you should buy

For most business functions, somebody has built the product, spread the cost across thousands of customers, and spent years finding the edge cases you have not thought of yet. Accounting, payroll, CRM, email, scheduling for common trades — buy these. The build case is close to nonexistent.

The advantages are large and easy to underrate: it exists today, somebody else maintains it, it gets better without you paying for each improvement, and if it is wrong you can leave.

The question that decides it

Evaluate the best-fitting product honestly, then ask: to use this, what would we have to change about how we work, and does that change make us worse?

Most of the time the answer is "a few things, and no." Your process was not sacred; it was whatever evolved. Adopting the product’s way is fine and often an upgrade.

Occasionally the answer is "a central thing, and yes." The process the product cannot accommodate is the reason customers choose you — the scheduling logic that lets you turn work around faster, the pricing model nobody else offers, the quality step that produces your reputation. Flattening that to fit software is trading your advantage for a licence fee.

Build when the process is the product. Buy when the process is just how you happen to do it.

The other legitimate build cases

Nothing exists for your niche

Genuinely narrow industries get skipped by software vendors because the market is too small. Tire mold machining, specialty lumber grading, regional franchise service networks — sometimes there really is no product.

The integration is the job

You have four systems that will not talk. The work is not a new application, it is the connective tissue between existing ones. That is custom by definition and it is often much smaller than a full build.

The licence arithmetic flips

Per-seat pricing at forty users, for ten years, is a large number. It is worth doing that arithmetic against a build plus maintenance — and worth doing it honestly, including the maintenance, which people leave out.

The costs people forget on each side

The right-hand column is why buying wins so often. A build is not a purchase, it is an ongoing commitment, and the honest comparison is against the total.

The hybrid, which is usually the real answer

Most businesses that need something custom do not need everything custom. Buy accounting. Buy payroll. Build the one thing that is genuinely yours, and integrate it with the rest.

That is the shape of nearly every project we do. Thomson’s Landscaping did not get a custom accounting package — they got a point-of-sale system built to their process that talks to the inventory system they already had. Smaller scope, lower risk, and the custom work is spent where it buys something.

Before you decide

1. Write down the process, as it actually runs, not as the org chart says.
2. Find the three best-fitting products and get demos with your real scenario, not theirs.
3. For each, list what you would have to change. Mark which changes make you worse.
4. If that list is empty or trivial, buy. Today.
5. If one item is central and makes you worse, scope a build around just that.

The scoping quiz runs a version of this in seven questions and hands back a written brief — including whether the honest answer is that you should be buying something instead.