What should a small business automate first?
Start with a task that repeats often, follows rules you can explain and has a manageable consequence if something goes wrong. Make sure someone can see failures and take over. The first project should be small enough that you can inspect its results.
Good candidates might include turning an enquiry into a callback task, preparing an internal report or scheduling approved reminders. Whether any of these fits your business depends on your data, tools and working process.
Record the work before choosing technology
For a working week, ask the people doing the admin to note repeated tasks. For each one, write down what starts it, what information they use, what they produce and where they need judgement.
Be specific. “Email is taking too long” is hard to improve. “Every website enquiry must be copied into the job system and assigned to the office manager” describes a process you can examine.
Use this task-selection worksheet
Complete these fields for each candidate:
- Trigger: the event that starts the work.
- Required inputs: the information needed, and where it comes from.
- Decision rules: what determines the next action.
- Finished result: what a person can inspect to confirm completion.
- Exceptions: missing data, conflicting instructions or unusual requests.
- Failure consequence: who is affected if the task is wrong, delayed or duplicated.
- Owner: the person responsible for reviewing exceptions.
- Current effort: time spent doing, checking and correcting the task.
If you cannot describe the decision rules, first improve the process with the team. Automating an unresolved disagreement about who should do what can make the confusion harder to see.
Choose between a built-in feature, automation and AI
A rule such as “create a task when this form is submitted” does not necessarily need an AI model. Check the tools you already pay for. For example, Xero provides invoice reminder controls. A native feature can remove an integration you would otherwise need to maintain.
AI is worth evaluating when the work involves variable language, such as drafting a summary from an enquiry. You still need a way to check accuracy and stop unsupported actions. Keep a draft for approval if errors would affect the customer.
A worked decision: enquiry intake
Imagine a fictional plumbing business copying website messages into its job system. The first version could create an unassigned enquiry containing the original message and notify the office. Staff would still decide whether to accept the work, quote or book.
That is a narrower project than automatically interpreting every request, promising a price and dispatching a technician. It gives the business a useful record while keeping the consequential decisions with someone who knows the context.
Possible acceptance checks are: an enquiry arrives once, contact details are preserved, missing fields are visible and a failed connection creates an alert. Add a check that resubmitting the same form does not silently create duplicate work.
Write a pilot agreement on one page
- Scope: name the task and explicitly list the actions it may take.
- Baseline: record current volume, time and common errors.
- Success: define the useful result and how you will check it.
- Review: name the person inspecting outputs and receiving failures.
- Stop: decide what would cause you to pause the pilot.
- Fallback: document how staff resume the manual process.
Set a review date that covers enough normal work to judge performance. There is no universal trial length that proves an automation is useful.
Measure the work left over
Compare manual effort before the pilot with the new effort required for review, corrections and maintenance. Separate faster processing from an actual reduction in staff workload. If employees now spend their time finding mistakes, the task needs redesign.
For a broader rollout, use our 90-day AI pilot planning guide. RightLink’s AI strategy service can help turn your task worksheet into a defined first project.