What can actually be automated in my business?
Work is worth automating when it passes three tests: it happens often, it follows the same steps each time, and the information it needs already exists in writing somewhere. That covers most of what happens between a message arriving and a job being booked: reading and answering enquiries, qualifying them, sending a quote, chasing the follow-up, raising the invoice, copying the same details into a second system, and assembling the weekly report. It does not cover judgement with no rule behind it, or work whose inputs only exist in somebody’s head. The practical test is whether you could write the steps down for somebody starting on Monday. Whether a tool could do it matters less.
Which jobs qualify?
- Often
- Enough times a week that somebody would notice it stopping. Once a quarter is not worth building for.
- Same steps
- The same decision, on the same inputs, reached the same way. Exceptions are fine if you can name them.
- Written inputs
- The information needed is already in a message, a form, a sheet or a system. Not in a conversation nobody recorded.
What does automating an enquiry actually mean?
Read what arrived, in whichever language it arrived in, and work out what is being asked for. Decide whether it is real work, a supplier, or somebody who has the wrong company. Answer it, with an actual answer rather than a confirmation that it was received. Price it where the price follows a rule, and say what the price depends on where it does not. Offer a time, and write the booking into the calendar that the team already uses. Follow up on the ones that went quiet, on a schedule, until they answer or the schedule runs out.
What else is on the list?
Quotes and invoices. Generated from the details already captured, sent, and chased when unpaid. The chase is the part that gets dropped. Onboarding a new client. The same eight messages, folders, logins and reminders, triggered once instead of remembered eight times. Moving data between systems. The same details typed into a second place because the two do not speak. This is the most common one and the least interesting to describe. Scheduling and reminders. Confirmations, the day-before reminder, the reschedule, and the no-show follow-up. The weekly report. Pulled from the systems that hold the numbers, assembled, and sent. Nobody enjoys this one and everybody does it by hand. Document handling. Reading what arrived as a PDF or a photograph and putting the fields where they belong. Review and feedback requests. Sent after the job rather than when somebody remembers, which is what makes the difference to a Google Business Profile.
What should be automated first?
What is not worth automating?
Judgement with no rule behind it. If two experienced people would decide differently and both be right, there is nothing to encode. Anything that happens rarely. A process that runs twice a year will have changed by the second time, and nobody will remember how the automation worked. Work whose inputs are a conversation. If the information only exists in somebody’s head or in a call nobody wrote up, write it down first. The irreversible step. Sending money, signing something, cancelling something. Automate the preparation and leave the last click to a person.
Does this mean replacing people?
Where does the automation actually run?
Questions people actually ask
- How do I work out whether I have enough volume to bother?
- Count one week. How many enquiries arrived, how many were answered the same day, how many got a second message when they went quiet. Most businesses are surprised by the second and third numbers, and those two are the case for doing anything at all. If the weekly count is in single figures and all of them were answered within the hour, you do not need this yet.
- Does it need to be AI, or is this just automation?
- Most of it is ordinary automation and has been possible for years: a trigger, some steps, a system updated. The genuinely new part is the step that reads something unstructured (a message written any which way, in Arabic or English, or a document) and turns it into fields the rest of the process can use. That step used to require a person. Everything downstream of it did not.
- What happens when something changes in the business?
- Someone has to change the workflow, which is the part that gets left out of the sales pitch. Prices change, the team changes, a tool gets replaced. Our monthly fee is for exactly that: keeping the three workflows working as the business moves. If you are buying from somebody who quotes a build and no monthly, ask who does this.
- Can you automate something in a system we built ourselves?
- Usually, if it has an API or a database we can reach. If it has neither, the options are narrower and sometimes the answer is that the integration is its own project rather than part of a fixed workflow. That is worth establishing before anything is quoted, not after.
- Where should I start if I only want one thing?
- The instant reply, in whichever channel most of your enquiries arrive on. It is the one with the shortest path between building it and seeing a difference, because the problem it fixes, a message sitting unanswered for hours, is happening today and can be measured today.