Which task should you give an AI agent first?
Start with a repetitive workflow, check the output and measure before expanding.

Twenty AI ideas do not provide a starting point. A first project should answer a concrete question: can this work be prepared more simply, with a result the team can check?
Describe a workflow, not a job
“Automate administration” is too broad. “For each quote request, extract five fields, prepare a record and flag missing details” defines an input, a process and an output. That makes the project testable.
Choose work that occurs often enough to observe. An annual exception may need attention, but is rarely the best way to learn how an agent works in your business.
Look for four practical signs
When one of these is missing, clarify it first. Adding an AI model does not resolve unclear responsibilities.
- An identifiable input: an email, document, form or case.
- An observable result: a record, draft, category or alert.
- Rules the team can explain using examples.
- Someone who can decide whether the result is acceptable.
Compare three candidate tasks
For each task, note monthly volume, actual handling time, tools and exceptions. Add the cost of an error and how easy the output is to check. Hours alone are insufficient: actions involving a customer or payment require different controls from an internal draft.
Preparing a response to a recurring request is a useful candidate. Autonomous contract negotiation needs much more scoping. The initial workflow may stop at the draft, even if automatic sending is technically possible.
Build a small set of test examples
Gather anonymised examples: common cases, an incomplete document, an ambiguous request and an out-of-scope case. Write down the expected behaviour. Should a missing detail trigger a question, an alert or a stop?
Measure review and correction time as well. Time saved is what remains after those activities, rather than the whole original task being declared eliminated.
Make the decision after validation
Agree acceptance criteria before testing: correct fields, flagged errors, retained approval and acceptable review time. Afterwards, launch, adjust the scope or stop.
The free Relaist audit reviews one process from your brief. It helps define this starting scope; it does not include a production system.
Describe a task, your tools and the volume. The free audit reviews one workflow and provides an initial summary.
Request my free audit

