deal-recon

Featured

Revenue reconnaissance — audit current sales pipeline, deal patterns, ICP definition, and revenue motion to understand what's working and where the constraint is. Use when asked to "audit our sales", "where is revenue stuck", "what's our pipeline state", "before designing a playbook".

AI & Automation 2,274 stars 319 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Revenue Reconnaissance You are Deal — the revenue & sales engineer on the Product Team. Map the current revenue state before building any playbook or pipeline. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Revenue Artifacts Scan for sales and revenue artifacts: ```bash # CRM or deal tracking find . -name "*.md" -o -name "*.csv" -o -name "*.json" 2>/dev/null | xargs grep -l "pipeline\|deal\|prospect\|customer\|ARR\|MRR\|revenue\|close.date\|ICP" 2>/dev/null | head -15 # Pricing docs find . -name "*.md" 2>/dev/null | xargs grep -l "pricing\|price\|tier\|plan\|enterprise\|starter\|pro\|free" 2>/dev/null | head -10 # Sales playbooks or sequences find . -name "*.md" 2>/dev/null | xargs grep -l "outbound\|sequence\|outreach\|cold.email\|SDR\|AE\|BDR\|sales.call\|discovery" 2>/dev/null | head -10 # Revenue metrics find . -name "*.md" 2>/dev/null | xargs grep -l "churn\|NRR\|MRR\|ARR\|ARPU\|LTV\|CAC\|win.rate\|conversion" 2>/dev/null | head -10 ``` ### Step 1: Diagnose Revenue Stage Determine which stage the company is at based on any available signals: | Signal | Stage 1 ($0-$1M) | Stage 2 ($1M-$10M) | Stage 3 ($10M-$100M) | | ------------ | ---------------- | ------------------ | -------------------- | | Deals closed | <10 | 10-100 | 100+ | | Sales motion | Founder-led | First reps | Sa...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

deal

Revenue & Sales engineer — B2B pipeline, deal strategy, pricing proposals, sales playbooks, and enterprise closing.

2,274 Updated today
jeremylongshore
AI & Automation Listed

cro-advisor

Revenue leadership for B2B SaaS companies. Covers revenue forecasting, sales model design, pricing strategy, net revenue retention, sales team scaling, pipeline management, and board-level revenue reporting. Use when designing the revenue engine, setting quotas, modeling NRR, evaluating pricing, building forecasts, scaling sales teams, or when user mentions CRO, revenue strategy, sales model, ARR growth, NRR, expansion revenue, churn, pricing strategy, sales capacity, pipeline, quota, or MEDDPICC.

208 Updated 4 days ago
borghei
AI & Automation Solid

revenue-operations

Analyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics for SaaS revenue optimization. Use when analyzing sales pipeline coverage, forecasting revenue, evaluating go-to-market performance, reviewing sales metrics, assessing pipeline analysis, tracking forecast accuracy with MAPE, calculating GTM efficiency, or measuring sales efficiency and unit economics for SaaS teams.

16,782 Updated 3 days ago
alirezarezvani
AI & Automation Listed

revenue-operations

Analyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics for SaaS revenue optimization. Use when analyzing sales pipeline coverage, forecasting revenue, evaluating go-to-market performance, reviewing sales metrics, assessing pipeline analysis, tracking forecast accuracy with MAPE, calculating GTM efficiency, or measuring sales efficiency and unit economics for SaaS teams.

3 Updated today
Elfredaaroused655
AI & Automation Featured

deal-pipeline

Design or audit B2B sales pipeline — define stage names, entry/exit criteria, qualification standards, and CRM field requirements. Use when asked to "design our pipeline", "audit our CRM stages", "define what qualified means", or "build a sales process".

2,274 Updated today
jeremylongshore