Which tasks should a small business automate first?
What to automate first in a small business: the tasks that happen often, always follow the same rule and do little harm if one goes wrong. To automate a task means to let software do it by itself. A task that passes all three tests soon saves time. A task that fails one of them should wait, however annoying it is.
Why the most annoying task is often the wrong start
Most teams want to hand over the job they dislike most. Often that is a rare and messy one, such as the yearly stock count or a difficult customer complaint. Rare jobs save little time. Messy jobs are hard to describe to software. The best first candidates are boring: small, frequent and always the same.
Three questions per task
- How much time does it take per month? Count how often it happens and how long it takes each time.
- Is there a clear rule? Can you describe the task as "when this happens, do that", without the word "usually"?
- What happens if it goes wrong once? A small correction, an awkward email or lost money?
Sort your tasks by time per month. Then cross out every task where the rule is unclear or a mistake is expensive. The task now at the top is your first one.
A worked example
The numbers below are made up to show the method. Replace them with one week of your own counting.
| Task | Time per month | Rule and risk | Verdict |
|---|---|---|---|
| Copy website enquiries into the contact list | 5 hours | Clear rule, low risk | First |
| Set up a project after a customer says yes | 4 hours | Clear rule, medium risk | Second |
| Remind customers of unpaid invoices | About 3 hours | Clear rule, low risk | Third |
| Answer customer complaints | 5 hours | No clear rule, high risk | Not yet |
Complaints take as much time as enquiries. But every complaint is different, and the answer goes to a customer. So they stay with a person for now.
Tasks that usually come out on top
- Taking in requests. A form on your website saves the request directly, so nobody retypes an email.
- Handing out work. Every new request gets a responsible person at once.
- Reminders. A due date passes, and the right person hears about it.
- Copying between lists. A customer says yes, and the project is set up with the details already filled in.
Tasks to leave for later
- Anything done less than once a month.
- Ways of working that still change every few weeks. Let them settle first.
- Payments and messages to customers, until the simpler tasks have run without surprises.
Start with one task and watch it for two weeks
- Count the task by hand for one week, so you know where you start.
- Automate only that one task.
- Check every result for two weeks.
- Fix the cases the rule did not cover.
- Then take the next task from your list.
One automated task that the team trusts is worth more than five that people check by hand anyway.
How Worknano handles this
The tasks at the top of most lists need two things: a form and a workflow, which is a rule that carries out the next steps by itself. Worknano has both in the same workspace. A filled-in form becomes a record straight away. For example, a contact form feeds your list of new sales contacts, and a job application fills a candidate profile. A workflow then starts when a record is created, a field changes, a status moves or a set time arrives. It can create records, update fields, assign people and send email. Forms and workflows use the same data, so there is nothing to connect before the first automation runs.
Create a free workspace and automate the task at the top of your list.