You will be able to score any repetitive task by frequency, time per run and error cost, and rank tasks by payoff.
Most people pick their first automation the wrong way. They choose the task that annoys them most, spend a weekend wiring it up, and save four minutes a month. The annoyance was real, but it was never the expensive part of the week.
A better way to choose is to price each task before you touch any tool. Three numbers do most of the work. Frequency is how often the task happens: daily, weekly, or twenty times a day. Time per run is how long it takes you each time, including the switching cost of opening the right app, finding the right file and getting back to what you were doing. Error cost is what a mistake costs when it happens: a lost lead, a wrong invoice, an angry customer, an afternoon spent fixing it.
Multiply frequency by time per run and you get the hours the task takes over a month. Then add the error cost on top, because a task you do by hand at 6pm on a Friday is the one where you paste the wrong email address. A task that is rare but very costly to get wrong can be worth automating even if it only saves a few minutes, because the automation does it the same way every time.
Take a small tuition centre in Tampines. A parent fills in an enquiry form on the website. Someone on the team copies the details into a spreadsheet, replies to the parent with the timetable, and adds a reminder to call back in two days. Each enquiry takes about six minutes. At fifteen enquiries a week, that is an hour and a half every week, and when the centre is busy in January, replies slip by a day and some parents enrol elsewhere. The time is moderate, but the error cost is a lost student. That is a strong candidate.
Now compare a monthly report that the same centre owner builds from three spreadsheets. It takes forty minutes, once a month, and the owner checks it carefully because it goes to the landlord. It feels tedious, but the hours are low and the owner already catches the errors. Automating it would take longer to build and fix than it would ever save. Leave it for now.
There is a fourth question to ask before you build: is the task stable? If the steps change every week, or depend on a judgement call that only you can make, an automation will break or make the wrong call. Automations are good at tasks with the same inputs, the same steps and a clear finish. They are poor at tasks where the right action depends on reading the situation.
You will also notice that some tasks are slow because the process is messy, not because a person does them. A form that asks for the same information twice, or a spreadsheet with five tabs nobody uses, will still be messy after you automate it, only faster. Fix the process on paper first. Sometimes that alone saves most of the time.
This course uses tools such as Zapier, Make and n8n as examples, but the choice of tool comes later. The decision about what to automate does not depend on the tool, and it is the decision that decides whether the work pays off.
Your task: list ten things you do at work in a typical week that involve moving information from one place to another. For each one, write down how often it happens, roughly how many minutes it takes, and what a mistake would cost. Circle the two with the highest combined score. You will build one of them during this course.
List ten weekly tasks that move information between places, score each on frequency, minutes and error cost, and circle the top two.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).