Sales management
Review pipeline stage age without hiding still-open deals using AI
Separate elapsed age, completed stage visits and repeat visits before describing a sales bottleneck.
An unfinished stage visit has elapsed time, even when a completed-duration field is blank.
Editorial workflow guide · AI-assisted preparation · Not a hands-on product test. How we work
Choose the clock and the comparison population
Define whether the review concerns how long open deals have been waiting now, how long completed stage visits took, or total time across repeat visits. These questions require different fields and denominators. Record the snapshot time, time zone, included pipeline, stage mapping and any exclusions.
Ask AI to prepare separate views rather than one average that mixes the populations. Missing entry dates should stay in an exception group. A deal without a completed duration is not automatically a zero-day deal. Do not discard unfinished work simply because the reporting field is easier to summarize after exit.
Sponsor
SPONSORED
AI FOR YOURSales team.Less busywork.More selling.
Your team knows sales.
We help put AI to work.
Work a still-open example
In a fictional stage, two deals have exited after two and four days. A third has been waiting for 20 days and is still open. The completed-visit average is three days, based on two exits. It does not mean the stage currently clears every deal in three days. The third deal belongs in the open-age review with 20 elapsed days.
Use an explicit label such as completed visits: two, average duration: three days; open visits: one, elapsed age: 20 days. Keep the ongoing visit out of a completed-duration average rather than pretending it ended at the snapshot. This simple split makes the reporting limitation visible without inventing the eventual outcome.
Check repeat visits and the actual properties
HubSpot documents separate current-stage, latest-visit and cumulative-time properties. Latest and cumulative properties can remain blank during an initial ongoing visit or reflect prior visits when a record re-enters a stage. Its current-stage properties answer a different question. Access to calculated properties depends on subscription and configuration.
For a deal that spent five days in a stage, left it and returned two days ago, preserve the earlier visit and current elapsed age separately. Do not assume a stored five-day completed value includes the current two days. Check source history and definitions before computing any custom cumulative figure.
Turn the analysis into a review queue
Return an open-age list with deal ID, current entry time, elapsed age, buyer dependency, next action and owner. Provide completed-visit statistics separately with counts and the exact date window. Flag reopened records, migrated stage names and missing history instead of silently blending them.
Ask the manager what action each unusually old deal needs; age alone does not prove poor selling or buyer rejection. Rehearse with ongoing, completed, re-entered and missing-date examples. This is a proposed reporting review, not a tested forecasting model. Preserve the distinction between observed waiting time and a claim about how quickly future deals will move.
A prompt to adapt
Using these stage definitions and dated records, separate current elapsed age, completed visit duration and repeat-visit history. State the snapshot time, counts and exclusions. Keep missing data unknown and ongoing visits unfinished. Prepare an owner review queue; do not infer win probability or rep performance from age alone.
Use fictional or anonymized examples while testing. Add your approved business rules before using a draft.Source documents
Primary sources support the references above. These workflows are editorial suggestions; confirm current product availability, pricing, permissions, and integration details directly.
Questions or corrections?
See our editorial policy for how we distinguish workflow suggestions, vendor statements, and tested results.