You do not need to begin with a company-wide AI plan. A better starting point is often a task that somebody can describe without a presentation: “We copy these enquiries into a spreadsheet every morning,” or “We answer the same arrival questions all week.”
The useful question is not whether AI can do the task. It is whether a controlled workflow would make the working day easier.
Look for repetition you can actually observe
Choose a task that happens often enough to review. Watch how it starts, what information it uses and where it finishes. If nobody agrees on those steps, map the process before adding automation.
Repeated work is not automatically suitable work. A task can be frequent and still involve judgement, sensitive information or costly mistakes. Start with a lower-risk part, such as gathering details or preparing a draft, rather than handing over the whole decision.
Check the source of the answer
An assistant needs something reliable to work from. For customer questions, that might be an approved service guide. For an internal request, it might be a current process document.
If three people give three different answers, the first job is to agree the answer. Automation can help distribute good information; it cannot resolve an organisation's uncertainty simply by sounding confident.
Make the next person visible
Decide who receives an exception and what they need to see. “Send it to the team” is not enough if the team is a shared inbox that nobody owns.
A useful hand-off contains the request, the information already collected, what is missing and why review is needed. This lets a person continue the work instead of starting the conversation again.
Choose a modest measure
Before the pilot, record what happens now. You might count manual copying steps, measure staff handling time or note how often an enquiry arrives without the details needed to respond.
After the pilot, check the same measure and look for new problems. More automated replies are not necessarily better if staff spend extra time correcting them.
Make the first decision reversible
A sensible pilot has a clear boundary, a pause option and a way to return to the existing process. Start with one task and an accountable owner. Expand only when the result is useful.
Have a task in mind? Bring it to a demo conversation with SBM Ananta.
Try the related demo →