Skip to content

Enrichment waterfall economics

Measure enrichment by cost per verified record. Gate duplicates, set account-level budgets, and stop provider lookups once the required field is usable.

Goal: Control enrichment spend while measuring additional usable coverage.

Complexity

Medium

Tools

4

Context

The Problem

A team can buy more data without gaining more usable contacts. Duplicate rows, stale CRM values, and unmeasured provider overlap obscure the cost of the final record.

Before adding providers, establish which fields the campaign needs, which existing values remain usable, and what each account warrants spending.

Resolution

The Solution

Use the tiers and pilot design below as starting rules to test with your own data.

Level 1: Price what you already run

Export a recent, bounded cohort from the CRM. Retain the original account tier and source date. Freeze that cohort before comparing providers.

Define a usable record before running enrichment. For an email, record the identity match, verification outcome, and verification date. Decide explicitly whether catch-all addresses qualify. A returned string alone is insufficient.

Use two cost views:

Cost viewCalculationDecision
Incremental cash costExtra charges caused by the run / newly usable recordsWhether to run the next batch
Allocated operating costAllocated subscription, usage, verification, and operator cost / usable recordsWhether to renew or redesign the system

Avoid counting the same credits twice. If the subscription allocation already includes consumed credits, add only charges outside that allowance. Record currency and accounting period.

Build a worksheet with account key, person key, tier, existing field, last checked date, provider, attempt outcome, verification result, and charged usage. Keep missing results in the log.

Level 2: Run a tiered waterfall

Apply these gates in order:

  1. Dedupe by stable person and account keys.
  2. Check the existing CRM field and its freshness rule.
  3. Confirm the account belongs in the campaign.
  4. Assign the account's allowed field set and spend cap.
  5. Run the first provider only for missing or unusable fields.
  6. Validate the result against the campaign's definition.
  7. Continue only when the field remains unusable and budget remains.
  8. Save the result, source, checked date, and stop reason.
Suggested tierRequired dataStop rule
Named priority accountVerified work email; phone only if the motion uses itStop when required fields pass, or the approved account cap is reached
Standard ICP accountVerified work emailStop at a usable email or the tier cap
Exploratory accountCompany fit and existing contact dataQueue further spend until the account qualifies

These are proposed policies. Set the caps from expected account value and the pilot's actual costs.

Clay states that an enrichment returning no result consumes neither Data Credits nor Actions. Runs using your own API key consume Actions but no Clay Data Credits. Provider charges and other workflow steps still need separate accounting. Clay pricing.

Do not use a provider's advertised coverage as its position in the waterfall. Compare the additional verified records it supplies after earlier providers, the cost of those records, and how often its results fail verification.

Apollo's waterfall can use third-party sources when Apollo lacks the required contact data. Check team-wide settings before enabling another enrichment route. Apollo waterfall overview.

Level 3: Govern provider order

Use the same frozen cohort to compare the current sequence and one proposed alternative. Preserve raw outcomes so a changed verification rule cannot silently improve the apparent result.

Worksheet measureDefinition
Usable coverageUnique records meeting the field rules / eligible unique records
Incremental provider yieldNewly usable records first supplied at that step
Cost per added recordCost attributable to that step / incremental provider yield
Duplicate spendCharges on records that already met the freshness and usability rules
Rework ratePreviously accepted records later rejected / previously accepted records checked

Review results by segment. A provider that helps one geography may add little to another. Remove a provider only after comparing its marginal contribution with its full cost.

Keep a monthly owner review. Recheck provider terms when plans change. Test configuration changes on a capped batch, and retain the last working order for rollback.

How to measure the pilot

Allocated cost / usable records

Allocated cost per verified record

Usable / eligible records

Usable coverage

New usable records at that step

Incremental provider yield

Charges on already usable rows

Duplicate spend

Decisions to make before increasing coverage

Provider order

Traditional

Retain the order inherited from a template

Our Approach

Test marginal verified yield on a frozen cohort

Existing data

Traditional

Run every imported row

Our Approach

Check usability and freshness before a paid lookup

Budget

Traditional

Use one lookup depth across accounts

Our Approach

Set the required fields and cap by account tier

Cost

Traditional

Compare nominal cost per lookup

Our Approach

Separate incremental cash and allocated operating cost

Tools & Data

Minimum setup

Suggested tool roles; use existing contracts where they fit.

CRM : Stable keys, existing values, source dates, and campaign eligibility.
Enrichment platform : Conditional lookups, provider outcomes, and usage export.
Verification service : A documented pass, fail, and catch-all policy.
Worksheet : Allocated cost, incremental cash cost, and marginal provider yield.

Competitor Landscape

ToolApproachBest ForLimitation
One existing providerUse a single contracted source with verification.A narrow segment with adequate coverage.Measure whether missing records justify a second provider.
Managed waterfallConfigure provider order and conditional steps in an enrichment platform.Repeatable batches requiring multiple sources.Requires usage accounting and an owner for configuration.
Custom API sequenceImplement lookup gates, retries, and logs in code.Teams with engineering ownership and specific integration needs.Include maintenance time in the cost comparison.

Team Responsibilities

RoleResponsibility
RevOps leadOwn record keys, freshness rules, cost allocation, and provider changes.
Growth managerDefine account tiers, required fields, and whether additional coverage is commercially useful.

Failure Patterns

PatternWhat HappensWhyPrevention
Returned becomes verifiedThe report counts addresses that cannot be used.Lookup success and verification success share one status.Store both outcomes and apply one acceptance rule.
Subscription counted twiceThe calculated cost overstates the run.Included credits are counted again as separate spend.Reconcile allocation to the invoice before comparing providers.
Unbounded fallbackLow-priority records consume the remaining budget.The workflow has no tier cap.Stop on either a usable result or the approved cap.

ICP Fit Notes

Best fit

  • •B2B teams running repeatable enrichment batches
  • •Teams with reliable record keys and access to usage data

Also works for

  • •Small teams testing a second provider on a bounded cohort

Insight: First measure the records a second provider adds after the first has finished.

Implementation Checklist

Phase 1: Measure

  • Define usable fields and catch-all handling.
  • Freeze a cohort and export costs.
  • Separate allocated cost from incremental cash.

Phase 2: Configure

  • Add dedupe, existing-value, and freshness gates.
  • Set account tiers and caps.
  • Log outcomes and stop reasons.

Phase 3: Compare

  • Test one alternative provider order.
  • Compare marginal verified yield by segment.
  • Keep the previous configuration for rollback.

Phase 4: Maintain

  • Assign the monthly cost review.
  • Check contract changes before increasing volume.

FAQ

When NOT to Use

  • •The current provider already supplies adequate verified coverage; test the gap before adding complexity.
  • •Stable person keys are unavailable; fix deduplication before buying more data.
  • •No one can export or reconcile usage costs; establish the baseline first.
  • •The campaign does not use the extra fields being purchased; remove those lookups.
  • •No one owns provider changes or spending caps; keep the workflow bounded.
  • •The batch is too small to distinguish provider contribution; use a manual pilot and report its limits.

Tools & Tech

CRM
Clay or Apollo
Email verification service
Cost worksheet
Take the GTM Readiness Score

Put this playbook to work

Need help adapting this workflow to your team? Explore the relevant implementation services.