Watch where time goes during a working week
List tasks where someone copies data, searches for information, sends similar emails or reminds others to act. Ask the person doing the work what gets in their way. Follow the customer journey too: where are replies delayed, bookings left unconfirmed or enquiries lost? Describe a specific action, such as “I copy a website enquiry into a spreadsheet and send a confirmation.” “Sales” is too broad for a first automation.
Define the trigger, input and expected result
What starts the task? Where does the information come from, and where must it go? Who decides what happens when something is missing? A website enquiry might create a CRM record, send a confirmation and assign a follow-up task. Include exceptions such as an existing customer, a duplicate enquiry or missing contact details. If the current process is unclear, agree how it should work before building it.
Estimate volume and the share you can actually automate
Measure time per occurrence and the number of repetitions per month. An illustrative calculation: 10 minutes × 60 occurrences is 10 hours a month. If automation covers 70%, the estimated released time is 7 hours; review still takes time. These are example assumptions. Add several tasks to the calculator and compare monthly and yearly time value. Released hours can support customer work or development; they do not automatically reduce payroll.
Choose the first task by benefit, feasibility and risk
A useful first candidate happens often, uses accessible data and has a result you can clearly verify. Compare time saved, customer benefit, integration complexity and the consequences of an error. Capturing an enquiry and notifying the right person can be a starting point. Payments, pricing agreements and deleting records need more specific controls. Choose a bounded task that you can stop and continue manually if necessary.
Do you need an integration or AI?
If the rule is clear, a conventional automation may be enough: form data into a CRM, a confirmed booking into a calendar or a reminder triggered by a deadline. AI can help when the input is free-form text, a document or a message whose meaning needs interpretation. Define what AI may decide and when a person approves the result. Check your existing software’s capabilities first to avoid adding an unnecessary system.
Test one workflow and measure the result
Record the starting point: time spent, corrections and work waiting. Test normal cases and exceptions such as duplicate enquiries and a failed connection. Assign an owner and decide where failures will be noticed. Hoid ja Hool shows how bookings, customer records, notifications and invoice work can form one connected process. Your first step may be a small part of that. Use the checklist to assess readiness and the calculator to compare assumptions.
Try the automation readiness checklist ↗
Explore the related project ↗