Feature · Stale Deal Detection

Stale deals in the pipeline, detected before they slip.

Not another "last activity" column. Strkr surfaces stale deals as a first-class list, AI-drafts the nudge email, tracks days-in-stage against the pipeline average, and flags slip signals before the Monday forecast meeting.

Start free trial See pricing
What stale means in your pipeline

The deals that are silently going cold.

A stale deal is one that has stopped moving: no activity in a defined window, no field update, no stage transition. The deal still sits in the pipeline, still counts toward the forecast, still reports in the dashboard. But the signals say it is dying. Most teams discover stale deals at quarter-close when the forecast misses. Strkr surfaces them earlier so the save motion starts while there is still a chance.

What counts as stale

A tenant-configurable threshold.

The default: no activity in 10 days on a commit deal, 20 days on best-case, 30 days on pipe. Teams running longer sales cycles can extend the thresholds. Admin surface sets the thresholds per pipeline so new business and renewals can have different definitions of stale.

What activity counts

Emails, calls, meetings, SMS, notes.

Activity means a real touch: an email sent or received, a call logged, a meeting held, an SMS exchanged, a note added, a stage transition. Field updates alone do not count (reps editing fields to "look busy" would otherwise mask real stall). The classic workaround ("I bumped the close date, that counts") is prevented.

Stale by stage

Different stages, different patience.

A deal in Discovery can be stale after 5 days because early-stage deals should move quickly. A deal in Negotiation can tolerate 15 days because contract negotiation stalls happen. The threshold varies by stage so the alerts match reality rather than fire false positives.

Days-in-stage comparison

Compare to the pipeline average.

Beyond the stale threshold, the deal page shows how long the deal has been in its current stage versus the pipeline average. A deal in Proposal for 45 days when the average is 14 is a red flag even if there was activity last week. Context on top of absolute thresholds.

AI signal grading

Multiple signals combined into a grade.

Strkr AI reads six signal classes (activity recency, decision-maker engagement, stage velocity, close-date slippage, email reply cadence, meeting attendance) and produces a Green / Yellow / Red grade. A deal with recent activity but no DM engagement and three close-date slips still grades Red.

Visible everywhere

Stale indicator on the Kanban card.

The stale state surfaces on the Kanban board card (red dot or chip), on the deal detail page, on the forecast surface, in the Monday email, and in the rep's daily task list. The signal reaches the rep in whichever surface they open first; no "I did not see the alert" excuse.

The stale-deal list surface

A first-class page for pipeline rescue.

Most CRMs surface stale deals as a filter on the deal list. Strkr builds the stale-deal list as a dedicated page because rescue is a specific workflow that benefits from its own home. Reps open the page Monday morning, triage the list in 15 minutes, and send drafted nudges from the surface.

Ranked list

Sorted by amount, filterable by rep.

The stale-deal page shows every stale deal sorted by amount descending by default. Managers filter to a specific rep. Reps see only their own deals. Each row shows the deal, amount, stage, days-in-stage, days-since-activity, AI grade, and the one-line reason.

AI-drafted nudge

The follow-up email, pre-written.

Each stale deal gets an AI-drafted nudge email referencing the last conversation and suggesting a specific next step. The rep opens the deal, reads the draft, edits for voice, and sends in under a minute. Fifteen stale deals get rescued in the time it used to take to rescue three.

Bulk actions

Snooze, send, assign, close.

Multi-select deals and run bulk actions: snooze for 7 days (will not re-surface until then), send all drafts after review, reassign to another rep, or mark as closed lost with a reason. The 20-minute batch triage is a one-page workflow.

Save motion tracking

Which rescues work, which do not.

When a rep sends a nudge from a stale deal, the deal's status is tracked: did the nudge produce a reply, a next step, a stage transition, a close? Over a quarter the surface shows which reps have the highest rescue rate and which nudges produce the best results.

Manager roll-up

The team's rescue queue, visible.

Managers see the team-level rescue queue: how many stale deals, how many drafts pending, how many sent this week, how many produced replies. The 1:1 conversation about pipeline hygiene has numbers rather than vibes.

Weekly digest

Stale deals land in the Monday email.

The Monday forecast email includes the top stale deals across the team. Leader opens the email, sees the three largest deals that need rescue, walks into the standup with a specific agenda.

Automatic rescue

The stale-deal nudge Flow that runs itself.

The stale-deal rescue workflow is one of the most useful automations a mid-market revenue team can turn on. Strkr ships it as a starter template that runs daily, generates AI drafts, routes them to the owning rep, and tracks the outcome.

Daily scheduled Flow

6am local, every rep gets their stale list.

Scheduled Flow runs daily at 6am tenant-local. For every rep, pulls stale deals, sorts by amount, generates AI-drafted nudges, lands the list in the rep's inbox and in-app notification. The rep opens Strkr Monday morning to a prepared rescue queue.

Smart draft generation

The draft knows the deal context.

The AI draft is informed by the thread history, the deal stage, the last conversation, and the rep's past tone. The draft references the specific prior interaction ("following up on our chat about the pilot program") rather than a generic "just checking in." Context on the draft, not a mail-merge template.

Suggested next step

A specific CTA, not a generic ask.

The draft includes a specific proposed next step tied to the deal stage: "Can we schedule the security review for next week?" or "Do you have 20 minutes Wednesday to walk through the mutual close plan?" Reps edit the specifics; the CTA shape is already there.

Rep review

Nothing sends without the rep clicking.

Drafts land in the rep's review queue, not in the recipient's inbox. The rep reads, edits, and sends. The classic "the AI sent something tone-deaf" risk is prevented by human-in-the-loop on every send.

Follow-up tracking

Did the nudge produce a response?

When the nudge sends, the deal is tagged as "rescue attempted." The Flow watches for a reply within 7 days. If a reply lands, the rescue is marked successful. If not, the deal appears on next week's stale list with an escalated signal. The classic "I nudged but nothing happened" result is tracked and surfaced.

Snooze and dismissal

Not every deal needs rescue.

Reps can snooze a deal from rescue (waiting on legal, buyer OOO, mutually scheduled next step), with a reason captured. Snoozed deals do not re-surface until the snooze expires. The classic "the alert keeps firing on a deal I know about" annoyance is addressed.

The slip signal

Deals that fell out of commit, week over week.

Stale deals are one failure mode. Slip is another: a deal that was in a rep's commit column last week and in best-case or pipe this week. The slip is a leading indicator of a quarter-close miss. Strkr tracks every slip, surfaces them weekly, and feeds the pattern into rep accuracy scoring.

Slip definition

Commit to lower category, week over week.

When a rep moves a deal from commit to best-case, pipe, or omit between forecast submits, Strkr records the slip. The slip is tracked at the submit boundary (Friday 5pm lock), so mid-week waffling does not count. The number is the number of slips at the Friday boundary.

Weekly slip list

Every slip from the last submit cycle.

A dedicated page lists every slip from the most recent submit cycle: deal, amount, prior category, new category, reason (editable by rep), manager comment. Managers scan the slip list before the Monday standup; the conversation about "what fell out this week" has specifics.

Rep slip count

A quarterly tally per rep.

Over the quarter, Strkr tracks total slips per rep. A rep with 15 slips in a quarter has a different pipeline-management pattern than a rep with 3. The slip count surfaces on the rep profile and feeds the manager coaching conversation.

Pattern recognition

Which stages produce the most slips?

The slip report breaks slips down by stage: which stages see commits slip most often? If 60 percent of slips happen out of Negotiation, the problem is late-stage. If 60 percent slip out of Proposal, the problem is proposal quality. The pattern tells the ops team where to focus.

Commit creep

Reps who raise mid-week, then slip.

Some reps show a pattern: raise commit mid-week, then slip it on next Friday's submit. The raise-then-slip pattern is coachable. Strkr flags reps who show the pattern over the quarter so managers can intervene before the quarter-close surprise.

Accuracy score impact

Slips shape the rolling accuracy number.

Rep accuracy score is computed as the rolling 8-week delta between committed and actual. Slips show up in the delta: a rep who commits high and lands low has a low accuracy score. The score surfaces on the forecast page next to the roll-up and on the rep profile.

Integration with the Monday ritual

The stale-deal and slip signals in the forecast meeting.

The Monday morning forecast meeting is the ritual revenue teams run against pipeline health. Stale deals and slips are the two most useful signals in that meeting. Strkr surfaces both directly in the forecast surface and the Monday email so the meeting opens with the right specifics.

On the forecast surface

Stale and slipping, inline.

The forecast page shows every rep's commit column with inline indicators: red dot for stale, down arrow for slipped-this-week. The manager scrolling the roll-up sees the signal without a separate hunt.

In the Monday email

Top stale and top slipped at the top.

The Monday forecast email leads with the three largest stale deals across the team and the three largest slips from last week. The leader opens the email and sees the hot items before scanning the rest of the roll-up.

During meeting mode

The standup walks the hot items first.

Click Meeting Mode on the forecast surface and the presentation layout opens with stale and slipped deals ranked at the top of each rep's section. The manager's standup script has the agenda baked in.

Action items

Rescue tasks assigned during the call.

When the manager assigns a rep an action during the call ("rescue this stale deal by Wednesday"), Strkr drops the action as a task with a due date. The task surfaces in the rep's daily list. The classic "we talked about it but nothing happened" leak is prevented.

Weekly digest to leaders

Executive view of pipeline hygiene.

The VP-level Monday email adds a hygiene section: total stale deals, total slips, team average rescue rate, worst-performing rescue rep. The leader scanning the digest sees whether pipeline hygiene is improving or regressing.

Quarter-close reconciliation

The end-of-quarter rescue scorecard.

Final week of the quarter, Strkr generates the rescue scorecard: how many stale deals were worked, how many were rescued, how many closed. One page per rep, one aggregate per team. The QBR has the hygiene data pre-pulled.

Compared to the alternatives

What a native stale-deal surface replaces.

Most CRMs surface stale deals as a last-activity column on the deal list, if at all. Teams running pipeline-hygiene seriously typically assemble the stack from four tools: the CRM filter, a sales-enablement platform for nudging, a BI dashboard for the report, and a sales-ops Slack channel for the manager visibility. Strkr's native stale-deal surface replaces the stack.

Salesforce stale filter

A filter on the deal list, not a surface.

Salesforce handles stale-deal detection via a saved report filter on last-activity date. The report exists but has no surface for rescue (no drafted nudges, no bulk actions, no outcome tracking). Teams built on top with workflow rules and custom code; the result is a brittle in-house build.

HubSpot workflows

Alerts on inactivity, no AI drafts.

HubSpot Workflows can send alerts when a deal has no activity in N days. The alert goes to the rep but no AI-drafted nudge accompanies it. The rep writes the email from scratch. The feature exists but the recovery friction is still high.

Pipedrive Rotting Deals

Simple rotting-deal indicator.

Pipedrive highlights deals that have been in a stage longer than the stage's rotting threshold. The indicator exists on the Kanban card. Beyond the visual flag, no drafted nudge, no bulk workflow, no slip tracking.

Gong Engage / Outreach

Cadence tools that can nudge, separately.

Sales-engagement tools (Outreach, Salesloft, Gong Engage) can enroll stale deals in a nudge cadence. The feature works but lives in a separate tool from the CRM with a sync bridge. The rep context-switches between pipeline and cadence tool.

Clari Flow

Forecasting-first with pipeline-health signals.

Clari's pipeline-health module surfaces stale deals and slip signals in the context of forecasting. Strong at the signal, priced as an enterprise add-on. For teams already on Clari for forecasting the feature extends the subscription cleanly; for teams starting fresh, Strkr's native surface replaces it.

Strkr Stale Deals

Native, AI-drafted, bulk, tracked.

Dedicated stale-deal page, AI-drafted nudges, bulk send actions, outcome tracking, slip signal, Monday email integration, meeting mode visibility, quarter-close scorecard. The pipeline-hygiene surface most teams build from four tools ships as one layer on Pro.

The stale-deal surface ships on Pro. The AI nudge drafter ships on Pro. The slip tracker ships on Pro.

A dedicated rescue workflow, drafted nudges, bulk actions, outcome tracking, included. Start a trial, rescue your stale pipeline this week.

Start free trial See pricing
Common questions

What buyers ask about this feature.

What are stale deals in a deal pipeline?

A stale deal is one that has stopped moving in your pipeline: no activity (emails, calls, meetings, SMS, notes) in a defined window, no field update, no stage transition. The deal still sits in the pipeline, still counts in the forecast, still reports in the dashboard. But the signals suggest it is dying. Most teams discover stale deals at quarter-close when the forecast misses. The useful move is to detect them earlier and start the rescue motion while there is still a chance to save them. Strkr's stale-deal surface is a first-class page for exactly this workflow.

How do I find stale deals in my pipeline?

Three paths. First, the dedicated stale-deal page in Strkr lists every stale deal across the pipeline, sorted by amount, filterable by rep, with AI-drafted nudges attached. Second, the Kanban board shows a red indicator on each stale card so stale deals are visible wherever the rep works. Third, the Monday forecast email leads with the top stale deals across the team so leaders see the hot items before the standup. The classic approach (a last-activity-date filter on the deal list) exists in every CRM but misses the context (what counts as activity, what the threshold should be per stage, which deals are the right rescue priority).

What counts as activity on a deal?

Activity means a real touch: an email sent or received, a call logged, a meeting held, an SMS exchanged, a note added, a stage transition. Field updates alone do not count because reps editing fields to "look busy" would otherwise mask real stalls. The classic workaround ("I bumped the close date, that should count") is prevented by the activity definition. Admins can configure which activity types count toward the stale threshold at the tenant level, with the default covering the standard CRM-event set.

How is the stale threshold configured?

The default: no activity in 10 days on a commit deal, 20 days on best-case, 30 days on pipe. The threshold varies by forecast category because the expected activity cadence differs. Admins can also configure thresholds per stage (Discovery stale at 5 days, Negotiation at 15 days) and per pipeline (new business tighter than enterprise). The configuration lives in the admin surface so sales ops owns the tuning without engineering help.

Can Strkr automatically nudge stale deals?

Yes. A scheduled Flow runs daily. For every rep, it pulls stale deals, sorts by amount, generates AI-drafted nudges, and lands the list in the rep's inbox and in-app notification. The draft is informed by the thread history, the deal stage, the last conversation, and the rep's past tone, so it references the specific prior interaction rather than a generic "just checking in." The rep reads, edits, and sends. The classic "the AI sent something tone-deaf" risk is prevented by human-in-the-loop on every send.

What is the difference between a stale deal and a slipped deal?

A stale deal has stopped moving: no recent activity, no transitions. A slipped deal moved backward in forecast category: it was in commit last week and in best-case or pipe this week. Both are leading indicators of a quarter-close miss, but they signal different problems. Stale signals the rep is not working the deal; slip signals the deal's probability of close has materially dropped. Strkr tracks both independently: the stale-deal surface for inactivity, the slip report for category downgrades. Reps and managers see both signals in their Monday ritual.

Related features

Pair this with...

Sales Pipeline Pipeline Management Deal Tracking Sales Forecast Sales Automation Opportunity Management

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing