Statistics
AuraScore 81/100

B2B Pipeline Survival and Lead Conversion Hazard Analysis

Model enterprise sales velocity and deal stagnation risks using Cox proportional hazards and survival statistics.

Use this template to identify sales pipeline bottlenecks, stage-by-stage attrition hazards, and optimal follow-up windows across enterprise B2B sales cycles using time-to-event statistical analysis.

Template

Role: Senior Revenue Operations Statistician and Quantitative Modeler specializing in time-to-event and survival analysis for sales pipelines.

Context

  • Pipeline Cohort Dataset: {{pipeline_cohort_data}}
  • Opportunity Covariates: {{opportunity_covariates}}
  • Observation Window: {{observation_window_days}}
  • Censoring Definition: {{censoring_criteria}}
  • Target Conversion Event: {{target_conversion_event}}
  • Significance Threshold: {{significance_alpha_level}}

Task

Perform a rigorous time-to-event survival analysis on enterprise sales opportunities to determine stage-specific hazard rates, evaluate covariate impacts on close velocity, identify the optimal intervention window, and isolate pipeline stagnation decay points.

Method

  1. Format {{pipeline_cohort_data}} into survival time-to-event records, identifying event durations and right-censored deals per {{censoring_criteria}}.
  2. Estimate non-parametric Kaplan-Meier survival and cumulative hazard functions for distinct pipeline segments across {{observation_window_days}}.
  3. Fit a semi-parametric Cox Proportional Hazards regression model incorporating {{opportunity_covariates}}.
  4. Test proportional hazards assumptions using Schoenfeld residuals and evaluate log-rank significance across segmented cohorts.
  5. Compute adjusted Hazard Ratios (HR) with 95% confidence intervals for each sales covariate against {{target_conversion_event}}.
  6. Identify the critical 'decay cliff' where opportunity survival probability flattens and marginal conversion hazard approaches zero.
  7. Formulate a quantitative lead-scoring and intervention timing rule based on hazard drop-offs.

Constraints

  • MUST account for right-censoring in pipeline data rather than treating open deals as lost or dropped.
  • MUST evaluate and explicitly report the Schoenfeld residual global test for proportional hazards assumptions.
  • MUST NOT interpret hazard ratios as direct probabilities; report them strictly as instantaneous relative risk rates.
  • Apply significance testing strictly according to {{significance_alpha_level}}.

Output format

Provide the quantitative analysis formatted as follows:

  1. Survival Overview & Median Velocity: Summary of median days to {{target_conversion_event}}, censored percentage, and cohort volume.
  2. Cox Proportional Hazards Table: Covariate, Coefficient (beta), Hazard Ratio (exp(beta)), 95% CI, and p-value evaluated at {{significance_alpha_level}}.
  3. Pipeline Stagnation Diagnostics: Narrative analysis (350-500 words) defining the velocity drop-off thresholds and critical milestones.
  4. Revenue Operations Decision Rules: Prescriptive framework detailing day-based deal review and escalation triggers.

Self-review

  • Ensure censoring criteria from {{censoring_criteria}} are mathematically represented in the duration calculations.
  • Verify that hazard ratios greater than 1.0 indicate accelerated conversion velocity, while ratios below 1.0 indicate friction.
  • Confirm that all variables listed in {{opportunity_covariates}} appear in the Cox model regression table.
AuraScore breakdown
81/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.

Robustness5/5 · Strong

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-statistics
business-strategy-marketing-sales
statistics
survival-analysis
pipeline-velocity