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

Flag at-risk deals and auto-draft the re-engagement sequence

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

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 chain with your own pipeline and connectors to see live results.

A pipeline review that only flags risk leaves the rep with a list and no plan. The Pipeline Review Skill tells you which deals are stalling, contact-stale, or coverage-thin — but knowing that a deal is at risk and knowing what to send to fix it are two different jobs. This play chains both skills into one pass: Claude runs the Pipeline Review Skill to flag every at-risk deal with the specific reason, then automatically hands each flagged deal to the Sequence Writer Skill, which drafts a complete re-engagement sequence grounded in the actual risk signal — a departed champion, a missing buying role, a stalled thread. The rep opens the output with the diagnosis and the fix already written.

How to set it up

1

Install both skills in the same Claude Project

Make sure the Pipeline Review Skill and the Sequence Writer Skill are both installed, with the Lusha in Claude connector active in the same Project.

2

Paste your open deal list

Add account name, deal stage, and ACV for every open deal — or connect your CRM and tell Claude to use your live pipeline instead of a pasted list.

3

Send the prompt

Claude runs the Pipeline Review Skill first, flags every at-risk deal with the specific reason, then automatically chains each flagged deal into the Sequence Writer Skill to draft the matching re-engagement sequence.

 

The prompt

Open in Claude Open in ChatGPT 
Run the Pipeline Review Skill on my open deals below.

My open deals:
[Paste account name, deal stage, and ACV for each —
or connect your CRM and say "use my open pipeline"]

For every deal flagged At Risk, automatically chain into
the Sequence Writer Skill using the specific risk reason
as the trigger event. For example:
- "Champion departed" becomes the trigger for a
  re-engagement sequence to the new contact
- "No verified Economic Buyer" becomes the trigger for
  a sequence introducing the product to that role
- "No activity in 30+ days" becomes the trigger for a
  signal-based re-opening sequence

Return:
1. The full risk-ranked deal list from Pipeline Review
2. For every At Risk deal only — a complete sequence
   from Sequence Writer, grounded in that deal's specific
   risk reason
3. Skip sequence generation for deals rated Needs
   Attention or On Track — flag those separately with
   no sequence attached

What you'll get back

A risk-ranked pipeline review where every At Risk deal already has its fix attached.

DealRisk reasonSequence generated
[Company A]Champion departed 5 weeks ago3-step re-entry sequence to new VP of Sales
[Company B]No verified Economic Buyer, Stage 3CFO introduction sequence, 2 steps
[Company C]No activity in 34 daysSignal-based re-opening sequence, 2 steps

Example output is illustrative — real output runs the live skill chain against your actual pipeline.

Why use Lusha in Claude

Pipeline reviews and outreach drafting are usually two separate motions, often run by two different tools or at two different times. A rep gets the risk flag in a forecast call, then has to context-switch into a separate writing task hours or days later — by which point the urgency from the review has faded and the sequence ends up generic.

Chaining the two skills removes that gap entirely. The risk reason that the Pipeline Review Skill surfaces — verified live via Lusha, not guessed from CRM notes — becomes the exact trigger event the Sequence Writer Skill needs to ground its first line. A departed champion doesn’t just get flagged. It gets a sequence written for the most senior new contact, addressing the disruption directly instead of pretending nothing changed.

Skipping sequence generation for healthy deals matters too — it keeps the output focused on what actually needs a rep’s attention this week, not a sequence for every deal regardless of whether one is needed.

FAQ

  • Do I need both skills installed before running this

    Yes. Install the Pipeline Review Skill and the Sequence Writer Skill in the same Claude Project, then run this prompt. Claude calls each skill’s instructions in sequence — you don’t need to invoke them separately.

  • What if a deal is flagged for multiple reasons at once?

    The chain uses the highest-severity reason as the primary trigger for the sequence and notes the secondary risks in the deal summary. A champion departure with no Economic Buyer coverage gets a sequence built around the departure first, since that’s usually the more urgent fix.

  • Can I run this weekly without re-explaining the chain each time?

    Yes — save this prompt in a Claude Project alongside both skills, and it becomes a one-line weekly request: “run the chain on my current pipeline.”

  • What happens to deals rated Needs Attention?

    They’re listed with their flag but no sequence is generated automatically. If you want a sequence for a specific Needs Attention deal, ask for it directly and Claude will run Sequence Writer on that deal alone.

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