Pipeline bottleneck analysis

Analyse pipeline bottlenecks by stage and create practical actions to improve movement and conversion.
Sales - Pipeline bottleneck analysis

Who it's for

Sales managers, RevOps teams, Founders, Revenue leaders, CRM administrators

Get Ready

Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.

How to use this prompt

1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.

🔒

Unlock the Full Workflow

Get access to this workflow and 1000+ others designed to save hours and get better results with AI.

Workflow Prompt

				
					You are a sales pipeline analyst. Your task is to analyse pipeline bottlenecks and recommend practical actions to improve deal movement, conversion, and stage hygiene.

### Required Input
- Pipeline Data: [Provide stage counts, deal values, conversion rates, average stage age, or exported CRM summary]
- Pipeline Stages: [List current stages in order]
- Time Period: [State period analysed, e.g. "last 30 days", "Q1", "current quarter"]
- Sales Motion: [Describe sales type, e.g. "inbound SMB", "outbound mid-market", "enterprise consultative"]
- Team Context: [Describe team size and roles, e.g. "3 AEs, 2 SDRs, founder-led sales"]
- Known Issues: [List suspected problems, e.g. "too many deals stuck in proposal", "poor discovery-to-demo conversion"]
- Sales Targets: [State relevant goal, e.g. "increase monthly closed-won revenue", "reduce deal slippage"]
- Available Activity Data: [List activity data if available, e.g. "calls, emails, meetings, next steps, last activity date"]

### Input Validation
Review all inputs before analysing. If pipeline data, stages, time period, or known issues are missing or too vague, ask specific clarification questions. If exact metrics are unavailable, proceed with a qualitative analysis only if enough context exists, and clearly label limitations. Do not invent conversion rates or stage ages.

### Instructions
Analyse the pipeline to identify where deals are slowing down, dropping out, accumulating without progress, or moving forward without enough qualification. Look at stage volume, stage age, conversion rate, deal value concentration, activity gaps, and stage definitions.

Separate symptoms from likely causes. A large number of deals in proposal may indicate weak qualification, unclear economic buyer access, poor proposal follow-up, pricing friction, or slow approval processes. Do not assume the first visible issue is the root cause.

Prioritise bottlenecks based on revenue impact and fixability. Recommend practical actions that a small team can implement, such as stage exit criteria, stronger discovery questions, proposal review process, next-step enforcement, manager inspection, lead qualification changes, or follow-up cadence improvements.

Include diagnostic questions the team should answer if the provided data is incomplete. Make the output useful for a sales manager preparing a pipeline review or process improvement plan.

### Output
Provide the final answer in this structure:

1. Pipeline Bottleneck Summary
- Main bottleneck
- Secondary bottlenecks
- Revenue impact
- Confidence level based on available data

2. Stage-by-Stage Analysis
For each relevant stage include:
- Stage
- Observed issue
- Likely cause
- Evidence from data
- Risk if unresolved
- Recommended fix

3. Root Cause Hypotheses
- Hypothesis
- Why it may be true
- Data needed to confirm

4. Action Plan
For each action include:
- Priority
- Action
- Owner
- Expected impact
- Timeline

5. Metrics to Monitor
- Metrics that show improvement
- Warning signs that the bottleneck remains

6. Data Gaps and Follow-Up Questions
- Missing data
- Questions to answer before next analysis
				
			

Optional advanced instructions

				
					Add a version that separates bottlenecks caused by lead quality, sales execution, buyer process, and CRM hygiene.
				
			

Example output

1. Pipeline Bottleneck Summary

Inputs used: Pipeline data current quarter: New Lead 180 deals/$1.2M avg age 5d; Discovery 70/$900k avg age 12d; Demo 42/$720k avg age 18d; Proposal 38/$1.1M avg age 34d; Legal 9/$420k avg age 21d; Closed Won 14/$310k. Stages: New, Discovery, Demo, Proposal, Legal, Closed. Motion: inbound SMB and mid-market. Team: 3 AEs, 2 SDRs. Issues: too many deals stuck in proposal, discovery-to-demo inconsistent. Target: increase monthly closed-won revenue and reduce slippage. Activity data: meetings, emails, next steps, last activity date.

Main bottleneck: Proposal stage accumulation and aging. Secondary: inconsistent discovery-to-demo conversion. Revenue impact: $1.1M sitting in proposal with high slippage risk. Confidence: medium-high because stage counts and age show clear congestion.

2. Stage-by-Stage Analysis

  • New Lead: Issue: high volume. Cause: normal inbound flow. Evidence: 180 leads, 5d age. Risk: SDR overload. Fix: hot lead routing and disqualification rules.
  • Discovery: Issue: 70 deals, 12d age. Cause: qualification may be loose. Evidence: large drop into demo. Risk: weak demos. Fix: require pain, timeline, and next step before demo.
  • Demo: Issue: 18d age. Cause: demos may not lead to proposal criteria. Evidence: slower conversion. Risk: vague interest. Fix: add demo exit criteria and stakeholder question.
  • Proposal: Issue: 38 deals, 34d age, $1.1M. Cause: proposals sent too early or not reviewed live. Risk: forecast inflation. Fix: proposal review meeting required and stale proposal cleanup.
  • Legal: Issue: 21d age. Cause: legal may be normal but should be inspected. Risk: close date slip. Fix: legal owner and redline status required.

3. Root Cause Hypotheses

  • Weak qualification: proposal deals lack economic buyer or urgency. Data needed: decision-maker field completeness.
  • Poor proposal process: proposals emailed without live review. Data needed: proposal review meeting rate.
  • Next-step gaps: stalled deals have no scheduled activity. Data needed: next activity coverage by stage.

4. Action Plan

  • High: clean proposal stage. Owner: sales manager. Impact: forecast accuracy. Timeline: this week.
  • High: require proposal review meeting. Owner: AEs. Impact: conversion. Timeline: immediate.
  • Medium: add discovery exit criteria. Owner: manager + SDR lead. Impact: better demos. Timeline: 2 weeks.
  • Medium: stale deal review for deals over 30 days. Owner: AEs. Impact: hygiene. Timeline: weekly.

5. Metrics to Monitor

Proposal age, proposal-to-close conversion, next-step coverage, discovery-to-demo conversion, legal stage age, stale close dates. Warning: proposal count stays high while closed-won remains flat.

6. Data Gaps and Follow-Up Questions

Missing: stage conversion by source, next-step completion, loss reasons, economic buyer field, proposal review rate. Ask: how many proposal deals have a scheduled buyer meeting?

When to reuse this workflow

You may also like...

🔒

Unlock the Full Workflow

Get access to this workflow and 1000+ others designed to save hours and get better results with AI.

No guesswork. Just proven systems.

  • Copy & paste ready prompts
  • Step-by-step instructions
  • Works with ChatGPT instantly

BANT-Based Discovery Call Qualification Script

Qualify leads using the BANT framework to determine fit, urgency, and readiness for sales progression.

Proof Points and Case Study Insertion

Strategically insert proof points and case studies into presentations to increase credibility.

Demo Customisation Framework

Customise demos based on prospect context to increase engagement and close rates.

Unlock the full library.

Get access to all workflows, across every sector, with structured systems built for better results.

Get Free Access