Gtm Board And Investor Communication

If you're prepping for a board meeting and tired of building 40-slide decks nobody reads, this gives you a repeatable structure. It's built around the "Three Things" narrative model (what's working, what's not, what you're doing about it) and a four-tier metric hierarchy that prevents boards from drowning in data. The pre-read pattern is smart: send financials and metrics 48 hours ahead, use the actual meeting for strategy and decisions, not reciting numbers. Also covers how to handle misses without losing credibility and how to run deep dives so your board doesn't become a rubber stamp. Opinionated about narrative before data, which is the right call.

skills.sh installs: 1.6K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill gtm-board-and-investor-communication --agent claude-code

Installs into .claude/skills of the current project.

Files

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:

SKILL.md on GitHub