Meeting Prep and Briefing
Deliver a one-page client meeting brief to every partner two hours before each client meeting - automatically.
The business case
The difference between a partner who walks into a client meeting fully prepared and one who is catching up in real time is not subtle - clients feel it immediately. The prepared partner asks the right questions, references the right context, and demonstrates that they know what has happened since the last conversation. The unprepared partner asks questions that were already answered, misses follow-through items, and signals that this client is one of many. The problem is not that partners don't care - it's that preparation takes time they don't have. Pulling email threads, reviewing the last proposal, checking CRM notes, scanning recent news about the client's business: that's 20 - 45 minutes per meeting. For a partner with 10 client meetings per week, that's 4 - 7 hours of data gathering work every single week.
What this play does
n8n runs on a schedule that checks the calendar 2 - 3 hours before each client meeting. When it finds an upcoming meeting with a known CRM contact, it pulls the relevant account data: account summary, revenue history, the last three logged interactions, any open items flagged as pending, and any service issues. That data goes to an AI that produces a concise, one-page brief. The brief arrives in each partner's email two hours before the meeting. It covers who the client is, what's happened recently, what's outstanding, the relationship health signals, and what the meeting context suggests. It takes two minutes to read.
Before and after
Before
Senior partners are in back-to-back calls. Five minutes before the next meeting, they're skimming an email thread while still on the previous call. They walk in with partial context and spend the first 10 minutes catching up on information the client assumed they already had. The client doesn't say anything. But they notice.
After
At 9 AM, a brief is waiting in the partner's inbox for the 11 AM client meeting. They read it over coffee. They walk in knowing exactly where things stand, what the client is expecting, and what needs to happen. The meeting starts at the right level. The client feels remembered and prepared for.
Business impact
If this Play saves 30 minutes of prep time per client meeting, and a firm has 10 client meetings per week, that's 5 hours of strategic time returned weekly - roughly $78,000 per year in recovered capacity at a $300 loaded hourly rate. The more significant impact is harder to measure: consistent preparation quality compounds across every client relationship, drives higher retention, and generates more referrals. Partners who are consistently prepared have shorter average meeting times, fewer misunderstandings about deliverables, and higher client satisfaction scores.
Prerequisites
Complete these before opening n8n. Skipping prerequisites is how you end up rebuilding workflows.
Confirm calendar integration
Google Calendar and Outlook Calendar both integrate with n8n directly. Confirm which calendar system your firm uses and that you have API access configured.
Audit CRM data quality before building
A meeting brief is only as good as the data behind it. Run a data quality check first. If your CRM has sparse, inconsistent records, the briefs will be thin and potentially misleading. Implement Play One before Play Nine - Play One feeds the data that Play Nine synthesizes.
Define how you identify client meetings vs. internal meetings
The workflow needs a signal to know which calendar events warrant a brief. Client meetings with a CRM contact linked as an attendee is the cleanest approach. Internal meetings, interviews, and vendor calls should not receive client briefs.
Step-by-step implementation
The steps below are the full build guide. Each step includes configuration notes and exact AI prompts where applicable.
Build the calendar scanning workflow
Create an n8n workflow with a Schedule trigger - either hourly or once in the morning (once per day works for most firms since you're generating briefs for meetings 2 - 3 hours out). On each run, n8n queries your calendar for events starting within the next 2 - 3 hours that haven't yet had a brief generated. For each qualifying event, extract the attendee list. Cross-reference each attendee's email against your CRM contact database. If at least one attendee matches a known CRM contact, flag this as a client meeting and continue to brief generation. If no attendees match CRM contacts, skip. Add a deduplication check: if a brief was already generated for this event (check by event ID), skip it. This prevents duplicate briefs if the workflow runs multiple times before the meeting.
Pull the CRM account data
For each client meeting identified, pull the following from your CRM: **Account data**: Company name, account tier, total revenue from this client, start date of relationship, assigned partner, and any custom fields relevant to your firm (practice area, case type, matter status, etc.). **Recent activity**: The last 3 - 5 logged activities (from Play One's email and calendar logging), with timestamps, activity type, and the AI-generated summaries. This is where Play One's data quality directly determines Play Nine's output quality. **Open items**: Any tasks or follow-up items on the account that are open or overdue. **Service issues**: Any active complaints, disputes, or satisfaction concerns flagged in the CRM. **Meeting context**: The meeting title from the calendar event and any description text.
Generate the meeting brief
Pass the structured account data to the AI with the brief generation prompt. The AI synthesizes a one-page brief in a consistent format that the partner can read in two minutes. Send the brief to the partner's email 2 hours before the meeting with a subject line that makes it easy to find: "[Client Name] - Meeting Brief - 11:00 AM Today." If the CRM data is insufficient to generate a meaningful brief (no logged activity, minimal account data), flag it as a "thin brief" and route a note to the exception queue so the partner knows to do their own prep.
AI Prompt
You are a senior relationship manager preparing a one-page meeting brief for a partner at a professional services firm.
Account information:
- Client: {{company_name}}
- Meeting: {{meeting_title}} at {{meeting_time}}
- Attendees: {{attendee_names}}
- Relationship history: {{account_summary}}
- Recent interactions (last 90 days):
{{recent_activities}}
- Open items: {{open_items}}
- Service issues: {{service_issues}}
- Meeting description/notes: {{meeting_description}}
Write a one-page meeting brief that covers:
**Client Snapshot** (2-3 sentences): Who they are, what they engage us for, and their current relationship health in plain terms.
**Recent Activity** (3-5 bullet points): What has happened in this relationship since the last meeting. Be specific - cite actual interactions from the activity log.
**Open Items** (bullet list): Any commitments, follow-ups, or pending items that need to be addressed in or after this meeting.
**Meeting Context** (2-3 sentences): What this meeting is about based on the calendar entry and recent activity. What should the partner expect the client to want to discuss?
**Watch For** (1-3 bullets): Any relationship signals, service issues, or sensitivities the partner should be aware of walking in.
Keep the brief scannable. Use headers and bullets, not paragraphs. The partner should be able to read this in 2 minutes.
If any section has insufficient data, note it clearly: "[Insufficient CRM data for this section - manual review recommended]"Week-by-week rollout plan
- Confirm calendar API access.
- Audit CRM data quality for active client accounts. Identify gaps.
- Define event qualification criteria (which events get briefs).
- Build calendar scanning and contact matching workflow.
- Build CRM data pull for each matched meeting.
- Build brief generation prompt. Test against 5 real upcoming meetings.
- Have 2 - 3 partners review briefs for accuracy and usefulness.
- Refine prompt based on feedback.
- Go live. Collect feedback after first 10 briefs sent.
Success benchmarks
These are the specific, measurable signals that confirm the play is working. Check against each benchmark at the 30-, 60-, and 90-day mark.
Common mistakes
Building before CRM data is in acceptable shape
Play Nine is entirely dependent on the data quality established by Play One. A brief generated from a CRM with sparse, inconsistent records is not just useless - it can actively mislead. Run Play One for at least 4 weeks before implementing Play Nine.
Sending briefs for every calendar event
An internal team meeting does not need a client brief. Define the event qualification criteria carefully - only actual client meetings with CRM-matched attendees should trigger a brief.
Delivering the brief too early or too late
Two hours before the meeting is the right window for most partners. Sending it the night before means it will be buried by morning. Sending it 20 minutes before means there's no time to act on what it surfaces.
Exception rule
Read before going live
Meeting briefs generated by AI should always be reviewed by the partner before use, not treated as ground truth. The brief is synthesized from CRM data, which may be incomplete or outdated. The partner owns the accuracy of what they bring into a client meeting.
Revenue Institute
Want someone to build this play for your firm? Revenue Institute implements the full AI Workforce Playbook system as part of every engagement.