HubSpot, RevOps
Time in Stage in HubSpot: Is Your Pipeline Real?
Posted 20 Nov, 2026 by Lewis Chawko
Time in stage tells you which deals are moving and which are being carried. HubSpot calculates it for you through stage calculated properties, so there is nothing to build. Turn them on, read the median instead of the average, and set a threshold per stage. A pipeline where half the value has not moved in two sales cycles is not a pipeline you can forecast from.
Most pipeline reviews measure the wrong thing. Deal count tells you how busy the team is. Total pipeline value tells you how optimistic they are. Neither tells you whether anything is progressing. Time in stage does, and it is the cheapest signal in the portal because HubSpot already holds it.
What does time in stage measure in HubSpot?
Time in stage is the elapsed time a record has spent in a given pipeline stage. It measures movement, not effort, which is why it exposes deals that look alive on a board and have not changed in months.
HubSpot ships a set of stage calculated properties covering this. Date entered and Date exited give you the timestamps for each stage. Latest time in gives you the time spent since the record last entered that stage. Cumulative time in gives you total time across every entry, which matters when deals bounce backwards. Time in current stage gives you where a deal sits right now.
Those last two distinctions are where most reporting goes wrong, so it is worth being precise about them.
Why does the report show nothing for deals sitting in a stage?
Because Latest time in and Cumulative time in only populate once a record has left the stage. While a deal is sitting in Negotiation, Latest time in Negotiation has no value. The deal that has been stuck for ninety days, which is the one you want to find, is invisible in a report built on those properties.
Time in current stage is the property that works on open deals. Build your stuck-deal view on that one, and keep Latest time in and Cumulative time in for retrospective analysis of deals that have already closed. The same rule applies to automation. HubSpot will not enrol a record in a workflow on Latest time in or Cumulative time in while it is still in that stage, so stalled-deal workflows have to trigger on Time in current stage or Date entered current stage.
This single property choice is the difference between a report your sales leaders use every week and one they open twice and abandon.
What threshold should you set per stage?
Set it from your own closed-won data rather than a benchmark. Pull your won deals from the last twelve months, look at Cumulative time in for each stage, and take the median. The average gets dragged by the one enterprise deal that took eleven months. The median tells you what a normal deal looks like.
HubSpot already does a version of this calculation. The default deal properties include Average deal owner duration in current stage, and Is stalled after timestamp, which HubSpot sets when Time in stage exceeds the deal owner's closed-won average for that stage by twenty per cent. That is a reasonable starting threshold if you have enough closed-won history to make the average meaningful. Below about thirty won deals per stage, set it manually and revisit each quarter.
Expect the thresholds to differ sharply by stage. Discovery to qualified should be days. Proposal to negotiation is usually weeks. The stage where your threshold is hardest to agree is normally the stage with no exit criteria, and that is a process finding, not a reporting one.
What do you do with a stalled deal?
The deal moves forward with a dated next step in the calendar. The deal moves back to a stage that reflects where it genuinely sits. Or the deal closes lost with a reason recorded.
The third option is the one teams avoid, and avoiding it is what makes a forecast unreliable. Carrying a dead deal at seventy per cent probability for two quarters inflates coverage, flatters the commit and hides the gap until the quarter ends. Clearing it out costs you a conversation and buys you a number you trust. If you are also fixing the loss reasons, the two pieces of work compound, which is covered in the post on closed lost reasons.
Build the review into a cadence rather than a campaign. A deal-based report filtered to open deals where Time in current stage is more than your threshold, reviewed in the weekly pipeline meeting, takes ten minutes and does more for forecast accuracy than any amount of probability tuning. Stage hygiene is one of the leaks worth hunting before you look anywhere else, and it sits alongside the other patterns in finding the real revenue bottlenecks in your SaaS funnel.
How does this change the forecast?
It changes what you are allowed to count. Once you have a stage threshold, pipeline coverage splits into two numbers. Active coverage is the deals inside threshold. Carried coverage is everything past it. Teams that report both stop having the argument about whether the pipeline is strong enough, because the question becomes specific.
It also exposes where your cycle is lengthening before revenue shows it. Time in stage moving out in a mid-funnel stage, three months before win rate drops, is the earliest warning you get. Pair it with the accuracy work in what good forecast accuracy looks like and you have a forecast built on observed movement rather than rep sentiment.
None of this needs a project. Turning on stage calculated properties takes an admin a few minutes, and the thresholds come out of data you already hold.
Where should you start?
If you cannot say how much of your current pipeline is moving and how much is being carried, that is the question a RevOps Audit answers. It is a health check of your pipeline, stages and reporting, with a prioritised roadmap that balances quick wins your team can ship this sprint against the foundations that need fixing underneath.
FAQs