For AI labs, model developers and research teams
AI training data
from real businesses.
License the record of how work gets done: the context, decisions, exceptions and outcomes. Review a de-identified sample before agreeing the scope and permitted use.
- De-identification scope agreed in writing
- Rights reviewed per supplying company
- Availability subject to review
Send a data brief
We review your brief for a possible partner introduction. Any sample depends on availability, a rights review and agreed confidentiality terms.
The workflow is the value.
Preserve the sequence: what happened, why, and what followed.
Illustrative structure, not an available dataset. Supply depends on what suppliers approve.
What's available
The mix changes as suppliers join. These are the categories we see most.
Work conversations
Threads where problems are raised, argued over and settled, with the people and the reasoning still attached.
Operations & finance
Orders, invoices, reconciliations and ledgers, including the odd cases that never fit a template.
CRM & customer support
Pipelines, account history and tickets, plus the service knowledge that built up around them.
Documents & knowledge
Contracts, reports, procedures and playbooks, with the revision history that shows how they changed.
Tasks & project work
Tickets and projects captured end to end: the brief, the discussion, the handoffs and the result.
Sectors we're sourcing
Potential sectors include the fields below. Availability changes as suppliers join and is always subject to review.
How a licence works
You define the use
Training, evaluation or both, and the model types in scope.
The supplier approves the scope
Nothing ships beyond what they have agreed to share.
Terms are signed first
Permitted use, duration and re-identification limits are written down.
Data is delivered and tracked
Delivery follows the signed scope, with a record of what was shared.
Questions
No. It comes from real operating systems at real businesses. Where a supplier has generated or modelled data, we say so up front.
Direct identifiers are removed before review and the licence limits re-identification. De-identification reduces risk but cannot promise anonymity, so the terms address it explicitly.
No. You receive a licence for a defined scope, use and term. The supplier keeps ownership.
Pricing depends on volume, rights and exclusivity. Share a budget band if you can; "not sure" is a fine answer.
Yes. Exclusions are part of the scope, for example direct messages, attachments, regulated categories or named customers.
The supplier approves what is shared, and we check rights and de-identification before any sample reaches you.
After the brief is reviewed and an NDA is signed. The timing depends on the supplier and the redaction work.