Skills may execute instructions and code that could affect your environment. Marketplace scans reduce risk but do not guarantee safety. Always review files, run your own security checks, and use at your own risk.
board-prep
Security Scan Summary
Status: Safe
Source: Syntic Skills registry
Automated security scan completed with no high-risk patterns detected. Manual review is still required.
About This Skill
Use when preparing for a board meeting, investor update, or fundraising presentation — mastering numbers cold, anticipating hard questions, and building an honest narrative.
Downloadable SKILL.md
Download SKILL.md and place it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review contents, and run in a controlled environment first. Acknowledge the risk notice above to enable the download.
---
name: board-prep
description: Use when preparing for a board meeting, investor update, or fundraising presentation — mastering numbers cold, anticipating hard questions, and building an honest narrative.
category: C-Level Advisory
version: 1.0.0
tools: []
---
# Board Meeting Preparation
Prepare for the adversarial version of the board meeting, not the friendly one — master every number cold, anticipate the hard questions, and build a narrative that acknowledges weakness without losing the room.
## The Reality of Board Meetings
Board members have seen 50+ companies. They notice founders who flinch at their own numbers, spin bad news as "learning opportunities," or present sanitized decks that hide what's actually happening — and they know when the CEO isn't being straight with them. The best board meetings aren't the ones where everything looks good; they're the ones where the CEO demonstrates clear-eyed awareness of reality, a plan, and the ability to execute under pressure.
## The Preparation Framework
### Phase 1: Numbers Cold
Every number in the deck should live in the CEO's head, not just on the slide: current MRR/ARR and month-over-month growth, monthly burn rate and runway in months, headcount by department, CAC and LTV by channel/segment, Net Revenue Retention, pipeline value/conversion rate/sales cycle, churn rate and top reasons and top churned accounts, gross and net margin, and key open hiring positions with time-to-fill. Stress-test: can every number be answered without hesitation? A pause means it isn't known.
### Phase 2: Anticipate the Hard Questions
For every agenda item, generate its adversarial version. Typical categories: revenue performance ("what specifically failed, and is it pipeline, conversion, or capacity?"), runway/burn ("what's the plan if the next round takes 9 months, what gets cut first?"), product/roadmap ("what shipped that customers didn't use, what got killed and why, what's slipping?"), team ("who's a flight risk and how does that affect execution, is this the right team for this stage?"), and competition ("how does a competitor's raise change the position, what's the moat if they copy the best feature in 90 days?").
### Phase 3: Build the Narrative
A board meeting is a leadership demonstration, not a status update. Structure: (1) where we are, honestly — the real number, not the smoothed one; (2) what we learned that we didn't know 90 days ago; (3) what we got wrong, named directly, before the board has to ask; (4) what we're doing about it, with specific dated owners; (5) what we need from this room — a concrete ask, not "support." Never let the board be surprised: bad news should reach them before the meeting, e.g. a short email 3 days prior stating the number, what happened, and what's being done.
### Phase 4: Adversarial Preparation
Run a mock board meeting: present the deck as planned while someone plays the hardest director, asking every uncomfortable question, answered without referring to the deck. Afterward, note every question that produced hesitation or defensiveness — those are exactly the questions to prepare harder for.
### Phase 5: Director-by-Director Prep
Not every board member wants the same thing. For each director, know their primary concern (usually tied to their investment thesis), the metric they watch most closely, what would make them lose confidence, and what they raised last meeting that needs addressing. Common types: the operator (what's breaking, who owns the fix), the financial investor (path to profitability or next raise), the strategic investor (competitive position and moat), and the independent (governance, team dynamics, judgment).
## Pre-Meeting Checklist
48 hours before: verify every number against source systems, review the deck for internal consistency, send a pre-read (deck plus a 1-page brief on key topics), do one-on-ones with any director likely to have concerns, and rehearse the three hardest expected questions out loud. Day of: distribute the agenda with time allocations, know the ask for each item (decision, input, or FYI), and have follow-up materials ready.
## During the Meeting
The board is watching whether bad news gets owned or deflected, whether the CEO is defending a narrative or sharing reality, whether numbers are known cold or looked up, whether challenge produces engagement or defensiveness, and whether the CEO knows what they don't know. The single best move: name the hard thing before the board does.
## After the Meeting
Within 24 hours: send action items with owners and dates, send any data promised but not delivered, note the questions that weren't ready for, and follow up with any director who seemed unsatisfied. The next board prep starts now.
Bundle Download
Includes SKILL.md and bundled support files where provided. Risk acknowledgement is required.
Install Targets
Syntic App
- 1. Create a dedicated folder for this skill in your local skills library.
- 2. Place SKILL.md into that folder.
- 3. Restart Syntic and invoke this skill on matching tasks.
Syntic Code (CLI)
- 1. Save SKILL.md in your local Syntic Code skills directory.
- 2. Keep related files in the same skill folder.
- 3. Run in a safe environment and validate outputs.
Source
https://github.com/alirezarezvani/claude-skills/blob/main/c-level-advisor/executive-mentor/skills/board-prep/SKILL.md
Open Source LinkRelated Skills
agent-protocol
Use when C-suite agents query each other, coordinate cross-functional analysis, or run board meetings with...
C-Level Advisoryboard-deck-builder
Use when assembling board/investor decks. Covers structure, narrative framework, bad news delivery, financial...
C-Level Advisoryboard-meeting
Use when running structured C-suite deliberation on a strategic question. 6-phase protocol: context, isolated...
C-Level Advisoryboardroom
Use when a decision spans multiple C-suite domains (e.g., pricing change, funding vs. cuts). Runs 6-phase...