How to Build a B2B Prospect List That Is Ready to Contact

What we will have at the end

By the end of the workflow, we will have:

• one explicit ideal customer profile;
• a Getlead-ready search specification;
• a list of companies and decision-makers;
• verified business emails where available;
• a documented reason for accepting or excluding each row;
• segment fields that connect the list to a specific campaign;
• a CSV structure another team member can understand without a meeting.

If we cannot explain why a row is on the list, it is not ready for outreach.

1. Start with the problem, not the database

Most weak lists start with a database filter:

Industry: Software
Title: Founder
Country: United States

That is searchable, but it is not yet an ICP. It tells us what a record looks like, not why the company would need our offer.

We start one level earlier:

• What operational problem do we solve?
• What changes after the customer buys?
• Which companies experience that problem often enough to act?
• Who inside those companies owns the problem?
• What would make an otherwise attractive company a poor fit?

For example, imagine we sell an appointment-setting service for growing B2B SaaS companies.

A weak definition is:

SaaS founders in the United States.

A usable definition is:

US B2B SaaS companies with an active sales motion, where a sales leader owns pipeline creation, the team is hiring or expanding outbound, and the company is not consumer-only.

The second version gives us:

• company criteria;
• a reason to buy;
• buyer roles;
• timing signals;
• exclusions.

That is enough to start building a list without pretending every SaaS company is equally valuable.

2. Turn the idea into a searchable ICP

An ideal customer profile describes the company we want to sell to. A buyer role describes the people inside that company who influence or own the decision. We need both, but we should not combine them into one vague persona.

We use four groups of criteria.

Account criteria

These define the company:

• industry;
• geography;
• company-size band;
• business model;
• stage or operating maturity;
• must-have traits.

Buying-group criteria

These define the people:

• department;
• job title;
• seniority;
• economic buyer;
• likely champion;
• titles to exclude.

Timing criteria

These help us prioritize:

• hiring in the target team;
• a new executive;
• funding or expansion;
• a tool migration;
• a manual process reaching capacity;
• a renewal window.

Disqualification criteria

These protect the list:

• consumer-only business;
• no relevant department;
• geography we cannot support;
• company too early or too complex for the offer;
• no credible way to verify the contact;
• data older than our accepted freshness window.

An ICP without exclusions is usually a market description. It keeps expanding until nearly every company looks “close enough.”

Use the free ICP Builder

Our Ideal Customer Profile Builder separates the criteria Getlead can use as search filters from the criteria we still need to review manually.

The current Getlead B2B search supports:

• job title;
• industry;
• country;
• seniority;
• department;
• verified-emails-only;
• target result count.

Company size, growth stage, trigger events and technology requirements remain useful qualification fields, but we do not pretend they are active search filters when they are not. We keep them in the review checklist.

That distinction prevents a common failure: believing the database has already applied a criterion that only exists in our strategy document.

3. Create the search specification

For our example appointment-setting offer, the builder might produce this search:

| Search field | Value | |---|---| | Industry | Software, Computer Software | | Country | United States | | Department | Sales | | Job titles | Chief Revenue Officer, VP Sales, Head of Sales, Sales Director | | Seniority | CXO, Vice President, Head, Director | | Verified emails only | Yes | | Initial result target | 100 |

It would keep these as qualification criteria:

| Qualification field | Rule | |---|---| | Employee band | 11-200 | | Business model | B2B | | Must have | Active sales motion | | Preferred trigger | Hiring sales roles or a new sales leader | | Exclude | B2C-only product, no active sales function | | Freshness | Review within 30 days |

We start with 100 results for a reason. The first search is a calibration sample, not a production export.

If 15 of the first 20 records are wrong, exporting 5,000 records will not fix the search. It will multiply the mistake.

4. Build the first universe

Now we can run the search.

At this stage, we are not deciding that every result deserves an email. We are creating a first universe of possible contacts.

We use a three-layer acceptance model:

Layer 1: Account fit

Does the company meet the commercial conditions?

• Is it in a relevant industry?
• Is it in a geography we support?
• Does it operate the business model we can serve?
• Does it meet the size or maturity rule?
• Does it have the required operating trait?
• Does it avoid our explicit exclusions?

Layer 2: Person fit

Is this the right person inside the account?

• Does the person work in the function that owns the problem?
• Is the title appropriate for the company size?
• Is the seniority high enough to influence the decision?
• Are we contacting a buyer, champion or user intentionally?
• Is the title overly broad or administrative?

Layer 3: Reachability

Can we contact the person responsibly?

• Is a business email present?
• Has the address been verified?
• Is the result deliverable, risky or unknown?
• Is the source date recent enough?
• Is the contact already suppressed or duplicated?

A row must pass all three layers before it becomes campaign-ready.

5. Choose the right people, not just the highest title

The CEO is not automatically the best prospect.

In a 10-person company, the founder may still own sales operations, hiring and pipeline. In a 500-person company, the same problem may belong to a VP, Head or Director. Targeting only CEOs can remove the people who experience the problem every day.

We normally build a small buying-group map:

| Role | What they care about | Typical titles | |---|---|---| | Economic buyer | Budget, risk, strategic outcome | CRO, VP Sales | | Champion | Workflow pain, implementation | Head of Sales, Sales Director | | User | Daily execution | Sales Manager, SDR Manager | | Possible blocker | Security, data or process concerns | IT, Legal, Operations |

We do not need every role in every campaign. We do need to know which role we selected and why.

For the first test, one primary role per segment is easier to evaluate than a list mixing founders, managers and individual contributors.

If the buying group is unclear, our guide to finding decision-makers at a company continues this workflow.

6. Verify reachability before we write the campaign

Email verification is not the final cleanup step. It changes which records are safe enough to include.

When we enable Verified Emails Only, Getlead keeps addresses that passed its real-time SMTP check at verification time and excludes catch-all or risky results. This reduces hard-bounce risk before outreach, but we still preserve the verification status and time context. A mailbox can close after verification, and a receiving server can behave differently during a later delivery.

The approved Getlead export uses these exact columns:

• First Name
• Last Name
• Job Title
• Email
• Company
• Website
• LinkedIn URL
• Industry
• Employee Count
• Verification Status

We classify results using the statuses the verification system actually returns. Our wider working list still needs a clear distinction between:

• verified/deliverable;
• risky or catch-all;
• invalid/undeliverable;
• unknown;
• missing email.

We do not replace those labels with a single “good” field.

For an initial campaign, verified contacts are the cleanest control group. Risky or catch-all records should remain separate so we can make a deliberate decision instead of mixing them into the same launch.

For an existing CSV, we can use the bulk email verifier. For an individual spot check, we can use the free email verifier.

Verification confirms the SMTP result at a point in time. It does not prove that the person still owns the problem, that the company fits the ICP, that the message is relevant or that a future delivery is impossible to bounce. That is why verification is the third layer, not the entire qualification system.

7. Use a CSV structure that preserves decisions

A minimal file with name,email is easy to export and difficult to operate.

The native Getlead export gives us:

First Name
Last Name
Job Title
Email
Company
Website
LinkedIn URL
Industry
Employee Count
Verification Status

We then add workflow columns that preserve why the record exists:

source
source_date
icp_profile
segment
qualification_status
exclusion_reason

The first ten columns come directly from the confirmed Getlead export. The workflow columns are additions we make for qualification and campaign operations.

The most important columns are often the least glamorous:

• source_date tells us when freshness should be reviewed;
• icp_profile tells us which definition created the row;
• segment connects the row to one message;
• qualification_status prevents unfinished research from entering a campaign;
• exclusion_reason teaches us why rows fail.

Without those fields, the same bad records tend to return in the next export.

8. Clean the file without confusing cleaning and verification

Before launch, we run the list through a hygiene sequence:

1. Normalize email casing and whitespace.
2. Normalize company domains.
3. Remove exact duplicates.
4. Flag duplicate people across different sources.
5. Flag missing company or role data.
6. Separate role-based addresses.
7. Apply the suppression list.
8. Verify business emails.
9. Keep risky and unknown records in separate review groups.
10. Preserve excluded rows with an exclusion reason.

Cleaning fixes the structure and removes obvious operating problems. Verification tests email reachability. We need both.

Our free B2B Lead List Cleaner will handle structural hygiene in the browser. The bulk email verifier handles SMTP verification after the file is clean.

9. Segment before writing

A campaign segment should share:

• one commercial problem;
• one buyer role;
• one proof point;
• one next step.

If the records cannot share the same opening logic, they should not share the same campaign.

For our example, one large list might become:

Segment A: New sales leader

• Role: VP Sales or Head of Sales
• Trigger: joined recently
• Problem: inherited pipeline target
• Proof: launch or rebuild outbound without hiring a full internal team

Segment B: Sales hiring

• Role: CRO or VP Sales
• Trigger: open SDR/AE roles
• Problem: pipeline requirement is growing faster than team capacity
• Proof: add qualified conversations while the team is being built

Segment C: Founder-led sales

• Role: Founder or CEO
• Company condition: smaller B2B SaaS company
• Problem: founder still owns prospecting
• Proof: create a repeatable list and outreach system

The campaign copy can now be specific without pretending every email is individually researched.

For the full workflow, use our guide to segmenting a B2B lead list for cold email.

10. Run a 20-row quality review

Before scaling, we review 20 rows manually.

We record:

| Check | Pass condition | |---|---| | Account fit | Company meets every must-have and no exclusion | | Person fit | Role intentionally matches the segment | | Reachability | Verification status is allowed for the test | | Freshness | Source date meets the profile requirement | | Segment | One campaign angle clearly applies | | Evidence | We can explain why the record belongs |

We then calculate:

sample acceptance rate = accepted rows / 20

This is not a predictive conversion metric. It is a search-quality check.

We use a simple rule:

• 17-20 accepted: the search is ready for a larger export;
• 13-16 accepted: revise one filter or qualification rule;
• 0-12 accepted: stop and rebuild the search specification.

The thresholds are an internal operating rule, not an industry benchmark.

For every rejected row, we capture one exclusion reason. If the same reason appears repeatedly, we update the ICP or search rather than continuing to remove records manually.

11. Decide whether the list is campaign-ready

We consider a prospect list ready when:

• the ICP has explicit must-have and exclusion rules;
• the search specification uses only fields the platform actually supports;
• unsupported criteria are retained as manual qualification rules;
• the first 20 rows pass the agreed acceptance threshold;
• every campaign row has an intentional buyer role;
• emails are separated by verification status;
• duplicate and suppressed records are removed;
• each row belongs to a defined segment;
• the file preserves source and freshness information;
• another team member can understand the file without asking how it was built.

Word count and row count do not make the list better. Clear decisions do.

The complete workflow in Getlead

We can now connect the pieces:

1. Build the ICP with the Ideal Customer Profile Builder.
2. Transfer the supported filters into Getlead's B2B lead database.
3. Run a 100-result calibration search.
4. Review 20 records against account fit, person fit and reachability.
5. Export the accepted records.
6. Clean and verify the file.
7. Split it into campaign-ready segments.
8. Launch a small test in Getlead's cold email software.
9. Track replies and pipeline in the lead CRM.

We do not need to guess our way from “SaaS founders” to a 5,000-row export. We can make the definition explicit, test it with 100 results and scale only after the records prove the search is working.

The CTA carries supported criteria into registration through URL parameters. After registration, we restore the filters for review before running a search or using lead credits.

Continue to the decision-maker workflow to build buying-role coverage, or use the company-list-to-contacts guide when the target accounts already exist. Before campaign launch, clean the file with the B2B Lead List Cleaner, prioritize limited capacity with the prospect scoring framework and divide the result using the segmentation guide.

Frequently asked questions

What is a B2B prospect list?

A B2B prospect list is a structured set of companies and contacts selected for a specific sales motion. A usable list includes account-fit criteria, the intended buyer role, contact and verification fields, source/freshness information and a campaign segment.

How large should the first prospect list be?

We recommend beginning with a 100-result calibration search and manually reviewing 20 rows. The right production size depends on how many records pass the ICP, role and reachability checks. Starting smaller makes filter mistakes cheaper to correct.

Is an email list the same as a prospect list?

No. An email list answers “which addresses do we have?” A prospect list answers “which companies and people fit this specific sales motion, why do they fit, and can we contact them safely?”

Should we target the CEO?

Only when the CEO or founder genuinely owns the problem at that company size. In larger companies, a VP, Head or Director may be the more relevant champion or buyer.

Do verified emails mean the list is qualified?

No. Verification addresses reachability. Qualification also requires company fit, person fit, relevance, freshness and an intentional campaign segment.

How often should we refresh a prospect list?

The right interval depends on the source and the criteria. We store a source date and define a freshness rule in the ICP. Before reusing an older list, we review employment data and verify the addresses again.

Can Getlead apply every ICP criterion automatically?

The current B2B search supports title, industry, country, seniority, department, verified-emails-only and result-count filters. We retain criteria such as company size, stage, triggers and technology requirements in the qualification checklist unless the live product supports them as filters.