AI Guides › Playbooks
By Nigel Guy · 6 min read
Most people pick a first automation by picking a tool: they open a no-code builder, see 3,000 app logos and start connecting things. Or they pitch "AI automation" to a local business and get a polite blank. It feels like progress because something gets built, and it fails because nobody can say which problem it fixed or how you would tell.
The rule: automate one named leak, with one trigger, one owner and one number you can check in a week. Nothing else goes in the first build.
A "leak" is a repeated bit of work or a repeated loss in a small business: enquiries answered late, appointments missed, reviews never requested, invoices not chased. The tool is the last decision, not the first.
A note on money. You will see claims that small businesses pay thousands of dollars a month for simple no-code automations. We could not verify that figure from any primary source, so do not build a business plan on it. What is verifiable is the cost of the tools (below) and the fact that a client pays for a result they can see, not for the word "AI".
Fill this in before you open any tool. If a line stays blank, you are not ready to build.
| Line | What goes in it | Example |
|---|---|---|
| Leak | One repeated loss, in a sentence | "Website enquiries wait until the next morning for a reply" |
| Trigger | The single event that starts it | "New form submission" |
| Action | The one thing that should happen | "Send an acknowledgement and add a row to a sheet" |
| Human step | What a person still decides | "Owner reads the row and sends the quote" |
| Owner | One named person who watches it | "Front-desk lead" |
| Number | One figure, measured before and after | "Median time to first reply" |
| Off switch | How to pause it in under a minute | "Toggle the workflow off" |
You need a business owner, a week of real examples and the courage to choose boring. Ask for the last ten times the problem happened, not their opinion of it. Rank candidates by three questions: does it repeat at least weekly, is the input already digital (a form, an email, a booking), and is a wrong output cheap to fix? A late acknowledgement is cheap to fix. A wrongly sent refund is not.
With the card complete, the tool choice is mostly arithmetic. Prices below are from each vendor's pricing page on 2026-10-04 and move often. Dollar and euro figures are converted roughly. Check the pound price at checkout.
| Tool | Free tier | Paid entry point | Catch |
|---|---|---|---|
| Zapier | $0, 100 tasks a month, two-step Zaps only | Professional from $19.99 a month billed yearly (about £15 at time of writing), $29.99 billed monthly (about £23), 750 tasks | Multi-step workflows need a paid plan; tasks add up fast |
| Make | $0, 1,000 credits a month, 2 active scenarios, 15-minute minimum interval | Core $12 a month (about £9 at time of writing), 10,000 credits | Each module action uses credits, so a long scenario burns them faster than you expect |
| n8n | Free self-hosted Community Edition | Cloud Starter €20 a month (about £17 at time of writing), 2,500 executions; Pro €50 (about £42) | Self-hosting means you maintain it, including updates and security |
For a first build the free tiers are often enough to prove the idea. Move to paid only when the card's number has improved and the volume needs it.
Build trigger, one action and a notification to the owner. Add an AI step only if the leak needs language, such as drafting a reply from an enquiry. Keep the draft going to a person, not straight to a customer. A reusable brief for the AI step:
You are a drafting assistant for [BUSINESS_NAME], a [BUSINESS_TYPE] in [TOWN].
Goal: write a short, friendly acknowledgement to the enquiry below that a staff member will review before it is sent.
Enquiry: [ENQUIRY_TEXT]
Facts you may use: opening hours [HOURS]; services and prices [PRICE_LIST]; booking link [LINK].
Rules: British English; under 90 words; use only the facts above; if the enquiry asks for anything not covered, say a team member will reply by [TIME]; never promise availability, discounts or medical or legal outcomes.
If any fact you need is missing, list what is missing instead of guessing.
Before answering, check you invented nothing and that the tone matches [TONE_NOTES].
Output: subject line, then body.
Fill in the business facts and the enquiry field your form produces.
Instead of "I do AI automation", say what the card says: "When someone fills in your enquiry form, they get a reply within minutes, and you get a tidy list. We will compare reply times before and after for two weeks." The leak, the number and the time frame are the pitch.
A salon owner, call her Dee, loses enquiries because the form is checked once a day.
| Line | Dee's card |
|---|---|
| Leak | Enquiries sit unanswered overnight |
| Trigger | New form submission |
| Action | AI-drafted acknowledgement for staff to approve, row added to a sheet |
| Human step | Receptionist approves, books the slot |
| Owner | Receptionist |
| Number | Time from form to first reply, taken from the sheet's timestamps |
| Off switch | Disable the workflow |
Week one, you expect to see rows arriving, drafts approved, and a first-reply time lower than the baseline you noted beforehand. You are not expecting a revenue change yet.