---
name: board-update-writer
description: Write high-signal startup board updates, investor updates, quarterly board pre-reads, CEO letters to the board, monthly board emails, bad-news updates, and board-prep memos. Use when the user needs to report company performance, explain deltas versus plan, surface risks without spin, tailor the update for seed or growth stage, decide what metrics belong up top, turn issues into concrete asks, or rewrite a weak board update into something directors will actually read before the meeting. Trigger even when the user asks for a board deck, board memo, investor email, quarterly summary, pre-read, or "help me write the board update."
---
# Board Update Writer
Write startup board updates that make the company legible fast, surface the real issues early, and give the board specific ways to help. Favor a short written artifact over presentation theater. Open with the CEO-level story, support it with a small set of decisive metrics, state misses plainly, and convert issues into asks.
At a high level, the process of writing a board update goes like this:
- Figure out what stage the company is in, what kind of artifact the user needs, and whether the board needs status, a decision, or both.
- Identify the top-line story before choosing metrics.
- Pick the few metrics that explain company health at this stage.
- Pair every headline number with a comparison frame and one sentence of interpretation.
- Surface lowlights, risks, and misses early.
- Translate major issues into concrete asks the board can act on.
- Choose the lightest format that still reads cleanly: email, memo, pack, or deck.
- Tighten the writing until a board member can understand the company in minutes.
Your job when using this skill is to figure out where the user is in that process and jump in at the right point. Some users will arrive with raw notes, a KPI dump, or a weak draft. Others will ask for a board update from scratch. In either case, diagnose the stage, the artifact, the audience, and the decision load first, then move forward.
On the other hand, some users do not need a full process. They may just need a stronger opening summary, a rewrite of a bad-news section, better asks, or help deciding which metrics belong in the first page. If so, do that directly, but keep the same standards.
If the user wants a lighter-weight answer, skip the heavier process and produce the artifact quickly. If they want a full board-ready update, get the structure right before polishing sentences.
The description is doing real work here. Board-update requests are often phrased indirectly as "help me prep for the board," "write the investor email," or "turn this dashboard into a memo." Treat those as triggers.
Cool? Cool.
Communicating with the user
Start by understanding four things: stage, artifact, audience, and decision load.[1][2][3][4][5]
Capture intent
- Ask what the company stage is: pre-seed/seed, early Series A, or growth/post-PMF.[8][7][3]
- Ask what artifact is needed: monthly email, quarterly memo, board pack, deck, CEO letter, or bad-news update between meetings.[4][5][2]
- Ask who will read it: full board, investor observers, independent directors, or just existing investors between meetings.
- Ask whether the board mainly needs a status read, a decision, introductions, recruiting help, financing advice, or calibration on a miss.[4][5][2][3]
Interview for the missing operating facts
- Ask what changed since the last update.
- Ask what is going well, what is not going well, and what is keeping management up at night.[3][2]
- Ask which metrics management actually trusts right now. If the data is messy, ask which few numbers are still solid enough to show.[8][2]
- Ask what the board can actually do next: customer introductions, candidate leads, fundraising calibration, product/market feedback, or a decision on a tradeoff.[4][5][6]
Adapt to where the user is
- If they have raw notes, impose structure first.
- If they have a KPI dump, cut it down to the smallest set that explains company health.[2][7][8]
- If they have a weak draft, rewrite the opening first, then fix metrics, lowlights, and asks.
- If they only need a between-meetings email, keep it short and inline.[6][4]
Creating a board update
Start with the board-level story, not the dashboard.[2][3][8]
Step 1: Write the opening summary first
- Write 3-6 sentences that answer: What changed? What matters most now? What is going well? What is not going well? What does the board need to help with?[2][3][8]
- Be blunt. If pipeline slipped, say it. If burn is too high, say it. If the company is ahead of plan, say by how much.[3][8][6][10]
Step 2: Choose the headline metrics by stage
Pick metrics by decision stage, not by function.[8][7][3][2]
Seed / pre-seed / very early Series A
- Usually lead with 3-5 traction-and-survival metrics: active users, engagement depth, retention, conversion to active or paid, initial revenue if real, burn, and runway.[8][7][2][3]
- Do not stuff a seed update with mature-board vanity. If the company is still searching, emphasize learning velocity and cash risk.
Growth / post-PMF / later Series A and beyond
- Usually lead with the few metrics that explain repeatability and economic health: ARR or MRR growth, net new revenue components, churn, retention, expansion, gross margin where relevant, pipeline or forecast attainment, burn, cash, runway, and any usage metric that truly leads revenue or retention.[3][7][12]
- Keep the headline set narrow even if the appendix is larger.[7][2][9]
Step 3: Write every metric as number + benchmark + reason
- Do not write "revenue grew nicely" or "pipeline was softer than expected." Write the actual number, the comparison frame, and one sentence of interpretation.[10][7][11]
- Use the shortest comparison frame that explains the decision: versus plan for accountability, year-over-year for growth framing, month-over-month for fast operational shifts.[11][10]
Step 4: Put risks and misses near the top
- Give lowlights their own labeled space: lowlights, challenges, burning issues, or what we are worried about.[2][4][5]
- Name the miss, quantify it, explain it briefly, and say what management is doing now.[3][8][10]
- If cash risk or another issue changes the whole conversation, move it into the opening summary.[3][2]
Step 5: End with concrete asks
- Convert each major issue into 1-2 actions the board can actually take.[4][5][6]
- Make asks target-specific whenever possible. "Need intros to 3 fintech buyers" works. "Would love thoughts on GTM" does not.[4]
Step 6: Choose the format by decision load
- Use a short email for routine status or interim updates.[6][4][9]
- Use a memo or board pack when the board needs reasoning, tradeoffs, or a strategic decision.[4][5][2]
- Use a deck only when visuals materially improve comprehension. The board still needs a written pre-read.[4][5][2][3]
Running and evaluating examples
Use worked examples to teach the pattern, not to show off. Keep them short, literal, and copyable.[1][10][4]
Example 1: Rewrite vague growth language into board language
Input:
Revenue continued to grow nicely this quarter, and we feel good about demand.
Output:
New ARR was $1.7M, $200K above plan and up 42% YoY. Two enterprise expansions closed in the final month, which offset slower mid-market win rates.
This pattern works because it gives the result, the benchmark, and the reason immediately.[10][7]
Example 2: Rewrite spun bad news into usable bad news
Input:
Pipeline was somewhat slower than expected, but we remain optimistic and are seeing positive early signs from the team.
Output:
Pipeline coverage ended at 2.1x versus our 3.0x target, mostly because two enterprise reps ramped slower than planned. We cut the Q3 forecast accordingly, moved the VP Sales into weekly pipeline review, and need introductions to three enterprise buyers in fintech.
This pattern works because the miss is explicit, the cause is concrete, the response is operational, and the ask is usable.[3][8][4]
Example 3: Seed-stage opening summary
Input:
We're making progress on product and user growth, and there are a few challenges we want to discuss.
Output:
This quarter we shipped self-serve onboarding, increased weekly active teams from 120 to 185, and held 8-week retention flat at 61%. The biggest issue is conversion from activated team to paid workspace, which stayed at 4.2% versus our 6% target. Burn remained $210K per month, leaving 11 months of runway. We need help with pricing feedback from two SaaS operators and introductions to three design partners in compliance-heavy industries.
This pattern fits seed because it stays narrow, uses a few traction-and-survival metrics, and ends with specific asks.[8][2][3][4]
What to check before you ship a draft
- Can a director understand company state in under five minutes?[4][5][10]
- Are the top metrics tied to plan, prior period, or year-over-year context?[10][11][7]
- Is the worst problem visible near the top?
- Does each major issue produce a concrete ask?
- Did you cut anything that reads like internal status theater instead of board-level synthesis?[4][5]
Improving the board update
This is the heart of the loop. Draft fast, then cut hard.[1][5][4][10]
How to improve a weak draft
- Cut throat-clearing in the first paragraph. The opening should contain company state, not scene-setting.
- Replace adjectives with numbers and comparisons.[10][11][7]
- Move the worst news up.
- Cut KPI count until the top section reads cleanly in one pass.[2][7][9]
- Turn any generic closing request into a concrete ask with a target, role, or account.
- Delete feature chatter unless it changes revenue, retention, roadmap risk, or strategic choice.[5]
Rewrite patterns
- Weak: "We had a solid quarter and learned a lot."
- Better: "Net new ARR was $940K, 6% below plan, because two enterprise deals moved into next quarter. Gross retention held at 91%, and burn stayed flat at $410K per month."
The better version works because it lets the board calibrate immediately.[7][10][2][3]
When the data is messy
- Say what you know, what you do not know yet, and when you will clean it up.
- Use prose plus a few trusted numbers instead of a fake-complete dashboard.[8]
- Do not hide behind imprecision. If a number is preliminary, label it preliminary.
Advanced: Stage and format branching
Branching by context is not optional here. Seed updates, growth-stage updates, interim emails, and board-decision memos should not sound the same.[1][8][3][7][4]
Seed branch
- Keep it shorter.
- Use fewer metrics, usually 3-5.[8][7]
- Emphasize traction, learning velocity, hiring bottlenecks, burn, and runway.[8]
- Memo or email formats are often enough.[8][2][4]
Growth branch
- Keep the top narrow, but support it with a more formal KPI package.[3][7]
- Use plan-versus-actual framing aggressively.
- Make departmental accountability clearer, but do not let the update become a departmental dump.[3][4][5]
Interim update email branch
- Keep it inline in the email body if possible.
- Use bullets or short paragraphs.
- Organize it around performance, major changes, burning issues, and asks.[4][6]
Board-decision memo branch
- Add a section that states the decision to be made.
- Write the decision framework explicitly.
- Write down uncertainties and blind spots instead of hiding them.[4]
Gotchas
- Do not lead with housekeeping. Put approvals and admin items later or in a clearly separate section.[3][2][8]
- Do not bury cash. If runway is getting tight, put cash, burn, and runway near the top.[3][2][10]
- Do not send an all-positive update. If nothing is wrong on the page, the board will assume management is missing something or hiding it.[3][8][5]
- Do not dump 20 KPIs into the opening pages just because you have them. Lead with the few that explain the company.[2][7][9]
- Do not make the board infer the punchline from charts. Write the takeaway in a sentence next to the metric.[7][10][5]
- Do not end with vague asks. Name the person, role, account list, or decision you need.[4][5]
- Do not turn the meeting into a live read-through of the packet. The document should absorb most of the status work before the meeting starts.[4][5][14]
Package and present
- Use a stable order: opening summary, top metrics, lowlights or burning issues, asks, then supporting detail.[4][2][3]
- Use short paragraphs, bullets, and simple tables.[6][10][5]
- Send materials early enough for directors to read them. Exact timing varies, but advance distribution is the rule.[2][3][13][6][5][4]
Repeating one more time the core loop here for emphasis:
- Diagnose the stage, artifact, audience, and decision load.
- Write the blunt CEO-level story first.
- Pick the few metrics that explain company health now.
- Write every important number with a benchmark and one sentence of interpretation.
- Surface the real problems early.
- Turn issues into concrete asks.
- Choose the lightest written format that still reads cleanly.
- Cut until a board member can understand the company in minutes.
Put these steps in your working checklist so you do not forget them halfway through.
