--- name: stalled-deal-revival description: Finds open deals in your CRM that have gone idle, diagnoses the likely stall reason from engagement history, and drafts a tailored revival email for each one. Use when the user asks to "revive stalled deals", "which deals went quiet", "what's gone cold", "re-engage my dead deals", or wants outreach drafted for idle pipeline. license: MIT compatibility: Requires a connected CRM. Read-only — drafts outreach, no writes. metadata: author: Builder.org version: 2.0.0 persona: Strategic Steve, Operator Owen rave: R4 A4 V3 E3 category: crm --- # Stalled Deal Revival ## What it does Catches deals that have quietly gone idle, works out why from the history, and drafts the specific revival move for each: the right play for the right stall, written and ready to send. This is revenue protection for the deals that would otherwise slip away without anyone deciding to let them. ## When to use - "Revive stalled deals", "which deals went quiet", "what's gone cold this month". - "Re-engage my dead deals", or a recurring monthly revival pass. - Not for deals merely aging in a stage with activity still happening; that early-warning job is `deal-stage-nudges`. This skill takes over when the conversation itself has died. ## Inputs None required. Optional: idle-day threshold (default 10), owner, pipeline, minimum deal value. Works with any CRM your assistant can read (HubSpot, Salesforce, or similar); it only needs deals, stages, and engagements. ## The bar - Every draft is specific to why that deal stalled. A generic "just checking in" is the anti-deliverable; if the skill cannot beat it, it should say so. - Diagnoses are labeled as best guesses with their evidence, never stated as fact. - Drafts are short: 60 to 100 words. A revival email is a door reopened, not a proposal resent. - Each deal gets one play. The rep can improvise a second; the skill commits to its best. ## Workflow 1. **Find idle deals.** Open deals with no logged engagement in 10+ days (default; a working deal usually has a pulse inside two weeks). Sort by value times stage proximity to close, because a quiet Negotiation deal is a house fire and a quiet Discovery deal is a draft. 2. **Diagnose each stall** from the last few engagements: no reply to our last message, went dark after pricing, went dark after demo, champion changed or left, they promised an internal step that never came back, or we dropped the last ball ourselves. Name the evidence. 3. **Pick the play to match.** No reply: change the angle, not the volume. Dark after pricing: reframe value or offer the smaller start. Dark after demo: send the one artifact the demo was missing. Lost champion: multi-thread to a named second contact. Their internal step overdue: the polite deadline note. We dropped it: own it plainly and restart. 4. **Draft the email** for each deal: references the real last interaction by date or content, one idea, one easy ask. Include a subject line. If a breakup email is the honest play (three prior touches ignored), write that instead and say why. 5. **Output the ranked revival list**, highest cost-of-loss first, diagnosis and draft together. ## Output ``` ## Stalled deal revival for [date] 1. **[Deal] · $[amount]** · [stage], idle [N] days Diagnosis: [best guess + evidence] Play: [the revival move and why it fits] Draft: Subject: [subject] [60-100 word body] 2. ... ``` ## Worked example ``` Fictional example. Never reuse these names or numbers in real output. ## Stalled deal revival for March 3 1. **Brightpath Staffing onboarding suite · $44k** · Proposal, idle 19 days Diagnosis: went dark after pricing; Dana opened the proposal twice on Feb 12 (tracked), replied to nothing since. Play: reframe around the smaller start. Silence after pricing usually means the number, not the need. Draft: Subject: a smaller first step Dana, the proposal I sent covers the full rollout, and rereading it, that might be more commitment than the first quarter needs. Most teams your size start with credentialing only, prove the turnaround gain in 60 days, then expand. Happy to send a one-page version of that scope. Worth a look? 2. **Meridian Freight TMS rollout · $48k** · Decision, idle 12 days Diagnosis: champion went quiet after her CFO joined the Feb 18 call; likely an internal budget conversation we are not in. Play: arm the champion instead of chasing her. Send the artifact her CFO needs. Draft: Subject: the payback math, one page Elena, guessing the conversation moved to Rob's desk after our last call. Here is the one-page payback model with your Columbus hub volumes in it, in case it helps that conversation go faster. If the timing has shifted, tell me and I will stop guessing. ``` ## Never - Never send-style a "just checking in" or "bumping this to the top of your inbox" draft. If there is nothing new to say, the play is a breakup email or an artifact, not a nudge with no content. - Never state a diagnosis as fact. The rep knows things the CRM does not; phrase it so they can correct it. - Never draft to a contact who asked to be left alone or whose deal is marked lost. Surface those separately as "do not revive". - Never write anything to the CRM. Drafts and diagnoses are handed to the rep; sending and logging are theirs. ## Recovery - History too thin to diagnose: say so, and default to the two safest plays: a value-add artifact or an honest "did this fall off your list?" note. - The last message was ours and it was bad (vague, long, no ask): name that gently as the likely stall and draft the sharper replacement rather than a follow-up to it. - Champion left the company: flag the deal for re-mapping, draft the intro request to the most plausible successor, and mark confidence low. - Fifty deals qualify: cap the list at ten by cost-of-loss, say how many wait behind them, and suggest raising the minimum value or tightening the threshold for the next run.