Rank active deals by end-of-quarter close probability

Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha and Gmail connector output, but were not pulled from a live session. Run the prompt with your own pipeline data to see live results. Personal details in any live examples are masked or abbreviated for privacy.

End-of-quarter close probability built on real signals — not deal stage alone — means validating every contact via Lusha, checking thread recency and open commitments via Gmail, and scoring each deal STRONG, POSSIBLE, UNLIKELY, or PUSH before a manager walks into the forecast call with a number. This Claude prompt does it in one pass and returns a ranked list with ACV totals, a specific risk flag per deal, and a recommended action before quarter end.

The prompt

Open in Claude Open in ChatGPT 
<context>
It's end of quarter. Before the forecast call, I want a ranked list of every active deal scored by close probability — based on what's actually happening in each deal, not just what stage it's in.

My pipeline:
- Active deals: [PASTE DEAL NAME, COMPANY, PRIMARY CONTACT, STAGE, ACV, CLOSE DATE — one per line]
- What I sell: [PRODUCT / SOLUTION]
- Quarter end date: [DATE]
- Slack channel: [CHANNEL NAME OR "skip"]
</context>

<task>
1. For each deal, use Lusha to validate:
   - Primary contact still at the company in the same role?
   - Any account signal in the last 14 days?
   - Secondary contacts covering economic buyer and technical evaluator?

2. Search Gmail for thread status per deal:
   - When was the last inbound reply from the prospect?
   - Is there an open commitment from the rep that hasn't been delivered?
   - How many days since last two-way communication?

3. Score each deal for close probability this quarter:
   STRONG (>70%): verified contacts + recent inbound + no open rep commitments + Proposal or beyond
   POSSIBLE (40–70%): verified primary contact + some thread activity + Discovery/Proposal
   UNLIKELY (<40%): departed contact or stale thread (14+ days no reply) + single-threaded + early stage
   PUSH: deal will almost certainly not close this quarter — flag for pipeline review

4. Build the EoQ close ranking:
   ## EoQ close ranking — [Quarter]
   Rank · Company · ACV · Stage · Score · Key risk · Recommended action

   ## Strong closes — protect these
   Specific action needed to ensure close

   ## Possible closes — push these
   What needs to happen per deal

   ## Unlikely / Push — flag these
   Don't spend close cycle time here

   ## Pipeline summary
   Total ACV · Strong ACV · Possible ACV · Unlikely ACV

5. Post to Slack if specified — tag manager and reps.
</task>

<constraints>
- STRONG requires recent inbound — not just a recent outbound.
- PUSH deals must be explicitly called out, not hidden in UNLIKELY.
- ACV summary must be specific dollar amounts.
- Score based on verifiable signals: Lusha contact status + Gmail thread recency + stage.
</constraints>

What you'll get back

The situation: A sales manager runs the EoQ ranking for a rep’s 5 active deals before the Thursday forecast call. Quarter ends June 30.

EoQ close ranking — Q2 2026

🟢 STRONG — protect these

Ashford Platforms · $95K · Negotiation

Last inbound: May 29 (D.R. replied “legal team reviewing DPA”) — 2 days ago Contacts: D.R. ✓ · M.L. ✓ · CFO not yet introduced ⚠ Signal: Sales headcount up 28%

Key risk: CFO not introduced — rep needs to ask D.R. to make the introduction before close Recommended action: Get CFO on a call before June 20. Don’t send contract without the signer engaged.

🟡 POSSIBLE — push these

Dunmore Analytics · $72K · Proposal

Last inbound: May 27 (T.K. replied asking about pricing tiers) — 4 days ago, no response sent Contacts: T.K. ✓ · no secondary contact Signal: Series B closed 18 days ago — window is open

Key risk: Rep owes T.K. a pricing response that hasn’t been sent Recommended action: Reply to T.K. today with the tier breakdown. Single-threaded — add a RevOps contact this week.

Briarway SaaS · $50K · Discovery

Last inbound: May 20 (P.O. replied to cold outreach) — 11 days ago, no response sent Contacts: P.O. ✓ · no secondary contact Signal: None

Key risk: Thread at risk of going cold. Still early stage — close by June 30 is tight. Recommended action: Reply to P.O. today. If no reply in 5 days, move to UNLIKELY.

🔴 UNLIKELY / PUSH — don’t spend close cycle time here

Vantage Enablement · $58K · Negotiation

Primary contact: B.N., Sr Director RevOps — DEPARTED per Lusha. No active contact. Last inbound: April 14 — 47 days ago Signal: None

Key risk: Deal is at Negotiation with no active contact. This is a PUSH — not a June 30 close. Recommended action: Find replacement contact immediately. Don’t count this deal in June forecast.

Elmont Systems · $35K · Discovery

Last inbound: None — rep has sent 3 emails, no replies received Contacts: Director-level only — below VP threshold Signal: None

Key risk: No engagement, wrong seniority level. PUSH. Recommended action: Find VP-level contact via Lusha before spending more call time.

Pipeline summary — Q2 2026

Total active ACV: $310K 🟢 Strong (closeable): $95K 🟡 Possible (with effort): $157K 🔴 Unlikely / Push: $93K

Recommended forecast: $95K committed · $157K upside · $58K moved to Q3

Illustrative example — fictional company names used. Run with your own pipeline to see live results.

Built by: Lusha
Time to build: 4 min
Difficulty: Medium
Tools: Claude, Gmail, Lusha
Type: Prompt

Why use Lusha in Claude

Lusha in Claude finds the B.N. departure at Vantage Enablement in seconds — a $58K Negotiation-stage deal with no active contact that the CRM still shows as active. Without the contact check, that deal goes into the Q2 forecast and the manager sets a number that includes $58K that won’t close. With it, the deal moves to Q3 and the forecast is accurate. The STRONG classification for Ashford requires recent inbound — D.R.’s reply 2 days ago — not just a high ACV and a late stage. A Negotiation-stage deal where the prospect went silent 3 weeks ago is not STRONG regardless of ACV. That distinction is what separates a forecast that holds from one that slips.

Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.

FAQ

  • Why does STRONG require recent inbound and not just recent outbound?

    A rep can send an email any time — recent outbound proves the rep is working the deal, not that the prospect is engaged. Recent inbound (the prospect replied) is the signal that the deal is alive. A Negotiation-stage deal where the rep sent three emails and received no reply in 14 days is UNLIKELY regardless of stage.

  • How is this different from the weekly pipeline review?

    The weekly pipeline review flags every deal at risk on an ongoing basis. This play is built specifically for the end-of-quarter forecast conversation — it scores every deal against the close date, produces dollar ACV totals by band, and generates the recommended forecast number. Use the weekly review throughout the quarter, use this play for the EoQ call.

  • What if most deals come back as UNLIKELY or PUSH?

    That’s accurate data. A pipeline where most deals are UNLIKELY heading into the last two weeks of the quarter needs a pipeline review conversation, not an optimistic forecast. The play is most useful precisely in this scenario — it surfaces the real number before the manager has to discover it on a forecast call.

  • Is this a manager play or can individual reps run it too?

    Both. A rep running this on personal deals gets a clear picture of where to spend the next two weeks. A manager running it across the full team gets a consolidated forecast view. Run it at both levels — the inputs are the same, the audience for the output is different.

Related Prompts

Ready to run this?

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

Get free access Read the Docs