Customer success records: onboarding, QBR transcripts and renewals
Summary
Seven years of customer success work at one vertical SaaS company: CSM email, onboarding and quarterly business review call transcripts, health scores, success plans and renewal outcomes for about 2,900 business accounts. Each account carries a timeline, so a model can see the warning signs months before a churn or an expansion. Customer and contact identities are replaced with consistent placeholders, call audio is dropped and contract values are removed.
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
- 3.3Memails, call transcripts and success records
- Size
- 10 GB
- Tokens, estimated
- 1.1B
- Years
- 2019 to 2026
- Firms
- 1
- Owner profile
- US vertical SaaS company selling property operations software to commercial landlords and managers, 150 to 300 staff
- Industry
- Software
- Data type
- Sales and CRM
- Headcount
- 150 to 300 staff
- Region
- United States
- Languages
- English
- Formats
- JSONL, Parquet
- Updated
Sources
| System | Kind | Records |
|---|---|---|
| Google Workspace mail | 2.84M emails | |
| Zoom transcripts | Call transcripts | 38,600 call transcripts |
| Gainsight | CRM | 412K health scores, CTAs and success plan tasks |
| HubSpot record exports | CRM | 2,910 accounts with renewal history |
Good for
- predicting churn and expansion from account timelines months before renewal
- training CSM agents to prepare QBR briefs from email, calls and health data
- evaluating meeting summaries and action items against the CSM's own follow-up
- learning onboarding playbooks that get a new account to first value
Fields
| Field | Type | Description |
|---|---|---|
| event_id | string | De-identified event id |
| account_code | string | De-identified customer account |
| segment | enum | SMB, mid-market or enterprise |
| event_type | enum | email, call transcript, health change, CTA or renewal |
| occurred_at | timestamp | When the event happened |
| csm | string | De-identified CSM |
| health_score | int | Account health from 0 to 100 at the time of the event |
| text | string | Email body, transcript or note text |
| renewal_outcome | enum | renewed, expanded, contracted, churned or pending |
Example record
{
"event_id": "CS-0061177",
"account_code": "[ACCOUNT_1408]",
"segment": "mid-market",
"event_type": "call transcript",
"occurred_at": "2024-09-12T15:00:00Z",
"csm": "[PERSON_19]",
"health_score": 54,
"text": "[PERSON_19]: Work order volume is down about a third since June. What changed? [PERSON_77]: We lost two buildings in [CITY_4] and the new site leads still log requests by email. [PERSON_19]: Let's get the three site leads on a 30-minute session next week and turn on the email-to-work-order inbox so nothing gets missed.",
"renewal_outcome": "renewed"
}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.