Stage duration is a managed SLA, not a random variable
The right amount of time for a deal to sit in any pipeline stage is determined by your historical data, not intuition. If a deal consistently takes longer than the threshold derived from your average cycle, it either needs a specific intervention or it needs to be disqualified. Leaving aging deals in place degrades forecast accuracy, inflates pipeline coverage ratios, and gives sales managers false confidence.The method for setting stage SLAs:
1. Pull your average sales cycle length from closed-won deals over the past twelve months, segmented by deal size or segment if your cycles differ materially. 2. Map where deals historically spend their time across stages. This is usually available in your CRM's time-in-stage reporting. 3. Set a maximum threshold per stage somewhat above the historical average for that stage, enough to allow for legitimate variation without masking genuinely stalled deals. 4. Flag any deal exceeding the threshold in your pipeline reviews and require a documented reason to remain in stage.
Stage-specific thresholds, not uniform rules
| Stage | Typical characteristics | Threshold logic |
|---|---|---|
| Qualification | Should move quickly to either progress or disqualify | Tighten; long qualification = unclear ICP fit |
| Discovery / Demo | Depends on scheduling and stakeholder count | Moderate; watch for stalls at multi-threading |
| Proposal / Evaluation | Often extended by procurement cycles | Allow more buffer; require documented next step |
| Negotiation / Legal | External dependencies are real | Set a threshold but allow documented exceptions |
| Verbal commit / Close | Should be the shortest stage | Short threshold; long stays here signal slippage |
Why thresholds improve forecast signal
Time-in-stage thresholds surface deal-slippage risk before close dates are officially pushed and force a hygiene conversation that clears zombie deals from the pipeline. Both improve forecast reliability. A pipeline with hard aging limits produces a smaller, cleaner number that is more accurate than a larger pipeline with no discipline around deal age.
Operationalizing the threshold
Thresholds only work if they are reviewed on a cadence. Build them into your weekly or bi-weekly pipeline inspection as a standing agenda item. Surface all deals past threshold automatically in your CRM views so managers are not manually hunting. Connect aging alerts to your deal-risk scoring so that time-in-stage feeds the broader risk signal alongside engagement and stakeholder activity.
For the method that connects stage SLAs to overall pipeline-hygiene, see also time-in-stage for the metric definition and how it is calculated.
Frequently Asked Questions
How do I set a time-in-stage limit for my pipeline?
Take your average sales cycle length and divide it proportionally across your stages based on where deals historically spend time. Add a reasonable buffer above average to account for legitimate variation, then treat anything beyond that threshold as requiring active inspection. Review the thresholds quarterly as your cycle data matures.
What happens when a deal sits too long in one stage?
Deals that age in a stage without documented next steps tend to be either dead opportunities that are not being disqualified, or stalled opportunities that need a different stakeholder or a change in approach. Both outcomes contaminate your forecast and distort pipeline coverage metrics.
Should every stage have the same aging limit?
No. Early stages like discovery or qualification typically move faster. Later stages like legal review or procurement negotiation often have legitimate structural delays. Set thresholds per stage based on actual historical data, not uniform rules applied across the whole funnel.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like how long should a deal sit in a pipeline stage? into prescriptive action for your team.
Schedule a Demo