Cold Email Engine That Killed the Clay Bill

A r/gtmengineering thread shared the playbook: 10K to 20K cold emails per client per month, run with Claude Code, and the move that materially cut the agency's Clay bill. Twenty-five upvotes and a long comment chain. The playbook is real. Here is the breakdown plus the honest tradeoffs.

The Volume Profile

10K to 20K cold emails per client per month is high-volume outbound. At that volume, every per-record cost matters. Clay's per-action pricing surfaces faster than teams expect. The agency in the thread reported a five-figure monthly Clay bill across their book of clients.

The Switch

Migrate the steady-state waterfalls out of Clay into Claude Code skills plus a multi-platform search API plus a focused emails vendor. Keep Clay for prototyping new waterfalls because the visual UI is fast for ideation. Run the high-volume, stable waterfalls in code.

The Stack

1. Claude Code: orchestration. One markdown skill per repeatable workflow.
2. Scavio: SERP, Reddit, and public LinkedIn-via-SERP. $30/mo for 7,000 credits, fast tier $0.003/query.
3. ZeroBounce or NeverBounce: email verification. Pay-per-verify, no flat fee.
4. Smartlead: sequencer plus inbox warmup. $39/mo plus per-inbox.
5. Postgres: enrichment store and dedupe.

What Each Step Costs Per Record

SERP discovery via Scavio: 1 credit at fast tier ($0.003). Reddit signal: 1 credit ($0.003). Email verify via ZeroBounce: $0.003 to $0.008 depending on plan. Postgres write: free. Total per record before sequencer: under $0.02.

At 20K records per month per client, that is $400 in API spend per client per month for the enrichment portion. Clay at the same volume ran $2K to $5K per client per month for the comparable enrichment depth.

The Claude Code Skill Pattern

Each repeatable workflow becomes a markdown file under~/.claude/skills. The skill defines inputs, the steps, and the expected output. Claude Code runs it. The agency's playbook has roughly six skills covering discovery, verify, score, sequence, dedupe, and report.

# discover-and-enrich.md
Inputs: domain, ICP description
Steps:
1. Scavio SERP for site:linkedin.com/in {{domain}}
2. Filter by ICP role match
3. Scavio Reddit search for {{domain}}
4. ZeroBounce verify the candidate emails
5. Score against ICP description
6. Write top 25 to Postgres
Output: Postgres rows + summary digest

What This Lost Versus Clay

Visual debugging. Clay's UI shows every step of the waterfall in one screen. Claude Code shows logs and final output. For prototyping a new waterfall, Clay is faster. For running a stable waterfall, the visual UI is overhead.

What This Won

Cost per record dropped 70%+ at steady state. Latency dropped (no Clay run queue waiting). Customization became easy (every step is markdown). And the agency could run more clients on the same headcount because the steady state did not need babysitting.

The Playbook in Practice

Day one for a new client: prototype the waterfall in Clay because the UI is fast. Day five, when the waterfall stabilizes: port to a Claude Code skill with Scavio plus ZeroBounce plus Postgres. Day ten: run at full volume. The migration takes one engineer-day per client.

Where Clay Still Wins

Prototyping new waterfalls. Onboarding non-engineers. Visual review with the client. None of these are obsoleted by code. Clay Launch at $185/mo per workspace fits the prototyping budget.

The Honest Tradeoff

High-volume agencies should split the workload: Clay for prototyping, code for production. Solo operators running under 5K records per month per client may not hit the breakeven. The cost-cut math gets clear above 10K records per month per client.