Look for tedious work, not difficult judgement
Ask the team what they keep copying, checking or chasing. The useful opportunities are often small enough to describe in one sentence.
- Copying website enquiries into a customer record.
- Sending appointment, renewal or missing-document reminders.
- Preparing key details from a supplier order for review.
- Routing new requests by type, area or customer.
- Answering common questions from approved business information.
Score each idea against five questions
Start with a task that passes most of these checks. If nobody owns it or a mistake would be hard to spot, deal with that before automating it.
- Does it happen often enough to justify the setup?
- Could someone write down the normal rules clearly?
- Is the required information available and reasonably consistent?
- Would someone notice an error quickly, and can its effects be contained?
- Does one person know what a correct result looks like?
Design the stopping points first
Decide what should not happen automatically. Where do missing information, duplicate records and unexpected replies go? Who can pause the workflow? Keep a record of what ran and why.
PayBlah uses this pattern for overdue-invoice email reminders. Payments, replies and disputes affect the sequence, and firmer follow-up requires approval. The same thinking can apply to renewals, documents and other routine follow-up.
Add AI only where interpretation helps
Plain rules handle many reminders and hand-offs. AI becomes useful when something needs to be read or interpreted: a free-text enquiry, an attachment, or the same question phrased in different ways. Use approved information and a clear route to a person when the answer is uncertain.
Start with review built in. Work involving money, complaints, safety or commitments needs explicit limits and appropriate human judgement. An unclear process is not ready just because it can be automated.
Run a focused pilot, review the exceptions and ask the team whether the useful work actually became easier. That evidence should decide the next change.