- 1One-page financial summary. Revenue, gross margin, opex, EBITDA, cash, runway. Designed for the CEO's morning coffee.
- 2P&L with variance to budget and prior month. Three columns, written commentary on the lines that moved.
- 3Cash position and forecast. Current cash, 13-week forecast, runway calculation.
- 4Department spending recap. Actual vs budget by department, who's on track, who's overspending.
- 5Headcount tracker. Current FTEs, planned hires, open requisitions, attrition.
- 6KPI dashboard. Three to five metrics that matter most for your stage. Trend, not just point-in-time.
- 7Forward look. What to expect next month, what to watch, what management is doing about it.
The one-page summary
Every person on the leadership team reads this page, and most of them read only this page. So it has to carry the whole story on its own: revenue against plan, cash and runway, the two or three operating metrics that matter, what moved materially, and what decisions are on the table. Half a page of numbers, half a page of commentary. Get this page right and the rest of the package becomes optional reading. Get it wrong and the meeting burns its first twenty minutes re-explaining basics instead of making calls. It is worth more of your time than any other page in the pack.
Keep the format identical month to month. Same structure, same metric order, same way of writing the commentary. When people know exactly where cash sits and where to find the revenue line, they read faster and trust what they are reading. Reinventing the layout every month just makes them hunt.
Financial statements with commentary
Behind the summary sits the full financial detail: a P&L for the month and year-to-date, each compared to plan and to the prior period, plus balance sheet highlights and a cash flow summary. On any line that moved meaningfully, write a sentence explaining why. A table of twelve monthly revenue figures is harder to read than a twelve-month trend chart, so use charts for direction and tables for point-in-time comparisons like this month versus plan.
The commentary is where you earn your keep. Revenue flat for the month is a shrug. Revenue down 10% because one large customer churned is a conversation. Tell leadership the story behind the number, not a restatement of the number itself, because they can already see the figure sitting right next to your note.
Operating metrics
Financials tell you what happened. Operating metrics tell you why. Break revenue down by the dimensions that actually drive your business, whether that is product line, customer segment, or channel, so leadership can see where growth is real and where it is thinning out. Pair that with unit economics: CAC, LTV, payback, and margin structure. Watch the trend on these more than the current level, because a payback period creeping from nine months to fourteen is a warning you want long before it shows up in the cash line.
Then headcount. For a growing company, people are the biggest expense and the ceiling on how much revenue the business can produce, so leadership needs a monthly read on current FTEs, open roles, hiring pace, and attrition. When the plan assumes five hires and only one has closed, that gap changes the forecast, and everyone should see it in the same place every month.
What to leave out
What you leave out matters as much as what you include. Raw data dumps do not belong here. The full AR aging report, the detailed general ledger, transaction lists, granular reconciliations: those live in the data room as support material, ready if someone asks, but they are not the briefing. The same goes for process notes. "We finally sorted out the AP categorization mess" is a real win for the accounting team and completely irrelevant to a CEO deciding whether to greenlight a hire. Report what informs a decision, not what you did to close the books.
Resist the urge to pad the pack with appendices nobody asked for. A 40-page package that gets skimmed is worse than a 10-page one that gets read cover to cover. If leadership wants to go deeper on a number, they will ask, and you should have the backup ready. Until then, cut hard and keep the package to what earns its place.