Catamount Data documentation
Field definitions, measured coverage, sourcing methodology and stated limitations for a database of 8,594 Web3 industry contacts.
Most contact-data vendors publish a headline number and nothing else. This documentation publishes the counts behind every field, explains how each one is populated, and states plainly where the data is weak. Every figure here was measured against the live database, not estimated.
Start here
Quickstart
From a downloaded CSV to your first conversation in about twenty minutes. Filtering, channel choice, and what to actually write.
Guides
Choosing a channel
When X beats LinkedIn beats Telegram, decided per contact rather than per campaign.
Verifying a Telegram handle
The thirty-second check that stops you messaging a stranger.
Reference
Data dictionary
Every field, what it means, how it is populated, and how many records have it.
Coverage report
Measured field coverage across the master list and each vertical.
Methodology
Where contacts come from, how they are enriched, and what "verified" does and does not mean here.
The database at a glance
| Measure | Value |
|---|---|
| Unique contacts | 8,594 |
| Reachable on at least one channel | 8,549 (99.5%) |
| Reachable on two or more channels | 7,152 (83.2%) |
| X (Twitter) handle | 8,503 (98.9%) |
| LinkedIn profile | 6,046 (70.4%) |
| Telegram handle | 2,709 (31.5%) |
| Role | 6,411 (74.6%) |
| Company | 5,866 (68.3%) |
| X biography text | 6,729 (78.3%) |
| Duplicate X handles | 0 |
What this database is
Catamount Data is a database of people who registered for Web3 industry events — conferences, side events and mixers — and supplied their social profiles as part of registering. It is organised into nine role-based verticals plus event-specific lists, and is sold as CSV downloads.
The people in it are practitioners: founders, business development leads, engineers, investors, marketers and community managers at crypto and Web3 companies. The most common single role is Founder.
What it is not
- It is not an email list.
- No email addresses are sold or included. Contact is made through social channels.
- It is not identity-verified.
- Names and social handles are as supplied by the person, then enriched from public profiles. See Methodology for exactly what is and is not checked.
- It is not a lead-scoring product.
- There is no intent data, no firmographic enrichment beyond company and role, and no predicted propensity to buy.
- It is not exhaustive of Web3.
- Coverage reflects the events that were ingested. It skews toward conference-attending professionals, which is a real selection effect and a deliberate one.
Answers to common questions
How many contacts are in the Catamount Data database?
8,594 unique contacts, deduplicated by X handle, with zero duplicate handles across the master list.
What percentage of contacts have a Telegram handle?
31.5% (2,709 of 8,594). Those handles are inferred rather than confirmed — the methodology page explains precisely how, and what that means for reliability.
What percentage have LinkedIn?
70.4% (6,046 of 8,594).
How current is the data?
Contacts are added continuously as new events are ingested. Profile enrichment is re-run periodically rather than in real time, so a person's company or role reflects their public profile at the time of last enrichment, not necessarily today.
Can the data be accessed programmatically?
Not currently. Delivery is by CSV download through the buyer portal. An API is under consideration.