Flag accounts at churn risk before the QBR cycle

<context>
QBR season is coming up and I want to get ahead of any accounts that might be at risk before the cycle starts. I don't want to discover a problem during the QBR — I want to know about it beforehand so I can act.

My book of business:
- Account list: [PASTE COMPANY NAMES, ONE PER LINE — or "check my Gmail for active accounts"]
- Segment or tier (if relevant): [ENTERPRISE / MID-MARKET / SMB]
- Renewal window I'm focused on: [NEXT 90 DAYS / NEXT 6 MONTHS / ALL]
- Contract values (if known): [RANGE OR SPECIFIC — helps prioritise by risk exposure]
</context>

<task>
For each account in my list, run a two-part check:

PART 1 — Structural signals (Lusha)
Use Lusha's signals layer to check each account for:
- Executive changes in the last 90 days in Finance, IT, or the business unit most likely to own the vendor relationship
- Headcount contraction — meaningful reduction in the team or department using the product
- M&A activity where our customer is the acquired party
- A new senior hire in a function that typically re-evaluates vendor relationships on arrival

For each signal found, rate the churn risk it creates:
- HIGH — signal directly threatens the contract
- MEDIUM — signal is worth a proactive conversation but doesn't immediately threaten the contract
- LOW — signal is worth noting but unlikely to affect the contract in the near term

PART 2 — Engagement signals (Gmail)
For each account, check my Gmail for:
- Days since last meaningful exchange (not auto-replies, not calendar confirmations)
- Whether the last email was inbound or outbound
- Any unanswered email on either side older than 21 days
- Any open commitment — something I said I'd send or do that I haven't

Flag engagement risk:
- COLD — no meaningful exchange in 45+ days
- COOLING — last exchange was 21–44 days ago and was outbound from me
- ACTIVE — exchange within 21 days with at least one inbound from them

Combine both signals into a final account risk rating:
- AT RISK — HIGH structural signal, or COLD engagement, or both
- WATCH — MEDIUM structural signal + COOLING engagement
- STABLE — no structural signal + ACTIVE engagement

Return:
1. A ranked list of accounts by risk rating (AT RISK first, then WATCH, then STABLE)
2. For each AT RISK or WATCH account: the specific signal, the last Gmail touchpoint, and one recommended next action
3. A summary line at the top: how many accounts are AT RISK, WATCH, and STABLE out of the total scanned
</task>

<constraints>
- Only flag signals Lusha actually returns. Don't infer risk from company size or industry alone.
- Don't mark an account AT RISK based on engagement alone if Lusha returns no structural signals — flag it as WATCH with a note to check in.
- If an account can't be found in Lusha, note it and skip the structural check — don't leave it off the list entirely.
- Keep the output scannable. One row per account for the ranked list, detail only for AT RISK and WATCH.
</constraints>

The situation: A CS manager at a B2B SaaS company runs the play across a book of 11 mid-market accounts, two weeks before QBR season. Mix of $40K–$180K ARR contracts, renewals spread across Q3 and Q4.

Output: 3 accounts flagged AT RISK, 4 on WATCH, 4 STABLE. The AT RISK flags each have a different signal — one structural, one engagement, one both. The WATCH accounts have a clear recommended action. The whole thing fits one screen.

Summary

11 accounts scanned. 3 AT RISK · 4 WATCH · 4 STABLE.

Run: May 21, 2025. Structural signals via Lusha. Engagement signals via Gmail.

AT RISK accounts

Meridian Logistics · $148K ARR · Renews August

• Structural: CFO departed 6 weeks ago, no replacement confirmed. Finance owns vendor approvals for contracts above $100K at this account.
• Engagement: Last inbound email 52 days ago. Last outbound 11 days ago, no reply.
• Lusha signal: CFO departure confirmed. No interim appointment detected.
• Action: Don’t wait for the QBR. Call the VP of Finance this week to confirm who owns the renewal sign-off now.

Cartway Technologies · $92K ARR · Renews October

• Structural: Acquired by a larger competitor 5 weeks ago as the target entity. M&A as acquired party typically freezes or re-routes vendor contracts pending integration review.
• Engagement: ACTIVE — last exchange 8 days ago, inbound from their side.
• Lusha signal: Acquisition confirmed via signals layer.
• Action: The relationship is warm but the contract path has likely changed. Use the next touchpoint to ask directly whether the acquisition affects how they handle vendor renewals.

Orlen Health · $67K ARR · Renews September

• Structural: No signals detected.
• Engagement: COLD — last meaningful exchange 61 days ago. Last email was outbound from me, no reply. Two follow-ups since, both unanswered.
• Action: One more direct reach-out before QBR — but escalate the contact. Email the champion and CC their manager. If still no reply by end of week, flag for CS leadership.

WATCH accounts

STABLE accounts

Brightfield Co · $112K · Active engagement, no signals Corelink SaaS · $95K · Active engagement, no signals Aster Platforms · $61K · Active engagement, no signals Novela Group · $48K · Active engagement, no signals

Structural signals pulled via Lusha connector, May 21. Engagement data from Gmail. Account names are illustrative; details masked for privacy.