Contact dataSeptember 2026
B2B data provider benchmark, September 2026
This benchmark measures B2B contact data providers on coverage, accuracy, stale records and results by segment, using one shared list of LinkedIn profiles. The September 2026 edition compares Apollo, BlitzAPI, GetLeads.io, MoltSets, Prospeo and QuickEnrich.
Run by BlitzAPI, one of the 6 providers measured. The reference every answer is scored against comes from none of them. How to check us
01
The ranking: accurate records per 100 contacts
One number ranks these providers, and it is the only one you can budget against: out of 100 contacts you send, how many come back with the right current employer and a matching title. It is coverage multiplied by accuracy, so nobody can lift it by answering less often, or by answering more loosely.
Out of 100 contacts, the strongest provider hands back 82.4 usable records and the weakest 31.9. The rest were either returned but not verified accurate, or never returned.
out of 100 contacts queried
AccurateReturned, not verified accurateNever returned
The exact numbers
| Provider | Rank | Coverage% of queried | Accuracy% of answered | Accurate per 100 | Interval |
|---|---|---|---|---|---|
| BlitzAPI | 1 | 90.4% | 91.2% | 82.4 | 81.1 to 83.7 |
| Apollo | 2 | 96.8% | 72.3% | 70.0 | 68.4 to 71.5 |
| Prospeo | 3 | 94.9% | 55.5% | 52.7 | 51.0 to 54.4 |
| QuickEnrich | 4 | 68.8% | 63.7% | 43.8 | 42.2 to 45.5 |
| MoltSets | 5 | 84.6% | 51.7% | 43.7 | 42.1 to 45.4 |
| GetLeads.io | 6 | 81.1% | 39.3% | 31.9 | 30.3 to 33.4 |
Coverage
69% to 97%
How often a provider answers at all. A stale answer still counts here.
Accuracy
39% to 91%
How often that answer carries the right current employer and a matching title.
Accurate records per 100
31.9 to 82.4
The only measure nobody can improve by answering less often, or more loosely.
Apollo answers most often, on 96.8% of the list, and 72.3% of those answers are right. Which side matters depends on whether an unusable row costs you more than a missing one.
02
Reach against accuracy
A record is lost in one of two places: the provider never returns it, or the answer it returns is not verified accurate, because the title differs, the employer is one the person has left, or the answer cannot be verified.
Answering more often and answering correctly pull against each other: the provider with the widest reach is not the one that is right most often.
every provider on one frame: how often it answers, and how often that answer is right
How often it answers at allVertical axis: how often that answer is right
Bands, accurate records per 100under 2020 to 4040 to 6060 to 80over 80
- BlitzAPIanswers on 90%, right on 91% of those, 82.4 accurate per 100
- Apolloanswers on 97%, right on 72% of those, 70.0 accurate per 100
- Prospeoanswers on 95%, right on 56% of those, 52.7 accurate per 100
- QuickEnrichanswers on 69%, right on 64% of those, 43.8 accurate per 100
- MoltSetsanswers on 85%, right on 52% of those, 43.7 accurate per 100
- GetLeads.ioanswers on 81%, right on 39% of those, 31.9 accurate per 100
Show the exact numbers
| Provider | Queried | Returned | Right employer | Right employer and title |
|---|---|---|---|---|
| BlitzAPI | 3,445100.0% | 3,11590.4% | 2,91984.7% | 2,84082.4% |
| Apollo | 3,445100.0% | 3,33496.8% | 2,91984.7% | 2,41170.0% |
| Prospeo | 3,445100.0% | 3,27194.9% | 2,18863.5% | 1,81652.7% |
| QuickEnrich | 3,445100.0% | 2,37068.8% | 1,78651.8% | 1,51043.8% |
| MoltSets | 3,445100.0% | 2,91584.6% | 1,91755.6% | 1,50743.7% |
| GetLeads.io | 3,445100.0% | 2,79381.1% | 1,89254.9% | 1,09831.9% |
The top right corner is the only place worth being: answering often, and answering correctly. Nobody is there. The distance from it is what a provider costs you, in rows you never get plus rows you cannot use.
03
What a wrong answer is made of
Each provider's answers are broken down into four verdicts: right employer and title, right employer with a different title, stale employer, and unverifiable.
Accuracy is the green band on the left, from 39% to 91%. For 5 of the 6, the widest band after it is an employer the person has left; only Apollo loses more to titles that do not match.
BlitzAPI3,115 returned
Apollo3,334 returned
Prospeo3,271 returned
QuickEnrich2,370 returned
MoltSets2,915 returned
GetLeads.io2,793 returned
Show the exact numbers
| Provider | Returned | Right employer and title% of returned | Right employer, different title% of returned | Stale employer% of returned | Unverifiable% of returned |
|---|---|---|---|---|---|
| BlitzAPI | 3,115 | 91.2%2,840 | 2.5%79 | 4.4%138 | 1.9%58 |
| Apollo | 3,334 | 72.3%2,411 | 15.2%508 | 10.8%360 | 1.6%55 |
| Prospeo | 3,271 | 55.5%1,816 | 11.4%372 | 17.5%574 | 15.6%509 |
| QuickEnrich | 2,370 | 63.7%1,510 | 11.6%276 | 24.6%582 | 0.1%2 |
| MoltSets | 2,915 | 51.7%1,507 | 14.1%410 | 33.2%969 | 1.0%29 |
| GetLeads.io | 2,793 | 39.3%1,098 | 28.4%794 | 32.2%900 | 0.0%1 |
A stale employer is usually lag, not invention: 84% to 94% of stale answers name a company the person really worked for, just not now.
04
Data quality after a job change
On accurate records per 100, every provider is at its best on jobs older than a year, and all of them bottom out no later than 4 to 6 months after the move. The drop runs from 23 points for the steadiest to 56 for the most brittle.
Measure
accurate records per 100 contacts queried, by months since the current job started
accuracy, the share of returned contacts carrying the right employer and title, by months since the current job started
coverage, the share of contacts the provider returned at all, by months since the current job started
stale rate, the share of returned contacts naming an employer the person has left. Lower is better
| Provider | 0 to 1n = 785 | 2 to 3n = 916 | 4 to 6n = 255 | 7 to 12n = 448 | 12+n = 1,041 | Shape |
|---|---|---|---|---|---|---|
| BlitzAPI | 65798311 | 7386868 | 9398950 | 9598971 | 9699970 | |
| Apollo | 56609418 | 67709510 | 74749910 | 78789911 | 79801006 | |
| Prospeo | 35389232 | 31339534 | 56599513 | 7476973 | 7579961 | |
| QuickEnrich | 22395746 | 19326049 | 31437333 | 6888776 | 7592813 | |
| MoltSets | 29368150 | 27338249 | 21248752 | 48568628 | 7383887 | |
| GetLeads.io | 22297451 | 17227653 | 20238445 | 38448724 | 5361875 |
Reading aidweakest to strongest within a column. Bold marks the strongest value of the column.
05
Results by segment: country, seniority, company size
Six dimensions, and for each one the count of segments a provider leads before any single row is read. A row is ranked only above 100 contacts, and a row whose top two values sit inside each other's confidence interval is marked as too close to separate.
Measure
accurate records per 100 contacts queried
coverage, the share of the segment the provider answered at all
accuracy, the share of answered contacts carrying the right employer and title
Cohort
Segments led, of 6 ranked
1 too close to call
No leader is declared on this measure
Ties are only tested on accurate records per 100
No leader is declared on this measure
Ties are only tested on accurate records per 100
- BlitzAPI5
- Apollo0
- Prospeo0
- QuickEnrich0
- MoltSets0
- GetLeads.io0
| Cohort | Contacts | BlitzAPI | Apollo | Prospeo | QuickEnrich | MoltSets | GetLeads.io |
|---|---|---|---|---|---|---|---|
| New jobs · Americastop two too close to separate | 835 | 71.685.384.0 | 67.396.969.5 | 39.692.642.8 | 23.262.037.5 | 31.590.135.0 | 20.879.426.2 |
| New jobs · Europe | 723 | 62.479.778.3 | 52.489.558.6 | 22.893.824.3 | 16.249.932.4 | 23.969.234.6 | 16.666.824.8 |
| Large cos · US/UK | 494 | 93.196.097.0 | 77.399.278.0 | 67.896.670.2 | 62.679.878.4 | 57.789.164.8 | 41.789.346.7 |
| SMB industry · US | 490 | 96.197.198.9 | 80.499.680.7 | 70.296.372.9 | 64.379.680.8 | 63.994.567.6 | 45.186.752.0 |
| SMB · EMEA | 454 | 94.996.798.2 | 78.999.679.2 | 71.696.074.5 | 68.380.285.2 | 51.378.265.6 | 46.385.754.0 |
| Micro cos · US | 449 | 95.597.697.9 | 74.899.875.0 | 70.496.972.6 | 59.076.477.3 | 53.590.259.3 | 37.287.342.6 |
Country
Segments led, of 5 ranked
2 too close to call
No leader is declared on this measure
Ties are only tested on accurate records per 100
No leader is declared on this measure
Ties are only tested on accurate records per 100
- BlitzAPI3
- Apollo0
- Prospeo0
- QuickEnrich0
- MoltSets0
- GetLeads.io0
| Country | Contacts | BlitzAPI | Apollo | Prospeo | QuickEnrich | MoltSets | GetLeads.io |
|---|---|---|---|---|---|---|---|
| US | 1,649 | 85.792.392.9 | 73.398.474.5 | 56.794.460.1 | 46.673.063.9 | 47.292.551.0 | 29.883.935.6 |
| GB | 493 | 83.290.791.7 | 68.895.172.3 | 52.194.755.0 | 46.974.063.3 | 43.484.851.2 | 33.982.441.1 |
| DEtop two too close to separate | 204 | 70.682.485.7 | 62.395.165.5 | 42.693.645.5 | 38.766.258.5 | 12.726.548.1 | 26.573.036.2 |
| FR | 152 | 65.884.278.1 | 50.093.453.5 | 28.399.328.5 | 27.040.167.2 | 34.278.343.7 | 17.870.425.2 |
| CAtop two too close to separate | 118 | 83.994.189.2 | 79.7100.079.7 | 58.598.359.5 | 50.071.270.2 | 55.191.560.2 | 39.889.044.8 |
Seniority
Segments led, of 5 ranked
1 too close to call
No leader is declared on this measure
Ties are only tested on accurate records per 100
No leader is declared on this measure
Ties are only tested on accurate records per 100
- BlitzAPI4
- Apollo0
- Prospeo0
- QuickEnrich0
- MoltSets0
- GetLeads.io0
| Seniority | Contacts | BlitzAPI | Apollo | Prospeo | QuickEnrich | MoltSets | GetLeads.io |
|---|---|---|---|---|---|---|---|
| Director | 1,121 | 89.393.595.5 | 74.098.874.9 | 62.096.364.4 | 55.077.471.1 | 49.186.456.8 | 38.785.545.3 |
| C-level/Founder | 860 | 84.790.893.2 | 75.597.177.7 | 60.693.664.7 | 42.862.368.7 | 49.787.356.9 | 33.781.041.6 |
| VP | 642 | 94.998.396.5 | 76.599.876.6 | 67.197.069.2 | 63.682.477.1 | 55.991.061.5 | 41.388.946.4 |
| IC/Staff | 542 | 60.578.876.8 | 48.989.754.5 | 20.393.021.8 | 13.147.627.5 | 20.872.328.8 | 13.365.920.2 |
| Managertop two too close to separate | 280 | 62.181.476.3 | 62.994.366.7 | 21.192.922.7 | 16.463.925.7 | 20.778.226.5 | 13.275.017.6 |
Company size
Segments led, of 8 ranked
3 too close to call
No leader is declared on this measure
Ties are only tested on accurate records per 100
No leader is declared on this measure
Ties are only tested on accurate records per 100
- BlitzAPI5
- Apollo0
- Prospeo0
- QuickEnrich0
- MoltSets0
- GetLeads.io0
| Company size | Contacts | BlitzAPI | Apollo | Prospeo | QuickEnrich | MoltSets | GetLeads.io |
|---|---|---|---|---|---|---|---|
| (unknown) | 939 | 78.086.590.1 | 67.394.970.9 | 50.194.053.2 | 35.961.358.5 | 39.483.747.1 | 29.477.737.8 |
| 51-200 | 599 | 87.391.795.3 | 73.197.874.7 | 57.495.360.2 | 53.173.572.3 | 49.284.658.2 | 35.282.142.9 |
| 1001-5000 | 499 | 84.892.691.6 | 72.197.673.9 | 54.396.656.2 | 48.972.967.0 | 47.185.055.4 | 35.983.443.0 |
| 11-50 | 429 | 90.794.695.8 | 73.498.874.3 | 59.494.662.8 | 50.873.769.0 | 50.888.657.4 | 32.983.739.3 |
| 201-500 | 374 | 88.093.993.7 | 74.197.176.3 | 60.494.963.7 | 52.175.968.7 | 48.785.357.1 | 38.284.045.5 |
| 10001+top two too close to separate | 202 | 65.384.777.2 | 55.094.158.4 | 24.894.626.2 | 19.357.433.6 | 25.276.732.9 | 15.873.321.6 |
| 1-10top two too close to separate | 183 | 80.391.388.0 | 73.298.474.4 | 53.695.156.3 | 42.166.163.6 | 42.189.147.2 | 31.185.836.3 |
| 501-1000top two too close to separate | 148 | 75.791.982.4 | 66.996.669.2 | 47.396.649.0 | 40.570.957.1 | 39.283.846.8 | 26.481.832.2 |
| 5001-10000small sample, not ranked | 72 | 73.684.786.9 | 62.597.264.3 | 44.491.748.5 | 30.666.745.8 | 29.279.236.8 | 27.877.835.7 |
LinkedIn followers
Segments led, of 5 ranked
2 too close to call
No leader is declared on this measure
Ties are only tested on accurate records per 100
No leader is declared on this measure
Ties are only tested on accurate records per 100
- BlitzAPI3
- Apollo0
- Prospeo0
- QuickEnrich0
- MoltSets0
- GetLeads.io0
| LinkedIn followers | Contacts | BlitzAPI | Apollo | Prospeo | QuickEnrich | MoltSets | GetLeads.io |
|---|---|---|---|---|---|---|---|
| 1k-4.9k | 2,002 | 86.793.393.0 | 73.598.674.6 | 55.895.558.5 | 48.973.266.8 | 47.286.754.5 | 35.083.841.7 |
| 5k-9.9k | 503 | 90.796.494.0 | 72.699.073.3 | 61.495.064.6 | 50.976.566.5 | 48.189.953.5 | 35.487.140.6 |
| 500-999top two too close to separate | 384 | 65.982.679.8 | 64.194.368.0 | 36.794.339.0 | 29.958.351.3 | 35.477.945.5 | 25.875.034.4 |
| 10k+ | 312 | 91.795.895.7 | 73.499.473.9 | 66.798.168.0 | 43.968.963.7 | 45.290.150.2 | 29.886.534.4 |
| < 500top two too close to separate | 244 | 44.760.274.1 | 41.078.352.4 | 16.487.718.7 | 9.833.229.6 | 17.660.729.1 | 11.548.823.5 |
Industry
Segments led, of 7 ranked
3 too close to call
No leader is declared on this measure
Ties are only tested on accurate records per 100
No leader is declared on this measure
Ties are only tested on accurate records per 100
- BlitzAPI4
- Apollo0
- Prospeo0
- QuickEnrich0
- MoltSets0
- GetLeads.io0
| Industry | Contacts | BlitzAPI | Apollo | Prospeo | QuickEnrich | MoltSets | GetLeads.io |
|---|---|---|---|---|---|---|---|
| Software Development | 676 | 88.893.594.9 | 75.099.175.7 | 59.595.162.5 | 55.075.772.7 | 45.781.855.9 | 35.584.841.9 |
| Technology, Information and Internet | 245 | 88.294.393.5 | 72.797.174.8 | 59.295.961.7 | 48.672.267.2 | 46.188.252.3 | 33.184.938.9 |
| IT Services and IT Consultingtop two too close to separate | 179 | 79.989.489.4 | 72.697.274.7 | 54.295.057.1 | 43.067.064.2 | 43.685.551.0 | 33.583.240.3 |
| Higher Education | 159 | 78.091.285.5 | 62.395.665.1 | 44.795.047.0 | 31.464.249.0 | 40.379.950.4 | 30.875.540.8 |
| Financial Services | 132 | 81.891.789.3 | 66.797.768.2 | 53.095.555.6 | 41.771.258.5 | 46.286.453.5 | 22.784.127.0 |
| Business Consulting and Servicestop two too close to separate | 119 | 78.291.685.3 | 66.498.367.5 | 45.495.047.8 | 33.663.053.3 | 36.189.140.6 | 26.179.033.0 |
| (unknown)top two too close to separate | 102 | 69.682.484.5 | 65.788.274.4 | 39.290.243.5 | 27.547.158.3 | 37.388.242.2 | 24.561.839.7 |
| Hospitals and Health Caresmall sample, not ranked | 63 | 74.685.787.0 | 66.795.270.0 | 46.092.150.0 | 33.361.953.8 | 34.988.939.3 | 33.377.842.9 |
Where each provider falls behind, including us. On accurate records per 100, BlitzAPI is behind on 1 of the 36 ranked segments, Apollo on 35, Prospeo, QuickEnrich, MoltSets and GetLeads.io on all 36. The table above carries every value behind that sentence; switch the measure to read the same rows on coverage or on accuracy, where the order is not the same.
Where each provider falls behind, including us. On accurate records per 100, BlitzAPI is behind on 1 of the 36 ranked segments, Apollo on 35, Prospeo, QuickEnrich, MoltSets and GetLeads.io on all 36. The tables above carry every value behind that sentence. This printed copy shows accurate records per 100 only; the same rows on coverage and on accuracy, where the order is not the same, are on the web page.
The counts above are on accurate records per 100. Switch the measure to coverage and the picture moves: Apollo returns more contacts than every other provider on 5 of the 6 cohorts, and Prospeo returns more on New jobs · Europe (93.8%).
The counts above are on accurate records per 100. On coverage, which this printed copy leaves out, the picture moves: Apollo returns more contacts than every other provider on 5 of the 6 cohorts, and Prospeo returns more on New jobs · Europe (93.8%).
06
Head to head: every provider pair
If you are replacing one provider with another, this is the comparison that matters. Each pair is scored only on the contacts they both returned, so a provider cannot look good here by staying silent.
On the contacts both providers returned, 1 of the 15 pairs is too close for this test to separate.
points of accuracy, row against column, on the contacts both returned
| Row is ahead by | BlitzAPI | Apollo | Prospeo | QuickEnrich | MoltSets | GetLeads.io | Ahead on |
|---|---|---|---|---|---|---|---|
| BlitzAPI | +18.13,081BlitzAPI is ahead of Apollo by 18.1 points on 3,081 shared contacts | +33.43,033BlitzAPI is ahead of Prospeo by 33.4 points on 3,033 shared contacts | +28.72,287BlitzAPI is ahead of QuickEnrich by 28.7 points on 2,287 shared contacts | +39.82,730BlitzAPI is ahead of MoltSets by 39.8 points on 2,730 shared contacts | +52.42,683BlitzAPI is ahead of GetLeads.io by 52.4 points on 2,683 shared contacts | 5 of 5 | |
| Apollo | −18.13,081Apollo is behind BlitzAPI by 18.1 points on 3,081 shared contacts | +16.73,213Apollo is ahead of Prospeo by 16.7 points on 3,213 shared contacts | +14.32,366Apollo is ahead of QuickEnrich by 14.3 points on 2,366 shared contacts | +24.32,889Apollo is ahead of MoltSets by 24.3 points on 2,889 shared contacts | +37.12,784Apollo is ahead of GetLeads.io by 37.1 points on 2,784 shared contacts | 4 of 5 | |
| Prospeo | −33.43,033Prospeo is behind BlitzAPI by 33.4 points on 3,033 shared contacts | −16.73,213Prospeo is behind Apollo by 16.7 points on 3,213 shared contacts | too close | +7.92,895Prospeo is ahead of MoltSets by 7.9 points on 2,895 shared contacts | +24.32,762Prospeo is ahead of GetLeads.io by 24.3 points on 2,762 shared contacts | 2 of 51 too close | |
| QuickEnrich | −28.72,287QuickEnrich is behind BlitzAPI by 28.7 points on 2,287 shared contacts | −14.32,366QuickEnrich is behind Apollo by 14.3 points on 2,366 shared contacts | too close | +10.12,176QuickEnrich is ahead of MoltSets by 10.1 points on 2,176 shared contacts | +22.72,292QuickEnrich is ahead of GetLeads.io by 22.7 points on 2,292 shared contacts | 2 of 51 too close | |
| MoltSets | −39.82,730MoltSets is behind BlitzAPI by 39.8 points on 2,730 shared contacts | −24.32,889MoltSets is behind Apollo by 24.3 points on 2,889 shared contacts | −7.92,895MoltSets is behind Prospeo by 7.9 points on 2,895 shared contacts | −10.12,176MoltSets is behind QuickEnrich by 10.1 points on 2,176 shared contacts | +13.02,578MoltSets is ahead of GetLeads.io by 13.0 points on 2,578 shared contacts | 1 of 5 | |
| GetLeads.io | −52.42,683GetLeads.io is behind BlitzAPI by 52.4 points on 2,683 shared contacts | −37.12,784GetLeads.io is behind Apollo by 37.1 points on 2,784 shared contacts | −24.32,762GetLeads.io is behind Prospeo by 24.3 points on 2,762 shared contacts | −22.72,292GetLeads.io is behind QuickEnrich by 22.7 points on 2,292 shared contacts | −13.02,578GetLeads.io is behind MoltSets by 13.0 points on 2,578 shared contacts | 0 of 5 |
Row ahead, darker is a wider gapRow behindGap inside the combined intervalSmall figure in each cell: contacts both providers returned
Show the exact numbers
| Pair | Both returned | First is right | Second is right | Gap |
|---|---|---|---|---|
| BlitzAPI vs GetLeads.io | 2,683 | 92.1% | 39.7% | 52.4 pts |
| BlitzAPI vs MoltSets | 2,730 | 92.1% | 52.3% | 39.8 pts |
| Apollo vs GetLeads.io | 2,784 | 76.4% | 39.3% | 37.1 pts |
| BlitzAPI vs Prospeo | 3,033 | 91.3% | 57.9% | 33.4 pts |
| BlitzAPI vs QuickEnrich | 2,287 | 93.4% | 64.7% | 28.7 pts |
| Apollo vs MoltSets | 2,889 | 76.0% | 51.7% | 24.3 pts |
| Prospeo vs GetLeads.io | 2,762 | 63.3% | 39.0% | 24.3 pts |
| QuickEnrich vs GetLeads.io | 2,292 | 64.5% | 41.8% | 22.7 pts |
| BlitzAPI vs Apollo | 3,081 | 91.4% | 73.3% | 18.1 pts |
| Apollo vs Prospeo | 3,213 | 73.1% | 56.4% | 16.7 pts |
| Apollo vs QuickEnrich | 2,366 | 78.0% | 63.7% | 14.3 pts |
| MoltSets vs GetLeads.io | 2,578 | 52.3% | 39.3% | 13.0 pts |
| QuickEnrich vs MoltSets | 2,176 | 64.2% | 54.1% | 10.1 pts |
| Prospeo vs MoltSets | 2,895 | 59.5% | 51.6% | 7.9 pts |
| Prospeo vs QuickEnrich | 2,327 | 66.8% | 63.8% | too closewithin the interval |
One page per pair against BlitzAPI. Each one sets out, in order, the main measures side by side (accurate records per 100, coverage, accuracy, the wrong title rate and the stale employer rate), each counted on the whole list or on what each provider returned, with the count of published segment comparisons the other provider leads or ties; each provider's answers split into four verdicts; the pair scored on the contacts both returned; and how both hold up after a job change: vs Apollo, vs Prospeo, vs QuickEnrich, vs MoltSets and vs GetLeads.io.
07
Waterfall: what a second provider adds
The usual answer to a coverage gap is to buy a second provider and fall back to it. Here is what that buys, measured rather than assumed: each step only queries the contacts no earlier step returned.
Querying a second provider on the misses lifts the run from 82.4 to 86.9 accurate records per 100. A third adds 0.3.
accurate records per 100 contacts, cumulative
StartBlitzAPI3,445 contacts queried
82.4start
ThenApollo330 misses queried, 253 returned
86.9+4.4
ThenMoltSets77 misses queried, 20 returned
87.1+0.3
ThenProspeo57 misses queried, 15 returned
87.2+0.0
ThenQuickEnrich42 misses queried, 1 returned
87.2+0.0
Best possible with all providers: 91.2. Reaching it would mean knowing which answers are wrong without a reference.
Show the exact numbers
| Chain | Queried at this step | Coverage | Accurate per 100 | Records gained |
|---|---|---|---|---|
| BlitzAPI | 3,445 | 90.4% | 82.4 | |
| BlitzAPI then Apollo | 330 | 97.8% | 86.9 | +153 |
| BlitzAPI then Apollo then MoltSets | 77 | 98.3% | 87.1 | +9 |
| BlitzAPI then Apollo then MoltSets then Prospeo | 57 | 98.8% | 87.2 | +1 |
| BlitzAPI then Apollo then MoltSets then Prospeo then QuickEnrich | 42 | 98.8% | 87.2 | +1 |
The ceiling for any combination is 91.2 per 100, the share of contacts where at least one of the 6 providers is right. Reaching it would mean knowing which answers are wrong without a reference, which is the whole problem.
08
Every measure, side by side
The measures that rank, in one table, including the rows that flatter nobody. Colour is a reading aid only, computed inside each row: green towards the better end, amber towards the weaker one. Rows that describe a run rather than score it, such as the query date, carry no colour and no mark.
| Measure | BlitzAPI | Apollo | Prospeo | QuickEnrich | MoltSets | GetLeads.io |
|---|---|---|---|---|---|---|
| Accurate records per 100 queried | 82.4 | 70.0 | 52.7 | 43.8 | 43.7 | 31.9 |
| Coverageanswered, % of queried | 90.4% | 96.8% | 94.9% | 68.8% | 84.6% | 81.1% |
| Accuracyright employer and title, % of answered | 91.2% | 72.3% | 55.5% | 63.7% | 51.7% | 39.3% |
| Right employer, any title% of answered | 93.7% | 87.6% | 66.9% | 75.4% | 65.8% | 67.7% |
| Stale rateemployer the person has left, % of answered | 4.4% | 10.8% | 17.5% | 24.6% | 33.2% | 32.2% |
| Work history recall% of reference roles | 96.1% | 86.1% | 69.6% | 17.3% | 16.5% | 17.1% |
| Queried on | 2026-09-17 | 2026-09-17 | 2026-09-17 | 2026-09-18 (+1d) | 2026-09-17 (+1d) | 2026-09-17 (+1d) |
| Separate recomputation | 9 of 9 pass | 9 of 9 pass | 8 of 9, 1 warning | 9 of 9 pass | 9 of 9 pass | 9 of 9 pass |
No price appears anywhere on this page, and no billing unit either. None of the providers tested publishes a per-unit list price we could verify and date, and a cost comparison built on quoted rates would not be checkable. Ask each provider for the rate it quotes you, and apply it to the volume you actually send.
09
How we ran the test
The reference
On the day of the test, the public LinkedIn profile of every contact was read from a source that is none of the providers tested, one row per role held. 3,916 profiles came back, 100.0% of those requested, producing 39,836 experience rows.
It comes from none of the providers being tested. A benchmark scored against one vendor's database measures similarity to that vendor, not accuracy.
The rules
Every provider received the same list, one query per contact, through its own public API with the same input. Employers are matched by LinkedIn company id, then company URL slug, then normalized company name; then the title on the matched role, after normalization.
Before publication, a separate script recomputes every verdict and aggregate from the raw answers: 9 checks per provider. Prospeo passes with a warning, on a field its answers never fill. The reference itself passes 12 of 13 gates.
Who was left out
- 435started the current job in the month of the test, so no index could reasonably have seen it yet
- 20have no current role on their profile, so there is nothing to be right or wrong about
- 15have fewer than 30 connections, our floor for an active account
- 1have no start date on the current role, so job age cannot be computed
They were removed before any provider was queried, never after. Excluding contacts once the answers are in is the easiest way to shape a benchmark.
The population
| Cohort | Contacts | What it isolates |
|---|---|---|
| New jobs · Americas | 835 | Recent job changes, Americas (Sales Navigator export, 17 Sept 2026) |
| New jobs · Europe | 723 | Recent job changes, Europe (Sales Navigator export, 17 Sept 2026) |
| Large cos · US/UK | 494 | Sample 1.1: marketing leaders, large companies (1,001-5,000+ employees), mostly US/UK |
| SMB industry · US | 490 | Sample 1.4: VP / Director marketing, 51-500 employees, US, manufacturing / medtech / pharma |
| SMB · EMEA | 454 | Sample 1.3: marketing leaders, 51-500 employees, EMEA (UK, DE, IL, FR, ES) |
| Micro cos · US | 449 | Sample 1.2: marketing / growth leaders, very small companies (1-50 employees), mostly US |
The providers, and how each was queried
- BlitzAPIPOST https://api.blitz-api.ai/v2/enrichment/person
- ApolloPOST https://api.apollo.io/api/v1/people/match
- ProspeoPOST https://api.prospeo.io/enrich-person
- QuickEnrichGET https://app.quickenrich.io/api/employees/search
- MoltSetsPOST https://api.moltsets.com/api/v1/reverse_linkedin_lookup
- GetLeads.ioDirect API route not published here
Each provider keeps the same colour in every figure and in every edition, from the first report it appears in. Colours follow the order providers first appear, then the alphabet, never the ranking, and the provider publishing the test never takes the colour closest to its own brand.
Full protocol, definitions, uncertainty rules, limits and the corrections policy: the methodology page.
10
Download the report
The report as one printable document, with every figure and every number drawn from the same data as this page.
You are reading it. This document is the report page, printed: every figure and every number in it comes from the same data as the page. The live version is at blitz-api.ai/benchmarks/contact-data-september-2026.
Figures with a measure selector print on their default measure; the other measures stay on this page.
sha256 31f12affc4d9a9a2
No row in this report identifies a person. If you appear in a reference and want out of future runs, write to antoine@blitz-api.ai.