Lead finding skill

Find qualified prospects and decision-makers from ICP criteria using public research, company signals, role mapping, and source confidence.

by LeadMagic·MIT license·★ 62 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# Lead Finding

## Overview

The most common lead-finding mistake is relying on a single source — usually a B2B database like Apollo or ZoomInfo — and accepting whateve…

This skill provides a multi-source lead discovery methodology spanning eight source categories: B2B contact databases (Apollo, Sales Naviga…

For each source, the skill provides search templates, data extraction patterns, and guidance on which sources are most productive for speci…

## When to Use

- User says "find leads" or "build a prospect list" → activate this skill
- User asks "where can I find companies that match our ICP" → use this skill
- User mentions "lead sourcing," "account discovery," or "prospecting list" → this skill applies
- User has an ICP definition but no leads to work with

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Lead finding

LeadMagic/main1 file shown
SKILL.md
Show the full text339 lines

Lead Finding

Overview

The most common lead-finding mistake is relying on a single source — usually a B2B database like Apollo or ZoomInfo — and accepting whatever it returns as the universe of addressable accounts. Single-source lead discovery produces lists with systematic gaps: entire categories of companies that don't appear in one database but dominate another. The non-obvious rule is that high-quality lead discovery requires multiple, complementary sources, each with its own coverage bias, used in combination to triangulate the full universe of ICP-matching companies.

This skill provides a multi-source lead discovery methodology spanning eight source categories: B2B contact databases (Apollo, Sales Navigator), professional networks (LinkedIn Sales Navigator advanced search), code repositories and technical communities (GitHub, Stack Overflow, DevPost), funding and company databases (Crunchbase, PitchBook, Tracxn), job boards (LinkedIn Jobs, Indeed, Wellfound), conference and event lists (event sponsor/exhibitor lists, speaker rosters), industry directories and associations, and vertical-specific sources (G2/Capterra for SaaS, BuiltWith for technographics, SaaStr/Product Hunt for early-stage).

For each source, the skill provides search templates, data extraction patterns, and guidance on which sources are most productive for specific verticals (SaaS, fintech, healthcare, manufacturing, e-commerce, professional services). The output is a deduplicated, prioritized lead list with source provenance, ready for enrichment and scoring.

When to Use

  • User says "find leads" or "build a prospect list" → activate this skill
  • User asks "where can I find companies that match our ICP" → use this skill
  • User mentions "lead sourcing," "account discovery," or "prospecting list" → this skill applies
  • User has an ICP definition but no leads to work with
  • User's current lead source has dried up and they need new channels
  • Before running lead-enrichment or list-building

Do NOT use for:

  • Enriching existing leads with additional data — use lead-enrichment
  • Finding email addresses for known contacts — use email-finding
  • Building scored, prioritized lists in Clay — use list-building
  • Finding leads based on real-time signals — use signal-scoring

Authoritative Foundations

  • Winning by Design — SPICED Framework. The Situation component maps to lead sourcing: finding companies in the right "situation" (industry, size, stage) that is the starting point for SPICED qualification. The Decision component maps to identifying the right contacts within sourced companies.

  • Force Management — MEDDICC. The Economic Buyer, Champion, and Decision Process elements guide which contacts to find within sourced companies. Finding a company is not enough — you need to find the specific personas who can champion, influence, and authorize a purchase.

  • Gartner — Buying Committee Research. The finding that B2B buying committees average 6-10 decision makers informs the contact discovery strategy. Finding one contact at a company is insufficient — the skill targets identification of 2-4 key personas per account.

  • ColdIQ / Alex Hoar — Multi-Source Prospecting. The methodology of combining Sales Navigator, job boards, funding data, and conference lists to build comprehensive prospect lists rather than relying on a single database.

Prerequisites

  • Upstream skills: gtm-context (provides ICP definition, target industries, company size, geography). icp-scoring (provides scoring model to prioritize discovered leads).
  • Required inputs: ICP definition with specific firmographic criteria (industries, company size, geography), target personas with job titles.
  • Optional: Access to Apollo, LinkedIn Sales Navigator, Crunchbase, or equivalent tools. API keys for LeadMagic People Search and Role Finder for enhanced contact discovery.
  • Optional tools: LeadMagic People Search API to discover contacts at target companies. LeadMagic Role Finder API to identify specific personas by function and seniority.

Step-by-Step Process

Phase 1: Intake

Ask all questions at once:

  1. What is your ICP definition? (Industries, company size range in employees, revenue range, geography, any technographic requirements.)
  2. What are the 2-4 target personas you need to find at each company? (Job titles, department, seniority level.)
  3. What lead sources have you used before, and what were the results? (Coverage, quality, conversion rates.)
  4. What is your target list size? (How many unique companies do you want to find?)
  5. Do you have access to: Apollo, LinkedIn Sales Navigator, Crunchbase, or equivalent tools?
  6. What is your target industry? (This determines which vertical-specific sources to prioritize.)
  7. Are there any companies or types of companies you explicitly want to exclude?
Phase 2: Research

Source Prioritization by Vertical: Different verticals have different source strengths. Prioritize sources based on the target industry:

SaaS / Technology:

  • Primary: LinkedIn Sales Navigator (company search by industry + tech stack), Apollo (CSV export with tech filters), Crunchbase (funding + category), GitHub (open-source contributors and enterprise users), BuiltWith (technology stack detection)
  • Secondary: G2/Capterra (reviewing companies — they're evaluating your category), Product Hunt (early-stage companies launching products), job boards (hiring signals)
  • Tertiary: Conference lists (SaaStr, SaaSter, TechCrunch Disrupt), industry directories

Fintech / Financial Services:

  • Primary: Crunchbase/PitchBook (funding data), LinkedIn Sales Navigator (industry + company size), regulatory filings (SEC EDGAR for public companies)
  • Secondary: Job boards (compliance, engineering hires), conference lists (Money20/20, Finovate)
  • Tertiary: Industry associations, partner directories (Plaid, Stripe ecosystem)

Healthcare / HealthTech:

  • Primary: LinkedIn Sales Navigator, Crunchbase (healthcare category), FDA/regulatory databases, hospital/health system directories
  • Secondary: Conference lists (HIMSS, HLTH, JPMorgan Healthcare), job boards
  • Tertiary: Industry associations, academic medical center lists

Manufacturing / Industrial:

  • Primary: LinkedIn Sales Navigator (company size + industry), industry directories (ThomasNet, IndustryNet), trade association member lists
  • Secondary: Job boards (engineering, operations hires), conference lists (IMTS, Hannover Messe)
  • Tertiary: BuiltWith (technology stack), government contractor databases

E-commerce / Retail:

  • Primary: BuiltWith (e-commerce platform detection), LinkedIn Sales Navigator, Crunchbase, Shopify/Shopify Plus partner directory
  • Secondary: Job boards (marketing, e-commerce hires), conference lists (Shopify Unite, NRF)
  • Tertiary: SimilarWeb (traffic estimation for retail sites)

Professional Services:

  • Primary: LinkedIn Sales Navigator (service category filters), Clutch.co / agency directories, industry association member lists
  • Secondary: Job boards (client-facing role hires), conference lists
  • Tertiary: Crunchbase, GitHub (for technical consultancies)
Phase 3: Execution

Execute multi-source discovery following this sequence:

Step 1: B2B Database Export (Apollo or equivalent)

If you have Apollo access:

  • Use the Company Search with ICP filters (industry, employee count, revenue, location, technologies)
  • Export the full result set as CSV
  • Note: Apollo has coverage biases — it tends to overrepresent US-based, funded, tech-forward companies. This is your starting point, not your complete list.

Apollo search template per persona:

  • Title: [Persona title variants, comma-separated]
  • Company Industry: [Target industries]
  • Company Size: [Min]-[Max] employees
  • Company Location: [Target geography]
  • Seniority: [Director, VP, C-level as applicable]

Step 2: LinkedIn Sales Navigator Advanced Search

Sales Navigator provides company and people search with filters not available in regular LinkedIn:

Company search template:

  • Industry: [Target industries]
  • Company Size: [Min]-[Max] employees
  • Headquarters Location: [Target geography]
  • Annual Revenue: [Target range]
  • Technologies Used: [Key technologies if ICP includes technographics]

People search template per persona:

  • Title: [Persona title variants]
  • Function: [Department]
  • Seniority Level: [Target seniority]
  • Company Industry: [Target industries]
  • Company Size: [Target range]
  • Geography: [Target locations]

Export results using Sales Navigator's list-building feature. Note: LinkedIn terms of service prohibit automated scraping. Use native export features only.

Step 3: GitHub and Technical Communities (for technical ICPs)

For companies where technology stack matters:

  • Search GitHub for organizations using relevant technologies (e.g., topic:kubernetes org:, search for companies by their GitHub org pages)
  • Use Stack Overflow's company pages and job listings
  • Search DevPost for hackathon participants building in your problem space
  • Use npm, PyPI, or package registries to identify companies maintaining relevant packages

Step 4: Crunchbase and Funding Databases

For growth-stage and funded companies:

  • Search Crunchbase by category, funding stage, location, and employee count
  • Filter for companies that recently raised funding (funding is a buying signal — use signal-scoring to evaluate further)
  • Export company data including funding details, key people, and website

Step 5: Job Boards

Hiring signals are strong ICP indicators. Search:

  • LinkedIn Jobs: [Target titles] at companies in [Target industries]
  • Indeed: Same filters, different coverage
  • Wellfound (AngelList): For startup/tech companies
  • Built In: For tech hubs (Built In NYC, Built In SF, etc.)
  • Industry-specific job boards: Stack Overflow Jobs (tech), Behance/Dribbble (design)

Search for roles that indicate the company needs your product:

  • Hiring for the role your product serves → they have the problem you solve
  • Hiring for roles that manage the budget your product draws from → they have funding
  • Hiring for growth roles → they're scaling and likely re-evaluating tools

Step 6: Conference and Event Lists

Conference sponsor, exhibitor, and speaker lists are high-quality sources:

  • Identify 5-10 relevant industry conferences
  • Collect sponsor/exhibitor lists from conference websites
  • Collect speaker rosters (speakers' companies are engaged in the community)
  • Add attendee lists if available (some conferences publish these)
  • These companies are actively engaged in the ecosystem and have budget for industry participation

Step 7: Industry Directories and Associations

  • Industry-specific directories (e.g., AI 50, Cloud 100, Inc 5000, Deloitte Fast 500)
  • Trade association member directories
  • Chamber of Commerce business lists (by region)
  • Government contractor databases (for companies selling to government)

Step 8: Vertical-Specific Sources

  • G2/Capterra: Companies actively reviewing in your category — they're in-market
  • Product Hunt: Recently launched products — early-stage companies likely to be tool adopters
  • BuiltWith / Wappalyzer: Companies using specific technologies
  • Partner ecosystems: Companies using complementary products (e.g., if you integrate with Salesforce, find Salesforce customers)
  • SEC EDGAR: Public company filings — identify customers, suppliers, and partners

Step 9: Deduplication and Merge

After collecting from all sources:

  • Normalize company names (strip legal suffixes: Inc, LLC, Ltd, Corp)
  • Deduplicate on domain name (the most stable unique identifier)
  • For companies found in multiple sources, merge records and track source provenance
  • Flag companies found in only one source (may need additional verification)
  • Cross-reference against exclusion lists

Step 10: Initial Prioritization

Apply a lightweight prioritization before full enrichment:

  • Tier 1: Found in 3+ sources, recent funding or hiring activity
  • Tier 2: Found in 2 sources, matches core ICP criteria
  • Tier 3: Found in 1 source, matches core ICP criteria but may be a database artifact
Phase 4: Delivery

Deliver a structured lead list with:

  1. Company name (normalized)
  2. Domain
  3. Industry
  4. Employee count (range)
  5. Revenue (range if available)
  6. Location (HQ city/state/country)
  7. Source provenance (which sources found this company)
  8. Source count (number of sources)
  9. Key contacts found (name, title, LinkedIn URL if available)
  10. Prioritization tier
  11. Notes (funding events, hiring signals, conference participation)

Also deliver a Source Performance Summary showing how many unique companies each source contributed (accounting for overlap) and recommendations for which sources to prioritize in future lead-finding cycles.

Output Format

# Lead Discovery Report: [Company Name]

## Discovery Summary
- Total unique companies discovered: [#]
- Sources used: [#]
- Date range: [Start - End]

## Source Performance

| Source | Companies Found | Unique to This Source | Overlap % |
|--------|----------------|----------------------|-----------|
| Apollo | [#] | [#] | [%] |
| Sales Navigator | [#] | [#] | [%] |
| Crunchbase | [#] | [#] | [%] |
| Job Boards | [#] | [#] | [%] |
| Conferences | [#] | [#] | [%] |
| GitHub | [#] | [#] | [%] |
| [Other] | [#] | [#] | [%] |

---

## Lead List

| # | Company | Domain | Industry | Size | Location | Sources | Contacts | Tier |
|---|---------|--------|----------|------|----------|---------|----------|------|
| 1 | [Name] | [.com] | [Ind] | [# emp] | [City, ST] | [3 sources] | [2 contacts] | 1 |
| 2 | [Name] | [.com] | [Ind] | [# emp] | [City, ST] | [2 sources] | [1 contact] | 2 |

[Full lead list — recommend CSV export for large lists]

---

## Source-Specific Exports

### Apollo Results ([#] companies)
[Summary table]

### Sales Navigator Results ([#] companies)
[Summary table]

### Crunchbase Results ([#] companies)
[Summary table]

### [Additional sources]

---

## Recommendations
- Best sources for future cycles: [Ranked list based on unique contribution, quality, and cost]
- Sources to deprioritize: [Low-unique-contribution sources]
- Coverage gaps: [ICP segments not well represented in discovered leads]
- Next step: Run lead-enrichment on Tier 1 and Tier 2 leads

Quality Check

Before delivering, verify:

  • Were at least 3 distinct source categories used?
  • Is every company deduplicated (no duplicate entries)?
  • Are company names normalized (legal suffixes stripped)?
  • Does each lead include source provenance (which sources found it)?
  • Are contacts associated with the correct company?
  • Do prioritization tiers follow the documented criteria?
  • Are exclusion lists applied (no excluded industries or companies)?
  • Is the source performance analysis actionable (sources ranked by unique contribution)?
  • Are coverage gaps explicitly identified?
  • Is the output format ready for import into the next skill (lead-enrichment)?

Common Pitfalls

  1. Single-source dependency. Relying on Apollo or ZoomInfo alone produces systematic coverage gaps. Apollo underrepresents non-US, non-funded, and traditional-industry companies. Sales Navigator underrepresents very small companies. Crunchbase only covers funded companies. Multi-source is not optional — it's the difference between seeing 60% of your addressable market and seeing 90%+.

  2. Using the same search criteria across all sources. Each source has its own taxonomy and filters. "Manufacturing" in Apollo is not the same as "Manufacturing" in Sales Navigator. Adapt search criteria to each source's specific categorization system. Test and calibrate.

  3. Finding companies but not contacts. A list of companies without contacts is a research artifact, not a prospecting list. Every company in the lead list should have at least contact count and, for Tier 1 leads, specific contact names and titles. Use the persona definitions from ICP to guide contact discovery.

  4. Accepting database coverage as reality. If Apollo returns 500 companies matching your ICP in the US, there are almost certainly more than 500. The database return count is a lower bound, not the actual market size. Use the coverage gaps section to identify where additional sources might surface more leads.

  5. Skipping source provenance tracking. When a lead turns out to be high-quality (or low-quality), knowing which source it came from is essential for optimizing future lead-finding cycles. Without provenance data, you can't improve your sourcing strategy.

  6. Prioritizing volume over quality. A list of 5,000 poorly-matched leads is less valuable than 500 precisely-matched leads. Apply ICP criteria aggressively during discovery, not after. It's better to surface fewer, better-matched companies than to dump everything into enrichment.

  7. Neglecting vertical-specific sources. The B2B databases cover broad markets well but specific verticals poorly. Healthcare companies are better found through hospital directories than Apollo. E-commerce companies are better found through BuiltWith. Always include at least one vertical-specific source.

  8. Job board scraping that produces stale data. Job postings expire. Conference lists age out. Source data has a half-life. Track the date of data collection per source and flag leads from sources where the data is more than 90 days old for re-verification.

Execution Artifacts

  • references/framework-notes.md — Named frameworks and reference tables
  • templates/output-template.md — Deliverable shell for agent output
  • scripts/check-output.py — Lightweight deliverable validator
  • gtm-context: Run before this skill. Provides the ICP definition that drives search criteria.

  • icp-scoring: Run before this skill. Provides the scoring model to prioritize discovered leads.

  • lead-enrichment: Run after this skill. Takes the discovered lead list and enriches each company and contact with additional data.

  • signal-scoring: Run after this skill. Scores discovered leads on dynamic signals (hiring, funding, tech stack, intent) to identify active buyers.

  • list-building: Run after lead-enrichment. Builds production-ready prospecting lists in Clay with enrichment and verification.

  • email-finding: Run after lead-enrichment. Discovers email addresses for the contacts found during lead discovery.

1---
2name: lead-finding
3description: >-
4 Find qualified prospects and decision-makers from ICP criteria using public research, company signals, role mapping, and source confidence. Produces a prospect list spec, search strategy, qualification rubric, source log, and QA checklist. Use when building target lists or finding buyers at named accounts.
5license: MIT
6compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
7metadata:
8 version: "1.0.0"
9 author: LeadMagic
10 category: prospecting
11 tags: [lead-generation, prospecting, list-building, sourcing, discovery]
12 related_skills: [gtm-context, icp-scoring, lead-enrichment, list-building, signal-scoring, sales-navigator-prospecting]
13 frameworks: [Winning by Design SPICED, Force Management MEDDICC, Gartner Buying Committee Research]
14---
15# Lead Finding
16 
17## Overview
18 
19The most common lead-finding mistake is relying on a single source — usually a B2B database like Apollo or ZoomInfo — and accepting whatever it returns as the universe of addressable accounts. Single-source lead discovery produces lists with systematic gaps: entire categories of companies that don't appear in one database but dominate another. The non-obvious rule is that high-quality lead discovery requires multiple, complementary sources, each with its own coverage bias, used in combination to triangulate the full universe of ICP-matching companies.
20 
21This skill provides a multi-source lead discovery methodology spanning eight source categories: B2B contact databases (Apollo, Sales Navigator), professional networks (LinkedIn Sales Navigator advanced search), code repositories and technical communities (GitHub, Stack Overflow, DevPost), funding and company databases (Crunchbase, PitchBook, Tracxn), job boards (LinkedIn Jobs, Indeed, Wellfound), conference and event lists (event sponsor/exhibitor lists, speaker rosters), industry directories and associations, and vertical-specific sources (G2/Capterra for SaaS, BuiltWith for technographics, SaaStr/Product Hunt for early-stage).
22 
23For each source, the skill provides search templates, data extraction patterns, and guidance on which sources are most productive for specific verticals (SaaS, fintech, healthcare, manufacturing, e-commerce, professional services). The output is a deduplicated, prioritized lead list with source provenance, ready for enrichment and scoring.
24 
25## When to Use
26 
27- User says "find leads" or "build a prospect list" → activate this skill
28- User asks "where can I find companies that match our ICP" → use this skill
29- User mentions "lead sourcing," "account discovery," or "prospecting list" → this skill applies
30- User has an ICP definition but no leads to work with
31- User's current lead source has dried up and they need new channels
32- Before running lead-enrichment or list-building
33 
34Do NOT use for:
35- Enriching existing leads with additional data — use lead-enrichment
36- Finding email addresses for known contacts — use email-finding
37- Building scored, prioritized lists in Clay — use list-building
38- Finding leads based on real-time signals — use signal-scoring
39 
40## Authoritative Foundations
41 
42- **Winning by Design — SPICED Framework.** The Situation component maps to lead sourcing: finding companies in the right "situation" (industry, size, stage) that is the starting point for SPICED qualification. The Decision component maps to identifying the right contacts within sourced companies.
43 
44- **Force Management — MEDDICC.** The Economic Buyer, Champion, and Decision Process elements guide which contacts to find within sourced companies. Finding a company is not enough — you need to find the specific personas who can champion, influence, and authorize a purchase.
45 
46- **Gartner — Buying Committee Research.** The finding that B2B buying committees average 6-10 decision makers informs the contact discovery strategy. Finding one contact at a company is insufficient — the skill targets identification of 2-4 key personas per account.
47 
48- **ColdIQ / Alex Hoar — Multi-Source Prospecting.** The methodology of combining Sales Navigator, job boards, funding data, and conference lists to build comprehensive prospect lists rather than relying on a single database.
49 
50## Prerequisites
51 
52- **Upstream skills:** gtm-context (provides ICP definition, target industries, company size, geography). icp-scoring (provides scoring model to prioritize discovered leads).
53- **Required inputs:** ICP definition with specific firmographic criteria (industries, company size, geography), target personas with job titles.
54- **Optional:** Access to Apollo, LinkedIn Sales Navigator, Crunchbase, or equivalent tools. API keys for LeadMagic People Search and Role Finder for enhanced contact discovery.
55- **Optional tools:** LeadMagic People Search API to discover contacts at target companies. LeadMagic Role Finder API to identify specific personas by function and seniority.
56 
57## Step-by-Step Process
58 
59### Phase 1: Intake
60 
61Ask all questions at once:
62 
631. What is your ICP definition? (Industries, company size range in employees, revenue range, geography, any technographic requirements.)
642. What are the 2-4 target personas you need to find at each company? (Job titles, department, seniority level.)
653. What lead sources have you used before, and what were the results? (Coverage, quality, conversion rates.)
664. What is your target list size? (How many unique companies do you want to find?)
675. Do you have access to: Apollo, LinkedIn Sales Navigator, Crunchbase, or equivalent tools?
686. What is your target industry? (This determines which vertical-specific sources to prioritize.)
697. Are there any companies or types of companies you explicitly want to exclude?
70 
71### Phase 2: Research
72 
73**Source Prioritization by Vertical:** Different verticals have different source strengths. Prioritize sources based on the target industry:
74 
75**SaaS / Technology:**
76- Primary: LinkedIn Sales Navigator (company search by industry + tech stack), Apollo (CSV export with tech filters), Crunchbase (funding + category), GitHub (open-source contributors and enterprise users), BuiltWith (technology stack detection)
77- Secondary: G2/Capterra (reviewing companies — they're evaluating your category), Product Hunt (early-stage companies launching products), job boards (hiring signals)
78- Tertiary: Conference lists (SaaStr, SaaSter, TechCrunch Disrupt), industry directories
79 
80**Fintech / Financial Services:**
81- Primary: Crunchbase/PitchBook (funding data), LinkedIn Sales Navigator (industry + company size), regulatory filings (SEC EDGAR for public companies)
82- Secondary: Job boards (compliance, engineering hires), conference lists (Money20/20, Finovate)
83- Tertiary: Industry associations, partner directories (Plaid, Stripe ecosystem)
84 
85**Healthcare / HealthTech:**
86- Primary: LinkedIn Sales Navigator, Crunchbase (healthcare category), FDA/regulatory databases, hospital/health system directories
87- Secondary: Conference lists (HIMSS, HLTH, JPMorgan Healthcare), job boards
88- Tertiary: Industry associations, academic medical center lists
89 
90**Manufacturing / Industrial:**
91- Primary: LinkedIn Sales Navigator (company size + industry), industry directories (ThomasNet, IndustryNet), trade association member lists
92- Secondary: Job boards (engineering, operations hires), conference lists (IMTS, Hannover Messe)
93- Tertiary: BuiltWith (technology stack), government contractor databases
94 
95**E-commerce / Retail:**
96- Primary: BuiltWith (e-commerce platform detection), LinkedIn Sales Navigator, Crunchbase, Shopify/Shopify Plus partner directory
97- Secondary: Job boards (marketing, e-commerce hires), conference lists (Shopify Unite, NRF)
98- Tertiary: SimilarWeb (traffic estimation for retail sites)
99 
100**Professional Services:**
101- Primary: LinkedIn Sales Navigator (service category filters), Clutch.co / agency directories, industry association member lists
102- Secondary: Job boards (client-facing role hires), conference lists
103- Tertiary: Crunchbase, GitHub (for technical consultancies)
104 
105### Phase 3: Execution
106 
107Execute multi-source discovery following this sequence:
108 
109**Step 1: B2B Database Export (Apollo or equivalent)**
110 
111If you have Apollo access:
112- Use the Company Search with ICP filters (industry, employee count, revenue, location, technologies)
113- Export the full result set as CSV
114- Note: Apollo has coverage biases — it tends to overrepresent US-based, funded, tech-forward companies. This is your starting point, not your complete list.
115 
116Apollo search template per persona:
117- Title: [Persona title variants, comma-separated]
118- Company Industry: [Target industries]
119- Company Size: [Min]-[Max] employees
120- Company Location: [Target geography]
121- Seniority: [Director, VP, C-level as applicable]
122 
123**Step 2: LinkedIn Sales Navigator Advanced Search**
124 
125Sales Navigator provides company and people search with filters not available in regular LinkedIn:
126 
127Company search template:
128- Industry: [Target industries]
129- Company Size: [Min]-[Max] employees
130- Headquarters Location: [Target geography]
131- Annual Revenue: [Target range]
132- Technologies Used: [Key technologies if ICP includes technographics]
133 
134People search template per persona:
135- Title: [Persona title variants]
136- Function: [Department]
137- Seniority Level: [Target seniority]
138- Company Industry: [Target industries]
139- Company Size: [Target range]
140- Geography: [Target locations]
141 
142Export results using Sales Navigator's list-building feature. Note: LinkedIn terms of service prohibit automated scraping. Use native export features only.
143 
144**Step 3: GitHub and Technical Communities (for technical ICPs)**
145 
146For companies where technology stack matters:
147- Search GitHub for organizations using relevant technologies (e.g., `topic:kubernetes org:`, search for companies by their GitHub org pages)
148- Use Stack Overflow's company pages and job listings
149- Search DevPost for hackathon participants building in your problem space
150- Use npm, PyPI, or package registries to identify companies maintaining relevant packages
151 
152**Step 4: Crunchbase and Funding Databases**
153 
154For growth-stage and funded companies:
155- Search Crunchbase by category, funding stage, location, and employee count
156- Filter for companies that recently raised funding (funding is a buying signal — use signal-scoring to evaluate further)
157- Export company data including funding details, key people, and website
158 
159**Step 5: Job Boards**
160 
161Hiring signals are strong ICP indicators. Search:
162- LinkedIn Jobs: [Target titles] at companies in [Target industries]
163- Indeed: Same filters, different coverage
164- Wellfound (AngelList): For startup/tech companies
165- Built In: For tech hubs (Built In NYC, Built In SF, etc.)
166- Industry-specific job boards: Stack Overflow Jobs (tech), Behance/Dribbble (design)
167 
168Search for roles that indicate the company needs your product:
169- Hiring for the role your product serves → they have the problem you solve
170- Hiring for roles that manage the budget your product draws from → they have funding
171- Hiring for growth roles → they're scaling and likely re-evaluating tools
172 
173**Step 6: Conference and Event Lists**
174 
175Conference sponsor, exhibitor, and speaker lists are high-quality sources:
176- Identify 5-10 relevant industry conferences
177- Collect sponsor/exhibitor lists from conference websites
178- Collect speaker rosters (speakers' companies are engaged in the community)
179- Add attendee lists if available (some conferences publish these)
180- These companies are actively engaged in the ecosystem and have budget for industry participation
181 
182**Step 7: Industry Directories and Associations**
183 
184- Industry-specific directories (e.g., AI 50, Cloud 100, Inc 5000, Deloitte Fast 500)
185- Trade association member directories
186- Chamber of Commerce business lists (by region)
187- Government contractor databases (for companies selling to government)
188 
189**Step 8: Vertical-Specific Sources**
190 
191- **G2/Capterra:** Companies actively reviewing in your category — they're in-market
192- **Product Hunt:** Recently launched products — early-stage companies likely to be tool adopters
193- **BuiltWith / Wappalyzer:** Companies using specific technologies
194- **Partner ecosystems:** Companies using complementary products (e.g., if you integrate with Salesforce, find Salesforce customers)
195- **SEC EDGAR:** Public company filings — identify customers, suppliers, and partners
196 
197**Step 9: Deduplication and Merge**
198 
199After collecting from all sources:
200- Normalize company names (strip legal suffixes: Inc, LLC, Ltd, Corp)
201- Deduplicate on domain name (the most stable unique identifier)
202- For companies found in multiple sources, merge records and track source provenance
203- Flag companies found in only one source (may need additional verification)
204- Cross-reference against exclusion lists
205 
206**Step 10: Initial Prioritization**
207 
208Apply a lightweight prioritization before full enrichment:
209- Tier 1: Found in 3+ sources, recent funding or hiring activity
210- Tier 2: Found in 2 sources, matches core ICP criteria
211- Tier 3: Found in 1 source, matches core ICP criteria but may be a database artifact
212 
213### Phase 4: Delivery
214 
215Deliver a structured lead list with:
2161. Company name (normalized)
2172. Domain
2183. Industry
2194. Employee count (range)
2205. Revenue (range if available)
2216. Location (HQ city/state/country)
2227. Source provenance (which sources found this company)
2238. Source count (number of sources)
2249. Key contacts found (name, title, LinkedIn URL if available)
22510. Prioritization tier
22611. Notes (funding events, hiring signals, conference participation)
227 
228Also deliver a Source Performance Summary showing how many unique companies each source contributed (accounting for overlap) and recommendations for which sources to prioritize in future lead-finding cycles.
229 
230## Output Format
231 
232```markdown
233# Lead Discovery Report: [Company Name]
234 
235## Discovery Summary
236- Total unique companies discovered: [#]
237- Sources used: [#]
238- Date range: [Start - End]
239 
240## Source Performance
241 
242| Source | Companies Found | Unique to This Source | Overlap % |
243|--------|----------------|----------------------|-----------|
244| Apollo | [#] | [#] | [%] |
245| Sales Navigator | [#] | [#] | [%] |
246| Crunchbase | [#] | [#] | [%] |
247| Job Boards | [#] | [#] | [%] |
248| Conferences | [#] | [#] | [%] |
249| GitHub | [#] | [#] | [%] |
250| [Other] | [#] | [#] | [%] |
251 
252---
253 
254## Lead List
255 
256| # | Company | Domain | Industry | Size | Location | Sources | Contacts | Tier |
257|---|---------|--------|----------|------|----------|---------|----------|------|
258| 1 | [Name] | [.com] | [Ind] | [# emp] | [City, ST] | [3 sources] | [2 contacts] | 1 |
259| 2 | [Name] | [.com] | [Ind] | [# emp] | [City, ST] | [2 sources] | [1 contact] | 2 |
260 
261[Full lead list — recommend CSV export for large lists]
262 
263---
264 
265## Source-Specific Exports
266 
267### Apollo Results ([#] companies)
268[Summary table]
269 
270### Sales Navigator Results ([#] companies)
271[Summary table]
272 
273### Crunchbase Results ([#] companies)
274[Summary table]
275 
276### [Additional sources]
277 
278---
279 
280## Recommendations
281- Best sources for future cycles: [Ranked list based on unique contribution, quality, and cost]
282- Sources to deprioritize: [Low-unique-contribution sources]
283- Coverage gaps: [ICP segments not well represented in discovered leads]
284- Next step: Run lead-enrichment on Tier 1 and Tier 2 leads
285```
286 
287## Quality Check
288 
289Before delivering, verify:
290 
291- [ ] Were at least 3 distinct source categories used?
292- [ ] Is every company deduplicated (no duplicate entries)?
293- [ ] Are company names normalized (legal suffixes stripped)?
294- [ ] Does each lead include source provenance (which sources found it)?
295- [ ] Are contacts associated with the correct company?
296- [ ] Do prioritization tiers follow the documented criteria?
297- [ ] Are exclusion lists applied (no excluded industries or companies)?
298- [ ] Is the source performance analysis actionable (sources ranked by unique contribution)?
299- [ ] Are coverage gaps explicitly identified?
300- [ ] Is the output format ready for import into the next skill (lead-enrichment)?
301 
302## Common Pitfalls
303 
3041. **Single-source dependency.** Relying on Apollo or ZoomInfo alone produces systematic coverage gaps. Apollo underrepresents non-US, non-funded, and traditional-industry companies. Sales Navigator underrepresents very small companies. Crunchbase only covers funded companies. Multi-source is not optional — it's the difference between seeing 60% of your addressable market and seeing 90%+.
305 
3062. **Using the same search criteria across all sources.** Each source has its own taxonomy and filters. "Manufacturing" in Apollo is not the same as "Manufacturing" in Sales Navigator. Adapt search criteria to each source's specific categorization system. Test and calibrate.
307 
3083. **Finding companies but not contacts.** A list of companies without contacts is a research artifact, not a prospecting list. Every company in the lead list should have at least contact count and, for Tier 1 leads, specific contact names and titles. Use the persona definitions from ICP to guide contact discovery.
309 
3104. **Accepting database coverage as reality.** If Apollo returns 500 companies matching your ICP in the US, there are almost certainly more than 500. The database return count is a lower bound, not the actual market size. Use the coverage gaps section to identify where additional sources might surface more leads.
311 
3125. **Skipping source provenance tracking.** When a lead turns out to be high-quality (or low-quality), knowing which source it came from is essential for optimizing future lead-finding cycles. Without provenance data, you can't improve your sourcing strategy.
313 
3146. **Prioritizing volume over quality.** A list of 5,000 poorly-matched leads is less valuable than 500 precisely-matched leads. Apply ICP criteria aggressively during discovery, not after. It's better to surface fewer, better-matched companies than to dump everything into enrichment.
315 
3167. **Neglecting vertical-specific sources.** The B2B databases cover broad markets well but specific verticals poorly. Healthcare companies are better found through hospital directories than Apollo. E-commerce companies are better found through BuiltWith. Always include at least one vertical-specific source.
317 
3188. **Job board scraping that produces stale data.** Job postings expire. Conference lists age out. Source data has a half-life. Track the date of data collection per source and flag leads from sources where the data is more than 90 days old for re-verification.
319 
320## Execution Artifacts
321 
322- `references/framework-notes.md` — Named frameworks and reference tables
323- `templates/output-template.md` — Deliverable shell for agent output
324- `scripts/check-output.py` — Lightweight deliverable validator
325 
326## Related Skills
327 
328- **gtm-context**: Run before this skill. Provides the ICP definition that drives search criteria.
329 
330- **icp-scoring**: Run before this skill. Provides the scoring model to prioritize discovered leads.
331 
332- **lead-enrichment**: Run after this skill. Takes the discovered lead list and enriches each company and contact with additional data.
333 
334- **signal-scoring**: Run after this skill. Scores discovered leads on dynamic signals (hiring, funding, tech stack, intent) to identify active buyers.
335 
336- **list-building**: Run after lead-enrichment. Builds production-ready prospecting lists in Clay with enrichment and verification.
337 
338- **email-finding**: Run after lead-enrichment. Discovers email addresses for the contacts found during lead discovery.
339 

Discussion

Alternatives

AI Sales Team — Main OrchestratorYou are a comprehensive AI sales intelligence and outreach system for Claude Code. You help founders, sales teams, agency owners, and…Sales & ecommerce · MITAuto research publicAutonomous cold email campaign launcher. Takes one target company domain, scrapes their website, generates an ICP with Claude, pulls matching leads via Prospeo, enriches emails + company descriptions, personalizes each lead with parallel Claude Code Task sub-agents (A/B/C variants), and uploads as a live Smartlead campaign. Uses local JSON files for state (no database required). Use for automated daily campaign launches after you have an initial `client-profile.yaml` from /icp-onboarding. Triggers on "auto-research", "launch an automated campaign", "daily campaign", "run the research loop".Sales & ecommerce · MITABM Campaign — DIY PlaybookABM campaign skill for Claude Code: run a full Account-Based Marketing campaign end-to-end — from ICP definition to live LinkedIn Ads. Builds targeted account lists with Vibe Prospecting, enriches and scores companies with real-time B2B data, generates personalized ad creatives with Claude Code and Figma, pushes matched audiences to LinkedIn Ads, and monitors campaigns daily at scale. The complete GTM skill for AI-driven account-based marketing in Claude Code, Codex, Hermes-Agent, and OpenClaw. No agency needed.Sales & ecommerce · MITAccount contact shortlistContact data skill for Claude Code and Codex: build a ranked shortlist of decision-makers and contacts at a target company for outbound prospecting, deal acceleration, or renewal/expansion plays. Returns verified contact data including email, phone, LinkedIn profile, title, seniority, and department. Provide a company name or domain plus optional seniority focus or use case. Use for contact data enrichment, LinkedIn profile lookup, and building outbound contact lists. Works in Claude Code, Codex, Hermes-Agent, and OpenClaw.Business & ops · MIT