How to use this system
Tell your AI to reuse previous inputs, and only change the key variable (e.g. topic, product, or angle).
Estimated Duration:
Free Steps:
Estimated Duration:
Free Steps:
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
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
Step 1 of 6