What should a small business automate first?
2026-10-14 · 6 min read
Rather not build it yourself? We build the automation on your tools and keep it running. Get it built for me→
It's Tuesday, a little after four. You've had three calls go to voicemail since lunch. Two quotes from last week still haven't had a follow-up. Your office manager is putting together the confirmations for tomorrow by hand, and you remember the Smiths still owe for September. Every one of those could be automated, and that's what makes it hard to pick. Where do you start?
My answer, after building these systems for small businesses: automate first the work that happens every day, goes the same way every time, and costs you a job or a payment when it's late. For most service businesses that's missed calls or quote follow-up. Invoicing reminders usually come next. Reporting and training documents can wait, even though those are the ones owners tend to ask about first.
The three tests for what to automate first
Put each piece of repetitive work through three questions.
Does it happen often? Something you do forty times a week pays back faster than something you do once a month. A monthly owner report is annoying, but it's one afternoon. Calling back missed calls happens all day, every day.
Does it follow the same steps every time? The best first project is one where you could write the steps on an index card: the call is missed, a text goes out, the reply lands in one place, someone calls back. If every case needs judgment about pricing, scope or a customer's history, it isn't a good first project. Automate the steps around that judgment later.
Does something walk away when it's late? This is the question that matters most. A late owner report costs you nothing but irritation. A missed call that waits until tomorrow is often a customer who already booked whoever picked up. A quote nobody follows up on tends to go quiet and close with someone else. When being late costs you the job, fixing it pays back far faster than a tidier report ever will. Whatever passes all three tests goes first.
How the common bottlenecks usually rank
Here's how the usual candidates score for a typical small service business. Your business may be different, which is why the next section has you check your own week.
| Bottleneck | How often | Same steps each time | Cost of being late | Usual priority |
|---|---|---|---|---|
| Missed and after-hours calls | Daily | Yes | The caller books someone else | First |
| Quote and estimate follow-up | Daily to weekly | Mostly | The quote goes cold | First or second |
| Intake and lead capture | Daily | Mostly | Callbacks without the details you needed | Second |
| Confirmations and reminders | Daily | Yes | Empty slots and wasted drives | Second (first for booked practices) |
| Invoicing and payment chasing | Weekly | Yes | Money comes in late, rarely lost outright | Third |
| Reporting and owner updates | Weekly to monthly | Yes | Decisions made on old numbers | Later |
| Onboarding, SOPs and training | When you hire | No, it varies | Slow ramp-up for new staff | Later |
Two notes on that table. Appointment-based businesses like dental offices, salons and med spas often put confirmations first, because an empty chair is their version of a missed call. And if a lot of your money sits in late invoices, invoicing moves up, even though money that's late is usually not money that's gone.
Find yours in one week
Don't guess. Run a tally for five working days.
- Put a sheet of paper by the phone and one on the desk of whoever does the office work.
- Every time someone does a repetitive task, they make a mark next to it: called back a missed call, chased a quote, typed a form into the job software, sent a reminder, chased a payment.
- Next to each mark, write a W if that one turned into work you won, and an L if it didn't, or if you never found out.
- Friday afternoon, count up.
The task with the most marks and the most L's is your first project. In my experience it usually turns out to be the one people complain about least, because it's spread out across the whole day in two-minute pieces.
If missed calls win, you can see what a missed call costs your business in the missed call calculator, and read how long missed-call texting takes to set up.
What a first project looks like
A good first project is small enough to go live in a week or two, and it stays in a single lane. Using missed calls as the example:
- When a call to the business number isn't answered, a text goes out within a minute, with the business name and a question about what they need.
- The reply goes to one shared place, not to whichever phone happened to ring.
- Anything that looks urgent goes to the person on call right away.
- Everything else lands on a callback list sorted by when it came in.
- Once a week you look at what came in and what turned into a job.
That's the whole first project. Get it running, and get your team trusting it, before you add the next thing. When I've seen these projects go sideways, it was usually because someone tried to fix five bottlenecks at once and then nobody could tell which part broke.
For a Chicago-area pool service company, the first piece was lead capture and tracking on the website, so every inquiry landed in one place with its source attached. Stripe payments came after that, built on top of it. For a freight forwarder, the first piece was intake: sorting quote, import, export and general inquiries as they come in, so nobody had to dig through a shared inbox. Neither project tried to fix the whole business on day one.
What stays human
Automation handles the first minute and the repetitive steps. A person still owns the conversation. Someone has to call the customer back, price the job, and handle the reply that doesn't fit the template ("my basement is flooding" isn't a scheduling question). Someone also has to decide what the rules are, like who gets a call instead of a text and when a follow-up should stop. Before you automate anything, name the one person who looks at it every week. If nobody has that job, the system will drift and nobody will notice until a customer does.
What it costs to start
If you want help with the first one, builds start at $500 one-time, then a flat monthly from $99 after an included run-in period, cancellable. There's a fuller breakdown in what business automation costs, and the business automation page shows the kinds of systems I build.
Not sure which one is yours?
Book a free 20 minute process audit. We'll walk through your week, I'll tell you which bottleneck I'd start with and why, and if the answer is a better habit and no software at all, I'll say that too. Book it here.