The 8 metrics a seed-stage board actually looks at

Board meeting metrics at seed stage come down to a short list: how fast revenue is growing, what is driving that growth, how much cash is going out, and how long it lasts. Everything else is context. This post covers the eight numbers I would put in front of a seed-stage board, and how to show each one so the meeting is spent on decisions rather than on decoding slides.

A caveat up front. Your investors may want something different, and they will tell you if you ask. Ask. This list is a starting point that covers what boards almost always end up asking about anyway.

I will use one fictional company throughout: a B2B software startup with $84K of MRR at the start of the month.

1. MRR and growth rate

Monthly recurring revenue, and how it changed. The company went from $84K to $98K, which is 16.7% month on month.

Show three numbers side by side: this month, last month, and what you said you would hit. The plan figure matters more than founders expect. A board can live with a miss. What it struggles with is not knowing what the target was.

If you are not a subscription business, use revenue, and pick a growth rate period that smooths out noise. Weekly numbers at seed stage mostly measure luck.

2. Net new MRR, and what it is made of

Growth of $14K is one number hiding three. Split it:

$84KMRR start+$12KNew-$3KChurn+$5KExpansion$98KMRR now▲ net new +$14K
Example: one month of MRR movement. Net new is the number the board asks about first.
  • New: +$12K from new customers
  • Expansion: +$5K from existing customers paying more
  • Churn: −$3K from customers who left or downgraded

This is the slide boards spend the most time on, because it separates two very different companies. One grows by adding customers while losing them out the back. The other grows on top of a base that is mostly sticking. Same headline growth, completely different future.

The bridge layout also answers the most common follow-up before it is asked. If net new MRR was lower than last month, the board can see straight away whether new sales slowed or churn picked up. I wrote a longer piece on this kind of breakdown in how to explain why revenue changed.

3. Churn, in dollars and in customers

Show churn two ways, because at seed stage they can tell different stories.

Revenue churn: $3K of $84K starting MRR is 3.6% for the month.

Logo churn: 12 customers left out of 420, which is 2.9%.

When revenue churn runs well above logo churn, you are losing your bigger customers, which is worth knowing early. When it runs below, the losses are small accounts, which may be fine.

And show the counts alongside the percentages. Early on, two customers can be a large percentage. Twelve customers is a list of names, and the board will likely want to know what happened with the three largest.

4. Net revenue retention, once you have the history

Net revenue retention asks: of the revenue you had from existing customers at the start of the period, how much do you have at the end, including expansion?

For our month: ($84K + $5K expansion − $3K churn) ÷ $84K = 102.4%. Above 100% means the existing base grows on its own, before any new sales.

Two cautions. Monthly NRR is noisy, so most companies report it over twelve months on a cohort basis once they have that much history. And don't annualise a single good month by compounding it. Somebody on the board will do the maths, and it will not go well.

5. Cash and net burn

Cash in the bank, and net burn: how much more went out than came in.

Our company spent $208K this month and collected $98K, so net burn was $110K. Show gross burn too if it moved, because a flat net burn can hide spending growing just as fast as revenue.

Use cash rather than accounting profit. A seed-stage board is asking one question with this number: how long until we need more money?

6. Runway

Which brings us to runway: cash divided by net burn.

Runway17 moCash$1.9MNet burn$110K÷
Example: runway is cash divided by net burn. Show both inputs, not just the answer.

$1.9M ÷ $110K a month is about 17 months. Show both inputs next to the answer, because the follow-up is always "what if burn goes up?" If you are hiring two people next quarter at $15K a month each, burn goes to $140K and runway drops to about 13.5 months. Have that number ready.

Paul Graham's essay on being default alive or default dead is a good frame here: at current growth and burn, do you reach profitability before the money runs out? Some boards ask that exact question. It is worth answering on the page.

7. One leading indicator for your growth motion

Revenue tells the board what already happened. Add one number that predicts next month.

Which one depends on how you sell:

  • Sales-led: qualified pipeline created this month, and its value.
  • Product-led: trial starts and trial-to-paid conversion. If trials are 400 and 8% convert, that is 32 new customers next month.
  • Usage-based: active usage of the core feature, measured the same way every month.

Pick one and keep it. A different leading indicator every meeting looks like you are hunting for a good number, even when you aren't.

8. Headcount against plan

People are most of a seed-stage budget. Show how many you planned to have by now, how many you have, and the open roles. If plan said nine and you have eight, that is $15K a month of burn you haven't spent yet, and it will show up later.

What to leave off the page

Some numbers are tempting because they always go up. Total signups since launch, website visitors, social followers, the size of the waitlist. None of them tell the board whether the business is working, and an experienced investor will read a page full of them as a sign that the real numbers are not good.

A few others are legitimate but premature. Lifetime value and customer acquisition cost are the classic pair. At seed stage you rarely have enough churn history to estimate lifetime honestly, so LTV ends up as a forecast built on a forecast. If you show it, show the assumptions next to it, and expect them to be questioned.

Pipeline is the third trap. A pipeline number with no stage definitions is a wish list. If you include pipeline as your leading indicator, define each stage in one line at the bottom of the page and keep the definitions fixed from month to month.

The rule I use: if a number could not change a decision the board might make, it goes in the appendix or nowhere.

Showing changes, not just numbers

Eight metrics fit on one page. The work is in presenting them so that every number answers the question "compared to what?"

For each metric, show:

  1. This period
  2. Last period
  3. Plan
  4. One line on why it moved, in drivers, not adjectives

"MRR +$14K, below plan of $16K: new sales on target, expansion light because the annual upgrade campaign slipped to next month." That sentence will save you ten minutes of questions.

Keep the layout identical every month. Boards learn where to look. When you change the format, they spend the first part of the meeting re-learning it instead of reading the numbers.

Why fewer slides work better

A thirty-slide deck signals effort. It also buries the two or three things the board actually needs to weigh in on, and invites questions on slide 24 that eat the time you wanted for hiring or fundraising.

Send the one-page metrics view 48 hours ahead. Use the meeting for decisions. Put supporting detail in an appendix that people can open if they want it.

There is one honest limit to all of this. At seed stage, numbers are small and noisy. A single large customer can swing churn from 1% to 6%. Say so when it happens, with the customer's name. Boards are generally much happier with "one customer, here is what happened" than with a percentage that looks alarming and turns out to mean nothing.

Building it without the night-before scramble

The worst part of board reporting is not the meeting. It is the evening before, copying numbers from Stripe into a spreadsheet and from the spreadsheet into slides.

You can cut most of that with a spreadsheet that pulls exports into a fixed layout, plus a KPI tree that shows how MRR is built. That alone fixes the "where did this number come from" problem.

I built FlowProofs partly for this exact use: connect Stripe, draw the MRR bridge and the runway tree once, and send the board a read-only link with an expiry date instead of a deck. Board members open it without an account. The founders page shows the setup. Whatever tool you use, the list above is the part that matters.

This week, write your eight numbers on one page with last month and plan beside each. If any of them takes you more than ten minutes to find, that is the one to fix before the next meeting.