Writing

Build vs buy: should you automate it or just buy software?

Most small businesses ask this question backwards. They start with "what should we build" when the right default is "what can we just buy." Custom automation is powerful, but it is the exception, not the starting point. Buy first. Build only when buying genuinely fails you, and for a reason you can name.

Default to buying

Off-the-shelf software is cheap, already built, and maintained by someone else. When a product does the job the way you already work, paying a monthly fee beats building every time. You get updates, support, and security without owning any of the upkeep. If a fifty-dollar-a-month tool solves it, the conversation is over. Buy it and move on.

Four signs you should build instead

1. Your process is genuinely specific. Not "we like to do it our way," but a real workflow that no product models, often because it grew out of your particular customers or industry. Forcing a generic tool onto it costs you more in workarounds than it saves.

2. The tools do not talk to each other. If the work lives across email, spreadsheets, a CRM, and an accounting app that all ignore one another, the value is in the connective layer between them. That layer is almost never something you can buy.

3. The task is your bottleneck. When one repetitive step gates everything downstream, shaving it is worth real money, and a tool that gets you 80 percent there still leaves the expensive 20 percent on your plate.

4. The work is a differentiator. If how you do this thing is part of why customers choose you, you do not want the same off-the-shelf process your competitors have. That is worth building.

The hidden cost of buying: tool sprawl

Buying has a failure mode too. One tool becomes five, each solving a sliver, none of them talking, and you become the human glue copying data between them. At that point you have not bought a solution, you have bought a part-time job. If you are stacking subscriptions to patch around a process, the build conversation is worth having.

The honest answer is usually a hybrid

Buy the commodity pieces. Build the judgment layer. Use the email provider, the accounting software, the CRM that already exist, then build the thin custom automation that connects them the way your business actually runs. You are not rebuilding what works. You are building the part that only exists in your business.

How to decide in ten minutes

Write down the steps of the task. Ask whether a single product does roughly 80 percent of it. If yes, buy it and accept the rest as manual for now. If the 20 percent it cannot do is exactly where your time or money leaks, that 20 percent is what you build. You almost never need to build the whole thing, just the expensive part nobody sells.