Full prospect analysis orchestrator skill

You are the full prospect audit engine for /sales prospect <url>.

by zubair-trabzada·MIT license·★ 1,400 Stars on the repo·GitHub ↗

Use now

Files of Full prospect analysis orchestrator

zubair-trabzada/main1 file shown
SKILL.md
Show the full text615 lines

Full Prospect Analysis Orchestrator

You are the full prospect audit engine for /sales prospect <url>. You launch 5 parallel subagents, aggregate their results, and produce a unified PROSPECT-ANALYSIS.md report that is ready-to-use and deal-focused.

When This Skill Is Invoked

The user runs /sales prospect <url>. This is the flagship command of the entire suite. It produces the most comprehensive deliverable: a scored, prioritized, actionable prospect analysis with a ready-to-send outreach email.


Phase 1: Discovery (Sequential — Pre-Analysis)

Before launching subagents, perform these discovery steps sequentially. Every subsequent phase depends on this data.

1.1 Fetch the Target URL

Use WebFetch to retrieve the company homepage. Store the full content for subagent consumption.

If the homepage loads successfully, also fetch up to 5 key interior pages:

  • About / Company page
  • Team / Leadership page
  • Pricing page
  • Blog / Resources page
  • Careers / Jobs page
  • Contact page

For each page, store:

  • Page URL
  • Page title
  • Raw content (text)
  • Key data points extracted (names, numbers, product details)

If the URL is unreachable:

  1. Report the error to the user: "Could not reach [url] — HTTP [status code]"
  2. Attempt alternate URLs: try with/without www, try https vs http
  3. If still unreachable, suggest the user verify the URL and try again
  4. Do NOT proceed to Phase 2 if zero pages are accessible
1.2 Detect Company Type

Classify the prospect into one of these categories. This classification shapes every subagent's analysis focus and scoring calibration:

Company Type Detection Signals Analysis Focus
SaaS/Software Free trial CTA, pricing tiers, feature pages, "login" link, API docs, developer documentation, integration marketplace Tech stack, ARR signals, product-led growth, integration ecosystem, developer team size, churn indicators
Agency/Services Case studies, portfolio, "work with us", client logos, testimonials, service packages, hourly/retainer pricing Client roster quality, team size, service positioning, retainer vs project pricing, industry specialization
E-commerce Product listings, cart/checkout, product categories, SKU counts, reviews, shipping info, return policy Product catalog size, traffic signals, tech platform (Shopify, WooCommerce), revenue estimates, fulfillment model
Enterprise Large employee count (500+), multiple office locations, compliance pages, procurement portal, partner ecosystem Org structure, procurement process, budget cycles, compliance needs, vendor requirements, multi-stakeholder buying
SMB Small team (1-50), owner-operator signals, local focus, simple pricing, limited product line Budget constraints, quick ROI needs, ease of implementation, owner as decision maker, price sensitivity
Startup "Backed by" investor logos, founding year recent, small team growing fast, beta/early access language, Y Combinator/accelerator badges Funding stage, burn rate signals, growth trajectory, founding team background, product-market fit signals

Detection procedure:

  1. Scan homepage for signals from each category
  2. Check careers page for employee count and hiring velocity
  3. Check pricing page for pricing model complexity
  4. Look for investor/funding mentions
  5. Assign the best-fit category (if ambiguous, note the two most likely categories)
1.3 Extract Key Pages and Site Architecture

Map the site architecture to identify all pages relevant to sales intelligence:

Page Type Common URLs Data to Extract
Homepage / Headline, value prop, CTAs, social proof, product positioning
About /about, /company, /about-us Founding story, mission, team size, locations, history
Team /team, /leadership, /about/team, /people Names, titles, photos, bios, LinkedIn links
Pricing /pricing, /plans, /packages Tiers, prices, features per tier, enterprise CTA
Blog /blog, /resources, /insights, /news Recent topics, posting frequency, content depth
Careers /careers, /jobs, /join-us, /hiring Open roles, team sizes by department, growth signals
Contact /contact, /get-in-touch, /demo Contact forms, phone numbers, office addresses
Products /products, /features, /solutions, /platform Product lines, features, use cases, integrations
Customers /customers, /case-studies, /testimonials Customer logos, case study details, industry verticals served
Partners /partners, /integrations, /ecosystem Technology partners, integration depth, ecosystem maturity
1.4 Identify Industry Vertical

Determine the prospect's primary industry vertical from these categories:

  • Technology / Software
  • Financial Services / Fintech
  • Healthcare / Healthtech
  • Education / Edtech
  • E-commerce / Retail
  • Manufacturing / Industrial
  • Media / Entertainment
  • Real Estate / Proptech
  • Professional Services / Consulting
  • Marketing / Advertising
  • Logistics / Supply Chain
  • Energy / Cleantech
  • Food / Hospitality
  • Non-profit / Government
  • Other (specify)

Detection signals: Industry-specific terminology, customer logos, case study industries, job posting requirements, compliance mentions, regulatory references.

1.5 Run Structured Data Extraction

Execute the Python analysis script for machine-readable data extraction:

python3 scripts/analyze_prospect.py --url <url> --output json

This script extracts:

  • Structured company metadata
  • Technology stack detection
  • Social media profile links
  • Contact information patterns
  • SEO and traffic signals

If the script is not available or fails:

  1. Log the error but continue the analysis
  2. Perform manual extraction using WebFetch data
  3. Note in the report that automated extraction was unavailable
1.6 Compile Discovery Briefing

Before launching subagents, compile a discovery briefing object containing:

DISCOVERY BRIEFING
==================
URL: [target url]
Company Name: [detected name]
Company Type: [SaaS/Agency/E-commerce/Enterprise/SMB/Startup]
Industry Vertical: [detected vertical]
Key Pages Found: [list of accessible pages with URLs]
Homepage Content: [stored content]
Team Page Content: [stored content or "not found"]
Pricing Page Content: [stored content or "not found"]
Blog Content: [stored content or "not found"]
Careers Content: [stored content or "not found"]
Script Output: [JSON data or "unavailable"]
Initial Signals: [key observations from discovery]

This briefing is passed to every subagent as context.


Phase 2: Parallel Analysis (5 Subagents Simultaneously)

Launch all 5 subagents simultaneously using Claude Code's Task tool. Each subagent receives the full discovery briefing. All subagents run with subagent_type: "general-purpose".

CRITICAL: Launch all 5 in parallel. Do NOT run them sequentially. Each subagent is independent and does not depend on the others.

Subagent 1: sales-company (Company Research & Firmographics)

Skill file: skills/sales-research/SKILL.md Weight: 25% of Prospect Score Focus: Company research, firmographics, financial signals, growth trajectory

Task prompt must include:

  • The full discovery briefing
  • Instruction to produce a Company Fit Score (0-100)
  • Instruction to return structured data: company name, founding date, employee count, funding total, revenue estimate, growth rate, tech stack, key strengths, key risks

Expected output: Company Fit Score (0-100) with breakdown across:

  • Size fit (0-20): Is the company the right size for your solution?
  • Industry fit (0-20): Is the industry a match for your ideal customer profile?
  • Growth trajectory (0-20): Is the company growing, stable, or declining?
  • Tech sophistication (0-20): Does their tech stack suggest readiness for your solution?
  • Budget signals (0-20): Are there signals of adequate budget?
Subagent 2: sales-contacts (Decision Maker Intelligence)

Skill file: skills/sales-contacts/SKILL.md Weight: 20% of Prospect Score Focus: Decision maker identification, org chart mapping, personalization anchors

Task prompt must include:

  • The full discovery briefing
  • Instruction to produce a Contact Access Score (0-100)
  • Instruction to return structured data: buying committee map (name, title, role, personalization anchor), org chart, top 3 priority contacts, multi-threading strategy

Expected output: Contact Access Score (0-100) with breakdown across:

  • Decision makers identified (0-25): How many key decision makers were found?
  • Contact info accessibility (0-25): Can you reach them (email patterns, LinkedIn, etc.)?
  • Personalization anchors (0-25): Quality of personalization hooks found per contact
  • Warm paths available (0-25): Shared connections, communities, mutual contacts
Subagent 3: sales-opportunity (Opportunity & Budget Assessment)

Skill file: skills/sales-qualify/SKILL.md Weight: 20% of Prospect Score Focus: Lead qualification (BANT + MEDDIC), pain point detection, budget signals, buying timeline

Task prompt must include:

  • The full discovery briefing
  • Instruction to produce an Opportunity Quality Score (0-100)
  • Instruction to return structured data: BANT scorecard, MEDDIC assessment, buying signals, red flags, recommended approach

Expected output: Opportunity Quality Score (0-100) with breakdown across:

  • Budget signals (0-25): Evidence of budget availability
  • Authority mapped (0-25): Clarity on who decides and how
  • Need confirmed (0-25): Strength of pain point evidence
  • Timeline urgency (0-25): Signals of near-term buying intent
Subagent 4: sales-competitive (Competitive Positioning)

Skill file: skills/sales-competitors/SKILL.md (if available) or general-purpose competitive analysis Weight: 15% of Prospect Score Focus: Current solutions the prospect uses, switching costs, competitive gaps, positioning strategy

Task prompt must include:

  • The full discovery briefing
  • Instruction to produce a Competitive Position Score (0-100)
  • Instruction to analyze: current vendor signals, technology stack, switching costs, competitive vulnerabilities, positioning angles

Expected output: Competitive Position Score (0-100) with breakdown across:

  • Current vendor identified (0-25): Do we know what they use today?
  • Switching cost assessment (0-25): How hard would it be to switch? (Low cost = high score)
  • Competitive gaps (0-25): Are there gaps in their current solution we can exploit?
  • Win probability (0-25): Based on competitive dynamics, how likely are we to win?

Research methodology for the competitive subagent:

  1. Scan the prospect's website for technology signals (built-with indicators, integration mentions, vendor logos)
  2. Check job postings for tool/platform requirements (e.g., "Salesforce experience required")
  3. Search for the prospect company name alongside competitor product names
  4. Look for review or case study mentions that reveal their current stack
  5. Analyze their tech requirements from careers page
  6. Search web for "[prospect name] uses [competitor]" or "[prospect name] partnered with [vendor]"
Subagent 5: sales-strategy (Outreach Strategy & Messaging)

Skill file: skills/sales-outreach/SKILL.md Weight: 20% of Prospect Score Focus: Outreach strategy, messaging, channel selection, first email draft

Task prompt must include:

  • The full discovery briefing
  • Instruction to produce an Outreach Readiness Score (0-100)
  • Instruction to return: recommended outreach framework, personalization research, channel strategy, first email draft, objection preparation

Expected output: Outreach Readiness Score (0-100) with breakdown across:

  • Personalization depth (0-25): Quality and quantity of personalization anchors
  • Trigger events found (0-25): Recent events that create natural outreach timing
  • Channel strategy clarity (0-25): Clear path to reach decision makers
  • Message-market fit (0-25): Strength of the value proposition match

Phase 3: Synthesis (Sequential — Aggregation and Scoring)

After all 5 subagents complete, aggregate their results into the final analysis.

3.1 Handle Subagent Failures

If any subagent fails or times out:

  1. Note the failure in the report: "[Agent name] analysis unavailable — [reason]"
  2. Assign a neutral score of 50 for that category
  3. Reduce confidence level of the overall Prospect Score
  4. Continue with all available data
  5. Recommend manual follow-up for the failed analysis area
3.2 Calculate Prospect Score (0-100)

Compute the composite Prospect Score using the weighted formula:

Prospect Score = (
    Company_Fit      * 0.25 +
    Contact_Access   * 0.20 +
    Opportunity_Quality * 0.20 +
    Competitive_Position * 0.15 +
    Outreach_Readiness  * 0.20
)

Score interpretation:

Score Range Grade Label Meaning Recommended Action
90-100 A+ Hot Lead Exceptional fit across all dimensions. High close probability. Prioritize immediately. Assign senior rep. Multi-thread outreach within 24 hours.
75-89 A Strong Prospect Strong fit with minor gaps. Worth significant sales investment. Begin personalized outreach within 48 hours. Invest in deep research.
60-74 B Qualified Lead Good fit but notable gaps. Standard sales approach warranted. Add to active pipeline. Begin standard outreach sequence. Monitor for trigger events.
40-59 C Lukewarm Mixed signals. Some fit indicators but significant concerns. Nurture with value-add content. Do not hard sell. Re-evaluate in 30-60 days.
0-39 D Poor Fit Fundamental misalignment on multiple dimensions. Deprioritize. Add to long-term nurture only if one dimension scores above 70.
3.3 Generate Prioritized Action Plan

Based on the Prospect Score and subagent findings, create a three-tier action plan:

Immediate Actions (Next 24-48 Hours):

  • Specific outreach actions to take right now
  • Decision makers to connect with on LinkedIn
  • Content to share or engage with
  • Internal preparation (CRM notes, team briefing)
  • List 3-5 specific actions with assigned priority

Short-Term Actions (Next 1-2 Weeks):

  • Follow-up sequence to execute
  • Additional research to conduct
  • Stakeholders to engage (multi-threading)
  • Competitive positioning to prepare
  • List 3-5 specific actions with timeline

Long-Term Actions (Next 1-3 Months):

  • Relationship-building activities
  • Content nurture strategy
  • Event or conference opportunities
  • Partnership or referral approaches
  • List 2-3 specific actions with milestones
3.4 Create Ready-to-Use First Email

Using the outreach strategy subagent's findings, craft the actual first outreach email. This must be:

  • Copy-paste ready (not a template with placeholders)
  • Personalized to the specific prospect (reference real data found during research)
  • Under 100 words in the body
  • Using one of the four outreach frameworks from the sales-outreach skill
  • With a clear, low-friction CTA
  • With 2 subject line options for A/B testing
  • With the specific send target (name, title, company)
3.5 Confidence Assessment

Rate the overall confidence of the analysis:

Confidence Level Criteria
High All 5 subagents completed successfully. Rich public data available. Multiple data sources confirmed findings.
Medium 4 of 5 subagents completed. Moderate public data. Some findings based on inference.
Low 3 or fewer subagents completed. Limited public data. Significant reliance on inference.
Very Low Major data gaps. Most findings are speculative. Recommend manual research before outreach.

Output Format: PROSPECT-ANALYSIS.md

Write the final report to PROSPECT-ANALYSIS.md in the current directory with this exact structure:

# Prospect Analysis: [Company Name]
**URL:** [url]
**Date:** [current date]
**Company Type:** [detected type]
**Industry:** [detected vertical]
**Prospect Score: [X]/100 (Grade: [letter grade] — [label])**
**Confidence:** [High/Medium/Low/Very Low]

---

## Executive Summary

[3-5 paragraph summary for a sales leader. Lead with the Prospect Score and grade.
Highlight the single biggest opportunity, the single biggest risk, and the
recommended approach. Include the top decision maker to target and the
recommended outreach timing. End with a clear go/no-go recommendation
and expected deal timeline.]

---

## Prospect Snapshot

| Dimension | Value |
|-----------|-------|
| **Company** | [name] |
| **Website** | [url] |
| **Industry** | [vertical] |
| **Company Type** | [SaaS/Agency/E-commerce/Enterprise/SMB/Startup] |
| **Founded** | [year] |
| **Employees** | [count or estimate] |
| **Funding** | [total or "Bootstrapped" or "Public"] |
| **Revenue Est.** | [estimate range] |
| **HQ Location** | [city, state/country] |
| **Key Decision Maker** | [name, title] |
| **Prospect Score** | [X]/100 ([grade]) |
| **Recommended Action** | [one-line action] |

---

## Score Breakdown

| Category | Score | Weight | Weighted | Key Finding |
|----------|-------|--------|----------|-------------|
| Company Fit | [X]/100 | 25% | [X] | [one-line finding] |
| Contact Access | [X]/100 | 20% | [X] | [one-line finding] |
| Opportunity Quality | [X]/100 | 20% | [X] | [one-line finding] |
| Competitive Position | [X]/100 | 15% | [X] | [one-line finding] |
| Outreach Readiness | [X]/100 | 20% | [X] | [one-line finding] |
| **TOTAL** | | **100%** | **[X]/100** | |

---

## Company Profile

[Full company research findings from the sales-company subagent.
Include: overview, business model, product/technology, funding history,
market position, recent developments. Cite specific sources.]

---

## Decision Maker Map

### Buying Committee

| Name | Title | Buying Role | Personalization Anchor | Approach Strategy |
|------|-------|-------------|----------------------|-------------------|
| [name] | [title] | [Economic Buyer/Champion/Technical Evaluator/End User/Blocker] | [specific anchor] | [1-line strategy] |

### Org Chart (Text-Based)

[CEO Name] — CEO ├── [CTO Name] — CTO (Technical Evaluator) │ ├── [VP Eng] — VP Engineering │ └── [Dir Product] — Director of Product ├── [CRO Name] — CRO (Economic Buyer) │ └── [VP Sales] — VP Sales (Champion) └── [CMO Name] — CMO └── [Dir Marketing] — Director of Marketing


### Top 3 Priority Contacts

[Detailed profile for each: name, title, role in buying process,
LinkedIn summary, recent activity, personalization anchors,
recommended approach, suggested first message]

---

## Opportunity Assessment

### BANT Scorecard

| Dimension | Score | Evidence | Confidence |
|-----------|-------|----------|------------|
| Budget | [X]/25 | [specific evidence] | [High/Medium/Low] |
| Authority | [X]/25 | [specific evidence] | [High/Medium/Low] |
| Need | [X]/25 | [specific evidence] | [High/Medium/Low] |
| Timeline | [X]/25 | [specific evidence] | [High/Medium/Low] |
| **Total** | **[X]/100** | | |

### MEDDIC Assessment

| Element | Finding | Evidence | Confidence |
|---------|---------|----------|------------|
| Metrics | [what metrics matter to them] | [source] | [level] |
| Economic Buyer | [who] | [source] | [level] |
| Decision Criteria | [what factors] | [source] | [level] |
| Decision Process | [how they buy] | [source] | [level] |
| Identify Pain | [specific pain points] | [source] | [level] |
| Champion | [potential champion] | [source] | [level] |

### Buying Signals Detected
[Bulleted list of positive buying signals with evidence]

### Red Flags
[Bulleted list of concerns or risks with evidence]

---

## Competitive Landscape

### Current Solutions Detected
[What tools/vendors the prospect currently uses, with evidence]

### Switching Cost Assessment
[Analysis of how difficult it would be for them to switch]

### Competitive Positioning Angles
[How to position against their current solution. Key differentiators to emphasize.
Weaknesses of their current solution to highlight.]

---

## Recommended Outreach Strategy

### Selected Framework
[Which of the 4 outreach frameworks was selected and why]

### Channel Strategy
[Primary and secondary channels. LinkedIn + email timing.]

### Personalization Research
[All personalization anchors found: trigger events, personal interests,
shared connections, recent content, career milestones]

### Objection Preparation
[Top 3 likely objections and prepared responses]

---

## Prioritized Action Plan

### Immediate (Next 24-48 Hours)
1. [Specific action with details]
2. [Specific action with details]
3. [Specific action with details]

### Short-Term (Next 1-2 Weeks)
1. [Specific action with details]
2. [Specific action with details]
3. [Specific action with details]

### Long-Term (Next 1-3 Months)
1. [Specific action with details]
2. [Specific action with details]

---

## Ready-to-Send First Email

**To:** [Name], [Title] at [Company]
**Subject Line A:** [subject]
**Subject Line B:** [subject]

---

[Full email body — copy-paste ready, under 100 words,
personalized with real data from the research]

---

**CTA:** [specific ask]
**Send Timing:** [recommended day/time]
**Follow-Up:** [when and how to follow up if no response]

---

*Generated by AI Sales Team — `/sales prospect`*

Terminal Output

In addition to the file, display a condensed scorecard in the terminal:

============================================
  PROSPECT ANALYSIS COMPLETE
============================================

Company:  [name] ([type])
Industry: [vertical]
URL:      [url]

Prospect Score: [X]/100 (Grade: [letter] — [label])
Confidence:     [High/Medium/Low]

Score Breakdown:
  Company Fit:         [XX]/100 ████████░░
  Contact Access:      [XX]/100 ██████░░░░
  Opportunity Quality: [XX]/100 ███████░░░
  Competitive Position:[XX]/100 █████░░░░░
  Outreach Readiness:  [XX]/100 ████████░░

Key Decision Maker: [Name], [Title]

Top 3 Opportunities:
  1. [opportunity]
  2. [opportunity]
  3. [opportunity]

Top 3 Risks:
  1. [risk]
  2. [risk]
  3. [risk]

Next Step: [single most important action]

Full report saved to: PROSPECT-ANALYSIS.md
============================================

Bar chart rendering rules:

  • Each bar is 10 characters wide
  • Score 0-10 = 1 filled block, 11-20 = 2 filled blocks, etc.
  • Use Unicode block characters: filled = \u2588, empty = \u2591
  • Align all bars and labels for clean terminal display

Error Handling

URL Unreachable
  1. Try alternate URL formats (www/non-www, http/https)
  2. If all fail, report error and stop: "Could not reach [url]. Please verify the URL and try again."
  3. Do NOT generate a report based on zero data
Subagent Failure
  1. Log which subagent failed and why
  2. Assign neutral score (50) for that category
  3. Add a note in the report: "[Category] analysis unavailable — neutral score assigned"
  4. Reduce overall confidence by one level
  5. Continue with remaining subagent data
Site Behind Authentication
  1. Note what was publicly accessible
  2. Analyze only the public pages
  3. Add a note: "Site requires authentication. Analysis limited to publicly accessible pages."
  4. Recommend manual review of gated content
  5. Reduce confidence level accordingly
Minimal Content Site
  1. If fewer than 3 pages are accessible, note "Limited site content"
  2. Supplement with WebSearch for external data (Crunchbase, LinkedIn, news)
  3. Adjust confidence to Low or Very Low
  4. Recommend additional manual research

Cross-Skill Integration

  • If COMPANY-RESEARCH.md exists in the current directory, incorporate its findings instead of running the sales-company subagent from scratch
  • If DECISION-MAKERS.md exists, incorporate its findings into the contact analysis
  • If LEAD-QUALIFICATION.md exists, incorporate its findings into the opportunity assessment
  • If COMPETITIVE-INTEL.md exists, incorporate its findings into the competitive landscape
  • If OUTREACH-SEQUENCE.md exists, reference it in the outreach strategy section
  • Suggest follow-up commands: /sales outreach for full email sequence, /sales prep for meeting preparation, /sales proposal for deal-specific proposal
1# Full Prospect Analysis Orchestrator
2 
3You are the full prospect audit engine for `/sales prospect <url>`. You launch 5 parallel subagents, aggregate their results, and produce a unified PROSPECT-ANALYSIS.md report that is ready-to-use and deal-focused.
4 
5## When This Skill Is Invoked
6 
7The user runs `/sales prospect <url>`. This is the flagship command of the entire suite. It produces the most comprehensive deliverable: a scored, prioritized, actionable prospect analysis with a ready-to-send outreach email.
8 
9---
10 
11## Phase 1: Discovery (Sequential — Pre-Analysis)
12 
13Before launching subagents, perform these discovery steps sequentially. Every subsequent phase depends on this data.
14 
15### 1.1 Fetch the Target URL
16 
17Use `WebFetch` to retrieve the company homepage. Store the full content for subagent consumption.
18 
19If the homepage loads successfully, also fetch up to 5 key interior pages:
20- About / Company page
21- Team / Leadership page
22- Pricing page
23- Blog / Resources page
24- Careers / Jobs page
25- Contact page
26 
27For each page, store:
28- Page URL
29- Page title
30- Raw content (text)
31- Key data points extracted (names, numbers, product details)
32 
33**If the URL is unreachable:**
341. Report the error to the user: "Could not reach [url] — HTTP [status code]"
352. Attempt alternate URLs: try with/without www, try https vs http
363. If still unreachable, suggest the user verify the URL and try again
374. Do NOT proceed to Phase 2 if zero pages are accessible
38 
39### 1.2 Detect Company Type
40 
41Classify the prospect into one of these categories. This classification shapes every subagent's analysis focus and scoring calibration:
42 
43| Company Type | Detection Signals | Analysis Focus |
44|--------------|-------------------|----------------|
45| **SaaS/Software** | Free trial CTA, pricing tiers, feature pages, "login" link, API docs, developer documentation, integration marketplace | Tech stack, ARR signals, product-led growth, integration ecosystem, developer team size, churn indicators |
46| **Agency/Services** | Case studies, portfolio, "work with us", client logos, testimonials, service packages, hourly/retainer pricing | Client roster quality, team size, service positioning, retainer vs project pricing, industry specialization |
47| **E-commerce** | Product listings, cart/checkout, product categories, SKU counts, reviews, shipping info, return policy | Product catalog size, traffic signals, tech platform (Shopify, WooCommerce), revenue estimates, fulfillment model |
48| **Enterprise** | Large employee count (500+), multiple office locations, compliance pages, procurement portal, partner ecosystem | Org structure, procurement process, budget cycles, compliance needs, vendor requirements, multi-stakeholder buying |
49| **SMB** | Small team (1-50), owner-operator signals, local focus, simple pricing, limited product line | Budget constraints, quick ROI needs, ease of implementation, owner as decision maker, price sensitivity |
50| **Startup** | "Backed by" investor logos, founding year recent, small team growing fast, beta/early access language, Y Combinator/accelerator badges | Funding stage, burn rate signals, growth trajectory, founding team background, product-market fit signals |
51 
52**Detection procedure:**
531. Scan homepage for signals from each category
542. Check careers page for employee count and hiring velocity
553. Check pricing page for pricing model complexity
564. Look for investor/funding mentions
575. Assign the best-fit category (if ambiguous, note the two most likely categories)
58 
59### 1.3 Extract Key Pages and Site Architecture
60 
61Map the site architecture to identify all pages relevant to sales intelligence:
62 
63| Page Type | Common URLs | Data to Extract |
64|-----------|-------------|-----------------|
65| **Homepage** | / | Headline, value prop, CTAs, social proof, product positioning |
66| **About** | /about, /company, /about-us | Founding story, mission, team size, locations, history |
67| **Team** | /team, /leadership, /about/team, /people | Names, titles, photos, bios, LinkedIn links |
68| **Pricing** | /pricing, /plans, /packages | Tiers, prices, features per tier, enterprise CTA |
69| **Blog** | /blog, /resources, /insights, /news | Recent topics, posting frequency, content depth |
70| **Careers** | /careers, /jobs, /join-us, /hiring | Open roles, team sizes by department, growth signals |
71| **Contact** | /contact, /get-in-touch, /demo | Contact forms, phone numbers, office addresses |
72| **Products** | /products, /features, /solutions, /platform | Product lines, features, use cases, integrations |
73| **Customers** | /customers, /case-studies, /testimonials | Customer logos, case study details, industry verticals served |
74| **Partners** | /partners, /integrations, /ecosystem | Technology partners, integration depth, ecosystem maturity |
75 
76### 1.4 Identify Industry Vertical
77 
78Determine the prospect's primary industry vertical from these categories:
79 
80- Technology / Software
81- Financial Services / Fintech
82- Healthcare / Healthtech
83- Education / Edtech
84- E-commerce / Retail
85- Manufacturing / Industrial
86- Media / Entertainment
87- Real Estate / Proptech
88- Professional Services / Consulting
89- Marketing / Advertising
90- Logistics / Supply Chain
91- Energy / Cleantech
92- Food / Hospitality
93- Non-profit / Government
94- Other (specify)
95 
96**Detection signals:** Industry-specific terminology, customer logos, case study industries, job posting requirements, compliance mentions, regulatory references.
97 
98### 1.5 Run Structured Data Extraction
99 
100Execute the Python analysis script for machine-readable data extraction:
101 
102```bash
103python3 scripts/analyze_prospect.py --url <url> --output json
104```
105 
106This script extracts:
107- Structured company metadata
108- Technology stack detection
109- Social media profile links
110- Contact information patterns
111- SEO and traffic signals
112 
113**If the script is not available or fails:**
1141. Log the error but continue the analysis
1152. Perform manual extraction using WebFetch data
1163. Note in the report that automated extraction was unavailable
117 
118### 1.6 Compile Discovery Briefing
119 
120Before launching subagents, compile a discovery briefing object containing:
121 
122```
123DISCOVERY BRIEFING
124==================
125URL: [target url]
126Company Name: [detected name]
127Company Type: [SaaS/Agency/E-commerce/Enterprise/SMB/Startup]
128Industry Vertical: [detected vertical]
129Key Pages Found: [list of accessible pages with URLs]
130Homepage Content: [stored content]
131Team Page Content: [stored content or "not found"]
132Pricing Page Content: [stored content or "not found"]
133Blog Content: [stored content or "not found"]
134Careers Content: [stored content or "not found"]
135Script Output: [JSON data or "unavailable"]
136Initial Signals: [key observations from discovery]
137```
138 
139This briefing is passed to every subagent as context.
140 
141---
142 
143## Phase 2: Parallel Analysis (5 Subagents Simultaneously)
144 
145Launch all 5 subagents simultaneously using Claude Code's Task tool. Each subagent receives the full discovery briefing. All subagents run with `subagent_type: "general-purpose"`.
146 
147**CRITICAL:** Launch all 5 in parallel. Do NOT run them sequentially. Each subagent is independent and does not depend on the others.
148 
149### Subagent 1: sales-company (Company Research & Firmographics)
150 
151**Skill file:** `skills/sales-research/SKILL.md`
152**Weight:** 25% of Prospect Score
153**Focus:** Company research, firmographics, financial signals, growth trajectory
154 
155**Task prompt must include:**
156- The full discovery briefing
157- Instruction to produce a Company Fit Score (0-100)
158- Instruction to return structured data: company name, founding date, employee count, funding total, revenue estimate, growth rate, tech stack, key strengths, key risks
159 
160**Expected output:** Company Fit Score (0-100) with breakdown across:
161- Size fit (0-20): Is the company the right size for your solution?
162- Industry fit (0-20): Is the industry a match for your ideal customer profile?
163- Growth trajectory (0-20): Is the company growing, stable, or declining?
164- Tech sophistication (0-20): Does their tech stack suggest readiness for your solution?
165- Budget signals (0-20): Are there signals of adequate budget?
166 
167### Subagent 2: sales-contacts (Decision Maker Intelligence)
168 
169**Skill file:** `skills/sales-contacts/SKILL.md`
170**Weight:** 20% of Prospect Score
171**Focus:** Decision maker identification, org chart mapping, personalization anchors
172 
173**Task prompt must include:**
174- The full discovery briefing
175- Instruction to produce a Contact Access Score (0-100)
176- Instruction to return structured data: buying committee map (name, title, role, personalization anchor), org chart, top 3 priority contacts, multi-threading strategy
177 
178**Expected output:** Contact Access Score (0-100) with breakdown across:
179- Decision makers identified (0-25): How many key decision makers were found?
180- Contact info accessibility (0-25): Can you reach them (email patterns, LinkedIn, etc.)?
181- Personalization anchors (0-25): Quality of personalization hooks found per contact
182- Warm paths available (0-25): Shared connections, communities, mutual contacts
183 
184### Subagent 3: sales-opportunity (Opportunity & Budget Assessment)
185 
186**Skill file:** `skills/sales-qualify/SKILL.md`
187**Weight:** 20% of Prospect Score
188**Focus:** Lead qualification (BANT + MEDDIC), pain point detection, budget signals, buying timeline
189 
190**Task prompt must include:**
191- The full discovery briefing
192- Instruction to produce an Opportunity Quality Score (0-100)
193- Instruction to return structured data: BANT scorecard, MEDDIC assessment, buying signals, red flags, recommended approach
194 
195**Expected output:** Opportunity Quality Score (0-100) with breakdown across:
196- Budget signals (0-25): Evidence of budget availability
197- Authority mapped (0-25): Clarity on who decides and how
198- Need confirmed (0-25): Strength of pain point evidence
199- Timeline urgency (0-25): Signals of near-term buying intent
200 
201### Subagent 4: sales-competitive (Competitive Positioning)
202 
203**Skill file:** `skills/sales-competitors/SKILL.md` (if available) or general-purpose competitive analysis
204**Weight:** 15% of Prospect Score
205**Focus:** Current solutions the prospect uses, switching costs, competitive gaps, positioning strategy
206 
207**Task prompt must include:**
208- The full discovery briefing
209- Instruction to produce a Competitive Position Score (0-100)
210- Instruction to analyze: current vendor signals, technology stack, switching costs, competitive vulnerabilities, positioning angles
211 
212**Expected output:** Competitive Position Score (0-100) with breakdown across:
213- Current vendor identified (0-25): Do we know what they use today?
214- Switching cost assessment (0-25): How hard would it be to switch? (Low cost = high score)
215- Competitive gaps (0-25): Are there gaps in their current solution we can exploit?
216- Win probability (0-25): Based on competitive dynamics, how likely are we to win?
217 
218**Research methodology for the competitive subagent:**
2191. Scan the prospect's website for technology signals (built-with indicators, integration mentions, vendor logos)
2202. Check job postings for tool/platform requirements (e.g., "Salesforce experience required")
2213. Search for the prospect company name alongside competitor product names
2224. Look for review or case study mentions that reveal their current stack
2235. Analyze their tech requirements from careers page
2246. Search web for "[prospect name] uses [competitor]" or "[prospect name] partnered with [vendor]"
225 
226### Subagent 5: sales-strategy (Outreach Strategy & Messaging)
227 
228**Skill file:** `skills/sales-outreach/SKILL.md`
229**Weight:** 20% of Prospect Score
230**Focus:** Outreach strategy, messaging, channel selection, first email draft
231 
232**Task prompt must include:**
233- The full discovery briefing
234- Instruction to produce an Outreach Readiness Score (0-100)
235- Instruction to return: recommended outreach framework, personalization research, channel strategy, first email draft, objection preparation
236 
237**Expected output:** Outreach Readiness Score (0-100) with breakdown across:
238- Personalization depth (0-25): Quality and quantity of personalization anchors
239- Trigger events found (0-25): Recent events that create natural outreach timing
240- Channel strategy clarity (0-25): Clear path to reach decision makers
241- Message-market fit (0-25): Strength of the value proposition match
242 
243---
244 
245## Phase 3: Synthesis (Sequential — Aggregation and Scoring)
246 
247After all 5 subagents complete, aggregate their results into the final analysis.
248 
249### 3.1 Handle Subagent Failures
250 
251If any subagent fails or times out:
2521. Note the failure in the report: "[Agent name] analysis unavailable — [reason]"
2532. Assign a neutral score of 50 for that category
2543. Reduce confidence level of the overall Prospect Score
2554. Continue with all available data
2565. Recommend manual follow-up for the failed analysis area
257 
258### 3.2 Calculate Prospect Score (0-100)
259 
260Compute the composite Prospect Score using the weighted formula:
261 
262```
263Prospect Score = (
264 Company_Fit * 0.25 +
265 Contact_Access * 0.20 +
266 Opportunity_Quality * 0.20 +
267 Competitive_Position * 0.15 +
268 Outreach_Readiness * 0.20
269)
270```
271 
272**Score interpretation:**
273 
274| Score Range | Grade | Label | Meaning | Recommended Action |
275|-------------|-------|-------|---------|-------------------|
276| 90-100 | A+ | Hot Lead | Exceptional fit across all dimensions. High close probability. | Prioritize immediately. Assign senior rep. Multi-thread outreach within 24 hours. |
277| 75-89 | A | Strong Prospect | Strong fit with minor gaps. Worth significant sales investment. | Begin personalized outreach within 48 hours. Invest in deep research. |
278| 60-74 | B | Qualified Lead | Good fit but notable gaps. Standard sales approach warranted. | Add to active pipeline. Begin standard outreach sequence. Monitor for trigger events. |
279| 40-59 | C | Lukewarm | Mixed signals. Some fit indicators but significant concerns. | Nurture with value-add content. Do not hard sell. Re-evaluate in 30-60 days. |
280| 0-39 | D | Poor Fit | Fundamental misalignment on multiple dimensions. | Deprioritize. Add to long-term nurture only if one dimension scores above 70. |
281 
282### 3.3 Generate Prioritized Action Plan
283 
284Based on the Prospect Score and subagent findings, create a three-tier action plan:
285 
286**Immediate Actions (Next 24-48 Hours):**
287- Specific outreach actions to take right now
288- Decision makers to connect with on LinkedIn
289- Content to share or engage with
290- Internal preparation (CRM notes, team briefing)
291- List 3-5 specific actions with assigned priority
292 
293**Short-Term Actions (Next 1-2 Weeks):**
294- Follow-up sequence to execute
295- Additional research to conduct
296- Stakeholders to engage (multi-threading)
297- Competitive positioning to prepare
298- List 3-5 specific actions with timeline
299 
300**Long-Term Actions (Next 1-3 Months):**
301- Relationship-building activities
302- Content nurture strategy
303- Event or conference opportunities
304- Partnership or referral approaches
305- List 2-3 specific actions with milestones
306 
307### 3.4 Create Ready-to-Use First Email
308 
309Using the outreach strategy subagent's findings, craft the actual first outreach email. This must be:
310- Copy-paste ready (not a template with placeholders)
311- Personalized to the specific prospect (reference real data found during research)
312- Under 100 words in the body
313- Using one of the four outreach frameworks from the sales-outreach skill
314- With a clear, low-friction CTA
315- With 2 subject line options for A/B testing
316- With the specific send target (name, title, company)
317 
318### 3.5 Confidence Assessment
319 
320Rate the overall confidence of the analysis:
321 
322| Confidence Level | Criteria |
323|-----------------|---------|
324| **High** | All 5 subagents completed successfully. Rich public data available. Multiple data sources confirmed findings. |
325| **Medium** | 4 of 5 subagents completed. Moderate public data. Some findings based on inference. |
326| **Low** | 3 or fewer subagents completed. Limited public data. Significant reliance on inference. |
327| **Very Low** | Major data gaps. Most findings are speculative. Recommend manual research before outreach. |
328 
329---
330 
331## Output Format: PROSPECT-ANALYSIS.md
332 
333Write the final report to `PROSPECT-ANALYSIS.md` in the current directory with this exact structure:
334 
335```markdown
336# Prospect Analysis: [Company Name]
337**URL:** [url]
338**Date:** [current date]
339**Company Type:** [detected type]
340**Industry:** [detected vertical]
341**Prospect Score: [X]/100 (Grade: [letter grade] — [label])**
342**Confidence:** [High/Medium/Low/Very Low]
343 
344---
345 
346## Executive Summary
347 
348[3-5 paragraph summary for a sales leader. Lead with the Prospect Score and grade.
349Highlight the single biggest opportunity, the single biggest risk, and the
350recommended approach. Include the top decision maker to target and the
351recommended outreach timing. End with a clear go/no-go recommendation
352and expected deal timeline.]
353 
354---
355 
356## Prospect Snapshot
357 
358| Dimension | Value |
359|-----------|-------|
360| **Company** | [name] |
361| **Website** | [url] |
362| **Industry** | [vertical] |
363| **Company Type** | [SaaS/Agency/E-commerce/Enterprise/SMB/Startup] |
364| **Founded** | [year] |
365| **Employees** | [count or estimate] |
366| **Funding** | [total or "Bootstrapped" or "Public"] |
367| **Revenue Est.** | [estimate range] |
368| **HQ Location** | [city, state/country] |
369| **Key Decision Maker** | [name, title] |
370| **Prospect Score** | [X]/100 ([grade]) |
371| **Recommended Action** | [one-line action] |
372 
373---
374 
375## Score Breakdown
376 
377| Category | Score | Weight | Weighted | Key Finding |
378|----------|-------|--------|----------|-------------|
379| Company Fit | [X]/100 | 25% | [X] | [one-line finding] |
380| Contact Access | [X]/100 | 20% | [X] | [one-line finding] |
381| Opportunity Quality | [X]/100 | 20% | [X] | [one-line finding] |
382| Competitive Position | [X]/100 | 15% | [X] | [one-line finding] |
383| Outreach Readiness | [X]/100 | 20% | [X] | [one-line finding] |
384| **TOTAL** | | **100%** | **[X]/100** | |
385 
386---
387 
388## Company Profile
389 
390[Full company research findings from the sales-company subagent.
391Include: overview, business model, product/technology, funding history,
392market position, recent developments. Cite specific sources.]
393 
394---
395 
396## Decision Maker Map
397 
398### Buying Committee
399 
400| Name | Title | Buying Role | Personalization Anchor | Approach Strategy |
401|------|-------|-------------|----------------------|-------------------|
402| [name] | [title] | [Economic Buyer/Champion/Technical Evaluator/End User/Blocker] | [specific anchor] | [1-line strategy] |
403 
404### Org Chart (Text-Based)
405 
406```
407[CEO Name] — CEO
408├── [CTO Name] — CTO (Technical Evaluator)
409│ ├── [VP Eng] — VP Engineering
410│ └── [Dir Product] — Director of Product
411├── [CRO Name] — CRO (Economic Buyer)
412│ └── [VP Sales] — VP Sales (Champion)
413└── [CMO Name] — CMO
414 └── [Dir Marketing] — Director of Marketing
415```
416 
417### Top 3 Priority Contacts
418 
419[Detailed profile for each: name, title, role in buying process,
420LinkedIn summary, recent activity, personalization anchors,
421recommended approach, suggested first message]
422 
423---
424 
425## Opportunity Assessment
426 
427### BANT Scorecard
428 
429| Dimension | Score | Evidence | Confidence |
430|-----------|-------|----------|------------|
431| Budget | [X]/25 | [specific evidence] | [High/Medium/Low] |
432| Authority | [X]/25 | [specific evidence] | [High/Medium/Low] |
433| Need | [X]/25 | [specific evidence] | [High/Medium/Low] |
434| Timeline | [X]/25 | [specific evidence] | [High/Medium/Low] |
435| **Total** | **[X]/100** | | |
436 
437### MEDDIC Assessment
438 
439| Element | Finding | Evidence | Confidence |
440|---------|---------|----------|------------|
441| Metrics | [what metrics matter to them] | [source] | [level] |
442| Economic Buyer | [who] | [source] | [level] |
443| Decision Criteria | [what factors] | [source] | [level] |
444| Decision Process | [how they buy] | [source] | [level] |
445| Identify Pain | [specific pain points] | [source] | [level] |
446| Champion | [potential champion] | [source] | [level] |
447 
448### Buying Signals Detected
449[Bulleted list of positive buying signals with evidence]
450 
451### Red Flags
452[Bulleted list of concerns or risks with evidence]
453 
454---
455 
456## Competitive Landscape
457 
458### Current Solutions Detected
459[What tools/vendors the prospect currently uses, with evidence]
460 
461### Switching Cost Assessment
462[Analysis of how difficult it would be for them to switch]
463 
464### Competitive Positioning Angles
465[How to position against their current solution. Key differentiators to emphasize.
466Weaknesses of their current solution to highlight.]
467 
468---
469 
470## Recommended Outreach Strategy
471 
472### Selected Framework
473[Which of the 4 outreach frameworks was selected and why]
474 
475### Channel Strategy
476[Primary and secondary channels. LinkedIn + email timing.]
477 
478### Personalization Research
479[All personalization anchors found: trigger events, personal interests,
480shared connections, recent content, career milestones]
481 
482### Objection Preparation
483[Top 3 likely objections and prepared responses]
484 
485---
486 
487## Prioritized Action Plan
488 
489### Immediate (Next 24-48 Hours)
4901. [Specific action with details]
4912. [Specific action with details]
4923. [Specific action with details]
493 
494### Short-Term (Next 1-2 Weeks)
4951. [Specific action with details]
4962. [Specific action with details]
4973. [Specific action with details]
498 
499### Long-Term (Next 1-3 Months)
5001. [Specific action with details]
5012. [Specific action with details]
502 
503---
504 
505## Ready-to-Send First Email
506 
507**To:** [Name], [Title] at [Company]
508**Subject Line A:** [subject]
509**Subject Line B:** [subject]
510 
511---
512 
513[Full email body — copy-paste ready, under 100 words,
514personalized with real data from the research]
515 
516---
517 
518**CTA:** [specific ask]
519**Send Timing:** [recommended day/time]
520**Follow-Up:** [when and how to follow up if no response]
521 
522---
523 
524*Generated by AI Sales Team — `/sales prospect`*
525```
526 
527---
528 
529## Terminal Output
530 
531In addition to the file, display a condensed scorecard in the terminal:
532 
533```
534============================================
535 PROSPECT ANALYSIS COMPLETE
536============================================
537 
538Company: [name] ([type])
539Industry: [vertical]
540URL: [url]
541 
542Prospect Score: [X]/100 (Grade: [letter] — [label])
543Confidence: [High/Medium/Low]
544 
545Score Breakdown:
546 Company Fit: [XX]/100 ████████░░
547 Contact Access: [XX]/100 ██████░░░░
548 Opportunity Quality: [XX]/100 ███████░░░
549 Competitive Position:[XX]/100 █████░░░░░
550 Outreach Readiness: [XX]/100 ████████░░
551 
552Key Decision Maker: [Name], [Title]
553 
554Top 3 Opportunities:
555 1. [opportunity]
556 2. [opportunity]
557 3. [opportunity]
558 
559Top 3 Risks:
560 1. [risk]
561 2. [risk]
562 3. [risk]
563 
564Next Step: [single most important action]
565 
566Full report saved to: PROSPECT-ANALYSIS.md
567============================================
568```
569 
570**Bar chart rendering rules:**
571- Each bar is 10 characters wide
572- Score 0-10 = 1 filled block, 11-20 = 2 filled blocks, etc.
573- Use Unicode block characters: filled = `\u2588`, empty = `\u2591`
574- Align all bars and labels for clean terminal display
575 
576---
577 
578## Error Handling
579 
580### URL Unreachable
5811. Try alternate URL formats (www/non-www, http/https)
5822. If all fail, report error and stop: "Could not reach [url]. Please verify the URL and try again."
5833. Do NOT generate a report based on zero data
584 
585### Subagent Failure
5861. Log which subagent failed and why
5872. Assign neutral score (50) for that category
5883. Add a note in the report: "[Category] analysis unavailable — neutral score assigned"
5894. Reduce overall confidence by one level
5905. Continue with remaining subagent data
591 
592### Site Behind Authentication
5931. Note what was publicly accessible
5942. Analyze only the public pages
5953. Add a note: "Site requires authentication. Analysis limited to publicly accessible pages."
5964. Recommend manual review of gated content
5975. Reduce confidence level accordingly
598 
599### Minimal Content Site
6001. If fewer than 3 pages are accessible, note "Limited site content"
6012. Supplement with WebSearch for external data (Crunchbase, LinkedIn, news)
6023. Adjust confidence to Low or Very Low
6034. Recommend additional manual research
604 
605---
606 
607## Cross-Skill Integration
608 
609- If `COMPANY-RESEARCH.md` exists in the current directory, incorporate its findings instead of running the sales-company subagent from scratch
610- If `DECISION-MAKERS.md` exists, incorporate its findings into the contact analysis
611- If `LEAD-QUALIFICATION.md` exists, incorporate its findings into the opportunity assessment
612- If `COMPETITIVE-INTEL.md` exists, incorporate its findings into the competitive landscape
613- If `OUTREACH-SEQUENCE.md` exists, reference it in the outreach strategy section
614- Suggest follow-up commands: `/sales outreach` for full email sequence, `/sales prep` for meeting preparation, `/sales proposal` for deal-specific proposal
615 

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 · MITCold email outreachRun end-to-end B2B cold-email outreach through the Hyper MCP — enrich prospects with Apollo, scrape per-prospect signals from company sites and LinkedIn, draft personalized emails using proven hook frameworks, send via Gmail with safe defaults, and route replies into labeled folders. Use when the user wants to write cold emails, run an outbound sequence, prospect a list, build a follow-up cadence, "reach out to leads," or asks why nobody is replying to their cold emails.Sales & ecommerce · MITBuild a system for handling sales leadsTell us how leads reach your team today and you get back a written playbook for scoring, routing, and following up on every lead fast.Business & ops · MIT