Buy first. Build only when the tool you bought starts bending your business to fit it. Off-the-shelf software is the right answer most of the time, and the signs that you have outgrown it are easy to spot once you know them.
The cost of getting this wrong runs both ways. Build too early and you pay to maintain something a subscription already did. Stay too long and you pay every month in workarounds, double entry and a bill that grows faster than the business.
When should you just buy it?
When the job is common. Moving a form into a spreadsheet, sending a reminder, syncing two apps that already talk to each other: thousands of businesses share those problems, and a standard tool will beat a custom build on cost, speed and reliability.
Buy when the volume is modest, when you need it working this week, and when the process is likely to change and you want to change it yourself. If a tool covers most of the job cleanly, take it and handle the rest by hand until the gap actually hurts.
Have you outgrown it?
Four signs show up again and again:
- The bill climbs with every job you win. Per-task pricing that was trivial at low volume becomes one of the bigger lines on the statement.
- Your rules do not fit. The process has exceptions the tool cannot hold, so people track them in a side spreadsheet, and the spreadsheet becomes the real system.
- One job runs through five subscriptions. Each one is another login, another bill, another place for a record to go wrong.
- The records are sensitive. Client files should not sit in a general-purpose tool shared with thousands of other businesses.
What costs most?
Three things, and none of them is the code. How clearly the process can be written down. How many existing tools it has to work with. And who watches it once it runs. Building software got cheaper through 2025 and 2026. Understanding a business did not.
That is also why a half-way answer is often the right one: keep the common parts on the tool you already pay for, and build only the piece that genuinely outgrew it.
What goes wrong?
At the shopping stage. Owners compare tools before they have written down the job. Map the work first: what starts it, every step, every decision, what happens when something goes wrong. Half the time the map shows steps you can delete, which is cheaper than automating anything.
And sometimes the answer is neither. A job that happens twice a month may not be worth a tool or a build.
One step for this week
Pick the one task your team repeats most. Write it out end to end on one page. Then ask one question of it: does a common tool cover this as written, or would we have to change how we work to fit the tool? If it is the second, bring the page to the five questions you should ask before you hire anyone.
Nothing we build comes off the shelf. See why.


