The best Claude prompts for CS and AMs

Renewal risk usually shows up before the renewal call — in a champion who changed roles six weeks ago, a headcount cut in the team using the product, an acquisition that nobody mentioned. By the time you’re on the call, you either know or you don’t.

These four Claude prompts are built for the moments CS and AMs deal with most: walking into a renewal call prepared, finding which accounts are ready to expand before the conversation comes up, getting back into an account after a champion leaves, and knowing which accounts are quietly at risk before QBR season starts.

All four run on Lusha’s verified contact and company data. Connect the Lusha connector once and it runs in the background. Some prompts also use Gmail, Google Calendar, and Zoom.

PROMPT 1 — Pre-call brief and post-call follow-up for renewal and expansion Zooms

Two phases, one prompt. Before the call: Calendar finds the Zoom, Lusha validates every attendee and scans the account for changes, Gmail surfaces the last thread. After the call: the Zoom transcript tells Claude what was agreed and it drafts the follow-up email with the right contacts confirmed via Lusha. The brief is one screen. The follow-up is under 200 words and attributed by owner.

Tools: Lusha + Google Calendar + Gmail + Zoom

→ Full play page and example output

<context>
I have an upcoming renewal or expansion Zoom call. Before I join, brief me on who's attending and what's changed at the account. I want to walk in knowing the current state of the buying group, any structural changes at the company, and what was last said in email.

My account:
- Company: [COMPANY NAME]
- What's up for renewal or expansion: [PRODUCT / CONTRACT DETAILS]
- Contract value (annual): [DOLLAR AMOUNT]
- Renewal date or expansion target: [DATE OR TIMEFRAME]
- Who I think is the main contact: [NAME, TITLE — or "find it from the Calendar invite"]
</context>

<task>
1. Find my next Zoom call for this account on Google Calendar. Pull the external attendees from the invite.

2. Validate each attendee with Lusha:
   - Confirm their current title and that they're still at the company
   - Flag anyone whose role has changed since the last touchpoint
   - Identify anyone on the invite who wasn't in the original buying group
   - For the primary contact, confirm they're reachable (verified email or direct phone)

3. Scan the account for changes since the last touchpoint using Lusha's signals layer:
   - Executive moves in Finance, IT, or the business unit owning this contract
   - M&A activity — especially if our customer is the acquired party
   - Headcount signals — meaningful growth or contraction in the team using the product
   - Any leadership hire that typically re-evaluates existing vendor relationships

4. Pull the last email thread with this account from Gmail:
   - Summarize what was last discussed and any open commitments on either side
   - Flag if there's an unanswered email or a commitment I made that I haven't followed up on
   - Pull the date of the last touch — if it's been more than 30 days, flag it

5. Return a one-screen pre-call brief:
   - Who's in the room and their current validated role
   - Any structural change at the account I need to know before I join
   - What we left off in email and whether there's anything outstanding
   - ONE thing to address early in the call based on what Lusha and Gmail surfaced
</task>

<constraints>
- Validation is binary — the person is at the company or they aren't, the title matches or it doesn't.
- Don't invent contacts, signals, or email content. Surface only what Lusha and Gmail return.
- Keep it to one screen.
</constraints>

PROMPT 2 — Scan your accounts for expansion signals

Expansion conversations usually start too late — on the renewal call, when the customer already has a number in their head. This prompt moves that conversation earlier. Lusha scans your book of business for signals that typically precede expansion: headcount growth in the team using the product, a new CRO who audits the stack in the first 90 days, a funding round that unlocks new budget. The output is a ranked shortlist — STRONG, POSSIBLE, MONITOR — with a specific opening line for each account worth calling this week.

Tools: Lusha

→ Full play page and example output

<context>
I want to find expansion opportunities in my current book of business before I go looking for new logos. I'm looking for accounts that have a signal worth acting on this week.

My book of business:
- Account list: [PASTE COMPANY NAMES, ONE PER LINE]
- What I sell: [PRODUCT / USE CASE]
- How we typically expand: [SEATS / NEW TEAMS / NEW USE CASES / GEOGRAPHY]
- Any accounts already in an active expansion conversation: [LIST OR "NONE"]
</context>

<task>
1. For each account, use Lusha to scan for signals that typically precede an expansion conversation:
   - Headcount growth of 15%+ in the team or function currently using the product
   - New hires in a function or geography we don't currently sell into
   - A spike in open roles in a relevant function
   - New funding round in the last 90 days
   - New VP or C-level hire in a function we sell into but don't currently have coverage in
   - New CRO, VP of Sales, or Head of GTM (typically audits the sales stack within 90 days)

2. For each signal found, rate the expansion opportunity:
   - STRONG — signal directly suggests a near-term expansion conversation
   - POSSIBLE — signal is worth a proactive mention on the next call
   - MONITOR — signal is early or indirect — flag for next quarter

3. For each STRONG or POSSIBLE account, return:
   - The specific signal Lusha surfaced
   - The expansion angle it suggests
   - A one-line conversation opener specific to the signal

4. Return a ranked list: STRONG first, then POSSIBLE, then MONITOR.
5. Flag if any account shows both an expansion signal and a churn signal.
</task>

<constraints>
- Only surface signals Lusha actually returns.
- The conversation opener must reference the specific signal — not a generic check-in.
- If fewer than 3 accounts have a STRONG signal, say so. Don't inflate ratings.
</constraints>

PROMPT 3 — Find who owns an account after your champion leaves

Champion departure is the leading cause of quiet churn. The relationship was warm, the contact goes silent, and by the time you find out they’ve left, the new owner has already formed an opinion of your product without ever talking to you. This prompt maps who’s currently in the relevant function at the account, identifies the most likely heir, confirms their contact details via Lusha, and drafts a re-entry email from the context in your last Gmail thread — so the first message you send isn’t a cold reset.

Tools: Lusha + Gmail

→ Full play page and example output

<context>
My champion at an account has left or gone dark. I need to find who owns this account now, confirm their contact details, and draft a re-entry email that picks up from where the last conversation left off — not a cold outreach.

My account:
- Company: [COMPANY NAME]
- Person who left (or went dark): [NAME, TITLE]
- What we sell them / what they use: [PRODUCT OR CONTRACT]
- Contract value and renewal date (if known): [DOLLAR AMOUNT / DATE]
- How I found out: [EMAIL BOUNCED / LINKEDIN UPDATE / WENT SILENT / OTHER]
- Last meaningful interaction: [DATE OR "CHECK GMAIL"]
</context>

<task>
1. Use Lusha to map who's currently at this account in the relevant department and seniority band:
   - Pull current employees at [COMPANY NAME] in [DEPARTMENT]
   - For each person returned, confirm: current title, how long they've been in the role, seniority level
   - Flag anyone who joined or was promoted in the last 90 days
   - Flag anyone whose title includes "Head of", "VP", "Director" or "Manager" in the same function

2. Identify the most likely new owner of this relationship:
   - Return: one primary contact to reach, one backup

3. Validate the primary contact with Lusha:
   - Confirm their current title and tenure at the company
   - Pull their verified work email and direct phone if available

4. Pull the last email thread with this account from Gmail:
   - Summarize what was last discussed and any open commitments on either side
   - Flag any contract details, pricing, or feature requests mentioned in the thread

5. Draft a re-entry email to the primary contact:
   - Acknowledge the transition — don't pretend you don't know [NAME] left
   - Carry forward one specific thing from the Gmail thread
   - Keep it under 120 words
   - No "just checking in", no "I wanted to reach out"
   - Close with a specific, low-friction ask

6. Return the org map, primary + backup contact, Gmail summary, draft email, and one risk flag.
</task>

<constraints>
- Don't invent contacts or roles. Only return what Lusha verifies.
- The re-entry email must carry something specific from the Gmail thread.
- If the Gmail thread is empty or very old (90+ days), flag this.
</constraints>

PROMPT 4 — Flag accounts at churn risk before the QBR cycle

QBR prep usually means pulling a dashboard and looking at health scores built from product usage data — things that already happened. This prompt checks what’s happening now at each account: who left, who was hired, whether the company was acquired, whether your own engagement has dropped. Lusha handles the structural signals. Gmail handles the engagement check. The output is a ranked shortlist — AT RISK, WATCH, STABLE — with a specific recommended action for every flagged account, before the QBR cycle starts rather than during it.

Tools: Lusha + Gmail

→ Full play page and example output

<context>
QBR season is coming up and I want to get ahead of any accounts that might be at risk before the cycle starts.

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]
</context>

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

PART 1 — Structural signals (Lusha)
- Executive changes in the last 90 days in Finance, IT, or the business unit owning this contract
- M&A activity where our customer is the acquired party
- Headcount contraction in the team using the product
- A new senior hire that typically re-evaluates vendor relationships on arrival

Rate the churn risk: HIGH / MEDIUM / LOW

PART 2 — Engagement signals (Gmail)
- Days since last meaningful exchange
- Whether the last email was inbound or outbound
- Any unanswered email older than 21 days
- Any open commitment I haven't followed through on

Flag engagement risk: COLD (45+ days) / COOLING (21-44 days, outbound) / ACTIVE

Combine 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: AT RISK first, then WATCH, then STABLE
2. For each AT RISK or WATCH: the specific signal, last Gmail touchpoint, one recommended action
3. Summary: how many AT RISK, WATCH, STABLE out of total scanned
</task>

<constraints>
- Only flag signals Lusha actually returns.
- Don't mark AT RISK based on engagement alone if no structural signals — flag as WATCH.
- Keep the output scannable.
</constraints>