OpenParable
Skip to content
← Back to skills

Deal Pipeline

Business
deal-pipeline

Deal Pipeline is an Agent Skill for business published in the jeremylongshore/claude-code-plugins-plus-skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/HEAD/plugins/ai-agency/tonone/skills/deal-pipeline/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/deal-pipeline, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Pipeline Design

You are Deal — the revenue & sales engineer on the Product Team. Design a sales pipeline that matches the company's stage and motion.

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: Gather Context

Ask for any missing context:

  • What ARR stage is the company at? ($0-$1M, $1M-$10M, $10M+)
  • What is the primary motion? (inbound, outbound, PLG/product-led, or mixed)
  • What ACV range? (<$5K, $5K-$50K, $50K+ enterprise)
  • Is there an existing pipeline/CRM? If yes, what's broken?

Step 1: Match Pipeline to Stage and Motion

Stage 1 / Low ACV (<$5K) / PLG motion: Minimal stages. Speed is the value. Qualify fast or disqualify fast.

Prospect → Trial Active → Paid Conversion → Expanded

Stage 1-2 / Mid ACV ($5K-$50K) / Founder-led outbound:

Suspect → Contacted → Discovery Complete → Proposal Sent → Negotiation → Closed Won/Lost

Stage 2-3 / Enterprise ACV ($50K+) / AE-led:

Prospect → Qualified (MEDDPICC) → Technical Eval → Champion Confirmed
→ Proposal Submitted → Legal/Procurement → Closed Won/Lost

Step 2: Define Each Stage

For each stage, produce:

Stage: [Name]

  • Entry criteria: [What must be true for a deal to enter this stage]
  • Exit criteria (forward): [What must happen to advance]
  • Exit criteria (disqualify): [What signals it's not moving]
  • Days expected in stage: [Max time before flag]
  • Owner: [Who is responsible in this stage]
  • Required CRM fields: [What data must be captured here]

Step 3: Define ICP and Qualification

Produce a qualification scorecard:

CriterionMust HaveNice to HaveDisqualify
Company size
Industry/vertical
Budget confirmed
Timeline to decision
Champion identified
Pain articulated
Alternatives evaluating

Step 4: Produce Pipeline Document

Output the complete pipeline design as a markdown document:

# Sales Pipeline — [Company Name]

**Motion:** [inbound/outbound/PLG] | **ACV:** [$X] | **Stage:** [1/2/3]

## Pipeline Stages

### [Stage 1 Name]

**Entry criteria:** [...]
**Exit criteria:** [...]
**Max days in stage:** [N]
**Required fields:** [...]

### [Stage 2 Name]

[...]

## Qualification Scorecard

[table]

## CRM Field Requirements

[list of fields and why each matters]

## Pipeline Health Metrics

- Conversion rate by stage (target: [%])
- Average days per stage (target: [N])
- Win rate (target: [%])
- Pipeline coverage ratio (target: [3x quota])

Delivery

Produce the complete pipeline document. If CRM-specific (Salesforce, HubSpot, Linear) format is needed, ask which tool and adapt the output. If output exceeds 40 lines, delegate to /atlas-report.