Businesses often use “automation” to describe very different operating models. That makes tool selection feel more important than process design. A stronger sequence is to classify the work first, then give technology only the amount of authority the job can justify.
Workflow automation: rules execute known work
Use deterministic workflow automation when triggers, inputs and actions are predictable: create a CRM record from a valid form, route a lead by region, send a booking confirmation, move approved data between systems or remind an owner when a defined deadline arrives.
This kind of automation is powerful because it is boring. The business decides the rule and the system applies it consistently. Do not use a language model to solve a problem a reliable rule can solve better.
AI-assisted work: the system prepares, a person decides
AI becomes useful when the work contains language, variation, summarisation, classification or pattern recognition that is difficult to express as simple rules, while the material decision should remain human.
Useful examples include summarising an enquiry for sales, extracting structured information from an email, drafting a response from approved context, classifying support requests or surfacing missing information before a human review.
Bounded agentic automation: useful autonomy inside a controlled lane
An agent can reason across steps, use tools and take actions. That does not mean it should have unlimited authority. A useful agent has a bounded job, defined tools, observable actions, explicit permissions and an escalation route.
Adaptive research, lead preparation or low-risk administrative sequences may justify this model when actions are reversible, logs are inspectable and confidence or exception thresholds trigger human review.
Human process with software support: judgement is the product
Some work should remain primarily human even when technology can gather context, keep records or prepare options. Significant negotiation, sensitive customer conflict, strategic qualification and ambiguous legal, ethical or reputational risk are obvious examples.
When context materially changes the answer and accountability cannot sensibly be delegated, software should support the decision-maker rather than replace one.
A practical decision sequence
First ask whether the current process creates meaningful delay, error, labour, missed opportunity or poor visibility. Then ask whether the process is actually defined: trigger, owner, states, exceptions and expected outcome.
Next assess interpretation, consequence, reversibility and observability. The cost of being wrong should determine the amount of autonomy. Define the human gate before launch, not after the first serious mistake.
One sales-follow-up problem can use all four models
Workflow automation can create the CRM record and due date. AI assistance can summarise the enquiry and prepare a draft acknowledgement. A bounded agent can research approved public sources and recommend a next action. A human can retain qualification, commercial fit, proposal strategy and sensitive negotiation.
The mistake is treating the whole journey as either manual or AI. Stronger operating design allocates each part to the model that matches its decision load and risk.
Use the simplest operating model that can reliably solve the commercial problem: rules before AI when rules are enough, assistance before autonomy when judgement matters, bounded autonomy before open-ended agents, and human responsibility where the consequence belongs with a person.
Apply the logic to a real process: Run the AI Automation Opportunity Scorecard →