SaaS sales team archive: CRM history, deal email and call transcripts
Summary
Ten years of the sales record of one B2B SaaS company: CRM opportunities with stage history, the email threads behind each deal and transcripts of discovery and demo calls. Deals can be followed from first meeting to closed won or closed lost, with the rep's notes on why. Prospect names, emails, phone numbers and company names are replaced with consistent placeholders, contract values are removed and call audio is dropped.
Collected to order. We collect it from US companies for your order. Scope, volume and timing are confirmed in writing before you sign.
Pricing on request
Request scope and pricingAt a glance
- Planned scope. Volume, sources and timing are confirmed in writing before you sign.
- Records
- 6Memails, CRM activities and call transcripts
- Size
- 15.2 GB
- Tokens, estimated
- 1.6B
- Years
- 2016 to 2025
- Firms
- 1
- Owner profile
- US B2B SaaS company selling field scheduling software to mid-market service businesses, 50 to 150 staff
- Industry
- Software
- Data type
- Sales and CRM
- Headcount
- 50 to 150 staff
- Region
- United States
- Languages
- English
- Formats
- JSONL, Parquet
- Updated
Sources
| System | Kind | Records |
|---|---|---|
| Salesforce | CRM | 41K opportunities, 1.38M activities |
| Google Workspace mail | 4.62M emails | |
| Zoom transcripts | Call transcripts | 21,400 call transcripts |
Good for
- training sales agents to write follow-ups that fit the deal stage and the buyer's last objection
- forecasting deal outcomes from stage history, email cadence and call content
- evaluating call summaries against the rep's own CRM notes
- learning objection handling from real discovery and demo calls
Fields
| Field | Type | Description |
|---|---|---|
| opportunity_id | string | De-identified opportunity id |
| account_code | string | De-identified prospect account |
| segment | enum | SMB, mid-market or enterprise |
| created_at | timestamp | When the opportunity was created |
| stage_history | array<string> | Each stage with the date it was entered |
| outcome | enum | closed_won, closed_lost or open at export |
| loss_reason | string | Rep-entered reason, if lost |
| seats | int | Seats in the final proposal |
| linked_emails | int | Count of email records linked to the deal |
| call_transcript | string | Speaker-labeled transcript of the linked call (excerpt in the sample) |
Example record
{
"opportunity_id": "OPP-0029114",
"account_code": "[ACCOUNT_812]",
"segment": "mid-market",
"created_at": "2023-01-09T17:40:00Z",
"stage_history": [
"Discovery 2023-01-09",
"Demo 2023-01-24",
"Proposal 2023-02-15",
"Closed lost 2023-03-30"
],
"outcome": "closed_lost",
"loss_reason": "Stayed with incumbent. [PERSON_40] liked our dispatch board but IT would not approve a second vendor this year.",
"seats": 85,
"linked_emails": 37,
"call_transcript": "[PERSON_40]: Our techs live in the mobile app, so if offline mode is shaky we're dead in the water. [PERSON_6]: Fair. Offline sync queues every job update and pushes it when signal comes back. Want me to show it with airplane mode on?"
}Licenses available
Exclusive
One buyer. Nobody else can license it during the exclusive term, usually 2 years.
Non-exclusive
Licensed to more than one buyer.
First look
One buyer gets 2 to 4 weeks to make an offer before anyone else sees the dataset.
What ships with it
- Datasheet: what it is, what it is good for, verified size, sources, years, format and limits.
- Provenance file: the owner shown by code, staff notice and consent status, exclusions, mapped to the EU AI Act Article 53 training-data summary and California AB 2013.
- Manifest with a hash for every file.
- QC report and de-identification report.
- Your own copy, with unique canary records.
How it is de-identified
Default exclusions removed, files flattened to text, identifiers found in three layers and replaced with consistent placeholders, and the result measured against a 99% bar for each identifier type in each source.