Reports founders read vs. reports they ignore

Most management reports fail in a quiet, polite way. They get sent, the founder says thanks, and nobody opens them again. The report wasn't wrong. The numbers tied out, the formatting was clean, the close was done on time. It just didn't help anyone decide anything, so it got ignored.

The problem is almost always structure. A typical pack is organized the way the accounting system is organized — a tab for the profit and loss, a tab for the balance sheet, a tab for each cost category, a tab for the cash flow statement. That layout is logical if you're an accountant reconciling accounts. It's useless if you're a founder trying to figure out whether you can afford to hire next month.

A report a founder reads is built backward from the decisions they actually make: do we have enough cash, are we on plan, are we making money on each sale, and what changed since last month. Five numbers, one page, sixty seconds. Everything else is backup.

The 12-tab pack nobody reads

I've inherited plenty of these. A spreadsheet or PDF with a cover page, a full P&L by month, a balance sheet, a detailed expense breakdown across forty line items, a tab of payroll, a tab of vendor aging, and a cash flow statement built the formal three-section way. Twenty pages, all technically correct.

The founder reads none of it. Not because they're lazy — because the work of turning twenty pages into a decision is being handed to them instead of done for them. To answer "can I hire," they'd have to find the cash balance, estimate burn from the P&L, guess at timing, and do the math themselves. So they don't. They wait until something feels tight, then ask in a panic.

The pack isn't bad reporting. It's raw material pretending to be a report. The backup belongs in the file. It should not be the thing you lead with.

The one page they actually use

Replace the cover with a summary that fits on a single screen and answers the questions a founder genuinely has. Five things, in this order, because order signals priority:

• Cash on hand — the real bank balance today, e.g. $480,000, not a month-end figure that's three weeks stale.
• Runway — months of cash left at current burn, e.g. 11 months at $44,000 net burn, and whether that number went up or down since last month.
• Revenue vs. plan — actual against the number you committed to, e.g. $210,000 against a $230,000 plan, so down 9 percent, stated as a dollar gap, not just a percentage.
• Gross margin — what's left after the direct cost of delivering, e.g. 62 percent this month vs. 66 percent last month, because a margin that's quietly slipping is an early warning.
• Top 3 variances — the three biggest things that moved versus plan or last month, each with one sentence of plain-English why.

Lead with the variance, not the number

The single most-read line in any report is the explanation of what changed. A founder can see that costs were $186,000. What they can't see is that $14,000 of that was a one-time annual software renewal, so next month drops back to normal. Without that sentence, they either worry needlessly or miss the trend entirely.

So write the variances as sentences a tired person can read at 9pm: "Marketing ran $9,000 over plan — we pulled forward the conference sponsorship from Q3." "Revenue missed by $20,000 — two deals slipped from March into April, both still expected to close." That's the part that turns a report into a conversation. Three of these, every month, is plenty.

Notice what this does. It moves the analysis from the founder's head onto the page. You already know why the numbers moved — you closed the books. Spending five extra minutes writing it down is the difference between a report that gets read and one that gets archived.

What to cut

Cut the balance sheet from the front. Most early founders don't read it and don't need to monthly — keep it in the backup for when it matters (a raise, a loan, a tax question). Cut the forty-line expense breakdown from page one; nobody scans forty rows. Group costs into five or six buckets — people, software, marketing, contractors, everything else — and let the detail live one click deeper.

Cut precision that pretends to be insight. "Net income of $3,142.87" reads as false confidence on a number that will move with one late invoice. Round to the nearest thousand on the summary. Cut any metric you can't tie to a decision — if you can't say what a founder would do differently based on it, it doesn't belong on the front page.

The test is simple. For every line on the summary, ask: what decision does this inform? Cash and runway inform spending and hiring. Revenue vs. plan informs whether the strategy is working. Margin informs pricing and delivery. Variances inform what to fix. If a number doesn't answer one of those, it's backup, not headline.