How is this different from the month-end close playbook?

The close makes the numbers right — clean inputs, reconciled accounts, totals with shown work. This playbook makes them presentable and defensible to a board — it assembles the close, the model, the KPIs, and the budget variance into one pack with the metrics investors track, a narrative, and a traceable appendix. Close first; this is the orchestration layer that turns a finished close into a board story.

Can I run this without the other Finance playbooks?

Not well. This is a Stage 3 orchestration playbook — it assembles the verified outputs of the others rather than re-deriving them. If you haven't run the reconciliation, spend audit, model, and budget variance, there's nothing trustworthy to pull from, and a board pack built on unverified numbers is worse than none. Do the foundations and systems first; this ties them together.

How do I make sure every number survives board scrutiny?

The appendix is the mechanism: every headline figure traces to a specific source file and the formula behind it, and any metric that isn't traceable is left blank with a note rather than estimated. Before the meeting, spot-check the two or three numbers most likely to be questioned — runway and burn — against their source files, so 'where's that from?' has a one-page answer.

Should I just have Claude write the whole board deck?

Claude assembles the pack — metrics, narrative, deck outline, appendix — but a human owns what goes to the board. Review every number against the appendix, set the tone on any sensitive message, and never let it spin a missed target. It does the assembly that used to eat your week; you do the judgment a board is actually trusting.

Assemble the board & investor finance pack

when to reach for this

The board meeting is the highest-stakes thing Finance produces, and it's where every other playbook gets put on a slide in front of people who'll ask hard questions. Done ad hoc, it's a frantic week of copying numbers between a deck and five spreadsheets, ending in a pack you hope nobody probes too closely. This is the orchestration layer: it takes the verified outputs of the close, the cash-flow model, the spend work, and the budget variance and assembles one coherent board pack — the metrics investors actually track, a narrative that explains the quarter, and an appendix where every headline number traces to a source. Where month-end close makes the numbers right, this makes them presentable and defensible to a board.

gather this first

Your verified monthly artifacts — the reconciliation, spend-audit, cashflow-model, budget-vs-actuals, and leadership-summary files from the other Finance playbooks. This playbook assembles them; it doesn't re-derive them, so they must be closed and trustworthy first.
The metrics your board tracks — revenue/MRR, gross margin, burn, runway, cash balance, and any north-star or unit-economics figures (CAC, LTV, DSO) they've asked for before.
Last quarter's board pack and any commitments made in it — the targets you set, the things you said you'd watch — so this pack closes the loop on what you promised.

the workflow

Assemble the metrics from verified sources only

A board pack is only as defensible as its inputs. In Claude Desktop, open the folder with all your closed monthly artifacts and ask in the chat — no terminal needed. Have Claude pull each board metric from the specific verified file it came from, and refuse to fill a gap with a guess.

you ask

Read my closed artifacts — reconciliation, spend-audit, cashflow-model, budget-vs-actuals, and leadership-summary for the quarter. Build the board metrics table: revenue, gross margin, burn, runway, cash balance, and DSO, for each month of the quarter and the quarter total. For every number, note which file it came from. If a metric isn't traceable to one of these files, leave it blank and tell me what's missing — don't estimate it.

what you get back A metrics table with a source beside every figure: "Q2 burn 468,000 (sum of monthly closes); runway 3.5 months (cashflow-model.md); DSO 42 (ar-aging-may.md). Gross margin: MISSING — no COGS file provided." Every present number is traceable; every gap is named, not papered over.

The discipline that makes a board pack survive scrutiny is that no number is in it that you can't point to a source for. A blank with a reason is infinitely safer than a confident guess a board member disproves live.
Write the quarter's narrative against last quarter's commitments

A board reads the story, then checks the numbers. Have Claude draft the narrative around what changed and whether you did what you said you'd do — the loop a board actually cares about.

you ask

Here's last quarter's board pack and the commitments we made in it. Write this quarter's narrative: what happened to each headline metric and why, which commitments we hit or missed and the honest reason, and the 2–3 things that most need the board's attention. Use the context I'll add: [the migration we flagged is done; the slipped enterprise deal closed in Q2]. Keep it to a page. Don't spin a miss — state it and what we're doing about it.

what you get back A board-grade narrative that closes the loop: "We committed to extending runway to 4 months and reached 3.5 — the gap is the delayed enterprise deal, now closed in Q2, which adds ~3 weeks. Margin held; burn is flat ex-migration." Honest, specific, and tied to prior commitments.

Boards forgive a missed target that's explained; they lose trust over a missed target that's hidden. Have Claude surface every miss against last quarter's commitments rather than quietly dropping the ones you didn't hit.
Build the slide outline and the charts to show

Turn the metrics and narrative into a deck structure — headline per slide, the one chart each slide needs — without losing the traceability underneath.

you ask

Turn this into a board-deck outline: a slide order (highlights, financials, metrics vs plan, cash & runway, risks, asks), a one-line headline per slide stating the takeaway not the topic, and the single chart each slide should show (e.g. 'runway: cash balance line, 12 months, zero-line marked'). Note which metric file feeds each chart so the deck stays traceable to the appendix.

what you get back A deck skeleton: "Slide 3 — 'Burn is flat; the spike was one-time migration' → bar chart, monthly burn with migration isolated, source budget-vs-actuals.md." Headlines that make an argument, charts that prove it, each tied back to a verified file.
Assemble the pack with a defensible appendix

End with one artifact: the narrative, the deck outline, and an appendix that makes every number traceable — so when a board member asks 'where's that from,' the answer is one page away. Review the diff before it saves.

you ask

Assemble everything into board-pack-q2.md: the one-page narrative, the metrics table, the deck outline, and an appendix that traces each headline figure to its source file and the formula behind it (especially runway and burn). Add a short 'open questions / what we're still verifying' section so nothing looks more certain than it is. Show me the diff before saving, and list anything I should personally re-check before this goes to the board.

what you get back A board-pack-q2.md with a defensible appendix — every headline number sourced and formula-backed — plus a short re-check list ("verify gross margin once COGS lands; confirm the Q2 deal close date"). The pack is presentable, traceable, and honest about its own gaps.

make it your own

Investor update instead of a board deck: ask Claude to recast the same narrative and metrics as a monthly investor email — shorter, the same honesty, the metrics investors track inline — reusing the exact same verified appendix.
Bilingual board pack: for a board that operates in Arabic and English, produce both — author the Arabic narrative natively for the right register, don't translate the English, and keep one shared numbers appendix so both languages reference identical figures.
Scenario slide for the ask: if you're raising or requesting budget, pull the stress scenarios from Build a cash-flow model you understand into a dedicated slide — runway under base, downside, and the ask — so the board sees the decision, not just the position.
Standardize the pack (Power Track): once the structure is stable, save the assembly prompts as a /board-pack custom command, and let a scheduled agent (see the Features tab) pre-assemble the metrics table from the closed files the day after close — so your prep is judgment and narrative, not copy-paste.

watch out for

Assembles verified numbers — it does not create them. This playbook is downstream of the close. If the reconciliation didn't tie out or a total wasn't checked, a beautiful board pack just makes a wrong number look authoritative. Close first, present second.
No number without a source. Every figure on a board slide must trace to a verified file and formula in the appendix — a board member will ask, and 'I'd have to check' on your own pack is the credibility you can't get back. A named gap beats a confident guess every time.
Don't let it spin a miss. A board pack that buries a missed target reads fine until the board notices — then every other number is suspect. State misses plainly with the cause and the fix; honesty is what makes the wins believable.
Board and investor materials are among the most confidential data you handle. Keep them in your approved workspace, swap anything truly sensitive for a [placeholder], and remember that what goes to the board is the CFO's call to own — Claude assembles the pack; a human signs it.

you'll end up with A board-ready finance pack — the metrics investors track, a narrative that closes the loop on last quarter's commitments, a deck outline, and an appendix where every number traces to a verified source — so the whole quarter is one coherent, defensible story you can stand behind line by line.

Questions people ask

How is this different from the month-end close playbook?: The close makes the numbers *right* — clean inputs, reconciled accounts, totals with shown work. This playbook makes them *presentable and defensible to a board* — it assembles the close, the model, the KPIs, and the budget variance into one pack with the metrics investors track, a narrative, and a traceable appendix. Close first; this is the orchestration layer that turns a finished close into a board story.
Can I run this without the other Finance playbooks?: Not well. This is a Stage 3 orchestration playbook — it assembles the verified outputs of the others rather than re-deriving them. If you haven't run the reconciliation, spend audit, model, and budget variance, there's nothing trustworthy to pull from, and a board pack built on unverified numbers is worse than none. Do the foundations and systems first; this ties them together.
How do I make sure every number survives board scrutiny?: The appendix is the mechanism: every headline figure traces to a specific source file and the formula behind it, and any metric that isn't traceable is left blank with a note rather than estimated. Before the meeting, spot-check the two or three numbers most likely to be questioned — runway and burn — against their source files, so 'where's that from?' has a one-page answer.
Should I just have Claude write the whole board deck?: Claude assembles the pack — metrics, narrative, deck outline, appendix — but a human owns what goes to the board. Review every number against the appendix, set the tone on any sensitive message, and never let it spin a missed target. It does the assembly that used to eat your week; you do the judgment a board is actually trusting.