Translated from the Dutch article. The original publication date is retained.
Where do you start with automation? The answer is rarely the biggest process. Look for a task that returns every week and needs little changing judgement.
Question 1: does it come back every week?
Repetition makes costs and benefits easier to compare. A repeatedly retyped quote may be a candidate. An occasional task can also be worth automating, but needs a different assessment. First record what recurs and how much work it takes.
Question 2: are the steps always the same?
A system does what you teach it. Tasks with fixed steps work well: enquiry comes in, copy the details, send a confirmation. Tasks that need a judgement call every time, you leave with people.
Question 3: what happens when it goes wrong?
Start with work where a mistake is easy to put right. A wrong confirmation email is annoying. A wrong invoice to a major customer is worse. Build in an approval step there, or start somewhere else.
Three tasks that almost always make a good start
- Quote follow-up: after three days without a reply, a short email goes out automatically.
- Sorting enquiries: a form comes in, the system fills your CRM and sends a confirmation.
- Customer questions out of hours: a chatbot answers what it knows and passes on the rest.
What to leave alone
Anything where your customer expects a human. A complaint, a large project, bad news. That calls for a name and a phone number, not a system.
Pick one task. Build it, measure for a month, and only then look further. That way you know it works before you invest more.
Which task should I automate first?
Choose a recurring task with fixed steps where mistakes are easy to correct. Record the current way of working and desired result before selecting a solution.
Do I need to buy new software to automate?
First check what existing tools can do. Whether a new integration or another system is needed depends on the task, data and permissions. Assess that before buying.
How long does the first automation take?
That depends on scope, data, integrations and required checks. Discuss those first, then record timing and acceptance. A general article does not promise a project timeline.
