Reporting
AuraScore 79/100

Commercial Pipeline Velocity and Leakage Reporting Framework

Structure an advanced diagnostic reporting framework to identify sales funnel friction, deal slippage, and revenue velocity.

Use this prompt when commercial leadership requires an exhaustive diagnostic reporting mechanism to pinpoint where revenue leaks occur between deal stages. It establishes rigorous stage-gate criteria, velocity calculations, and remediation protocols.

Template

Role: Senior Director of Revenue Operations and Strategic Commercial Analytics specializing in pipeline integrity, conversion mechanics, and forecasting accuracy.

Context

  • Business & GTM Model: {{revenue_model}}
  • Defined Sales Stages: {{pipeline_stages}}
  • Historical Conversion Baselines: {{win_rate_benchmarks}}
  • Stagnation Criteria: {{deal_slippage_thresholds}}
  • Sales Coverage Segmentation: {{sales_territory_segmentation}}
  • Analytical Time Horizon: {{forecast_period}}

Task

Develop a comprehensive commercial pipeline health and velocity reporting framework that uncovers operational leakages and provides forecast risk visibility across {{pipeline_stages}} for {{sales_territory_segmentation}}.

Method

  1. Formulate standardized stage-to-stage conversion rate formulas normalized for {{revenue_model}} sales dynamics.
  2. Define velocity metrics measuring average days in stage, total sales cycle duration, and pipeline throughput.
  3. Establish an automated pipeline leakage identification protocol based on {{deal_slippage_thresholds}} and historical win rates.
  4. Design risk-weighting algorithms that adjust pipeline coverage ratios based on deal age and rep activity signals.
  5. Structure segment-level cohort analysis comparing performance across {{sales_territory_segmentation}} against {{win_rate_benchmarks}}.
  6. Create an executive exception report mechanism to highlight stalled high-value opportunities over the {{forecast_period}}.
  7. Establish actionable governance protocols detailing operational remediation actions for sales managers.

Constraints

  • MUST distinguish between deal stagnation (aging in stage) and genuine deal slippage (push-date changes).
  • MUST NOT treat pipeline volume as a proxy for pipeline quality or forecasted revenue certainty.
  • All conversion benchmarks must incorporate weighted statistical confidence intervals.
  • Provide direct cross-references between stage transition definitions and CRM data validation gates.

Output format

  1. Stage-Gate Velocity & Leakage Matrix (table with Stage, Entrance Criteria, Exit Velocity, Leakage Trigger)
  2. Pipeline Risk-Weighting Algorithm Specification (mathematical definitions and variable criteria)
  3. Territory Performance Diagnostic Blueprint (visual hierarchy and comparative KPI structure)
  4. Managerial Remediation Playbook (action matrix mapping specific leak types to coaching/operational interventions)

Self-review

  • Are the calculations adaptable across different deal sizes within {{sales_territory_segmentation}}?
  • Does the framework define clear push-date penalty rules to counter forecast sandbagging?
  • Is every pipeline transition in {{pipeline_stages}} rigorously defined with measurable entry/exit criteria?
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

data-analytics
data-reporting
business-strategy-marketing-sales
pipeline analytics
sales reporting
revenue velocity