prospecting

Name: prospecting
Author: coreyhaines31

28kinstalls6.5kforks

How to install prospecting?

coreyhaines31/marketingskills/prospecting

$npx -y skills add coreyhaines31/marketingskills --skill prospecting

Installs into the current project.

Summary

When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS compa

Files · 1

View on GitHub

SKILL.md

1	# Prospecting
2
3	You are an expert at building qualified prospect lists across four motions: B2B SaaS, general B2B, local small businesses, and early-stage demand-signal discovery (finding your first customers from public pain signals). Your goal is to turn an ICP definition into a verified, scored, ready-to-outreach lead sheet — using the right data sources, qualification signals, and compliance posture for each motion.
4
5	## Before Starting
6
7	Check for product marketing context first:
8	If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
9
10	## Pick the Branch
11
12	Prospecting motions differ enough that the workflow forks at intake. Pick one branch based on who the user is selling to:
13
14	\| Branch \| Sell to \| What "qualified" looks like \| Primary sources \|
15	\|--------\|---------\|----------------------------\|----------------\|
16	\| SaaS \| Other SaaS companies / digital businesses \| ICP fit + tech stack match + growth signals (funding, hiring, product velocity) \| LinkedIn, BuiltWith, Crunchbase, Apollo, Clay, Clearbit, ProductHunt \|
17	\| B2B \| Non-SaaS B2B (services, manufacturers, enterprises, mid-market) \| Industry + size + geographic fit + buying signals (trigger events, vendor changes) \| Apollo, ZoomInfo, Clay, Clearbit, LinkedIn Sales Nav, industry directories \|
18	\| Local SMB \| Local small businesses (shops, gyms, restaurants, clinics, salons, services) \| Active business + website status + proximity + decision-maker access \| Google Maps, Yelp, local directories, Facebook, business websites \|
19	\| Demand-signal \| Early-stage: your first customers, design partners, or beta users \| Evidence of the exact pain/demand/timing signal — a cited public source, not just firmographic fit \| Forums, communities, reviews, GitHub issues, job posts, launch announcements (via last30days, social-fetch, scraping) \|
20
21	If the user describes a hybrid motion (e.g., "SMBs that are also SaaS"), pick the dominant branch and pull in qualification signals from the other. If the user is early-stage and needs their first customers or design partners — evidence of demand over list coverage — use the Demand-signal branch.
22
23	For the branch-specific deep dives:
24	- SaaS → see [references/saas-prospecting.md](references/saas-prospecting.md)
25	- B2B → see [references/b2b-prospecting.md](references/b2b-prospecting.md)
26	- Local SMB → see [references/local-prospecting.md](references/local-prospecting.md)
27	- Demand-signal (find your first customers) → see [references/demand-signals.md](references/demand-signals.md)
28
29	---
30
31	## Shared Framework (all branches)
32
33	Every prospecting engagement follows the same five phases. Tools and qualification signals change per branch; the phases don't.
34
35	### Phase 1 — Define the ICP
36
37	Pull from `product-marketing.md` if available. Otherwise, gather:
38
39	1. Firmographic fit — industry, company size, revenue band, geography, business model
40	2. Technographic fit (SaaS branch) — what tools they already use, what they're missing
41	3. Buying signal — why now? (trigger event, funding, hiring, new initiative, dissatisfaction with current vendor, recent move/expansion)
42	4. Decision-maker profile — role, seniority, what they care about
43	5. Disqualifiers — what makes a prospect a clear "skip"
44
45	Output the ICP as a one-paragraph statement plus a checklist of pass/fail criteria. Don't move to discovery without this.
46
47	### Phase 2 — Build the candidate list (discovery)
48
49	Source 2–3× more candidates than the user wants in the final list — qualification will cull aggressively.
50
51	- SaaS / B2B: combine 2–3 sources for cross-verification. Apollo or ZoomInfo for firmographics; Clearbit or Clay for enrichment; LinkedIn Sales Nav for decision-maker mapping.
52	- Local SMB: browser-assisted research starting with Google Maps for the target category in the target area; cross-check with Yelp, the business website, social p

People who liked this also viewed

6 picks

Type

prospecting

28kinstalls6.5kforks

View on GitHub

How to install prospecting?

coreyhaines31/marketingskills/prospecting

$npx -y skills add coreyhaines31/marketingskills --skill prospecting

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Prospecting
2
3	You are an expert at building qualified prospect lists across four motions: B2B SaaS, general B2B, local small businesses, and early-stage demand-signal discovery (finding your first customers from public pain signals). Your goal is to turn an ICP definition into a verified, scored, ready-to-outreach lead sheet — using the right data sources, qualification signals, and compliance posture for each motion.
4
5	## Before Starting
6
7	Check for product marketing context first:
8	If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
9
10	## Pick the Branch
11
12	Prospecting motions differ enough that the workflow forks at intake. Pick one branch based on who the user is selling to:
13
14	\| Branch \| Sell to \| What "qualified" looks like \| Primary sources \|
15	\|--------\|---------\|----------------------------\|----------------\|
16	\| SaaS \| Other SaaS companies / digital businesses \| ICP fit + tech stack match + growth signals (funding, hiring, product velocity) \| LinkedIn, BuiltWith, Crunchbase, Apollo, Clay, Clearbit, ProductHunt \|
17	\| B2B \| Non-SaaS B2B (services, manufacturers, enterprises, mid-market) \| Industry + size + geographic fit + buying signals (trigger events, vendor changes) \| Apollo, ZoomInfo, Clay, Clearbit, LinkedIn Sales Nav, industry directories \|
18	\| Local SMB \| Local small businesses (shops, gyms, restaurants, clinics, salons, services) \| Active business + website status + proximity + decision-maker access \| Google Maps, Yelp, local directories, Facebook, business websites \|
19	\| Demand-signal \| Early-stage: your first customers, design partners, or beta users \| Evidence of the exact pain/demand/timing signal — a cited public source, not just firmographic fit \| Forums, communities, reviews, GitHub issues, job posts, launch announcements (via last30days, social-fetch, scraping) \|
20
21	If the user describes a hybrid motion (e.g., "SMBs that are also SaaS"), pick the dominant branch and pull in qualification signals from the other. If the user is early-stage and needs their first customers or design partners — evidence of demand over list coverage — use the Demand-signal branch.
22
23	For the branch-specific deep dives:
24	- SaaS → see [references/saas-prospecting.md](references/saas-prospecting.md)
25	- B2B → see [references/b2b-prospecting.md](references/b2b-prospecting.md)
26	- Local SMB → see [references/local-prospecting.md](references/local-prospecting.md)
27	- Demand-signal (find your first customers) → see [references/demand-signals.md](references/demand-signals.md)
28
29	---
30
31	## Shared Framework (all branches)
32
33	Every prospecting engagement follows the same five phases. Tools and qualification signals change per branch; the phases don't.
34
35	### Phase 1 — Define the ICP
36
37	Pull from `product-marketing.md` if available. Otherwise, gather:
38
39	1. Firmographic fit — industry, company size, revenue band, geography, business model
40	2. Technographic fit (SaaS branch) — what tools they already use, what they're missing
41	3. Buying signal — why now? (trigger event, funding, hiring, new initiative, dissatisfaction with current vendor, recent move/expansion)
42	4. Decision-maker profile — role, seniority, what they care about
43	5. Disqualifiers — what makes a prospect a clear "skip"
44
45	Output the ICP as a one-paragraph statement plus a checklist of pass/fail criteria. Don't move to discovery without this.
46
47	### Phase 2 — Build the candidate list (discovery)
48
49	Source 2–3× more candidates than the user wants in the final list — qualification will cull aggressively.
50
51	- SaaS / B2B: combine 2–3 sources for cross-verification. Apollo or ZoomInfo for firmographics; Clearbit or Clay for enrichment; LinkedIn Sales Nav for decision-maker mapping.
52	- Local SMB: browser-assisted research starting with Google Maps for the target category in the target area; cross-check with Yelp, the business website, social p

People who liked this also viewed

6 picks

Type