How to Pick Your First AI Use Case
The first AI project sets the tone for every one after it. Pick one that succeeds visibly and the organisation leans in. Pick an ambitious moonshot and it becomes the reason AI "doesn’t work here".
- Published
Score each candidate
| Criterion | What a 5 looks like |
|---|---|
| Volume | Happens hundreds or thousands of times a month |
| Clarity | Everyone agrees what a correct result is |
| Data access | Inputs are already digital and reachable |
| Low risk | Mistakes are cheap and reversible |
| Measurable | Today’s baseline is known or easy to measure |
Add the scores. Pick from the top three the one with an enthusiastic internal owner.
Good first picks
- Answering repetitive customer questions from your documents.
- Extracting data from invoices or forms into your system.
- Triaging and routing inbound emails or tickets.
- Booking and rescheduling appointments.
Poor first picks
- Anything where one mistake is very costly: pricing decisions, medical advice.
- Tasks nobody does consistently today, so there is no baseline.
- Projects that depend on data you do not yet collect.
- A company-wide "AI assistant for everything".
Frequently asked questions
How big should the first project be?
Small enough to show results in 4–8 weeks, real enough that people notice.
Who should own it internally?
The manager of the team whose work changes — not IT alone.
Can you help us choose?
Yes — a short discovery session scores your candidates and recommends one.