What Your Board Will Ask at Month Six, and the Metrics That Answer It

At month six a games board wants evidence that players behave the way your deck said they would. That means early retention, cost to acquire, session behaviour, and a clear read on what you learned. Progress updates do not answer those questions. Numbers from a live build do.

Why this matters

The first two board meetings are about plans. By the third, the money has been spent on something, and the question quietly changes from what you intend to build to what you found out.

Founders who prepare for this shift keep control of the conversation. Founders who arrive with a build demo and a timeline usually lose the room.

The useful part is that the questions are predictable. There are five of them, and they barely change between investors.

The five questions that come up in every games board meeting

1. Do players come back? Early retention, expressed as a curve rather than one number.
2. What does a player cost? Cost to acquire, and how stable that cost is.
3. What is a player worth? Revenue per user over a defined window, with the window stated.
4. How long until those two cross? Payback period, or an honest statement that it is unknown.
5. What did you learn that changed the plan? The one that separates operators from reporters.

Everything else is detail hanging off these. Prepare them in this order.

A board meeting is not a status report. It is a decision meeting about whether to keep going, and the numbers exist to make that decision possible.

Retention: what number is defensible

Retention is the first question because it gates everything else. A game nobody returns to cannot be fixed with marketing.

Report day one, day seven, and day thirty as a set. One of them alone is easy to misread, and investors know it.

Three rules make the number defensible.

• State the cohort. Which installs, from which dates, through which channel. Organic and paid behave differently and mixing them hides the truth.
• State the sample size. A day-thirty figure from a small cohort is a rumour, not a metric.
• Show the shape. The ratio between day one and day seven says more about the loop than either number does alone.

Benchmarks by genre are worth knowing before you present, and we cover the general shape in Retention Benchmarks: D1, D7, D30.

Cost to acquire and payback period

Cost per install is the number most founders can produce and most misrepresent, usually without meaning to.

Be explicit about four things every time you show it.

Then connect it to value. Payback period is the metric that turns two disconnected numbers into a business, and the honest answer at month six is often that the window is still too short to know. Say that rather than extrapolating.

Both sides of that equation are explained in What Is CPI and How to Lower It and What Is LTV.

Why "we shipped on time" is not an answer

Shipping on time is necessary and it is not evidence. It answers a question about your team, not about your game.

The reframe that works is simple. For every milestone, state what it was designed to prove and whether it proved it.

• "We shipped the vertical slice" becomes "the slice tested the core loop with players, and here is what they did with it."
• "We hit the deadline" becomes "we reached the test two weeks early, which bought us an extra iteration."

Boards fund learning rate. Delivery is how you demonstrate it, not the thing itself.

Building the one-slide metrics view

Every board update should carry one slide that a director can read in twenty seconds.

Put four things on it.

1. The retention curve, with the cohort and sample stated in small text.
2. Acquisition cost with its qualifiers, shown as a trend rather than a point.
3. Session behaviour: sessions per day and length, since these move before retention does.
4. One sentence naming the single most important thing you learned this period.

Keep the rest in an appendix. A dense slide gets interrogated line by line, which spends the meeting on your formatting rather than your decisions.

What to say when the numbers are bad

They will be bad at least once, and how you handle it sets the tone for every meeting afterwards.

Lead with the number, not the context. Investors read a delayed reveal as a lack of control.

Then give three things in order: what the number is, what you believe caused it, and what you are changing as a result. Keep the diagnosis short and specific.

If you do not know the cause yet, say that plainly and state how you will find out and by when. An honest unknown is credible. A confident wrong answer costs you the next two meetings.

The decision framework for the harder version of this conversation is in When to Kill a Game and What to Salvage.

What we would do

Set up the reporting before you need it. Pick the metrics above in month one, instrument them properly, and produce the slide monthly even when nobody is asking. The habit is worth more than the document.

Agree the definitions with your board early. Retention measured on calendar days and retention measured on rolling windows give different numbers, and discovering that mid-meeting is avoidable.

Bring one decision to every meeting. A board that is asked to decide something engages differently from a board that is being informed, and you get better input.

The short version

• Five questions: do they return, what does a player cost, what are they worth, when do those cross, and what did you learn.
• Report retention as a curve with cohort and sample size stated.
• Qualify acquisition cost by geography, channel, creative age, and scale.
• Replace "we shipped on time" with what the milestone proved.
• One slide, four elements, everything else in an appendix.
• Lead with bad numbers, then cause, then the change you are making.

Build the slide this month even if your next board meeting is far away. If you want a read on whether your metrics stack up before you present them, talk to us.

Related reading: Game Analytics to Track From Day One, What Investors Mean When They Ask About Your Tech Stack, and Why Retention Beats Downloads.