How to Build a Clay Enrichment Waterfall That Actually Works

You open a list of leads. Two hundred rows. Maybe three hundred. You fire up Clay, pick the shiniest data provider, hit enrich — and watch half your credits disappear on records that come back empty.

Congratulations. You've just done enrichment the expensive way.

It doesn't have to go like that. A properly built enrichment waterfall in Clay means you only pay for expensive data when cheaper options have already failed. It's sequenced, it's conditional, and once it's set up, it runs without you babysitting it.

Here's how to build one.

---

What a Waterfall Actually Is

The concept is simple. Instead of hitting one enrichment source and hoping for the best, you stack multiple providers in order — cheapest first, most expensive last. Each step only runs if the previous one came back empty.

Think of it like a literal waterfall. Water flows down. If it finds a pool at the first level, it stops. If that pool is dry, it keeps falling. You're not paying for the whole drop — just wherever it lands.

In Clay, this is done through conditional columns. Each enrichment column only fires when the field above it is blank. Stack them correctly and you get reliable data at a fraction of the cost.

---

Step One: Know Your Fields Before You Build

Before you touch Clay, get clear on what you actually need. The most common enrichment fields for B2B outreach are:

• Work email
• LinkedIn URL
• Company size
• Job title
• Company website
• Mobile or direct dial

Don't try to enrich everything at once. Pick the fields your workflow actually depends on. Enriching for things you'll never use is just noise — and credits.

---

Step Two: Order Your Providers by Cost

This is the part most people skip. They pick their favourite provider, enrich everything, and wonder why their Clay bill looks like a mortgage payment.

The general principle: free or flat-rate sources first, credit-heavy sources last.

A reasonable ordering for email enrichment looks something like this:

1. LinkedIn data already in the row — if it's there, use it before you spend anything
2. Claygent (Clay's built-in AI agent) — often surprisingly good for finding publicly available info
3. Hunter or Apollo — solid mid-tier options with good coverage on company emails
4. Prospeo or FindyMail — strong on deliverability, worth including for validation
5. Datagma or Dropcontact — good for European coverage in particular
6. RocketReach or Snov.io — deeper but pricier, used as fallback only

For phone numbers, the cost curve is steeper. Hold those providers for the end of your waterfall and only trigger them when email has already failed — or when the persona genuinely requires a direct dial to convert.

---

Step Three: Build the Conditional Logic in Clay

Here's where it gets practical.

In Clay, you add your first enrichment column — say, Hunter for email. Then you add a second column for your next provider. In the settings for that second column, set it to only run if the email field is empty.

Repeat this for every provider in your stack. Each column checks whether the field above it is blank. If it's filled, it skips. If it's empty, it fires.

A few things that save time here:

• Use a "final email" column that pulls the first non-empty result across all your enrichment columns. This keeps your output clean regardless of which provider found it.
• Add a validation step at the end. Run the final email through a verification tool — MillionVerifier or NeverBounce work well — before anything goes near your outreach tool. Bounced emails damage sender reputation. Don't skip this.
• Log which provider found the email. It sounds like admin, but over time this data tells you which providers are actually earning their place in your waterfall.

---

Step Four: Test on a Small Batch First

Build the full waterfall. Then run fifty rows before you run five thousand.

Check your match rates at each provider level. If Hunter is finding 70% of emails, your waterfall is doing its job — the expensive providers are barely getting used. If your first provider is consistently empty, you might have a list quality problem, not an enrichment problem.

Fix the inputs before you blame the workflow.

---

The Part That Matters Most

A Clay enrichment waterfall isn't complicated. It's disciplined. It's deciding in advance what order to try things and sticking to it, rather than defaulting to whichever provider you discovered last week.

The teams who get this right spend a fraction of what everyone else spends. They get the same data — often better data — because they're validating at the end instead of trusting blindly at the start.

Build the waterfall once. Let it do the work.

If you're setting up Clay for the first time or want to stress-test what you already have, I'm happy to take a look. Drop me a message.