NewYour AI employee is one email away →

Your Data Is Not AI-Ready: What to Fix First

Published Updated

Most data is not AI-ready because context is missing, not storage. Run a 5-question AI readiness assessment per job and start this week.

If your company data is not AI-ready, you usually do not need a data warehouse project before you start. Most “not ready” data is a context problem, not a storage problem: the numbers exist, but nobody wrote down which spreadsheet is current, what a status means or who decides. The practical fix is to run a small AI readiness assessment per job instead of per company: pick one recurring task, connect only the two or three systems it touches, write a one-page context note, and run it in parallel with the person who does it today. Reachable systems beat a perfect data platform, and most teams can start this week.

What should you fix first? The order that works

Fix the data in this order, and only for the job you are starting with:

  1. Scope one use case and list the data it touches. First, because it shrinks the problem from “all company data” to two or three systems. Effort: an hour.
  2. Agree on the source of truth for each number. Second, because no amount of cleaning helps if finance and sales trust different figures. Effort: one meeting.
  3. Write down definitions and exceptions. Third, because missing definitions, not dirty rows, cause most wrong AI answers. Effort: half a page, an afternoon.
  4. Set access and protect sensitive data. Fourth, because the AI should reach only what the job needs, and personal data must be masked or excluded before it is connected. Effort: a day with your IT or compliance owner.
  5. Clean what the job touches. Fifth, because by now you know exactly which duplicates, gaps and stale records matter. Effort: days, not quarters.
  6. Unify silos and harden pipelines. Last, because it is the most expensive fix and only pays off once several jobs depend on the same data.

Most teams can do steps 1 to 4 in a week and start the first job while step 5 continues.

Why does everyone say their data is not AI-ready?

Because the standard advice says so. The enterprise answer from data platform vendors and analysts is to consolidate, clean and govern your data before you use AI. For a large model-training project, that is right. For giving an AI employee real work, it is often the reason nothing happens for a year.

The research shows how common the feeling is. In a Wakefield Research study of 1,000 technology leaders published by Teradata in July 2026, 77% said 20% or less of their enterprise data and knowledge is ready for AI agents to use reliably, and 78% said they struggle to unify data across business functions.

But “unified enterprise data” is not what a single job needs. A weekly ad-spend report needs the ad accounts and a spreadsheet of targets. Invoice chasing needs the accounting tool and email. Each job touches a small slice of the company.

What does “AI-ready data” actually mean?

For an AI employee doing a specific job, data is ready when three things are true:

  1. It is reachable. He can access the system through an integration, an export or a browser, with the right permissions.
  2. The source of truth is agreed. Everyone accepts which system or file holds the correct number.
  3. The meaning is written down. Definitions, exceptions and the format of a good result exist somewhere he can read.

Notice what is missing: perfectly clean records, a single warehouse, a data catalogue. Those help, but they are not the threshold for starting.

How do you run an AI readiness assessment for one job?

Score the job, not the company. Use this five-question assessment for any recurring task:

Question

Ready

Not yet

Is the task done manually today, on a regular schedule?

Yes, weekly or monthly

Rarely, or nobody owns it

Can the systems it touches be reached?

Integrations, exports or browser access exist

On-premise with no API or export

Is there one agreed source of truth?

Yes

Teams dispute the numbers

Can someone explain a good result in half a page?

Yes

It lives only in one person’s judgment

Are compliance limits known?

Checked with the owner

Nobody has asked

Four or five “ready” answers: start now. Two or three: fix the gaps for that job only. One or none: pick a different job first.

How do you get from messy data to a working job in one week?

  1. Choose one recurring job a person handles manually today: invoice chasing, the ad-spend report, a pipeline hygiene pass.
  2. List only the systems that job touches. Usually two or three. Ignore the rest of the company for now.
  3. Connect them and set access at the same time. Give read access first, and decide which actions need approval.
  4. Write the context page. Source of truth, definitions, exceptions, output format, and what is never allowed.
  5. Run it in parallel for two cycles. The AI employee produces the result; the person who used to do it compares. Differences reveal missing definitions, not failure.
  6. Make it repeatable. Once two cycles match, schedule it so it runs on its own.

What should the context page include?

Half a page is normal. For a weekly paid-media report it might say:

  • Source of truth: spend from the ad platforms, revenue from the billing system, targets from the “Q4 targets” sheet.
  • Definitions: “CAC” means paid spend divided by new paying customers in the same week; exclude refunds.
  • Exceptions: brand campaigns are reported separately; ignore test accounts.
  • Output: five bullets and one table, posted in #marketing every Monday by 9:00.
  • Never: change budgets or pause campaigns without approval.

This page does more for AI readiness than months of cleanup, because it captures the knowledge that was only in someone’s head.

Why do most AI projects fail on data?

Not usually because the data is dirty. They fail because the project starts with the data instead of a job: a team spends quarters on a warehouse or a data lake, no business process changes, and the sponsor loses patience. Gartner predicted in 2024 that at least 30% of generative AI projects would be abandoned after proof of concept by the end of 2025, citing poor data quality, inadequate risk controls, escalating costs or unclear business value. Starting from one job with an owner and a measurable result avoids most of those traps.

How do you keep sensitive data and PII safe?

  • Connect the minimum. Give the AI employee access only to the systems and fields the job needs, read-only at first.
  • Exclude or mask personal data that the job does not need, such as personal emails, national ID numbers or health information, at the source or in the export.
  • Require approval for actions that send data outside the company, such as emails to customers.
  • Check the vendor: where data is processed, whether it is used to train models, retention, and security certifications.
  • Log everything so you can see who asked for what and what was accessed.

How should you prepare documents and unstructured data?

For an AI employee reading documents on demand, keep the current version in one known place, name files clearly, remove outdated copies and note on the context page which document is authoritative. If you are building your own retrieval (RAG) system, the extra steps are splitting documents into sections, adding metadata such as owner, date and document type, removing duplicates and personal data, and re-indexing when documents change. Structured data needs agreed definitions; unstructured data needs clear versions and ownership.

A worked example: the weekly revenue report

A 40-person company wanted an AI employee to produce its weekly revenue report. The data was “not ready”: revenue lived in the billing system, the CRM had duplicate accounts, and the targets sat in a spreadsheet three people edited.

  • Before: the first AI draft showed revenue 8% higher than finance’s number, because it counted refunded invoices and both copies of duplicated accounts.
  • Fixes, in order: finance was named the source of truth (one meeting); the context page defined revenue as paid invoices minus refunds (one afternoon); access was set to read-only billing and CRM (one hour); the 30 duplicate accounts the report touched were merged (two hours).
  • After: the second run matched finance to the dollar. After two matching weeks, the report was scheduled for Monday mornings, and the rest of the CRM cleanup continued in the background.

Where does team chat history fit in?

A lot of operational context already lives in Slack or Teams threads: why a number changed, which client is special, what was decided last quarter. An AI employee who works in those channels can use that history as context, within the permissions you set, instead of everyone re-explaining it. For a deeper checklist, see the AI employee readiness checklist.

When is the data genuinely not ready?

Some walls are real. Fix these first, or pick another job:

  • Disputed source of truth. If finance and sales disagree on the correct number, settle it between people first.
  • No access at all. A system with no API, export or web interface cannot be read.
  • Unrecorded inputs. If the input exists only in someone’s judgment, there is nothing to read until it is written down.
  • Unchecked regulation. Confirm with your compliance owner which systems and data types are in scope before connecting them.

What if our information lives in spreadsheets and PDFs?

That is normal and usually fine. AI can read spreadsheets, documents and PDFs directly. What matters is knowing which file is current and what the columns mean, which goes on the context page.

Do we need a data warehouse before using an AI employee?

  1. A warehouse helps with company-wide analytics and becomes valuable as you scale, but most single jobs run on the operational systems you already have. Many teams find their first AI jobs show them which data is worth consolidating.

How do you know the AI is getting the numbers right?

Run in parallel with the current owner for two cycles, compare line by line, and keep a person approving outputs until the results match consistently. Ask the AI employee to show his sources and calculations in each report.

How should leadership judge AI readiness?

Per job, not per company. Your invoice data can be ready on Monday while product analytics stays messy for another year. Track how many recurring jobs pass the five-question assessment and how many run with an AI employee, instead of waiting for a single company-wide “ready” date.

Frequently asked questions

What is an AI readiness assessment?

A check of whether a task, team or company can use AI effectively. For practical adoption, the most useful version scores individual recurring jobs on access, source of truth, documented context and compliance.

How much data cleanup is enough?

Enough that the job’s source of truth is agreed and its rules are written down. Clean what that job touches, not everything.

Does messy data make AI make things up?

Messy data leads to wrong answers when definitions are missing. A context page, source citations and a parallel run catch most of these before anyone relies on the output.

Who should own the context page?

The person who does the job today, with sign-off from the manager who uses the result.

Start with one job

Viktor is an AI employee who works in Slack and Microsoft Teams, connects to 9,800+ tools and asks before sensitive actions. Pick one recurring job, connect its systems and see the first result this week. Learn what an AI employee is or start free.

Ask ChatGPTAsk Claude
4.8 on G2G2 rating: 4.8 out of 5 stars

Start free. Viktor delivers.

Start for free today. No credit card required.

Get Started for Free