Verified against Claude · 2026-08-05
Structure a board meeting deck the room can actually use to make decisions
Separates a board deck into metrics-for-reading versus decisions-needing-input, so the meeting itself is spent on the questions that actually need the board's judgment rather than a live narration of numbers they could have read beforehand.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are helping structure a board meeting deck built to be sent and read in advance — the meeting itself is for discussion and decisions, not a live narration of numbers the board could have absorbed on their own. CONTEXT Company: Triagely Period since last board meeting: Since the last meeting, 10 weeks ago Key metrics and trend: MRR $58k → $71k, paying clinics 9 → 12, cash on hand $410k, monthly burn $62k Wins and challenges since last meeting: Won a 5-location regional group; lost 1 clinic to a competitor on price; second engineer hire fell through after an offer decline Specific decisions that actually need board input or a vote at this meeting: Whether to extend runway by pausing the second engineer hire for a quarter, or raise a small bridge now while metrics are strong METRICS DASHBOARD (FOR ASYNC READING) Lay out MRR $58k → $71k, paying clinics 9 → 12, cash on hand $410k, monthly burn $62k as a compact dashboard with trend arrows and one-line context per metric — written to be understood without anyone narrating it live, since the deck goes out at least 48 hours before the meeting and board members are expected to have read it. WINS AND CHALLENGES (FOR ASYNC READING) Summarize Won a 5-location regional group; lost 1 clinic to a competitor on price; second engineer hire fell through after an offer decline the same way — specific facts, not narrative buildup — clearly separated from the dashboard, and explicitly not requiring live walkthrough time in the actual meeting. DECISIONS NEEDING BOARD INPUT (THE ACTUAL MEETING AGENDA) For each item in Whether to extend runway by pausing the second engineer hire for a quarter, or raise a small bridge now while metrics are strong, write: the decision framed as a specific question the board needs to answer, the options genuinely on the table, your recommendation and why, and what happens if no decision gets made today. This section is the real meeting agenda — everything above it exists so the meeting doesn't have to spend time on it. FOLLOW-UP OWNERSHIP For any decision made or action agreed to, note that it needs an explicit owner and a deadline captured in the meeting notes — flag this as a structural requirement of the deck's follow-up section, not an afterthought bolted on if there's time. OUTPUT FORMAT Three sections: Metrics Dashboard, Wins & Challenges, Decisions Needing Board Input (as the clear focal point), plus a one-line reminder that follow-ups need a named owner and deadline.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Sending the deck in advance for async reading, rather than narrating it live, is a specific practice top-tier boards and VCs consistently push founders toward, because reading numbers out loud in the room wastes the one scarce resource a board meeting actually has — shared time for judgment calls only the board can make — on information transfer that a PDF sent 48 hours earlier accomplishes just as well without anyone's attention in the room. Explicitly separating 'decisions needing board input' from the metrics and wins-and-challenges sections forces the founder to know in advance exactly what they need from this specific meeting, rather than delivering a rambling update and hoping useful feedback emerges organically — a board that knows walking in that today's real agenda item is 'pause a hire versus raise a bridge' can actually prepare a position, while a board ambushed with that framing live in the room is far more likely to stall on a decision that needed a clear answer that day. Requiring a stated recommendation and a stated consequence of no decision for each agenda item — not just laying out options neutrally — matters because boards that are asked an open question with no anchor tend to default to more discussion and less decision, whereas a founder who states a recommendation gives the board something concrete to agree with, push back on, or amend, which is a fundamentally faster path to an actual resolution than an open-ended prompt for the room's opinion. Requiring a named owner and deadline on every follow-up addresses the most common way a board meeting fails silently — good discussion happens, a direction gets loosely agreed on, and then nothing changes before the next meeting because no single person was actually on the hook for the next step.
Verified against
Claude Sonnet 5 · 2026-08-05
Changelog
- 2026-08-05 — Initial publish, verified against Claude Sonnet 5.
Need this built into your business?
If a prompt isn't enough — custom software, built and maintained for you — that's Scult's day job.
EXPLORE CUSTOM SOFTWARE
