Run the weekly pipeline review and flag every deal at risk
Images on this page are for illustrative purposes only. Example outputs are based on Lusha data, with personal details masked or abbreviated for privacy.
This Claude prompt scans your active pipeline for deals at risk before the weekly standup — structural account changes via Lusha, meeting cadence gaps via Google Calendar. Returns a one-screen health report with RED / AMBER / GREEN ratings, a recommended action for each flagged deal, and a specific question to ask each at-risk rep in the standup.
The prompt
<context>
I want to run a weekly pipeline review before my team standup. I need to know which deals have a risk signal worth flagging — not from CRM health scores, but from what's actually happening at the prospect accounts right now.
My pipeline:
- Deal list: [PASTE DEAL NAME, COMPANY, STAGE, ACV, OWNER — one per line OR "pull from my calendar"]
- Team size: [NUMBER OF REPS]
- Focus: [ALL DEALS / CLOSE THIS QUARTER / SPECIFIC STAGE]
- What I want to flag: [ALL RISKS / STUCK DEALS / MISSING MEETINGS / STRUCTURAL CHANGES]
</context>
<task>
1. For each deal in the list, use Lusha to scan the prospect account for structural changes in the last 30 days:
- Executive departure or new hire in the buying function (CFO, CTO, CRO, VP of the relevant department)
- M&A activity where the prospect is the acquired party
- Significant headcount contraction in the team being sold into
- Any signal that typically re-routes or freezes vendor decisions
2. For each deal, check Google Calendar for meeting activity:
- When was the last meeting with this account?
- Is there a next meeting scheduled?
- Flag any deal where the last meeting was more than 21 days ago with nothing on the calendar — that's a stuck deal
3. Rate each deal on two axes:
ACCOUNT RISK (from Lusha signals):
- RED: structural change that directly threatens the deal
- AMBER: signal worth watching but not immediately threatening
- GREEN: no structural signals detected
ENGAGEMENT RISK (from Calendar):
- RED: no meeting in 21+ days, nothing scheduled
- AMBER: last meeting 11–20 days ago, next meeting not confirmed
- GREEN: active meeting cadence, next meeting on the calendar
4. Return a pipeline health report:
- Summary line: X deals reviewed, X RED, X AMBER, X GREEN
- RED deals first — account risk, engagement risk, and one recommended action for each
- AMBER deals — flagged with the specific signal or gap
- GREEN deals — listed only, no detail needed
- One question to ask each RED deal owner in the standup
5. Flag any deal where both account risk and engagement risk are RED — these are the deals most likely to slip the quarter.
</task>
<constraints>
- Flag only signals Lusha actually returns. Don't infer risk from deal age or rep tenure.
- The standup question for each RED deal must be specific to the risk — not "how's this deal going?" but "who's your relationship with now that Marcus left?"
- Keep the report to one screen. This is a standup tool, not a board deck.
- If a deal has no Lusha signal and an active meeting cadence, it's GREEN. Don't manufacture risk.
</constraints>What you'll get back
The situation: A sales manager at a B2B SaaS company runs the prompt Monday morning before a 9am standup. Eight deals in the pipeline, close this quarter focus, five reps on the team.
Output: 2 RED deals, 3 AMBER, 3 GREEN. One deal is double-RED. Standup runs in 12 minutes with specific questions per rep.
Pipeline health report — Week of May 19
8 deals reviewed · 2 RED · 3 AMBER · 3 GREEN
Run: Monday May 19, 7:58am. Signals via Lusha. Meeting cadence via Google Calendar.
RED DEALS — act before standup
Meridian Logistics · $148K · Negotiation · Owner: Sarah K.
- Account risk: 🔴 RED — CFO departed 18 days ago. Finance owns sign-off on contracts above $100K at this account. No replacement confirmed in Lusha.
- Engagement risk: 🔴 RED — Last meeting 26 days ago. Nothing on calendar.
- ⚠ Double RED — highest slip risk this week
- Recommended action: Sarah needs to get back in front of someone in Finance this week — either the interim owner or a direct ask to the CRO about who’s signing.
- Standup question for Sarah: “Who’s your current relationship with on the finance side at Meridian — and have you spoken to anyone there since the CFO left?”
Cartway Technologies · $92K · Proposal · Owner: James R.
- Account risk: 🔴 RED — Acquired by a larger competitor 12 days ago as the target entity. Contracts at acquired companies typically go under review during integration.
- Engagement risk: 🟡 AMBER — Last meeting 14 days ago. Next call not confirmed.
- Recommended action: James needs to ask directly on the next call whether the acquisition affects their vendor review process — before the proposal goes further into integration limbo.
- Standup question for James: “Have you spoken to anyone at Cartway since the acquisition was announced — and do you know if their procurement process has changed?”
AMBER DEALS — watch this week
| Deal | ACV | Stage | Owner | Flag |
|---|---|---|---|---|
| Finova Group | $180K | Proposal | Dana P. | New CTO hired 3 weeks ago — not in the buying group yet, but worth mapping before proposal goes to sign-off |
| Pallet Systems | $55K | Discovery | Alex M. | Last meeting 17 days ago, next call not confirmed — needs a booking this week |
| Dune Analytics | $44K | Negotiation | Chris T. | No structural signal, but negotiation has been open for 31 days with no movement — ask Chris what’s blocking |
GREEN DEALS — no action needed
Brightfield Co · $112K · Proposal · Owner: Sarah K. — active cadence, no signals Corelink SaaS · $95K · Closing · Owner: James R. — next meeting Thursday, no signals Novela Group · $48K · Discovery · Owner: Dana P. — meeting last week, no signals
Account signals via Lusha connector, May 19. Meeting cadence from Google Calendar live session.
FAQ
How many deals can I review in one run?
10–15 works well in a single prompt. Beyond that the output gets long and the standup value drops. If you have a larger pipeline, run it by segment — close this quarter first, then the rest of the pipeline separately.
What if my reps don't use Google Calendar for customer meetings?
The Calendar check only works if meetings are booked through Calendar. If your team uses a different scheduler or books calls informally, skip the Calendar field and run Lusha signals only — you’ll get the account risk layer without the engagement layer. Still valuable.
My CRM already has a pipeline health score. Why run this?
CRM scores are built from what reps log — activity, stage, close date. They don’t know the CFO left 18 days ago or that the prospect was acquired last month. Lusha’s signals are external and real-time. Running both gives you the full picture: what the rep sees and what’s happening around the deal that the rep may not know yet.
What does double-RED mean in practice?
It means the deal has both a structural account risk and an engagement gap at the same time — the worst combination. Structural risk without engagement means you can’t act on it. Engagement gap without structural risk is recoverable. Double-RED means the deal is at real risk of slipping the quarter without immediate action from the rep and the manager.
Can I use this for forecast calls instead of standups?
Yes — the output structure works for both. For a forecast call, add ACV totals by risk tier to the summary line so you can see how much revenue is at risk vs clean. The prompt handles that if you add it to the context.
What if all my deals come back GREEN?
That’s a clean pipeline read. GREEN means no structural signals detected and active meeting cadence — that’s the right state to be in. If it feels wrong given what you’re hearing from reps, that’s a signal to dig into the CRM data rather than the account signals.
Ready to build this?
Get started with Lusha and set up this play in minutes.
