Time in Stage

What Time in Stage Measures

Time in stage is the number of calendar days an opportunity sits in a specific opportunity stage before it advances to the next stage or exits the pipeline. It is a leading indicator: a deal that has been in "Proposal Sent" for 44 days when the average winning deal clears that stage in 9 days is not progressing — it is stalling. Caught at the deal review, it's a coaching conversation. Surfaced at forecast call, it's a revenue surprise.

Most CRMs record stage entry timestamps automatically. Salesforce, HubSpot, and their derivatives all have this data. The gap is in using it.

How Time in Stage Is Calculated

For a single opportunity: Stage Exit Date − Stage Entry Date = Days in Stage.

For a cohort benchmark: Sum of days in stage across all closed-won deals ÷ count of deals = average time in stage for that stage, for winners.

The comparison that matters is won deals versus lost deals, not a generic industry benchmark:

These compress for SMB and extend for enterprise. The authoritative benchmark is your own closed-won cohort from the prior two to four quarters — not a survey average.

Worked Example

A RevOps analyst pulls time-in-stage data on 84 closed-won and 61 closed-lost deals from the prior two quarters. Average time in "Proposal Sent" for won deals: 10 days. Average for lost deals that stalled at this stage before dying: 39 days. She sets an automated flag at 22 days — any deal in "Proposal Sent" longer than that triggers a manager review task in the CRM.

She also finds that deals with a mutual action plan attached moved through "Proposal Sent" in 8 days on average versus 21 days without one. That's a process finding worth acting on — MAP adoption becomes a coaching priority in the next sales kickoff.

Who Uses Time in Stage and How

Sales managers use it in weekly pipeline reviews to catch stalling deals before they slip the quarter. A deal that looks healthy on paper — right size, right stage — looks less healthy when it has been in "Technical Evaluation" for 58 days against a 21-day benchmark for that rep's segment.

RevOps uses stage-age thresholds to set forecast category downgrade rules and pipeline hygiene standards. Opportunities past a stage-specific age floor get automatically moved to a lower confidence tier or flagged for inspection. This creates structural accountability without requiring managers to manually audit every deal.

Individual reps use it as a self-diagnostic. Consistent stalling in "Technical Evaluation" almost always points to a discovery problem — deals were advanced before the technical requirements and success criteria were clear. Time in stage makes the pattern visible instead of attributing every lost deal to bad luck or a difficult buyer.

Finance weights late-stage pipeline by time in stage when building committed forecasts. A stage-4 deal that entered 8 days ago is modeled differently from one that has been there for 52 days, even if both carry the same dollar value and close date.

Gaming Patterns and Blind Spots

The most common manipulation: reps advance opportunities to later stages to reset the clock and avoid time-in-stage alerts, without any actual buyer advancement. A deal moves from "Proposal Sent" to "Negotiation" because the rep emailed a contract draft — not because the buyer responded, marked up terms, or involved legal. Stage velocity looks healthy. The deal is still dead.

The fix is buyer-action-based stage criteria. "Negotiation" begins when the buyer's legal or procurement team requests a redline or issues a purchase order, not when the rep sends one. Every stage-entry trigger should be something the buyer did, not something the rep did.

A second blind spot: time in stage is indifferent to the reason for the delay. A deal sitting in "Evaluation" because the buyer is stuck waiting on internal budget approval looks identical to a deal where the AE has stopped following up. Both read as 45 days. Manager inspection — not the metric alone — distinguishes between them.

Finally, speed through stages is only valuable if it correlates with wins. Pair time-in-stage data with stage conversion rate to know whether velocity actually predicts outcomes in your org. In some enterprise motions, deals that move too fast through evaluation are more likely to stall at legal — the buyer didn't finish their internal diligence. Fast is not always better.