A definition you can use in a meeting
If a person is moving the same information from one system to another, or chasing the same approval every Tuesday, that is a candidate. Automation is the piece of software that does the moving and the chasing, according to rules you can write down.
That last clause matters. If nobody can write the rules down, you do not have an automation project. You have a process-design project that has not happened yet. We see this constantly: a business asks for automation and discovers, in week one, that three people do the “same” job three different ways.
Automation is not digital transformation
Digital transformation is a change in how the business operates — often a new system of record, a new channel, a new operating model. Automation is a change to a single path through work you already do. Confusing the two is how a six-week workflow becomes a two-year programme.
If you are replacing the system of record itself, you are closer to custom ERP or legacy modernisation. If you are leaving the systems in place and connecting them, you are in automation.
Where it pays off first
| Process | Why it works |
|---|---|
| Invoice capture and posting | High volume, fixed fields, errors show up in the next reconciliation |
| Approval routing | Rules are usually simple once someone writes them down |
| New-staff onboarding | The same ten accounts, every time, in the same order |
| Customer email to ticket | The customer already typed the facts; stop retyping them |
| Stock or job-status notifications | People forget; software does not |
A longer treatment of how the work actually flows is in workflow automation explained. If you are not sure a process is ready, read when to automate first.
When AI is the wrong tool
If the next step is always the same, you do not need a model that “reasons”. You need a workflow. AI earns its keep when the input is messy — a PDF, an email, a spoken request — and the output still has to land in a structured system. That distinction is the whole of AI versus automation.
What it costs
A single approval or notification workflow, talking to systems that already have APIs, is usually two to four weeks. Connecting two systems that were never meant to talk is longer, because the work is the integration, not the “automation” slide. A document-heavy process that also needs extraction sits closer to an AI integration than to a pure workflow.
Budget the unglamorous parts: exception handling, an audit trail, and a named owner. Unowned automations get switched off the first time they do something surprising.