· 2 min read
AI Assistant vs Copilot vs Agent: The Five Levels of AI Process Adoption
"Should we be using AI agents?" is the wrong question. The useful question is: for this process, who acts, and does a person look first?
The book answers it with the Five Levels of AI Process Adoption, sitting above a Level 0 baseline.
The levels
- Level 0 - Human process. No AI. This is not the same as manual; a process full of rules-based automation can still be Level 0.
- Level 1 - AI assistant. A person asks for help and checks the answer before using it.
- Level 2 - AI copilot. AI suggests inside a tool the person already uses, such as the CRM. The person edits and accepts every output.
- Level 3 - AI workflow. The system starts the work on a trigger - a new message arrives - and runs a fixed sequence. People approve at gates and handle exceptions.
- Level 4 - AI agent. The system chooses its own steps toward a goal, using approved tools. People set boundaries and approve consequential actions.
- Level 5 - AI-managed process. Routine work runs end to end with no person checking each item. Humans govern policy, exceptions, and accountability.
Controls accumulate
Each step up gives AI more room to act before a person looks, so each level adds controls on top of those below it. A Level 3 workflow still needs Level 1's approved tool and data rules, plus validation, logging, and an exception path. A Level 4 agent adds tight permissions, budgets, and a kill switch.
A level reached without its controls is not a higher level. It is an unguarded one.
A level describes a process, not a company
The same product can sit at Level 1 in one process and Level 3 in another. A healthy small business runs many processes at different levels at once. That mix is the goal, not a stage to grow out of.
Not every flowchart is an agent
A system that chooses among paths someone designed in advance is still Level 3. Only a system that chooses steps nobody laid out counts as a Level 4 agent. Plenty of tools sold as "agents" are well-built workflows - which is usually good news, because workflows are easier to test and govern.
Choose the right level, not the most impressive one
Treating the levels as a maturity race is the most common mistake. Many processes belong at Level 1 or 2 for good reasons: high judgment, sensitive relationships, or data that is not ready. Very few small-business processes belong at Level 5 today, and none should start there.
Pick the lowest level that does the job. Prove it. Then decide, with evidence, whether the next level is worth the controls it requires.