Business process automation works best when you start with the task that costs you the most hours, happens most often and follows the same steps every time. For most small businesses that means a short list: replying to new enquiries, following up quotes, sending reminders, and typing the same details into two systems. Rank your tasks on three measures, pick the top one, and automate only that until it is running cleanly.
Start with a list of what actually costs you time
Most owners can name the job they hate, but that is not always the job that costs the most. Before you choose anything, spend one week writing down every repeated task that someone in the business does by hand. Use a notes app or a sheet. Ask the people doing the work, because the owner often does not see the small jobs.
For each task, write four things:
- What starts it (an enquiry arrives, a job finishes, a month ends).
- What the person does, step by step.
- How long it takes each time.
- How many times a week it happens.
You will end up with ten to thirty rows. That is enough to work with. You are not trying to map the whole business, only to find the few tasks where automation could pay.
Three measures that rank a task
Give every task a score from 1 to 3 on each of these. The task with the highest total goes first.
- Hours lost. Minutes per time, multiplied by times per week. A five minute job done forty times a week is more than three hours. A two hour job done once a quarter is not.
- Cost of getting it wrong or late. A missed follow-up on a large quote costs far more than a late internal report. Think about money lost, customers lost and rework.
- How steady the steps are. If the task is done the same way each time, it can be automated. If every case needs a judgement call, it cannot be, at least not yet.
The third measure is the one people skip. A task that eats hours but changes every time is a poor first choice, because you will spend your time handling exceptions instead of saving time.
Keep the scoring rough. You are not building a business case yet, only deciding the order. If two tasks tie, pick the one nearer the money: the task that sits between an enquiry and a signed job beats the task that sits between a job and a filing cabinet. Ask the people who do the work to check your scores too, because they know which tasks carry hidden steps and which ones only look short on paper.
A worked example of business process automation scoring
This is an example with made-up numbers, so swap in your own. Say a small building and renovation business writes down these five tasks.
| Task | Time and frequency | Cost of a miss | Steady steps? |
|---|---|---|---|
| Replying to new website enquiries | 10 min, 15 a week | High, a lost job | Mostly |
| Following up sent quotes | 5 min, 12 a week | High | Yes |
| Typing job details into the accounting system | 8 min, 10 a week | Medium, wrong invoices | Yes |
| Weekly report to the owner | 90 min, once a week | Low | Yes |
| Writing each custom quote | 3 hours, 4 a week | High | No, every job differs |
Do the sums. Enquiry replies come to 150 minutes a week. Quote follow-ups come to 60 minutes. Re-typing job details is 80 minutes. The weekly report is 90 minutes. Writing custom quotes is 12 hours, but it is the one task where the steps are not steady, so it stays with a person.
The winner here is not the biggest block of hours. It is the enquiry reply and the quote follow-up, because a miss costs a job and the steps are close to identical each time. The report is steady and takes time, but a late report costs little, so it goes later.
Good first candidates for small business automation
If your list is thin, these tasks suit most service businesses because they are triggered by an event, follow clear rules and carry a cost when missed.
- First reply to a new enquiry. A form or call arrives, the person gets a confirmation and a useful question, and the enquiry lands in your CRM with an owner. See our guide on how fast to reply to an enquiry.
- Quote follow-up. A quote is sent, and the system prompts a follow-up on day two, day five and day ten unless the customer has replied. The detail is in how builders follow up quotes.
- Reminders. Appointment, payment and renewal reminders go out on a schedule, so nobody has to remember them.
- Moving data between systems. Whenever someone copies details from one place to another, the copy can be automatic.
- Routine reports. A weekly summary that pulls from the same sources each time.
What to leave alone for now
Some tasks look attractive and are poor first projects:
- Anything that is broken by hand. If the manual process is unclear or people do it three different ways, automating it makes the confusion run faster. Fix the process first.
- Tasks with heavy judgement. Pricing a custom job, handling a complaint, deciding whether to take on a difficult client. Automate the preparation around them and leave the decision to a person.
- Rare tasks. If it happens twice a year, the build time will never come back.
- Anything touching money or legal records without a check. Automate the draft or the reminder. Let a person approve what goes out.
Write the manual process down before you build
Once you have picked one task, write its steps on a single page. Name the trigger, each action, who does it, and what a good result looks like. Then run it by hand for two weeks following the page exactly. You will find gaps: a field that is sometimes empty, a customer type that needs a different path, a step that only one person knows.
This step feels slow and saves the most time later. Automation that skips it tends to fail on the first unusual case. If the process involves several systems, our guide to what a webhook is explains how one system tells another that something has happened.
Build the smallest useful version, with a check
Do not automate the whole task at once. Automate the first two or three steps and put a person on the rest. For quote follow-up, that might be: the system reminds the right person on day two with the customer details and a draft message, and the person sends it. Once that runs reliably, you can let the system send the message itself.
For every automation, decide the check before you switch it on:
- What does a person look at? A daily list of what ran, or a weekly count compared with the CRM.
- What counts as a failure? An enquiry with no owner after an hour, a reminder that did not send, a duplicate record.
- Who is told? Name one person rather than a shared inbox.
Our guide on why automations break covers this in more detail.
When to bring in help
Many first automations can be built with the tools you already pay for, such as the automation features in your CRM or booking system. If that covers it, use it. It costs less and one fewer thing needs looking after. Outside help makes sense when the task crosses several systems, when it must keep working without anyone watching it, or when you have no one with the time to look after it. CentriWeb does this through automation work, starting with the task that costs the business most.
Measure it after a month
After a month, compare against your list. Is the task taking the time you expected it to save? Did anything slip through? Did the people involved find it easier or more awkward? If the answer is good, move to the next row. If it is not, fix this one before adding another. Two automations that run well beat six that nobody trusts. To work out whether a project is worth the build cost, see our guide to calculating automation ROI.