What should a small business automate first?

1. Find repeated manual work

For a few days, note activities involving copied information, similar messages or repeated status checks. Examples to investigate include entering enquiries into a CRM, notifying staff about new jobs and preparing summaries.

Describe the trigger, data source and required result. ‘Improve sales’ is a goal, not yet a process. ‘Create a record from each website enquiry and assign an owner’ is a scope that can be examined.

2. Compare frequency, time and exceptions

A daily task may be a better starting point than a rare, complex report. Measure frequency and time per case. Find out how often individual judgement is required.

Choose a process with available inputs and a result that can be checked. Where individual decisions are necessary, automation can prepare information rather than make the decision.

• How often is the task performed?
• How long does a typical case take?
• What exceptions occur?
• What happens if the output is wrong?

3. Compare benefits with total costs

An illustrative example: 80 monthly enquiries requiring four minutes of data entry each amount to 320 minutes, or five hours and 20 minutes. This is potentially affected work, not guaranteed time saved. Review, exceptions and maintenance remain relevant.

Compare implementation and tool costs with the value of time recovered and fewer mistakes. Sometimes a better form or shared job list is enough.

4. Plan for failure

Connecting systems is only part of the solution. Define what happens when data is missing, a submission is duplicated, a system is unavailable or permissions change. Who notices and follows up?

Include error notifications, history checks and manual recovery. Retries should not create duplicate records or send the same message again.

5. Use AI for a specific need

Moving form data into a spreadsheet can usually follow fixed rules. A language model may help summarise free text or suggest an enquiry category, but the quality of its output needs evaluation.

Test typical and difficult examples and define when a person reviews the result. A few successful demonstrations do not establish reliable decision-making.

6. Start with one workflow

An example first scope: create an enquiry record, assign an owner and send a notification. This is an illustrative scenario, not a claim about a completed client project. Feasibility depends on available integrations and tool plans.

Record response time, manual steps and error frequency before launch. Compare the same measures afterwards, accounting for changes in workload. Then select the next process.