AI & automation

The admin, running on its own

Four jobs eat most of a small business's week. None of them need a person until the moment judgement is actually required.

Leo Liebenberg · Durbanville, Cape Town

What actually gets automated

The same four jobs, in every business.

It does not matter much whether you are a physiotherapist, a salon or a plumber. The shape of the lost time is nearly identical, and it is nearly always these four.

Someone tries to reach you and nobody answers. At nine at night, or while your hands are full. They message the next business on the list and you never find out it happened. An instant, useful first reply is the single highest-value thing to automate, because it is the only one where the money leaves before you know there was money.

The same details get typed twice. Written on a pad, typed into a diary, typed again into an invoice. Every retype is a chance to get a phone number wrong. Capture it once, at the source, and the rest is just plumbing.

The quote goes out late. You knew the number on Tuesday. It left on Friday. By then they had two others and picked whoever replied first — which is usually the deciding factor, not price.

The follow-up never happens. The polite nudge, the unpaid invoice, the client you have not spoken to in eight months. Not refusal — just the job nobody wants after a twelve-hour day.

How it is built

Boring, observable, and it does not phone you.

Automation earns its keep by being dull. A workflow that runs every day for a year without anyone thinking about it is worth more than a clever one that needs watching. So the systems I build are event-driven, log everything they did, and fail loudly to me rather than silently to you.

Orchestration is usually n8n, self-hosted, because the logic should live somewhere you can read it and take it with you. Messaging runs on the official WhatsApp Business Platform under a written agreement — never a personal WhatsApp account with client details in it, which is the most common and least defensible thing I see in small businesses. Hosting is Cloudflare. The language-model work is on the Anthropic API.

  • n8n
  • Anthropic API
  • WhatsApp Business Platform
  • Cloudflare Workers
  • Webhooks
  • Structured data
  • POPIA

The AI part

It drafts. You decide.

The useful version of AI in a small business is not a chatbot that speaks for you. It is an assistant that knows your prices, your hours, your services and your policies, answers the questions you answer ten times a week, and drafts everything else for you to approve in one tap.

That line — drafts, does not decide — is deliberate and I do not move it. An assistant that sends unattended will eventually promise a customer something you cannot deliver, and you will be the one holding it. Leverage, not abdication.

The other half is the unglamorous half: using a model to turn machine output into something a human actually reads. A weekly summary that says how many bookings came in, how many no-showed and who has stopped coming back is worth more than a dashboard nobody opens.

Where the pattern came from

I learned this on a harder problem.

Before small-business automation, I architected and ran a pipeline that had to be right every single morning without anyone in the loop: pull the day's live vulnerability feeds, score them against exploit-probability data, match them to the exact installed software version on each of thousands of individual machines, open a staged workflow when something genuinely dangerous turned up, hold it behind two-person approval before anything touched a server, and use a language model to turn all of that into plain English somebody non-technical could act on.

Nothing about booking a haircut is harder than that. What carries over is the discipline: verify at the level of the individual thing rather than the group, never let an automated step take an irreversible action unattended, and write the output for the person who has to read it rather than the person who built it.

Straight answers

Questions about automation.

What is business process automation, in plain English?
It is software doing the repetitive admin a person currently does by hand — taking a booking, sending a confirmation, reminding someone the day before, chasing an unpaid invoice, copying details from a form into a diary. The work still happens, it just stops costing you evenings. Good automation is invisible: you notice it only because the jobs you used to dread stopped arriving.
Can a business really take bookings over WhatsApp?
Yes, on the official WhatsApp Business Platform under a written agreement — not a personal WhatsApp account. A customer messages at any hour, the system offers real open times from the diary, books one, confirms it and sends a reminder before the day. Consent is asked in the chat before any personal details are taken, and the cross-border transfer is disclosed, which is what POPIA expects.
Will an AI assistant answer my customers without me?
Only for the questions you have already answered. It handles prices, hours, directions and services, and it drafts everything else for you to approve in one tap. It does not send unattended replies on anything it is unsure of, because an assistant that promises a customer something you cannot deliver leaves you holding it. AI is leverage, not abdication.
What do you build automation on?
Orchestration is usually n8n, self-hosted, so the logic lives somewhere you can read it and take it with you. Messaging runs on the official WhatsApp Business Platform, hosting on Cloudflare, and the language-model work on the Anthropic API. Nothing is locked to a platform you cannot leave.
Is my customers' data safe in an automated system?
That depends entirely on how it is built, which is why I default to storing the least that makes the job work, encrypted, with consent captured before details are taken and a record of who was told what and when. Under POPIA the practice or business is the responsible party and the supplier is the operator, and that relationship has to be in writing. If a supplier has never given you that agreement, you do not have one.
How long does it take to set up?
Simple automation — an instant reply, a booking flow, a reminder sequence — is usually a matter of days once the decisions are made. The part that takes time is not the building, it is agreeing exactly what should happen at each step and what the system must never do on its own. That conversation is the work; the rest is plumbing.

Next

Which job would you take back first?

Tell me the task that eats the most of your week and you will get a plain answer about what handing it over actually looks like. Client work runs through Trevern Technologies, where the booking and automation service lives.