All articles
automationsmall businessoperations

What should a small business automate first?

Automate your follow-up first. It's where small businesses quietly lose the most money, and it's the safest thing to hand to software.

July 5, 20262 min read

Automate your follow-up first. The gap between "someone reached out" and "someone got a response" is where small businesses quietly lose the most money, and it's the safest thing to hand to software.

I've looked inside a lot of small business operations, and the pattern repeats: leads come in through a form, a phone call, or a referral, and then they wait. Not because anyone is lazy, but because following up is nobody's job. It happens when someone remembers. Meanwhile the lead calls your competitor, who answered.

Why follow-up is the right first automation

It doesn't require judgment. "When a form comes in, create a record, send a confirmation, and remind me if nobody has replied in two business days" is a rule a machine can follow perfectly. No AI required, no gray areas.

The payoff is obvious. Your response time drops in the first week, and you can watch it happen. Most automation projects take months to prove themselves. This one doesn't.

Failure is cheap. If your follow-up automation breaks, a reminder doesn't fire and you're exactly where you are today. Compare that to automating your invoicing badly. Start where mistakes are boring.

What it looks like in practice

Nothing fancy. A form or inbox feeds one central list. Every new inquiry gets a confirmation so the person knows they were heard. If nobody on your team responds within a set window, someone gets a nudge. That's it. You can build this with tools you likely already pay for.

The index card test

Here's the rule I use for deciding whether something is ready to automate: if you can write the instructions on an index card, it's automatable. If you can't, you're not ready, and no software will fix that. Pricing decisions, proposals, anything where the answer starts with "it depends": those stay human until the "it depends" turns into a rule.

That's also why I'd wait on anything you haven't done manually at least a dozen times. Automation freezes a process in place. Freeze a process you haven't figured out yet and you've just made your confusion faster.

The bigger point

Automate the boring thing, not the impressive thing. The flashy project makes a better demo. The boring one makes you money.

If you want a second set of eyes on where to start, that's exactly what my discovery engagement does, or book a free consultation and we'll talk through it. Wondering about the build side? Here's how long an internal tool actually takes.