Writing

How much should small business automation cost?

The honest answer is that it ranges from almost nothing to tens of thousands of dollars, which is useless on its own. So here is a way to think about it that keeps you from overpaying for a logo agency or getting nickel-and-dimed by the hour.

The market splits into two very different worlds

On one end you have commodity gig work: a single two-app connection for fifty to a few hundred dollars. It is cheap because it is shallow. It connects two things and breaks the first time your process changes, because nobody asked what the process was actually for.

On the other end you have serious custom work: a real, owned automation built around how your business actually runs. In 2026 that lands anywhere from a couple thousand dollars for one focused workflow to ten thousand and up for something that touches several systems. Ongoing support and iteration usually runs as a monthly retainer in the low thousands.

The expensive mistake is paying serious-tier prices for commodity-tier thinking. You want the judgment that comes with the build, not a contractor who wires up whatever you point at.

Stop paying by the hour

Hourly billing quietly works against you. It rewards the vendor for being slow and punishes them for being efficient. The better someone is, the less you should pay per outcome, but hourly flips that on its head. It also means you carry all the risk: an open-ended meter with no fixed finish line.

Fixed scope and fixed price put the risk where it belongs. You know the number before you start, the vendor is paid for the result instead of the clock, and efficiency becomes their problem to solve, not your bill to absorb. That is why everything I do is productized: one automation, one price, shipped.

The only number that actually matters: payback

Forget the sticker price for a second and look at payback. Take the hours a task eats each week, multiply by what an hour of that person's time is worth, and you have the annual cost of leaving it alone.

Say a task burns five hours a week at forty dollars an hour. That is roughly ten thousand dollars a year, every year, forever. Against that, a one-time automation in the low thousands pays for itself in a few months and then prints time back every week after. If the payback period is under a year, the price tag is almost beside the point. If it is over two or three years, do not build it yet.

When to just buy software instead

Sometimes the right answer is a forty-dollar-a-month tool, and an honest advisor will tell you so. If an off-the-shelf product already does the job the way you work, buy it. Custom automation earns its cost when your process is specific enough that no tool fits, when the work spans systems that do not talk to each other, or when the thing you are automating is the bottleneck the whole business waits on. The skill is knowing which case you are in before you spend a dollar.

A simple rule for what to spend

Spend in proportion to what the task costs you today, not what the technology costs to build. Find your most expensive repetitive task, price a year of doing it by hand, and you have your budget ceiling. Anything that pays back inside a year is a good deal. Start with one, ship it, let it run, then fund the next one out of the time the first one gave back.