Company and lead database
A real-time B2B database of 400M+ verified contacts. Records are verified and refreshed at the point of outreach, not pulled from a cached snapshot.
11x includes a real-time company and lead database of 400M+ verified B2B contacts, built into the platform rather than resold from a third party. The distinguishing property is when verification happens: records are verified and refreshed in real time, with email validation and title confirmation occurring before Alice or Julian uses the record — not at whatever point a provider last refreshed a snapshot.
This is why outreach doesn't reference a role someone left six months ago. A cached database tells you what was true at its last refresh; validating at the point of outreach tells you what's true now.
What the records contain
| Data category | Covers |
|---|---|
| Firmographics | Industry, size, revenue, geography |
| Technographics | Technology stack in use |
| Org charts | Reporting structure and team shape |
| Funding | Rounds, investors, timing |
| Contact details | Validated email and role |
| Hiring signals and job changes | Who's moving, what's being hired for |
| Tech stack data | Adoption and shifts |
Live, not static
| Static list or cached database | 11x database | |
|---|---|---|
| Verification timing | At provider refresh | Before the worker uses the record |
| Email validation | At export | At point of outreach |
| Title confirmation | Whenever the record was written | At point of outreach |
| Signals | A separate product | Built in |
| Commercial model | Data contract, seat licences, expiring list purchases | Included in the platform |
There are no separate data contracts, third-party seat licences, or expiring list purchases to manage. That matters for the cost comparison — see how 11x saves time and money.
Built-in signals
Job changes, tech stack shifts, and funding events are part of the database rather than a separate trigger dashboard, and feed directly into targeting logic. See signals and triggers.
This is a meaningful design difference: you don't monitor a signals dashboard and then act. The signal is already attached to the record your ICP filters run against.
Using it well
Source from the database rather than uploading lists
Uploaded lists bounce, and bounces damage sending reputation faster than almost anything else. See why emails go to spam.
Define your ICP against the available fields
Firmographics, technographics, and role. See ICP and targeting.
Use org charts for ABM motions
Buying-committee coverage depends on knowing who sits where. See playbooks.
Layer your own data where you have an edge
Proprietary firmographic or intent data can be pushed in via the API as custom attributes.
Keep CRM exclusions authoritative
The database supplies who exists; your CRM supplies who you may not contact.
Database coverage is thinner for small and private companies — there is simply less public material. For those segments, lean more on signals and CRM history than on research depth, and set expectations accordingly rather than forcing depth that isn't there.