Data quality

A B2B lead list quality checklist you can use on any vendor

Run these checks before you pay for a list or send email from one. They apply to ours too.

?

A poor B2B lead list rarely looks poor. It looks full: names, titles and emails in neat columns. The problems appear later as bounces, wrong contacts and a sales team that stops trusting the data.

This checklist is for buyers. Use it on any vendor or freelancer, and on us. A supplier who cannot answer one of these questions has already given you a finding.

Illustrative clip of the seven groups the checklist covers.

1. Sourcing

  • They can describe, in plain words, where the data comes from. "Proprietary database" is not an answer.
  • The sources are open-source data and other publicly available sources, such as company sites, registries, directories, event lists and press.
  • They explain how each source was collected. A vendor that cannot describe its method should not be trusted with your outreach.
  • They will tell you which fields came from where, at least by source type.

2. Fit to your ICP

  • You gave a written ICP and the vendor repeated it back with the must-have filters.
  • Open 20 random rows and check the company by hand. Most should clearly fit.
  • Job titles match the roles you asked for, not near neighbours.
  • Companies you must exclude are excluded: customers, competitors, no-go regions.

3. Freshness

  • Each row carries a date: when it was collected or last checked.
  • You can check a handful of people against their current public profile or company page. Many should still be in the role.
  • The vendor explains how often data is refreshed and what happens to rows that go stale.

4. Contact data

  • Email addresses are verified, and the vendor tells you what "verified" means. A syntax check alone is not verification.
  • Catch-all domains and risky addresses are marked, not silently mixed in.
  • Generic inboxes such as info@ or sales@ are labelled as such.
  • Phone numbers, if included, state their type and source.
Test the email column yourself. Take a small slice and run it through your own verifier, or ours. If the vendor's claim and your result disagree, believe your result.

5. Duplicates and structure

  • One row per person, one company per domain. The same company is not listed three times under variant spellings.
  • Columns are consistent: country names in one format, titles not stuffed into the name column.
  • The file opens cleanly as CSV with a header row.

6. Honesty about limits

  • The vendor tells you what they could not find, and gives a reason.
  • Coverage gaps are stated up front, not discovered by you later.
  • There are no promises about reply rates, meetings booked or revenue. Nobody controls those from a list.

7. Process and terms

  • You can start with a sample before committing to the full build.
  • Pricing is tied to a clear scope, with the drivers of cost explained.
  • You know who owns the files and how you can use them.
  • A real person answers questions, by email, within a sensible time.

Red flags

  • A price per contact with no scope, no sample and no description of how the list is built.
  • A "guaranteed" number of leads, replies or meetings.
  • No answer to "where does this come from?"
  • A reluctance to let you inspect any rows before payment.
  • The same file offered to many buyers, so you and your competitors contact the same people.

What to send a vendor

If you want a short email that does the work for you, ask these four things.

  1. What are the source types for each column?
  2. When was each row last checked, and how often do you refresh?
  3. How do you verify emails, and how do you label risky ones?
  4. Can I see a sample in my ICP before we agree on scope?

Honest vendors answer in a few lines. The answers tell you more than the sales page does.

A 30-minute audit you can run today

  1. Ask the vendor for a sample, 50 rows or so, in your ICP.
  2. Check 20 rows by hand against the company site (section 2).
  3. Run the emails through a verifier (section 4).
  4. Scan for duplicate domains and odd formatting (section 5).
  5. Ask the source questions from section 1 and note how clear the answers are.

Write the scores down. A vendor who passes the sample test is worth a trial. A vendor who avoids giving a sample has told you what you need to know.

Why a lead list quality checklist beats a score

A single "quality score" hides the reason a list is weak. A list can have clean emails and the wrong people. It can have the right people and stale titles. Each failure needs a different fix, and a different conversation with the vendor. A checklist keeps the causes separate, so you can say "sourcing is fine, freshness is not" and get a specific answer back.

It also keeps the audit honest on both sides. The vendor knows what you will check, and you know what to ask for.

Run it on us

We built our sample step to survive exactly this audit: a small batch, shaped to your ICP, that you can inspect before you scale anything. Our lists come from open-source data and publicly available sources, described on Data sourcing, and our checks are written up on the data quality page. For contacts you already hold, email verification is a standalone service, and for new lists see Custom B2B Lists.

Frequently asked questions

How do I check lead list quality quickly?

Ask for a sample of around 50 rows in your ICP, check 20 of them by hand against the company site, run the emails through a verifier and scan for duplicate domains. It takes about 30 minutes and covers sourcing, fit, contact data and structure.

Does a verified email mean it will not bounce?

No. Verification lowers the risk but cannot remove it. Ask the vendor what verified means, check that catch-all and risky addresses are marked, and test a small slice yourself before a full send.

Is a bigger B2B lead list always better?

No. A list that fits your ICP, is recently checked and has clean contact data beats a large file nobody has read. Size only helps after fit, freshness and structure are sound.

Want a sample you can audit?

Tell us your ICP and we will scope a sample you can check line by line before you commit.