Enrichment
Fill missing fields from a data provider, to a ceiling you set.
Fields nobody ever filled in. Industry, revenue and headcount are blank on most of the book, because they were never required at entry and nobody has gone back. Every segment built on them silently excludes the records that are missing them.
Enrichment fills what is missing rather than overwriting what is there. That distinction is the whole configuration: for each field you map, you decide what should happen when the CRM already holds a value.
A mapping is provider field to CRM field, plus a rule. Fill only when empty is the conservative default and the one most teams want. Overwrite is available for fields where the provider is more trustworthy than the record.
Spend is bounded by the run, not by the configuration. A credit cap belongs to the run because it is a decision about this pass, not a property of the mapping. A run stops at its cap rather than spending to the end of the scope.
How a pass runs
The detail
Cost
Which is why the preview is the first thing this tool offers.
Searching a provider costs nothing. Enriching a record costs a credit. The preview walks the scope and tells you how many records are actually missing the fields you asked for, which is almost never the same as how many records are in scope.
The cap is a ceiling rather than a target. A run set to five hundred stops at five hundred and reports what it did not reach, rather than quietly spending to the end of the book.
For agents
Reads are free and need no permission to write. Anything that changes a record is a separate grant.
preview_enrichment_run what it would fetch and what it would cost readcreate_enrichment_run a run over a scope, with a cap writedispatch_run start it writeWhere to start
The readiness scan runs detection against your own CRM and reports what it finds, before anything is merged.