Agent Readiness Assessment
8 questions about the task, not the technology. A recommendation: agent, deterministic workflow, or hybrid, including when the honest answer is "don't use an agent."
This assessment scores whether a task should be built as an AI agent, a deterministic workflow, or a hybrid, based on task complexity, autonomy, frequency, error cost, and four other factors — before any code gets written.
Task Complexity
How much judgment does each step require?
How it works
Answer 8 questions
Covering task complexity, autonomy, frequency, error cost, tool count, human approval, data requirements, and workflow variability.
Each answer points a direction
Higher points push toward an agent; lower points push toward a deterministic workflow.
Get a 0-100 fit score
Points are summed and normalized to a 0-100 scale.
See your recommendation
Your score maps to Agent Justified, Hybrid Approach, or Deterministic Workflow.
When should I use this?
- You're deciding how to build a new automation and want to know if it needs an agent.
- An existing workflow keeps breaking on edge cases a fixed script can't handle.
- You want to avoid building an agent for a task a deterministic pipeline would handle better.
Who is this for?
- Engineers scoping a new automation before writing code.
- Product and engineering leads deciding where to spend agent-building effort.
- Teams under pressure to "add AI" who want to check the task fits first.
Common Questions