Process automation in an SMB: where to start

Automation is no longer just for large companies. The tools are affordable and almost all the software an SMB uses (its CRM, its ERP, its email) can connect to other systems. What makes the difference isn't the technology but choosing well what to automate and in what order.

1. Take stock of what repeats

For a week, ask each person on the team to note the tasks they repeat: what they do, how often and how long it takes. You don't need stopwatch precision; reasonable estimates are enough.

Watch for these signs:

• Data typed into one system after seeing it in another.
• Emails almost always answered with the same text.
• Documents that get downloaded, renamed and filed.
• Follow-ups that depend on someone remembering.
• Reports put together by hand every week or month.

2. Put numbers on it

For each task, work out its monthly cost: hours per week × people × 4.33 weeks × cost per hour. With that figure you can compare very different tasks and, later, compare savings with the investment. The savings calculator does this sum for you.

3. Pick the first one with five criteria

A good first automation meets almost all of these points:

1. Volume: it repeats often and eats hours every week.
2. Clear rules: the path is almost always the same.
3. Digital data: the information is already in a system, an email or a PDF, not on paper.
4. Costly mistakes: when it fails, it costs money or clients.
5. Stability: the process doesn't change every month.

If a task meets all five, start with it. We explain it with worked numbers in which processes to automate first and how to calculate the return.

4. Map the process before automating it

Sit down with the person who does the work and map the process step by step, including its exceptions: what happens when a piece of data is missing, when the client doesn't exist or when the invoice comes in wrong. This exercise often reveals unnecessary steps, and it's worth removing them first.

5. Automate on top of your tools

You don't need to change software to get started. The normal approach is to connect the tools you already use through their APIs and an orchestrator such as n8n. Replacing a tool only pays off when it's clearly the bottleneck. If you're torn between orchestrators, compare n8n, Make and Zapier.

6. Decide what happens with exceptions

No automation resolves 100% of cases. Define from the start who receives the ones it can't resolve, through which channel and with what information. A well-built automation stops and flags; a badly built one guesses.

7. Measure afterwards

Compare hours and mistakes before and after. That measurement justifies the next automation and tells you whether the first one needs adjusting.

When the task needs judgement

If your stock-take shows that the heaviest tasks don't follow fixed rules (reading client emails with different requests, reviewing varied documents, deciding what to reply), what fits isn't classic automation but a digital employee. The differences are in digital employee, chatbot, RPA and AI agent: how they differ.

Summary

• Start with the process, not the tool.
• Measure what each repetitive task costs.
• Pick a small first automation with volume and clear rules.
• Simplify before automating.
• Define what happens with exceptions.
• Measure the result and grow from there.