Internal Debrief Writer

Generates the internal-only version of what happened in a meeting. This is where you document what you actually observed -- political dynamics, relationship reads, competitive signals, and the gap between what the customer said and what they meant.

Distinct from:

• Follow-up email (cc-email-drafter / follow-up-email-writer): what the customer sees
• Meeting outcome log (meeting-outcome-logger): what the CRM sees
• This debrief: what your team sees. The unfiltered analysis

How to Use

After a significant customer meeting, provide:

• What happened (the factual summary -- can be brief since the CRM log captures this)
• What you observed that is not in the formal notes (body language, tone shifts, sidebar comments, things said off the record, the gap between what was said and what was meant)
• Your relationship read (how is the relationship really doing, not how the health score says it is doing)
• Political observations (who has influence, who is aligned, who is resistant, who was notably silent)
• Competitive intelligence (any mentions, hints, or signals about alternatives)
• Strategic assessment (what this meeting means for the account, for the renewal, for expansion)
• What you need from your team (help, resources, executive engagement, product escalation)

Debrief Structure

1. Meeting Headline

One sentence: what was the most important thing that happened?

Not a summary of the agenda. The one insight that changes how you think about this account.

Example: "Tom is supportive but is not going to fight for the renewal without data he can show his CFO."

2. What the Customer Said vs. What They Meant

This is not a universal decoder. It is a framework for the CSM to document their specific read on what specific statements meant in the context of this specific relationship.

3. Political Landscape Update

Who matters and where they stand:

Specific things to note:

• Who spoke the most? Who was notably silent?
• Who deferred to whom? (Reveals the real hierarchy, not the org chart)
• Did anyone disagree with the group consensus? (Even subtle disagreement is a signal)
• Was there a conversation before or after the meeting that was more revealing than the meeting itself?

4. Competitive Intelligence

Any competitive signal from the meeting, even indirect:

5. Strategic Assessment

Your honest read on the account's trajectory:

• Health reality (may differ from the health score): [your assessment]
• Renewal outlook (your gut, not the forecast model): [your read]
• Expansion potential (based on what you heard today): [your assessment]
• Biggest risk right now: [one sentence]
• Biggest opportunity right now: [one sentence]
• What changed because of this meeting: [one sentence]

6. Help Needed

What you need from your team, stated directly:

Output Format

## Internal Debrief: [Account Name]
**Meeting date:** [date] | **Type:** [type]
**Classification:** [Routine / Significant / Concerning / Urgent]

### Headline
[One sentence -- the most important takeaway]

### Said vs. Meant
[Completed table with your reads]

### Political Landscape
[Completed table with observations and implications]

### Competitive Intelligence
[Any signals, or "None detected"]

### Strategic Assessment
Health reality: [your read]
Renewal outlook: [your read]
Biggest risk: [one sentence]
Biggest opportunity: [one sentence]
What changed: [one sentence]

### Help Needed
[Specific asks with urgency]

### Distribution
[Who should read this -- manager only, manager + leadership, broader CS team]

When to Write a Debrief (vs. Just Logging the Meeting)

Not every meeting needs a full debrief. The guideline:

Quality Gates

• Is the headline genuinely the most important takeaway? Not the first thing discussed -- the most important thing you learned. If the headline could apply to any account, it is too generic
• Is the "said vs. meant" analysis honest? Optimistic interpretation of ambiguous statements is the most common trap. If you are unsure, document the uncertainty rather than choosing the interpretation you prefer
• Is the distribution appropriate? Internal debriefs with sensitive political observations should go to your manager, not to the broader team Slack channel
• Would this debrief be useful to your successor if you left tomorrow? If so, it is well-written. If they would need to ask you to explain it, add more context
• Is there a specific ask in the "Help Needed" section, or is it empty? If you emerged from a significant meeting without needing anything from anyone, either the meeting was routine (and does not need a debrief) or you are not asking for help you should be asking for

Principles

• Write the debrief within 2 hours. Political reads and relationship observations fade fast. What felt like a clear signal during the meeting becomes a vague impression by the next morning
• This document is for your team, not for you. Write it assuming someone who was not in the meeting needs to understand what happened and what it means. Your manager, your successor, your leadership -- they should be able to read this and act
• Honesty is the entire point. If you sugarcoat the internal debrief the same way you would a customer-facing note, you are defeating the purpose. "I think Tom is going to leave and take the relationship with him" is more useful than "Tom seemed a bit less engaged than usual"
• The debrief is a living document for the account's history. Six months from now, when you are preparing for the renewal and wondering "when did things start to shift?", the debrief trail is where you will find the answer