How to Nudge Stalled Deals
A practical guide to finding deals past their stage dwell time and drafting context-aware follow-ups with approval.
Founder, Task Machine
A stalled-deal nudge is a follow-up sent when an open opportunity has sat in one sales stage longer than that stage normally allows. The job is not to bump every quiet prospect. It is to find the deals where the next step has gone stale, research what changed, and send a useful reason to re-engage.
The work matters because pipeline decay hides inside otherwise healthy CRM totals. The deal still exists, the amount still counts, and the forecast still looks alive, but no next action is moving it forward.
Why stalled deals quietly distort the pipeline
A stale opportunity creates two costs. The first is revenue that may still be recoverable if someone sends the right note. The second is a forecast that overstates reality because inactive deals stay in the same stage.
The usual manual response is a generic "just checking in" email. That is fast, but it gives the buyer no reason to answer. A better nudge ties back to the last conversation, a change in their world, a useful resource, or a concrete decision they need to make.
What the manual process looks like
Done by hand, stalled-deal rescue is a repeated CRM pass:
- Define expected dwell time for each stage.
- Scan open deals for days-in-stage, last activity, next step, owner, amount, and close date.
- Exclude deals that should not be nudged, such as legal review, procurement review, booked meetings, or founder-owned accounts.
- Research what changed since the last contact.
- Draft one follow-up per deal with a reason to reply and one clear question.
- Approve the send, update the deal record, and record whether the nudge worked.
The loop is simple, but it is easy to skip because every deal needs slightly different context.
What an agent can automate
An agent can handle the repetitive CRM and drafting work while keeping the send decision with a person:
- Find the stalled deals. It compares each open deal's days-in-stage against the dwell rules for that stage.
- Respect exclusions. It skips deals listed in the never-nudge rules and flags ambiguous cases for review.
- Research the context. It reads activity history and recent notes so the draft references something real.
- Draft one useful nudge. It avoids empty bumps, asks one question, and proposes a low-friction next step.
- Update the learning log. After approval, it records the stage, angle, and outcome so the team learns which nudges convert.
What stays judgment: every send, every CRM update, and any proposal to change stage or close a deal.
The guardrails that make it safe
The safety boundary is approval per follow-up. The agent drafts and explains the reason for each nudge, then the batch waits in your inbox. Nothing is sent and no CRM record is updated until a person approves it.
The stage dwell document is the second boundary. It states which stages can age how long, which deals are off-limits, and when silence should trigger a stage-change recommendation instead of another email.
Set it up in Task Machine
The Stalled-deal nudger playbook installs the Deal Nudger agent, the recurring workflow, the stage dwell document, the stall-pattern log, the goal, the schedule, and the outreach skills. Setup takes a few minutes. You need a Task Machine workspace and permission to install playbooks (workspace owners have it). CRM access is useful but not required up front; until you authorize it, the agent works from attached deal and activity exports.
1. Find the playbook
Open Playbooks in your workspace and search for "stalled deal", or browse to the Sales category.
2. Preview what it installs
Choose Preview & install to review the agent, workflow, documents, skills, schedule, and CRM service choices before anything is created.
3. Pick your CRM
Click Start setup and pick the CRM the agent should read from: HubSpot or Attio. Pick at least one. Only selected services are installed.
4. Define dwell rules and voice
Fill in the stage dwell expectations, follow-up voice, and deals that should never be nudged. Use specific rules such as "proposal sent: seven days" and "no nudges for legal review".
5. Generate and review
Select Generate customized playbook. Review the generated agent, workflow, dwell document, stall log, schedule, and selected CRM service.
6. Install
Use Install customized playbook to create everything. Follow-ups arrive to authorize the CRM, edit dwell rules, and start the first scan. Each run drafts follow-ups and waits for approval before any message is sent.
What good looks like
- Every nudge has a reason. The draft references a real prior conversation, trigger, or decision point.
- Forecast noise falls. Deals that should close-lost or move stage stop sitting untouched.
- Patterns improve the process. The stall log shows which stages need clearer next steps or different dwell times.
Common questions
Does this send follow-ups automatically? No. Every follow-up waits for approval before sending.
What if a deal has no clear next step? The agent flags that as part of the nudge context. The draft asks one concrete question instead of pretending the next step is known.
Can it update the CRM after a send? Yes, after approval. The update is part of the approved workflow, not an autonomous change.
Should every quiet deal get nudged? No. Deals in legal review, procurement, active meetings, or named-owner accounts should be excluded.