Start with work you can describe
A useful first automation starts with a process someone understands, rather than a tool someone wants to buy. Pick a recurring task with a recognisable trigger, an agreed output and a person who owns the result. An emailed order that needs checking and entering into a system is a clearer starting point than automating the whole sales department.
This guide is a planning method, not a forecast of savings. A process improvement or an existing software feature may solve the problem without any AI development.
Walk through one real example
Ask the person doing the work to show you a recent, permitted example. Record where the input arrives, what they check, which applications they use, and what happens when something is missing. Use representative material that your organisation is allowed to share. Remove personal or confidential data that is not needed for the review.
Pay attention to handoffs and exceptions. A task that looks like simple copying may depend on customer-specific rules that are known only to one experienced employee.
Use this process map
Copy the checklist below and fill it with your team's observations. Leave estimates blank until someone can explain how they were measured.
| Step | Owner | Input and system | Required check | Exception route | Observed time or volume |
|---|---|---|---|---|---|
| Receive input | |||||
| Validate details | |||||
| Prepare output | |||||
| Approve and record |
Compare candidates against five questions
- Does the work repeat often enough to justify maintaining an automation?
- Are the inputs accessible and sufficiently consistent?
- Can you describe the ordinary rules and the main exceptions?
- Can a person spot and correct an incorrect result before it causes harm?
- Is there a process owner who can test changes and look after the workflow?
Choose a small boundary
A first phase might prepare a draft record while leaving approval and posting with an employee. Agree what success means before building: which cases should work, what must be rejected, and which actions always need approval. Observe handling time, rework and error cases before comparing the new process with the old one.
Wait if ownership is unclear, permissions are unresolved or the business rules keep changing. The next useful step may be fixing those foundations. When you can name one bounded workflow, an assessment can examine feasibility, risks and possible approaches before implementation is quoted.