How to prepare a business for AI for service businesses
Preparation is mostly ordinary operational work. Write down how the target process actually runs, including the exceptions people handle without thinking. Identify which system holds the authoritative version of each record. Decide who is accountable for the output. None of that requires choosing a tool.
( The Detail )
The practical answer
Then set the boundaries early: what information is sensitive, what the system may not do, and who is told when it is wrong. Businesses that skip this stage usually rebuild once the first pilot exposes disagreements about definitions that nobody had needed to surface before.
Applied to this kind of business
Service businesses sell time, so the numbers that matter are utilisation, scope creep, and the gap between quoted and actual effort. That gap is usually invisible because time is recorded loosely, if at all, and it only surfaces once a job already feels unprofitable to everyone.
Work is coordinated through email, calendars and documents rather than through one operational system. Client context sits with whoever owns the relationship, which makes hand-overs risky and leaves the business quietly dependent on a few people remembering the right things.
How to approach it
Begin with the decision rather than the tool. Name the recurring judgement this affects, the information it depends on, and the person accountable for acting on the result. That framing keeps the first build small enough to inspect and useful enough to matter.
Keep a human review point in the loop until the quality and the failure modes are understood. A system that shows its working - what it drew on, where it is uncertain, and what it deliberately left alone - is one a business can keep running after the initial build.
( Next Step )
Start small enough to review, but on a workflow important enough to show whether a better system is worth building.