novahiz 0.2.2 → 0.2.5

package/bundled-skills/prospecting/evals/evals.json

@@ -1,122 +0,0 @@
-{
-  "skill_name": "prospecting",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "We're a B2B SaaS selling RevOps tooling at $30K ACV. Build me a list of 25 prospects.",
-      "expected_output": "Should check for product-marketing.md first. Should identify this as the SaaS branch. Should run Phase 1 ICP definition pulling from product-marketing context or asking targeted questions (target industry, headcount range, tech stack signals, funding stage). Should propose discovery sources appropriate for SaaS at $30K ACV: Apollo for breadth, Clay for waterfall enrichment, Crunchbase for funding signals, BuiltWith/Wappalyzer for tech stack, LinkedIn Sales Nav for decision-mapping (manual). Should ask about user's tool access before assuming. Should source 50-75 candidates (2-3x target) before qualifying. Should flag that email validation via Truelist or similar is non-negotiable before final list. Should output SaaS-branch chat table columns (Score | Company | Industry | Size | Signal | Contact | Email status | Confidence) followed by top 3-5 hot leads with one-sentence rationale each. Should reference references/saas-prospecting.md.",
-      "assertions": [
-        "Checks for product-marketing.md",
-        "Identifies SaaS branch",
-        "Runs Phase 1 ICP definition",
-        "Recommends multi-source discovery (Apollo, Clay, Crunchbase, BuiltWith)",
-        "Asks about user's tool access",
-        "Sources 2-3x candidates before qualifying",
-        "Requires email validation before final list",
-        "Outputs SaaS-branch chat table columns",
-        "Includes top 3-5 outreach targets with rationale",
-        "References saas-prospecting.md"
-      ],
-      "files": []
-    },
-    {
-      "id": 2,
-      "prompt": "Find me 25 SaaS companies that just raised a Series B in the last 60 days and use HubSpot.",
-      "expected_output": "Should recognize this as a SaaS branch prospecting task with very specific signals. Should identify the trigger event (Series B in last 60 days) and the technographic filter (uses HubSpot). Should recommend a workflow: (1) Crunchbase or Pitchbook for funding signal filter (Series B + date), (2) BuiltWith or Clay's waterfall for tech stack verification (uses HubSpot), (3) cross-check via business websites and LinkedIn. Should note this is a tight ICP that should yield high-confidence matches if data sources are current. Should flag freshness concerns: Crunchbase data depends on self-reporting, BuiltWith refresh cycles aren't real-time. Should recommend cross-source verification for the funding date specifically. Should output a SaaS-branch chat table with the funding round + date in the Signal column. Should include verified email validation before delivering.",
-      "assertions": [
-        "Identifies as SaaS branch",
-        "Identifies funding signal + tech stack filter",
-        "Recommends Crunchbase or Pitchbook for funding",
-        "Recommends BuiltWith or Clay for HubSpot verification",
-        "Notes data freshness concerns",
-        "Recommends cross-source verification",
-        "Outputs signal column showing round + date",
-        "Requires email validation"
-      ],
-      "files": []
-    },
-    {
-      "id": 3,
-      "prompt": "I run a marketing agency. Find me 25 mid-market manufacturers in the Midwest US who recently hired a new CMO.",
-      "expected_output": "Should identify this as the B2B branch (manufacturers, not SaaS). Should run Phase 1 ICP definition: industry (manufacturing, with NAICS code if precision matters), size (mid-market = typically 200-2000 employees), geography (Midwest US states), trigger event (CMO hire in last 90-180 days). Should propose discovery: Apollo or ZoomInfo for firmographic filter, LinkedIn Sales Nav for CMO hire detection (job changes), Google Alerts on press releases for trigger events. Should warn that CMO hires aren't always in public databases — LinkedIn Sales Nav alerts on job changes is the most reliable source. Should output B2B-branch chat table with the CMO trigger as the signal. Should reference references/b2b-prospecting.md. Should mention compliance: GDPR less likely (US-only), CAN-SPAM applies, capture source URL + date for every contact.",
-      "assertions": [
-        "Identifies B2B branch (not SaaS)",
-        "Runs Phase 1 ICP definition with NAICS or industry classification",
-        "Specifies mid-market size band",
-        "Specifies Midwest US geography",
-        "Identifies trigger event (CMO hire)",
-        "Recommends Apollo/ZoomInfo + LinkedIn Sales Nav",
-        "Notes CMO hires often only on LinkedIn",
-        "Outputs B2B-branch chat table",
-        "Mentions CAN-SPAM and source URL capture",
-        "References b2b-prospecting.md"
-      ],
-      "files": []
-    },
-    {
-      "id": 4,
-      "prompt": "We sell to industrial distributors. Build a list of 25 prospects.",
-      "expected_output": "Should identify this as the B2B branch. Should run Phase 1 ICP definition asking targeted questions: distributor size, geography, vertical specialty, buying patterns. Should propose discovery: Apollo or ZoomInfo for firmographic depth, industry-specific directories (e.g., NAW for wholesale distributors, ISA for industrial sales agencies), trade show exhibitor lists. Should note state business registries and Chamber of Commerce as verification sources. Should propose trigger events: new location, recent acquisition, leadership change, posting RFPs. Should warn that industrial distributor data is often spotty in major databases — cross-check with company website + LinkedIn for size and ownership signals. Should output B2B-branch chat table. Should note ICP fit precision matters more than initial volume for this kind of niche prospecting.",
-      "assertions": [
-        "Identifies B2B branch",
-        "Runs Phase 1 ICP definition asking targeted questions",
-        "Recommends industry-specific directories beyond Apollo/ZoomInfo",
-        "Mentions trade show exhibitor lists",
-        "Identifies relevant trigger events",
-        "Warns about data spottiness for industrial",
-        "Recommends cross-verification with business websites + LinkedIn",
-        "Notes ICP fit precision over volume"
-      ],
-      "files": []
-    },
-    {
-      "id": 5,
-      "prompt": "I build websites for local businesses. Find me 15 prospects near Austin, TX who don't have a website.",
-      "expected_output": "Should identify as Local SMB branch. Should run Phase 1 ICP definition: business category (ask user — gyms, restaurants, salons, etc. matter), radius (default 20 km from Austin), target count (15). Should run the browser research workflow: search Google Maps for category + Austin, build candidate list from visible results, cross-check via business name + city web search to verify website status. Should apply the 4-tier website status classification (No site found / Social only / Weak site / Has site) — prioritize No site + Social only as Hot. Should score: Hot (no site + active + phone + within radius), Warm (weak site), Cold (has site), Skip (closed/duplicate/out of scope). Should output Local SMB chat table (Score | Business | Category | Area | Distance | Website status | Website/Social | Phone | Why prospect | Confidence). Should add 'Best first outreach targets' top 3 with reasoning. Should reference references/local-prospecting.md. Should warn against bulk-scraping Google Maps (ToS violation) — browser-assisted research only.",
-      "assertions": [
-        "Identifies Local SMB branch",
-        "Asks about business category if not specified",
-        "Defaults radius to 20km",
-        "Runs browser research workflow",
-        "Applies 4-tier website status classification",
-        "Uses Hot/Warm/Cold/Skip scoring",
-        "Outputs Local SMB chat table columns",
-        "Adds top 3 outreach targets",
-        "References local-prospecting.md",
-        "Warns against bulk-scraping Google Maps"
-      ],
-      "files": []
-    },
-    {
-      "id": 6,
-      "prompt": "I have a list of 200 prospect emails from Apollo. How do I know which ones are deliverable before I start outreach?",
-      "expected_output": "Should explain the deliverability validation step in Phase 3. Should recommend Truelist (the integration in this pack) for bulk validation. Should explain the email_state classification output: ok (deliverable), email_invalid (bounces, exclude), risky (deliverable with risk like role or disposable, include cautiously), unknown (couldn't determine, skip or re-verify), accept_all (catch-all domain, include cautiously). Should warn that Apollo data accuracy is typically 60-80% — sending without validation will tank sender reputation (bounce rate >2% triggers ISP throttling and reputation damage). Should recommend the workflow: bulk POST to /api/v1/verify or CSV upload → keep ok, include risky/accept_all cautiously, exclude email_invalid, re-verify unknown → hand off to outreach. Should note Truelist also has an official MCP server for agent-driven validation. Should note cold email reputation is hard to recover once damaged — validation is non-negotiable, not optional. Should mention Hunter and Snov as alternatives with built-in verification. Should reference truelist.md integration guide.",
-      "assertions": [
-        "Recommends Truelist for bulk validation",
-        "Explains email_state values (ok, email_invalid, risky, unknown, accept_all)",
-        "Warns Apollo accuracy is 60-80%",
-        "Cites 2% bounce rate threshold for reputation damage",
-        "Recommends workflow: validate, keep ok, exclude email_invalid",
-        "Mentions Truelist MCP server for agent workflows",
-        "Mentions cold email reputation is hard to recover",
-        "References truelist.md or data-sources.md"
-      ],
-      "files": []
-    },
-    {
-      "id": 7,
-      "prompt": "I just built a tool that automates failed-payment follow-up for gym owners. I have no customers yet. Help me find my first ten — the people who are actually dealing with this problem right now.",
-      "expected_output": "Should select the Demand-signal branch (early-stage, first customers, evidence-of-demand) and load references/demand-signals.md — NOT the SMB/B2B list-building branches. Should start with a product brief, then mine the five signal buckets (explicit demand / pain / workaround / switching / timing) across public discourse (forums, communities, reviews, GitHub issues, job posts) — using last30days for recency, social-fetch/scraping to read original pages, not qualifying from snippets. Should score prospects on demand-fit (pain 25 / product fit 25 / timing 20 / reachability 15 / evidence quality 15, 0-100 with bands) rather than ICP-fit Hot/Warm/Cold, and require a cited public signal for every primary-shortlist prospect. Should draft source-based openers but never auto-send. Should produce an evidence report (verdict → ICP → top prospect → shortlist with sources+scores → repeated patterns → 7-day manual outreach plan → limits) and label prospects as 'potential customers based on public signals,' not confirmed buyers. Should honor the compliance guardrails including no data brokers/leaked data and no sensitive-trait targeting.",
-      "assertions": [
-        "Selects the Demand-signal branch, not the SMB/B2B/SaaS list-building branches",
-        "Mines the five signal buckets from public discourse rather than contact databases",
-        "Uses recency/original-source tooling (last30days, social-fetch, scraping) and does not qualify from snippets",
-        "Scores on the demand-fit rubric (0-100 weighted), not ICP-fit Hot/Warm/Cold",
-        "Requires a cited public signal for every primary-shortlist prospect",
-        "Drafts openers but never auto-sends; labels prospects as potential-based-on-public-signals",
-        "Produces the evidence report structure with a 7-day manual outreach plan and limits"
-      ],
-      "files": []
-    }
-  ]
-}

package/bundled-skills/prospecting/references/b2b-prospecting.md

@@ -1,106 +0,0 @@
-# B2B Prospecting Reference
-
-For when the user sells to non-SaaS B2B — services, agencies, manufacturers, mid-market and enterprise companies, professional services firms.
-
----
-
-## ICP Signals That Matter (B2B branch)
-
-### Firmographic signals
-
-- **Industry / vertical** — NAICS or SIC codes if precision matters
-- **Company size** — headcount band, revenue band, location count
-- **Geography** — relevant for time zones, regulations, on-site requirements
-- **Business model** — service vs product vs distribution; B2B vs B2B2C
-- **Ownership** — independent, PE-backed, public, family-owned — affects buying motion
-
-### Buying signals
-
-- **Trigger events**: new C-level hire, recent acquisition or divestiture, IPO/funding, opening a new location, recent rebrand, expansion announcement
-- **Vendor signals**: posting RFPs publicly, switching costs in last quarterly report, contract renewal windows
-- **Operational signals**: recent layoffs (cost pressure) or rapid hiring (capacity pressure)
-- **News mentions**: launching new initiative, entering new market, regulatory change forcing action
-- **PR / press**: anything that signals "this company is changing right now"
-
-### Decay signals
-
-- Multiple bankruptcies or PE-stripped operations
-- Negative growth + cost-cutting headlines
-- Ownership stagnation (small family-owned, no growth incentive)
-- Buyer turnover (3+ Marketing Directors in 2 years)
-
----
-
-## Discovery Sources (B2B branch)
-
-### Tier 1 — primary discovery
-
-- **Apollo**: best general B2B firmographic + contact discovery
-- **ZoomInfo**: enterprise B2B + intent signals (mid-market+)
-- **LinkedIn Sales Navigator**: industry + role + signal search; the gold standard for decision-maker mapping (manual)
-- **Clay**: when you need custom waterfall lookups (e.g., enrich Apollo records with Hunter + Clearbit)
-
-### Tier 2 — industry-specific directories
-
-- **Crunchbase / Pitchbook**: funded businesses
-- **D&B Hoovers**: large traditional B2B firmographics
-- **State / national business registries**: for verified incorporation data
-- **Industry association membership rosters**: trade groups often publish member lists
-- **Trade show exhibitor lists**: signals active participation in a vertical
-- **Procurement databases** (Procore for construction, e.g.): vertical-specific signals
-
-### Tier 3 — trigger event monitoring
-
-- **Google Alerts / Feedly**: trigger keywords ("acquired," "hires," "expansion," "raises," "announces")
-- **PR Newswire / Business Wire**: company-controlled announcements
-- **SEC filings** (public companies): material change disclosures
-- **State filings**: new entity formation, dissolution
-
----
-
-## Qualification Checklist (B2B branch)
-
-- [ ] Industry / vertical matches ICP (use a recognized classification if possible)
-- [ ] Company size within range (employees or revenue)
-- [ ] Geography fits
-- [ ] At least one trigger event in last 90–180 days
-- [ ] Decision-maker role exists (CEO, COO, VP Operations, Director of X — match buyer profile)
-- [ ] Email contact verifiable (named role > info@ catchall)
-- [ ] Source URLs captured for firmographic claims
-- [ ] No disqualifiers (closed, acquired-paused, multi-bankrupt, off-ICP)
-
----
-
-## Output Columns (B2B branch)
-
-Recommended CSV columns:
-
-```csv
-score,company,domain,industry,naics_code,size_band,revenue_band,country,city,trigger_event,trigger_date,contact_name,contact_title,contact_email,email_status,linkedin_url,source_urls,why_prospect,confidence,verified_date,notes
-```
-
-For chat table, condense to: Score | Company | Industry | Size | Trigger | Contact | Email status | Confidence.
-
----
-
-## Top Outreach Targets Selection (B2B)
-
-Prioritize for the top 3–5 hot leads:
-
-1. **Trigger event recency** — 30 days beats 6 months
-2. **Trigger event specificity** — new CMO hire in your buyer's role beats "company in the news"
-3. **Decision-maker access** — named contact with verified email + LinkedIn beats role-only
-4. **Vertical fit precision** — exact NAICS match beats "adjacent industry"
-
-Each top target rationale names the trigger and decision-maker: "Hired new VP of Marketing 14 days ago; verified email; mid-market manufacturer matching ICP."
-
----
-
-## Common Mistakes (B2B)
-
-1. **Treating B2B like SaaS** — funding rounds matter less; PE ownership and acquisition activity matter more.
-2. **Trying to verify private company revenue precisely** — most public databases approximate. Use size bands, not point estimates.
-3. **Ignoring procurement complexity** at enterprise scale — your prospect contact list may not include the actual approver.
-4. **Cold-emailing executive assistants** — they're not the buyer and they will flag your outreach as spam.
-5. **Source URL hygiene** — without source lineage, you can't defend a contact under GDPR DSAR or CAN-SPAM challenge.
-6. **Stopping at one source** — Apollo can be 60% accurate on small businesses. Cross-verify with LinkedIn or the business website.

package/bundled-skills/prospecting/references/compliance.md

@@ -1,123 +0,0 @@
-# Prospecting Compliance Reference
-
-The legal and platform-ToS constraints that apply to prospect list building. Read first, every engagement.
-
-> Operational guidance, not legal advice. For high-volume programs or programs touching EU/UK residents, run your setup past a privacy attorney.
-
----
-
-## United States — CAN-SPAM (downstream)
-
-CAN-SPAM regulates the cold email **send**, not the list build. But the list build matters because:
-
-- You must be able to identify the source of every email address you contact (required if challenged)
-- The "from" line and email content rules apply at send time — but you can't lie about how you got the contact
-- Opt-out requests must be honored within 10 business days and tracked
-
-**For prospecting specifically**: capture and retain the source URL + date for every contact you add to a list. CAN-SPAM doesn't require it explicitly, but defending your sender practices does.
-
----
-
-## EU / UK — GDPR
-
-The strictest applicable framework. Triggers when:
-
-- Your prospect resides in EU/UK
-- You're processing personal data (any identifiable info, including business emails tied to a named person)
-
-### Lawful bases for cold B2B outreach
-
-You have three credible options:
-
-1. **Legitimate interest** (most common for B2B). Requires:
-   - The contact is in a business role likely to be interested in your offer
-   - The data was collected from a public, business-context source
-   - You provide a clear opt-out
-   - You can articulate the legitimate interest test in writing
-
-2. **Consent** — typically not feasible for cold outreach (you don't have consent before first contact)
-
-3. **Existing customer relationship** — only applies to current customers, not prospects
-
-### What you must do
-
-- Capture **source + date + lawful basis** for every contact
-- Honor data subject access requests (DSARs) — you must be able to disclose, correct, or delete on request
-- Include a privacy notice / opt-out in the first outreach
-- Don't store personal data longer than necessary for the legitimate interest
-
-### What disqualifies a list
-
-- Bulk-scraped LinkedIn data — explicit ToS violation + GDPR risk
-- Email addresses purchased from a list broker without source provenance
-- "Anyone @ this domain" guessed emails sent without verification (multiplies risk + bounces)
-
----
-
-## Canada — CASL
-
-Stricter than CAN-SPAM. Cold B2B outreach requires:
-
-- **Express consent** (explicit opt-in) — typically not present for cold prospecting
-- **OR implied consent** — existing business relationship within 24 months, OR business address publicly published on the company's own site for the purpose of receiving such communications
-
-**Practical implication for Canadian prospects**: relying on the publicly-published-address exception is the most defensible cold prospecting basis in Canada. You must include sender identification, mailing address, and an unsubscribe mechanism in every message.
-
----
-
-## Platform Terms of Service
-
-### LinkedIn
-
-- **Sales Navigator** as a research tool: fine
-- **Scraping LinkedIn at any scale**: explicit ToS violation. Banned accounts are permanent. Don't.
-- **Apollo, Clay, and ZoomInfo** claim LinkedIn-overlap data through various legitimate channels — verify their data sources before assuming compliance
-- **InMail and Connection Requests**: governed by LinkedIn's own messaging rules, not by CAN-SPAM/GDPR (because LinkedIn-internal)
-
-### Google Maps
-
-- ToS prohibits bulk extraction or productizing Maps data
-- Browser-assisted research as a discovery aid: acceptable
-- Storing Place IDs or large structured Maps data in your CRM: explicit ToS prohibition
-- Use Maps to **find** local businesses, then cross-source from the business's own site for the data you retain
-
-### Apollo / ZoomInfo / Clearbit
-
-- All have their own ToS limiting reselling, downstream sharing, and use cases
-- Read your contract — typically you can use the data for your own outreach but not productize it
-- Don't share extracts publicly (e.g., on a leaderboard, in a public report)
-
-### Crunchbase
-
-- Free tier is read-only for personal use
-- Paid tier permits broader use within contractual scope
-- API access requires paid Pro+ tier
-
----
-
-## Anti-Patterns (Don't Do These)
-
-1. **Bulk-scraping LinkedIn / Google Maps / Yelp**. Browser-assisted research is OK; automated scrapers pointed at these platforms are not. **Firecrawl and Browserbase are fine for an individual prospect's own website** (the URL you found through manual discovery) — not for the platforms hosting prospects.
-2. **Buying lists from random vendors** without source provenance. You inherit their legal exposure.
-3. **Guessing emails and sending unverified**. Bounce rates over 2% destroy sender reputation; legally, you can't claim a "legitimate interest" basis for an email you fabricated.
-4. **Harvesting personal email addresses** (Gmail, personal Outlook, etc.) from public profiles. Personal addresses raise GDPR risk significantly.
-5. **Storing data you don't need**. Minimize retention. Don't keep prospect lists forever — GDPR right to deletion applies.
-6. **Skipping the lawful basis documentation**. If challenged, you need to show your work. Capture source URL + collection date for every contact.
-7. **Reselling prospect lists**. You may not have the right to share them downstream. Read your data provider contracts.
-8. **CAPTCHA bypass / login wall bypass**. Even if technically possible, this signals bot behavior and violates virtually every ToS.
-
----
-
-## Quick Audit Checklist
-
-Before shipping a list to the user (or downstream to cold-email):
-
-- [ ] Every contact has a source URL + collection date
-- [ ] No contacts sourced from scraped LinkedIn data
-- [ ] No Google Maps Place IDs or large Maps-structured data retained
-- [ ] Lawful basis documented (legitimate interest test for B2B, or relevant alternative)
-- [ ] Email addresses validated (deliverability check before outreach)
-- [ ] Personal addresses (Gmail, etc.) flagged or excluded
-- [ ] Source provider contracts permit the intended use case
-- [ ] Retention plan documented (when to delete)
-- [ ] First outreach will include unsubscribe + privacy notice (downstream concern for cold-email skill, but mention it now)

package/bundled-skills/prospecting/references/data-sources.md

@@ -1,287 +0,0 @@
-# Prospecting Data Sources
-
-Tool selection guide for prospecting across all three branches.
-
----
-
-## Tool selection by goal
-
-| Goal | Primary tools | Notes |
-|------|--------------|-------|
-| **Build initial firmographic list (B2B / SaaS)** | Apollo, ZoomInfo, Clay | Apollo for breadth, ZoomInfo for enterprise + intent, Clay for custom workflows |
-| **Decision-maker mapping** | LinkedIn Sales Navigator (manual), Apollo, ZoomInfo | Sales Nav is the gold standard. Never bulk scrape it. |
-| **Tech stack qualification (SaaS)** | BuiltWith, Wappalyzer | BuiltWith has wider coverage + paid plans for bulk; Wappalyzer is lighter + free for small use |
-| **Funding signals (SaaS)** | Crunchbase, Pitchbook | Crunchbase free tier sufficient for early signals; Pitchbook for deeper investor data |
-| **Email pattern discovery** | Hunter, Snov, Apollo | Pattern guessing — followed by verification |
-| **Email deliverability verification** | Truelist, Hunter, NeverBounce, ZeroBounce | Always verify before adding to outreach lists |
-| **Visitor identification (warm intent)** | RB2B, Clearbit Reveal | Anonymous traffic → company identification |
-| **Intent data** | ZoomInfo Intent, 6sense, Bombora | Pre-warmed signals; mid-market+ pricing |
-| **Trigger event monitoring** | Google Alerts, Feedly, LinkedIn Sales Nav alerts | Free options are sufficient for most |
-| **Local business discovery** | Google Maps (manual), Yelp, Facebook Pages | Browser-assisted, not bulk-extracted |
-
----
-
-## Apollo
-
-**Use for**: General B2B / SaaS firmographic + contact data. Best starting point if you don't already have a list.
-
-**Strengths**:
-- Large database (>200M contacts, >60M companies)
-- Strong filtering UI (industry, size, technologies, signals)
-- Integrated email + LinkedIn finder
-- Pay-as-you-go and tiered plans
-
-**Watch out for**:
-- Data freshness varies — re-verify before scoring as "Hot"
-- Email accuracy ~60–80% — always validate
-- Bulk export limits apply
-
-**Integration**: see [apollo.md](../../../tools/integrations/apollo.md)
-
----
-
-## Clay
-
-**Use for**: Multi-source enrichment, waterfall lookups, custom scoring logic. When list quality matters more than list size.
-
-**Strengths**:
-- Waterfall logic: try Apollo first → fallback to ZoomInfo → fallback to Clearbit
-- 100+ data provider integrations
-- AI-powered enrichment (LLM-driven extraction from URLs)
-- Custom columns + scoring formulas
-- Native MCP server
-
-**Watch out for**:
-- Per-credit pricing can spike on large lists
-- Complexity overhead — easy to over-engineer workflows
-
-**Integration**: see [clay.md](../../../tools/integrations/clay.md)
-
----
-
-## ZoomInfo
-
-**Use for**: Enterprise B2B + intent data. Mid-market+ buyer profiles.
-
-**Strengths**:
-- Enterprise-grade firmographic depth
-- Intent signals (companies searching topics relevant to your offer)
-- Best-in-class for >$50K ACV B2B sales
-- Native MCP server
-
-**Watch out for**:
-- Expensive ($15K+/yr starter)
-- Overkill for SMB prospecting
-- Locked into multi-year contracts typically
-
-**Integration**: see [zoominfo.md](../../../tools/integrations/zoominfo.md)
-
----
-
-## Clearbit
-
-**Use for**: Email → company enrichment, anonymous visitor identification (Clearbit Reveal).
-
-**Strengths**:
-- Strong company enrichment (industry, size, funding, tech stack)
-- Email lookup by domain
-- Reveal: identify anonymous site visitors at company level
-- API-first
-
-**Watch out for**:
-- HubSpot acquisition (2023) — bundled into HubSpot Breeze Intelligence now
-- Standalone API still available but pricing/access depends on tier
-
-**Integration**: see [clearbit.md](../../../tools/integrations/clearbit.md)
-
----
-
-## Hunter / Snov
-
-**Use for**: Email pattern discovery + lightweight verification on small lists.
-
-**Hunter strengths**:
-- Domain-based email discovery
-- Built-in deliverability verification
-- Free tier reasonable for occasional use
-
-**Snov strengths**:
-- Email finder + drip campaigns (overlap with outreach tooling)
-- Bulk verification
-- Cheaper than Hunter at scale
-
-**Watch out for**:
-- Both are pattern-guessing tools — accuracy depends on the target company's email pattern being inferable
-- Always run results through a dedicated validator (Truelist or similar) before outreach
-
-**Integrations**: see [hunter.md](../../../tools/integrations/hunter.md), [snov.md](../../../tools/integrations/snov.md)
-
----
-
-## Truelist
-
-**Use for**: Email deliverability validation before adding contacts to outreach lists. Critical safety step.
-
-**Strengths**:
-- Single-email sync verification (`/api/v1/verify_inline`) + bulk async (`/api/v1/verify`)
-- Returns `email_state` (ok / email_invalid / risky / unknown / accept_all) + `email_sub_state` (email_ok / is_disposable / is_role / unknown_error / failed_smtp_check) + did-you-mean typo suggestions
-- Catches catch-all domains, role accounts, spam traps, disposable providers
-- Official MCP server for agent-driven workflows (Claude, Cursor, VS Code)
-- Official SDKs in 7 languages + framework integrations (Django, Laravel, Next.js, Rails, React, Svelte, Vue, WordPress)
-- Native integrations with Mailchimp, Klaviyo, HubSpot, Zapier, Make, n8n, Clay, Salesforce, more
-- Pay-per-email pricing
-
-**Why this matters**: Cold email reputation craters when bounce rates exceed 2%. Validating before sending is non-negotiable. Apollo/ZoomInfo/Hunter data is often 60–80% accurate — Truelist catches the rest.
-
-**Integration**: see [truelist.md](../../../tools/integrations/truelist.md)
-
----
-
-## LinkedIn Sales Navigator
-
-**Use for**: Manual decision-maker discovery. The gold standard for B2B / SaaS prospecting but only when used as a research tool.
-
-**Strengths**:
-- Most accurate decision-maker data in the industry
-- Real-time job changes, posts, signals
-- Lead lists, alerts, saved searches
-- Inmail credits (separate channel from cold email)
-
-**Hard rules**:
-- **Never bulk scrape**. LinkedIn aggressively bans scrapers. Account ban risk is real and permanent.
-- Use Sales Nav as a research interface — open profiles, read, take notes, capture key data manually.
-- Apollo and other tools claim LinkedIn data via partnerships / public mirroring — verify the source legitimacy before assuming compliance.
-
-**Integration**: no MCP or API access at consumer level. Manual research only.
-
----
-
-## BuiltWith / Wappalyzer
-
-**Use for**: Tech stack qualification (SaaS branch).
-
-**BuiltWith**:
-- ~50K+ technologies tracked
-- API + bulk lookups (paid)
-- Historical data (when stack changed)
-
-**Wappalyzer**:
-- Free browser extension; paid API
-- Lighter coverage than BuiltWith
-- Faster for one-off lookups
-
-Cross-reference both for high-confidence tech stack signals.
-
----
-
-## Crunchbase
-
-**Use for**: Funding signals (SaaS branch).
-
-**Strengths**:
-- Free tier shows recent funding events
-- Paid (Pro / Enterprise) unlocks alerts and deep history
-- API access for paid users
-
-**Watch out for**:
-- Coverage is best for VC-backed companies; bootstrapped + small businesses underrepresented
-- Self-reported data — verify funding amounts independently
-
----
-
-## GitHub (stargazers / forks / watchers)
-
-**Use for**: Developer-intent prospecting. Especially powerful for dev-tool SaaS — stargazers of competitor or category-defining repos are in-market signal.
-
-**Strengths**:
-- Public API, no scraping concerns
-- High signal quality (a starred repo = explicit interest)
-- Forks are an even stronger signal (intent to modify, not just bookmark)
-- Bundled `github-prospects.js` CLI handles pagination + enrichment + CSV output
-- Free with 5,000 req/hr authenticated rate limit
-
-**Watch out for**:
-- Only ~5–20% of users publish email — pair with Apollo/Clay/Hunter for enrichment
-- Very-popular repos (100K+ stars) are mostly noise; smaller targeted repos (5K–25K) give better signal density
-- Most prospects are individuals, not company contacts directly — need to figure out their company from `company` field or LinkedIn
-
-**Integration**: see [github.md](../../../tools/integrations/github.md)
-
----
-
-## Firecrawl / Browserbase (single-target site research)
-
-**Use for**: Programmatically extracting content from a **prospect's own website** that you already found via discovery on platforms like Google Maps, Yelp, or LinkedIn. Not for scraping those platforms themselves.
-
-### Firecrawl
-
-- **Best for**: "Just give me the page as markdown" — Local SMB website status checks, B2B company about/team page extraction, structured field extraction
-- **Strengths**: Low overhead, returns clean LLM-ready markdown, handles most JS-rendered sites, has an MCP server
-- **API + MCP + SDKs**: Node, Python, Go, Rust
-
-### Browserbase
-
-- **Best for**: When you need real Chromium — JS-heavy pages, cookie consent dialogs, form submission to reach a contact page, session state
-- **Strengths**: Full browser control via Playwright/Puppeteer; Stagehand provides AI-friendly natural-language extraction; session recordings for debugging
-- **API + MCP (Stagehand) + SDKs**: Node, Python
-
-### Critical compliance line
-
-Both tools can technically point at any URL. The hard rule:
-
-- ✓ **OK**: extracting content from a single business's own website (`joescoffeeshop.com`) that you found through manual discovery
-- ✗ **NOT OK**: pointing them at `google.com/maps`, LinkedIn search results, Yelp listings, or any platform whose ToS prohibits bulk extraction
-
-Discovery happens on platforms (manual browser-assisted research). Extraction happens on individual public business sites.
-
-**Integrations**: see [firecrawl.md](../../../tools/integrations/firecrawl.md), [browserbase.md](../../../tools/integrations/browserbase.md)
-
----
-
-## RB2B / Clearbit Reveal
-
-**Use for**: Identifying anonymous site visitors as warm intent signals.
-
-**Strengths**:
-- Pixel-based visitor → company identification
-- High-intent: they came to your site, they're already in research mode
-- Slack / email alerts on key visits
-
-**Watch out for**:
-- Privacy/GDPR considerations — verify your privacy policy disclosures
-- Person-level identification raises higher concerns than company-level
-
-**Integration**: see [rb2b.md](../../../tools/integrations/rb2b.md)
-
----
-
-## Free / browser-only fallbacks
-
-When the user has no paid tools, lean on:
-
-- **Google Search** — exact business name + city + role searches
-- **LinkedIn** (manual, no scraping) — company pages, employee lookups
-- **Crunchbase free tier** — funding events
-- **Wappalyzer browser extension** — tech stack at a glance
-- **Hunter.io free tier** — 25 lookups/month
-- **Google Maps** — for Local SMB discovery
-- **Business websites + About pages** — primary source for any claim
-- **News sites + press releases** — trigger event monitoring via Google Alerts
-
-Slower than tooled-up workflows, but produces high-quality smaller lists if the user is willing to do the work.
-
----
-
-## Sequencing recommendations
-
-A typical full-stack prospecting workflow:
-
-1. **Define ICP** from product-marketing context (no tools needed)
-2. **Initial list** from Apollo or ZoomInfo (firmographic filter)
-3. **Enrich** with Clay (waterfall: tech stack, funding, trigger events)
-4. **Decision-maker mapping** in LinkedIn Sales Nav (manual)
-5. **Email pattern discovery** with Hunter or Apollo's built-in
-6. **Email validation** with Truelist before final list
-7. **Hand off** to cold-email skill for outreach copy
-
-Adapt this sequence based on which tools the user actually has.