Back to catalog

consulting-meeting-prep

Prepare executives for client meetings, presentations, and new lead discovery calls.

Category 📋 Consulting Meeting Prep
Version v1.1.0

Consulting Meeting Preparation

Prepare Joseph for client meetings, trade show conversations, discovery calls, and presentations. Covers lead preparation, intel gathering, talking points, speaker notes, and mock interviews.

When to Activate

  • Preparing talking points for a trade show or conference
  • Creating speaker notes for a client presentation
  • Simulating tough audience questions before a real meeting
  • Extracting intel from PDFs and case studies for meeting prep
  • New lead arrives — research company, create lead file, prepare discovery materials

Phase 0 — New Lead Preparation

When a new lead arrives (via Slack, email, or referral), prepare the full pre-call package BEFORE scheduling anything.

Step 1: Research the company

1. Web search for company overview: revenue, size, HQ, leadership, recent news

2. Search for the specific contact: LinkedIn, prior relationship, role

3. Search for their tech stack, competitors, and industry context

4. Extract key pages (about, leadership, case studies) via web_extract

5. If the company is public, pull financials from investor relations

Step 2: Create lead file

Write to wiki/wealth/consulting/[client]/leads/<company-slug>/:

  • <company>-lead.md — structured brief with: status, contact, company overview, tech landscape, pain points, NS fit analysis, research findings, next steps
  • Follow the existing file pattern (see leads/ospri/ospri-lead.md for template)

Step 3: Create discovery questionnaire

Write to the same directory as YYYY-MM-DD-discovery-questionnaire.md:

  • 7 sections: business context, current architecture, code/customisation, integrations, performance/security, team/delivery, rollout model
  • 30-40 questions total — specific to their stack and pain points, not generic
  • Designed to be sent BEFORE the workshop so the prospect fills in what they can

Step 4: Create workshop agenda

Write to the same directory as YYYY-MM-DD-workshop-agenda.md:

  • 90-minute session structure: opening → current state → pain points → future state → team → next steps
  • Include discussion prompts (open-ended questions, not yes/no)
  • Include pre-workshop preparation checklist (what to request from the prospect)
  • Include expected outcomes

Step 5: Update _context.md

Add the lead to wiki/wealth/consulting/[client]/_context.md under ## Active Leads.

Step 6: Store in Mnemosyne

Save the lead fact for cross-session recall.

Pitfalls:
  • Research the COMPANY first, not the contact. The company context determines NS fit.
  • Discovery questionnaire must be stack-specific (Adobe Commerce, Shopify, etc.) — generic questionnaires signal you haven't done homework.
  • Don't pitch in the lead file — focus on pain points and fit analysis.
  • Don't schedule the call until the lead file and discovery materials are ready.

Phase 1 — Intel Gathering

1. Read all source materials: battlecards, case studies, presentations, press releases

2. For PDFs: use pymupdf via uv run python3. Write script to /opt/data/tmp/, run with cd /opt/data && uv run python3 tmp/script.py. Always import pymupdf as fitz. If text extraction empty, use page.get_pixmap(dpi=200) + vision_analyze.

3. Extract web content via web_extract for case studies and news

4. Persist understanding in a file under the meeting directory BEFORE building deliverables

Pitfalls: Don't read PDFs with read_file (binary). Don't write scripts to /tmp/ (use /opt/data/tmp/).

Phase 2 — Talking Points

Structure: preparation framework → universal industry starters → company-specific briefs → proof points → what NOT to say.

Design principles:

  • Every talking point leads with a question, never a pitch
  • Goal is "earn the right to follow up," not close the meeting
  • Nested bullet lists, not tables (Joseph reads on Slack)
  • Reference specific proof points from past work

Phase 3 — Speaker Notes

Slide-by-slide: what to say, what NOT to say, key lines, timing. Add context block (audience, relationship, what they know). Include likely questions with tested answers.

Phase 4 — Mock Interview

Simulate audience in 3-5 rounds of 2-3 questions each. Cover: why now, cost, timeline, team capacity, AI credibility, measurement. After each answer, evaluate and update notes. Goal: make Joseph feel prepared.

After Each Session

Update _context.md with new client facts. Save meeting materials to meeting directory.