スキル一覧に戻る
majesticlabs-dev

pipeline-diagnostics

by majesticlabs-dev

18🍴 1📅 2026年1月24日
GitHubで見るManusで実行

SKILL.md


name: pipeline-diagnostics description: Pipeline health assessment with coverage ratios, conversion benchmarks, velocity analysis, and problem diagnosis frameworks. allowed-tools: []

Pipeline Diagnostics

Framework for assessing B2B sales pipeline health and identifying problems.

Pipeline Coverage

Minimum Coverage by Quarter Week:

WeekCoverage NeededWhy
Week 14x quotaTime to work deals
Week 53x quotaDeals maturing
Week 92x quotaLate-stage heavy
Week 131.2x quotaCommit deals

Formula:

Coverage Ratio = Total Pipeline / Quota Target

Stage Conversion Benchmarks

StageBenchmarkIf Below
Lead → Qualified30-40%ICP targeting issue
Qualified → Discovery60-70%Qualification criteria issue
Discovery → Demo50-60%Discovery quality issue
Demo → Proposal40-50%Demo effectiveness issue
Proposal → Closed30-40%Negotiation/pricing issue

Deal Velocity

Formula:

Sales Velocity = (Deals × Win Rate × ACV) / Sales Cycle

Higher velocity = more revenue, faster

Improvement Levers:

  1. More qualified opportunities (volume)
  2. Higher win rate (quality)
  3. Larger deal sizes (ACV)
  4. Shorter sales cycles (speed)

Stage Distribution Analysis

Healthy Pipeline Shape:

Stage 1 (Qualified):    ████████████████████ 35%
Stage 2 (Discovery):    ████████████████ 25%
Stage 3 (Demo):         ████████████ 20%
Stage 4 (Proposal):     ████████ 12%
Stage 5 (Negotiation):  █████ 8%

Red Flags:
- Top-heavy: Too much early stage
- Bottom-heavy: Not enough new pipeline
- Middle stuck: Conversion problem

Age Analysis

StageHealthy AgeStale Threshold
Qualified0-14 days>21 days
Discovery7-21 days>30 days
Demo14-30 days>45 days
Proposal7-14 days>21 days
Negotiation7-21 days>30 days

Stale Deal Actions:

  • <7 days stale: Update and next steps
  • 7-14 days stale: Manager review
  • 14 days stale: Downgrade or close

Win/Loss Analysis

Win Analysis Questions:

  • What was the trigger event?
  • Who was the champion?
  • What was the competitive situation?
  • What value resonated most?
  • How long was the sales cycle?

Loss Analysis Questions:

  • What stage did we lose?
  • Who made the decision?
  • What was the stated reason?
  • What was the real reason?
  • What would we do differently?

Problem Diagnosis

Not Enough Pipeline

Symptoms:

  • Coverage <3x in first half of quarter
  • New pipeline creation slowing
  • Deals closing without replacement

Solutions:

  • Increase outbound activity 50%
  • Run targeted campaign to ICP
  • Re-engage closed-lost from 6+ months ago
  • Ask for referrals from recent wins
  • Partner-sourced pipeline push

Deals Stuck in Stage

Symptoms:

  • Average age exceeds benchmark
  • Same deals appearing in reviews
  • No clear next steps

Solutions:

  • Implement stage exit criteria
  • Add "days in stage" to dashboards
  • Manager review for stale deals
  • Create urgency with limited-time offer
  • Multi-thread to other stakeholders

Low Win Rate

Symptoms:

  • Win rate <20%
  • Losing to "no decision"
  • Losing to specific competitor

Solutions:

  • Tighten qualification criteria
  • Improve discovery process
  • Build champion enablement
  • Create competitive battle cards
  • Address pricing/packaging

Inaccurate Forecasts

Symptoms:

  • Consistent over/under forecasting
  • Deals slipping between periods
  • Late-quarter surprises

Solutions:

  • Define clear commit criteria
  • Weekly deal-by-deal review
  • Track forecast accuracy by rep
  • Implement deal scoring
  • Require close plan for commits

スコア

総合スコア

60/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です