The working distinction
Automation is a path. AI is a reader and a drafter. If you can draw the flowchart without a “here a person interprets the email” box, you want a workflow. If that box is the whole job, you want a model in front of the workflow.
Vendors blur this because “AI” sells. A rule engine with a chat skin is still a rule engine — which is fine, and cheaper.
A simple test
Write the rule. If you can, automate it. If the sentence starts with “it depends on how they phrased it”, that is AI. If the sentence starts with “then the system should also decide to refund”, that is an agent, and you should not start there.
Side by side
| Automation | AI | |
|---|---|---|
| Input | A form, a status change, a known field | A document, an email, messy language |
| Decision | Rules you wrote | A model’s best next step, constrained |
| When it is cheap | The path never changes | Reading or drafting is the slow part |
| Failure | The rule was wrong | The model was confidently wrong |
| Typical first build | 2 to 4 weeks | 3 to 10 weeks |
Most useful systems are a reader or drafter, then a workflow. Invoice PDF → extract fields (AI) → create draft bill → manager posts (automation). Skip the model if the invoice is already a structured email you control.
How vendors blur the words
“AI-powered workflow” sometimes means a rule engine with a chat skin. That can still be a good buy — just pay for a workflow. “Automation” sometimes means an agent that emails customers. Ask what happens when the input is unexpected. If the answer is “it figures it out”, you are being sold a model with write-access. Read agents versus chatbots before you say yes.
Three office jobs, classified
Leave approval. Form, balance, manager, deadline. Automation. Putting a model in the middle does not make the manager faster. It makes the path harder to explain when someone is refused.
Supplier invoice PDF. The page is messy; the accounts package wants fields. AI to extract, automation to create the draft and route for post. Skip the extract if the supplier already sends a structured file you control.
“Sort out this late order.” That sentence hides a refund, a reship, or an apology. If you give a model tools and that goal, you have an agent. Do not start there. Start with “tell me where the order is” — a lookup — then a human decides.
How to buy the right one
Write the trigger and the output on a whiteboard. If both are structured, buy a workflow. If the trigger is language or a document and the output is structured, buy extraction or drafting, then a workflow. If the output is an action in another system with no person, you are buying an agent, and you should be able to name the tools and the cap on steps before you sign.
Price follows that choice. Workflows are weeks. Grounded assistants are a couple of months. Agents that write back are a quarter or more, mostly because of permissions and logs. Paying agent money for a workflow is the usual waste. Paying workflow money for a model with write-access is the usual accident.
Say this out loud before you sign
“If the input is a form and the path never changes, we want a workflow, even if you branded it AI. If the input is a PDF, we want extraction, then the same workflow. If you want to email the customer or post a bill without a click, that is an agent, and we will not start there.” A partner who argues with that paragraph is selling a word. A partner who writes it into the statement of work is selling a system.
The longer treatments if you are still unsure which job you have: when to automate, agents versus chatbots, and the pillar on AI for business.
A mailbox, classified in the room
Stand in accounts. Point at the inbox. Structured supplier file you required them to send — workflow, no model. PDF on a letterhead that changes — extract, then workflow. Customer asking where an order is — lookup, a chatbot with a read-only tool, not an agent. Customer saying “sort it out” — a person, until you have logged a hundred of those and know which three actions actually happen. Mixing all four into “AI for the mailbox” is how you buy a loop that emails the wrong supplier.
Write the four labels on a board. Sort last week’s mail into them. The pile sizes are your backlog. Automate the biggest clean pile first. That is usually cheaper and calmer than starting with the angry free-text pile because it sounded more “AI”.
If the board is mostly clean files and forms, you may not need this page. You need workflow automation. If the board is mostly language and PDFs, you need a reader, then a workflow — add AI to an existing application. If someone is still selling one login for both piles, they are selling a word. Pay for the pile you have.
Payroll, claims, and why the words keep getting mixed
Payroll on a known input file is automation. A medical claim PDF with a stamp over the total is extraction, then the same payroll-adjacent workflow — or a human. A chatbot that “explains payroll policy” is AI with retrieval, and it still must not change a salary. Three jobs, three tools. A vendor who wraps all three as “HR AI” is asking you to fund a category. Buy the pile that is actually slow.
Write the failure you will accept. A wrong rule in automation is your sentence, fixable. A wrong extract is a correction before post. A wrong email to an employee is a conversation you did not want. Design from that sentence backward. That is the difference, in one office, without a glossary.
A purchase order, labelled without a vendor in the room
Under a written limit, known cost centre, known supplier: automation. A photo of a handwritten quote as the only attachment: extraction first, then the same path — or refuse to start until a typed quote exists. “Just raise it, I already said yes on the call”: that is a person, logged, not a model with send-mail. If your last twenty POs are mostly the first kind, do not buy AI. If they are mostly photos, do not buy a workflow that assumes a form. Label the pile you have. Pay for that pile. Re-label in a month if the mix changed. The words on the invoice should follow the pile, not the other way around. If the vendor’s proposal will not name the pile, they are selling a category. Categories are not purchase orders. Ask them to point at last week’s mail and say which label they are pricing.