Closed-lost deal resurrection
Research what changed after a deal was closed lost, approve a small reactivation cohort, and learn from replies and reopened pipeline without chasing open stalled deals.
Saves you ~5 h / week
What it installs
Agents 3
-
Resurrection Analyst
Finds closed-lost opportunities whose documented loss condition changed and prepares attributable reactivation and readback packets.
-
Resurrection Reviewer
Independently verifies closed-lost state, changed-condition evidence, contact safety, drafts, and fixed-window outcome claims.
-
Closed-lost deal resurrection Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
Closed-Lost Resurrection Team
An analyst researches reactivation evidence while a reviewer checks eligibility, suppression, drafts, and outcome claims.
Workflows 2
-
Closed-lost resurrection review
Load closed-lost history, research changed conditions, independently verify candidates, draft exact outreach, approve the cohort, and record the fixed result plan.
-
Closed-lost resurrection readback
Wait for a complete fixed window, reconcile replies and downstream pipeline, review confounders, approve bounded learning, and preserve the exact decision.
Documents 2
-
Closed-lost reactivation rules
The approved scope, cooling-off periods, trigger evidence, suppression rules, contact boundaries, and result definitions.
-
Closed-lost resurrection register
The durable record of candidate evidence, approved cohorts, fixed windows, outcomes, confounders, and bounded decisions.
Goals 1
-
Reactivate only when the loss condition changed
Turn closed-lost history into selective, attributable learning without reopening bad-fit deals or automating sends.
Skills 1
-
closed-lost-deal-resurrection
Separates closed-lost opportunities from stalled deals, verifies changed conditions and contacts, drafts approval-gated reactivation, and learns from fixed-window outcomes.
Schedules 2
-
Review closed-lost resurrection candidates
Run the Closed-lost resurrection review on the configured cadence with the Resurrection Analyst assigned. Use only genuinely closed-lost records in the approved lookback, preserve verbatim loss reasons, apply cooling-off and hard exclusions, and research public attributable evidence that directly changes the old constraint. The Resurrection Reviewer independently checks CRM state, sources, contacts, suppression, ownership, drafts, and the fixed outcome plan before human approval. A successful run records an exact approved or rejected cohort, copy, feedback, baseline, final-touch and readback dates, measures, guardrails, and sources. It never handles open stalled deals, sends outreach, enrolls contacts, changes suppression, or reopens CRM work. ## Professional quality control Objective: complete the recurring Closed-lost deal resurrection operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Verify ICP fit, trigger evidence, contact lineage, conversation state, offer and policy limits, and every personalization detail. Outreach must sound like one informed person writing to another, without generic AI phrasing, fake familiarity, filler, hype, manipulative urgency, or reusable template lines disguised as research. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.
-
Read back closed-lost resurrection outcomes
Check approved resurrection cohorts on the configured cadence and start the Closed-lost resurrection readback only after the recorded final touch and complete fixed window. Reconcile human-provided sending evidence and CRM outcomes to exact recipients, keep positive replies primary, preserve downstream pipeline and revenue, separate delivery diagnostics and reputation guardrails, test baseline comparability, and inspect confounders and missing data. The reviewer reproduces material counts before a human approves reuse, keep testing, retire, or unproven for a bounded slice. The schedule never repeats outreach, edits rules, changes suppression, or creates or reopens opportunities. ## Professional quality control Objective: complete the recurring Closed-lost deal resurrection operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Verify ICP fit, trigger evidence, contact lineage, conversation state, offer and policy limits, and every personalization detail. Outreach must sound like one informed person writing to another, without generic AI phrasing, fake familiarity, filler, hype, manipulative urgency, or reusable template lines disguised as research. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.
Tools optional
-
HubSpot
Connects to HubSpot to inspect closed-lost history and read back approved cohort outcomes.
-
Attio
Connects to Attio to inspect closed-lost history and read back approved cohort outcomes.
Folders 1
-
Closed-lost resurrection
Requirements
What this playbook expects to do its job. Task Machine does not verify these — you decide whether your setup is ready.
- Closed-lost deal history — Provide CRM access or exports with closed-lost dates, reasons, contacts, owners, activity, values, and suppression status. Research sources must be public and attributable.
Setup guide
How to Revive Closed-Lost Deals
A practical method for finding closed-lost deals whose original loss condition changed, approving selective outreach, and learning from outcomes.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.
Install Closed-lost deal resurrection 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.