Deal Stuck Revival
Re-engagement messages sent for all qualifying stalled deals. CRM updated: revival attempt logged, next-step task set. Weekly report: deals revived (reply received), deals marked Closed Lost, deals moved to Paused with return date.
Before you start
- CRM with deal stage timestamps and last-activity tracking
- Access to deal history (emails, calls, notes)
- Approved re-engagement message templates by deal stage
- List of deals with no activity in 7+ days (CRM report)
- Last known deal stage and reason for stall (if logged)
- AE notes on deal context and prospect sentiment
The steps
- Pull stalled deal list from CRM — Run CRM report: deals in stages 'Demo Completed', 'Proposal Sent', or 'Negotiation' with last activity > 7 days ago. Export: deal name, primary contact, last stage, last activity date, deal value, and AE owner. Sort by deal value descending — prioritize largest stalled deals.
- Diagnose stall reason for each deal — Review last 5 activities per deal (emails, calls, notes). Categorize stall reason: (a) prospect went silent after proposal, (b) internal champion unresponsive, (c) deal explicitly paused by prospect, (d) objection was raised and not followed up, (e) AE dropped the ball. Log diagnosis on deal record. Skip category (c) if pause reason was specified — respect the timeline.
- Craft re-engagement message by stall type — Category (a) silent-after-proposal: lead with a new data point or case study relevant to their stated pain. Category (b) champion unresponsive: try alternate contact at same company via LinkedIn. Category (d) unresolved objection: address the objection directly and propose a call to work through it. Message length: 4-6 sentences max. No apologies for 'bothering them.' No generic 'checking in.'
- Research new trigger or hook for outreach — Check prospect company for: new job postings (signals growth or pain), press releases, LinkedIn posts by champion, funding announcements, competitor moves. Use one genuine trigger as the hook. If no trigger found, use a relevant customer story instead. Do not reach out without a hook — it reads as desperation.
- Send re-engagement messages and log — Send messages (email or LinkedIn depending on last-used channel). Send from AE's address — not a sequence alias. Log outreach in CRM as 'Revival Attempt 1'. Set 5-day follow-up task for non-responders. For deals > $25k ACV, have AE review before sending.
- Handle responses and re-activate pipeline — Positive response: book next meeting immediately, update deal stage, notify AE. Prospect says 'not now / Q3': set CRM reminder for Q3 start, update deal stage to 'Paused — Q3', log reason. No response after two attempts (10 days): move to 'Closed Lost — No Response', tag for 90-day recheck list.
If it goes wrong
Re-engagement emails ignored by entire company
Try LinkedIn InMail to a different stakeholder (CFO or COO if champion was VP-level). Reference a mutual connection if one exists. One different channel attempt before marking lost.
AE objects that deal is 'still active' despite no activity
Require AE to log a note with expected next activity date. Auto-flag again if still no activity 5 days past that date. Clarifies ownership without conflict.
Wrong stall-reason diagnosis leads to off-target message
Add required 'last-stall-reason' field in CRM that AE fills at end of each call. Reduces diagnosis guesswork. Audit 20% of diagnoses monthly against AE recollection.
All OpenLabor playbooks