Most small firms do not have an AI problem. They have a week that disappears into email, rework, chasing, and copying the same facts into three places.
Someone then says you need a strategy. A roadmap. A steering group. That is a good way to spend six months and still be copying invoices on a Friday.
You need a shorter question: what are we actually required to do, and what can we stop?
Start with the requirement, not the tool
Before you buy anything, write down the job in one sentence. “We need a weekly report for the client.” “We need to quote faster.” “We need fewer missed follow-ups.”
Then ask whether that job is real. Who asked for it? What happens if you do it less often, or not at all? A surprising amount of “must” is habit, a leftover from a bigger firm, or a template nobody reads.
If the job is not required, delete it. Do not automate a thing you should have stopped.
Make what is left simpler
If the job stays, strip it. One list, not three. One place the number lives. One person who owns it. Fewer fields on the form. A shorter email.
Speed comes after that. Same steps, less waiting: batch the quotes, answer the same three questions with a saved note, stop bouncing a file around the team.
Only then look at a tool. Automation last. If you automate a mess, you get a faster mess, and you pay a subscription for the privilege.
What this looks like in a small firm
You do not need a transformation programme. You need one slice of work, the people who actually do it, and an honest pass:
1. What is required?
2. What can we drop?
3. What can we simplify?
4. What can we do sooner?
5. What, if anything, should a tool take?
That is the whole method. It is how we run the AI Efficiency Workshop. Questions first, the real work on the table, a short list at the end. Not a slide pack about the future of work.
If someone is still selling you a 40-page AI strategy, ask them which Friday afternoon task it will remove this month.
Leave a Reply