Board / investor update

Board / investor update

Invocation: user only. Drafts a board update; sends only after explicit approval.

Workflow

1. Confirm the window and format

Default to the last full calendar month. Ask the user:

• Which investors / board members receive this? (May affect scrubbing.)
• Match last month's format? (Default yes; fetch the most recent update from Notion and mirror structure.)

2. Pull

In parallel:

• Previous update from Notion (mandatory — narrative continuity matters).
• Metrics: whichever dashboard is canonical. If we don't have a live source, list which metrics need manual input and ask the user for numbers.
• Shipped work: major launches in the window from Notion Shipped page, #ship Slack channel, or GitHub.
• Hires and departures: from Notion team page or user input.
• Customer signals: major wins, logos landed, meaningful losses or churn.
• Risk log (if role-pgm is enabled): high/critical risks.

3. Draft

Default structure (override to match the team's established format):

# <Company> Board Update — <Month Year>

## TL;DR
<Three sentences max. What happened, what's next, what we need.>

## Metrics
- **<metric 1>:** <current> (prev: <last period>, <% change>)
- **<metric 2>:** ...
(Hit your North Star metric first. No vanity metrics.)

## What shipped
- <item> — <one-line customer impact>

## Wins
- <1-3 concrete, externally verifiable wins>

## Challenges
<This section is the most important one. Be honest. List what's not working, what we're doing about it, and what we don't yet know.>

## People
- Hired: <role>, <name if announced>
- Departed: <role>, <reason one-liner>
- Open roles: <priorities>

## Runway
- Cash: $<amount>
- Net burn last month: $<amount>
- Months of runway at current burn: <N>

## Asks
- <specific, actionable ask — intro to X, advice on Y, review of Z>
- <or "None this month" if genuinely none>

## What I'm thinking about
<Optional: one paragraph of the CEO's current strategic preoccupation. Makes the update feel like a letter, not a report.>

4. Review

Show the draft. Common edits:

• Numbers confirmed or corrected
• Challenges section: add what's honestly worrying, remove what's resolved
• Asks: tighten from "advice on strategy" to a specific named intro

Check before sending:

• Are metrics consistent with last month's numbers (no unexplained re-bases)?
• Are all asks specific? Vague asks get ignored.
• Does the TL;DR stand alone — would a board member who reads only that three-sentence summary have the right picture?

5. Send (only on approval)

Offer three delivery paths:

• Email via Gmail MCP (use /team-core:draft-email flow)
• Notion page + share link
• Both (most common for boards)

On approval, send / publish, return links.

Don't

• Don't bury bad news. If it's material, it goes in Challenges.
• Don't announce hires or departures before the user confirms the person's okay with it.
• Don't make up a metric. If a dashboard isn't available, flag [NEEDS INPUT: <metric name>].
• Don't send to a different distribution than the user specified.