Skip to content

Enrichment

Buy the data domains your business actually needs. Nothing else shows up.

A health-tech team turns on a health-data provider and never sees an insurance field; an insurance brokerage does the opposite. Every enrichment result sits beside the capture it came from, clearly labelled with who supplied it and when — never confused with what your rep actually saw, and never pushed to your CRM without your say.

Per-domain, not a race between providers

Enable a provider from a catalogue tagged by domain — firmographic, verification, health, insurance, and whatever comes next — and supply that provider's own credentials. Nothing you haven't enabled ever runs, and nothing appears in your UI for a domain you never turned on. Two providers in the same domain never race to fill the same field first; that's a different, harder problem this phase deliberately doesn't solve.

Enable providers by domain, each with its own credentials
See every field a provider can return, and whether a miss still costs you, before you turn it on
Disabling a provider stops new calls immediately, without deleting what it already found
A workspace enables two of four provider domains; only the enabled domains route a capture to a call
Two domains enabled, two left off. Enrichment only ever runs for what a workspace actually turned on.

Run it once automatically. Run it again on purpose.

A new capture enriches automatically, once, shortly after it's saved — never blocking the capture itself, and never re-run later on a timer nobody asked for. When you have an actual reason to look again — a provider you just enabled, a lead worth a second look — re-enrich it explicitly, one record or a whole batch, and the earlier result stays exactly where it was rather than being overwritten by the new attempt.

Automatic, once, right after a capture is saved — no recurring background refresh
An explicit "Re-enrich" action for one record, or a bounded batch for many
Five distinct states, so a genuine miss never looks like an outage
Five distinct request states: queued, running, found, not found and failed — never a shared didn't-work shape
Queued, running, then one of three honest outcomes — found, genuinely not found, or failed.

When two providers disagree, you see both

A purchased value never overwrites what your rep captured — not automatically, not on auto-approve, not ever. If two enabled providers return different values for the same field, both are shown, each with its own provenance, and neither is silently merged or picked for you. Pushing any value to your CRM goes through the same approved, mapped write path every other change already uses, and whether it overwrites an existing CRM value is governed by an explicit per-field policy your admin sets — never an implicit default buried in enrichment logic.

Conflicting provider values shown side by side, never auto-merged
Promotion uses the same approval gate as every other CRM write — human, or an audited auto-approve you turn on per connection
Never / fill-if-empty / always — one explicit overwrite policy per field, defaulting to never touching what's already there
Two providers' conflicting values for one field, shown side by side with their own provenance, both reaching one approval gate
Two providers, two provenance-labelled values, one approval gate. Neither value is picked for you.

What this doesn't do yet

Worth knowing before you switch, rather than after.

  • No multi-provider waterfall. Enabling two providers in the same domain runs both — it does not race them for one field or pick a winner. That kind of ranking isn't built this phase.
  • No scheduled re-enrichment, ever. A record is enriched automatically once. Anything after that is a deliberate, costed action you take — never a timer running in the background.
  • A provenance mark never reaches your CRM field. We keep who supplied a value and when, permanently, on our side. That detail doesn't get written into your CRM property alongside the value itself — no vendor in this market solves that, and we don't pretend to either.
  • No self-serve creation of a CRM field that doesn't exist yet. If your CRM object has nowhere for a field a provider returns, that field waits for you to add it on your CRM's own admin console. We don't create destination schema on your behalf this pass.
  • No credit system. Cost is tracked in real cents per call, visible per provider and per period. There's no bundled-credit abstraction to buy into.

Turn on what you need. Review what comes back. Push only what you approve.

Enrichment is priced per provider you enable — there's no separate platform seat for it.