How to Build a B2B Prospect List: QA + Free CSV (2026)
An account-first field specification, send-readiness gates, and governance checks for established B2B software teams.
Build the account record first, add the right buying roles second, record why each account fits, preserve source and review dates, verify reachability, apply suppression, and freeze a reviewed export before outreach. An email address alone is not a send-ready prospect.
This guide is an operating specification, not a promise that one field, provider, or threshold guarantees replies. The downloadable template leaves your acceptance policy to your team and makes every decision auditable.
What is a B2B prospect list?
A B2B prospect list is a governed set of companies and people approved for a specific sales motion. It should answer five questions for every row: Does the account fit? Is this the right person? Why now? Can we contact them through the approved channel? Has the row passed suppression and review?
A database export is only a source input. It becomes a prospect list after account qualification, role mapping, evidence capture, reachability checks, deduplication, suppression, and ownership are recorded.
The B2B prospect-list data model
The CSV separates account fit, timing, contact fit, reachability, and governance so one provider's “found” result cannot silently stand in for qualification.
| Layer | Fields in the template | Decision the fields support |
|---|---|---|
| Account identity | account_domain, account_name, account_segment, employee_range, hq_country | Is this the same legal or operating company the sales team intended to target? |
| Account fit | account_fit_reason, account_fit_evidence_url, last_reviewed_at | Why does the account match the written ICP, and when was that evidence reviewed? |
| Timing signal | signal_type, signal_source_url, signal_observed_at | Is there a verifiable reason to prioritize the account now, or is this simply evergreen ICP fit? |
| Contact fit | first_name, last_name, job_title, buyer_role, seniority, department, linkedin_url | Does this person map to an approved buyer, champion, user, blocker, or procurement role? |
| Reachability | work_email, email_status, email_verified_at, email_data_source | What is the current channel status, when was it checked, and which source supplied it? |
| Governance | suppression_status, crm_owner, review_notes | Can the contact enter this campaign, who owns the record, and what exception needs review? |
Important: catch_all, unknown, and valid are reachability statuses—not proof of buyer fit, legal permission, or inbox placement. Define the treatment of each status before enrichment starts.
Start account-first for established software sales
Title-first search is useful for discovery. It is a weak final data model because company duplicates, subsidiaries, ownership, account tiers, and buying-committee coverage become afterthoughts. For a controlled enterprise motion, build or approve the account universe first, then add people against a role map.
| Method | Use it for | Required control before outreach |
|---|---|---|
| Title-first | Discovering companies through a known role and firmographic filter. | Collapse results to unique account domains, resolve subsidiaries, and qualify accounts before contact enrichment. |
| Account-first | Named accounts, territory plans, vertical campaigns, and multi-person buying committees. | Define approved roles and coverage depth for each account tier; do not use an arbitrary contacts-per-company cap. |
| Hybrid | Expanding a named-account core without losing the account structure. | Route discovered companies through the same fit, evidence, ownership, and suppression gates as the original accounts. |
If the ICP itself is still ambiguous, stop before sourcing and use the B2B SaaS ICP guide. A precise contact search cannot repair an undefined account market.
Qualify accounts before buying contact data
Enrichment is downstream of account fit. If the wrong companies enter the provider waterfall, a high fill rate only produces more complete records for the wrong market. Apply the inexpensive checks first: domain resolution, geography, segment, use-case fit, exclusions, and a written evidence reason.
Then review a sample sized to the risk of the campaign. The right sample and pass threshold depend on list size, account value, source variability, regions, and the cost of a false positive. Set both before review; do not choose a threshold after seeing the result.
Account qualification rate = reviewed accounts that meet the written ICP ÷ all reviewed accounts.
Record the result and the rejection reasons. “Wrong business model,” “outside approved geography,” “subsidiary already owned,” and “insufficient evidence” are more useful than a single opaque score because they reveal which source rule must change.
Seven send-readiness gates
- Identity: the domain resolves to the intended account, and parent, subsidiary, franchise, and duplicate treatment is documented.
- Account fit: the row carries a written fit reason and a reviewable evidence source—not only a vendor category.
- Contact fit: the person maps to an approved buying role and account tier; title text alone is not the role map.
- Timing: any “why now” claim includes its source and observed date. Evergreen ICP fit is labeled separately.
- Reachability: channel status, verification date, and provider are preserved. Your policy—not the vendor label—decides how to handle catch-all and unknown results.
- Suppression: current customers, open opportunities, active conversations, unsubscribes, legal exclusions, and CRM-owner restrictions are resolved before upload.
- Release: an owner approves a versioned export with a release date and frozen row count, so the launched audience can be reconstructed later.
These are process gates, not universal percentage targets. A startup testing a broad market and an enterprise team approaching named accounts should not share one pass threshold. Use the free List Quality Grader to surface mechanical issues, then apply the policy your team approved for this campaign.
How to choose sources without confusing coverage with quality
One source can supply accounts, another can identify people, and several providers can attempt the same work email. Preserve field-level lineage so your team can compare which source contributed each value and when it was checked. A blended record without lineage cannot be audited when the role, company, or email changes.
If provider coverage and cost are the open questions, our 30,000-call study across 10,000 fresh domains compares data-source and waterfall options. It measures provider results; it does not replace account qualification, licensing review, suppression, or the send-readiness gates above.
Common prospect-list failure modes
- A database category is treated as ICP evidence. Categories are discovery inputs; the account still needs a written fit reason.
- People are enriched before accounts are approved. Contact coverage cannot rescue a poorly defined market.
- Job titles have no review date. A plausible title can still belong to someone who changed roles or employers.
- Coverage is confused with accuracy. “Found” describes provider output, not whether the company, person, and channel are correct.
- Catch-all is confused with a generic inbox. A domain-level catch-all status and an address such as
info@are different conditions and require different rules. - Suppression happens after campaign upload. CRM collisions and prior opt-outs should be resolved before a sender can touch the rows.
- Multiple contacts are added without a role map. Buying-committee coverage should follow account tier and role purpose, not an arbitrary contacts-per-domain target.
How many prospects do you need?
Size the list from operating capacity, not from an arbitrary database export.
Launch contacts required = approved new contacts per sending day × active launch days + documented reserve.
Sequence steps are not new prospects. Keep new-contact capacity separate from follow-up volume, and document what the reserve covers: QA rejections, suppression matches, stale roles, and replacement records.
For a small named-account market, prioritize account coverage and buying-role completeness over row count. If the full market can be reviewed manually, the team may not need outsourced sourcing at all.
Enterprise handoff checklist
- ICP version and campaign purpose
- Source and licensing review by the relevant owner
- Field definitions and allowed values
- Suppression and CRM-collision timestamp
- QA sample size, precommitted threshold, and rejection distribution
- Export ID, frozen row count, owner, and release date
- Written policy for stale roles, catch-all and unknown results, and missing signals
Use the enterprise outbound readiness checklist for the wider launch decision and the cold-email legal guide as a practical issue map. Neither replaces review by your legal, privacy, security, or revenue-operations owners.
Build the list in six steps
- Approve the ICP, account tiers, exclusions, and campaign purpose.
- Source and resolve accounts before paying to enrich people.
- Capture fit evidence and any time-sensitive signal with source dates.
- Map approved buyer roles and contact coverage by account tier.
- Enrich reachability fields while preserving provider and verification lineage.
- Apply suppression, review the precommitted QA sample, resolve exceptions, and freeze the release export.
Download the 25-column CSV template, or run an existing export through the List Quality Grader before handoff.
