Where AI actually helps a small business

Start with your Tuesday, not a tool list

If your day involves answering the same questions, finding the same documents, or copying details from an email into another system, there may be a useful project there. Write down what happens, who does it, and what a good result looks like. “Use AI” is not a job description. “Turn a new service inquiry into a complete draft response” is.

I like to begin with one ordinary working day. Where did someone wait for information? Which message needed the same answer as yesterday? What took ten steps because two systems do not connect? These details give a build something concrete to improve.

Find a task with a clear finish line

Good first candidates tend to have repeatable inputs and an output someone can check quickly. An assistant could summarize a long inquiry, suggest the relevant service, and draft a reply using approved information. A person reviews it before it goes out. That is a useful boundary for an initial version.

A simple rule may be enough for some work. If every booking needs the same confirmation, a reliable template and integration may solve it without a model. I would rather build the straightforward thing that works than add another system to maintain.

• Sort inbound requests by topic and urgency.
• Draft replies from approved business information.
• Find a policy or project detail in internal documents.
• Prepare a structured handoff between people or tools.

Measure the whole job

Count the time spent checking and correcting the output, not just the time saved drafting it. Keep a small set of representative examples, including awkward ones. Compare the old process with the proposed one. Record what was missed, what needed editing, and whether the customer experience improved.

For example, a faster reply is not a win if it promises a service you do not offer. The review step, escalation path, and source information are part of the product. They belong in the scope from the start.

Build one useful version first

Pick a narrow pilot, assign an owner, and agree on the conditions for keeping it. You should know what happens when the system is uncertain or a connected service is unavailable. Expand only after the first workflow is useful in ordinary operation.

That is the kind of AI work I build at Aakhus Tech: a defined problem, a working implementation, and a clear way to tell whether it helps. Bring the repetitive part of your day. We can work out the right tool together.