35% off all annual plans Lusha summer sale - limited time only

Claim discount

Surface buying signals on closed-lost accounts

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: Claude ▪ Lusha
Type: Prompt

A Claude prompt that takes a closed-lost account list and scans each one for a re-engagement trigger fired since the deal was lost. A new CRO is the strongest reset signal in B2B. A fresh funding round is the second. A product launch into a new category is the third. The prompt isolates the accounts where one of those events has happened, and parks the accounts where nothing has changed for the next monthly scan.

Closed-lost re-engagement on a timer is random. Closed-lost re-engagement on a trigger is the conversation the buyer is now ready to have.

Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just paste the closed-lost list and run.

Images on this webpage are for illustrative purposes only. Any named individuals shown in live demo outputs are real, with last names abbreviated for privacy.

The prompt

Open in Claude Open in ChatGPT 
<context>
Closed-lost accounts from the last [WINDOW, e.g. 12-18 months].
Find the subset where a real re-engagement trigger has fired since the deal closed: events that change the buying context enough to warrant a fresh conversation.

For each closed-lost account, I'll provide:
- Account name or domain
- Close-lost date
- Primary objection or loss reason
</context>

<task>
1. Closed-lost list (one row per account, with close date and loss reason):
   [PASTE LIST]
2. For each account, use Lusha's signals layer to scan for re-engagement triggers fired AFTER the close-lost date:
   - New leadership in the buying group function (CRO, CTO, CMO, COO, CSO; anyone above the prior contact's manager)
   - Funding events (round, IPO, M&A; anything that resets budget conversations)
   - Strategic investments (signals direction of spend)
   - Major product launches (new category entry, platform repositioning)
   - Hiring surges in the function the rep originally sold into
3. For each triggered account, output:
   - Account name and close-lost date
   - Original loss reason
   - Trigger event(s) and date
   - Re-engagement angle: a one-sentence reframe tying the trigger back to the original objection
   - Recommended outreach contact (new leader if leadership changed; original contact if no leadership change)
4. Park accounts where no trigger has fired since the close-lost date. List them at the bottom for the next monthly scan.
5. Rank the triggered accounts: leadership changes first (highest signal), then funding events, then product launches, then hiring surges.
</task>

<constraints>
- A trigger must have fired AFTER the close-lost date. Events from before the deal was lost don't count. The buyer already knew about them.
- New leadership in the buying group is the strongest single trigger. A new CRO at an account lost on sales-team objections is a near-mandatory re-engagement.
- Do not invent loss reasons or fabricate signal events.
- Park accounts with no trigger fired. They go to next month's scan. Do not force outreach.
</constraints>

What you'll get back

Input: 6-account closed-lost list across enterprise SaaS (cloud data, cloud security, productivity, AI infrastructure, edge platform, database). Loss reasons range from product gaps to pricing pushback to sales-process friction. Close-lost dates span the last 9-15 months.

Output: 4 accounts with strong re-engagement triggers fired, 2 parked for next month’s scan. Below is the real result from running the prompt against the live Lusha connector.

Triggered accounts (re-engage now)

[Database SaaS] — TRIGGER: NEW CRO

  • Close-lost: 11 months ago, loss reason “sales engagement misalignment”
  • Trigger: Ryan M. appointed Chief Revenue Officer, effective April 27, 2026 — announced March 24, hired to “support next phase of growth” — article
  • Re-engagement angle: A new CRO inside their first 90 days has a fresh mandate, no allegiance to predecessor vendor decisions, and is openly scoped to grow revenue. The original objection is now structurally outdated.
  • Recommended contact: Ryan M. directly (or his incoming team)

[Cloud data platform] — TRIGGER: NEW CRO + NEW CSTO + 3 ACQUISITIONS

  • Close-lost: 14 months ago, loss reason “stack-fit concerns vs incumbent”
  • Trigger: New CRO (Jonathan B., March 31, 2026), brand-new Chief Security & Trust Officer (Mayank U., April 1, 2026), three acquisitions (an agentic AI data engineering startup, a data catalog startup, an AI observability startup) — all AI-adjacent
  • Re-engagement angle: The “stack fit” the rep lost on 14 months ago has materially changed — three acquisitions plus the new CSTO role mean the platform is publicly rebuilding the security + AI data layer. The architecture the rep was selling against doesn’t exist in the same form anymore.
  • Recommended contact: New CSTO if the rep sold security; new CRO’s team if the rep sold GTM tooling

[Cloud security SaaS] — TRIGGER: $5.8B FUNDING + NEW EMEA + ME LEADERSHIP

  • Close-lost: 10 months ago, loss reason “no budget approved”
  • Trigger: $5.8B valuation funding round Dec 2025 (CapitalG-led), new VP of EMEA Mark C. (Feb 2026), new Head of Middle East Fred C. (Jan 2026 — Dubai office opening)
  • Re-engagement angle: The budget objection that closed the deal 10 months ago is gone. The lead-investor-backed round resets the conversation. EMEA and ME expansion creates new buying centers the original loss didn’t cover.
  • Recommended contact: Mark C. or Fred C. if territory expansion is the angle; original contact if rep was already with a US team

[AI infrastructure SaaS] — TRIGGER: $1B FUNDING ROUND IN NEGOTIATION

  • Close-lost: 9 months ago, loss reason “stage too early — wait for Series B”
  • Trigger: $1B funding round currently in negotiation per March 6, 2026 reporting, valuation eyed at $7.5B
  • Re-engagement angle: The original “too early” objection is structurally resolved. A $1B round closes the conversation about budget appetite. The rep should re-engage at the front edge of the round announcement, not after.
  • Recommended contact: Original contact (no leadership change) plus any new VP-level hires arriving with the new round

Parked accounts (next month)

  • [Productivity SaaS] — Sales hiring surge fired (+204%) but loss reason was a product-fit issue not a sales-engagement issue. Hiring surge alone doesn’t reset a product-fit objection. Park.
  • [Edge/CDN platform] — Hiring surges fired across Sales, Operations, Engineering, but no leadership change, no funding event, no category-resetting product launch. Park for next month’s scan.

51 credits consumed for the full multi-signal scan across 6 closed-lost accounts. The triggered subset is now ready for prioritized outreach. Parked accounts return on the next monthly run.

Why use Lusha in Claude

Closed-lost is the most under-mined pipeline asset in B2B. The rep already had a buying conversation. The original loss reason is documented. The buying group is known. The only thing missing is the trigger that changes the buying context enough to make the second conversation worth having. Three things shift when signal scanning runs across the closed-lost list instead of a calendar-based re-engagement timer.

New leadership is the strongest reset signal. A new CRO, CTO, CMO, or CSTO has roughly 90 days to rewrite the function’s vendor list. They are looking for “what’s the right tool for this team going forward” — a question the rep who lost the deal a year ago is well-positioned to re-open. The database SaaS row in the demo above is the textbook case: incoming CRO with a public growth mandate at an account lost on sales-engagement friction. The objection is structurally outdated the moment the new CRO walks in.

Funding events reset budget objections specifically. An account lost on “no budget” or “wait for the next funding round” is exactly the account where a fresh funding announcement is the most surgical re-engagement trigger. The rep references the round in the opener, names the budget cycle implied, and walks back into the conversation with a closed objection. The AI infrastructure SaaS’s $1B in-negotiation round at a +9-month closed-lost is the cleanest example in the demo.

Product launches reset stack-fit objections. An account lost on “your product doesn’t integrate with X” is the account where the launch of an X integration matters most. Same for category expansion, repositioning, and major platform updates. The trigger has to be material — a routine point-release usually doesn’t reset a stack-fit objection. A new product category often does.

The parked accounts are part of the strategy. An account where nothing has changed since the deal was lost should not be force-re-engaged. The signal layer answers the question “should the rep call?” and trusting the answer when it’s “not yet” is what makes the trigger-based approach work over time. Random monthly re-engagement burns goodwill. Trigger-based re-engagement compounds it.

Data drawn from Lusha’s signals layer, built on 300M+ verified contacts and millions of company records under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.

FAQ

  • How do I match the signal to the original loss reason?

    The prompt asks for the loss reason on each row of input. The output ties the trigger back to that reason — a new CRO matches a sales-engagement loss, a funding round matches a budget loss, a product launch matches a stack-fit loss. Without the loss reason, the prompt still returns triggered accounts but cannot suggest the angle. Pasting loss reasons makes the output materially sharper.

  • What if the original buying contact has also left?

    The prompt surfaces this case. When the original contact has moved companies (caught by the contact-side signal layer), the row gets dual context — the original account has new leadership AND the rep’s known champion is now at a new account. Both rows go back into pipeline as separate re-engagement opportunities.

  • How often should I run this?

    Monthly is the right rhythm. Closed-lost re-engagement on a weekly cadence creates churn. Monthly aligns with the typical 30-60 day signal indexing latency and matches how new leadership mandates actually unfold (week 4-12 is the right outreach window for a new CRO).

  • Does the prompt cover M&A as a trigger?

    Yes — when an account gets acquired or acquires another company, the buying context changes materially. Acquired companies often re-evaluate every vendor contract within 12 months of close. Acquirers often consolidate stacks. Both are first-line re-engagement triggers and the prompt surfaces them.

  • What's the minimum window between close-lost date and re-engagement?

    The prompt does not enforce a minimum — it scans for triggers regardless of how recent the loss was. In practice, accounts closed-lost less than 3 months ago without a hard structural trigger (CRO, M&A, IPO) usually aren’t worth re-engaging — the rep should wait. The prompt surfaces the signal; the rep makes the call.

  • Can I combine this with the buying group prompt?

    Yes. Identify the triggered accounts first, then run the buying group prompt on each to pull the verified decision-makers — especially the new leaders the trigger surfaced. The combined workflow (closed-lost signal scan → buying group at triggered accounts → Prospect-to-Outreach Skill for drafts) is the most leveraged re-engagement motion in the gallery.

Related Prompts

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.

Get free access Read the Docs