Work Email Finding: a 292 Person Receipt

Measured 2026-09-16. Quality is a tie across vendors. Cost is the gap.

We ran a 292-person list (88 orgs, 16 industries, name + domain only) through five aggregators and compared the returned emails against each org's published team-page address. Every person had a public team-page email, so find rates are inflated vs. a cold list; cost per row and exact-match rate are the clean comparisons.

The run

treg.people.email.find routed across catalog providers that answered (QuickEnrich ~61%, Kitt ~36%, plus Tomba, DropLeads, Hunter, Findymail). The other columns represent alternative aggregators, not the underlying providers.

	treg.to	Clay	Monid	Freckle	Deepline
Found	289	280	250	281	266
Exact match	264	262	233	263	253
Success (exact/292)	90.4%	89.7%	79.8%	90.1%	86.6%
Precision (exact/found)	91.3%	93.6%	93.2%	93.6%	95.1%
Off-domain	5	4	0	4	0
Cost (finding only)	$1.49	$10.34	$5.98	$11.22	$23.38
Per row	$0.0051	$0.0354	$0.0205	$0.0384	$0.0801
Per correct	$0.0056	$0.0395	$0.0257	$0.0427	$0.0924
Hit latency (median)	0.44s	11.2s	2.0s	65s	batch

Monid = Hunter only. Freckle = LeadMagic→Findymail. Deepline = ZeroBounce-first play. Clay dollars are at Clay's Launch data-credit list price ($0.05/credit on 2026-09-16).

What the numbers say

Quality is a tie. treg.to, Clay and Freckle land at 264, 262 and 263 exact matches; the difference is noise.
Different-from-published is mostly not invalid. Many returned addresses are valid aliases. Exact-match is a floor, not a ceiling.
Cost is structural. Credit-based waterfalls run 7x to 16x treg.to per correct row. Deepline is an outlier because ZeroBounce fires on every pattern guess.
Latency only matters for per-call paths. treg.to (0.44s) and Monid (2.0s) are per-call; do not rank batch tools on speed.
Aggregator columns are routes, not products. Each column represents how that aggregator dispatched the query to its underlying providers.

When to choose Clay

Choose Clay when you want a visual table, the broader Clay ecosystem for GTM orchestration, or a seat that already includes enrichment inside a bigger workflow. Spreadsheet-native teams may prefer the Clay UI over API calls.

Choose treg.to when you want a metered catalog call with a known provider price and a dated receipt. See how billing works.

Disclosures

List bias: every person had a published team-page email, so find rates are inflated vs. a cold list.
MillionVerifier re-verify: we re-verified addresses with MillionVerifier after Kitt ran out of credits. MV served 0 cache hits. Kitt is also in the treg.to catalog, so its hits are not independent for the treg.to column.
treg.to bug: 3 rows returned HTTP 502 (route_failed) and were scored as misses. $0 charged for those rows.