We sell AI development, so you would expect us to say every business is ready for AI. They are not. A meaningful share of our free audits end with "not yet, fix this first" — because an AI project on top of a messy process just automates the mess. This is the checklist we actually run.
Sign 1: The same tasks eat hours every single week
Copying data between tools, drafting the same five email replies, processing routine requests, compiling the weekly report. If a task is repetitive and follows rules a new hire could learn in a week, it is in the automation sweet spot — that is exactly the work AI agents are built for. Track one ordinary week; if a role spends 10+ hours on rule-following work, the math almost always clears.
Sign 2: Your knowledge is written down somewhere
Support docs, SOPs, past tickets, contracts, product sheets — even messy ones. AI systems answer from your content (that is what RAG does), so written knowledge is the raw material. If everything lives in two senior employees’ heads, an AI project starts with an expensive extraction step; a company with docs skips straight to building.
Sign 3: Volume is growing faster than you want headcount to
More tickets, more leads, more orders — and the default plan is "hire another coordinator." If the marginal hire would mostly do routing, lookup, and data entry, an AI chatbot or agent handles the volume curve while your humans handle the judgment calls. AI pays off fastest exactly where growth is straining a repetitive process.
Sign 4: Your core processes are stable
Automation encodes a process. If the process changes weekly because you are still finding product-market fit in how you operate, you will rebuild the automation continuously. Stable-but-tedious is the ideal profile: the workflow has looked the same for six months and everyone is bored of it.
Sign 5: Someone owns the outcome
The AI projects that stick have an internal owner — someone who knows the workflow, reviews the system’s output in the first weeks, and has the authority to change the process around it. Tools do not transform businesses; owners using tools do. If nobody can name the owner, park the project.
Three signs you are not ready yet
- The process itself is chaos. If three people do the same task three different ways, standardize first — automation amplifies whatever exists, including dysfunction. This fix is free and makes the eventual AI build dramatically cheaper.
- The motivation is FOMO, not a metric. "We need an AI strategy" with no target number (hours saved, response time, tickets deflected) produces demos, not results. Pick the metric first; the project designs itself.
- You expect it to replace judgment. AI handles the repetitive layer so people can do the judgment layer. If the plan is "the AI decides and nobody checks," you are buying a liability, not leverage.
Scored at least three of five? Start small.
Do not launch a company-wide AI initiative. Pick the single most annoying, most stable workflow and automate that one thing — a support chatbot grounded in your docs ($2–4K, 1–2 weeks) or one agent for one workflow ($4–10K, 3–5 weeks). A working system in production for a month teaches you more about what to build next than any strategy deck. If you want the checklist run against your actual operations, that is the free 30-minute audit — and if the honest answer is "not yet," that is what you will hear.