Stalled-deal nudger
Every few days an agent finds deals sitting in a stage past its expected dwell time, checks what changed since the last contact, and drafts a tailored follow-up per stalled deal — then lands one approval where you approve each follow-up before it is sent and the deal is updated.
What it installs
Agents 1
-
Deal Rescue Agent
Keeps deals from dying quietly by spotting stage stalls early and drafting context-aware follow-ups for human approval.
Workflows 1
-
Stalled-deal nudge cycle
Scan for stage stalls, research what changed, draft per-deal follow-ups, approve each send, then send and update the records.
Documents 2
-
Stage dwell times & nudge rules
How long a deal may sit in each stage before it counts as stalled, and the rules every follow-up must respect.
-
Stall patterns & nudge outcomes
A living log of which stages stall most, which nudge angles get replies, and which convert — updated after each cycle.
Goals 1
-
No deal stalls silently
Every deal past its stage's expected dwell time gets a context-aware nudge or a deliberate human decision, every cycle.
Skills 3
-
stalled-deal-detection
Flag stuck, stale, overdue, and single-threaded deals, separate genuinely stalled deals from naturally slow ones, and rank nudge candidates by close date, deal size, stage, activity, and risk. Adapted from anthropics/knowledge-work-plugins/pipeline-review.
-
context-aware-nudging
Research first, rank hooks — trigger events over mutual connections over role-based pain — and draft AIDA follow-ups that give a dark deal a new reason to reconnect, on a 3-5 touch cadence where every touch adds a new angle; drafts only. Adapted from anthropics/knowledge-work-plugins/draft-outreach. Adapted from coreyhaines31/marketingskills/cold-email (sequence guidance).
-
stall-pattern-tracking
Record every cycle's stall counts and nudge outcomes in the living document, and surface repeat patterns — which stages stall, which nudge angles convert — with evidence.
Schedules 1
-
Stalled-deal sweep
Scans for stalled deals and drafts follow-ups every two to three days.
Connected services pick at least 1 of 2
-
HubSpot
Connects to HubSpot so the agent can read deal stages and activity, spot stalled deals, and update records after an approved send.
-
Attio
Connects to Attio so the agent can read deal stages and activity, spot stalled deals, and update records after an approved send.
Folders 1
-
Stalled deals
Requirements
What this playbook expects to do its job. Task Machine does not verify these — you decide whether your setup is ready.
- Browser access to your CRM — The agent works in your CRM through its web interface in your browser to read deal stages, activity history, and contacts, and pauses for your approval before any follow-up is sent or any record is updated. Until you connect it, it works from attached exports (deal and activity CSVs) and the relevant documents.
Setup guide
How to Nudge Stalled Deals
A practical guide to finding deals past their stage dwell time and drafting context-aware follow-ups with approval.
Read the setup guideInstall Stalled-deal nudger and run it with approvals.
Join the waitlist and we will send early access when the first private beta spots open.
Private beta. We invite teams in batches and never share your email.