How to Automate Business Processes: What to Automate First
How to automate business processes in a small company: fix the process first, split rule-based steps from AI steps, and pick a first task that pays back.
To automate business processes, first fix the process: write down how it runs, cut the steps nobody needs and agree on one standard way of doing it. Then split the steps. Rule-based steps go to automation software, writing and sorting steps go to AI with a person checking, and decisions stay with people. Automate one process, measure it, and only then start the next.
My company Retos galimybės (opens in a new tab) builds process automation in Lithuania, next to AI training, websites and custom AI tools, and we use every tool in our own businesses first. In my company programmes the audit of how work runs takes one to two weeks and the first workflow goes live in month one. This post is the checklist I use in that audit.
Fix the process before you automate it
Taiichi Ohno, who built the Toyota Production System, said: "There can be no kaizen without a standard." The Lean Enterprise Institute adds that without a stable operation, teams "perform kaizen on top of chaos", and the gains vanish. Automation follows the same law. If three people handle a client request in three different ways, software will copy all three, and you will spend the next month fixing exceptions.
So the first job has no software in it:
- Draw the process as it runs today. How to do process mapping shows the method in one session.
- Mark every step that adds nothing for the client or the team: double entry, copy and paste between tools, approvals nobody reads.
- Agree on one standard version and write it as a checklist.
Only that checklist goes into automation.
How to automate business processes: three kinds of steps
Take the checklist and label each step.
| Kind of step | Example | Who does it |
|---|---|---|
| Fixed rule | Form arrives, create a CRM row, send a confirmation, notify the owner | Automation software |
| Language or sorting | Draft a reply, summarise a call, classify an email, extract fields from a PDF | AI, with a person checking |
| Judgement | Price, approve, refuse, anything with legal or client risk | A person |
The first row needs no AI at all. Many tools you already pay for, such as your CRM, accounting software or email platform, have built-in rules. A no-code connector such as Zapier, Make or n8n links the tools that don't talk to each other. Start there, because rule-based steps never invent anything.
The second row is where AI earns its place, and where it makes mistakes. AI models produce confident errors, so every AI step in a workflow ends with a person who checks the output before it reaches a client. Design the check into the workflow from day one.
The third row stays human. Automation can prepare the decision, collect the documents, draft the summary and set the reminder. A person decides.
What to automate first in a small business
A good first process passes four tests:
- It repeats. Every day or every week, with the same path most of the time.
- It has an owner. One person who does it now and wants it to get easier.
- It has a clear end. You can see when it is done and whether it went right.
- A mistake is cheap. It costs a correction. If a mistake could cost a client or a fine, pick another task.
Common first picks:
- Inbound requests: a form or email arrives, the details land in the CRM, AI drafts a first reply, a person sends it
- Documents and invoices: AI extracts the fields, automation files them, a person approves the payment
- Meeting notes: the call summary turns into tasks with owners and dates
- Recurring reports: an export becomes a monthly summary with the three changes a manager needs to see
Leave payroll, contracts and anything tied to a regulator for later, once the team trusts the first workflows.
Build it, then measure it
Before you switch anything on, write down two numbers for the process: how long one run takes and how many runs happen per week. Build the smallest version that works end to end, run it next to the old way for a week, and compare. If the owner saves time and the output holds up, switch over and document the new standard. If not, find the step that breaks and fix it before you add anything.
Then go back to your list and take the next process. Automation pays off as a series of small processes that each work, which is how implementing AI in a business works too.
Automation needs trained people
A workflow fails the day its owner goes on holiday and nobody else knows how it runs. Every automated process needs a short written description, a second person who can run it, and a team that knows where AI sits in it and what to check. That part is training, and it is the reason my programmes end with coaching until the team runs the workflows without me. The training side is in AI training for employees.
Find your first process
Tell me which task eats the most hours in your team. On a 30-minute call you hear whether automation, training or both will fix it. For companies in Lithuania, Retos galimybės builds the automation and trains the team. See my AI training page or book a call.
Questions and answers
How do you automate a business process?
Write down how the process runs today, remove the steps nobody needs, and agree on one standard way of doing it. Then split the steps: rule-based steps go to automation software, writing and sorting steps go to AI with a person checking, and decisions stay with people. Automate one process, measure it, then move to the next.
What is the difference between automation and AI?
Automation follows fixed rules: when a form arrives, create a row, send a confirmation, notify the owner. AI handles steps that need language or judgement, such as drafting a reply or summarising a call, and it can make mistakes, so a person checks its output. Many workflows need both.
Which business processes should a small business automate first?
Pick a process that repeats every week, follows the same path most of the time, and has one owner who wants it to get easier. Inbound requests, invoice and document handling, meeting notes and recurring reports are common first picks.
Should you automate a bad process?
No. Automation makes a messy process run faster and spreads its errors further. Agree on one standard way of doing the work first, then automate that version.
Do I need a developer to automate business processes?
Not for the first steps. Many tools you already pay for have built-in rules, and no-code connectors link the rest. You need a developer when the process touches a system without a connector or handles data that needs custom security.