Claude Code runs a tracked 63-query lead funnel
The author reports a Claude Code prospecting funnel that splits a broad query into about 63 segments, tracks claimed queries, filters by ICP and uploads only verified email leads.
Original prompt
Shared by the source author. See source notes for context.
/run-pipeline
Reach people exploring AI agents
See placements →What happened
The author reports a Claude Code prospecting funnel that splits a broad query into about 63 segments, tracks claimed queries, filters by ICP and uploads only verified email leads.
Reported by u/innovatekit on RedditHow the agent did it
- Split the national prospect query into state and company-size segments.
- Claim each query in a shared Markdown tracking sheet.
- Order and poll collection APIs, skipping empty datasets.
Where a person stepped in
The author defines the ICP classifier and reviews the funnel. No pre-send approval gate is disclosed, and the author says reply rates remain weak.
A Claude Code user describes an operating cold-email pipeline built around a broad Sales Navigator query containing roughly forty-five thousand prospects. To work within the reported per-query collection limit, the agent decomposes it by state and time zone, subdividing dense states by company size. The result is about sixty-three tracked queries.
A Markdown tracking sheet marks each query in progress or done, allowing parallel sessions to claim work. The agent orders, polls, exports and downloads data through the connected APIs, skips empty datasets and applies a custom ideal-customer-profile threshold before paid enrichment. Enrow finds email addresses, MillionVerifier checks them and only verified addresses are uploaded to Instantly campaigns.
The author identifies repeated queries and wasted credits as the prior problem, and reports a more organised campaign-generation workflow after implementing tracking. They explicitly say reply rates are still weak, so the account does not support a claim of strong sales performance or complete market coverage. No human pre-send approval rule is disclosed. The useful control is the per-query claim/status record and eligibility gate before enrichment, separating collection, classification, verification and upload. The suggested prompt adds a review checkpoint for a reader's version without attributing that checkpoint to the original system.
Prompt
Original prompt
Source: Reddit · u/innovatekit on Reddit
Frequently asked questions
Why split dense states again?
Some state queries still exceed the author’s reported collection limit, so company-size segments further bound them.
How are duplicate queries reduced?
A shared Markdown tracking sheet records in-progress and done status so sessions can claim unprocessed work.
Did the pipeline prove good reply rates?
No. The author says reply rates are not strong and treats better organisation and iteration as the benefit.
More details
Remaining steps
- Apply the ICP threshold before email enrichment and verification.
- Upload verified addresses and record completion with funnel results.
About this account
Claude Code chooses the next unprocessed query, handles asynchronous APIs, filters candidates and chains enrichment, verification, upload and reporting tools.
Firsthand account by u/innovatekit on Reddit; original publication date verified against Reddit created_utc 1771455282, converted to UTC calendar date. Outcomes are the author’s reports, not independently reproduced. Original pipeline-command name from the account; the full skill implementation and commercial credentials are not reproduced.
Credit: u/innovatekit on Reddit
Source published 18 Feb 2026
Source checked 14 Oct 2026
Tools and topics
Claude Code · Sales Navigator · Vayne.io · ICP classifier · Enrow · MillionVerifier · Instantly
Claimed query tracking · Lead verification · Prospect segmentation
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.