Closed lost revival
Goes back to deals lost 90 days ago, checks what has changed at the account, and reopens the conversation where the reason for losing may have expired.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon5 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Find losses worth revisiting
Coming soonBlu builds a step
- 2
Write two revival emails
Coming soonBlu builds a step
- 3
Check what changed first
Coming soonBlu builds a step
- 4
Send at day 0 and day 14
Coming soonBlu builds a step
- 5
See what comes back to life
Coming soonBlu builds a step
About this recipe
When to use it
Most closed-lost deals never get revisited, even though budgets, leadership, and priorities change within a year. This re-engages them on a schedule instead of leaving them to rot in the CRM.
What it delivers
Revives closed-lost deals 90 days after loss with a fresh re-evaluation outreach, on the logic that context has likely changed (new initiatives, leadership, budget cycle). Typical revival rates run 5-10%, at low outreach cost.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Goes back to deals lost 90 days ago, checks what has changed at the account, and reopens the conversation where the reason for losing may have expired.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Find losses worth revisitingBuild a segment 'Closed-lost revival candidates' capturing deals where Deal lost event fired 90-180 days ago AND lost_reason is NOT 'wrong-fit' or 'competitor-won-firm-commitment' (those won't revive). Includes deals lost to: timing, budget, no-decision, internal-resourcing, postponed. Excludes accounts that have entered closed-lost more than twice (3-strikes rule: stop pestering).
- 02Write two revival emailsGenerate 2-touch revival email content. Touch 1 (Day 0): 'It's been a few months: wanted to check in. Last time we talked, [original_lost_reason]. Has anything changed?' Reference specific prior conversation context. Soft re-open, not a sales pitch. Touch 2 (Day 14, if no reply): share a relevant product update or customer story from a similar account that addresses their original objection. Send-from: the original AE owner. Tone: warm, low-pressure, acknowledging the prior 'no'. Use the result of "Find losses worth revisiting".
- 03Check what changed firstCreate a workflow firing daily for newly-eligible revival candidates. Step sequence: (1) refresh account enrichment (champion still there? new leadership? funding announced? product launched?); (2) IF significant change detected (new champion-role hire, funding round, etc.): create urgent AE task to manually reach out; ELSE trigger the standard 2-touch revival journey. Track responses and any new meeting bookings as revival_signal events on the original closed-lost deal record. Use the result of "Find losses worth revisiting", "Write two revival emails".
- 04Send at day 0 and day 14Build a 2-touch journey triggered by the revival workflow. Touch 1 at Day 0, Touch 2 at Day 14 (skipped if user replies or books meeting). Audience: the original deal's primary contact. Exit on: Meeting scheduled (revival success: open new deal), email_replied (warm handoff to AE), unsubscribe, or 30-day max duration. Use the result of "Find losses worth revisiting", "Write two revival emails", "Check what changed first".
- 05See what comes back to lifeCompose a revival performance dashboard: closed-lost deals entering revival per month, reply rate to revival outreach, meeting-booked rate from revival, revived-deal-to-win rate (final conversion), and ARR resurrected this quarter from revival pipeline. Break down by original lost_reason: which lost-reasons most often turn into revivals (informs sales coaching on when 'no' was actually 'not yet'). Use the result of "Find losses worth revisiting", "Write two revival emails", "Check what changed first", "Send at day 0 and day 14".
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /closed-lost-revival in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 