Start with a frustrating task, not a fashionable tool
For a small business in Singapore, the most useful AI opportunity is often hiding in an ordinary working day. It might be the same delivery question arriving ten times, an enquiry that gets lost between two inboxes, or a report that someone rebuilds every Friday. Start by observing the work. A clear problem is more valuable than a long list of impressive product features.
Ask the person doing the task to walk you through a recent example. Record what arrives, which information they need, what they produce and where they pause to make a judgement. Do not assume every step needs AI. A shared template, a better form or a simple reminder can sometimes solve the problem more cheaply and reliably.
Build a baseline you can actually compare
Before changing anything, measure a normal week. Count the requests, estimate handling time and note common mistakes. Include the time spent checking work and fixing exceptions, not just the time spent typing. If a task takes five minutes but creates another fifteen minutes of follow-up, your baseline should reflect the whole process.
Choose one primary outcome that matters to the business. For an enquiry workflow, that might be fewer requests left unanswered at closing time. For reporting, it could be a consistent report ready before the weekly meeting. Keep your notes simple enough that the team can maintain them without turning measurement into another administrative burden.
Pick a narrow and reversible pilot
A good first pilot has one owner, one workflow and a defined set of inputs. A retailer could trial draft replies for product availability questions without letting the assistant make promises about refunds or delivery dates. A service business could organise incoming enquiries without allowing the system to quote prices or confirm appointments.
Agree what the pilot will not do. Use approved business information, remove personal details when they are unnecessary and keep a manual fallback. Choose a review period that includes ordinary work and a few realistic exceptions. It should be possible to stop the pilot without losing enquiries, documents or the ability to serve customers.
Make human review part of the design
Someone needs to be accountable for the result, even when the system produces a convincing answer. Decide which outputs require approval, which can be used directly and which must be escalated. Financial decisions, customer commitments and sensitive information deserve particular care. The owner should understand the workflow well enough to recognise an answer that sounds plausible but is wrong.
Create a small review checklist. Does the draft answer the actual question? Is the supporting information current? Has the system added a promise that the business never approved? Review a sample of routine outputs as well as flagged exceptions. A system can make the same small mistake repeatedly without triggering an obvious warning.
Decide whether to improve, expand or stop
At the end of the pilot, compare the new process with the baseline. Add subscription fees, usage charges, implementation effort and the time spent reviewing outputs. Ask the team whether the workflow genuinely feels easier. A faster first draft is not a useful improvement if checking it takes longer than doing the original task.
If the evidence is positive, document the process before expanding it. Keep the approved information, access permissions and fallback instructions in a place the team can find. If the pilot is disappointing, record what you learned and consider a simpler approach. Choosing not to automate an unsuitable task is a sound business decision, not a failed AI strategy.
