Enrichment Intake and Field Mapping (Onboarding)

Enrichment Intake and Field Mapping (Onboarding)

1. 01

   Freeze the client's CRM export and record the pull date before any vendor is connected

   A dated snapshot gives you a baseline to measure match-rate lift against, and it stops enrichment runs from overwriting fields the client's sales team edited mid-project.

2. 02

   Inventory which fields the client actually uses in scoring, routing, and personalization

   Most accounts carry 60 to 120 contact fields and act on fewer than 20. Enriching the unused remainder inflates cost per record without changing campaign outcomes.

3. 03

   Classify each field as verified, inferred, or client-owned

   Phone numbers and firmographics from a provider like Cognism or ZoomInfo arrive verified; technographic guesses and AI-researched notes are inferred and need a separate confidence label in the CRM.

4. 04

   Map source fields to destination fields in a written crosswalk, including null behavior

   State explicitly whether an empty enrichment response overwrites an existing value or leaves it untouched. Ambiguity here is the most common cause of silent data loss in agency delivery.

5. 05

   Set the match key hierarchy and document the fallback order

   Work email first, then name plus company domain, then LinkedIn URL. Providers such as Wiza and Dropcontact resolve differently, so the fallback order must be fixed before the first batch runs.

6. 06

   Run a 200-record pilot and measure match rate, accuracy, and cost per usable contact

   Cleanlist publishes 98% email accuracy and 85% direct dial rates across its aggregated providers; hold every vendor in the stack to a measured number on the client's own list, not a marketing page.

7. 07

   Get written client sign-off on the crosswalk, match keys, and pilot results before full-volume processing

   This sign-off becomes the reference document when a client later disputes a record, and it protects the retainer from rework arguments.