Choose a repeated problem
Look for a bounded task with clear inputs, outputs and a person who owns the result. Avoid beginning with an open-ended instruction to automate an entire business.
Map what can go wrong
Missing data, duplicated requests, inaccessible systems and uncertain decisions need explicit handling. Some steps should request human approval rather than continue automatically.
Evaluate the full result
Review accepted output, manual effort, failure recovery, review time and operating cost. A fast demonstration is not the same as a dependable process.
Keep it explainable
Someone in the business should know what the workflow does, where it can be paused and who responds to exceptions. That is part of delivery, not an optional follow-up.