Enrichment Waterfalls for Startups (Without Defaulting to Clay)

Founders hear "enrichment waterfall" and assume it is a Clay feature they have to buy. In the Clay alternatives thread on r/gtmengineering, a repeated piece of advice is to split the problem: data APIs for finding emails and firmographics, a verification step, and an automation tool such as n8n to stitch the steps. In a consultants thread on r/coldemail, people who have actually wired this up keep circling the same warning: no single provider has perfect coverage.

Pramod Kumar, co-founder of Kingdom of Kumar. On X

·

That is the whole idea. A waterfall is a fallback order. You ask one source, then another, you verify before you write to the CRM or a sequencer, and you stop when the record is good enough — or when it is not, in which case you do not pretend.

This is not a Clay teardown. If Clay is already earning its keep, there is a separate article on when not to buy Clay and one on Clay alternatives. List quality sits beside this in How to build a B2B list without paying for bad data. The wider craft is on GTM engineer and GTM engineering.

I will not reprint vendor list prices or invent hit rates. Look at current pricing pages and run a small, honest test on your own domains the week you choose.

What a waterfall is, in working language

You have a record that is missing something you need before you are allowed to reach out: a work email, a role, a company size, a domain. You try sources in a fixed order. You write down what each source was allowed to overwrite. You verify the thing that can get you in trouble — usually the email — before it enters a sending tool.

That is all. It is not a personality. It is not "AI enrichment." It is an ordered set of lookups with a rule for empty results.

If you cannot name the fields you actually need, you do not have a waterfall problem. You have an ICP problem. Pause and write the fit rule first, and take the App Launch Score if the offer itself is still soft.

"No single provider has perfect coverage"

Write that sentence at the top of the sheet. Then act like you believe it.

Coverage varies by country, seniority, and how new the company is. A provider that looks excellent on US mid-market marketing titles can go quiet on a founding team in another market. If you let one vendor be the only vote, you will either under-contact people you could have reached, or you will store confident, wrong emails.

The practical response is not to buy five overlapping tools on day one. Pick a primary, one fallback for the field you care about most, and a verifier. Add a third source only after you have looked at a week of misses and can say, in a sentence, what the third source is for.

A starter waterfall you can run this month

Keep it smaller than the diagrams on Twitter.

1. Start with a record you already trust a little. Domain plus name, or LinkedIn URL plus company, is enough to begin. Do not begin with a 20,000-row dump.

2. Fill only the fields that gate outreach. For most early motions that is: work email, role, company, and one evidence field you will use in the first line. Everything else can wait.

3. Try sources in order. Example shape, not a recommendation of vendors: a primary email-and-firmographic API, then a second email API if the first returns nothing, then stop. Company size or industry can come from a different source than email. Do not let a company-size tool invent an email.

4. Verify the email before it can be sent. Verification is a separate step, not a feeling you have about the provider. If verification fails, the record does not enter the sequencer. It goes back to a "needs a look" pile.

5. Write results into a system you own. A CRM or a sheet, with source and date on the field. If two sources disagree, the field should show the conflict, not the last write.

6. Cap the experiment. Decide in advance how many records and how much budget this test may burn. Waterfalls get expensive when they retry out of curiosity.

You can stitch this with n8n or a similar tool, or even with a careful manual pass for the first hundred records. The manual pass will teach you where providers fail, which is the point of doing it before you automate.

Rules that keep the waterfall from lying to you

  • A blank is better than a guessed personal Gmail, unless you have a written policy for personal mail and a reason this person belongs on it.
  • Never overwrite a verified field with a new, unverified one.
  • Never let the sequencer pull records that skipped verification.
  • Log the source. In six weeks you will want to know which provider filled a bad email.
  • Recheck old emails before you reuse a list. People change jobs; inboxes die.
  • Do not "complete" a record by asking a model to invent the missing email or title.

When Clay is a reasonable place to put the waterfall

Clay can be a good workbench if you already understand the motion, you will cap credits, and someone on the team will actually maintain the tables. It is a weak first purchase if you are still deciding who you sell to, or if no one will look at the output. I will not pretend it is the only way to order a sequence of APIs. Several comments in the alternatives thread describe exactly this split: data providers, verification, automation. That path is more assembling than buying a platform, and it is a fair choice for a small team.

If a vendor or a GTM engineer insists the waterfall *is* the product, ask them to draw the steps on a page without their logo. If they cannot, they are selling you a home, not a method.

A one-afternoon test

Take fifty accounts you already know. Run your primary provider, then the fallback, then verification. Score, by hand: found and correct, found and wrong, not found. Do this in a sheet, in your own eyes. Then decide whether a second paid source is worth it, or whether you should spend the time improving the input list instead.

That test will tell you more than a comparison blog with unnamed "85% coverage" claims. I will not invent a coverage number for you, and you should be suspicious of anyone who will.

Where this sits in a wider system

A waterfall is a step, not a motion. It does not choose who deserves a message, and it does not write a first line you can stand behind. If you want help building the path around it — fit rules, approvals, sending infrastructure — Kingdom of Kumar builds and runs that kind of system on Grok and Claude for $500 a month, three-month minimum. You own it, and you approve what goes out. We will not quietly replace a waterfall with a single vendor because it is tidier on a slide.

FAQ

Do I need a waterfall if my list is small?

You still need verification and a rule for empty results. You may not need three paid sources. For a few dozen records, a primary provider plus a verifier plus a manual pass can be enough.

Is catching every possible email the goal?

No. The goal is trustworthy contact data for people you already decided to contact. Chasing coverage for its own sake is how budgets disappear.

Should I enrich inbound the same way?

Yes for the fields you need to route and reply. Be even stricter about not overwriting information the person typed into your form.

What about personal emails and mobile numbers?

Only with a written policy, a legal basis you actually understand, and a reason the motion requires them. Default to work email.

Contact

hello@work.kingdomofkumar.com