← ClaudeAtlas

enrichment-waterfalllisted

Use when the user says "enrich this list", "find emails", "our match rate is low", "which provider should we use", "enrichment is expensive", "build a waterfall", "fill in these fields". Designs a cost-ordered multi-provider waterfall with a free gate in front, verification, graceful exit, and per-tier economics. Writes workspace/data/waterfall-spec.csv.
guerrilla2799/ops-and-scale-os · ★ 1 · Data & Documents · score 74
Install: claude install-skill guerrilla2799/ops-and-scale-os
# Enrichment Waterfall Fill fields at the lowest defensible cost per usable record. The design decision that matters is ordering, not vendor selection. ## When to use - Any list needs contact or company data attached - Match rates are below benchmark - Enrichment spend is growing faster than the list - Choosing or replacing a provider ## Inputs - Reads: `workspace/data/universe.csv`, `workspace/data/object-model.md` - Needs from user: which fields are actually required, geography mix, current provider set and pricing, current match rate if known ## Workflow ### 1. Cut the field list Ask which fields will change a decision. Every field that will not is pure cost. The usual honest answer for outbound is: verified email, title, seniority, and one firmographic. Everything else is nice to have, and nice to have is billed at the same rate as necessary. ### 2. Put a free gate in front This step saves more money than every other step combined, and it costs nothing. ``` GATE (free or already-known fields only) Employee count in range? from sourcing data Industry in the allowed set? from sourcing data Geography in scope? from sourcing data Not on the suppression list? local file Not already in CRM with data? local join ↓ Only survivors proceed to paid columns ``` A well-built gate removes 40 to 70% of rows. If your gate kills under 25%, it is too permissive and you are overspending on rows you will discard anyway. **