The business processes to automate first with AI are the ones that repeat often, take real time by hand and produce output someone can check in seconds. Inbox triage, document data extraction and data entry between systems usually fit. Decisions about people, rare high-stakes work and processes nobody agrees on usually don't.
Picking well matters more than the technology. A good first automation saves visible time and makes the second one easy to approve, while a stalled pilot often becomes the reason nobody tries again.
Start with a list of real work
Don't start from AI capabilities ("what can a language model do?"). Start from where time goes today.
Ask each team lead a few questions and write down every answer, however small:
- Which tasks does your team repeat every day or every week?
- Where do people copy information from one system to another?
- What work piles up when someone is on vacation?
- Which requests come in by email or form and need sorting before anyone can act?
- Which reports does someone assemble by hand?
A first pass usually produces twenty to forty candidates. That's the right size. You're looking for the few that combine high value with low risk.
Score each candidate
Rate every candidate from 1 to 5 on four questions. Keep it quick; the goal is ranking, not precision.
| Factor | Question | High score means |
|---|---|---|
| Volume | How often does this happen? | Many times a day or week |
| Time | How long does each instance take by hand? | Minutes to hours of focused work |
| Rules | How clear is a correct result? | Someone can check the output quickly |
| Risk | What happens if one instance goes wrong? | Easy to catch and fix; nobody is harmed |
Multiply volume by time to get a rough sense of hours at stake. Then use rules and risk to filter: a high-hours process with unclear rules or serious consequences is a poor first project, however tempting.
Also note two things for each candidate: whether the data is accessible (an API, a shared inbox, an export) and who in the business owns the process. A process with no clear owner will have no one to tell you when the automation gets it wrong.
Processes that usually make good first automations
These patterns combine high volume with outputs that are easy to check:
- Triaging incoming emails, forms or tickets: classifying each one, extracting the details and routing it to the right person or queue.
- Pulling fields from invoices, purchase orders, delivery notes or application forms into a system of record.
- Drafting replies to common customer or supplier questions for a person to review and send.
- Moving information from emails or spreadsheets into a CRM, ERP or project tool.
- Assembling a weekly or monthly report from several sources, with a short written commentary.
- Writing summaries, action items and CRM updates after sales or support calls.
What these have in common: a person can check the result in seconds, a mistake is visible and reversible, and the work is boring enough that nobody will miss doing it.
Processes to leave for later
Some processes look attractive and are poor first choices:
- Decisions about people, such as hiring, performance evaluation and credit, carry legal obligations, including under the EU AI Act, and mistakes hurt individuals. They need careful design, not a pilot.
- Work that happens twice a year and carries high stakes offers little time to save and much to lose.
- If three people would handle the same case three different ways, agree on the process first and automate it afterwards.
- If the information lives in someone's head or in a system with no export, the integration work will dominate the project.
Design for review from day one
A good first automation doesn't need to handle everything. It needs to handle the common cases well and recognize the rest.
Build in three paths:
- When the automation is confident, it completes the work, and a sample is checked regularly.
- When it's uncertain, it prepares the work and a person approves or corrects it.
- When an item is out of scope, it goes to a person untouched, with a note on why.
Start with more items on the uncertain path than you think you need. As the team sees the automation handle those correctly, widen the confident path. Trust grows from evidence, and this structure produces it.
Run a small pilot
Keep the first pilot short and measurable:
- Measure the baseline. Before building anything, record how many items arrive and how long they take by hand for two weeks.
- Build the narrowest useful version. One process, one input channel, the common cases.
- Run it alongside the manual process for a week or two, comparing results.
- Switch over gradually, starting with the cases the automation handles most reliably.
- Report the result in hours saved, error rate and items needing review, against the baseline.
Measure before you build
The baseline is easy to skip and impossible to recreate later. Without it, nobody can say whether the automation saved time, and the case for the next one rests on opinion.
Plan who runs it
Before the pilot ends, agree who owns the automation: who receives alerts, checks samples, and updates it when the process or the inputs change. Automations without an owner degrade quietly, usually within months. Our article on why AI automations break covers the operating habits in detail.
Where to start this month
Spend an hour with each team lead collecting the list, and another hour scoring it together. Pick the candidate with the most hours at stake among those whose output someone can check at a glance, record two weeks of baseline, and name the owner before anything is built. The result of that pilot, in hours and error rate, is what decides the second automation.