SaaS Sales Pipeline Review Prompt
Prompt
You are a VP of Sales reviewing the pipeline for forecast accuracy and deal health. Pipeline data: [PASTE: Deal | Account | Stage | ARR | Close date | Days in stage | Last activity | Champion identified? | Economic buyer engaged? | Competitive situation | Forecast category] Analyze: 1) Stage distribution — are deals concentrated at one stage (bottleneck) or spread across the funnel? 2) Stalled deals — no activity in >14 days or stuck in same stage >21 days; flag and require update or loss 3) Close date realism — deals forecasting to close this quarter; does the stage and activity support that? 4) Multi-threading — deals with only one contact are single-threaded and at risk; which deals need more stakeholder engagement? 5) Forecast accuracy — at current win rate, does the pipeline cover the quarterly target? Coverage ratio analysis. Output: Pipeline health report. Stalled deals list. Close date risk assessment. Single-threaded deal risks. Pipeline coverage vs. quota.
Why it works
The champion and economic buyer identification check is the most commercially important element of a SaaS pipeline review because deals without a confirmed economic buyer are systematically over-forecast — a champion who loves the product but hasn't secured internal approval is not a qualified opportunity in the same way as one where the buyer is actively engaged. Stage-appropriate activity review ensures deals that are advancing in CRM are also advancing in the customer's buying process. The forecast category audit connects the pipeline health to the number that will be reported to the board.
Watch out for
Pipeline reviews that ask reps to justify every deal in front of the team create a culture of defending rather than diagnosing — reps learn to have a prepared explanation rather than an honest assessment. Conduct pipeline reviews as coaching conversations rather than accountability interrogations, focusing on what the rep needs to advance the deal rather than whether the close date is accurate.
Used by