Waterfall Enrichment for Reach, Built in Clay
One data provider finds valid emails for 60 to 75 percent of a real list, which means a quarter of your market is unreachable before you send a thing. This playbook builds the waterfall that lifts coverage to 85 to 92 percent while spending credits cheapest-first.
The problem
Every provider has blind spots by geography, industry and seniority. Buy one contract and you inherit its gaps: bounced emails burn your domain reputation, missing phone numbers strand your SDRs, and the accounts your provider cannot see simply never enter your pipeline. Buying two or three full contracts to compensate multiplies cost without logic connecting them.
This playbook is part of the companion set to Data Orchestration in 2026: Why Clay Sits Under Every Modern GTM Stack. Read that first for the strategy; this is the build.
What you will build
A Clay People Enrichment table that runs each contact through a provider chain in sequence, cheapest first, stopping at the first valid result. Emails are verified before they count, failed steps are not charged, results write back to the CRM, and a coverage dashboard tells you exactly what each provider is earning.
The stack
Architecture
One request, many providers, one answer: the contact enters, the chain runs until a step hits, verification gates the result, and only verified data reaches the CRM.
Clay tables and connected objects:
The build, step by step
Load the list and set the guard rails
Import contacts from your CRM sync or a CSV. Before any enrichment, add a qualification formula so you never spend credits on rows you would not contact anyway:
Return true only if Employee Count is between 50 and 5000, Country is in (US, CA, UK, DE, FR, AU), and Title contains any of: revenue, sales, marketing, growth, operations. Otherwise return false.
Set every enrichment column to Only run if this gate is true. This one setting typically cuts credit spend 30 to 50 percent.
Build the email waterfall, cheapest first
Add a column with Enrich Data → Work Email → Waterfall. Clay presents the provider menu with per-hit credit prices; order yours cheapest to most expensive. A typical 2026 chain:
- Apollo (2 to 3 credits) → Prospeo (3) → LeadMagic (3 to 4) → Findymail (4)
- Each step runs only if the previous returned nothing, and misses are not charged.
Start with two providers, measure the marginal hit rate of each addition for a week, and only then add a third and fourth. The most common Clay budget blowup is turning on a five-provider waterfall on day one.
Verify before you trust
Add a verification column (BounceBan or ZeroBounce through the marketplace) that runs on any found email. Then add a formula column Sendable Email:
If Verification Status is "valid" return the email. If "catch-all" return the email only if the winning provider was Findymail or Prospeo (their catch-all accuracy is higher). Otherwise return blank.
Only Sendable Email ever writes to the CRM or reaches a sequencer. This is the difference between 85 to 92 percent coverage and a burned sending domain.
Add the phone waterfall where it pays
Direct dials cost 10 to 40 credits per hit from premium providers, so gate them harder: run phone enrichment only where Title seniority is Director or above AND account tier is 1 or 2. The same waterfall pattern applies; the gate is just stricter because the credits are 10x.
Write back and record the receipts
Use Write to CRM to update the Contact with Sendable Email, phone, and an Enriched At timestamp. Add columns capturing the winning provider and credits spent per row; your coverage dashboard groups on them.
Gate passes: ~700 of 1,000 rows Email waterfall: ~4-8 credits average per found email Found emails: ~600 (85-92% of gated rows) Verification: ~1 credit per found email Total: roughly 3,500-6,000 credits per 1,000 raw contacts At Growth-plan rates: roughly $70-180 per 1,000, before phones
Schedule the refresh
B2B data decays 2 to 3 percent a month. Add a view of CRM contacts where Enriched At is older than 180 days AND account has open pipeline or fits current ICP, and run the waterfall on that view monthly. Refresh selectively; re-enriching everything is how credits vanish.
Measuring success
Measure reach in the sequencer and the CRM, and measure spend in Clay. The waterfall is working when coverage rises while cost per verified contact falls.
| Metric | Where to measure | Target | You know it is solved when |
|---|---|---|---|
| Email find rate | Clay coverage dashboard: found / gated | 85 to 92% | The unreachable quarter of your list shrinks to single digits |
| Verified deliverability | Sequencer bounce reports | Bounce rate under 3% | Domain reputation stops being a standing agenda item |
| Cost per verified contact | Clay credits spent / verified emails | $0.10 to $0.25 typical | Finance can predict enrichment spend within 10% |
| Provider marginal value | Coverage dashboard by winning provider | Every provider in the chain earns over 5% of hits | Renewal negotiations run on your data, not the vendor's deck |
Staffing the workflow
This is the lightest build of the five and the fastest payback. A fractional GTM engineer can run it.
| Phase | Hours | Who |
|---|---|---|
| Build: gates, waterfalls, verification, write-back | 10 to 15 hours | GTM engineer |
| Rollout: baseline coverage audit, first full run, dashboard | 4 to 6 hours | GTM engineer |
| Maintenance | about 2 hours per month | GTM engineer |
Maintenance and monitoring
Workflows drift as your GTM strategy, ICP and stack change. Keep this one honest with the following cadence.
- Check each provider's marginal hit rate monthly; drop any provider earning under 5% of wins and trial a replacement in its slot.
- Watch bounce rate weekly during active sending; over 3% means the verification gate needs tightening.
- Re-check credit prices after Clay marketplace updates; reorder the chain whenever relative prices change.
- Review the qualification gate when the ICP changes so you are not enriching yesterday's market.
- Cap monthly credit spend with a Clay workspace limit and alert at 80%.
Related
Want this running in your stack?
I build Clay-powered data orchestration systems for growth-stage GTM teams: this playbook and the four beside it, tuned to your ICP, CRM and motion.