AI Readiness Checklist for Small Business

25 yes/no questions across five areas. Score yourself in twenty minutes and find out what to fix first.

Short answer: AI readiness is not about how advanced your tools are. It is whether your data is organized enough to trust, your team already has access to the basics, your processes are written down, someone has actually tried using AI, and you have simple rules for what not to share. Answer the 25 questions below and your pattern of yes and no answers tells you what to fix before you spend more time or money.

Prefer a score? Take the AI readiness quiz: the same 25 items, scored by area, with the three to fix first.

This is not a test you pass or fail. It is a way to see, in one pass, where the real gaps are before you commit to a bigger project. Most small businesses are ready for more than they think in one area and less ready than they think in another. The point of going through it in five separate groups is to find out which is which.

Answer honestly. A "no" here is not a problem, it is information. Every item includes the reason it matters, so you can decide for yourself whether it is worth fixing.

Group 1: Data and documents

  1. Your core customer information lives in one system, not scattered across spreadsheets, email, and sticky notes. Why it matters: AI tools are only as useful as the data you can actually point them at.
  2. Your files and folders have a consistent naming and organization pattern. Why it matters: AI that reads your documents needs to find the right ones, the same way a new employee would.
  3. You could hand someone your last twelve months of a core process's records without spending a day cleaning them up first. Why it matters: messy source data produces confidently wrong AI output, not obviously wrong output.
  4. Your most-used templates (estimates, contracts, intake forms) are digital and editable, not scanned images or paper. Why it matters: AI can draft from and fill in a digital template. It cannot usefully touch a paper form.
  5. You know roughly how much of your customer or business data is sensitive (financial, medical, legal) versus routine. Why it matters: this is the line that determines what is safe to paste into a general AI tool and what is not.

Group 2: Tools and accounts

  1. Your business has a paid or verified account with at least one major AI tool (ChatGPT, Claude, Gemini, or Copilot). Why it matters: free, unverified personal accounts mean no admin control and no visibility into what is being used for what.
  2. You know whether your CRM, accounting software, or scheduling tool already has AI features built in. Why it matters: the fastest wins usually come from turning on what you already pay for, not buying something new.
  3. Someone in the business could explain, in one sentence, the difference between ChatGPT and a workflow tool like n8n or Zapier. Why it matters: chat tools and automation tools solve different problems, and conflating them leads to buying the wrong thing.
  4. You have a way to see which AI tools your team is actually using, even informally. Why it matters: unmanaged use of free AI tools on business data is the most common security gap in small businesses right now.
  5. Your accounting, CRM, and email systems can be connected to each other in some way (native integration, Zapier, n8n, or an API). Why it matters: automations that save real time usually connect two systems, not just one.

Group 3: Processes

  1. Your top three recurring tasks (the ones that happen weekly, without fail) are written down somewhere, not just known by one person. Why it matters: you cannot automate or train on a process that only exists in someone's head.
  2. You could describe, step by step, what happens between a new lead coming in and that lead getting a first response. Why it matters: this is usually the highest-value process to improve, and you cannot improve what you cannot describe.
  3. Someone has actually timed how long your team spends on at least one repeated task. Why it matters: without a real baseline, you cannot tell whether an automation helped.
  4. Your business has a consistent way customers get a response, follow-up, or reminder, rather than it depending on who happens to be free. Why it matters: consistency is what makes a process automatable in the first place.
  5. You have identified at least one task that is repetitive, rule-based, and does not require a judgment call unique to each situation. Why it matters: that is the shape of task AI handles well. Judgment-heavy, one-off work does not fit the same way.

Group 4: People and training

  1. At least one person on your team has spent real time (a few hours, not a five-minute demo) using an AI tool on actual work. Why it matters: hands-on time is what turns a vague idea about AI into a specific, useful opinion about it.
  2. Your team has had some structured introduction to these tools, rather than being left to figure it out alone. Why it matters: unstructured, solo experimentation is the most common reason adoption stalls. See why your team isn't using AI.
  3. There is someone in the business, even informally, who people ask when they have an AI question. Why it matters: without a point person, good habits do not spread past whoever discovered them first.
  4. Your team knows how to tell when AI output is wrong, not just how to generate it. Why it matters: AI that is used without review is where the real damage happens, not AI itself.
  5. Leadership has said out loud, at least once, that using AI on appropriate tasks is expected, not just tolerated. Why it matters: without that signal, cautious employees default to not using the tools at all, even when it would help.

Group 5: Security and policy

  1. You have a written answer, even a short one, to "what should never be pasted into an AI tool" at your business. Why it matters: this is the single most important guardrail, and it takes twenty minutes to write.
  2. Your team knows the difference between your business's paid AI accounts and someone's personal free account. Why it matters: data typed into a personal account is outside your control and often outside your visibility entirely.
  3. You know which of your existing tools keep your data private to your account versus which may use it for training their models. Why it matters: this varies by tool and by plan, and it is a one-time check worth doing before sensitive data goes anywhere near AI.
  4. Someone owns the decision of which new AI tools get approved for use, rather than it being first-come-first-served. Why it matters: without an owner, tool sprawl happens quietly and nobody notices until something goes wrong.
  5. If an AI tool produced a wrong or embarrassing result today, you know who would find out and what they would do about it. Why it matters: systems fail quietly more often than loudly, and knowing the response plan in advance is cheaper than improvising one.

How to read your score

Count your yes answers out of 25. This is a guide, not a grade. What matters more than the number is which group had the fewest yeses, because that tells you exactly where to start.

Mostly yes (20 or more)

You are ready to move past experimenting and into building something that runs with less manual effort. The list of automation examples is a good next stop, or a two-week assessment to map your specific processes against what is worth building first.

Mixed (12 to 19)

You have real strengths and real gaps, and the fix is usually narrow: shore up the weakest group rather than starting over everywhere. If the gap is in people and training, team training closes it faster than anything self-directed. If the gap is in process, work through where to start with AI in a small business on one task before going wider.

Mostly no (fewer than 12)

Do not buy anything yet. Start with the basics: get one person using a paid AI tool on one real task for a few weeks, and write down your top three recurring processes. Both are free and take days, not months. Revisit this checklist after that, and the picture will likely look very different.

Wherever you land, a written policy is worth doing regardless of score. The free AI policy generator produces a basic one in a few minutes, covering what should and should not be shared with AI tools. And if you want to put a number on the time at stake before deciding how far to go, the AI ROI calculator is a quick way to see it.

For a look at how a business with an existing team culture around AI got there, see the training and adoption stories in case studies, and for a broader read on what actually helps versus what does not, AI consulting for small business covers what to expect from outside help once you know your own readiness.

Try it

Example estimates

Find your 10 hours.

Set your industry and team size, then adjust each task to see how many hours a month AI could realistically take back.

Example estimates, adjust to yours.

Want the real number, not an estimate? Book a free 20-minute call →

Open the full demo →

0 hrs

a month AI could realistically take back.

    Estimates. The real number comes from two weeks watching the work. How the assessment works →

    Frequently asked questions

    What is an AI readiness checklist?

    A list of yes/no questions about your data, tools, processes, people, and security that tells you whether AI would be easy or hard to adopt right now, and which gaps to close first.

    How do I know if my business is ready for AI?

    Answer honestly across five areas: whether your documents and data are organized, whether your team already has accounts for the main AI tools, whether your key processes are written down, whether anyone has actually tried the tools, and whether you have basic rules for what not to share. Mostly-yes means you are ready to start now. Mixed means pick one small area to fix first. Mostly-no means fix the basics before any bigger investment.

    What usually blocks small businesses from being AI-ready?

    Two things most often: nobody has actually spent real time using the tools yet, and the processes AI would help with were never written down anywhere, so there is nothing consistent to automate. Both are fixable in days, not months.

    Do I need a data policy before using AI at work?

    You need at least a basic one: a short, written answer to what can and cannot be pasted into an AI tool. It does not need to be a legal document on day one, but it should exist and be understood by everyone using the tools.

    Can I use this checklist without hiring a consultant?

    Yes. It is built to be scored by you or your team in about twenty minutes. Where you land tells you what to do next, and for most of the items on it, "what to do next" is something you can do yourself.

    Related tool: AI policy generator

    Get the next one before it is published.

    I post the prompts, workflows and checklists behind these articles in the community first, and answer questions there myself.

    Join the community

    Want it done for your business?

    Twenty free minutes. No pitch.

    Book a free 20-minute call