Choose a workflow people can describe
Look for repeated work with clear inputs and outputs. Ask the people doing it where context gets lost, what decisions need human judgement, and what a useful improvement would look like.
Avoid automating a process simply because it is frequent. A workflow with sensitive information or ambiguous decisions may need a different kind of support.
Check the information before the technology
Understand where the relevant information lives, who can access it, and whether it is accurate enough for the task. Data handling and access requirements belong in the first conversation.
A small prototype can help test assumptions, but it should use appropriate data and have a clear review plan.
Agree on a useful next step
Write down the intended user, the task, the human review point, and how the team will learn from a pilot. That gives everyone a grounded basis for deciding whether to continue.
A good first project can also conclude that a simpler integration or process change is the better answer.