Playbook

What to Automate First in a Small Business (and What You Never Hand Over)

By David Saleh · Silas Main · 17 July 2026

A hot water system, a Salisbury backyard, a phone buzzing in a work shirt pocket that nobody hears over the van radio. Three enquiries came in that Tuesday afternoon. Two callers rang the next business that picked up. One became a job.

That's the real starting point for AI in a small business. Not a concept, not a demo. A phone ringing while the person who could answer it is doing the paid work that call was about to create more of.

We build AI systems for small businesses in Adelaide, under Silas Main: trades, tour operators, care providers, event businesses, kids' activity studios. Different industries, same pattern every time. The order you automate in matters more than what you automate.

The order that actually works

1. Missed calls and enquiries, first.
2. Follow-up on people who already showed interest, second.
3. Admin: quoting, scheduling, invoicing, third.

Get that order backwards and you spend money polishing the part of the business that was never the leak.

Why enquiries come first

An enquiry that goes unanswered is a customer who already decided to spend money with you, and then didn't. That's the most expensive loss a small business has, because it never shows up in any report. Nobody logs the calls that rang out.

Do the maths on your own numbers, not ours. Average job value, times missed or slow-answered enquiries in a normal week, times 52. Most owners have never run that formula, because you can't count what you didn't hear ring.

We built a triage system for a plumbing company in Adelaide that reads every new enquiry the moment it lands, sorts it by urgency, and drafts a reply in the office manager's own voice. It doesn't send anything on its own. She reads the draft, edits what she wants, and sends it herself. It caught a genuine emergency inside its first week live, and turned a five minute reply into a ten second read and a click. We go through exactly how that sort works, bucket by bucket, in the enquiry triage prompt linked below.

That's what "enquiries first" looks like in practice. Not a robot promising things to a customer. A system that makes sure nothing that walked in the door gets missed, with a person still deciding what goes back out.

Why follow-up is second

Most small businesses handle the person who's already on the phone reasonably well. Where the money disappears is after that call ends. A quote goes out Thursday, the customer goes quiet, and nobody chases it because everyone's already flat out on the job that's already booked.

Following up isn't about pestering someone. It's making sure a quote that took twenty minutes to write doesn't die of silence. A short, plain check-in a few days later recovers work that was already half sold. This sits second in the order, after enquiries, because you can't follow up on a lead you never captured properly in the first place.

Why admin comes last

Admin is the easiest thing to automate and the least urgent. Invoicing, scheduling, supplier emails: none of it brings in a new customer. It saves hours, and hours matter, but hours saved on the back end do nothing for a business that's still losing the leads that would have filled them with paid work.

Owners often want to start with admin. It feels safer: nothing customer facing, nothing that can go wrong in front of a client. That instinct makes sense, and it's still the wrong order. Fix the leak before you polish the bucket.

What we refuse to automate

A few things never get handed to a system, on any build, for any business.

A system never sends a reply to a customer without a person reading it first. Every draft stays a draft until someone who works there says otherwise.

A system never invents a policy, a price, or a yes or no it wasn't explicitly given. That failure is common enough, and expensive enough, that it has its own playbook on this site, linked below.

A system never makes the judgement call on an emergency. It can flag "this looks urgent" in plain words. It doesn't decide what happens next.

A system never does the actual trade. The plumbing, the tour, the class, the event: the thing the business actually does, and the reason the customer called in the first place. It answers the phone. It doesn't do the job.

A tool is not a system

A chatbot widget bolted onto a website is a tool. It answers a question when someone types one in. A triage system is different: it watches every channel a customer could use, all day, and makes sure a person sees the one thing that can't wait before the four things that can.

Most owners we talk to have already tried the tool version: a chat widget, an auto-reply, a canned text. It helped a little, then plateaued, because a tool waits to be used. A system goes looking for the problem before the problem finds you.

That distinction matters when you're deciding what "automate this" actually means for your business. Buying a chatbot is not the same decision as building a system that reads your inbox on a short cycle, sorts what it finds, and drafts the reply before anyone has to ask it to. One is a gadget sitting on the homepage. The other changes what a normal Tuesday looks like.

Where to start this week

Pick one: the phone, or the enquiry inbox. Whichever one is currently the fastest way to lose a customer without anyone noticing. Fix that, prove it over a week or two, then move to follow-up, then admin.

The two prompts below are what we run with a new business before a dollar gets spent on anything. Try the first one on your own numbers tonight.

The prompts

You are helping [BUSINESS NAME], a [INDUSTRY, e.g. plumbing / tour operator / kids' activity studio] business in [SUBURB OR CITY], work out what to automate first.

Here is how the business currently handles enquiries, follow-up, and admin:

ENQUIRIES: [Describe how a new customer currently reaches you: phone, website form, social DM, walk-in. Who answers, and how fast, on a normal day and on your busiest day.]

FOLLOW-UP: [Describe what happens after you send a quote or a price. Who chases it, after how long, and how often it actually happens versus how often it's supposed to.]

ADMIN: [Describe your invoicing, scheduling, and supplier communication. How much time per week it takes, and who does it.]

MONEY: Average job or booking value is $[X]. In a normal week we estimate we miss or lose track of [NUMBER] enquiries that would likely have converted.

Using only the information above:
1. Calculate the estimated annual cost of missed enquiries (average value times missed enquiries per week times 52). Show the working.
2. Rank enquiries, follow-up, and admin in the order I should automate them, based on where the actual dollar loss is happening in THIS business, not a generic rule.
3. For the top-ranked item, describe in plain language what a first, narrow automation would do, and what it would explicitly NOT do (who still approves or sends anything).
4. Flag anything I described that should never be automated, and say why.

Keep the answer under 400 words. No jargon. Write it like you're explaining it over coffee, not presenting a slide deck.

You are helping me write a one page guardrail policy for [BUSINESS NAME] before we automate anything with AI.

The business: [one or two sentences: what you do, who your customers are, and what would genuinely go wrong if an AI got it wrong, e.g. "we run kids' birthday parties" or "we're an emergency plumber"].

Write a short, plain language list of rules for what an AI system is never allowed to do here without a person checking first. Cover at minimum:
1. Sending anything to a customer (email, SMS, chat reply) without a person reading it first.
2. Stating a price, a policy, a yes or no, or an availability answer that isn't written down somewhere as a confirmed fact.
3. Deciding what counts as an emergency, a safety issue, or a complaint that needs a person immediately.
4. Doing or claiming to do the actual service the business sells: the trade, the tour, the class, the care, the event.
5. Anything specific to THIS business that would be a genuine problem if an AI got it wrong (ask me if you're not sure, don't guess).

For each rule, add one sentence on what the system CAN do instead: usually flag it, draft it, or ask a person.

Output this as a numbered, one page policy I could print and stick above the desk. Plain English, no jargon, under 300 words total.

Questions

Adelaide · ACST · ABN 17 626 827 646