Free guide · The First Automation

Build your first automation this weekend.

One working automation, built by you, live by Sunday night: every new enquiry gets answered in minutes, and followed up in three days if it goes quiet. No developer, no jargon, and your progress saves as you go.

Time: 3 to 4 hours across a weekend Cost: $0 to $30/month Skills: if you can set up email, you can do this

Why this automation first

Every business has enquiries, and speed decides who wins them. Reply within five minutes and you are talking to a customer; reply the next day and you are one of three quotes. It is also the safest possible first build: the inputs are already digital, the steps are the same every time, and the worst failure is an email that does not send.

Already know a different process is your biggest cost? Run it through the Workflow Score first. If it beats enquiry follow-up on score, build that instead; the steps below still apply.

The rule for any first automation: pick something you would happily do the exact same way 100 times in a row. If it needs judgement every time, it is not ready.
0 of 8 steps

Saturday morning · about 90 minutes

1. Map it on paper

30 minutes

Draw the journey of one enquiry today, from the moment it arrives to the moment someone replies. Five boxes maximum. Write down: where enquiries land (email inbox, website form, socials, phone), who sees them first, how long they typically wait, and what the reply usually says.

Stop check: if you cannot draw it in five boxes, the process is not understood well enough to automate. That is a useful discovery, not a failure. Write the steps down first.

2. Write the two emails, once, properly

45 minutes

Your automation is only as good as the words it sends. You need two templates:

  • The instant acknowledgment. Thanks them, tells them what happens next and when ("you'll hear from me by tomorrow morning"), and asks the one or two questions you always need before quoting.
  • The three-day follow-up. Sent only if they have not replied. Short, useful, no "just checking in".

Do not write these from a blank page. The enquiry reply and quiet-lead prompts in our Prompt Pack will draft both in your voice in ten minutes.

Saturday afternoon · about 60 minutes

3. Pick your plumbing

20 minutes

The tool matters far less than people think. Pick whichever one connects to where your enquiries already land. We have no affiliation with any of these.

Enquiries land in...Simplest option
Your email inboxGmail or Outlook rules plus templates. Free, no new tool.
A website formYour form tool's built-in auto-response, or connect it to Zapier or Make.
Several places at onceZapier or Make as the hub. Free tiers cover most SMB volumes.
Microsoft 365 shopPower Automate. Already included in most plans.

4. Build the happy path

40 minutes

One trigger, one action: new enquiry arrives, acknowledgment goes out. Nothing else yet. Set the trigger (new email matching your enquiry pattern, or new form submission), attach your acknowledgment template, and turn it on.

Then send yourself a fake enquiry from a personal address and watch it work. That first automatic reply landing in your inbox is the moment this stops being theory.

Sunday · about 90 minutes

5. Add the safety rails

30 minutes

  • BCC yourself on everything it sends, for the first week at least.
  • The follow-up condition: the three-day follow-up only sends if there has been no reply. Every automation tool has this check; do not skip it.
  • The handoff rule: decide what the automation does NOT touch. Complaints, existing clients, and anything mentioning a dollar figure go straight to a human. Write this down.

6. Break it on purpose

30 minutes

Send five test enquiries: a normal one, a vague one-liner, one with an attachment, one from a weird address, and one that is clearly not an enquiry at all (a supplier invoice, say). Watch what the automation does with each.

What you are looking for: the wrong emails getting a reply is worse than a missed one. Tighten your trigger conditions until the invoice does not get a cheery "thanks for your enquiry!".

7. Write the one-pager and tell the team

20 minutes

One page, four answers: what triggers it, what it sends, what it never touches, and how to turn it off. Save it where the team can find it and tell whoever handles enquiries that it exists. An automation nobody knows about becomes a mystery that erodes trust the first time something odd happens.

The week after

8. Watch it for a week, then count

5 minutes a day

Check your BCC copies daily for the first week. Fix anything odd. On Friday, count: how many enquiries got answered in minutes instead of hours, and how many follow-ups went out that you would never have sent manually. Write those two numbers down. That is your before-and-after, and you will want it.

If it worked

You just did, in miniature, what a proper systemisation pass does across a whole business: found a repeatable process, wrote it down, built the fix, added the rails, measured the result. The question is no longer "can this work" but "which process is next, and what is the queue worth in dollars".

If it broke

Also useful. First automations fail in three predictable ways, and each failure tells you something real:

  • The inputs were not digital. Enquiries arrive by phone or walk-in. Fix the capture first (a simple form), then automate.
  • Too many exceptions. Every enquiry needed judgement. The process needs standardising before automating.
  • The template felt robotic. A words problem, not a tech problem. Rewrite with your real voice, using a real email you have sent.

None of these mean automation is not for your business. They tell you exactly what to fix first.