How automation gets built
What actually happens when you automate something.
Most explanations of AI automation describe a result and skip the middle. This page is the middle: what gets examined, how the first system is chosen, how long the build takes, what it asks of you, and the things it will not do.
The short version
Business process automation means handing a repeatable task to software so a person stops doing it by hand. AI automation is the same idea, with one difference: the software can now read messy input, write a reasonable reply, and decide what to do next, so tasks that used to need a human reader can be handed over too.
That difference matters more than it sounds. A rules-based system can send a reminder on a schedule. It cannot read a reply that says next month is better, my sister is getting married and understand that it should stop reminding and offer a date in four weeks. That is the gap that has closed.
An engagement here runs in four stages, in order, and you can stop after any of them.
Stage one
The audit.
Thirty minutes on a call, free, no deck. The purpose is not to describe what we sell. It is to find where enquiries and money are falling out of your business, and to work out roughly how much is falling.
What gets examined
- Every route an enquiry can take in. Phone, WhatsApp, Instagram, the website form, the walk-in, the referral. Most businesses have more than they think, and at least one nobody is watching.
- The first hour. What happens between an enquiry arriving and a person responding to it, at nine on a Tuesday and at nine on a Saturday. These are usually different answers.
- The list you already own. How many past customers or patients are on file, how many are overdue, and what happens to them today. Usually the answer is nothing.
- What gets retyped. Any point where a person moves the same information from one screen to another. Invoices, forms, spreadsheets, booking systems.
- Where things go quiet. Quotes sent and never chased. Treatment plans discussed and never followed up. The fifth message nobody sends.
What is being looked for
One thing: a task that is repeated often, follows a pattern, and has a number attached to it. Frequency makes automation worth building. A pattern makes it possible to build. A number makes it possible to tell afterwards whether it worked.
A task that fails any of those three is a bad first automation, however annoying it is. That is worth saying plainly, because the most irritating task in a business is often the rarest one.
What you need to bring
Nothing prepared. No documentation, no process map, no logins. If you can answer what happens when somebody enquires on a Saturday, that is enough to run the call on.
Stage two
The roadmap.
After the call you get a written document. It lists what could be automated, in the order it should be done, with the reasoning next to each item and an estimate of what the first one should return. It is yours to keep and act on, with us or with anybody else.
How the first automation is chosen
Not by what is most impressive. The first build is chosen against four tests, and it has to pass all four.
- It pays for itself soonest. Reactivating a list you already own tends to win here, because the contacts are already yours and the cost of reaching them again is close to nothing.
- It touches the fewest systems. Every extra system in a build is another thing that can change under you. The first one should be simple enough to finish.
- It is measurable. If we cannot tell in six weeks whether it worked, it is the wrong first build, because you will have no basis for deciding what to do second.
- It fails safely. If it breaks, the worst case is that things go back to being done by hand, not that a patient gets the wrong message.
The best first automation is rarely the most interesting one. It is the one that is finished, measured and paying before anybody gets bored.
Stage three
The build.
A first system typically takes two to four weeks from agreement to running. That is a working estimate based on scope, not a guarantee, and the thing most likely to stretch it is not the code. It is waiting on access to a system somebody else controls.
What you supply
- Access to the systems the automation has to read from and write to, usually your booking or practice management software, your inbox, and whichever number or account the messages go out from.
- Your tone. Real examples of how your team actually writes to customers, because a system that sounds like a call centre gets treated like one.
- Your rules. What can be offered, what must never be promised, what has to reach a human, and who that human is.
- One person who can answer a question within a day. This matters more than anything else on the list.
Where it runs
On infrastructure the studio maintains, connected to the tools you already use. Nothing is ripped out and replaced. If your practice runs on a particular booking system, the automation works with that system rather than asking you to migrate off it.
Nothing goes live to a real customer until you have watched it run. The normal sequence is a build phase, then a supervised phase where every outbound message is reviewed before it sends, then live once you are comfortable with what it is saying.
Third party costs
Some builds need software the studio does not own: a messaging number, an AI provider, a data service. Those are billed through to you at a rate capped and agreed before the build starts, so a busy month cannot produce a surprise invoice.
Stage four
Handover, then optimisation.
At handover you get a written description of what the system does, what it will never do, how to pause it, and who to contact when something looks wrong. Being able to stop it yourself, immediately, without calling anybody, is part of the deliverable.
What runs itself actually means
It means nobody has to remember to do the task. It does not mean nobody looks at it again. Three things reliably drift:
- The systems underneath change. A booking platform updates, a messaging provider changes a rule, an account expires. None of this announces itself.
- Your business changes. A new treatment, a new price, a clinician leaving. A system that was accurate in March is quietly wrong in September.
- Replies teach you things. Once real people answer real messages, patterns appear that nobody predicted, and the sequence gets better because of them.
The monthly retainer covers exactly that: watching it, correcting it, and sending a report of what it did. If you would rather run it yourself after handover, that is a legitimate choice and it does not end the relationship.
The honest part
What it does not do.
Every claim on this site has a limit behind it. Here are the ones that matter most, stated before you ask rather than after you have signed.
It does not replace your team
It removes tasks, not people. In every build worth doing, the front desk ends up doing fewer things badly and more things well. A business that automates in order to cut staff usually finds it has automated the wrong half.
It does not fix a business that is not converting
If people are enquiring, being answered promptly, and still not booking, the problem is the offer, the price or the experience. Automation will get you to that answer faster. It will not change it, and a system that sends more messages into a broken funnel just annoys more people.
It does not sell to a list that does not want to hear from you
Reactivation works because these are your own past customers with a genuine reason to hear from you. It is not a way to message strangers, and the studio will not build that.
It is not instant
Two to four weeks for a first build, then a few more before there is enough data to judge it. Anyone promising a working custom system in a few days is selling a template.
It is not free of judgement calls
An AI system will occasionally produce a reply that is technically right and tonally wrong. That is why builds start supervised, why there is a hard stop for anything clinical or contractual, and why a person keeps reading a sample of what goes out.
Questions people ask at this stage
How does AI automation work in a small business?
Software takes over a repeated task end to end: reading the enquiry, deciding what it needs, replying in your words, and writing the result into your systems. A person sets the rules and reviews the output. The work happens whether or not anybody is at the desk.
What does it cost?
The audit is free. After that there are two charges: a one-time fee to build the system, and an optional monthly retainer to run and improve it. Builds are priced against the value the system is expected to recover, not against hours worked, so the number depends on what the audit finds rather than on a rate card. Third party software the build needs is billed through at a rate capped and agreed before anything starts. You get the full figures in writing with the roadmap, before committing to anything.
How long does the first automation take?
Two to four weeks from agreement to running, as a working estimate. The delay is almost never the build. It is waiting on access to a system somebody else controls, which is why access is the first thing requested.
Do I have to change the software I already use?
No. Automations are built around your existing booking, practice management and messaging tools. If a system genuinely cannot be worked with, you are told that during the audit rather than three weeks into a build.
How much of my time does it take?
A few hours across the build, mostly at the start. You supply access, examples of how your team writes, and the rules about what may never be said. After that the main requirement is one person who can answer a question within a day.
What happens if it sends something wrong?
You can stop it yourself, immediately, without calling anybody. Builds run supervised before they run live, anything clinical or contractual is routed to a human by design, and a sample of what goes out keeps being read after launch.
Do I own it at the end?
The roadmap is yours unconditionally, including if you never work with the studio. The built system and its logic are documented at handover so you can run it yourself, hand it to somebody else, or switch it off.
Where to go next
Start with
the audit.
Thirty minutes, free, and you keep the roadmap.