@monoes/monomindcli 2.15.2 → 2.15.4

package/org-skills/sales-enablement/references/one-pager-templates.md

@@ -0,0 +1,208 @@
+# One-Pager Templates
+
+Templates for different one-pager use cases, with layout guidance and copy prompts.
+
+## Product Overview One-Pager
+
+The default one-pager. Introduces your product to someone who knows nothing about you.
+
+### Structure
+
+```
+[Logo]                                              [Tagline]
+
+HEADLINE: One sentence describing what you do and who it's for.
+
+THE PROBLEM
+2-3 sentences describing the pain your buyer faces.
+
+THE SOLUTION
+2-3 sentences describing how your product solves it.
+
+WHY [YOUR PRODUCT]
+• Differentiator 1 — One sentence explaining the benefit
+• Differentiator 2 — One sentence explaining the benefit
+• Differentiator 3 — One sentence explaining the benefit
+
+PROOF
+"Customer quote with specific result." — Name, Title, Company
+[Optional: 2-3 metric callouts: "X% improvement", "Y hours saved"]
+
+[CTA Button/Link]                    [Contact: name@company.com]
+```
+
+### Copy Prompts
+
+- Headline: "What do you do, in one sentence, that makes someone say 'tell me more'?"
+- Problem: "What is your buyer struggling with before they find you?"
+- Differentiators: "If you could only tell them 3 things, what would make them choose you?"
+
+---
+
+## Use-Case Specific One-Pager
+
+Tailored to a specific workflow, vertical, or problem. More targeted than the product overview.
+
+### Structure
+
+```
+[Logo]                                    [Use Case: e.g., "For Sales Teams"]
+
+HEADLINE: How [your product] helps [persona] [achieve outcome].
+
+THE CHALLENGE
+When [persona] needs to [task], they face [specific pain].
+This leads to [consequence]: [time wasted / money lost / risk].
+
+HOW IT WORKS
+1. [Step 1] — What happens and why it matters
+2. [Step 2] — What happens and why it matters
+3. [Step 3] — What happens and why it matters
+
+RESULTS
+• [Metric 1]: Before → After
+• [Metric 2]: Before → After
+• [Metric 3]: Before → After
+
+CUSTOMER SPOTLIGHT
+"Quote about this specific use case." — Name, Title, Company
+
+[CTA: "See it in action" or "Start a pilot"]       [Contact info]
+```
+
+### When to Use
+
+- Different buyer personas need different one-pagers
+- Industry-specific versions (healthcare, fintech, e-commerce)
+- Use-case versions (reporting, onboarding, security)
+
+---
+
+## Post-Meeting Leave-Behind
+
+Designed to reinforce a conversation that already happened. Summarizes what you discussed and proposes next steps.
+
+### Structure
+
+```
+[Logo]                                            [Date of Meeting]
+
+MEETING RECAP: [Company Name]
+
+WHAT WE DISCUSSED
+• [Pain point 1 they mentioned]
+• [Pain point 2 they mentioned]
+• [Goal they're trying to achieve]
+
+HOW [YOUR PRODUCT] HELPS
+• [Solution to pain 1] — [Specific capability or workflow]
+• [Solution to pain 2] — [Specific capability or workflow]
+• [How you help them reach their goal]
+
+RELEVANT PROOF
+"Quote from a similar customer." — Name, Title, Company
+[1-2 metrics from a similar customer]
+
+PROPOSED NEXT STEPS
+1. [Next step with date]
+2. [Follow-up action]
+3. [Decision timeline]
+
+[Your name]  |  [Your title]  |  [Email]  |  [Phone]
+```
+
+### Tips
+
+- Send within 24 hours of the meeting
+- Reference specific things they said (shows you listened)
+- Keep proposed next steps concrete and time-bound
+- This is the asset your champion forwards to their boss
+
+---
+
+## Champion Enablement One-Pager
+
+Designed specifically for your internal champion to share with their team and leadership. Written to make them look smart.
+
+### Structure
+
+```
+[Logo]
+
+WHY WE'RE EVALUATING [YOUR PRODUCT]
+
+THE SITUATION
+[2-3 sentences about the internal challenge, written as if the champion
+is explaining it to their team. Use "we" and "our" language.]
+
+WHAT [YOUR PRODUCT] DOES
+[1-2 sentences. Plain language, no jargon.]
+
+WHY THIS SOLUTION
+• [Reason 1] — How it solves our specific problem
+• [Reason 2] — How it compares to what we do today
+• [Reason 3] — How it compares to alternatives we evaluated
+
+EXPECTED IMPACT
+• [Metric]: Current state → Expected state
+• [Metric]: Current state → Expected state
+• [Time to value]: Live within [X weeks]
+
+WHO ELSE USES IT
+[2-3 recognizable company names in their industry]
+"Relevant customer quote." — Name, Title, Company
+
+NEXT STEPS
+• [What we're doing next]
+• [What we need from the team]
+• [Decision timeline]
+
+Questions? Talk to [Champion name] or [Your name at email].
+```
+
+### Why This Works
+
+- Written in the champion's voice, not yours
+- Answers the questions their boss will ask
+- Includes peer proof from companies they respect
+- Clear ask and timeline to drive internal momentum
+
+---
+
+## Layout Guidance
+
+### Visual Hierarchy
+
+1. **Headline** — Largest text, top of page, immediately communicates value
+2. **Section headers** — Bold, clear, act as scannable anchors
+3. **Body text** — Short sentences, bullet points preferred over paragraphs
+4. **Proof elements** — Metrics and quotes should visually stand out (larger font, color, or callout box)
+5. **CTA** — Prominent placement, bottom of page or bottom-right
+
+### Whitespace
+
+- Margins: at least 0.75" on all sides
+- Space between sections: enough to visually separate (don't cram)
+- If it feels crowded, cut content. Never shrink font below 9pt.
+
+### Font Sizing
+
+| Element | Suggested Size |
+|---------|---------------|
+| Headline | 18-24pt |
+| Section headers | 12-14pt bold |
+| Body text | 10-11pt |
+| Fine print / footer | 8-9pt |
+
+### Color
+
+- Use brand colors for headers and accents
+- Keep body text dark (black or near-black) on white
+- Limit accent colors to 1-2 for visual consistency
+- Use color to draw attention to metrics and CTAs
+
+### File Format
+
+- **PDF** for email attachments and leave-behinds
+- **Google Slides / PowerPoint** for editable versions reps can customize
+- Always include both — reps will customize, prospects want clean PDFs

package/{dist/src/orgrt/role-skills/sales-engineer.md → org-skills/sales-engineer/SKILL.md}

@@ -1,3 +1,11 @@
+---
+name: sales-engineer
+description: "Sales Engineer role best practices. Bridges product capability and customer need during the technical sales cycle — running discovery, demos, and POCs that prove a solution actually solves the buyer's problem, not just that it has features."
+tags: ["sales"]
+tools: []
+license: Apache-2.0
+source: https://github.com/monoes/monomind
+---
 # Sales Engineer — Best Practices
 
 ## Focus

package/org-skills/sales-prospecting/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Corey Haines
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/org-skills/sales-prospecting/SKILL.md

@@ -0,0 +1,265 @@
+---
+name: sales-prospecting
+description: "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."
+tags: ["sales"]
+tools: []
+license: MIT
+source: https://github.com/coreyhaines31/marketingskills
+source_path: "skills/prospecting"
+source_commit: 5b2c0007766c6a1cf1d53fd8fc73e979e0821022
+---
+# Prospecting
+
+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.
+
+## Before Starting
+
+**Check for product marketing context first:**
+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.
+
+## Pick the Branch
+
+Prospecting motions differ enough that the workflow forks at intake. Pick **one** branch based on who the user is selling to:
+
+| Branch | Sell to | What "qualified" looks like | Primary sources |
+|--------|---------|----------------------------|----------------|
+| **SaaS** | Other SaaS companies / digital businesses | ICP fit + tech stack match + growth signals (funding, hiring, product velocity) | LinkedIn, BuiltWith, Crunchbase, Apollo, Clay, Clearbit, ProductHunt |
+| **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 |
+| **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 |
+| **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) |
+
+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.
+
+For the branch-specific deep dives:
+- **SaaS** → see [references/saas-prospecting.md](references/saas-prospecting.md)
+- **B2B** → see [references/b2b-prospecting.md](references/b2b-prospecting.md)
+- **Local SMB** → see [references/local-prospecting.md](references/local-prospecting.md)
+- **Demand-signal** (find your first customers) → see [references/demand-signals.md](references/demand-signals.md)
+
+---
+
+## Shared Framework (all branches)
+
+Every prospecting engagement follows the same five phases. Tools and qualification signals change per branch; the phases don't.
+
+### Phase 1 — Define the ICP
+
+Pull from `product-marketing.md` if available. Otherwise, gather:
+
+1. **Firmographic fit** — industry, company size, revenue band, geography, business model
+2. **Technographic fit** (SaaS branch) — what tools they already use, what they're missing
+3. **Buying signal** — why now? (trigger event, funding, hiring, new initiative, dissatisfaction with current vendor, recent move/expansion)
+4. **Decision-maker profile** — role, seniority, what they care about
+5. **Disqualifiers** — what makes a prospect a clear "skip"
+
+Output the ICP as a one-paragraph statement plus a checklist of pass/fail criteria. Don't move to discovery without this.
+
+### Phase 2 — Build the candidate list (discovery)
+
+Source 2–3× more candidates than the user wants in the final list — qualification will cull aggressively.
+
+- **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.
+- **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 pages, and public directories.
+
+If the user's list quality bar is high, smaller is better. 25 verified leads beats 250 mostly-junk ones.
+
+### Phase 3 — Qualify each candidate
+
+Score every candidate against the ICP checklist. Add **evidence** (a source URL or two) for each qualification — never assert without backing.
+
+**Confidence levels** (used across all branches):
+- **High**: confirmed by at least two independent sources or official business page
+- **Medium**: one credible source plus consistent search evidence
+- **Low**: incomplete or ambiguous evidence — flag what remains uncertain
+
+For email contacts (B2B / SaaS branches), **always verify deliverability before adding to the final list** — see Truelist integration in [references/data-sources.md](references/data-sources.md). Don't ship leads with invalid or risky emails.
+
+### Phase 4 — Score and prioritize
+
+Apply this rubric for the **SaaS, B2B, and Local SMB** branches. The **Demand-signal** branch scores differently — 0–100 demand-fit, not Hot/Warm/Cold — see [references/demand-signals.md](references/demand-signals.md).
+
+| Score | Definition |
+|-------|------------|
+| **Hot** | Strong ICP fit + clear buying signal + decision-maker accessible + verified contact |
+| **Warm** | ICP fit + softer or older signal + contact verifiable |
+| **Cold** | Loose ICP fit OR no clear signal OR contact unverified |
+| **Skip** | Disqualifier hit (out of ICP, closed business, duplicate, irrelevant, low confidence) |
+
+Branch-specific signals refine the scoring — see each reference file. Default ratio target: ~20% Hot, ~30% Warm, rest Cold/Skip.
+
+### Phase 5 — Output the lead sheet
+
+(SaaS / B2B / Local SMB. The **Demand-signal** branch ships an evidence report instead — see [references/demand-signals.md](references/demand-signals.md).)
+
+Default to a markdown table in chat. Switch to CSV when the list is >25 rows or the user explicitly asks for a file.
+
+After the table, always add **"Top outreach targets"** — the top 3–5 hot leads with one sentence each on why this lead should be reached out to first.
+
+Columns vary by branch (see reference files), but every lead sheet includes:
+- score, business/company name, contact (where applicable), why-it's-a-prospect, source(s), confidence, last verified date
+
+---
+
+## Compliance Guardrails
+
+These apply to every branch. **Read first, every engagement.**
+
+1. **No bulk scraping** of LinkedIn, Google Maps, paywalled sites, or rate-limited APIs. Browser is an assisted research tool, not a scraper.
+2. **No CAPTCHA, login wall, or bot protection bypass.** If a site requires it, work with what's publicly visible.
+3. **Public business contact channels only.** Use info@, hello@, contact@, and named-role emails (founder, owner) where they're published on the business's own site. Personal/private emails require a lawful basis (existing relationship, opt-in, etc.).
+4. **GDPR / CAN-SPAM / CASL aware.** Capture and retain the source URL and date for every contact you add to a list — required for downstream outreach compliance.
+5. **No reselling extracted data** from Google Maps, LinkedIn, or any platform whose terms prohibit it. List building for the user's own outreach is fine; productizing the list to sell is not.
+6. **Rate limit yourself.** Even on public sources, space requests. Don't fingerprint as a bot.
+7. **No breached, leaked, or unprovenanced data.** Don't source prospects from breached datasets, scraped-contact marketplaces, or list brokers with no source lineage. Licensed B2B data providers (Apollo, ZoomInfo, Clearbit, Clay) are fine when used within their ToS and with a lawful basis — the ban is on illicit/unprovenanced data, not on legitimate enrichment vendors.
+8. **Never target or infer sensitive traits.** Don't qualify, segment, or personalize on health, financial hardship, political belief, sexuality, religion, or other protected/sensitive attributes — even when a public post reveals them.
+
+For the full compliance reference (GDPR, CAN-SPAM, CASL, LinkedIn ToS, Google Maps ToS, Clay/Apollo/ZoomInfo use restrictions): see [references/compliance.md](references/compliance.md).
+
+---
+
+## Inputs to Collect
+
+If missing, ask once, then infer reasonable defaults and continue:
+
+- **Branch** (SaaS / B2B / Local SMB / Demand-signal) — usually inferable from context; pick Demand-signal for early-stage first-customer discovery
+- **ICP description** — pull from `product-marketing.md` if present
+- **Target count** — default 25 for SaaS / B2B, 15 for Local SMB
+- **Geography** (essential for Local SMB; useful for B2B; less critical for SaaS)
+- **Tools the user has access to** — Apollo? Clay? ZoomInfo? Hunter? Truelist? Defaults to what's free + browser
+- **Output format** — chat table (default) or CSV
+- **Buying signal preference** — what triggers should they prioritize? (funding rounds, hiring, recent move, etc.)
+
+---
+
+## Tool Selection Quick Picks
+
+Full breakdown in [references/data-sources.md](references/data-sources.md). Quick picks:
+
+| If the user has access to... | Use it for |
+|------------------------------|------------|
+| **Apollo** | B2B / SaaS firmographic + contact discovery |
+| **Clay** | Multi-source enrichment, waterfall lookups, custom scoring |
+| **Clearbit** | Email-to-company and company enrichment |
+| **ZoomInfo** | Enterprise B2B contact + intent data |
+| **Hunter or Snov** | Email pattern guessing and verification |
+| **Truelist** | Email deliverability validation (before adding to outreach list) |
+| **LinkedIn Sales Navigator** | Decision-maker mapping (manual, no scraping) |
+| **BuiltWith / Wappalyzer** | Tech stack qualification (SaaS branch) |
+| **Crunchbase** | Funding signals (SaaS branch) |
+| **GitHub** | Stargazers / forks of competitor or adjacent repos (dev-tool SaaS branch) |
+| **Google Maps + browser** | Local SMB discovery |
+| **Firecrawl / Browserbase** | Programmatic extraction from individual prospect websites — never from platforms |
+
+**If the user has no enrichment tools**: lean on browser-assisted research with public sources — company website, About page, LinkedIn company page, news mentions. Slower but works.
+
+---
+
+## Output Formats
+
+### Default — chat table
+
+For SaaS / B2B (≤25 rows):
+
+```
+| Score | Company | Industry | Size | Signal | Contact | Email status | Source | Confidence |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |
+```
+
+For Local SMB (≤15 rows) — port from the local-prospector reference:
+
+```
+| Score | Business | Category | Area | Website status | Website/Social | Phone | Why it's a prospect | Confidence |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |
+```
+
+### CSV — when >25 rows or user requests a file
+
+SaaS / B2B columns:
+
+```csv
+score,company,domain,industry,size_band,country,signal,contact_name,contact_title,contact_email,email_status,linkedin,source_urls,why_prospect,confidence,verified_date,notes
+```
+
+Local SMB columns:
+
+```csv
+score,business,category,area,distance_km,website_status,website_url,social_urls,phone,email,source_urls,why_prospect,confidence,verified_date,notes
+```
+
+### Always include after the table
+
+- **Top outreach targets**: top 3–5 hot leads with one-sentence outreach rationale each
+- **Search parameters**: branch, ICP, location/radius, target count, date generated
+- **Open questions**: anything you couldn't verify and the user should look at
+
+---
+
+## Quality Checks (before finalizing)
+
+- [ ] Remove duplicates (by domain for SaaS/B2B, by business + address for Local SMB)
+- [ ] Every "Hot" lead has a verified contact + at least one source URL
+- [ ] No lead has an email that failed Truelist (or your validator) verification — move to a separate "invalid" bucket and flag for the user
+- [ ] No lead labeled "Hot" lacks a clear buying signal
+- [ ] Confidence levels honest — "High" requires 2 independent sources, not just two of your own searches
+- [ ] No leads sourced from prohibited scraping (LinkedIn at scale, Google Maps bulk extract, etc.)
+- [ ] Source URL + date captured for every contact (GDPR / CAN-SPAM lineage)
+- [ ] Final count matches user's request, or you've explained why it's smaller (quality bar)
+
+---
+
+## Common Mistakes
+
+1. **Starting discovery without an ICP**. Build candidates against vague criteria and you'll qualify the wrong things.
+2. **Treating data sources as authoritative without cross-checks**. Apollo and ZoomInfo are out of date often; verify before scoring as "Hot."
+3. **Adding contacts without email verification**. Cold email reputation tanks fast with bounces — always validate.
+4. **Bulk scraping LinkedIn or Google Maps**. Real risk: account suspension + ToS violation. Browser as an assisted tool only.
+5. **Mixing branches**. Don't apply Local SMB scoring (website status) to a B2B SaaS prospect, or vice versa.
+6. **"Hot" labels without buying signals**. ICP fit alone is not enough — the signal is what makes the timing right.
+7. **No source URLs**. Every claim should be traceable to a public source. Future outreach depends on this lineage.
+8. **Ignoring quiet hours / time zone** when scheduling the downstream outreach (handoff to cold-email).
+9. **Forgetting to retain consent / lineage records**. Required for GDPR DSARs and CAN-SPAM audits.
+
+---
+
+## Task-Specific Questions
+
+1. Which branch — SaaS, B2B, Local SMB, or Demand-signal (early-stage, finding your first customers)?
+2. What's your ICP? (Or: should I pull from your product-marketing context?)
+3. How many qualified leads do you want?
+4. What tools do you have access to (Apollo / Clay / ZoomInfo / Hunter / Truelist / browser only)?
+5. What's the triggering buying signal you care most about?
+6. Geography or radius (Local SMB / B2B)?
+7. Chat table or CSV?
+
+---
+
+## Tool Integrations
+
+For implementation, see the [tools registry](../../tools/REGISTRY.md). Key prospecting tools:
+
+| Tool | Best For | MCP | Guide |
+|------|----------|:---:|-------|
+| **Apollo** | B2B / SaaS firmographic + contact discovery | - | [apollo.md](../../tools/integrations/apollo.md) |
+| **Clay** | Multi-source enrichment + waterfall | ✓ | [clay.md](../../tools/integrations/clay.md) |
+| **Clearbit** | Email-to-company enrichment | - | [clearbit.md](../../tools/integrations/clearbit.md) |
+| **ZoomInfo** | Enterprise B2B contact + intent | ✓ | [zoominfo.md](../../tools/integrations/zoominfo.md) |
+| **Hunter** | Email pattern + verification | - | [hunter.md](../../tools/integrations/hunter.md) |
+| **Snov** | Email finder + verifier | - | [snov.md](../../tools/integrations/snov.md) |
+| **Truelist** | Email deliverability validation | - | [truelist.md](../../tools/integrations/truelist.md) |
+| **Outreach** | Sales engagement (post-list) | ✓ | [outreach.md](../../tools/integrations/outreach.md) |
+| **RB2B** | Visitor identification (warm intent) | - | [rb2b.md](../../tools/integrations/rb2b.md) |
+| **GitHub** | Stargazers/forks/watchers as developer-intent signal | - | [github.md](../../tools/integrations/github.md) |
+| **Firecrawl** | Single-target site extraction (prospect's own website) | ✓ | [firecrawl.md](../../tools/integrations/firecrawl.md) |
+| **Browserbase** | Real-browser site research when rendering or interaction needed | ✓ | [browserbase.md](../../tools/integrations/browserbase.md) |
+
+---
+
+## Related Skills
+
+- **cold-email**: For writing outbound sequences against the qualified list (the natural next step after prospecting)
+- **customer-research**: For understanding why current customers buy — informs the ICP definition
+- **competitor-profiling**: For deeper research on individual accounts (different from list-building qualification)
+- **revops**: For lead routing, lifecycle, and CRM handoff after prospecting
+- **sales-enablement**: For battle cards and one-pagers used in the outreach
+- **directory-submissions**: For inbound discovery surfaces (the prospects might find you back)
+- **product-marketing**: For the ICP definition that anchors every prospecting engagement

package/org-skills/sales-prospecting/references/b2b-prospecting.md

@@ -0,0 +1,106 @@
+# 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.