Start with a real problem
Choose recurring work you can explain. Collecting information for a report, answering questions from documents, or handling inquiries are examples of processes worth examining. Describe who does the work, which systems they use, and what should change. These are examples to assess, not promises that every process should be automated.
Decide what is worth building
Map the opportunities before choosing tools. Check whether the data is available, where human review is needed, and how the cost compares with the useful outcome. The right decision might be to buy an existing tool, build a small integration, or leave the process as it is.
Define how you will know it works
Agree acceptance criteria before the build. What must the system do? What happens when the model is wrong? Who approves the result? Test against the agreement, then hand the system over to the people who will operate it.
This is the aiguys method: a first conversation, an opportunity map, architecture, then build and run. You can stop after a stage. Scope and price are agreed before starting the work that has been defined.