Customer call prep

Customer call prep

Gets the CEO (or anyone) ready to walk into an external customer call without scrambling. Read-only — no outbound actions.

Workflow

1. Identify the meeting

From $ARGUMENTS:

• Customer / account name
• Meeting date/time — if not given, find the next upcoming calendar event mentioning the company or their contacts

If the meeting isn't in the next 14 days or you can't locate it, confirm with the user what you're prepping for before proceeding.

2. Pull (in parallel)

• Gmail: all threads with anyone at @<customer-domain> in the last 90 days. Surface: unresolved questions they asked, commitments we made, notable sentiment shifts (cold → warm, frustrated → resolved).
• Fathom: any prior meetings with this customer — pull summaries, action items, quotes. Don't pull full transcripts unless the user asks.
• Slack: search internal channels for the customer's company name in the last 90 days. Surface context we've said about them internally that might be relevant. Flag (but don't include) anything that was clearly meant to be private.
• Notion: any account page, CRM-style record, or related spec/decision. Last N support tickets if tracked there.
• Calendar: the upcoming meeting invite itself — attendees, agenda, notes the customer sent ahead.

3. Profile the people

For each person from the customer's side attending the call, identify:

• Name, title, company
• Role in the decision ("economic buyer", "technical evaluator", "end user")
• Previous interactions — have we met them before? What did they ask about?
• Anything in Gmail/Slack that hints at their personal angle — are they an advocate, skeptical, just along for the ride?

Don't guess personal background the user hasn't already seen. Stick to what's in the systems the CEO has access to.

4. Surface signals

Look across what you pulled for:

• Unresolved asks — did they ask us for something we haven't answered?
• Commitments we made — did we say "we'll get back to you on X" and not?
• Product usage signals (if we have a product analytics MCP) — are they using the product actively? Which features? Any drop-offs?
• Recent support tickets — anything they opened that might come up?
• Pricing / renewal / expansion context — is there a contract event in play?
• Competitive signals — have they mentioned a competitor in any thread?

5. Suggest 3 angles

The core value of this prep is focus. Suggest three specific angles the CEO could lead with, based on what's in the context:

1. The ask they're bringing — what they're probably coming to discuss. Preempt it with a prepared answer.
2. An expansion or next-step opportunity — something you noticed that could grow the relationship, only if genuine.
3. A risk to address — a concern or dissatisfaction you spotted that it would be smart to name proactively.

Don't manufacture a third angle if there isn't one. Better to say "only two real angles here" than pad.

6. Output

# Customer call prep — <Company> — <meeting date/time>

## Who's in the room
- **<name>, <title>** — <role in decision>. <1-line context: what we know about them from prior interactions.>
- ...

## Account snapshot
- **Status:** <customer / prospect / expansion opp / at-risk>
- **Contract / stage:** <e.g. "Pro tier, 24 users, renewal Sep 2026" or "in eval, POC kickoff 3 weeks ago">
- **Last meeting:** <date, attendees, what we committed to>

## What they've asked (that we haven't answered)
- <question> — <date asked>

## What we've committed (that we owe them)
- <commitment> — <date> — <status>

## Recent signals
- <bullet — usage, support, sentiment, press, anything genuinely signal-bearing>

## 3 angles for this meeting

### 1. <angle — the ask they're probably bringing>
<2-3 sentences: what to expect, suggested framing of our answer>

### 2. <angle — expansion or opportunity>
<...>

### 3. <angle — risk / concern to address>
<...>

## Things to avoid
- <any landmine the CEO should not step on — e.g. "don't commit to a launch date for X, eng hasn't scoped it yet">
- <or "none noted">

## Don't forget
- <small context — e.g. "last call they mentioned their Q2 board review is next Tuesday, ask how it went">

Don't

• Don't include internal Slack gossip about the customer, even if technically accessible. Filter to professional, appropriate context.
• Don't speculate about the customer's mood or intent. Report signals ("last email tone was short, prior was longer") — let the CEO interpret.
• Don't auto-write the meeting notes page. That's for after the meeting, usually via /team-core:meeting-recap.
• Don't surface every email. Filter to what actually bears on this conversation.