LeadScorerFREE INTERACTIVE WORKBENCH
No sign-up · Download your planCan this prospect list move to outreach?
Review one batch against six release checks. This is an operational checklist, not an email-verification service or a legal assessment.
This tool does not submit or save your answers. Reloading clears them. Keep personal and confidential information out of your planning note.
The batch matches an approved offer, segment and account profile.
Each record resolves to the correct company or facility and a relevant current role.
Required fields include sources and checked dates; facts are separate from assumptions.
Released records have usable contact routes under the agreed method and freshness window; failed or unresolved records are held out.
Duplicates are resolved and excluded or conflicting records are removed or held out of the release batch.
Someone owns final release, replies, corrections and removal requests.
Your next checks
- Write the account inclusion and exclusion rules, then review the batch against them.
- Resolve company/facility ambiguity and check the role responsible for the relevant work.
- Record a source and checked date for required facts. Leave unverified information marked unknown.
- Verify the route before release and hold out failed or unresolved records. Email validation is not proof of identity, interest or permission.
- Reconcile current suppression and ownership records; remove or hold out excluded, duplicate and conflicting records before outreach.
- Assign the release reviewer and reply owner, and define the route for corrections and removal.
Your download includes the basis for each check and space to assign an owner, record evidence and set the next review. Add those details in your own records before acting on the plan.
What makes a B2B prospect list ready for outreach?
A useful B2B prospect list connects a suitable company, a relevant contact and an evidenced reason to approach them. Building it means researching accounts, checking roles and contact details, resolving duplicates and exclusions, and recording unknowns. Deliverable email addresses alone are not enough.
Your ideal customer profile defines the market. This guide turns those rules into reliable records for B2B lead generation. Scoring prioritises suitable records; it cannot repair missing evidence.
Use the free readiness check above to review six requirements and export your checklist and gaps. Its result reflects your answers, not an independent audit of the list.
Design the prospect record before sourcing it
Separate company, contact and campaign records. Multiple contacts can share an account and an existing sales owner.
| Record group | Fields to keep | Decision it supports |
|---|---|---|
| Account identity | Company name, primary domain, parent or subsidiary, CRM ID | Is this the correct business and already known to us? |
| Account evidence | Relevant product or service, target criterion, source URL, checked date | Does the business match the approved campaign? |
| Contact relevance | Name, current role, function, employment source, checked date | Is this a reasonable person to approach about the work? |
| Reachability | Business contact channel, verification result, verification date | Is the selected route usable or unresolved? |
| Relationship controls | Account owner, active opportunity, customer status, suppression result | Should this campaign contact the account at all? |
| Release decision | Ready, hold or exclude; reason; reviewer; next review | What happens to this record next? |
Scroll across to read all columns on smaller screens.
Record only information needed for the business purpose. Access controls, retention and permitted outreach should follow your organisation's approved policies.
Research accounts before collecting contacts
Start with one service, segment and small batch. Read company pages to confirm the business model. Directory categories may mix manufacturers with distributors or software vendors with consultancies.
Write one short evidence note against each essential criterion. Use “unknown” where a source does not answer the question. Save the page and date so another reviewer can repeat the check.
Identify the function owning the relevant work. A small agency's founder and a larger organisation's operations lead may cover the same responsibility. Map responsibilities before choosing seniority.
Test relevance with industry-specific fields
Fictional examples: each provider is researching a prospective customer, not describing an actual client result.
| Provider | What the prospect record should establish | What requires further discovery |
|---|---|---|
| Marketing agency offering paid acquisition | A brand sells through an active online store and the agency supports that business model | Whether acquisition support is needed, who owns it and what scope is relevant |
| Accounting firm offering recurring support | A B2B consultancy operates in the firm's supported market and fits its service scope | Current responsibilities, systems, complexity and handover requirements |
| B2B SaaS vendor offering production scheduling | A manufacturer operates a production process supported by the software | Current workflow, integration constraints and project ownership |
| Manufacturer supplying machined components | An OEM makes products that could use the supplier's actual capabilities | Drawings, materials, tolerances, volumes and supplier-approval process |
Scroll across to read all columns on smaller screens.
A brand that fails a mandatory requirement should not reach the campaign. Industry labels narrow research; they cannot replace it.
Verify contact data without confusing it with qualification
Check that the contact still works at the company and that the role relates to the offer. Keep the employment check separate from the email check. A mailbox result cannot establish job responsibility, purchasing authority or interest.
Use explicit verification statuses. If your verifier returns an uncertain result, preserve that uncertainty and follow the agreed handling rule. Do not relabel every non-invalid result “verified.” Check the provider's definitions before comparing results from different tools.
Recheck time-sensitive information before release when the research and campaign launch are separated. For sending infrastructure and technical checks, use the cold email deliverability checklist.
Resolve duplicate records and relationship conflicts
Normalise domains consistently and match them against the CRM. Review aliases, redirects and parent–subsidiary relationships rather than automatically merging every similar company name. Two trading names may be one buyer; two subsidiaries may buy independently.
Match contacts using stable identifiers where available. Preserve replies and exclusions when merging. Define whether an exclusion covers a person, account or domain.
Run suppression checks again at release, not only when research begins. A record may become a customer, enter an active opportunity or request no further contact while the list is being prepared. Account ownership conflicts should go to the owner for a decision.
Give every record a release decision
| Status | Use it when | Next action |
|---|---|---|
| Ready | Required account and role evidence is present; channel and relationship checks pass | Assign a campaign owner and approved message segment |
| Hold | A required fact is unknown, stale or conflicting | Name the missing check, researcher and review date |
| Exclude | A mandatory mismatch or applicable suppression rule exists | Record the reason and prevent re-entry through another import |
Scroll across to read all columns on smaller screens.
An overall completeness percentage should never override a critical failure. A record can have nearly every field filled and still belong to an excluded account.
Review samples from each source and segment, including ready, uncertain and rejected records. Examine both acceptance and rejection decisions. If a recurring defect appears, check the affected batch—not just sampled rows.
Measure usable coverage instead of purchased volume
Track unique researched accounts, accounts meeting mandatory criteria, contacts with relevant roles and records cleared for release. Keep duplicates and exclusions separate so a provider cannot count repeated entries as new coverage.
Fictional audit: a 120-record delivery contains 10 duplicates. Of the remaining 110 records, 15 are excluded, 20 need more research and 75 are ready. The ready share is 75 ÷ 110, or 68.2% of unique records—not 75 qualified buyers.
This breakdown identifies the next job: resolve the held records, investigate exclusion reasons and improve sourcing. It does not predict replies or meetings. The outbound reporting template tracks what happens after approved outreach starts.
Questions to ask a prospect-list provider
Ask to review a small sample against your actual criteria. Request source and check dates, contact-verification definitions, duplicate rules, suppression handling, correction terms and export fields. Clarify who owns the delivered data and who maintains it during the campaign.
Compare cost per usable record and research effort. Agree acceptance rules before expanding. Feed disqualification reasons and buyer corrections back into the research brief.
Build the account layer before the contact layer
A usable prospect record answers four questions: which account, why it fits, which role and what evidence supports contact. More purchased rows do not answer those questions.
- Write the offer and hard account exclusions.
- Research company or facility fit using low-cost sources first.
- Resolve the entity to a stable domain or internal account key.
- Identify the role that owns the relevant task.
- Fill missing fields from a second source only when the field changes a decision.
- Verify current contact routes and apply suppression before release.
This sequence avoids spending time and enrichment credits on accounts that fail a basic scope check. Keep the raw source separate from the approved release list so corrections remain traceable.
Check lookalikes and AI research before scaling
A lookalike account resembles a good customer on the fields that affect fit. Use profitable, well-served customers as seeds—not every logo your company has won. Reapply the hard rules to each new match.
For AI research, create a small set of accounts with known answers. Check wrong facts, missing facts, sources and the cost per usable record. Test the workflow on a small batch before expanding it. Do not fill an unknown field merely to make every row look complete.
| List problem | Repair | Release decision |
|---|---|---|
| Parent and facility mixed | Match the offer to the buying site | Hold until the entity is clear |
| Job title is current but irrelevant | Find the task owner | Do not release the wrong role |
| Two vendors return different values | Check the original sources and dates | Keep the disputed value unknown |
| Same account in several campaigns | Resolve ownership and shared exclusions | Use one coordinated account plan |
Scroll across to read all columns on smaller screens.
Measure cost per usable released account and role coverage, not just cost per row. Refresh the fields whose change could make the message false. Company size may change slowly; role ownership or an active project may need a shorter review window.
Frequently asked questions
Should we build or buy a B2B prospect list?
Compare required research depth, available staff and data freshness. Purchased data can provide candidates, but your account criteria, existing relationships and release checks still need to be applied. A tailored sample is more informative than a large headline database count.
Does a verified email mean a qualified lead?
No. Verification describes a technical check on an address. Qualification also concerns company fit, the person's role and, later, their expressed interest and meeting context. Store those decisions separately.
How many contacts should we include per account?
Enough to understand and reach the relevant buying function without overlapping outreach. Start with role coverage and account ownership. Adding contacts merely to reach a volume target can create duplicate conversations.
How often should a prospect list be refreshed?
Use the sensitivity of each field and the campaign schedule. Recheck relationship controls before release, investigate bounced or corrected contacts promptly, and assign review dates to stale evidence. One universal refresh interval will not suit every field.
What should an appointment-setting agency receive?
Provide approved account criteria, exclusions, relationship controls, evidence requirements and a named decision owner. Agree how new research enters the CRM and how replies update the list. The campaign operating standard helps define those responsibilities.
Further reading
Sopro's prospecting-list guide discusses contact data, verification and list maintenance. Belkins' sales-prospecting guide describes research checks and coordination with existing CRM records. The release decisions and fictional audit above are LeadScorer's practical examples.
WORKED MESSAGE · VARIABLES EXPLAINED
Prospect-list routing email: verify the task owner
An illustrative draft, not a sent campaign or client result. Adapt the service and sender to your own business. Verify each account detail and prepare any promised asset before use.
Subject Who owns {specific_task}?
Hi {first_name}, Your role at {company} appears to cover {work_area}. Is {specific_task} part of your team’s work? We help {account_type} with {defined_service}. I have a short example of how we handle that task, but I want to check the right owner before sending it. Would that sit with you or another team? Thanks, Shanay
Why this structure works
Even a verified address can belong to the wrong buyer. The message checks task ownership and names the service. It does not pretend that a guessed role or an email-verification result establishes interest.
- {first_name} / {company}
- Use: A current, checked contact and account.
Why: Contact-route validation alone does not confirm the person or employer. - {work_area} / {specific_task}
- Use: A researched role area and one concrete task.
Why: The buyer can confirm or correct the role match. - {account_type}
- Use: The account category supported by your offer.
Why: Fit remains required even when a contact replies. - {defined_service}
- Use: A task-based service with an example ready.
Why: The promise should be real and narrow enough to route.
Before sending: confirm why this buyer, why now, the work you offer and one clear next step. Keep the finished email under 100 words, including greeting and signature. Do not add made-up proof or urgency.
How to use this B2B outbound resource
Build records your team can use
Connect account facts, buyer roles, evidence and contact checks instead of collecting isolated email addresses.
Separate relevance from reachability
Review company fit and role fit independently from an email-verification result.
Catch repeated and excluded accounts
Resolve duplicate domains, account ownership and suppression rules before outreach.
Make uncertainty visible
Give unresolved fields a research owner and hold status rather than silently treating guesses as facts.
Approve a controlled release
Use record-level checks and a reviewed sample to decide which data is ready for a campaign.
Export your readiness checklist
Use the free check above to record confirmed requirements, unresolved questions and release blockers.
Apply this to your outbound decision.
Start with your actual offer, market, qualification requirements and the work your team can own. Examples and calculator estimates are not campaign guarantees.