The problem this solves
Closed-lost is the most mispriced asset in a CRM. These are companies that already knew you, took meetings, and said a version of 'not now' - and 'not now' expires. Budgets refresh, blockers change jobs, and the initiative that was postponed gets funded. But no one systematically watches for expiry. The deals sit in a graveyard stage, and re-engagement happens only when a rep happens to remember an account at the right moment, which is to say rarely and by luck.
The reason the graveyard stays unworked is that resurrection requires evidence. A generic 'checking back in' email re-earns none of the ground lost in the first evaluation; the win-back that lands is the one that names a change - new funding, a new leader, a hiring wave - and connects it to the conversation you already had. Checking every old deal for such changes is a research project across the whole lost pipeline, and it never makes anyone's sprint.
There is also a discipline problem: without a trigger requirement, win-back campaigns degrade into pestering the same unmoved accounts on a timer. The filter that says 'only the ones where something actually changed' is what separates a revival motion from a nuisance. Enforcing that filter across a whole lost pipeline is agent work, because it means rechecking every account every time.
How the mission runs
- Pull the graveyard from HubSpot. The agent retrieves your closed-lost deals older than six months from HubSpot, along with the context each record holds - when it was lost, at what stage, and any recorded reason. The old context matters because the eventual sequence gets to acknowledge the earlier conversation.
- Recheck every company for change. Each lost account is checked against Firmographics for new funding and leadership changes, and against Hiring Data for fresh hiring momentum. The agent looks specifically for changes postdating the lost date, because a trigger that predates the loss is old news the deal already priced in.
- Keep only the real triggers. Accounts with no meaningful change are set aside for a future pass rather than forced into the campaign. The survivors each carry a named, dated trigger, and the cut is deliberate: a smaller list where every entry has a reason outperforms a big list running on hope.
- Draft the trigger-grounded sequences. For each surviving account, the agent drafts a win-back sequence that opens with the change - the raise, the new leader, the hiring wave - and bridges to the prior conversation. The copy assumes familiarity without presuming warmth, which is the correct register for a re-approach.
- Stage the sequences into ActiveCampaign. Sequences are created in ActiveCampaign as drafts with contacts attached, staged for your review before anything activates. You see which accounts made the cut, what trigger each carries, and the exact copy, and you launch deliberately when the batch reads right.
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 win-back campaign staged in ActiveCampaign: every closed-lost account older than six months where something real has changed since the loss, each with its named trigger and a sequence drafted around it. Accounts without a trigger are reported but excluded, so the campaign contains only earned re-approaches. Review the batch, adjust any copy, and activate on your own call.
Make it yours
- Narrow the trigger set to funding only for a budget-timed revival, or to leadership changes only when your losses traced to a blocker.
- Shorten the lookback to deals lost 3 to 12 months ago, where memory of your product is freshest and the re-open is easiest.
- Run the mission quarterly as a standing ritual, so each quarter's newly expired 'not now' accounts get exactly one evidence-based re-approach at the right moment.
Frequently asked questions
What counts as a trigger worth reviving on?
A material change postdating the loss: a funding round, a new executive in the buying chain, or a hiring pattern indicating the relevant team is growing. Each surviving account names its trigger and date, so during review you can judge whether the evidence clears your own bar before launch.
Will this annoy accounts that told us no?
The trigger requirement exists to prevent exactly that. Accounts where nothing changed are excluded, and the accounts that remain receive a message about their new circumstances rather than a timer-based nudge. A re-approach grounded in a real change reads as attentiveness, and the review gate lets you drop any account that feels wrong.
Does the mission change my HubSpot records?
It reads from HubSpot; the campaign is staged in ActiveCampaign. If you want the outcome mirrored back - a note or property marking each revived account - ask for it, and that write goes through the standard review gate like any other CRM change.