Which processes to automate first: the repeat · volume · rules test

The situation

Every company has the same three hours a day that vanish: copying data from a form into a spreadsheet, sending the same "we received your order" message, calling customers to remind them about an invoice, building the Monday report from four sources. None of it is your work. It is the glue between your systems, applied by hand.

This guide is about choosing what to automate first — because the order decides whether in three months you have a system that runs itself or an abandoned project.

How you choose: the test and the map

The test: repeat, volume, rules

A process deserves to be automated first if it passes all three:

1. Repeat. It is done the same way every time. If every time is "it depends", it is not a process yet — it is a judgement. Judgements get automated last, or never.
2. Volume. It happens often enough for the time to matter: daily or several times a day. Something done once a month in 20 minutes is not worth the effort before the others.
3. Clear rules. You can write it down: "if X, then Y". If the description needs "and use your judgement", clarify the rule first.

Score each process 1 to 3 on each criterion. Anything scoring 8–9 goes first.

The one-page map

Before any tool, write the process on a single page:

• Trigger: what starts it (form submitted, email received, fixed time, status changed).
• Steps: what happens, in order, with which system at each step.
• Data: what information passes from one step to the next (name, phone, amount, date).
• Exceptions: what happens when a field is missing, when the customer does not reply, when a system is down.
• Outcome: how you know it finished well. Who is notified.

If it does not fit on one page, it is two processes. If under "exceptions" you write "don't know", you have found what to fix first — on paper.

Quick wins that work almost everywhere

• Lead → CRM → WhatsApp notification. The website form creates the contact in the CRM, with its source (campaign, page), and sends the team a message with name and phone within 10 seconds. Speed of response is among the biggest factors in converting a lead — and the easiest to automate.
• Invoice reminders. Three days before the due date, on the due date, seven days after. Three messages written once, sent forever. Cash flow improves without anyone making a call.
• Review requests. Two or three days after delivery or a visit, a message with a direct link to your Google profile. Reviews grow steadily without you remembering.
• The Monday report. Sales, leads, ad spend, traffic — in an automatic email, same numbers in the same format, every Monday at 8:00. Twenty minutes a week per person, returned.
• Confirmations and statuses. "We received your order", "your parcel has shipped", "you have an appointment tomorrow at 10:00". Every message sent automatically is a phone call you no longer receive.

Which tools: platforms or code

The simple rule: start on a platform for speed. When an automation becomes critical for money or customers, move it to code, with tests and a log. Some platforms can also be self-hosted, which matters when data must not leave the company.

The classic mistake: automating a broken process

A bad manual process is slow and visible. A bad automated process is fast and invisible. Fix it on paper first.

How to measure hours saved, honestly

The honest method:

1. Measure before. For one week, note how many times the process runs and how long one run takes. Do not estimate — time five runs and average them.
2. Include all the time. Not just the three minutes of copying data; also the two minutes of finding the email, and the four of fixing yesterday's mistake.
3. Subtract the new time. Automation has a cost too: checking exceptions, repairing it when it breaks. Estimate it and subtract it.
4. Check after 30 days. With the real number of runs, not the promised one.

Hours saved become value only if someone does something else with them. Decide what in advance.