Start with the copy-paste work
Ask each team one question: “What do you do every day or every week that feels like copying from one place to another?”
The answers often look similar. Leads copied from the website, IndiaMART or Meta ads into a CRM or sheet. Payment reminders for overdue invoices. Purchase bills typed into Tally. A daily sales report stitched from three sheets and sent on WhatsApp. Customers chased for documents. Order details retyped into a courier portal.
Write every answer down. Judge them later.
Measure before you automate
For each task, note how often it happens, how long one takes (time a few real examples), who does it, how often it goes wrong, and what a mistake costs: a lost sale, an angry customer, a tax problem.
That is your baseline. Without it, nobody can say whether the automation worked, and the first automation needs a visible win.
Score the candidates
Rate each task against these questions.
| Question | A good first candidate |
|---|---|
| How often does it happen? | Daily, or many times a week |
| Are the rules clear? | Two people would do it the same way |
| Is the input structured? | Mostly forms, spreadsheets or system records |
| How many systems does it touch? | Two or three |
| How bad is a mistake? | Low, or easy to catch and fix |
| Is there an owner? | One person who cares and will check it |
| Can you measure the result? | Yes, against the baseline |
Pick the task with the most good answers. It may not be the most exciting one on the list.
Five common starting points
Lead capture and acknowledgement is often the best first choice. Leads from every source land in one list, duplicates are merged by phone number, the lead gets an acknowledgement and sales gets a notification. Missed leads before and after are easy to count. For finding new prospects rather than handling inbound ones, MicroLead finds business leads from Google Maps listings, removes duplicates and scores them against an ideal customer profile.
We match on more than one field, never on a single one. Two businesses can share a phone number and one business can appear under several names, so a match has to agree on more than one thing before two records become one.
Payment reminders are close behind. Overdue invoices trigger reminders at set intervals with the invoice attached. Let the owner approve the wording and schedule, and measure days to collect.
A daily summary, compiled from the POS, accounts or CRM and sent to the owner each morning, is low risk and visible.
A document checklist compares what a customer uploaded against what’s required and asks for the missing items.
Appointment reminders go out before each booking, with a way to confirm or reschedule. On WhatsApp, reminders like these need approved templates (WhatsApp template rules).
For examples grouped by sector, such as clinics, hotels, real estate and logistics, see automation by industry.
Where AI helps
Plain rules are cheaper and more predictable. Use them whenever the input is already structured.
AI earns its place when the input is messy: reading purchase bills from PDFs and phone photos, sorting incoming emails into orders, complaints and quotation requests, pulling details from free-text enquiries, or drafting replies for a person to approve.
Keep a person in the loop at first. For example, AI reads the bill and fills the entry, and your accountant approves it before it posts. Once you’ve seen how accurate it is on your own documents, decide where review can be lighter.
What to leave for later
If the steps are unclear or everyone does the task differently, agree the process before automating it, or the automation just repeats the confusion faster. A task done once a month rarely repays the effort. Judgement-heavy work like pricing negotiations, hiring decisions and complaint resolution isn’t a first project. Payments, refunds and payroll changes should keep a human approval step. And a wrong message sent to your whole customer list is hard to take back, so bulk messaging waits until you trust the setup.
An automation nobody owns will break quietly. Before building, decide who gets alerted when it fails and what the fallback is; our integration guide covers this in detail (question 7).
After the first one works
Compare against the baseline after a few weeks. If it saved time or cut mistakes, move to the next task on your list. When you choose a platform to build on, our comparison of n8n, Zapier, Make and Activepieces may help. See also MicroFlow, our self-hosted workflow platform.