How to evaluate and buy a B2B data provider

Last updated: October 16, 2026

To evaluate and buy a B2B data provider, send the same sample of your own records to two or three vendors, score coverage and accuracy separately, price the winner per usable record at your real volume, and fix credit expiry, overage, exit and data-retention terms before you sign. We reviewed Crustdata's own sales and trial calls with 64 teams buying B2B data, and 37 of them ran or planned a side-by-side test on their own records. But the harder questions in those calls came after the test, about credits, renewals and how to get out of a contract. Start legal and procurement on day one, because approval took about six weeks at one investment firm we spoke with.

What should you check when choosing a B2B data provider?

Check nine things, and test each one on your own data instead of taking the vendor's word for it. Use this table as a map to the rest of the guide.

A B2B data provider sells information about companies and the people who work at them. That usually means firmographics like headcount and industry, people data like title and employer, and contact data like work email and phone. The checks above apply to all of it.

Why are coverage and accuracy two different scores?

Coverage tells you how many records came back with data, and accuracy tells you how many of those values are true, so a vendor can look strong on one and weak on the other. A head of data at a consumer software company told us that "even if it's a hundred percent complete ... if more than half are inaccurate, it's not going to be very helpful."

Of the 64 teams in our calls, 15 scored the two separately, and three said a wrong record is worse than a missing one. An engineer building enrichment at a developer-tools company said "we rather have no result than like a false positive." The builder of a relationship-mapping product only accepts an email when two providers return the same one.

Fill rate, match rate, accuracy and confidence, defined

Agree on the definitions before you test, or every vendor will report the number that flatters them.

Ask every vendor whether each match carries a confidence score. The same head of data said a confidence score would be "actually really helpful," because it shows which matches to trust and which to double-check.

Why do vendors look complete on the records you send?

A vendor can look complete on the exact records you send and thin everywhere else. An engineer who builds an investment firm's internal data platform warned that "some providers might just put some makeup over the companies we sent over and they're pretty complete, but the rest of the companies, they don't have that much depth."

To catch this, run a hold-out check. Keep back a slice of records the vendor never sees, then run those records through the vendor's self-serve app or API yourself after the trial, and compare their fill and accuracy with the sample you sent. If you are buying a bulk file, pull random rows from the delivered file and score them against your own records.

Is coverage sold by region?

At least some vendors package coverage by region, which means a test on one region tells you little about another. A data lead at an investment firm described vendors that say "you only cover Europe and the US, but we don't give you Asia. To me, that doesn't really make sense." A practitioner on r/SalesOperations warned that the same vendor can "nail US tech" and do badly on EU manufacturing (Reddit). So split your sample by region and score each slice.

How do you run the 100-record test?

Pull 100 records from your own systems, seed them with answers you already know, send the identical file to every vendor, and score fill rate and accuracy per field. The steps come from how the buyers in our calls tested. The record count and the 90-day window are our suggestion, sized so one person can hand-check the results.

Step 1. Pull 100 records using the identifier you actually hold

Spread the 100 across your segments and regions, and give each vendor the same input your production system will send. If your users sign up with personal emails, test with personal emails, because that is a harder match than a profile URL. For company data, send domains or company names and score headcount, industry and funding. If you are building search on an API, send every vendor the same 10 to 20 queries (our suggestion) and compare the people or companies each one returns.

The r/SalesOperations practitioner gave the same advice, "send 100 of your actual ICP, demand hit rate by segment" (Reddit). Make the sample harder than your best accounts, too. A poster on r/Data_Enrichment builds it "roughly half random and half deliberately difficult," with small companies, non-US records and old records in the difficult half (Reddit).

Step 2. Seed answers you already know

Mix in three kinds of records where you know the truth. One buyer's test plan mixed contacts with verified emails and contacts with no email on file, then checked whether each vendor returned the same email or found a new one. Our suggested mix:

• Records with a verified work email and a confirmed current employer.

• People who changed jobs in the last 90 days.

• Records you know are missing from your own data.

Step 3. Freeze the sample and send it unchanged to every vendor

Do not let any vendor pick, clean or re-sample the list. The head of data quoted earlier turned down a vendor's request for a fresh sample and said "just to make it fair and comparable, I don't want it to be a new random sample of 5,000."

Step 4. Score fill rate per field

Count how many records came back with each field populated, because a high overall match rate can hide a low fill rate on the one field you need, such as work email. Do not count role addresses like info@ or free webmail addresses as hits for a work-email field. One poster on r/SideProject found providers padding results with exactly those (Reddit).

Step 5. Hand-check every returned record for accuracy

Open each returned value and check it against a source you trust, such as the company website or the person's public profile. A poster on r/Data_Enrichment put a hand-verified set of 100 to 150 records at "a day of work, not a week," which is why we sized this test at 100 (Reddit).

Step 6. Check freshness and refresh cadence on the recent movers

The job changers you seeded in step 2 are your freshness test. A vendor that still shows them at their old employer is behind, whatever its stated refresh cycle says. Then ask three questions:

• What triggers a refresh of a record?

• Can you show a last-updated date on each record?

• Am I charged for a refresh when nothing changed?

Ask about refresh cadence by data type as well. The r/SalesOperations practitioner says mobile numbers go out of date fastest, then emails, then titles. If you have time before signing, check the same records again about 60 days later. A reply on r/SideProject suggests rerunning the same contacts "sixty days later," because a vendor whose accuracy holds beats one that starts higher and slides (Reddit).

Step 7. Scale to 1,000 to 5,000 records for match rate

Once a vendor passes the hand-check, send a bigger sample to measure match rate by segment, without checking every value by hand. Five of the 64 teams in our calls used or planned samples in the thousands, and one chose the larger size because it was "a much better representation" of its users.

Step 8. Fill in the scoring sheet

Put every vendor on one sheet so the comparison is field by field.

The last row comes from the pricing section below.

Should you buy data by API, flat file or app?

Buy by API if software will request records on demand, by flat file if a data team wants the full set in its own warehouse, and through an app if sales reps search and export by hand.

Teams in our calls disagreed. A data team at a large professional-services firm said an API "would be, I think, the last route" for bulk data and preferred file transfer, while a founding engineer at a startup said "I wouldn't do flat files" because loading them would be a pain. So decide before the trial, and test the model you will use in production. For a deeper look at how API-first and platform-first vendors differ on cost and freshness, see our B2B data API vs platform guide.

What reliability checks should you do before building on an API?

Ask for the facts that decide whether your product stays up:

• Rate limits per endpoint, and what happens when you hit them.

• Typical response time and timeout behavior.

• Uptime history and a public status page.

• How schema changes are announced and versioned. A team on r/Backend found that a vendor's renamed field kept "succeeding with bad/missing data" until a customer noticed (Reddit).

• A sandbox or free test credits.

Also ask how enriched data writes back to your CRM. When a field already has a value, the integration should overwrite, append or skip it according to a rule you set.

What should a bulk file contract spell out?

Spell out the file format, the delivery cadence, and whether you get a full snapshot each time or only the records that changed. Add a remedy for a broken or incomplete delivery, such as a corrected re-delivery within a set number of days.

What do the four pricing models cost at volume?

Entry seat plans start around $37 to $49 a month, and one vendor's per-record price runs from about $0.39 on its smallest plan to about $0.01 on its largest. Compare the four models, which are seats plus credits, prepaid credit tiers, "unlimited" plans with a fair-use cap and annual dataset licenses, at your real volume. All prices below were checked on each vendor's own pricing page on October 16, 2026.

If you are building a product on an API, seat plans rarely fit, because your volume comes from software rather than from reps.

Cost per usable record is the number to compare

Divide what you are billed by the records you can use. The usable rate comes from your test.

Cost per usable record = billed price ÷ (records billed × usable rate)

On Coresignal's published tiers, a full employee record costs 20 credits. On the $49 plan, 2,500 credits buy 125 full records, about $0.39 each. On the $5,000 plan, 10,000,000 credits buy 500,000 full records, about $0.01 each. If your test showed 70% of records were usable, those become about $0.56 and $0.014 per usable record.

What will finance ask to see?

Finance will want the annual cost at the volume you expect, so show it at three volumes. The example below uses Coresignal's published monthly plans and a 70% usable rate from a hypothetical test. These are illustrative numbers worked out from public prices. To see how a bill moves month to month, the r/SalesOperations practitioner suggests asking the vendor for a real customer's last three invoices.

Each plan in this example buys far more credits than the volume needs, because Coresignal's tiers jump in big steps. That surplus is why credit expiry and rollover matter in the contract. Coresignal also offers yearly billing at 10% off, which changes the math.

Do you pay for empty results?

Ask every vendor this before you sign. Two of the 64 teams in our calls asked directly whether a lookup that finds nothing still costs credits, and the answer can change your cost per usable record more than a small discount does.

How can you start small?

Ask for a monthly plan, no minimum commitment, or a lower first tier you can upgrade from. A minimum commitment slowed or blocked the deal for three of the 64 teams in our calls before they knew whether the data worked. One startup's product lead asked for "a lower slab that we can start with, and then upgrade on."

Which contract terms bite after you sign?

Credit expiry and exit terms come up most. Of the 64 teams in our calls, 11 asked for an exit, opt-out or service-level clause, and 6 asked whether credits expire or roll over. The table lists the clauses to settle before you sign.

Credit expiry and rollover

Vendors handle unused credits very differently, so read the exact sentence. Apollo's pricing page says "Unused credits expire at the end of each billing cycle and do not carry over" (Apollo). Lusha rolls unused credits over on monthly plans up to twice the plan's limit, but resets them at the end of the cycle on annual plans (Lusha). Clay's pricing table lists rollover of up to one month's credits on monthly Launch and Growth plans and "15% of annual credits" on annual plans, and its FAQ adds that "Enterprise customers can roll over up to 15% of their prior year's purchased credits, provided they renew at an equal or higher commitment" (Clay).

Overage and top-ups

Agree in writing what happens when you run out mid-cycle. Coresignal's FAQ says that if you run out, you can renew or upgrade, and that "Both actions will reset your billing cycle to the day of the purchase" (Coresignal). Four of the 64 teams in our calls asked about overage before signing.

Auto-renewal notice

Find the auto-renewal clause and put the notice deadline in your calendar the day you sign. One poster on r/sales learned they had to "stop the auto renew atleast 60 days before end of contract or they send you for another year" (Reddit).

A renewal price cap

Put a cap on the year-two increase in the first contract. Our suggestion is based on timing, because by renewal your team has built on the data and switching costs the most.

An exit clause tied to quality

Ask for a match-rate floor, measured over a stated window with a minimum number of records, a cure period, and the right to terminate if the vendor misses again. A head of sales at a sales-software company asked a vendor directly, "do you also offer some sort of exit clause if not all the ... KPIs are met?" If a full clause is too much, ask for a paid first month or a 90-day pilot with an opt-out.

Uptime and how often you see the report

Ask for an uptime SLA with a monthly report, because a quarterly report can surface a breach three months after it happened.

Rights to use the data in your product

If you will show the data to your own customers, get display and resale rights in writing. Check whether the license covers that use or only internal use.

Data rights when you leave

Ask what you may keep and export after the contract ends, and whether you must delete it. SalesIntel's buyer guide warns that some providers "may try and force you to delete their provided data if you switch vendors" (SalesIntel).

An audit trail of what was enriched and billed

Ask for a log of which records were enriched and what you were charged for each. One recruiting agency we spoke with turned off a vendor's paid enrichment after the vendor could not show a record of what it had enriched.

What compliance and procurement checks come before signing?

Request the compliance documents in week one and start legal review alongside the data test. Ask for:

• The vendor's lawful basis for processing personal data under GDPR, and how it handles CCPA.

• A data processing agreement you can sign.

• A SOC 2 or ISO 27001 report, or the vendor's answers to your security questionnaire.

• How it handles opt-outs and deletion requests.

• Where its data comes from, at the level of source types.

• How it would help you answer a person who asks where you got their data.

If a vendor cannot answer the last two questions clearly, treat it as a red flag for any market with strict privacy rules.

How do you judge whether a data vendor will still be around?

Ask what happens to your data and your access if the vendor shuts down, loses a source, or retires the product you use. Ten of the 64 teams in our calls raised this risk. A market-research AI company told us that with many of its past suppliers, "they like frequently get shut down."

Four questions to ask:

• How many independent sources sit behind each field you need?

• If you lose one source, which of my fields would go empty?

• Can I export everything I have paid for, at any time?

• How much schema work would it take me to move to another vendor?

One team in our calls expected to remap its fields and schema before it could move, so a stable vendor is worth some price premium.

What should a trial checklist cover before you sign?

A trial checklist should cover the data test in week one and the commercials in week two, with legal working alongside from day one.

1. Write down the fields you need and the identifier you will send.

2. Pull 100 records across your segments and regions.

3. Seed known emails, recent job changers and known gaps.

4. Hold back a slice the vendor never sees.

5. Send the identical file to every vendor.

6. Score fill rate and accuracy per field, and record confidence scores.

7. Check the recent movers for freshness.

8. Send 1,000 to 5,000 records to measure match rate by segment.

9. Work out cost per usable record at three volumes.

10. Ask whether empty results, refreshes and unchanged records are charged.

11. Negotiate expiry, overage, auto-renewal, renewal cap, quality exit, uptime and data-on-exit terms.

12. Collect the DPA and security documents, and get legal sign-off.

Close with a one-page decision memo that finance can read in two minutes. It should show each vendor's fill, accuracy and freshness scores, the annual cost at your expected volume, the contract terms you won, and the risks still open.

If you want to try this test on Crustdata, the price is $0.30 to $0.01 per credit, lower depending on plan. Per-endpoint credit costs are listed in the Crustdata pricing docs, which also answer three billing questions from this guide. A search that returns no results uses no credits, contact lookups with no match are not billed, and purchased credits expire 12 months after purchase (credit expiry).

Frequently asked questions

Do you get charged if a record doesn't match?

Some vendors charge for lookups that find nothing and some do not, so ask before you sign and get the answer in writing. Put it into your cost per usable record, because paying for misses can raise your real cost more than a small discount lowers it.

Do unused credits expire?

Often, and the rules vary by plan. Apollo's credits expire at the end of each billing cycle. Lusha rolls monthly credits over up to 2x but resets annual-plan credits at the end of the year, and Clay rolls over a capped share. Ask for rollover, or size the plan so you use what you buy.

What happens if the data vendor shuts down?

You can lose access to the data and to anything you built on it. Ask how many sources sit behind each field, confirm you can export everything you have paid for, and keep your own copy of anything your product depends on.

Can I get an exit clause if data quality drops?

You can ask for one, and it is easier to win before you sign than after. Ask for a match-rate floor over a stated window, a cure period, and the right to terminate after repeated misses. Or ask for a paid first month with an opt-out, which is the simpler version.

How big should a test sample be?

Use 100 records you can hand-check for accuracy, then 1,000 to 5,000 for match rate. The 100-record size is our suggestion. For the larger sample, five of the 64 teams in our calls used or planned samples in the thousands.

How much does B2B data cost?

Published prices checked October 16, 2026 put the cheapest paid seat plans at around $37 to $49 a month, and one vendor's full employee record at about $0.39 on its smallest plan and about $0.01 on its largest. Compare cost per usable record at your own volume.

Should I buy a flat file or use an API?

Buy a flat file if a data team will load the whole set into a warehouse and can work with monthly updates. Use an API if a product or workflow needs records on demand. Test the model you will use in production.

How long does buying a data provider take?

Plan for about two weeks of testing and commercials, plus legal and security review that can take several weeks at larger companies. One investment firm in our calls needed about six weeks for procurement.

Sources and method

The buyer findings come from a review of Crustdata's own sales and trial calls with 64 teams that were testing or buying B2B data, carried out in October 2026. A team counts toward a finding only if someone on the buyer side said it clearly on a call. Every count on this page is out of those 64 teams. Customer names and the prices customers mentioned are left out on purpose.

Vendor prices and terms were checked on each vendor's own page on October 16, 2026, and can change:

• Apollo pricing

• Lusha pricing

• People Data Labs person pricing

• Coresignal pricing

• RocketReach unlimited credits FAQ

• Clay pricing

• SalesIntel buyer guide

• Crustdata pricing docs and credit docs

Practitioner advice comes from public Reddit threads on r/SalesOperations, r/Data_Enrichment, r/SideProject, r/sales and r/Backend, read on October 16, 2026. The worked cost examples are our arithmetic from published prices.