How to Build Prospect Lists That Actually Convert

The difference between a contact list and a prospect list

A contact list is a pile of names and emails. A prospect list is a curated, segmented, and enriched asset that maps directly to a campaign strategy. The gap between them is the difference between a 1% reply rate and a 12% reply rate.

Every prospect list should answer four questions: Who is this person? Why are they relevant now? What problem does my product solve for them? What message variant should they receive? If your list can't answer these, it's not ready to use.

The right column structure for a prospect list

A well-structured prospect list has both contact fields and context fields. Contact fields identify the person (first name, last name, email, job title, company name, LinkedIn URL). Context fields power personalisation (company industry, company size, city, recent trigger/signal, and any custom notes).

The most underused column is the 'trigger' or 'signal' column — a one-line note on why you're reaching out now. 'Just raised Series A', 'Hiring 5 SDRs', 'Just launched enterprise tier', 'Speaking at SaaSBoomi in March'. This note becomes the first line of your email.

• Minimum viable columns: first_name, last_name, email, company_name, job_title, signal.
• Optional enrichment: linkedin_url, company_size, industry, city, tech_stack.
• Never import a list that's missing first_name — personalisation breaks instantly.

Segmenting your list before you import

Segmentation is dividing your list into groups that share a specific characteristic — so each group gets a message tailored to them. The most common segmentation mistake is sending one generic message to a mixed list and wondering why nobody replies.

Segment by at least one of: industry, job title/seniority, company size, or the problem they're most likely experiencing. If you're selling recruitment software, an HR Manager at a 50-person startup has very different pain points than a Talent Acquisition Head at a 2,000-person enterprise. Same product — completely different email.

• Start with two or three segments maximum. More than that becomes impossible to manage well.
• Name your segments clearly: 'Series-A SaaS CTOs', 'E-commerce Marketing Directors 50–200 headcount'.
• Each segment should have at least 30–50 prospects for statistical significance.

List hygiene: what to remove before you send

Sending to bad data hurts your deliverability. Every bounce raises your bounce rate, and inbox providers use bounce rate as a spam signal. Before any campaign, run your list through email verification, remove generic emails (info@, support@, hello@), flag disposable domains, and remove any domain that appears on a known spam-trap list.

Also scrub manually for obvious issues: companies that are clearly not your target, job titles so senior they'll never see your email (CEO of a 50,000-person company), job titles so junior they have no buying power, and contacts you've already reached out to in the last 90 days.

• Target a bounce rate under 2% per campaign. Above 5% is dangerous for your domain.
• Never send to role-based emails (info@, admin@, sales@) — they land in shared inboxes.
• Use a separate subdomain for cold outreach to protect your primary domain's reputation.

How many leads do you actually need?

More is not always better. For most B2B products, a campaign of 100–300 tightly targeted prospects with strong personalisation will outperform a spray-and-pray campaign of 3,000 generic contacts in terms of both reply rate and meeting quality.

A useful formula: work backwards from your goal. If you need 5 meetings, and your email-to-meeting rate is 5%, you need 100 replies. If your reply rate is 8%, you need 1,250 emails. So your list should have at least 1,250 valid contacts in that segment. Build in a 20% buffer for bounces and bad data.

• 5 highly targeted meetings are worth more than 50 meetings with the wrong people.
• For account-based campaigns, aim for 3–5 contacts per target account.
• Continuously add to your list — treat it as a rolling asset, not a one-time build.