The problem this solves
The deals your team already lost were the most expensive leads you ever generated: sourced, worked, met, demoed, and priced before they said no. Everything about them is known except the one thing that changes - their circumstances. Six months later some have raised money, hired a new marketing leader, or started staffing the exact team your product serves, and the 'no' that was true then is stale now. Nobody notices, because closed-lost is where CRM attention goes to end.
Reviving the whole graveyard indiscriminately is the classic mistake. Most lost deals are still correctly lost, and a blanket 'thought I'd check back in' campaign to all of them re-earns the no while training prospects that your follow-up is noise. The play only works with a filter: revive exclusively where something concrete changed, and open with the change itself, so the email reads as attention rather than a timer that expired.
The mechanics are what keep it theoretical. Cross-checking every old deal against funding, leadership, and hiring data, then writing per-account sequences that reference both the trigger and the prior relationship, then loading it all into the sending tool - the chain is a week of work spanning three systems, which is why the graveyard stays a graveyard. An agent runs the same chain as one mission.
How the mission runs
- Pull closed-lost from HubSpot. The agent retrieves deals marked closed-lost more than six months ago, with each record's context - the timing, the stage reached, and any loss reason logged. Deals lost recently are excluded on purpose; a no from last quarter has not had time to expire.
- Check each company for a fresh trigger. Every lost account is checked against Firmographics for funding rounds and leadership changes, and against Hiring Data for new hiring momentum - specifically changes dated after the loss. The trigger must postdate the no, because that is what makes the revival a new conversation.
- Keep only the triggered accounts. Accounts without a qualifying change are set aside, and the mission reports how the graveyard split. The surviving list is typically a fraction of the total, and that is the design: every account in the campaign has an evidence-based reason to be re-approached this month.
- Write the trigger-referencing win-back sequence. For each survivor, the agent drafts a sequence that opens with their specific change - the raise, the new leader, the hiring wave - and connects it to the earlier evaluation without re-litigating it. The tone assumes a shared history and a changed situation, which is exactly the truth.
- Load into Lemlist for your review. The campaign is assembled in Lemlist with contacts and per-account sequences attached, staged rather than launched. The summary shows each account's trigger beside its copy, so review is a scan down a list of reasons, and launch is your call.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A staged Lemlist campaign containing only the resurrectable fraction of your closed-lost pipeline: each account carrying a named, dated trigger that postdates its loss, with a win-back sequence that opens on the change and acknowledges the prior conversation. The mission summary shows how the full graveyard split between triggered and dormant, so you know both what you are reviving and what remains asleep.
Make it yours
- Restrict triggers to new leadership only, the cleanest revival when the original loss traced to a champion who blocked or left.
- Run it quarterly so each quarter's newly expired losses get checked once, keeping any single account from being revisited repeatedly.
- Route the two or three highest-value triggered accounts to a rep for personal outreach and let the campaign carry the rest.
Frequently asked questions
Why six months as the lookback threshold?
It is roughly how long a considered no takes to expire - budgets cycle, initiatives resurface, and the person who said no may have moved. The threshold is adjustable in the prompt; the principle is that revival needs both elapsed time and a concrete change, and the mission enforces both.
Does the sequence mention the old deal explicitly?
It acknowledges the prior conversation without re-arguing it - the register is 'things have changed on your side since we spoke', anchored to the trigger. During review in Lemlist you can tune how directly each sequence references the history, since accounts differ in how the loss ended.
What happens to the accounts with no trigger?
They stay untouched and unlisted in the campaign, reported only as a count. They will be rechecked on the next run, and some will have developed triggers by then. Sending them anything now would spend goodwill on accounts where nothing has changed, which the filter exists to prevent.