prospecting

Builds qualified, scored prospect lists for B2B SaaS, B2B, and local SMB outreach.

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill prospecting-ferrarifankid04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prospecting
Source: https://github.com/ferrarifankid04/ai-skills-public/tree/main/claude-code/skills/prospecting
Command: npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill prospecting-ferrarifankid04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning an ideal customer profile into a verified, ready-to-contact lead list is slow and error-prone: data sources disagree, emails bounce, and scraping platforms like LinkedIn or Google Maps risks account bans and legal exposure. This Skill structures the entire list-building and qualification workflow so every lead is scored, sourced, and compliant. ## Core Features & Use Cases - Three prospecting branches: Separate workflows for B2B SaaS (tech stack and funding signals), general B2B (trigger events and firmographics), and local SMBs (website status and proximity), each with its own qualification checklist and output columns. - Five-phase framework: ICP definition, candidate discovery at 2-3x target volume, evidence-backed qualification with confidence levels, Hot/Warm/Cold/Skip scoring, and lead sheet output as a chat table or CSV. - Compliance guardrails: Built-in GDPR, CAN-SPAM, and CASL guidance requiring source URL and date capture for every contact, plus hard rules against bulk scraping LinkedIn or Google Maps. - Use Case: A marketing agency asks for 25 mid-market manufacturers in the Midwest that recently hired a new CMO; the Skill selects the B2B branch, defines the ICP, recommends Apollo plus LinkedIn Sales Navigator for discovery, verifies emails with Truelist, and delivers a scored table with top outreach targets. ## Quick Start Ask the assistant to build a list of 25 qualified prospects for your product, describing your ideal customer, target geography, and which data tools you have access to.

Frequently Asked Questions about prospecting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a qualified B2B prospect list?

Define your ICP first with firmographic fit, buying signals, and disqualifiers, then source 2-3x more candidates than needed from tools like Apollo or ZoomInfo. Score each candidate against the ICP checklist with evidence URLs, verify emails before finalizing, and output a Hot/Warm/Cold/Skip scored table.

What tools work best for SaaS prospecting?

Apollo handles firmographic and contact discovery, Clay runs multi-source waterfall enrichment, Crunchbase tracks funding signals, and BuiltWith or Wappalyzer verify tech stacks. LinkedIn Sales Navigator is the standard for decision-maker mapping but must be used manually, never scraped.

How do I find local businesses without websites?

Search Google Maps manually for a category near your target location, then run an exact business-name web search to confirm no standalone site exists. Classify each business as no site, social only, weak site, or has site, and prioritize no-site and social-only businesses as hot prospects.

Can I scrape LinkedIn or Google Maps for prospect data?

No. Bulk scraping LinkedIn or Google Maps violates their terms of service and risks permanent account bans plus GDPR exposure. Use browser-assisted manual research for discovery, and tools like Firecrawl only on individual prospect websites you already found.

Why validate prospect emails before cold outreach?

Data from Apollo or ZoomInfo is typically only 60-80% accurate, and bounce rates above 2% damage sender reputation that is hard to recover. Run every email through a validator like Truelist and exclude addresses flagged as invalid before adding contacts to an outreach list.

What compliance records should a prospect list include?

Capture the source URL and collection date for every contact, document your lawful basis such as legitimate interest for B2B, and avoid personal email addresses. This lineage is required to defend against GDPR data subject requests and CAN-SPAM challenges.