Automation

What business processes should you automate first?

Nicolas Blassel, Co-founder

Most firms that decide to "automate more" start in the wrong place. They pick the process that annoys the owner most, or the one a software demo made look easy, and three months later they have one complicated automation that nobody trusts. The processes to automate first should be chosen almost boringly: frequent, repetitive, rule-based work that already happens the same way every time.

The direct answer: automate first the handoffs where someone copies information from one system to another, many times a week, following rules they could write on a sticky note. In a 10 to 50 person firm that usually means new enquiries into the CRM, client onboarding steps, appointment reminders, document chasers and invoice preparation. Leave judgment calls, money movements and anything regulated for later.

Five questions that score any process

Score each candidate process from 1 to 3 on these five questions. Add the scores; anything at 12 or above is a strong first candidate.

  1. How often does it happen? Daily scores 3, weekly 2, monthly or less 1. Frequency is what turns minutes into hours.
  2. How long does it take each time? Count the full time, including switching between screens and checking. Over 10 minutes scores 3.
  3. Are the rules clear? If two staff members would do it the same way given the same input, score 3. If it depends on "it depends", score 1.
  4. Is the process stable? A process that has not changed in a year scores 3. One you are redesigning this quarter scores 1. Automating a process that is about to change means building it twice.
  5. What happens when it goes wrong? A late reminder email is cheap to fix and scores 3. A wrong invoice, a misfiled client document or a payment error is not, and scores 1.

The last question matters more than it looks. Your first automations are also how your team learns to trust automation. Start where a mistake is visible and easy to undo.

Here is one process scored, as an illustration only: the reminder email an accounting firm sends to clients who have not yet sent their bank statements.

QuestionAnswerScore
How often?Every day in busy periods3
How long each time?Checking the list, writing, sending: over 10 minutes3
Are the rules clear?Any two colleagues would chase the same way3
Is it stable?Same routine for years3
If it goes wrong?A late or duplicate reminder is easy to fix3
Total15

At 12 or above, it is a strong first candidate. Your own scores will differ, and that is the point of doing it on paper.

The processes to automate first in most firms

In accounting firms, the same handful of processes score well again and again: document chasers, onboarding steps, draft invoices. Law firms and recruitment firms find the same pattern with their own paperwork.

New enquiry to CRM

A web form, email or booking creates a contact and a follow-up task in your CRM or practice management system, and the right person gets notified. It runs daily, the rules are simple, and a missed lead is expensive.

Client onboarding steps

Once a client says yes, the same sequence follows: create the client file, generate the engagement letter, send it for e-signature, file the signed copy, set up the folder structure, add the client to billing. In a law firm it is the matter instead of the client file, in a recruitment firm the new client brief. Together the steps often take an hour per new client. Our guide to automating accounting firm client onboarding goes through them in order.

Appointment and deadline reminders

Reminders to clients before meetings, and internal reminders before filing dates or renewal dates. Low risk, high frequency, and directly reduces no-shows and last-minute scrambles.

Document collection chasers

Accounting firms chasing bank statements and year-end records, law firms waiting on signed forms, recruitment firms waiting on candidates' documents. An automation that checks what is missing and sends a polite, scheduled reminder removes some of the most tedious work in the office. Our guide to automating document collection from clients shows how.

Invoice preparation from completed work

Turning finished client work, closed matters or approved timesheets into draft invoices in your accounting system. Note the word "draft": let a person review and send, at least at first. Check what your native connectors already handle before you build anything.

Internal handoffs

A matter moves from intake to a fee earner, a file moves from preparer to reviewer, a patient moves from booking to clinician. A message with the right link at the right time replaces "did you see my email?" conversations.

What to leave alone for now

Some work looks repetitive but should not be on your first list:

  • Anything that moves money or touches client funds. Trust account entries, payment runs and refunds need controls and reconciliation designed in from the start. Check with your accountant before automating any part of them.
  • Decisions that need professional judgment. Conflict checks, clinical triage, legal or tax advice. Automation can gather the inputs and route them to the right person; it should not make the call.
  • Processes nobody agrees on. If three people do intake three different ways, agree on one way first. Automating a disputed process just hardens one version of it.
  • Rare processes. Something that happens four times a year rarely repays the build and maintenance time, however annoying it is.
  • Regulated data flows you have not reviewed. If health, financial or highly confidential client data would pass through a new tool, check with your compliance lead first.

How to run your first automation project

  1. List candidates for one week. Ask each team member to note every time they copy information from one place to another, and roughly how long it took.
  2. Score them with the five questions above and pick the top one or two. Resist doing five at once.
  3. Write the process down in plain steps: what triggers it, what must be true at the end, and the three most common exceptions (missing email, duplicate client, cancelled appointment).
  4. Decide the source of truth for each piece of data, so the automation never has two systems arguing about a client's address.
  5. Measure before and after. Time spent per week, errors caught, response time. A number makes the next automation easier to justify.
  6. Name an owner. Someone checks the error alerts and the output, and knows what to do when a connected app changes. Zapier emails Zap errors to the account's address by default, immediately or as an hourly summary (Zapier's help page on error notifications). Make emails you when an error is not handled and disables a scenario's schedule after repeated failed runs (Make's guide to errors and warnings). Make sure those emails reach the owner.

Signs you picked well

A good first automation is quickly forgotten. Staff stop mentioning the task, the error alerts are rare and understood, and people start suggesting the next candidate themselves. If instead the team is double-checking every record the automation creates, the process was not stable or the rules were not clear enough; fix that before building more.

How Flow Mesh helps

We are a small team of specialists who connect the software firms already use and take the repetitive work between those systems off their people. The audit comes first: picking the right first processes is part of our workflow audit, where we review the tools you pay for, give each a written recommendation (keep as is, switch on properly, merge or let go), identify the handoffs worth automating, and write the scope. If you want help with the build, we quote it in writing after the audit and build it in your own accounts as part of our workflow automation service. For a sense of the outcomes, in one law firm case about 40 hours a month came back.

Nicolas Blassel

About the author

Nicolas Blassel, Co-founder

Nicolas Blassel has worked on software and data systems since 2007, including defence, aerospace and Paris 2024. He runs Flow Mesh's French missions himself, from the first call to go-live, connecting the software firms already use and working inside their own accounts after an NDA.

CHECKLIST

The SaaS stack self-audit: 12 checks

The same questions our paid audit starts with. Work through them in an hour and see whether your stack is costing more than the subscriptions. We'll email you the checklist.

More articles

See all articles →