More Resources
Prompt

Auto-prep a deal review doc in Drive before a QBR

Built by: Lusha
Time to build: 6 min
Difficulty: Medium
Tools: Gmail ▪ Google Calendar ▪ Google Drive ▪ Lusha ▪ Zoom

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

QBR prep typically takes 45 minutes — checking the CRM, re-reading email threads, finding the last call recording, writing a summary, and sending it to the manager. This Claude prompt does all of it in one pass: Google Calendar finds the meeting, Lusha validates every attendee, Gmail surfaces the full thread history and open commitments, Zoom pulls recent call context, and Google Drive saves the finished document. Five connectors. One output the exec can read in 5 minutes.

The prompt

Open in Claude Open in ChatGPT 
<context>
I have a QBR coming up. I want a complete deal review doc in Google Drive before I join — contact map, thread history, open commitments, Zoom call context, and a recommended agenda.

My QBR:
- Company: [COMPANY NAME]
- QBR event: [CALENDAR EVENT OR "FIND NEXT QBR WITH [COMPANY]"]
- Deal type: [NEW BUSINESS / EXPANSION / RENEWAL]
- ACV: [DOLLAR AMOUNT]
- Drive folder: [LINK OR "save to My Drive"]
- Attendees: [PASTE OR "CHECK CALENDAR"]
</context>

<task>
1. Find the QBR in Google Calendar:
   - Confirm date, time, and attendees
   - Note any agenda already in the invite
   - Flag if the meeting is less than 48 hours away

2. Use Lusha to validate all attendees and key contacts:
   - Confirm every Calendar attendee is still at the company in the same role
   - Map any key stakeholder NOT on the invite but relevant to know about
   - Check for any account signal in the last 30 days

3. Search Gmail for the full thread history with this account:
   - What has been discussed, agreed, and promised
   - Any open commitment on either side
   - Any unresolved concern or objection
   - Last 3 touch points and outcomes

4. Pull the last 2–3 Zoom call transcripts with this account:
   - Key topics discussed on recent calls
   - Any request or concern raised verbally but not in email
   - Any commitment made on a call that may not be in the email thread

5. Build the QBR review document and save to Google Drive:

   # QBR Review — [Company] — [Date]
   Account type · ACV · Attending · Created: [date]

   ## Account Health
   GREEN / AMBER / RED — with specific reason

   ## Who Is in the Room
   Every attendee verified via Lusha — name, title, role in the relationship
   Anyone on the account NOT in the room but worth knowing about

   ## Account Signals
   Any Lusha signal from the last 30 days — or "No signals detected"

   ## Relationship Summary
   5 sentences — how long the relationship has been active, what has been
   delivered, where things stand, what the open items are, and what the
   rep wants from this meeting

   ## Open Commitments
   What the rep owes the account · What the account owes the rep

   ## Recent Call Context
   Key points from the last 2–3 Zoom calls not captured in email

   ## Objections and Concerns on Record
   Any active unresolved concern across the relationship

   ## Recommended Agenda
   Based on open items, account health, and what needs to be resolved

   ## Exec Summary
   3 sentences — for someone joining this call cold

6. Return Drive link.
</task>

<constraints>
- Exec Summary: 3 sentences maximum — for someone with 60 seconds before joining.
- Open Commitments: specific items, not "follow up."
- QBR under 24 hours away: flag every open commitment as urgent.
- Save to Drive before returning the link.
</constraints>

What you'll get back

The situation: An AE has a QBR with Ashford Platforms tomorrow at 2pm — a $95K Proposal-stage deal. The AE’s VP is joining the call and has never spoken to Ashford before. Running the prompt tonight.

⚠ QBR is under 24 hours away — all open commitments flagged as urgent

Document created: “QBR Review — Ashford Platforms — June 5, 2026” (Drive link returned on live run)

QBR Review — Ashford Platforms — June 5, 2026

New Business · $95K ACV · Created: June 4, 2026

Account Health

🟡 AMBER — Two open commitments from the rep not yet delivered. Legal review flagged by D.R. as a pre-sign requirement — DPA not yet shared. ZoomInfo comparison requested on May 14 — still missing from proposal. Deal is engaged but not progressing until these items are addressed.

Who Is in the Room

AttendeeTitleRoleStatus
D.R.Head of Sales Strategy & OpsChampion, primary contact, economic influence✓ Verified · d.r@[ashford].com
M.L.Head of Sales OperationsTechnical evaluator✓ Verified · m.l@[ashford].com
VP (joining from our side)VP of SalesExec sponsor — first time on this account—

Not in the room but worth knowing: CFO at Ashford — D.R. mentioned informally on the May 14 Zoom call that “the CFO will need to sign off — she’s cautious about new vendors.” Not introduced yet. The VP should not push for a signature commitment today without understanding the CFO’s position.

Account Signals

No Lusha signals detected in the last 30 days at Ashford Platforms.

Relationship Summary

Relationship active since April 22 — 5 weeks. Two discovery calls completed, both productive. Proposal sent May 27. D.R. responded positively but raised two requirements: a ZoomInfo comparison and a DPA for legal review. Neither has been delivered. The deal is engaged and D.R. is not pulling away — but it will not move to Negotiation until both open items are closed. The goal for today’s QBR is to deliver both items live, address the legal pathway, and agree a close date.

Open Commitments

⚠ URGENT — rep owes account:

  • ZoomInfo comparison section — promised May 14, still missing from proposal. Send before or open the call by addressing it directly.
  • DPA link for legal review — flagged by D.R. on May 27 as a condition of signing. Never sent. Share at the start of the call.

Account owes rep:

  • D.R. to loop in legal team after DPA is received — not yet actioned (waiting on DPA)
  • M.L. to confirm HubSpot connector compatibility with IT — no update since May 21

Recent Call Context

From Zoom transcripts — not in the email thread:

  • May 14 call: D.R. mentioned “the CFO will need to sign off — she’s cautious about new vendors.” This was not followed up on in email. The CFO has not been introduced to the process.
  • May 14 call: M.L. asked about HubSpot duplicate record handling. Rep said “I’ll check and get back to you.” Not answered in email.
  • May 27 call: D.R.’s tone was positive overall — “this is the right direction” — but the legal question created a pause. D.R. said “I need to pause before we move forward on this.”

Objections and Concerns on Record

  • ZoomInfo coverage concern (Proposal stage) — D.R. said “they have more data coverage in our sector.” Partially addressed verbally, no written comparison sent. Still active.
  • Pricing model flexibility (Discovery) — D.R. asked about per-seat vs flat-rate. Flat-rate discussed verbally, not confirmed in writing. May resurface if pricing section needs revision.
  • Legal review requirement (Proposal) — D.R.’s legal team needs to review DPA. Active blocker until DPA is shared.

Recommended Agenda

  1. Open with delivery (5 min): Share the ZoomInfo comparison and DPA link before any other topic. “I know these items were outstanding — I wanted to address both before we started.”
  2. Legal pathway (10 min): Agree the process for legal review. Who is the legal contact? What is the timeline? Is a 30-minute legal-to-legal call useful?
  3. CFO introduction (5 min): Surface the signing authority question directly. “D.R., you mentioned the CFO will need to sign off — when is the right moment to bring the CFO in?”
  4. Technical confirmation (5 min): M.L. to confirm HubSpot duplicate handling question — share documentation now if needed.
  5. Close date (5 min): Based on legal timeline, agree a realistic close date and next steps.

Exec Summary

Ashford Platforms is a $95K new business deal at Proposal stage — engaged and positive but stalled on two open items the rep hasn’t delivered: a ZoomInfo comparison and a DPA for legal review. The primary contact D.R. is the champion and economic influencer, but a CFO sign-off requirement has been raised verbally and the CFO hasn’t been introduced yet. The goal for this call is to deliver both outstanding items, clarify the legal pathway, and agree a close date — not to push for a signature before those items are resolved.

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

Why use Lusha in Claude

The CFO note — “she’s cautious about new vendors” — came from a Zoom call on May 14 and was never in the email thread. Without the Zoom layer, the VP joining this call cold has no idea there’s an unintroduced economic decision-maker who is likely to slow the close. With it, the exec summary includes it explicitly: “don’t push for a signature before the CFO is introduced.” The recommended agenda is built directly from the open items — it doesn’t suggest discussing product features because product isn’t the blocker. The two open commitments are the blocker. A QBR agenda that opens with delivery rather than pitch is the one that moves the deal forward.

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

FAQ

  • How long before a QBR should I run this?

    The night before, or the morning of. Running it more than 48 hours in advance means the open commitments and signals may be stale by the time the call happens. The prompt flags when the meeting is under 48 hours away — that urgency marker is the signal to run it immediately.

  • What if the VP or exec joining the call doesn't have time to read the full document?

    The Exec Summary is built for exactly that scenario — three sentences, written for someone with 60 seconds before joining. Share the Drive link in a Slack message to the exec the morning of the call: “QBR doc for Ashford in Drive — Exec Summary is at the bottom.”

  • What if there are no Zoom recordings for this account?

    The prompt processes what’s available. If no Zoom transcripts are found, the Recent Call Context section returns “no Zoom recordings found for this account — verbal commitments from calls are not captured here.” The rest of the document still builds from Gmail and Calendar. Encourage teams to enable Zoom cloud recording for all external calls.

  • Can I use this for renewal QBRs with existing customers?

    Yes — change the deal type field to “Renewal.” The Relationship Summary shifts to capture what was delivered during the contract year, what the customer said about value in recent calls, and what renewal terms have been discussed. The Exec Summary frames the call as a renewal rather than a close. The objections section surfaces any concern raised during the year that might affect renewal probability.

  • How is this different from the QBR prep prompt that already exists in the library?

    The existing QBR prep prompt prepares a rep for a multi-stakeholder exec review — it briefs on stakeholder roles and talking points. This play creates a permanent Drive document combining all five connectors — it’s the source-of-truth document the whole team references during and after the call, not just a personal brief. Use the existing prompt for personal prep; use this play when the manager or exec also needs a shared document.

Related Prompts

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.

Start for free Read the Docs