Board Update Memo With Metrics, Asks, and Honest Lowlights
Produces a candid, scannable board update with a metrics table, honest lowlights, and specific asks.
A board update is a trust instrument. Directors read dozens of them and can instantly tell when a founder is spinning, so the updates that build credibility are candid, scannable, and specific about where help is needed. This prompt structures exactly that: a one-line state of the company, a compact metrics table, then highlights, honest lowlights, decisions made, and concrete asks. The lowlights section is non-negotiable and deliberately spin-free, because the fastest way to lose a board is to let them discover a problem you hid. The asks section pushes for specificity, naming the intro or hire you actually want rather than a vague 'let us know if you can help.' It also instructs the model never to invent numbers, which matters because a board update is the worst possible place for a hallucinated metric. Send it monthly between meetings so the board is never surprised in the room, and so the live meeting can focus on the two or three things that actually need their judgment.
Act as a founder writing a monthly board update for [COMPANY]. Reporting period: [MONTH OR QUARTER]. Use these inputs: headline metrics [REVENUE, GROWTH, CASH, RUNWAY], what went well [WINS], what didn't [MISSES], and where you need help [ASKS]. Write a tight narrative update with: a one-line state-of-the-company, a metrics dashboard in a compact table, Highlights, Lowlights (be candid, no spin), Key decisions made, Asks for the board with specific names or intros wanted, and Focus for next period. Keep it scannable for busy directors, under 600 words, confident but transparent. Do not invent numbers I did not provide.
What you can expect back
State of the company: Growing steadily with our first enterprise proof point, but sales hiring is the bottleneck this month. Metrics: MRR $220k (+6% MoM), cash $1.4M, runway 11 months, gross churn 3.5% (up from 2%). Highlights: Signed our first enterprise customer, validating the move upmarket; shipped the public API, unblocking three partner integrations. Lowlights: Both VP Sales finalists passed, leaving the pipeline founder-led another month; churn rose to 3.5%, driven by two small accounts that never onboarded fully. Key decisions: Paused mid-market outbound to focus on enterprise; extended the API beta by three weeks. Asks: Warm intros to VPs of logistics at mid-size carriers; a referral for an experienced VP Sales who has sold to operations buyers. Focus next period: Close the VP Sales hire and ship guided onboarding to arrest churn.
Illustrative example — your results will vary by tool and inputs.
Get sharper results
- 01Send it a few days before the meeting, not in it. Pre-read updates make the live time about decisions, not narration.
- 02Never let the model soften a lowlight. Directors fund candor and punish surprises.
- 03Make every ask specific enough to forward. 'Intros to logistics VPs' beats 'help with sales' every time.
- 04Keep a running archive; comparing month over month shows the board the trajectory, not just the snapshot.
Adapt it for your case
Add: 'Frame highlights to build toward a Series A narrative and flag which metrics need to improve before raising.'
Tell it the period was rough and ask for an honest update that names the problem and the recovery plan without panic.
Ask for a shorter monthly investor email version for a wider list that excludes confidential board-only detail.
Common questions
Should I really include bad news?
Yes, prominently. The lowlights section exists because hidden problems destroy board trust when they surface later. Candor plus a plan is what earns directors' confidence.
Will the AI make up metrics if I'm vague?
The prompt explicitly forbids inventing numbers, but you should still supply real figures. Leave a metric blank rather than letting any placeholder slip into a board document.
How long should a board update be?
Under 600 words. Directors skim several updates per cycle; a tight, scannable memo gets read fully while a sprawling one gets skipped.
You may also need
Summarize a Sprint Retro Into Themes and Owned Actions
Clusters messy retro notes into themes with root causes and a table of owned, dated actions.
Executive Summary of a Long Document for Time-Poor Leaders
Condenses a long document into a layered executive brief tailored to one reader's priorities.
Write a Board Update / Investor Memo
Write a direct, no-spin investor update memo with metrics, wins, challenges, and asks.
Build a Structured Daily Plan From Your To-Do List
Turn a task list into a time-blocked daily schedule with deep work sessions and an MIT.