A first-month automation checklist for a UK small business

Week one: understand where the work goes

The first week is for observation. Before choosing a tool, write down the recurring work that takes place around customers, enquiries and administration.

List the repeated tasks

Make a simple list of the tasks you or your team carry out repeatedly. Include work that happens by email, phone, website form, messaging app, spreadsheet and calendar.

Examples might include replying to common questions, copying an enquiry into a spreadsheet, checking whether a booking has been confirmed, preparing a draft quote, sending a follow-up or asking for missing details.

Do not judge the tasks yet. A job that takes only a few minutes can still be a useful candidate if it happens many times or is easy to forget.

Follow one request from start to finish

Choose a recent enquiry, booking or customer message and trace what happened next. Note where it arrived, who saw it, what information was missing, which system was updated and how the next action was assigned.

Look for handoffs. A handoff happens whenever work moves from a customer to a team member, from email to a spreadsheet or from one colleague to another. These points often create delays because responsibility is not visible.

Write down the exceptions as well as the normal path. A workflow that works for a straightforward enquiry may need a different route for an existing customer, a complaint, an urgent request or someone outside the service area.

Record the information the process needs

For the workflow you are studying, list the details required before the next step can happen. A cleaning enquiry might need the property type, location and requested service. A trades business might need a description of the job and a preferred contact time.

This list will help you decide what an assistant or automation should ask for.

Week two: choose one safe starting point

In the second week, turn your observations into a small, testable project. The aim is not to automate the most impressive task. It is to select a process with a clear boundary and an owner.

Choose a repeated, rule-based step

A good first candidate usually has a recognisable beginning, a limited number of paths and a next action that can be described clearly. It might be sorting new enquiries, preparing a summary, sending an internal notification or drafting a response for review.

Be cautious with work that depends on professional judgement, sensitive information, an unusual customer situation or a decision about money. Those areas may still benefit from support, but a person should remain responsible for the decision.

Define what the automation can and cannot do

Write the boundary clearly. For example:

• It can collect a name, postcode and description of a new enquiry.
• It can identify whether the request is about a listed service.
• It can prepare a summary for the business owner.
• It can suggest a reply using approved information.
• It cannot confirm a booking, make a diagnosis or approve a quote.

This distinction matters whether you are using an AI assistant, a form, an integration or a simple reminder. A system should not imply that a person has made a decision when nobody has reviewed the request.

Decide where a person takes over

Set a clear handoff for requests that are urgent, sensitive, unclear or outside the normal workflow. Decide who receives the handoff and where it appears. An alert that nobody owns is not a useful automation.

Decide whether the first project covers one channel or several. Keeping the scope narrow makes it easier to see what is working.

Check the data and access involved

Before connecting a new tool, list what information it will receive and which people or systems can access it. Collect only what the workflow needs, and check the relevant policies and agreements before moving customer records, documents or messages between services.

Week three: build and test the smallest useful version

The third week is for configuration. Start with the version that supports one workflow and one clear handoff.

Write the approved information

Prepare the answers, instructions and templates the system may use. Include opening hours, service areas, the types of work the business accepts and the next steps customers can expect. Keep the wording accurate and easy to review.

Avoid giving an AI assistant a vague instruction such as “handle customer enquiries”. Explain what information it should collect, what it should do with that information and when it must stop. If an answer is not available in the approved material, the safe route may be to say that a team member will review the question.

Test ordinary and awkward examples

Use examples from the first week, with personal details removed where appropriate. Test a straightforward request, an incomplete request, an existing customer, a request outside the service area and a message needing human judgement.

Check whether the system:

• asks for the information the next person needs
• places the result in the agreed location
• keeps request types separate
• avoids inventing availability, prices or policies
• makes the human handoff clear

Read the full output, not just the successful examples. A polished sentence is not enough if the summary leaves out the postcode or sends a complaint to the ordinary queue.

Keep review in the loop

For an early version, draft-first is often easier to control than send-first. Let a person approve a message or confirm a booking before the system takes an external action.

When the owner changes a draft, note why. The correction may show that the instructions need updating or that the task should stay manual.

Week four: use it carefully and review the process

The fourth week is for a limited live trial and review. Tell the team who owns the handoff and how to report a problem.

Review examples, not just activity counts

Look at a sample of completed interactions and ask whether the next step was clear. Did the right person receive the information? Were customers asked unnecessary questions? Did anyone need to correct an answer? Did the workflow create a new manual task that was harder than the old one?

You do not need to invent a return-on-investment figure. Review observed examples: what was easier to find, what was missed and what still needs a person.

Update the boundary

You may discover that the first workflow is too broad. Narrow it if necessary. Add routes for cancellations, complaints or urgent messages only when the business knows who will handle them.

If the automation behaves unpredictably or creates more checking than it removes, pause the live use and return to the workflow map. That is a valid result. The first month is for learning whether the process is suitable, not for forcing every task into a tool.

A simple checklist for the end of the month

By the end of the first month, you should be able to answer:

• Which workflow did we examine?
• Which details does the next person need?
• What can the automation do?
• What must remain with a person?
• Who reviews the output?

If those answers are unclear, more process mapping may be useful before adding another tool. If they are clear, decide whether to refine this workflow, extend it to another channel or leave it at its current boundary.

The best first month gives a small business a reliable understanding of where automation can support the team, where human judgement belongs and what should happen next.

Amoskalets helps UK small businesses examine practical AI automation opportunities, starting with one real workflow and the decisions that should remain with a person. Find out more at amoskalets.com.