Client meeting prep
Turn scattered notes, past emails, and CRM excerpts into a one-page prep brief your team can reuse.
Overview
Before high-stakes calls, teams lose time re-reading threads and still miss risks. A structured brief separates facts from guesses, sequences the conversation, and gives everyone the same mental model before you dial in.
Who should use it
Account leads, consultants, and client success roles in SMB services—especially when more than one person touches the account or the last touchpoint was weeks ago.
Use it for
Quarterly business reviews and renewal conversations where the narrative has to match finance and delivery.
Expansion or upsell motions where you need shared language on value delivered so far.
Repair or escalation calls where tone, facts, and next steps must be agreed internally first.
Inputs
Meeting purpose and the decision or commitment you want by the end of the call.
Last three touchpoints in bullets (who, what changed, open threads)—even rough notes are enough.
Risks, blockers, and questions you owe the client—or need from them—before you promise anything.
Sensitivity map: NDA topics, personalities, procurement timing, anything you must not wing.
Context
Paste only anonymized or client-approved excerpts. Ask the model to label inference as assumption, flag missing data instead of filling gaps, and keep the tone professional-services calm—not sales hype. If your firm bans certain data in generative tools, stay within that line; this pattern still works with synthetic examples.
Prompt Skeleton
You are preparing me for a client meeting. Context: - Client industry and stage: ... - My role and goal for the call: ... - What success looks like by end of call: ... Materials (may be incomplete): """ <paste notes, email thread excerpts, ticket summaries> """ Task: 1) Executive summary: 5 bullets max (facts vs assumptions labeled). 2) Agenda: 6–8 minutes per section with a suggested order. 3) Talking points: grouped by theme; include 2 prompts I can ask the client. 4) Risks & objections: top 5 with a suggested response stance (not scripts). 5) Next-step menu: 3 options with tradeoffs. Rules: - If information is missing, list questions to ask internally before the call. - Do not fabricate metrics or commitments.
Review checklist
Every client-specific claim traces to pasted material or is explicitly marked as assumption.
PII and regulated details are stripped or replaced; only share-safe placeholders remain.
Next steps are feasible within one business week and name an owner on your side.
Objection handling frames responses without over-promising legal, security, or commercial terms.
Common mistakes
Letting the model invent client history when the source notes are thin—label gaps and prep questions instead.
Dropping "assumption" labels to sound more decisive; that backfires under client challenge.
Turning the output into a word-for-word script—you still need room to listen and pivot.
