ThinkWithPrompt by SynotticThinkWithPrompt

Review pipeline health and forecast

Assesses deal quality, risks, and forecast confidence, with actions per deal.

SalesRCTFVVAdvancedHealth & WellnessAnalyzeFill-in Template

The prompt

Role: Act as a revenue operations lead preparing the weekly forecast and pipeline review. Context: Period: [PERIOD]. Target: [TARGET]. Pipeline snapshot (stage, amount, close date, age, last activity per deal): [PIPELINE_DATA]. Historical stage conversion rates: [CONVERSION_RATES]. Prior forecast: [PRIOR_FORECAST]. Goal: Give sales leadership a clear-eyed view of whether the number is at risk and why, with the specific deals and actions that matter. Task: Analyse: coverage ratio vs target; weighted and unweighted pipeline; deals slipping (age or close-date movement); stuck deals (no recent activity); concentration risk; and a commit / best-case / worst-case forecast with the assumptions behind each. Recommend the 5 actions with the most impact on the number. Constraints: Use only the data provided; do not assume deals not listed. State the conversion assumptions used for the weighted view. Keep commentary factual, not optimistic. Examples: Slip flag shape: 'Deal X - close date moved 3x, now [DATE], age [N] days -> treat as best-case, not commit.' Format: Sections: Coverage & pipeline math | Risks (slipping / stuck / concentration) | Forecast (commit / best / worst + assumptions) | Top 5 actions. ~600 words. Verification: Recompute the coverage ratio and weighted pipeline and show the arithmetic. Flag any deal where required fields are missing. Validation: Challenge your own forecast as a sceptical CRO: which assumption, if wrong, breaks the commit number? Say what evidence would change the call.

Highlighted [brackets] are blanks to replace with your own details.

Fill in the blanks and use this promptMore Sales prompts

What to fill in

  • PERIOD
  • TARGET
  • PIPELINE_DATA
  • CONVERSION_RATES
  • PRIOR_FORECAST
  • DATE

How this prompt is built

This prompt follows the RCTFVV structure (Role, Context, Task, Format, Verification, Validation). RCTFVV extends RCTF with two checking steps. Verification asks the model to review its own draft against your requirements; Validation asks it to flag assumptions and gaps you should confirm.

Related prompts

Find more prompts like this