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 pulls today’s external meetings from Google Calendar, validates every attendee and scans every account via Lusha, and returns a one-screen brief for each call — who’s in the room, what changed at the account, and one thing to know before you join. Run it in the morning. Walk into every call prepared.
<context>
I want a one-screen brief covering every external meeting I have today — who's in each room, what's changed at each account, and the one thing worth knowing before each call. Pull today's meetings from my calendar and run the check automatically.
My context:
- What I sell: [PRODUCT / SOLUTION]
- Which meetings to include: [ALL EXTERNAL / CUSTOMER CALLS ONLY / PROSPECT CALLS ONLY]
- Anything I already know about today's calls: [NOTES OR "NOTHING — START FROM SCRATCH"]
</context>
<task>
1. Pull today's external meetings from Google Calendar — any meeting with external attendees.
2. For each meeting, use Lusha to validate the attendees and scan the account:
- Confirm each external attendee's current title and that they're still at the company
- Flag anyone whose role has changed or who is new to this meeting
- Check Lusha's signals layer for anything that changed at the account in the last 30 days
- Note the account type: prospect / active customer / renewal / other
3. For each meeting, return a brief block:
MEETING: [time] — [company] — [meeting type]
WHO'S IN THE ROOM: verified attendees with current titles
WHAT CHANGED: any signal or contact change worth knowing
ONE THING TO KNOW: the single most important context before this call
4. Order the briefs chronologically — first meeting first.
5. End with a daily summary:
- Total external meetings today
- Any meeting with a flagged signal
- Any meeting where an attendee couldn't be verified
</task>
<constraints>
- If a meeting has no signal and no contact change, "what changed" returns "nothing flagged — clean account."
- ONE THING TO KNOW must be specific to this account and this meeting.
- Internal-only meetings are excluded.
- If today has no external meetings, say so.
</constraints>The situation: An AE at a sales intelligence company runs the prompt at 8:15am on a Tuesday. She has three external meetings: a discovery call, a renewal, and a prospect demo. Runs it before her first coffee.
Output: Three meeting briefs, one flagged signal, one contact change, one clean account.
3 external meetings · 1 signal flagged · 1 contact change · 1 clean
9:00am — Halcyon Ventures — Discovery call
WHO’S IN THE ROOM
WHAT CHANGED New CRO hired 18 days ago — external hire from a larger org. Sales team has 8 open roles currently posted.
ONE THING TO KNOW This is an audit call, not a discovery call. A CRO 18 days in is evaluating what the team is working with, not shopping for a new tool. Open with “what does the current setup look like” before pitching anything.
11:30am — Cartway Technologies — Renewal call
WHO’S IN THE ROOM
WHAT CHANGED ⚠ Cartway was acquired as target entity 9 weeks ago. Procurement structure may have changed. S.V.’s departure from Lusha records is a flag worth addressing on the call.
ONE THING TO KNOW Don’t push for renewal signature today. Ask A.K. directly who owns vendor approvals post-acquisition before anything moves forward.
2:00pm — Waverly Digital — Product demo
WHO’S IN THE ROOM
WHAT CHANGED Nothing flagged — clean account. Sales team has grown 18% in the last quarter.
ONE THING TO KNOW S.R. is 22 days in and still forming opinions about the current stack. D.K. has been there 14 months and knows the existing setup well. Address D.K.’s institutional knowledge, win S.R.’s confidence on the new direction.
Attendees validated via Lusha connector, May 20. Calendar pulled from live session. Details masked for privacy.
Prepping for three different meetings manually means three separate LinkedIn checks, three company page visits, three sets of notes that may or may not be current. Lusha in Claude does all three in one pass — pulls the meetings from Calendar, validates every attendee, checks every account for signals, and returns a brief you can read over coffee. The Cartway flag — procurement contact gone after an acquisition — is exactly the kind of thing a rep discovers mid-call if they didn’t check. The Halcyon title mismatch — CRO on the invite listed as “Sales Operations” — changes how the SE should open the call. Both surface in 90 seconds before anyone joins anything.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
Yes — running it the evening before gives you time to act on a flag before the meeting rather than during it. The Cartway acquisition flag, for example, is worth a quick email to A.K. the evening before rather than discovering it cold on the renewal call. Data is pulled live when you run it, so an evening-before check is as accurate as a morning one.
The prompt automatically excludes internal-only meetings — no external attendees, no brief. You’ll only see briefs for calls with people outside your company.
The brief flags any meeting where attendees couldn’t be fully pulled. For those meetings, paste the attendee names directly into the prompt and the Lusha validation still runs — Calendar is the trigger, not the only input.
Yes — specify in the “which meetings to include” field. Useful if you have a mix of internal demos and external calls and only want the brief for one type.
The renewal meeting brief and QBR prep prompt are deep briefs for one specific high-stakes meeting. This prompt is a daily sweep — lighter per meeting, covering everything on the calendar. Use this one every morning, the single-meeting prompts when a specific call needs more depth.
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
