Why check readiness before buying anything?
Because the most expensive AI mistake is solving the wrong problem well. A business that cannot say where its leads leak, or who would own a new system, will get the same result from a great tool as from a mediocre one: an abandoned subscription.
The good news is that readiness is not a technology audit. It is ten honest questions, answerable by any owner in twenty minutes.
The ten questions
- 1. Can you list every channel where a customer can contact you — and who is responsible for each?
- 2. Do you know your typical first-response time to a new inquiry, including evenings and weekends?
- 3. Can you see all open leads and their status in one place, today, without asking anyone?
- 4. Which three tasks does your team repeat most often in a week — and roughly how long do they take?
- 5. If a key staff member left tomorrow, is the knowledge of how things run written down anywhere?
- 6. Where does customer data actually live — one system, or five that disagree with each other?
- 7. What decisions in your business genuinely require human judgment — and which just require information?
- 8. Who in the business would own a new system: review it, maintain it, decide when it changes?
- 9. What would you never want an automated system to do without a human approving it first?
- 10. If one bottleneck disappeared tomorrow, which would change your revenue or your evenings the most?
How to read your answers
Questions 1–3 map your demand capture. Blanks here usually mean leads are leaking, and a lead response system is the highest-leverage first build. Questions 4–6 map operations: strong repetitive-task answers with scattered data point toward a workflow automation sprint, usually preceded by simple data consolidation.
Questions 7–9 are the governance test — and the strongest predictor of success. A business that can already say what must stay human has done the hardest design thinking. Question 10 is the whole game: the honest answer to it is where any engagement should start.
What to do with the result
Do not fix everything. Take your answer to question 10, and the leaks you found on the way, and scope the smallest system that addresses the single most expensive one. Prove it on real operations. Then decide about the second thing.
This checklist is, in miniature, what a structured systems diagnostic does with more rigor: map the workflow, find the highest-leverage bottleneck, and design around it. If you want a second pair of eyes on your answers, that is exactly what the diagnostic call is for.