Where to start with automation: a five-step audit for a UK small business

Step 1: choose one process to examine

Choose a process rather than a tool. “Automate the business” is too broad to assess properly. Handling a new enquiry, confirming a booking or preparing a follow-up has a beginning, steps and an outcome you can describe.

Start with something familiar enough to map. It may also be a process that regularly interrupts the owner or moves between several channels.

Look for friction, not fashionable use cases

Ask the people involved where they have to do the same task repeatedly. You might hear that someone copies details from an email into a spreadsheet, checks several places for an appointment request or writes similar replies each evening.

Write down the process in one sentence, for example: “When a new domestic cleaning enquiry arrives, we collect the property details, check whether the location is covered and decide who follows up.” This gives the audit a useful boundary.

Do not combine unrelated processes yet

A new enquiry, an existing-customer complaint and an urgent technical question may all arrive through the same inbox, but they do not necessarily belong in the same workflow. Different requests may need different information, owners and safety checks.

Keep the first audit narrow. Examine connected processes later if the first map shows that they genuinely depend on one another.

Step 2: map what happens today

Before considering automation, record the current path from the first message to the next meaningful action. Include the channels people use, the information they need and the points where work waits.

For a small building firm, the path might begin with a phone call, continue with a text message requesting photographs and end with a person deciding whether to arrange a site visit.

Capture the ordinary route and the exceptions

The ordinary route shows repeated work. Exceptions show where an automated assistant could make a wrong assumption.

Note what happens when a caller is outside the service area, when information is missing or when a request needs professional judgement. Also record what happens out of hours and who checks the process when the usual owner is unavailable.

A simple table or written sequence is enough:

• where the request starts
• what information is collected
• which system or document is updated
• who makes the next decision
• how the customer is told what happens next
• where the process can stop or go another way

This map often reveals that the hardest part is deciding who owns the next action and where the latest information should live.

Step 3: separate repeatable work from judgement

Divide the process into tasks that follow an agreed pattern and decisions that need a person.

An assistant may be able to collect details, classify a request, draft a response, summarise a conversation or create a reminder. It may also use approved information to answer a routine question. The exact capability depends on the systems and checks around it.

Human judgement is more important when the process involves a complaint, sensitive personal information, a professional opinion, a safety concern, a financial commitment or a promise to a customer. These boundaries should be written down rather than left to the assistant to infer.

Make the handoff explicit

For each part of the workflow, ask:

• Can the assistant complete this step using information the business has approved?
• Does a person need to review the result before it is sent or acted on?
• What should happen when the request does not match the normal route?

For example, an assistant could collect a postcode and a description of a roofing enquiry, then prepare a summary for review. It should not decide that the work is safe, calculate a quote without an agreed method or promise an unconfirmed visit.

The handoff needs an owner. “Someone will check it” is not a workflow. Name the role or person responsible, the place where the summary will appear and the point by which it should be reviewed according to the business’s normal practice.

Step 4: check the information and systems involved

List the systems used in the chosen process and check whether they contain the details the next step needs.

This could include an email inbox, phone system, website form, calendar, customer record, spreadsheet or booking tool. Focus on the systems the selected workflow touches.

Ask what can be accessed and changed

For each system, note what the assistant would need to read, create or update. An enquiry workflow may need to read a form submission, create a task and send a summary. A booking workflow may need to check availability, but that does not mean it should confirm an appointment without a defined rule.

Also check whether the records are consistent. If names, addresses or job references differ between systems, automation may pass on the inconsistency rather than solve it. A short clean-up or clearer form may be a better first step.

Keep data collection proportionate

Only collect information the workflow needs. Extra questions make a form or call longer. Consider who should have access, how long information needs to be kept and how a customer can reach a person.

Businesses should take appropriate advice for their own legal and regulatory responsibilities, particularly where personal, health or financial information is involved. An audit is not a substitute for that advice.

Step 5: define a safe first test

Turn the audit into a small test with a clear boundary. Choose one route, write the approved information and decide what the assistant can do, suggest and when it must stop.

Test ordinary examples as well as awkward ones: an incomplete enquiry, a request outside the service area, an existing customer, an urgent-sounding message and a question that needs a person. Review whether the details are useful, the handoff is clear and any wording could be understood as a promise.

Decide what to observe

Define what you want to learn from the test. You may want to see whether the team receives the information it needs, staff can find the handoff, customers know what happens next or the workflow creates unnecessary questions.

The observations can lead to a decision to continue, revise the process or leave it manual. A narrow audit is useful when it helps the business avoid automating an unclear or unsuitable process.

What a useful audit should leave you with

At the end of the five steps, you should have:

• one process with a defined starting point and outcome
• a map of the current route and its exceptions
• a distinction between repeatable tasks and human decisions
• a list of relevant systems and information needs
• a bounded test with an owner and review points

That is enough to have a grounded conversation about whether AI automation fits. It also gives you a better basis for comparing tools, because you can assess them against a real workflow rather than a general promise.

Start with the process, then choose the technology

The best first automation is often not the most impressive demonstration. It is a small, understandable improvement to a process the team already knows. A person should remain responsible for decisions that require judgement, and the assistant should have a clear route for uncertainty and exceptions.

Amoskalets helps UK small businesses examine practical AI automation opportunities. An AI Automation Audit starts with one process, maps how it works now and identifies a sensible next step, including where automation may not be appropriate.

You can find out more at amoskalets.com.