Revive a stuck deal with a fresh signal trigger
A Claude prompt that takes a stuck deal — opportunity that went quiet after a clear next step — and scans the prospect company for signal triggers fired since the last touch. New CRO arrived. Fresh funding closed. Acquisition announced. Product launched into a new category. The prompt maps each trigger to a specific re-engagement hook the AE can use as the opener, replacing the dead-letter “just checking in” with a real reason to re-open the conversation.
A revival message tied to a real event lands. A generic follow-up reads as desperation. Built for AEs working active pipeline and Sales Managers running deal reviews where multiple deals need pulse checks.
Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just name the stuck deal 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
<context>
I have a stuck deal — opportunity went quiet after the last meaningful touch. I want to re-engage but "checking in" emails read as desperation. I need a fresh signal-based hook to legitimately re-open the conversation.
My stuck deal:
- Prospect company / domain: [COMPANY]
- Primary contact at the prospect: [NAME, TITLE]
- Last meaningful touch date: [DATE]
- Stage where deal stalled: [Discovery / Proposal / Negotiation / Other]
- What I was selling: [PRODUCT / SOLUTION]
- Original next step that didn't happen: [WHAT WAS SUPPOSED TO HAPPEN NEXT]
</context>
<task>
1. Use Lusha's signals layer to scan the prospect company for events fired since the last meaningful touch:
- Leadership events (executive hires, promotions, departures in the buying group or above)
- Strategic moves (M&A, funding rounds, strategic investments)
- Product activity (launches, integrations, category expansion)
- Hiring surges (in the function I sell into, or adjacent functions)
- Market signals (web traffic shifts, partnerships, recognition events)
2. For each fired signal, map a specific re-engagement angle:
- What changed because of the signal
- Why it matters to my deal's product or solution
- The one-line email opener tied to the signal
3. Rank the signals by re-engagement value:
- STRONG — leadership change in buying group, fresh funding, or major acquisition (the conversation has structurally changed)
- MEDIUM — product launch in adjacent area, hiring surge in target function (relevant context, indirect connection)
- WEAK — minor news, isolated departures outside buying group (color, not catalyst)
4. Surface the recommended primary hook plus 1-2 backup angles. The primary hook is the strongest single signal mapped to the cleanest re-engagement reason.
5. If the original primary contact has departed or been promoted, flag this — the right move may not be re-engaging the original person but rather re-introducing the value to the new owner.
</task>
<constraints>
- The signal must have fired AFTER the last meaningful touch date. Events that happened before the stall aren't fresh triggers — the prospect already knew about them.
- The hook references the signal, not the silence. Never write "I noticed we haven't spoken in a while" as the opener.
- Do not invent signals or fabricate hooks. Surface only what Lusha returns.
- If no signal has fired in the window, surface that honestly. A genuinely quiet account may need a different revival approach (executive sponsor escalation, breakup email, or a wait-and-watch period).
</constraints>What you'll get back
Input: Stuck deal — Snowflake. Primary contact — VP-level RevOps leader. Last meaningful touch — Q4 2025. Stage — Proposal. Product being sold — sales productivity platform. Original next step — security and procurement review that never started.
Output: 7 fresh signal triggers fired since the last touch, 3 ranked STRONG, 2 MEDIUM, 2 WEAK. Below is the real result from running the prompt against the live Lusha connector.
Strong re-engagement triggers
1. New Chief Revenue Officer — Jonathan B., March 31, 2026 (STRONG)
- What changed: Snowflake’s GTM function now has a new top leader. The previous CRO Mike G. left for personal reasons. Jonathan was an internal hire and is inside his first-90-days mandate window.
- Why it matters: The original deal stalled during procurement review. A new CRO often re-evaluates every active GTM vendor in the first quarter — including the stuck deal in our pipeline. The conversation is now structurally different than when the deal stalled.
- One-line opener: “Saw the CRO appointment in March — given Jonathan’s mandate to scope the next phase of GTM, wanted to share where the conversation left off and see if a fresh look makes sense now.”
2. Three AI-related acquisitions — TensorStax, Select Star, Observe (STRONG)
- What changed: Snowflake announced three acquisitions between November 2025 and February 2026, all in the AI data infrastructure space. The company is publicly building toward an agentic AI data layer.
- Why it matters: A sales productivity platform that operates inside this AI direction has new relevance — Snowflake’s sales team will be selling into a different positioning, with different competitive context. The original deal’s value proposition is materially sharper post-acquisition.
- One-line opener: “The TensorStax acquisition and the agentic AI data layer direction changes what a sales productivity platform needs to do for Snowflake’s GTM team — wanted to revisit the conversation in that context.”
3. Brand-new Chief Security & Trust Officer — Mayank U., April 1, 2026 (STRONG)
- What changed: Snowflake created a new C-suite role for Security and Trust, hired externally. The role didn’t exist when the original deal stalled.
- Why it matters: The original deal stalled at security and procurement review. There’s now a dedicated C-suite owner for that review process — a clean reason to re-introduce the security positioning to the right named owner.
- One-line opener: “The new CSTO role at Snowflake creates a clear owner for the security review the deal was waiting on — happy to coordinate a brief that goes to Mayank’s team directly.”
Medium re-engagement triggers
4. Operations hiring surge +60%, April 2026 (MEDIUM)
- What changed: Snowflake’s Operations function is hiring at 60% above baseline.
- Why it matters: Operations growth often signals broader process and tooling investment. Adjacent to the GTM tooling sale but not the primary buying group.
- One-line opener: “Saw the Operations team is scaling fast — when the timing’s right, would be valuable to revisit where our conversation left off in light of the broader operational build-out.”
5. Cortex Code Agent SDK launch, April 21, 2026 (MEDIUM)
- What changed: Snowflake shipped a new agentic AI product for enterprise app integration.
- Why it matters: Connects to the broader agentic direction, but adjacent to the original deal’s specific value prop.
- One-line opener: “Cortex Code Agent SDK fits the agentic direction we discussed last time — the GTM tooling conversation has new context worth a fresh look.”
Weak signals (background, not lead)
- Senior departures (Caroline V. to Fortinet, Bryan A. to AtScale) — useful color but not a re-engagement reason on their own
- +29% sales hiring surge — relevant context, but covered in the CRO trigger as a derived signal
Recommended approach
The primary hook is the new CRO appointment (Trigger 1). It is the cleanest re-engagement reason because it structurally changes the buying group, opens a fresh mandate window, and gives a non-desperate reason to re-introduce the deal context. The new CSTO role (Trigger 3) is the strongest backup because it maps directly to the security review where the deal stalled.
Recommended sequence:
- Open with the CRO trigger to the original VP-level contact, framing the deal context as “worth a fresh look under the new CRO’s mandate”
- If no response in 5-7 business days, pivot to the new CSTO angle — coordinate a security brief that goes to Mayank’s team directly
- Use the agentic-AI direction (Trigger 2) as the discovery framing once the re-engagement lands
The signal data reused from earlier gallery runs — zero new credits consumed.
Why use Lusha in Claude
A stuck deal is a deal where the original conversation’s context has gone stale. Three patterns repeat across every revival motion.
The signal-based hook replaces the awkward “checking in” opener with a legitimate, non-desperate reason to re-engage. Generic follow-up emails read as the seller’s problem — the seller wants to close, the prospect doesn’t owe a response. A signal-based opener reads as the buyer’s context — the buyer’s company just changed something, the seller noticed, the conversation has new relevance. That reframe is often the difference between an inbox dismissal and a reply.
Leadership changes are the strongest revival triggers because they structurally rewrite the buying group. The new CRO inherits the budget but not the conversation. The new CSTO inherits the review process but not the deal context. The seller’s job is to be on the calendar in the first 60-90 days of the new leader’s tenure — and a stuck deal that died at the prior leader’s procurement review is exactly the kind of opportunity that should re-open under the new one. The prompt surfaces these triggers first because they are the only ones strong enough to override a stale conversation context.
The ranking system matters more than the signal count. Five strong triggers and ten weak ones do not add up to fifteen reasons to re-engage. The strongest single trigger does the work. The prompt ranks deliberately because writing one excellent re-engagement email tied to the right signal converts at a multiple of writing five generic ones tied to noise. STRONG signals carry the deal forward. MEDIUM signals support the conversation once it re-opens. WEAK signals are color, not catalyst.
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 is this different from the closed-lost re-engagement prompt?
The closed-lost prompt fires on deals the rep already lost — the deal is officially closed and the relationship needs a structural reset. This prompt fires on deals still in the pipeline that have gone quiet but aren’t formally lost. Different stages, different framing. Closed-lost re-engagement is “this was a no, here’s why it should be re-opened.” Stuck-deal revival is “this never reached a no, here’s why the silence ends now.”
What if no signals have fired since the last touch?
The prompt surfaces this honestly. A genuinely quiet account may need a different revival approach — executive sponsor escalation through the prospect’s leadership chain, a breakup email that gives the prospect an explicit off-ramp, or a wait-and-watch period until a signal does fire. The prompt avoids fabricating reasons to re-engage when none exist.
Should the AE always lead with the strongest single trigger?
Almost always yes. The exception is when the strongest trigger is leadership change in the buying group — in which case the opener may need to acknowledge the silence (briefly) and the new leader (specifically), because the AE is re-introducing a deal context the new leader may have never seen. The prompt surfaces this case in the recommended approach section.
How fresh does a signal need to be to qualify as a revival trigger?
The signal must have fired AFTER the last meaningful touch. Events from before the stall are not fresh — the prospect already knew about them. The prompt enforces this constraint and filters out pre-stall events automatically.
Can I run this against a list of stuck deals in one pass?
Yes. Paste 5-15 deals with the relevant context (prospect, last touch, stage), and the prompt returns a ranked revival plan per deal. For Sales Managers running pipeline reviews, this is the most efficient version of the workflow — surface the deals with strong triggers, deprioritize the ones with no signal, allocate revival time accordingly.
Does the prompt know if my primary contact left the prospect company?
Yes. The prompt cross-references the primary contact’s record against the prospect company. If the contact has departed, the response surfaces the departure as the primary revival challenge — the right move may not be re-engaging the original person but rather re-introducing the value to the new owner of the buying decision.
Ready to build this?
Get started with Lusha and set up this play in minutes.
