Find · Enrichment
There are no enrichment buttons, because there is nothing left to press
Both lead paths enrich before the write. A corpus pull reveals every candidate before the import; the LinkedIn sweep reveals every gate-passed lead by profile URL before the contact insert. Only people an address came back for become contacts, so your list never holds anyone you cannot write to.
| Name | Title | Company | Status | Intent | Industry | Size |
|---|---|---|---|---|---|---|
| PRPriya Raghavan | VP Revenue Ops | Northwind | Queued | 5Burning | Financial Services | 240 |
| DODaniel Okoye | Head of Demand Gen | Cadence | Queued | 4Hot | Software | 90 |
| MLMara Lindqvist | Director, Sales Dev | Fernweh | Queued | 4Hot | Software | 60 |
| ABAisha Bello | CRO | Threadline | Booked | 5Burning | Retail Tech | 410 |
| THTomás Herrera | Founder | Halyard | New | 3Warm | Logistics | 24 |
| EMElena Marchetti | VP Marketing | Sablefish | New | 2Cold | Fintech | 130 |
| JWJonas Weber | GTM Lead | Kestrel | New | 1Cold | Software | 45 |
| RCRavi Chandran | Head of Growth | Loomis | New | 1Cold | Marketplaces | 310 |
What is actually going on
Every claim below is followed by the mechanism under it, because a claim without a mechanism is a slide.
Synchronous, not a webhook you wait on
The reveal answers in the same request. Nothing writes a pending state, nothing polls, and a tripwire test in the suite fails the build if any path tries to.
The search context travels with the contact
An id resolves against the population the filters describe, so enriching without them reveals a different person and charges for it. The import stores the search context on the contact, because a backstop reveal can run days later and by then it is the only thing that makes their id mean anything.
One vendor, on purpose
A person the corpus does not hold is simply not imported, rather than sent to a second provider for a second bill. The exception is deliberate and narrow: a high-intent lead is worth a second source in a way a cold one is not.
Suppression is checked at the reveal
On every path but hiring, the reveal is the first instant an address or a domain exists to match against a list. A suppressed person is not imported at all rather than imported and flagged.
Step by step
How enrichment runs
- 1
Translate
Provider-internal member-id URLs are resolved through your own connected account first.
- 2
Reveal
The corpus is asked by profile URL, in batches of 100, and retries its other corpus on a miss.
- 3
Charge
Every reveal is metered and balance-checked against the ledger before the batch runs.
- 4
Report
A lead the corpus could not answer for is counted and named on the run, and retried the next time the sweep sees them.
The numbers
Facts, not adjectives
Every figure here is a real value from the running product. A cadence from the scheduler, a price from the credit table, a limit from the ramp. A marketing page that invents a limit is a support ticket with a delay on it.
- Metered as
- enrich.reveal, 30 data credits
- Latency
- Same request. No pending state
- Batch size
- 100 candidates
- Returned
- Email, phone where held, title, company
- Dedupe key
- LinkedIn profile URL
Enrichment, honestly
Am I charged for a miss?
No. Cache hits and reveals that spent nothing at the vendor are free. You are charged per person the vendor actually billed for.
What about contacts that predate this rule?
The launcher buys anything missing after the intent hold and before the send, then parks the row if the reveal still comes back empty. Rather than asking the same vendor the same question every hour.
Find
Who to talk to, and when they got warm
Keep reading
All featuresEnrichment is one part of it. The rest runs too.
Sourcing, enrichment, intent, copy, sending, replies and reporting are one product with one bill and one gate. Connect a channel and the whole motion starts.
Start with sales. $2,000 or $5,000 onboarding, then at least $250 monthly credit funding.