Scale
Enrich a 60-million-contact CRM
30 million companies. 60 million contacts. Functions, not forked tables.
The loop
- 01Keep HubSpot the source of truthClay is the engine, not a second CRM. ~200 reps with their own licenses.
- 02Enrich once for the whole orgWaterfall across 150+ providers. Same record for email, AE prep, and CS.
- 03Wrap repeats as FunctionsEdit once; every table updates. Stop rebuilding the same chain.
- 04Track ROI per contactStamp source + last enriched. Don’t buy more data until the last batch gets worked.
- 05Curate a workspace, not 1,034 propertiesSync back only fields reps act on. Automate triage the way reps already judge.
HubSpot’s demand-management CRM is roughly 30 million companies and 60 million contacts, with a couple thousand inbound contacts a day. Faris Sumadi’s team came to Clay to experiment in days instead of waiting on data engineering — and to keep experimental data in Clay’s environment so legal stays calm. Around 200 reps each keep their own Clay license. Once that many hands are in one system, the problem is coherence, not coverage.
The operating model is an internal platform. Enrich once so email, AEs, and CS draw from the same record. Wrap the chain you rebuilt twice as a Function. Stamp every contact with source and last-enriched, then stop buying data until the last batch actually gets worked. HubSpot has 1,034 properties on a single contact; reps don’t hunt them — they get a prospecting workspace. The table is a prototype. The Function is the release.
