Open Doesn’t Mean Active
A deal sits in the pipeline for four months. Close date came and went back in June.
No calls logged, no notes, no tasks. Ask the rep about it and you get the same answer every time: “Oh, that one’s still open — just waiting to hear back.”
That’s the problem. “Open” is a status, not a promise that something is happening. A pipeline full of technically-open deals gives leadership a forecast that isn’t really a forecast — it’s optimism wearing a spreadsheet. The rep usually isn’t lying. They genuinely believe the deal is alive. But nothing in HubSpot is checking that belief against reality, so it sits there unchallenged, dragging the whole pipeline’s credibility down with it.
The one thing that works is a workflow that checks three conditions at once: no activity logged in X days (Last Activity Date), no future task or meeting scheduled (Next Activity Date is empty), and a close date that’s already passed (Close Date). When all three are true — not one, not two — the workflow doesn’t touch the deal itself. It creates a task for the deal owner. And the task doesn’t ask “is this still good?” It forces a decision: move it forward with a real next step and a close date backed by something the buyer actually said, or close it as lost. Leaving it exactly as it was isn’t an option.
Here’s why the timing matters more than most sales teams realize: deals closed within 50 days of entering the pipeline carry roughly a 47% win rate, but that number drops to 20% or lower the longer a deal sits. A deal that’s already past its close date with no logged activity isn’t a coin flip anymore — it’s much closer to dead than alive. That’s why this can’t be a report a manager glances at once a month. By the time a stale deal shows up in a pipeline review, the odds of saving it have usually already collapsed.
For a sales team, that translates into two very different kinds of help. Reps get a shorter list to actually work — the task tells them exactly which accounts need a real conversation this week, instead of scrolling a pipeline view trying to remember which “open” deals are actually live. And leadership gets a forecast that reflects what’s really likely to close, which means quota conversations, hiring decisions, and revenue projections stop getting built on deals that were already gone.
What I set up for teams
When a client tells me stale deals are a concern, the decision workflow is the centerpiece — but I build two things around it so a deal never drifts all the way to that point unnoticed.
An early nudge at 14 days. A deal-based workflow watches Last Activity Date. When a deal goes 14 days with nothing logged, the owner gets a notification and a task to reach out. This isn’t the decision point. It’s the tap on the shoulder that keeps a quiet deal from becoming a stale one. Fourteen days is where I usually start; longer sales cycles can stretch it.
A stale deals report that shows up on its own. I build a Stale Deals report on the same filters, add it to a sales dashboard, and schedule that dashboard to email the sales team once a week. Nobody has to remember to go look. The list lands in their inbox every week — and a rep who sees their name on it three weeks running doesn’t need a manager to point it out.
Together, the three layers do three different jobs. The 14-day nudge catches deals while they’re still warm. The weekly report keeps the whole team honest. And the decision task makes sure nothing stays “open” just because nobody got around to closing it.
If you want to try this
Start with the report, not the workflows. Build it on the three filters, put it on the dashboard, and let a manager watch the list for a week or two before anything starts assigning tasks. It’s a good gut check on what “stale” should mean for your sales cycle.
Then set your numbers. Thirty days with no activity is a reasonable starting point for the decision task in most B2B cycles, with the 14-day nudge sitting ahead of it as the early warning. A 90-day enterprise sale and a 2-week transactional sale shouldn’t use the same numbers. And don’t confuse any of this with deals that were dead on day one — that’s a qualification problem, not a hygiene problem, and it needs a different fix.
A few habits that keep deals from going quiet in the first place:
- Log every touch, even the small ones. A quick call that didn’t move things forward still resets the clock on Last Activity Date — that’s what keeps the “no activity” trigger honest.
- Never leave a deal without a next step. Before closing out any task tied to a deal, schedule the next one. A deal with an empty task queue is already halfway to stale.
- Treat the close date as a commitment, not a placeholder. If a rep doesn’t have something the buyer actually said to justify the date, it shouldn’t go on the deal yet.
- Check deal age against your average, not the calendar. A deal open 45 days isn’t stale for a 90-day enterprise cycle — it might be very stale for a 2-week transactional one.
- Require a reason on every Closed Lost. It’s the only way “why deals stall” turns into a pattern you can actually fix instead of a mystery you re-solve every quarter.
- Review the stale-deal view weekly, not monthly. By the time a monthly pipeline review catches it, the deal’s win odds have usually already dropped.
Teajai “TJ” Kimsey has been in email marketing since 2005 — credentialed early enough to be featured in a Wichita Eagle story on the shift from direct mail to digital — and is now a certified HubSpot Solutions Partner running BWD LLC, a fractional HubSpot admin practice for small to mid-size B2B companies. With 25+ years of digital marketing experience and Upwork Top Rated Plus status (top 3% worldwide), TJ works directly with every client — no account handoffs, no junior staff. View her portfolio or get in touch to talk through your pipeline.
“Open” is a status, not a promise that something is happening
Frequently Asked Questions
What HubSpot properties actually drive the three conditions?
You need Last Activity Date, the deal’s associated future tasks/meetings (HubSpot can check for an upcoming activity date), and Close Date. All three already exist on a standard deal record — this isn’t a custom property build, it’s a workflow that reads what’s already there.
Do I need Sales Hub Professional or higher to build this?
Yes, for the workflow itself — deal-based workflow automation with multiple branching conditions is a Sales Hub Pro and above feature. If you’re on Starter, you can still build the saved view or dashboard widget on the same three filters and run it as a manual weekly check until you’re ready to automate it.
What if my sales cycle is genuinely long — won't this flag deals that are fine?
Only if you use someone else’s numbers. A 90-day enterprise cycle and a 2-week transactional sale need different “no activity” windows. Set both the 14-day nudge and the stale threshold from your own average time between touches, not a generic best practice — and revisit them once you’ve watched the workflows run for a month.
Does this replace the monthly pipeline review?
No, and it shouldn’t try to. The workflow catches individual deals the moment they go stale so nothing waits a month to get noticed. The pipeline review is still where a manager looks at patterns — is one rep’s whole pipeline aging out, is one stage a consistent bottleneck. Different job, same data.
If a rep closes a deal as lost from this task, how do we keep that useful instead of just clearing it out?
Require a Closed Lost Reason on the way out. Otherwise you’ve fixed your pipeline hygiene but lost the one piece of information — why deals like this stall — that would help you stop it from happening as often.


