A CRM-ready prospect list connects each account to a reason for targeting it, identifies relevant people, and fits the fields and rules your sales team actually uses. A spreadsheet with names and email addresses is only one part of that handoff.
Start with the next action: what must a salesperson know before deciding whether to reach out? Then work backwards to the data, evidence and permissions needed. The following checklist is a practical specification you can adapt to your CRM, rather than a claim that one set of fields suits every business.
1. Record why the account fits
An account name does not explain relevance. Keep the agreed ICP criteria close to the record: industry, market, size range, use case and exclusions. Add a short fit rationale supported by an identifiable source. Distinguish an observed fact from an inference.
For example, an advertised vacancy may show that a company is hiring for a role. It does not establish its budget, dissatisfaction with a supplier or intention to buy. If a fit decision depends on that interpretation, label it as a hypothesis for sales to test.
- Company name and canonical company domain.
- Segment and the criteria used to assign it.
- A concise fit rationale, with source and date checked.
- Exclusion status: existing customer, competitor, unsuitable market or another agreed rule.
2. Define the fields before collecting them
Agree the CRM object, field type and permitted values with the CRM owner. A free-text “region” field is hard to import into a picklist that accepts only country codes. Separate account-level information from contact-level information so a company’s size is not copied into a person’s job-title field.
| Field | Illustrative value | Handling rule |
|---|---|---|
| company_domain | northstar.example | Account match candidate; check group companies before merging. |
| segment | Industrial suppliers · DACH | Use one approved segment label. |
| fit_reason | Offers equipment maintenance to factories | Attach the supporting source; do not convert an assumption into a fact. |
| buyer_role | Operations leadership | A target role is not a verified named contact. |
| email_status | Not verified | Keep unknowns explicit; do not invent an address. |
| checked_on | 2026-11-04 | Record the actual research date in a consistent format. |
| outreach_status | Awaiting review | Do not trigger a sending workflow on import. |
| record_owner | Assigned sales queue | Map to an existing permitted CRM owner or queue. |
3. Separate contact details from permission to contact
Useful contact fields can include name, current role, company association, business contact channel, source and verification status. Record what a verification label means: syntax checked, provider-verified and manually confirmed are different claims. Missing data should remain missing, with a reason where useful.
A valid address is not proof that outreach is permitted or wanted. Review the intended channel, applicable rules, source terms and recipient preferences before use. Keep suppression records available to the people operating outreach, and prevent an enrichment job from reintroducing a previously excluded contact.
4. Make quality checks part of acceptance
Agree checks that can be repeated before the full import. A small sample should demonstrate the field mapping and reasoning, including awkward cases, rather than only the cleanest rows.
- Check required fields, formats and allowed picklist values.
- Review a sample of source references and fit explanations.
- Match existing accounts and contacts using agreed identifiers. Flag uncertain matches for review.
- Apply customer, competitor and do-not-contact exclusions before delivery.
- List missing information and conflicting evidence separately.
- Test how a record displays for a salesperson, including content links and ownership.
Record accepted, rejected and review-needed rows separately. “Every row has a value” is a poor quality rule if it encourages guesses. A smaller, clearly explained batch can be easier to use than a larger list with hidden uncertainty.
5. Agree the import and the next owner
Before a bulk change, decide whether this is a new-record import, an update to existing records or both. Specify which fields may be overwritten, how duplicates are handled and how changes can be reversed. Have the CRM administrator review a sample and the backup or rollback method.
The handoff should state what was delivered, where the campaign assets live, what remains unresolved and who owns the next action. Avoid creating active outreach tasks automatically unless that workflow was explicitly approved. Import success is not proof that records are correct or ready to send.
A brief you can use before commissioning a list
- Who is in the ICP, and who is excluded?
- Which company and contact fields are required, optional or intentionally absent?
- What evidence must accompany a fit decision?
- What do the enrichment and verification statuses mean?
- How will duplicates and suppression records be checked?
- Who approves the sample and CRM changes?
- Who maintains the records and handles outreach after delivery?
alebGTM can prepare the ICP, account research and enrichment, then agree a CRM delivery and handoff around your team’s setup. If sending is also a constraint, compare client-led and managed outreach responsibilities before adding it to the scope.