Pick one repeatable task.
Look for work that follows a stable pattern: copying approved information between tools, creating a task after a status change or reminding someone about an appointment. Start with a task that has a clear input and a result you can check.
Know when to stop.
Missing details, conflicting records or an unusual request should have a clear route to a person. An automation should not quietly make a business decision that nobody agreed it could make.
Check the whole process.
Test a normal example and a realistic exception. Confirm that repeated events do not create duplicate work and that someone can see a failure. Measure usefulness through the work removed and the errors avoided, not the number of automations running.