The DIY Waterfall Approach
Clay has become the go-to platform for teams that want to build their own enrichment waterfall instead of using a turnkey solution. With access to over 100 data sources, no per-seat charges, and workspace-level credit tuning, Clay gives you the raw materials to assemble a cascade that matches your exact needs. The trade-off is that you are the architect. You design the workflow, configure the logic, monitor the performance, and troubleshoot when things break.
This guide walks through building a complete waterfall enrichment workflow in Clay, from initial setup through optimization. If you have considered Clay but were not sure where to start, this is your blueprint.
Understanding Clay's Architecture
Clay works as a spreadsheet-like interface where each row is a record (a company or contact) and each column can pull data from different sources. The power comes from Clay's integration layer, which connects to enrichment APIs, CRM platforms, and dozens of other data tools.
When you build a waterfall in Clay, you are essentially creating a series of columns that query different data providers in sequence. Column A queries Provider 1. Column B checks whether Column A returned a result. If not, Column B queries Provider 2. Column C checks Column B, and so on. The conditional logic happens through Clay's formula system, which lets you write if-then rules that control when each provider gets queried.
This is fundamentally different from a turnkey waterfall platform where the cascade logic is built into the product. In Clay, you are building the cascade from scratch, which gives you more control but requires more setup time and ongoing maintenance.
Step 1: Define Your Data Needs
Before building anything, decide what data points you need for each contact. The typical B2B enrichment priority list:
- Work email address (verified)
- Mobile phone number
- Job title and seniority level
- Company name and domain
- Company size (employee count)
- Industry classification
- LinkedIn profile URL
Different providers in Clay's marketplace excel at different data types. Some are email-focused, some specialize in phone numbers, and others provide firmographic data. Mapping your priorities to provider strengths is the foundation of an effective cascade.
Step 2: Select Your Providers
Clay's 100+ data sources include many of the same providers that turnkey waterfall platforms use. For a solid email-finding waterfall, you might select four to six providers and arrange them by expected hit rate and cost.
A typical email waterfall configuration in Clay might use:
- Position 1: A broad-coverage email finder with good accuracy and moderate cost
- Position 2: A LinkedIn-derived email tool that catches contacts missed by database-first providers
- Position 3: A pattern-matching email generator that constructs likely email addresses based on company domain and name format, then verifies them
- Position 4: A specialized provider with strong coverage in your target industry or geography
For phone numbers, build a separate cascade. Phone data providers are typically different from email providers, and the hit rates are lower (phone data is harder to source). A phone waterfall might have three providers rather than four or five.
Step 3: Build the Cascade Logic
In Clay, the cascade logic is built using conditional columns. Here is the pattern:
Column 1: Email from Provider A. Query Provider A with the contact's name and company. This column either returns an email or returns empty.
Column 2: Email from Provider B (conditional). Write a formula: if Column 1 is empty, query Provider B. If Column 1 has a result, skip Provider B entirely. This prevents wasted API credits on contacts that were already found.
Column 3: Email from Provider C (conditional). Same pattern: if both Column 1 and Column 2 are empty, query Provider C.
Final column: Best email. A formula that returns the first non-empty value from Columns 1, 2, and 3. This is the email you use for outreach.
The conditional logic is what makes this a waterfall rather than a parallel query. Each provider only gets called when the previous ones failed, keeping your credit usage efficient. Without the conditionals, Clay would query every provider for every contact, burning through credits on redundant lookups.
Step 4: Add Verification
Finding an email is only half the job. You also need to verify it. Add a verification column after your final email column. Clay integrates with several email verification tools that check deliverability, detect catch-all domains, and flag disposable addresses.
This verification step is critical. Without it, you are trusting each provider's data quality at face value. As benchmarks show, hard bounce rates across enrichment tools range from 0.9% to 11.2%. Verification catches the bad data before it damages your sender reputation.
For phone numbers, add a line-type detection column that identifies whether the number is mobile, landline, or VoIP. This prevents your reps from wasting time calling office switchboards when they need mobile numbers for direct outreach.
Step 5: Configure Credit Management
Clay uses a credit system where different providers consume different amounts of credits per query. A cheap email finder might cost 1 credit per lookup while a premium phone number provider costs 5 credits. Your waterfall design directly impacts credit consumption.
Workspace-level credit tuning lets you set budgets per workflow, per provider, and per time period. Set daily or weekly credit limits to prevent a runaway workflow from burning through your entire monthly allocation. This is especially important during the testing phase when you are experimenting with different cascade orders and provider combinations.
Monitor your credit usage per provider per week. If Provider C in your cascade is consuming 30% of credits but only finding 5% of contacts, it is costing too much relative to its contribution. Either move it later in the cascade or replace it.
Step 6: Test and Optimize
Run your waterfall on a test batch of 500 contacts from your CRM. Measure:
- Overall find rate: What percentage of contacts got an email? Target: 85-95% for a well-configured waterfall.
- Per-provider contribution: What percentage of found contacts came from each position in the cascade? If Provider 3 is finding more contacts than Provider 2, swap their positions.
- Verification pass rate: What percentage of found emails passed verification? If a provider's emails fail verification at high rates, its data quality is suspect.
- Credits per valid contact: Divide total credits consumed by the number of verified contacts. This is your true cost metric.
Based on the results, reorder providers, replace underperformers, and adjust credit allocations. Run another 500-contact test batch and compare. Two or three rounds of testing typically gets you to an optimized configuration.
The DIY Trade-Offs
Building a waterfall in Clay gives you maximum flexibility. You choose exactly which providers to use, in which order, with which logic. You can build separate cascades for different segments, add custom logic for specific industries, and integrate with any tool that has an API.
The cost is time and expertise. Initial setup takes 4-8 hours for someone comfortable with Clay's interface. Ongoing optimization requires monthly performance reviews and periodic provider swaps. If a provider changes their API, raises prices, or degrades in quality, you are responsible for detecting and adapting.
Turnkey waterfall platforms handle all of this internally. They manage provider relationships, optimize cascade ordering, handle API changes, and deliver a simple interface where you submit contacts and get results. The trade-off is less control and potentially higher per-contact costs since you are paying for the platform's orchestration layer on top of the raw data costs.
For teams with technical chops and the time to invest in setup and maintenance, Clay offers a powerful and cost-effective way to build exactly the waterfall you want. For teams that prefer to focus on selling rather than data infrastructure, a turnkey platform with pay-per-valid pricing gets you to the same coverage outcomes with significantly less operational overhead. Both approaches beat single-source enrichment on coverage. The choice comes down to whether you want to build or buy your cascade.
