Skip to content
AI & Agents
Skill

/gtm-board-and-investor-communication

Board meeting preparation, investor updates, and executive communication. Use when preparing board decks, writing investor updates, handling bad news with the board, structuring QBRs, or building board-level metric discipline. Includes the "Three Things" narrative model, the

From plugin
awesome-copilot
39k200 skills200 agents
Install
$ npx -y skills add github/awesome-copilot --skill gtm-board-and-investor-communication --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/gtm-board-and-investor-communication

Context preview

The summary Claude sees to decide when to auto-load this skill.

Board meeting preparation, investor updates, and executive communication. Use when preparing board decks, writing investor updates, handling bad news with the board, structuring QBRs, or building board-level metric discipline. Includes the "Three Things" narrative model, the

SKILL.md

gtm-board-and-investor-communication.SKILL.md
name: gtm-board-and-investor-communication
description: Board meeting preparation, investor updates, and executive communication. Use when preparing board decks, writing investor updates, handling bad news with the board, structuring QBRs, or building board-level metric discipline. Includes the "Three Things" narrative model, the 4-tier metric hierarchy, and the pre-brief pattern that prevents board surprises.
license: MIT
metadata:
  author: Smit Patel (https://linkedin.com/in/smitkpatel)
  source: https://github.com/beingsmit/technical-product-gtm

Board and Investor Communication

Structure board meetings, investor updates, and executive communication that builds trust and drives decisions — not slide decks that nobody reads.

When to Use

**Triggers:**

  • "How do I prepare for our board meeting?"
  • "What should go in our investor update?"
  • "We missed our numbers, how do we communicate this?"
  • "Board deck structure"
  • "How often should we update investors?"
  • "Our board meetings aren't productive"

**Context:**

  • Seed through growth-stage companies
  • Board meeting preparation and follow-up
  • Monthly/quarterly investor updates
  • Handling misses and bad news
  • Cascading strategy from board to organization

---

Core Frameworks

1. Tell the Story, Then Show the Data

**The Pattern:**

Most board meetings start with a data dump. Slide after slide of metrics, then 10 minutes of Q&A where board members try to figure out what it all means.

Flip it. The narrative should lead; data should confirm.

**How It Works:**

Open with where you are in the journey. Not "here's our ARR" but "here's what we believed coming into the quarter, what we learned, and where that puts us now." Then show the data that validates the narrative.

**Board Meeting Structure:**

**Pre-Read (Sent 48-72 Hours Before)**

  • Financial dashboard (ARR, burn, runway, pipeline)
  • Metric scorecard with health indicators (green/yellow/red)
  • 2-3 page narrative summary covering market context and strategic update
  • Rule: If it can be read, don't present it

**The Meeting (90-120 Minutes)**

1. **Market context and questions on pre-read** (15 min)

  • What's changed in the market since last meeting?
  • Board asks about anything unclear from pre-read
  • No re-presenting the data

2. **CEO strategic update — The "Three Things"** (15 min)

  • **What's working** (2-3 areas showing momentum)
  • **What's not** (1-2 specific gaps, not vague)
  • **What we're doing about it** (specific changes, not promises)
  • This is narrative, not numbers

3. **Decision items** (30-45 min)

  • 1-3 topics where the board's input or approval is needed
  • Come prepared: "We're deciding between X and Y, board thoughts?"
  • Leave with a decision, not "let's revisit next quarter"

4. **Deep dive** (20-30 min)

  • One topic explored in depth (rotating each meeting)
  • Bring the functional leader who owns it
  • Examples: pricing strategy, competitive landscape, org design, market expansion

5. **Closing** (10 min)

  • Summarize decisions made and action owners
  • Closed session (board without management)
  • CEO and board chair debrief

**Common Mistakes:**

  • Opening with data before narrative (board gets lost in numbers without context)
  • Multiple competing narratives (board can't synthesize — pick one arc)
  • Trying to cover too many topics deeply (results in rushed decisions on everything)
  • No deep dives (board becomes a rubber stamp)
  • Filling the meeting with good news (boards don't trust CEOs who only share wins)

---

2. The "Three Things" Narrative Model

**The Pattern:**

Businesses are too complex to summarize in one headline. Three distinct points — what's working, what's not, what's changing — let the board grasp status and trajectory in minutes.

**What's Working (2-3 areas):** Be specific. Not "sales are going well" but "closed first six-figure enterprise deal, validating the commercial motion." Quantify momentum:

  • New product launches gaining adoption
  • Sales motion maturing (first big customer, repeatable motion emerging)
  • Community/ecosystem milestones

**What's Not Working (1-2 areas):** Be equally specific. Not "we had some challenges" but "self-serve conversion is weak — strong awareness but 0.1% conversion rate." Board needs to understand the actual problem, not a euphemism.

**What We're Doing About It (for each "not working"):** Articulate specific changes. What product changes? What org changes? What's the timeline? What resources are committed?

**Why This Works:**

Board members read dozens of updates. The Three Things model gives them a mental filing system: momentum (feel good), risk (pay attention), agency (this team handles problems). Without it, boards either over-index on one bad metric or miss the real issue buried in a 40-slide deck.

---

3. Progress Is Directional, Not Absolute

**The Pattern:**

It doesn't matter if you hit 100K users if you were aiming for 50K — or if you missed 200K. Context is everything. Show progress toward your goal, not just the number.

**How to Frame Progress:**

  • **On track:** "Target 100K active developers. Currently 70K. All initiatives performing as planned. Confidence: High."
  • **At risk:** "Target 100K active developers. Currently 50K. Acquisition cost higher than expected. Testing new channels. Adjusted target: 85K. Confidence: Medium."
  • **Ahead:** "Target 100K active developers. Currently 95K. Exceeding acquisition forecasts. New partnerships accelerating growth. Confidence: Very high."

**The Rules:** 1. Set the goal upfront (every metric needs a target) 2. Show progress as % toward goal, not just absolute number 3. Acknowledge misses; explain pivots 4. State confidence level based on trajectory

**Common Mistake:**

Changing goals when you miss them. Boards track this. If Q1 target was 100K and you hit 60K, don't make Q2 target 75K and call it "revised guidance." State the miss, explain why, show the recovery plan. Credibility comp

Read more
Ships withawesome-copilot

A community-created collection of custom agents, instructions, skills, hooks, workflows, and plugins to supercharge your GitHub Copilot experience.

Get the whole plugin

Other skills on awesome-copilot.