The Enrichment Bake-Off: Don’t Crown a Winner, Map the Coverage
We needed a verified cell for every contact, so I ran two vendors head-to-head for about thirty-three cents. Neither won. The fix was a cost-ordered waterfall, and the most predictive field was free.
Forwarded to you? I am Heath. I build go-to-market systems and put AI to work in sales, the right way, then I write down exactly what I built, what broke, and what it moved. One story per week, receipts only. This one is about the vendor bake-off that stopped being about who wins.
| 1 | The cell phone is the wall. Email is easy, almost anyone has it. The mobile is the field most vendors are thin on, and the one that gets a rep a live conversation. |
| 2 | Pick one vendor and hope is the wrong game. A head-to-head that only asks who is better misses who actually lands the hard signal, and where each one falls short. |
| 3 | Neither vendor won. They covered different halves. On any given contact one had the cell, the other the email. The answer was a waterfall, not a single pick. |
| 4 | The cheapest question won. A free MX lookup was the most predictive field, and 9 of 10 supposedly-cold accounts were already known to a vendor. Same data, a fraction of the spend. |
The reflex: pick the best vendor and hope it covers everyone
Every team buying contact data reaches for the same move. Reps need a verified email and a cell for every account. So you line up the vendors, read the mobile-coverage pitch, sign the one that sounds strongest, and hope it lands the numbers you cannot get anywhere else.
I did exactly that. Reps needed a verified email and a cell for every contact. Email was easy, almost anyone has it. The cell was the wall, the field most vendors are thin on, and the one that actually gets a rep a live conversation. My instinct was to pick the vendor with the best mobile story and move on. Then I ran a controlled sample before I signed anything, both vendors against the same accounts, for about thirty-three cents total, scored on the one field that mattered. Neither vendor won. They covered different halves. On any given contact one had the cell and the other had the email.
The block was never the vendor. It was the question. A head-to-head that only asks who is better cannot tell you who lands the hard signal or where each one falls short. Worse, 9 of 10 accounts I thought were cold were already known to one vendor or the other. The data was not missing. My model for buying it was.
The AE feels this as "I need a direct dial to get a live conversation." The CSM feels it as "I need the decision-maker's current line, not one that is eighteen months stale." The marketer feels it as "I need a verified email that will not bounce past the sending threshold." Same reflex every time: one vendor, signed on a pitch, asked to own a signal no single source owns.
The reframe: run the bake-off to map coverage, not crown a winner
Contact data is not a vendor you pick. It is a signal, and no single vendor owns all of it. The move is not to crown the best provider. It is to take the loud question everyone asks and drill it down to the one quiet, specific thing that actually controls the cost.
Do not crown a winner. Map the coverage, then rank the stack by cost.
Same move, other seats. An AE drills "which vendor is best" down to "which rung lands the direct dial for this one persona." A CSM drills "who owns our account data" down to "which source has the current decision-maker, and which one is stale." A marketer drills "which email tool" down to "which verifier keeps the bounce rate under the threshold." The loud question is never the one you act on. The cheapest predictive field underneath it is.
How the best teams frame it
I am not the first person to argue that no single vendor is enough. The operators who have built enrichment at scale mostly agree on where the leverage is, and it is not the vendor. It is the sequence and the cost order.
SOURCE
Clay, "The Complete Guide to Waterfall Enrichment"
What it argues. Waterfall enrichment queries providers in sequence and only bills you when one returns a usable value, which is how teams push contact coverage from roughly a third to over eighty percent without a single annual contract. You do not buy one vendor, you order many and pay per hit.
My take. Agree, and the billing model is the part people skip. If you only pay when a provider hits, then the order of the providers is the whole cost story. Rank them cheapest-first and the coverage gain is nearly free.
SOURCE
Unify, "Waterfall Enrichment: The 2026 B2B Contact Data Architecture"
What it argues. Single-source enrichment leaves a large share of qualified prospects unreachable, so a layered, multi-provider architecture is now table stakes rather than a growth hack. The reachable record is assembled across sources, not bought from one.
My take. Extend. Architecture is right, but sequence beats stack. Put the cheapest predictive field first, or you pay a premium vendor for coverage a free lookup could have flagged.
SOURCE
Cleanlist, "15 Best B2B Data Enrichment Providers, Tested on 1,000 Leads"
What it argues. Run the same benchmark list through every provider and accuracy and coverage swing widely by field, especially on mobile. No provider tops the table on everything, and the gaps do not overlap the same way twice.
My take. Agree hard. This is the bake-off run in public, and it lands where mine did. Because no vendor owns every field, you map what each one covers instead of crowning a winner.
Even a curator has to concede when the field agrees: nobody who has actually built this thinks one vendor is the answer. The sequence and the cost order is the moat.
The method: Solve, Stack, Split
SOLVE THE CRUX
What is the real problem, framed as work and not a headcount?
The problem is not "which vendor should we buy." It is "which cheapest field lands the cell, and in what order." So the first work is a controlled sample: run both vendors against the same accounts, for about thirty-three cents total, and score them on the one field that matters, a valid reachable mobile, not just an email. For the AE that field is the direct dial, for the CSM the decision-maker's current line, for the marketer the verified email that will not bounce.
STACK THE CONTEXT
What tech and signals turn a raw list into a landed cell a rep can call?
Not a pile of vendor logins. The free field goes first: a simple MX-record lookup flags which accounts run our best-fit email stack, and it costs nothing. Then Deepline orchestrates the waterfall, running FullEnrich, Findymail, LeadMagic, and ContactOut in cost order until one returns a verified cell. The expensive vendor only fires when the cheaper rungs miss. One workflow, not five browser tabs.
SPLIT · CUT THE DRAG
What low-judgment work goes to the system?
The lookups. Run the MX check, then each provider cheapest-first, verify the mobile, stop when one hits. Every contact, every list, in cost order, with no human clicking between vendor dashboards. This is the part that never scaled when a person did it by hand, and the part AI does perfectly because it is mechanical.
SPLIT · KEEP THE JUDGMENT
What stays human?
The model. The operator decides which vendor owns which half of the signal, what counts as verified, and when the sample is big enough to trust. Neither vendor won the bake-off. Reading that, and turning it into a cost order, is judgment, not a query.
The workflow: the board that runs it
Solve, Stack, Split is the shape. Here is the actual board, lane by lane: what the agents run, what stays human, and the tool at each step. Once it is wired, the whole thing runs on any list without anyone stitching vendors together by hand.
What it moved
At a company I was at, an outbound sales team that lived and died on reaching a live person, this is the exact build I ran. Sample both vendors on the hard signal, ask the free question first, then waterfall the rest in cost order.
The reps did not buy more data. They stopped paying the expensive vendor for fields a free lookup or a cheaper rung already had, and they got a contact good enough that a dollar of pipeline books better than 1 in 3 instead of 1 in 5. Coverage and cost came from ordering the stack, not from signing a bigger contract.
Both of my receipts are outbound-side. Drop your own workflow in. A CSM turns the same build into a contact-hygiene sweep: run the book through the cost-ordered waterfall and refresh the decision-maker line before a renewal call. A marketer turns it into a deliverability gate: verify every email cheapest-first so the campaign clears the sending threshold instead of burning the domain.
WHAT I LEARNED
1. Do not run a bake-off to crown a winner. Run it to map what each vendor covers. Neither one wins outright.
2. The most predictive field is often the cheapest. A free MX lookup beat the expensive vendor at flagging which accounts to trust.
3. Rank the stack by cost and run it as one waterfall. The expensive vendor fires last, only when the cheap rungs miss.
4. Verify the hard signal, the cell, not just the email. A reachable mobile is what turns a record into a live conversation.
Run this one this week
Do not sign a vendor. Take one list of fifty contacts you think are cold. Run a free MX lookup first, then your two cheapest sources, and only then the expensive one. Count how many were already reachable before you paid the premium. That is the bake-off in miniature, and it tells you the shape of your waterfall before you commit a budget to it.
Two builds that sit next to this one:
- Scoring the TAM — "You cannot prioritize a market by scoring one deal at a time. Put the entire TAM through one rubric and make reps work the ranked list top-down." The enriched, verified contact is what makes that ranked list callable.
- The ICP Playbook — "A firmographic filter is not an ICP; it is a list. Derive the real one from evidence, then your ICP survives contact with a real pipeline." Enrichment is wasted until you know which fields define the fit worth paying for.
This is one build from the Build Log. Every week I take one sales or revenue problem, run it through the loop, and show the receipts. If someone forwarded this, the subscribe button is right below. Keep building. Heath.
You bought the signal. You never built the motion.
Everyone can capture intent now. The pipeline leaks in the gap between knowing and acting. What I got wrong, and what I am asking Adam Robinson on air.
The Seventh Analyst: The Agent That Reads the Other Six
Anyone can stand up six AI analysts. The one that makes the system compound is the seventh, the meta-analyst that reads the others' audit trails and turns every miss into a rule the next run enforces.
The Governance File: How a Pipeline Stops Repeating Its Worst Week
When you automate, your failures go silent. This build turned every past break into an enforced gate, so a fixed bug stays fixed and nothing broken ships confidently again.