Find the right moment to re-engage a closed-lost account

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own closed-lost accounts and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

A closed-lost deal is a company that wasn’t ready to buy at that specific moment — not a company that will never buy. The timing was wrong, the budget wasn’t there, the champion didn’t have enough pull, or a competitor got there first. Any of those conditions can change, and when they do, the account is worth reopening. The problem is nobody is watching for the moment it changes.

This Claude prompt takes your closed-lost accounts, runs each one through Lusha to check what’s changed since the deal closed, and identifies the accounts where a meaningful signal has appeared — a new executive, a funding event, a hiring surge, a competitor intent spike. For each one it drafts a re-engagement message that opens with the specific change at the account, not with a reminder that they said no last year.

The prompt

<context>
I want to find the closed-lost accounts worth re-engaging
right now — the ones where something meaningful has changed
since the deal closed — and draft a re-engagement message
for each one that leads with what's different, not with a
reminder that they said no.

My closed-lost accounts:
[Paste company names, close dates, and close reasons —
or say "use my closed-lost accounts" if your CRM is
connected]

My product: [one sentence — what you sell and the problem
it solves]

Minimum time since close: [e.g. 6 months — accounts closed
more recently than this are excluded]
</context>

<task>
1. SIGNAL SCAN — For each closed-lost account, use Lusha
   to check what has changed since the deal closed:
   - New executive in the buying role
   - Funding event since close date
   - Hiring surge in the target function
   - Competitor intent signal — account researching
     alternatives
   - Tech stack change relevant to your product
   - Leadership change that removes the original
     objection owner

2. CONTACT VERIFICATION — For each account, check the
   status of the original contact:
   - Still in seat? If yes — relationship exists,
     re-engagement is warmer
   - Departed? If yes — new owner, fresh start,
     no institutional memory of the previous no
   - Promoted? If yes — new scope, potentially new
     budget, different conversation than before

3. CLOSE REASON ANALYSIS — Cross-reference the signal
   found with the original close reason:
   - Closed lost: budget — look for funding events
     or headcount growth as budget indicators
   - Closed lost: timing — look for new signals that
     create urgency now
   - Closed lost: competitor — look for intent signals
     suggesting they're evaluating again
   - Closed lost: champion left — check if new champion
     has been identified and is now in seat

4. RE-ENGAGEMENT SCORING — Score each account:
   - Strong: signal directly addresses close reason,
     contact verified, 6+ months since close
   - Moderate: signal present but doesn't directly
     address close reason, or contact has changed
   - Weak: no meaningful signals since close —
     not worth re-engaging yet

5. RANKED OUTPUT — Return accounts ranked by
   re-engagement readiness. For each strong or
   moderate account:
   - Signal found and how it relates to close reason
   - Contact status and verified details
   - Draft re-engagement email that opens with the
     specific change at the account — not a generic
     check-in
   - Suggested subject line
   - Best timing: this week / this month
</task>

What you'll get back

Your closed-lost accounts ranked by re-engagement readiness. For each one worth reopening — the specific signal that changed, the contact status, and a re-engagement email that leads with what’s different now, not with a reminder that they passed.

Accounts scanned: 22  ·  Strong re-engagement signal: 5  ·  Moderate: 7  ·  Not ready yet: 10

Strong re-engagement — act this week

AccountClose reasonMonths since closeSignal foundContact status
[Company A]Budget9Series B closed — $18M✓ Original contact in seat
[Company B]Timing11New VP Sales — 5 weeks in seat⚠ Original contact departed
[Company C]Competitor8Intent score 79 — your category✓ Original contact in seat
[Company D]Champion left14New Head of Sales verified✓ New champion identified
[Company E]Budget7Headcount up 28% — sales function✓ Original contact in seat

[Company A] — full detail

Close reason: Budget — procurement put the deal on hold in Q3 last year.

Signal found: Series B closed last month — $18M raised. Headcount up 14% in the sales function since close date.

ContactTitleTenureEmailDirect dial
R.M.VP of Sales22 monthsr.m@[company].com+1 512 555 ••••

Contact confirmed live via Lusha connector, [date]

Why re-engage now: The deal stalled on budget nine months ago. They just closed a Series B and are scaling the sales team. The budget constraint that killed the deal no longer exists.

Suggested subject line: Congrats on the Series B — worth a conversation now?

Re-engagement email:

R.M. — saw the Series B announcement. Congratulations.

We spoke last year and timing wasn’t right — the budget wasn’t there to move forward. Looks like that’s changed.

You’re scaling the sales team fast. We work with a lot of teams in exactly this position — standing up a new SDR motion and making sure every rep has verified data from day one, not a list that was last touched six months ago.

Worth a 20-minute call this week?


[Company B] — full detail

Close reason: Timing — the VP of Sales who championed the deal left the company before it closed.

Signal found: New VP of Sales joined 5 weeks ago. No institutional memory of the previous evaluation.

ContactTitleTenureEmailDirect dial
J.K.VP of Sales5 weeks ⚑ recent hirej.k@[company].com+1 646 555 ••••

Contact confirmed live via Lusha connector, [date]

Why re-engage now: The original deal died when the champion left. The new VP has no history with your company — this is a clean introduction, not a re-engagement. They’re in their first 30 days and evaluating the inherited stack.

Suggested subject line: New to [Company] — quick intro

Re-engagement email:

J.K. — congrats on the new role.

We worked with your predecessor on a similar project last year — the timing didn’t come together on their end before they moved on.

Given you’re standing up the sales motion fresh, it might be worth a quick conversation. We help teams like yours make sure every rep is working verified contact data from day one — not a stale list inherited from the last regime.

20 minutes this week?


Moderate re-engagement — act this month

7 accounts with signals present but not directly addressing the original close reason. Worth a softer re-engagement touch — a relevant piece of content, a signal-based check-in, or a LinkedIn connection before a cold email.

AccountClose reasonSignalContactRecommended approach
[Company F]CompetitorHeadcount up 12%✓ In seatSignal-based check-in
[Company G]BudgetIntent score 61✓ In seatContent share
[Company H]TimingNew CFO hired✓ In seatWarm introduction via champion

Not ready yet — monitor

10 accounts checked. No meaningful signals found since close date. Original close reasons still likely apply. Check again next quarter — set a reminder to re-run this play in 90 days.

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own closed-lost accounts and connectors to see live results.

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: Claude, Gmail, Lusha

Why use Lusha in Claude

Most closed-lost follow-up fails for one reason: it doesn’t acknowledge why the deal closed. A generic check-in email six months after a lost deal tells the prospect nothing has changed — and they’re right to ignore it. The conversation that actually reopens a deal leads with the specific thing that’s different now. A budget constraint that disappeared because of a funding round. A timing issue that resolved because a new VP just joined and is evaluating everything from scratch. A competitive loss that might reverse because the account is back in research mode on your category.

Lusha’s signal layer is what makes that conversation possible. Every closed-lost account gets checked against the 24 live signal types Lusha tracks — not to find any signal, but to find the signal that directly addresses why the deal closed in the first place. A deal closed on budget needs a funding event or a headcount surge to reopen it. A deal closed because the champion left needs a new decision-maker in seat. A deal lost to a competitor needs an intent signal showing the account is evaluating again. The cross-reference between close reason and signal found is what separates a genuine re-engagement trigger from a generic follow-up excuse.

The contact verification step catches the dynamic that makes closed-lost accounts particularly valuable. When the original contact is still in seat, the re-engagement is warm — there’s an existing relationship and institutional context that doesn’t exist with a cold prospect. When the original contact has departed, the re-engagement is actually a clean introduction — no history of a lost deal, no residual objection, just a new decision-maker evaluating their inherited stack with fresh eyes. Both scenarios are valuable. They just require different messages, and this play writes each one accordingly.

The result isn’t a list of accounts to check in with. It’s a prioritized re-engagement sequence where every message is built around a specific reason the conversation makes sense right now — not a reason that made sense nine months ago.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use.

FAQ

  • How is this different from the Closed-Lost Reengagement Signals play?

    The Closed-Lost Reengagement Signals play surfaces buying signals on closed-lost accounts and returns a signal digest — useful for monitoring a large list of lost deals for any meaningful activity. This play goes further: it cross-references the signal found with the original close reason, scores each account by re-engagement readiness, verifies the current contact, and drafts a re-engagement email built around the specific change at the account. It’s the complete motion from signal to send, not just the signal check.

  • How far back should I go with closed-lost accounts?

    Six months minimum — deals closed more recently than that are usually too fresh to re-engage without it feeling premature. Twelve to eighteen months is the sweet spot for most sales cycles: enough time for circumstances to have changed meaningfully, not so long that the relationship has gone completely cold. For deals closed more than two years ago, treat them as cold prospects rather than re-engagements — the relationship context has faded and a fresh introduction usually works better than referencing a deal that closed under a different leadership team.

  • What if the original close reason wasn't recorded in the CRM?

    Leave that field blank and the play runs the signal scan without the cross-reference step. It still surfaces every signal that has appeared since the account was closed and returns a re-engagement score based on signal strength alone. The output is slightly less precise — without knowing why the deal closed, the play can’t confirm that the signal directly addresses the original objection — but a strong signal on a closed-lost account is still worth acting on even without the close reason context.

  • Should I re-engage through the original contact or find a new one?

    Depends on what the contact verification step finds. If the original contact is still in seat, start there — the existing relationship is an asset and the re-engagement is warmer than a cold introduction. If the original contact has departed, go straight to the new decision-maker and treat it as a fresh introduction. Mentioning that you worked with their predecessor briefly acknowledges the history without leading with it — the new VP doesn’t need to inherit the previous no, and framing it as a fresh conversation gives you a better opening than reopening a dead deal.

  • Can I run this as an automated workflow rather than a manual prompt?

    Yes. Connect Lusha’s API to n8n or Make, trigger the workflow on a quarterly cadence, and have it automatically check your full closed-lost list for new signals. When a signal appears that matches a close reason, it fires a notification with the account details and a draft re-engagement message. The manual prompt version works well for a one-off review of your full closed-lost pipeline. The automated version means you never miss a re-engagement window because you forgot to check. The Lusha Campus plays library has workflow plays for building both approaches.

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.