In most businesses, automation replaces retyping. Not a role, not a person, but the part of somebody's day spent moving information that already exists from one screen to another. That is a smaller claim than automation is usually sold with, and it is the one that survives contact with a real office.
What the work actually looks like
An order arrives by email. Someone reads it, opens the system, and types in the same details. A payment lands in the bank; someone marks the invoice paid in a different place. A form is submitted on the website; someone forwards it to whoever should handle it, and sometimes forgets.
None of that is skilled work and all of it is error-prone, precisely because it is boring. A person doing the same transcription for the fortieth time that day is not concentrating, and the mistake will surface later as a dispute rather than as an error message.
Why "it will replace staff" is usually wrong
In a small business the person doing the retyping is also doing five other things, several of which require judgement. Removing the transcription does not remove the person; it returns two hours a day to the parts of their job that cannot be automated, which in a business of that size is normally where the growth is.
Where automation genuinely does displace work, it is worth being honest about it rather than describing it as efficiency. But that is not the common case, and pretending it is makes the whole subject harder to discuss inside a company.
What it does not replace
Judgement. If a decision requires weighing things nobody has written down, automating it produces confident wrong answers faster than a person produces careful right ones. The right design in that case is to route the case to a person quickly, not to answer it automatically.
It also does not replace a process that nobody agrees on. If three people describe step four differently, automation will pick one of their versions and make that disagreement permanent and invisible.
What is left over afterwards
The part people underestimate: something has to watch the automation. A workflow that stops silently is worse than one that was never built, because everyone continues to assume it is running. Failure alerts and someone whose job it is to read them are part of the work, not an optional extra.
Where to start
Write down, for one week, every time somebody copies information from one system to another. The list is usually shorter than expected and the frequencies are usually higher. The top two lines of it are your automation project; the rest can wait.
AI Agents Automation n8n