Your data is agent-ready when the information a task needs lives in one or two connected tools, the process is written down step by step, and you know which data the agent must never touch. Spend 20 minutes listing where the data lives, writing the process, cleaning one sample set, and setting access limits before you build anything.
Most AI agent projects in small businesses don’t fail because the AI is weak. They fail because the agent can’t find what it needs, or nobody ever wrote down how the job is supposed to be done.
People who build agents for small businesses describe the same two problems again and again: data scattered across five or six tools, and processes that live only in the owner’s head (r/AI_Agents, 20+ businesses; r/AI_Agents, 5 businesses). And when owners hesitate, privacy and security (36% in the U.S.) and accuracy (26%) are among the top reasons (Intuit 2026 AI Impact Report, PDF). Both are data problems.
This checklist takes about 20 minutes for one task. Do it before you pick a tool.
The checklist at a glance
| # | Check | Time | Ready if… | Red flag |
|---|---|---|---|---|
| 1 | Pick one task | 2 min | It repeats 10+ times a week | “Help with everything” |
| 2 | Map where the data lives | 4 min | 1–2 tools | 5+ tools, or paper |
| 3 | Write the process | 5 min | Someone new could follow it | “I just know” |
| 4 | Check one sample for consistency | 3 min | Same fields, same format | Free-text everywhere |
| 5 | Check the tool connects | 2 min | Native integration exists | Copy-paste only |
| 6 | Mark off-limits data | 2 min | Clear list | “Not sure” |
| 7 | Decide where a human approves | 1 min | One named step | No review step |
| 8 | Define “done” and “good” | 1 min | Measurable | “It feels better” |
1. Pick one task (2 minutes)
Write a single sentence: “When [trigger], the agent should [action] using [data], and [person] approves before [outcome].”
Example: “When a new web inquiry arrives, the agent should draft a reply using our price list and FAQ, and I approve before it’s sent.”
Good first tasks are repetitive, text-heavy and low-risk. If you can’t fill in the sentence, the task is too vague for an agent.
2. Map where the data lives (4 minutes)
List every place the agent would need to look. For the example above: the inbox, a price list (where?), the FAQ (where?), maybe a calendar.
- 1–2 sources: great.
- 3–4 sources: workable if each has an integration.
- 5+ sources, or anything on paper or in your head: fix this first. Consolidate into one sheet or doc.
You don’t need fancy software. A tidy Google Sheet or a built-in store like Zapier Tables works — Zapier Tables triggers and actions don’t count toward task usage (Zapier pricing).
3. Write the process (5 minutes)
Write the steps you actually follow, as if training a new hire:
- Read the inquiry.
- Identify the product or service.
- Look up the price in the price list.
- If it’s a custom job, say we’ll quote within one business day.
- Never promise a delivery date.
- Sign off with name and phone number.
This document becomes the agent’s instructions. IBM notes that agents “require goals and predefined rules defined by humans” (IBM). If you find yourself writing “it depends,” write down what it depends on.
4. Check one sample for consistency (3 minutes)
Open the data source and look at 10 rows or records:
- Are the same fields filled in every time?
- Are dates, prices and names in the same format?
- Are there duplicates or outdated entries?
- Is the important information in a field, or buried in a notes column?
AI handles messy text better than old automations, but inconsistent data still produces inconsistent answers. Accuracy is the top concern for 32% of small-business owners considering agents (Bluehost/ListenLabs, PDF); clean inputs are the cheapest fix.
5. Check the tool connects (2 minutes)
Search the integration directory of the tool you’re considering for each data source. Zapier lists 9,000+ app connections, and n8n includes all its integrations on every plan plus custom HTTP requests for anything else (Zapier pricing, n8n pricing). If your system has no integration and no API, plan to export to a sheet on a schedule.
Not sure which platform? See Zapier vs Make vs n8n.
6. Mark off-limits data (2 minutes)
Write a short “never” list:
- Passwords and logins
- Full card or bank numbers
- Patient, legal or HR records — unless the tool’s plan and agreements are approved for them
Then give the agent the minimum access: one inbox label instead of the whole inbox, one sheet instead of the whole drive. If you handle regulated data, check what each vendor offers. Lindy, for example, offers HIPAA with a signed BAA only on Enterprise, and Claude lists a HIPAA-ready offering only on Enterprise (Lindy pricing, Claude pricing). Self-hosted n8n keeps data on your own server (n8n pricing).
7. Decide where a human approves (1 minute)
Owners consistently want agents that propose and a person who approves with one tap (r/AI_Agents). Name the step and the person: “Sam approves the draft before it’s sent.” Our email assistant recipe shows how to make “draft” the final action.
8. Define “done” and “good” (1 minute)
Pick one number to track for the first month:
- Drafts used without edits, out of the total
- Minutes saved per week
- Errors caught at the approval step
Without a number, it’s hard to tell whether the agent is helping — and agents that aren’t measured tend to get abandoned after launch (r/Solopreneur).
A filled-in example: web inquiries for a small service business
Here is how the checklist reads for the example task above. This is an illustration of the method, not a measured case study.
- Task: draft replies to new web inquiries; owner approves.
- Data map: inbox (Gmail), price list (a PDF on the desktop), FAQ (nowhere — in the owner’s head). Three sources, one of them missing. Red flag on #2.
- Fix: paste the price list into a Google Sheet with columns for item, price and notes; write the 10 most common questions and answers in a Google Doc.
- Process: six steps, written in 5 minutes (see section 3).
- Sample check: price list had two items with old prices — updated.
- Connection: Gmail, Google Sheets and Google Docs all have integrations in the major platforms.
- Never list: customer payment details stay out of the sheet.
- Approval: owner reviews every draft for the first month.
- Metric: drafts sent without edits, out of total.
Score after fixes: 8/8. Before fixes: 5/8.
Scoring
Give yourself one point for each “Ready if…” in the table.
| Score | What it means | Next step |
|---|---|---|
| 7–8 | Agent-ready | Build it this week |
| 4–6 | Almost there | Fix the red flags first (usually #2 and #3) |
| 0–3 | Not ready | Consolidate data and write the process before buying any tool |
The most common fixes
- Scattered data: make one master sheet for the task, even if it duplicates other systems.
- Process in your head: record yourself doing the task once and turn it into steps.
- Messy records: clean the 50 most-used rows; ignore the archive.
- Too much access: create a dedicated label, folder or account just for the agent.
The bottom line
The 20 minutes you spend here decide whether your first agent saves time or creates a mess. Pick one task, get its data into one or two places, write the steps down, fence off what’s sensitive and name the person who approves.
Verdict: Do this checklist before every new agent. It’s free, fast, and the best predictor of whether the agent will work.
Frequently asked questions
What does 'agent-ready data' mean?
It means an AI agent can find the information a task needs, in a consistent format, through a tool it can connect to — and that the rules for the task are written down rather than living in someone's head.
Why do AI agents fail in small businesses?
People who build agents for small businesses most often cite scattered data across five or six tools, undocumented processes, low trust in the agent acting alone, and agents being abandoned after launch.
Do I need a database to use an AI agent?
No. A well-organized Google Sheet, Airtable base or built-in tool like Zapier Tables is enough for most first agents. What matters is consistent columns and one source of truth.
What data should I never give an AI agent?
Avoid passwords, full payment card numbers, and regulated data such as patient health information unless the tool's plan and agreements are approved for it. Give the agent the minimum access the task needs.
How long does it take to get data agent-ready?
The checklist takes about 20 minutes per task. Fixing what it finds can take an afternoon for a simple task or a few weeks if information is spread across many systems.
Prices and features change often. We checked every linked source on the date above; confirm on the vendor's page before you buy. Some links may be affiliate links — see our disclosure.
Get The Tested Agent
One agent recipe a week, in plain English: what it costs, where you approve, what broke. Tuesdays, about a 5-minute read.