GuideWorking better
What to automate first in a small business
Start with a task you can describe, measure and stop. Work out whether the time saved will cover the checking and maintenance it creates.
The quick answer
Good first candidates include routing a form to the right person, creating an internal follow-up task and copying agreed fields between systems. The input and expected action are usually easier to define than an automatic quote or complaint decision.
Write the process down before choosing a tool. If the team cannot agree what should happen manually, software will not settle the disagreement.
On this page
- The quick answer
- Find your starting point
- Choose a task with a clear finish
- Write the instructions before choosing software
- Choose rules or AI for the actual task
- Work out whether the saving is worthwhile
- Plan for a failed connection
- Test more than the ideal case
- Trial it with a clear stop rule
- Questions to put in the supplier brief
- Bring one process to the conversation
Find your starting point
| The problem | First automation to consider | Keep a person responsible for |
|---|---|---|
| Enquiries are lost between inboxes | Create a task for the appropriate team from one controlled entry point | Checking exceptions and confirming ownership |
| Staff repeatedly type the same acknowledgement | Send a short receipt message after the enquiry has been accepted | The substantive response and any service promise |
| Follow-ups depend on memory | Create an internal reminder after an agreed period | Deciding whether and how to contact the customer |
| People copy the same details between systems | Transfer a small set of validated fields | Resolving conflicting records |
| Many requests need interpretation | Prepare a suggested category or draft for review | Approving the action before it affects a customer |
A normal rule can be enough. You do not need an AI system to send a known form type to a known person.
Choose a task with a clear finish
Finish this sentence: “When ___ happens, the system should ___, unless ___, in which case ___ takes over.” If you cannot fill in the exceptions, the first job is to agree the process.
Before committing, ask whether the task happens often enough to justify maintaining the connection. A rare exception with little administrative cost may be easier to handle manually.
Write the instructions before choosing software
| Decision | Instruction |
|---|---|
| Trigger | A valid website enquiry has been accepted |
| Required information | Submission reference, selected service, message and reply details |
| Routing | Match the selected service to a named member of the booking team |
| Action | Create one task containing the enquiry details |
| Missing or unknown information | Send the request to a manual review queue |
| Duplicate event | Reuse the original submission reference; do not create a second task |
| Reminder | Notify the owner if the task is still unanswered after the business's agreed interval |
| Completion | Record who responded and stop the reminder |
| Failure | Keep the original request available and alert the owner |
| Pause | Allow the owner to disable the workflow and handle requests manually |
A reminder needs a cancellation rule as well as a start rule. If the customer has already received a reply, the workflow should not continue behaving as though the request is unanswered.
Choose rules or AI for the actual task
Use a defined rule when the inputs and action are predictable.
A service selected from a fixed list can route to a named team. An order reference can link related records.
Consider an AI-assisted step when interpretation is useful.
A long enquiry might be summarised into a draft for a member of staff. The original message should remain available to that reviewer.
Keep consequential decisions under explicit control.
A suggestion should not silently become a binding quote, a refund decision, a promise of emergency attendance or a confirmed appointment.
Work out whether the saving is worthwhile
| Weekly work | Minutes |
|---|---|
| Before automation: 25 enquiries × 4 minutes to route and record each | 100 |
| After automation: checking the task list | 20 |
| After automation: correcting exceptions and maintaining the workflow | 20 |
| Time released: 100 − 20 − 20 | 60 |
That releases one hour a week under these assumptions. Compare its value with the setup cost and recurring software fees. Count the time spent checking failed tasks; it belongs in the calculation.
At only ten enquiries a week, the same four-minute manual task takes 40 minutes. If the checks and maintenance still take 40 minutes, there is no time saving. Improving a template or assigning one inbox owner may be the better first step.
Time released is not automatically a cash saving. It becomes useful when staff can spend it on work the business needs, or when it actually reduces a cost.
Plan for a failed connection
If a task cannot be created in the receiving system, where does the original enquiry remain and who sees the failure? Agree that route before launch. Retrying the same request should not create a second customer task or send a second acknowledgement.
Keep access limited to the systems and records the workflow actually needs. Avoid copying a whole customer history into a tool when the task only requires a reference and service selection. Agree which records are retained and who can inspect them before connecting systems.
For outbound messages, define the recipient and purpose separately. Confirming receipt of an enquiry does not mean the person requested promotional follow-ups.
Test more than the ideal case
Before enabling a workflow for customers, use controlled test data to check:
Test customer-facing messages separately from internal tasks. A successful internal action does not demonstrate that an external message reached an inbox.
Trial it with a clear stop rule
For a manageable trial, have the owner compare the first 20 eligible requests with the tasks created. Check the recipient, key details, duplicates and exceptions. Twenty is a suggested review batch, not proof of reliability; a rare but important exception needs its own test.
Pause the affected action if it sends to the wrong person, loses a request or produces duplicate customer messages. Fix the cause and repeat the relevant checks before resuming. Keep the manual process available during the trial.
Questions to put in the supplier brief
Who maintains it?
Ask who investigates failures, updates a changed connection and pays for that work.
What happens if we change tools?
Ask what can be exported, which subscriptions are required and how the workflow can be stopped without losing incoming requests.
What may it send or change without approval?
List the permitted actions. A draft reply, a confirmed appointment and a quoted price need different controls.
Bring one process to the conversation
Write down one repetitive task, how often it occurs, which tools it touches and who currently finishes it.
Discuss an automation with Ascent using that example, or read the business automation service scope.