First Customer Finder
Find evidence-backed potential first customers, beta users, or design partners from...
Install
npx skills add Kappaemme-git/codex-first-customer-finder-skill --skill first-customer-finder -g -a claude-code -y- Repository
- Kappaemme-git/codex-first-customer-finder-skill1.1k
- Category
- Design
- Updated
- 2mo ago
- License
- MIT
- Context cost
- Mediumabout 2,227 tokens
- Runs scripts
- Yes, review before use
What it does
Find evidence-backed potential first customers, beta users, or design partners from public demand signals. Use for product-specific prospect research, qualified shortlists, source-grounded outreach drafts, and follow-up searches refined by the user's feedback and local prospect history. Does not send outreach automatically.
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 before researching or scoring prospects and references/report-artifact.md before creating the final report. For saved history, feedback, or a repeat search, also read references/feedback-and-history.md.
Use English by default; follow an explicit language request. Keep the chat handoff short and put the useful detail in the report. Research requires available web search/browser tools; the bundled Python helpers only validate, export, and manage local files. If live browsing is unavailable, report that limitation instead of inventing leads.
Workflow
1. Understand the product
- Inspect the supplied URL, repository, landing-page copy, or product description.
- 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.
- Use one stable product-specific workspace folder. If its history exists, inspect the saved preferences and excluded prospects before searching. Never load another product's history just because it is nearby. State briefly where history will be saved; respect requests for no saved history.
2. Build a public-signal search plan
Search current public sources for:
