What qualifies
Everyday data from the tools your team already runs.
AI labs license genuine business records to train and test their models. Those records usually come from systems like these.
Get my estimateWhy some records matter more
Genuine work, over time
Labs are not looking for polished marketing copy. They want the everyday record of a business doing its job: questions, revisions, handoffs and the reasons for decisions.
- A history that goes back several years.
- Work kept in consistent business systems, not scattered personal files.
- Real exchanges between people, not only final documents.
- Records your company owns and controls.
In practice
What a useful record looks like
A help desk case where a customer reports an issue, a tech asks two more questions, tests a fix and closes it with a note. A project board where a task is opened, reassigned, blocked, discussed and finally shipped. An email thread where a quote is drafted, challenged, revised and accepted.
None of these is special by itself. Together, over years, they show the judgment and routine that keep a business running. That is what labs cannot find on the open web.
What a license never includes
Anything you do not approve. On top of that, personal details, account numbers, health information and other sensitive data can be excluded or de-identified before sharing. Client and patient data in regulated practices stays out.
See our safeguards page for more.
Common questions about records
- Do our records need to be cleaned up first?
- No. Labs want ordinary, everyday records. Scoping decides what is included and what is removed.
- What if our history is spread over old and new tools?
- That is common. Tell your specialist which tools you used and for roughly how long, and scope can cover more than one.
- Could we include just one department?
- Yes. Scope can be as small as one team, one system or one date range.
Not sure which systems count?
See my estimateSystems that often qualify
Which ones are included is your call.
Email
Customer threads, supplier back and forth and internal coordination. Email shows how requests are understood, negotiated and resolved over days or weeks.
Docs and shared drives
Procedures, proposals, templates, checklists and project documents. These capture how the business explains its work to its own people.
Team chat
Channels and threads where people ask for help, hand off tasks and settle small decisions quickly.
CRM
Account notes, pipeline history and follow ups that track a customer relationship from the first contact on.
Service tickets
Each ticket is a small story: a question, the steps taken, and how it was closed.
Project tools
Boards, tasks, comments and status changes that show how work gets planned and delivered.
Finance and operations
Approval, ordering and purchasing processes. Account numbers and other sensitive values stay out.
Code repositories
Repositories, pull requests, code review comments and change history from software your team built and maintains.
Find out what your records could be worth
Your starting range comes from team size and years in business.
Find out what my data is worth