Resource
AI agent readiness checklist for small teams.
Before a client gets an AI employee, the workflow needs an owner, a clear trigger, safe data scope, approval gates, and a rollback path.
Checklist
- One workflow has a named human owner and measurable pain.
- Inputs, outputs, and system of record are known.
- Sensitive data and off-limits systems are documented.
- External/destructive actions are draft-only or approval-gated.
- Pilot success can be measured in 30 days.
Operator note
A practical checklist for deciding whether a business workflow is ready for an AI employee or agent pilot.
This resource exists to make AI work visible, bounded, and supportable: scoped workflows, clear approvals, artifacts, logs, and rollback before autonomy.
When to use it
Use this checklist before a sales call, discovery session, or internal pilot decision. It is designed to prevent the most common failure mode: picking a flashy AI use case before the workflow, data owner, and approval path are understood.
A good first AI employee candidate is boring in the best way. The task repeats often, the inputs are available, the output is easy for a human to review, and mistakes can be contained without harming customers or production systems.
If the workflow cannot pass this checklist, the right move is not more automation. The right move is discovery, process cleanup, or a narrower prototype.