Where should a small business start with process automation?

In short

Start with one process that repeats often, always looks the same and takes the most time. Work out how many hours a year it costs, map it step by step, automate only the repetitive steps and check the effect before taking on the next one.

Key points
  • The best first candidate is frequent, repetitive and based on digital data.
  • Before you build anything, count the time: minutes times repetitions times people.
  • Automate steps, not the whole process. Decisions stay with people.
  • A good automation reports an error loudly instead of quietly stopping.

Which processes can be automated?

The best candidates meet four conditions:

  • they repeat often, for example daily or weekly,
  • they run the same way every time,
  • they rely on digital data: emails, forms, spreadsheets,
  • they have clear rules that can be written down.
Process in a small businessWhat can be automatedWhat stays with people
Enquiries from the website formSaving to a spreadsheet or CRM, notifying the right person, a confirmation for the clientThe reply and the quote
Orders from emailsReading the data from the message, creating the order, a reminder about missing itemsExceptions and complaints
Purchase invoicesDownloading, naming, passing to the accountant, matching to paymentsApproving the expense
Deadlines and remindersReminders by email or text message, escalation after the deadlineA conversation when someone doesn't respond
Weekly reportsCollecting data from several sources and sending the summaryConclusions from the report

How much time manual work really takes

Manual tasks are invisible because each one takes a moment. Only multiplied out do they show their scale. Enter your numbers:

What manual work costsCalculator
…hours a month
…hours a year
…working days a year
…a year (cost)

I count 46 working weeks a year and an 8-hour day. It's an estimate on your numbers, not a promise of savings.

Tip

Count honestly: enter the time the task really takes, including switching between programs, not the ideal time. The switching usually eats the most.

How to choose the first process

Ask three questions about each candidate process: how often it repeats, how long it takes each time and what happens when someone makes a mistake. The winner is the one that is frequent, time-consuming and where mistakes are costly.

The first process doesn't have to be the biggest. It matters more that the effect shows quickly: then it's easier to judge whether automation pays off and easier to win the team over to the next changes.

A five-step plan

  1. Map the process the way it really runs

    Not the way it should. Write down every step, who does it and in which program. Best of all, watch the person who does it every day.

  2. Mark the repetitive steps

    Only the steps that always look the same go to automation. Steps that need judgement stay.

  3. Check what your tools allow

    Data export, integrations, APIs, webhooks. It often turns out the programs can already talk to each other, nobody just switched it on.

  4. Build and test on test data

    Including the error paths: what if the email has no order number, and what if the server doesn't respond.

  5. Launch and watch for a few weeks

    Only when the first process runs steadily do you take on the next one.

What is better left unautomated

  • decisions that need human judgement,
  • processes that keep changing,
  • tasks that happen a few times a year,
  • a mess: if the process is chaotic, automation only speeds up the chaos.
Caution

The most common mistake is automating a process nobody has tidied up first. Agree on one version of the process first, then automate it.

A ready-made tool or a custom solution?

Ready-made tools for connecting apps (n8n, Make, Zapier) are enough for simple flows between popular programs. A custom solution makes sense when the process has unusual rules, the data has to stay in the company or the ready-made tool needs too many workarounds. A comparison of the three tools is in a separate guide.

Terms from this guide

Process automation

Replacing repetitive, manual steps with a program that performs them by itself according to agreed rules. Decisions usually stay with people.

Questions and answers

How long does the first automation take?

It depends on the number of steps and systems to connect. A simple flow between two popular programs is usually days, not weeks. It's worth choosing the first process so the effect shows quickly.

Does automation require changing programs?

Usually not. First you check what the current tools allow, and often it's enough to connect them.

What if the automation breaks?

A well-designed automation reports the error instead of quietly stopping. It's one of the first requirements I agree on.

Will automation take people's jobs?

In a small business it usually takes the boring part of the job: retyping and keeping track of deadlines. The time goes back to talking to clients and to tasks that can't be automated.

The service related to this guide

Business process automation

Describe the problem

Question 1 of 5

What would you most like to improve?

Pick the closest one. It doesn't have to fit perfectly.

First summary

This is a first suggestion based on a few answers, not a diagnosis. Nothing is saved until you send the message.