Every January a small business decides this is the year it gets the right software. Most of them are answering a two-way question that actually has three answers.
Build or buy is the framing everyone arrives with. The third option — leave it alone, and spend the money on something that matters more — wins more often than either, and almost nobody puts it on the list.
What buying is actually good at
Off-the-shelf software is excellent when your process is genuinely ordinary. Payroll, accounting, email, scheduling — these are solved problems, and a product with thousands of customers has absorbed edge cases you have not met yet. Building your own version of a solved problem is one of the more expensive mistakes available to a small business.
The cost of buying is not the subscription. It is that you adapt to the product’s assumptions. That is usually fine, and occasionally it is the whole problem.
What building is actually good at
Building earns its cost in a narrow band: where the process is genuinely specific to how you make money, and where no product fits without contorting the business around it.
The most reliable signal is that you are already paying for two or three products and manually moving data between them. The gap between the products is the shape of the thing worth building — and it is usually far smaller than a full application. Often it is a piece of connective tissue, not a system.
The cost of building that people underestimate is not the build. It is that you now own it: it needs maintaining, it breaks when something upstream changes, and it has exactly one person who understands it.
What “leave it alone” is good at
A spreadsheet that one person maintains, that everyone understands, and that has not caused an incident is not technical debt. It is a system that fits its problem.
The honest test is whether it is failing, not whether it is unfashionable. Replacing something that works consumes the capacity you needed for the thing that is genuinely broken — and there is always something genuinely broken.
Where the answer depends on you
Three variables decide it, and all three are yours: how specific your process really is compared to your competitors’, how much a failure costs you, and whether you have anyone who could maintain what gets built after the person who built it moves on.
That third one is where small businesses come unstuck most often. A build justified purely on volume can still be the wrong call if it creates a dependency nobody can carry — and that judgement needs an honest look at your team, not at your process map.
How we would walk you through it
We look at the process end to end and mark every point where a person moves data between two systems by hand. Those points are where both the cost and the opportunity are concentrated.
Then we cost all three options honestly — including maintenance, including the do-nothing case — and give you the comparison rather than a recommendation dressed as one. Where the answer is buy, we will tell you which category of product and let you choose. Where the answer is leave it alone, we say so, and that has been the right answer often enough that we say it without embarrassment.
This decision work sits at the front of CAO Technologies, ahead of any workflow automation build.
Tell us which two systems your team retypes data between. That single answer usually settles most of the question.
A question worth answering
If the person who maintains your most important spreadsheet left next month, would you rebuild it, buy something, or discover you never needed it? Whichever you answered, that is your real position — not the one in the plan.
