Every client thread, internal approval, and scheduling exchange is a record of how work moved from request to resolution. Buyers want the sequence, not the sender. With people and companies replaced by consistent fictional values, years of mailbox history show a model how a real business communicates, decides, and follows through.
No dataset needed to start. Buyers price from a one-page manifest; nothing leaves your systems until you sign.
Buyers want the request-to-resolution sequence in a thread, not the sender. Mailboxes with the reply chain intact and the outcome visible do best.
Every record type carries a weight in the estimator behind /estimate, and the weights are published so you can see the work. Email & calendar sits at the middle of the eight.
Indicative range observed across the market for single-company operational data licenses. Not a quote. Actual value depends on buyer demand, data quality, rights, and exclusivity.
Open the estimator →A fictional record, prepared the way a buyer would receive it. The workflow survives. The people, companies, and identifiers do not.
| Field | Your record | De-identified copy |
|---|---|---|
| From | Dana Whitfield <dana@brightline-consulting.example> | Person A <person-a@company-01.example> |
| To | Marcus Oyelaran <m.oyelaran@northgate-logistics.example> | Person B <person-b@company-02.example> |
| Subject | Re: Q3 onboarding scope | Re: Q3 onboarding scope |
| Sent | 2024-07-18 09:42 | 2024-07, week 3, morning |
| Body | Marcus, confirming we can start the warehouse audit on Aug 5. I have looped in Priya from our ops team. Can you send the site list by Friday? | Person B, confirming we can start the warehouse audit on [date]. I have looped in Person C from our ops team. Can you send the site list by [date]? |
Fictional example for illustration. Names, companies, and identifiers are made up; no real record is shown. The signed license specifies the de-identification standard, who performs it, who verifies it, and the remedy if it is missed.
What gets removed, what gets excluded by rule, and what to confirm about your rights. Your counsel signs off on scope before any buyer sees it.
Names, email addresses, phone numbers, and signature blocks are replaced with consistent fictional values, so a thread still reads as one conversation.
Personal mail, HR matters, legal threads, and anything flagged by your counsel are excluded by rule before any sample is built.
Confirm the mailboxes belong to the company (company domain, company accounts) and check client agreements for confidentiality clauses that cover correspondence.
We help you build the manifest and we ask these questions, but we do not provide legal advice. Whether a specific set of records can be licensed is a decision for your counsel.
Client onboarding, project delivery, reusable methods.
Matter workflows, document drafting, review and approval trails.
Reconciliation, close checklists, approvals, client correspondence.
Briefs, creative review, client approvals, campaign ops.
Transaction coordination, leasing, maintenance workflows.
Buyers evaluate a small de-identified sample you approve, then train on the licensed copy as a whole. Nobody is reading your mail for its own sake. What the model learns is the pattern: how a request is phrased, who it goes to, what gets asked back, and how it closes.
They are excluded by rule. The preparation step filters out mail that is not about company business, along with HR, legal, and medical topics, before a sample exists. You review the rules and the sample before anything is licensed.
You pick. Most sellers include the shared and operational mailboxes (sales, support, projects, accounts) and a set of individual accounts whose owners agree. The manifest records which mailboxes and date ranges are in scope, and the license covers only those.
Seven questions. No dataset. First offer in 24 to 48 hours of a complete manifest.
Measured from a complete data manifest. A first offer is a process target, not a guarantee; buyers decide eligibility, price, and terms.