Brief yourself before a renewal call and draft the follow-up after
Most renewal risk doesn’t show up on the renewal call. It shows up in the two weeks before it — a champion who changed roles, a new VP who owns the budget now, a procurement freeze nobody flagged. By the time you’re on the Zoom, you either know or you don’t.
This play has two phases. Phase 1 runs before the call: Calendar finds your next renewal or expansion Zoom, Lusha validates every attendee and scans the account for what changed, Gmail pulls your last thread so you know exactly where you left things. You walk in with a one-screen brief — who’s in the room, whether anything shifted, and what context to carry in from the last email exchange.
Phase 2 runs after: Zoom’s transcript tells Claude what was said. It drafts the follow-up email — clean summary, agreed next steps, right contacts pulled from Lusha — so the first thing you send after a 45-minute renewal call isn’t written from scratch at 6pm.
Both phases run on Claude with the Lusha, Google Calendar, Gmail, and Zoom connectors. Once connected, they run in the background — no special syntax needed. Just ask Claude to run Phase 1 before you join, Phase 2 after you’re done.
Images on this page are for illustrative purposes only. Example outputs are based on Lusha data, with personal details masked or abbreviated for privacy.
The prompt
Phase 1 block
<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 — especially if they now own the budget or the decision
- Identify anyone on the invite who wasn't in the original buying group (new stakeholder, procurement addition, executive observer)
- For the primary contact or decision maker, 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 soften gaps with "probably still there."
- Don't invent contacts, signals, or email content. Surface only what Lusha and Gmail return. Flag what can't be verified.
- Keep it to one screen. I'm reading this in the few minutes before I join.
</constraints>Phase 2 block
<context>
I just finished a renewal or expansion Zoom call. I need a clean follow-up email drafted from the recording, with a summary of what was agreed and next steps. Then I want the right contact details from Lusha so I can send it immediately.
My account:
- Company: [COMPANY NAME]
- What we discussed: [RENEWAL / EXPANSION / SPECIFIC TOPIC]
- Who was on the call: [NAMES AND TITLES — or "pull from the Zoom recording"]
- What I need to send: [SUMMARY + NEXT STEPS / SPECIFIC ASK / PROPOSAL REFERENCE]
</context>
<task>
1. Pull the transcript or recording summary from the most recent Zoom call for this account.
2. From the transcript, extract:
- What was agreed (specific commitments, timelines, numbers discussed)
- Who owns each next step — their side and mine
- Any objection or concern raised that wasn't fully resolved on the call
- Any reference to pricing, contract terms, or competing vendors (flag these separately)
3. Draft a follow-up email:
- Open with a one-sentence summary of the call outcome — not "Great to connect," just what happened
- List agreed next steps clearly, attributed by owner
- If there was an unresolved concern, acknowledge it and state the next action on it
- Close with a specific ask or confirmation needed from their side
- Tone: direct and clear — matches a CS or AM relationship, not cold outreach
4. Use Lusha to confirm the send-to contacts:
- Validate the email address for the primary contact and anyone else who needs to be on the thread
- If a new stakeholder was on the call who I haven't emailed before, pull their verified contact from Lusha and add them as CC
5. Return:
- The draft email, ready to send (just add the verified emails above the draft)
- A one-line note on any open risk or unresolved item from the call I should track
</task>
<constraints>
- Don't invent commitments or paraphrase loosely. Only include what was explicitly said in the transcript.
- If the transcript is missing or unclear on a point, flag it rather than fill it in.
- Keep the email under 200 words. If it needs more, something is wrong with the structure, not the length.
</constraints>What you'll get back
The account: A SaaS company — mid-market, ~400 employees — up for a $96K annual renewal on a sales intelligence platform. The CS rep last emailed the champion 23 days ago. No reply. A renewal Zoom is on the calendar for Thursday with three attendees.
Phase 1 output: Pre-call brief
One structural change and one unanswered email. Worth knowing before you join.
Who’s on the call (from Calendar, validated by Lusha)
| Attendee | Verified title | Status |
|---|---|---|
| Sarah M. | VP Revenue Operations | ✓ Title confirmed — same role, still primary contact |
| Daniel K. | Director of Sales Enablement | ⚠ Role change — was Senior Manager when the deal started. Promoted 6 weeks ago. Now owns enablement budget directly. |
| Priya N. | Head of IT Procurement | ⚠ New stakeholder — not part of the original buying group. Procurement added to renewal reviews Q1 this year. |
One flag worth raising early: Daniel’s promotion means the person who originally signed off on this contract no longer holds the same title or scope. Worth confirming on the call that his budget authority for this renewal is unchanged — or whether Priya’s presence signals a new approval step.
Account signals (Lusha signals layer)
- Headcount contraction in Sales: The sales team has shrunk from ~110 to ~87 over the past quarter — a 20% reduction. If the contract is priced per seat, the renewal conversation may open with a usage-based challenge.
- No M&A or security events detected.
- No C-suite changes in Finance or IT — existing approval chain intact.
Last email thread (from Gmail)
Last touch: 23 days ago. You sent a renewal prep summary with three open items: updated seat count, confirmation of the legal contact for the new order form, and a request to loop in IT if procurement needed to be involved. No reply received.
Open commitment on your side: You offered to send a revised proposal if the seat count changed. That proposal hasn’t been sent.
One thing to address early in the call: Priya’s presence on the invite confirms that IT procurement is now involved — exactly what your unanswered email was flagging. Open the call by acknowledging it: “Glad Priya’s on — I wanted to make sure procurement had what they needed, and it sounds like you’ve already looped her in.”
Phase 2 output: Post-call follow-up draft
Based on a 38-minute Zoom transcript. Contact emails validated via Lusha before sending.
To: sarah.m@[company].com
CC: daniel.k@[company].com; priya.n@[company].com (email pulled from Lusha — first contact)
Subject: Renewal next steps — [Company] × [Your company]
Hi Sarah,
Good call today. Here’s where we landed:
Agreed:
- Renewal term: 12 months, same scope, adjusted to 82 seats (from 110) — your side to confirm final number by Friday
- Order form to go to Priya for IT procurement review — I’ll send the updated form by EOD tomorrow
- Legal sign-off: Sarah to confirm whether existing legal contact still owns vendor agreements or if it routes through procurement now — your side, before order form goes out
One open item: Priya raised a question about data residency — whether your instance is EU-hosted. I said I’d check and follow up separately. Sending that confirmation tomorrow alongside the order form.
Let me know if I’ve missed anything.
[Your name]
Open risk to track: The seat reduction from 110 to 82 was agreed on the call but not formally confirmed in writing yet. Don’t send the order form until you have that number in email — otherwise the renewal could re-open if the final seat count shifts again.
Contact details confirmed live via the Lusha connector at time of sending. Zoom transcript pulled from the session recorded May 22. Personal details abbreviated for privacy.
Why use Lusha in Claude
Renewal calls feel like a formality until they aren’t. The customer you’ve been speaking to for 18 months gets promoted, or procurement gets added to renewals as a new policy, or the team using your product shrinks 20% and nobody flagged it. None of that shows up on the calendar invite. All of it changes how the conversation goes.
Phase 1 solves the information gap before you walk in. Calendar tells the play which meeting is happening and who’s on it. Lusha answers the questions the invite can’t: is this person still in the same role, who’s new to the buying group, what’s moved at the account since the last touchpoint. Gmail fills in the last email thread so you know exactly where you left things — and whether there’s something you said you’d do that you haven’t done yet. The brief is one screen because that’s all the time you have before you join.
Phase 2 solves the follow-up problem. Most follow-up emails after a renewal call are either vague (“Great to connect — here’s a summary”), too long, or sent three days late because the rep had four other calls that day. Zoom’s transcript is the source of truth — what was actually said, what was actually agreed. Claude reads it and writes the email directly from the record, not from memory. Lusha validates the send-to addresses so the first email you send to a new procurement contact doesn’t bounce.
The two phases reinforce each other. A strong pre-call brief means you ask sharper questions on the call. Sharper questions mean the transcript has cleaner commitments. Cleaner commitments mean the follow-up email is easy to write — and harder to dispute later.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
Do I need all four connectors?
Lusha and Calendar are the core of Phase 1. Gmail adds the email thread context — if you don’t have it connected, you’d just skip that part of the brief. Zoom is Phase 2’s trigger — without it, you’d paste the transcript manually. All four together make the play fully automatic. Missing one just means you fill in that part yourself.
What if the Zoom recording isn't ready yet?
Zoom usually processes transcripts within 10–15 minutes of the call ending. If it’s not there yet, wait and run Phase 2 after it’s available. The transcript is what makes the follow-up accurate — don’t run Phase 2 from memory.
What if someone on the invite can't be verified in Lusha?
They get flagged to confirm on the call rather than guessed at. For a new procurement contact like Priya in the example above, Lusha will return their details if they’re in the database — if not, the play tells you to verify directly and pulls what it can.
How is this different from the signing call validation play?
The pre-close signing play is built for a single moment — the last check before ink. This play is built for an ongoing relationship: it layers in email history, headcount signals, and role changes across a customer you’ve been managing for months. It also has a second phase — the signing play ends when you walk into the room. This one follows you out.
Can I run Phase 1 the evening before?
Yes, and it’s often better. Running it the night before gives you time to act on something — send a quick email to the new procurement contact, confirm the seat count before the call, or check that open commitment you forgot about. The data is pulled live when you run it, so an evening-before check is as accurate as one run 5 minutes before you join.
What if the account has no signals in Lusha?
No signals is a clean read — it gets returned as “no structural changes detected.” That’s useful information too. A clean account scan going into a renewal means the risk is in the conversation, not the org chart.
Does the follow-up email go out automatically?
No. Claude drafts it and validates the send-to addresses. You review and send. For a renewal or expansion — where the email is a record of what was agreed — you want eyes on it before it goes.
Ready to build this?
Get started with Lusha and set up this play in minutes.
