Skip to content

tonone-ai/tonone / bundle/full-team/skills/deal-recon

deal-recon

Verified

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".

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:

# 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:

SignalStage 1 ($0-$1M)Stage 2 ($1M-$10M)Stage 3 ($10M-$100M)
Deals closed<1010-100100+
Sales motionFounder-ledFirst repsSales org
PlaybookInformal/noneWrittenFormalized
CRMSpreadsheetBasic CRMFull RevOps

Step 2: Map the Pipeline

Identify current state of:

  • ICP definition — Is target customer segment defined? Documented?
  • Acquisition motion — How do prospects find the product? Inbound / outbound / PLG?
  • Pipeline stages — What are the defined stages from prospect to closed?
  • Deal velocity — How long from first contact to close?
  • Win rate — What % of qualified opportunities close?
  • ACV/ARR — Average contract value, range, and distribution

Step 3: Identify the Constraint

Use the MEDDPICC framework to find where deals stall:

ComponentStatusEvidence
Metrics (ROI defined)[✓/✗/~]
Economic Buyer (identified)[✓/✗/~]
Decision Criteria (mapped)[✓/✗/~]
Decision Process (documented)[✓/✗/~]
Paper Process (known)[✓/✗/~]
Pain (buyer-level, not user-level)[✓/✗/~]
Champion (inside account)[✓/✗/~]
Competition (understood)[✓/✗/~]

Step 4: Inventory Sales Assets

AssetExists?Quality
ICP definition doc[✓/✗]
Outbound sequence[✓/✗]
Discovery call guide[✓/✗]
Pricing tiers[✓/✗]
Proposal template[✓/✗]
Objection handling guide[✓/✗]
Case studies/social proof[✓/✗]

Step 5: Present Assessment

## Revenue Reconnaissance

**Stage:** [1/2/3] — [descriptor] | **ARR:** [current or estimated]
**Primary motion:** [inbound/outbound/PLG/founder-led]
**Biggest constraint:** [the one thing blocking more revenue]

### Pipeline State
| Stage | Defined | Measured | Notes |
|-------|---------|----------|-------|
| Awareness → Lead | [✓/✗] | [✓/✗] | |
| Lead → Qualified | [✓/✗] | [✓/✗] | |
| Qualified → Proposal | [✓/✗] | [✓/✗] | |
| Proposal → Close | [✓/✗] | [✓/✗] | |

### MEDDPICC Gaps
[List the 2-3 most critical gaps]

### Highest Leverage Action
[Single most important thing to do this week to improve revenue]

Delivery

If output exceeds 40-line CLI budget, invoke /atlas-report with full findings. CLI is the receipt — box header, one-line verdict, top 3 findings, report path. Never dump analysis to CLI.

rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall