> For the complete documentation index, see [llms.txt](https://docs.11x.ai/llms.txt).
> Use it to discover all available pages before exploring further.

# 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.

<Callout kind="tip">
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.
</Callout>

## 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 |

<Callout kind="info">
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](/help-center/overview/how-11x-saves-time-and-money).
</Callout>

## 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](/data/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

<Steps>
  <Step title="Source from the database rather than uploading lists" icon="database">
    Uploaded lists bounce, and bounces damage sending reputation faster than almost anything else. See [why emails go to spam](/help-center/deliverability/why-emails-go-to-spam).
  </Step>
  <Step title="Define your ICP against the available fields" icon="crosshair">
    Firmographics, technographics, and role. See [ICP and targeting](/alice/icp-and-targeting).
  </Step>
  <Step title="Use org charts for ABM motions" icon="network">
    Buying-committee coverage depends on knowing who sits where. See [playbooks](/alice/playbooks).
  </Step>
  <Step title="Layer your own data where you have an edge" icon="upload">
    Proprietary firmographic or intent data can be pushed in via the [API](/integrations/webhooks) as custom attributes.
  </Step>
  <Step title="Keep CRM exclusions authoritative" icon="ban">
    The database supplies who exists; your CRM supplies who you may not contact.
  </Step>
</Steps>

<Callout kind="alert">
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.
</Callout>

## Frequently Asked Questions

<Expandable title="Why is volume lower than expected for our ICP?">
The segment may be genuinely small, or a filter is narrower than intended. Widen one dimension at a time and check the count at each step.
</Expandable>

<Expandable title="Why are we getting bounces despite real-time validation?">
Check whether those contacts came from the database or from an uploaded list. Uploaded lists are the usual source.
</Expandable>

<Expandable title="Why are contact titles out of date?">
Titles are confirmed before use, so a stale title suggests the contact came from an upload or from your CRM rather than the database.
</Expandable>

<Expandable title="What if database coverage is poor in a specific region?">
Regional coverage varies. Raise it with your 11x representative rather than assuming a configuration problem.
</Expandable>

<Expandable title="What if we have better data than the database for our niche?">
Push it in via the API as custom attributes and use it in your ICP filters. A specialized proprietary source is a legitimate reason to keep your own data alongside.
</Expandable>

## Next steps

<Columns cols={2}>
  <Card title="Signals and triggers" icon="radar" href="/data/signals-and-triggers" horizontal>
    Built-in signals, and custom definitions.
  </Card>
  <Card title="Website visitor tracking" icon="eye" href="/data/website-visitor-tracking" horizontal>
    Identifying anonymous traffic.
  </Card>
  <Card title="ICP and targeting" icon="crosshair" href="/alice/icp-and-targeting" horizontal>
    Filtering the database down to your segment.
  </Card>
  <Card title="Deep research" icon="search" href="/alice/deep-research" horizontal>
    What happens once a prospect is selected.
  </Card>
</Columns>