pipeline-velocity-tracking

Track HubSpot pipeline velocity by computing stage-age ratios against trailing 4Q historical medians and flagging opportunities exceeding 1.5x the expected duration. This requires HubSpot stage entry/exit history with data-as-of labeling to detect aging stalls before they impact the quarter.

Pipeline velocity tracking compares current-quarter sales cycle time against historical baselines to identify movement degradation. RevOps teams need it for early stall detection, coaching prep, and segment-level velocity comparisons across active pipeline before a missed quarter becomes apparent.

Compare quarter over quarter sales cycle time by calculating current-quarter average cycle durations against prior-quarter baselines. The Skill uses HubSpot stage entry/exit history and config inputs like avg_sales_cycle_days to generate velocity trend reports showing acceleration or degradation.

Yes, detecting pipeline slowdowns by segment and rep requires historical median stage durations from the trailing four quarters. The Skill uses this baseline alongside HubSpot stage entry/exit history and a primary_segment config to compute stage-age ratios and flag deals aging past expected durations.

Yes, the Skill produces manager-ready analytical outputs that treat flagged deals as escalation-ready signals. It identifies opportunities with stage-age ratios exceeding 1.5x the trailing 4Q historical median, enabling RevOps to prepare coaching and intervention before deals stall further.

Tracking pipeline velocity requires accurate data-as-of labeling on HubSpot stage entry/exit records and trailing 4Q historical medians. Without complete stage transition history or properly configured avg_sales_cycle_days and primary_segment inputs, stage-age ratio calculations and aging flag sweeps will not produce reliable results.