Home / Guides / Data you need first

Before you build: the data you need.

An agent is only as good as what it learns from and what it can reach. Most delays and most wrong answers trace back to one of six missing inputs.

Short answer

Before an AI agent is built you need six things: real examples of the work (for instance 50 to 100 recent conversations or documents, anonymised where needed), the approved answers, prices and policies it may use, access to the systems it must read or write, a list of edge cases that must go to a person, one owner who approves content, and one measurable target. Just as important is what you leave out: under the GDPR's data-minimisation principle, the agent should only get the personal data it actually needs.

The six inputs

What to collect.

01Real examples

Recent emails, chats, calls or documents, covering the normal cases and the awkward ones.

02Approved knowledge

FAQs, price lists, terms, preparation instructions, tone of voice: the only sources the agent may answer from.

03System access

Which inbox, calendar, CRM or ERP, with the least access that does the job.

04Edge cases

Complaints, refunds, legal or medical topics, VIPs: the list that always goes to a person.

05One owner

The person who signs off answers and decides when the agent is wrong.

06One target

Response time, hours saved or documents processed: a number to judge it by.

Readiness check

Are you ready? A quick test.

QuestionReady if…Not ready if…
Can we find 50 real examples in a day?They are in one inbox or systemThey are spread over personal phones
Is our price list current?One source, updated this quarterThree versions in three places
Do we know who approves answers?A named person with time"Everyone" or nobody
Does the software have an API on our plan?Yes, or we have checkedUnknown
Do we know what personal data is needed?A short list of fields"Everything, just in case"
Leave it out

Data the agent should not get.

Less data makes the build faster and the privacy questions easier.

Full customer histories when the agent only books appointments
Health, financial or ID documents unless the process truly needs them
Personal inboxes when a shared mailbox will do
Old exports kept 'just in case'
Measuring

Record the baseline now.

Write down today's numbers before the build: how long a reply takes, how many items per week, how many hours. The NIST AI Risk Management Framework calls this measuring against intended purpose; in plain terms, without a baseline nobody can say whether the agent helped.

Note

Not legal advice.

This guide is general information, checked against the sources listed, and not legal advice. Rules change; check the current text or ask a lawyer before you rely on it. Checked November 2026.

FAQ

Common questions.

Do we need a data warehouse first?

No. Most first agents connect directly to an inbox, calendar or CRM. A warehouse helps for reporting across many systems, not for a first agent.

Do you train a model on our data?

Usually not. The agent uses a general model and looks up your approved content at the moment it answers, which keeps your data out of model training.

What if our data is messy?

Then the first step is fixing the few sources the agent needs, not all of them. The Data Readiness service exists for exactly this.

How many examples are enough?

Enough to cover the common cases and the known edge cases. For a front desk, a few weeks of messages usually is.

Free 30-minute audit

Want this in your business?

Tell us how you work today. We'll tell you honestly what AI can take off your team's plate, what it costs, and whether we are the right fit.