B2B Prospecting, Waterfall Data Enrichment & Buying SignalsPlaybook3 min readUpdated September 2026

How to Test a Lead Vendor's Data Before You Buy

Every lead-data vendor publishes an accuracy number, and none of those numbers are calculated the same way, so comparing them side by side tells you almost nothing about how well a vendor will actually perform on your specific list.

The only reliable test is running your own sample against a vendor's data and checking it against records you already know are correct.

Why Published Numbers Don't Tell You Much

A vendor's self-reported accuracy figure is measured against their own book of records, using their own definition of a correct match, with no independent audit behind it. Two vendors can both claim a similarly high figure while performing very differently on the specific industries and roles you actually sell into.

Treat every vendor's own claim as a starting point for a conversation, not as something you can compare directly against a competitor's claim. Ask each vendor directly how they calculate the number, since a willingness to explain the methodology in detail is itself a useful signal about how seriously they take data quality.

Build a Test Sample From Records You Already Trust

Pull twenty or thirty companies and contacts from your own customer base, people whose current title, direct dial, and email you've personally confirmed are correct. Run those exact companies through each vendor you're evaluating and compare what comes back against what you already know is true.

This is the only apples-to-apples test available, since it removes the vendor's own self-reported methodology from the equation entirely.

Separate Coverage From Field-Level Correctness

A vendor can return a record for nearly every company on your list, which looks like strong coverage, while getting the actual phone number, title, or email wrong on a meaningful share of them. Coverage and correctness are two different things, and a vendor's marketing tends to emphasize the one that looks better.

Score each field separately: does a record exist at all, and separately, is the direct dial the one that actually reaches the right person, is the title current, is the email one that doesn't bounce. A vendor that's strong on one field and weak on another is common, so a single overall score tends to hide exactly the tradeoff you need to see.

A Reference Checklist for the Comparison

When you run the test sample, it helps to check for a consistent set of things across every vendor:

  • Whether the direct dial actually connects to the named person, not a general switchboard
  • Whether the listed title matches the person's current role rather than a past one
  • Whether the email address bounces or delivers cleanly
  • How the vendor sources and refreshes its data, and how often

Weighting these consistently across every vendor you test is what makes the comparison meaningful.

How Often to Re-Test

Lead data quality drifts as people change jobs, companies restructure, and vendors change how they source information. A vendor that performed well a year ago isn't guaranteed to still be accurate now, especially if their sourcing methodology has changed in the meantime.

Re-run the same test sample every six months or so, using the same known-good records, so you're comparing the vendor against a consistent baseline over time rather than testing a different sample each time. Note the date of each test run alongside the results, so a stale comparison doesn't get mistaken for a current one months later.

What to Do With Mixed Results

It's common for one vendor to win on direct-dial accuracy and another to win on title freshness or email deliverability. Rather than picking one winner, many teams end up using different vendors for different fields, or waterfalling a query through two providers and keeping whichever result actually validates.

This adds complexity, so only go this route once you've confirmed through your own testing that a single vendor genuinely can't cover your needs well enough on its own. Document which vendor won on which field so the decision is easy to revisit the next time you re-test.

Executive Capability Standard

What Good Looks Like

A reliable comparison runs a real test sample of known-good records against each vendor, scores coverage and field-level accuracy separately, and repeats the test on a fixed schedule rather than trusting any vendor's own published claims.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Pull twenty known-good customer records and manually check what a candidate vendor returns for each one before making any purchasing decision.
2. Do Manually:Run the full test sample yourself across every vendor you're seriously considering, scoring each field separately rather than relying on an overall impression.
3. Delegate:Hand the recurring six-month re-test to an ops or data teammate once the initial methodology is set, so drift gets caught without your direct involvement each time.
4. Automate:Build a lightweight script that runs your known-good sample against each vendor's API and flags field-level mismatches automatically.
5. Buy:Bring in a data-quality consultant if you're evaluating vendors at a scale where a manual sample test isn't practical to run and repeat yourself.

How to Get Started

Frequently Asked Questions

How big should my test sample be?

Twenty to thirty known-good records is usually enough to spot meaningful differences between vendors without taking too long to build. The key requirement is that you already know the correct answer for every record in the sample, not the sample size itself.

Does a vendor's 'verified' badge actually mean anything?

It means the vendor's own process flagged the record as checked, using whatever definition they use internally. It's worth more than an unflagged record from the same vendor, but it isn't independently audited, so it's not a substitute for testing the vendor's data against records you already trust.

Should I just use two vendors instead of picking one?

Only if your own testing shows a real, consistent gap between them on different fields. Running two vendors adds cost and complexity, so confirm through testing that a single provider genuinely can't cover your needs before committing to that extra overhead.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides