← ClaudeAtlas

iofind-customerlisted

Find and qualify evidence-backed potential first customers, early adopters, design partners, or beta users for a startup using recent public pain and buying signals. Use when the user types /io:find-customer or asks to analyze a product URL or idea, define an ideal customer profile, research public discussions and business pages, identify first-user prospects, rank lead fit and timing, prepare source-based outreach drafts, or create a shareable early-customer prospecting report — without sending messages automatically.
integratedoperations/io · ★ 0 · Data & Documents · score 70
Install: claude install-skill integratedoperations/io
# /io:find-customer — First Customer Finder Turn a startup URL or product description into a short, evidence-backed list of plausible first customers. Use public signals, preserve privacy, and distinguish a prospect from a confirmed buyer. Read [references/research-framework.md](references/research-framework.md) before researching or scoring prospects. Read [references/report-artifact.md](references/report-artifact.md) before creating the final report. Parse `$ARGUMENTS` as an optional leading mode keyword (see **Modes**) followed by the product URL or description. If no mode is given, use `standard`. If no target is given, ask the user for a URL or product description before starting. ## Workflow ### 1. Understand the product - Inspect the supplied URL, repository, landing-page copy, or product description (use `WebFetch` to read a URL). - Identify the product, outcome, buyer, user, price or buying motion, geography, and strongest use case. - Define one primary ICP, one adjacent ICP, pain triggers, positive signals, and disqualifiers. - Infer missing context when safe and label the inference. Ask one concise question only when ambiguity would materially change the search. ### 2. Build a public-signal search plan Search current public sources (use `WebSearch`, then `WebFetch` the original pages) for: - explicit tool or alternative requests - first-person descriptions of the target problem - manual workflows and repeated workaround complaints - migration, chur