A verified lead record identifies the right person or company and shows how the fields you plan to use were checked. When buying lead list enrichment services, ask which fields are supported, what the evidence says, when it was checked, and what happens when the provider cannot resolve a match. A single “verified” label can hide very different answers for the employer, job title, and email address.
Define what the enriched list needs to do
Start with the decision the list supports. If you’re assigning accounts to sales reps, the correct company identity and territory may be enough. If you’re routing outreach to the person responsible for operations, you need evidence of the current employer and relevant role. If the intended channel is email, define the email checks separately. A mail server response alone cannot establish who controls a mailbox or whether a person still works at the company.
Web Morphix’s guide to evaluating B2B lead research quality covers what to ask when commissioning research. For enrichment, give the provider an existing list and specify which fields to add, which to recheck, and which to leave as they are.
Ask for evidence at the field level
| Field | Evidence to request | Reason to hold |
|---|---|---|
| Company identity | Matched domain or company identifier, source reference, and date checked | Two plausible companies share a name or the record could refer to a subsidiary |
| Employer and role | A dated source check tying the person to the employer, plus the title as recorded and any normalized title | Sources disagree or the only evidence refers to a past role |
| Work email | How the address was sourced and checked, the outcome, and the check date | Only a guessed pattern or a domain-level result supports the address |
Ask the provider to distinguish the date it checked a source from the date that source was updated, where known. A page checked today may still describe an old appointment. If the source is licensed, agree what evidence your reviewer can see, such as the provider name, record reference, and the check outcome.
Make the pilot include difficult records
Send a representative sample that includes recent contacts, old records, duplicate company names, and missing domains. Use stable row IDs so you can compare the returned file against the input. Agree on a few known cases your reviewer can independently check. Include normal rows as well as exceptions so the pilot reflects the list your team actually uses.
Suppose a supplier finds a current company domain and an old profile for a person listed as Head of Operations. The company match may be usable for account routing. The role should remain unresolved if the supplier cannot establish that it is current. If a proposed email was inferred from a pattern, preserve that status even when the domain accepts mail. You can then accept the company fields while holding the contact fields.
Review three numbers using denominators you agreed in advance. Count the eligible fields supported by evidence, the accepted fields in the sample that matched your independent review, and the records with unresolved exceptions. Ask what the supplier charges for partial matches and unresolved rows. A high fill rate can be expensive if your team has to repeat the checks before using the data.
Agree what happens to existing CRM values
Request a review file with the original value, proposed value, evidence reference, check date, and disposition. Use dispositions your team can act on, such as accept, hold for review, or leave existing value. Name the person who approves conflicts and decide which fields the provider may fill automatically. For instance, HubSpot’s data enrichment settings distinguish filling empty properties from overwriting existing ones. HubSpot also documents that an individual enrichment workflow can override the general rule. Check the actual workflow before allowing enrichment to update live records.
Keep the approval step separate from the research handoff. A provider can deliver a reviewed file while a CRM owner controls imports and merges. If the pilot also reveals gaps in your target accounts, Ops by Maaz Khan’s lead research and list-building service is relevant to scoping additional prospect research as a separate workstream.
Compare quotes using the same deliverables
Give each provider the same field list, sample, rules for retaining existing values, and permitted sources. Ask for a sample return file, an exceptions log, and a named reviewer. Have the provider explain how they handle conflicting sources and corrections after handoff. A quote should identify who does the checking, what your team receives, and what happens before any live CRM changes.
Frequently asked questions
Is B2B contact enrichment the same as list building?
Enrichment adds or checks information against records you supply. List building finds additional companies or people that meet your criteria. Define the expected output and acceptance checks for each if you buy both.
How fresh should a verified record be?
Set the freshness requirement by field and use. A company domain and a current role may need different recheck windows. Ask for the check date and, when available, the date on the underlying evidence.
Can a partially verified record pass?
Yes, if it meets the requirements for the intended use. An accepted company match can support account assignment while unresolved role or email fields stay on hold.
Should the supplier overwrite CRM fields?
Specify that by field. Many teams can start by filling approved blanks and reviewing conflicts separately. Require explicit approval for sensitive changes such as replacing an existing owner or merging identities.