The monthly management review in startups rarely fails because of the meeting itself. It fails because of what is missing in the days before it. CFOs, Heads of Finance, Controllers and FP&A leads who go into the meeting without structured preparation spend most of the time explaining numbers that nobody in the room has seen before. The problem starts earlier: on day one after month end, when data from multiple sources has to be gathered manually. The fix starts with the right data aggregation, a template that team leads fill in, and an agenda that uses 80 percent of the time for forecast and decisions rather than looking back.
Why nobody can make decisions in the meeting
Finance pulls up the monthly numbers for the first time with everyone in the room. The CEO asks about the variance in the headcount line. The head of marketing explains why they are 30,000 euros over budget. Everyone sees the same numbers at the same time.
This is not an exception. It is the default in most startups under 100 people.
Anyone seeing the numbers for the first time in the meeting cannot make decisions there. They can react, explain, defer. Decisions need context and lead time. Neither is available when the numbers land for the first time in the meeting.
The no-surprises principle
The most important rule for a functioning management review is not a rule about slides or agenda items. It is the principle that nobody in the meeting hears anything for the first time. No variances, no explanations, no bad news.
The pre-meeting check-in with each team lead in the 24 hours before the meeting takes 15 to 20 minutes per area. Finance walks through the variances from the pack, listens to the team lead's explanation, and both agree on a framing they can stand behind in the full group.
Teams that skip the pre-meeting check-ins feel it in the meeting: 90 minutes, no decisions, everyone leaves with open questions.
Step zero: data from scattered sources
In a mature company, numbers flow automatically from the ERP into the BI dashboard. In a startup they sit in four to six different places that do not talk to each other. The monthly management accounts come from the tax advisor, with a four to six week delay and often as a PDF. Marketing costs sit in the Google Ads portal and Meta Business Manager, each requiring a separate export. Pipeline and CAC come from HubSpot or another CRM. Headcount and payroll sit in Personio or a payroll spreadsheet. The budget-versus-actuals model is an Excel file that Finance maintains itself.
Below 80 people, this is the normal state. According to TheSaaSCFO's annual tech stack survey, 90 percent of companies at this size still use spreadsheets as their primary planning tool.
| Data source | Where it lives | Typical delay |
|---|---|---|
| Management accounts | Tax advisor / accounting software | 4–6 weeks after month end |
| Marketing costs | Google Ads, Meta Business Manager | Instant, but manual export |
| Pipeline and CAC | CRM (HubSpot, Salesforce) | Current, but no automatic export |
| Headcount and payroll | Personio, HR spreadsheet | Current, format varies |
| Budget vs. actuals | Finance Excel model | Depends on accounts arriving |
| Project margins (if relevant) | Project management tool or Excel | Varies significantly |
This aggregation is step zero of the preparation process. It takes three to four hours in structured startups and up to a full day in less structured ones. It has to happen on day one or two after month end. Teams that push it to the day the pack is built work under time pressure with incomplete numbers. Teams that push it to meeting day search for data in the meeting.
The process solution before any tool investment: Finance defines a standardised template per area, maximum one page. Revenue or order intake, costs by category, open items. Every team lead fills it in by day two after month end. It is not perfect, but it separates data collection from data analysis. When it makes sense to invest in integrated FP&A tooling is covered in Finance Tech Stack for Startups: The Three Phases.
The template for team leads
A standardised template solves this. Not because Finance needs control, but because a shared structure puts everyone in a better position. Finance knows what it is getting. Team leads know what to prepare. The meeting starts with a shared set of numbers instead of the question of which version is correct.
The most common mistake when introducing it: framing the template as a reporting obligation. That creates resistance. What works is a different frame. When first meeting with each team lead, Finance shows the template and explains that it is there to avoid surprises in the meeting. Saying “I will walk through the numbers with you before we sit in front of the CEO” is a different offer from “please send me your template by Tuesday.” Almost nobody turns down the first approach.
The template stays deliberately short. Ask a team lead to fill in five fields and you get five fields. Send twenty and you get nothing or a hastily completed table. Finance sets the structure; each team lead enters their own top KPIs.
Part 1: Your KPIs
| KPI | Actual | Plan | Delta |
|---|---|---|---|
| Your most important metric (define yourself) | |||
| Second metric | |||
| Third metric |
Part 2: Context
| Question | Answer |
|---|---|
| Biggest variance and explanation | |
| Forecast to end of quarter | |
| What could still change the forecast? | |
| What do you need from management? |
The template as a printable version to share with team leads: Open team lead template.
What Finance does before the meeting
Once the team lead templates are in and the data is consolidated, the real preparation begins on Finance's side. It follows a fixed sequence. Anyone who skips it brings a pack with numbers nobody knows and then wonders why the meeting goes off the rails.
- 1Set the closing date: Numbers are frozen by the third to fifth working day after month end. No adjustments after that. Anyone still making corrections on meeting day loses all credibility in the room.
- 2Build the pack: Put together the management pack with actuals, forecast and variance commentary. The basis is the frozen number set from step one.
- 3Send the pack: The management pack goes out 48 hours before the meeting. Not the evening before. Not the morning of. Anyone who does not read it still walks in prepared, because the pre-meeting check-ins have delivered the context.
- 4Pre-meeting check-in with each team lead: 15 to 20 minutes per area. Finance walks through the relevant numbers, hears the explanation for variances, and clarifies which points will be raised in the full group.
- 5Set the narrative: Before the first slide comes up, Finance already knows what message the meeting carries. Anyone who waits for others to interpret the numbers loses control of the conversation.
Who brings what
| Participant | Comes prepared with | Not responsible for |
|---|---|---|
| Finance Lead | Pack ready, company numbers prepared, variances discussed with each team lead beforehand, narrative set | Searching for numbers or calculating live in the meeting |
| Team leads | Explanation of their own variances, proposed next steps | Defending decisions that have already been made |
| CEO | Decisions, prioritisation between competing topics | Data entry, bookkeeping questions, asking for numbers |
What Finance presents in the meeting
Finance opens the meeting with the overall picture: revenue against plan, gross margin, operating costs, cash and runway. These are Finance's numbers, presented in the meeting itself. No pre-alignment needed, because they concern the company as a whole, not any individual department.
The pre-meeting check-ins serve a different purpose. They prepare team leads to explain their own area numbers: the headcount that is 15 percent above plan, the marketing costs booked a quarter too early. Those explanations come from the team leads themselves in the meeting, not from Finance.
The distinction is straightforward: Finance sets the context, team leads provide the explanations for their area. When these roles get mixed up, accountability breaks down. If Finance explains every variance and team leads just nod, nothing gets decided.
The agenda: 20 percent backward, 80 percent forward
The most common reason for inefficient finance meetings is the wrong time allocation. Prior month numbers get 45 minutes. The forecast gets 10 minutes. The next 90 days get 5 minutes. This does not reflect the relative importance of these topics.
What happened last month cannot be changed. What happens this quarter can. The meeting should spend most of its time where there are still levers to pull. Three questions structure a well-run review:
- 1Where do we stand? Actuals versus plan, the two or three most important variances, no complete line-by-line analysis.
- 2Where do we land at the current run rate? The current forecast for the quarter, with risks and upsides.
- 3What do we change? Concrete decisions with owner and date.
The third question is the only one that distinguishes the meeting from a status update. It is also the one that is most often missing.
| Time block | Content | Outcome |
|---|---|---|
| 0–5 min | Open action items from last month | Status update, no new discussion |
| 5–15 min | Actuals vs. plan: the key variances | Shared understanding, no surprises |
| 15–40 min | Forecast: where do we land, what are the risks | Decision needs identified |
| 40–55 min | Decisions and action items | Responsibilities fixed in writing |
| 55–60 min | Next steps and date of next review | Process clarity for everyone |
Common mistakes
- The pack goes out on meeting day. Everyone reads it at the same time. That is not preparation, that is collective discovery.
- No pre-meeting check-ins. Finance presents variances that team leads hear for the first time. Defence instead of decisions.
- No action items at the end. The meeting ends, everyone leaves, nothing is written down. Four weeks later the same conversation starts again.
- Only Finance speaks. Team leads nod. That is a presentation, not a review.
- No forecast at all. 60 minutes of actuals analysis, zero minutes on the outlook. The meeting has no decision value.
- No fixed date. If the review has no recurring slot in the calendar, it is the first thing cancelled when pressure rises.
What applies now, what can wait
Not every step in this article fits every startup. A team of 15 does not need a formalised data aggregation protocol. A team of 60 cannot manage without structured pre-meeting check-ins. The difference is not discipline, it is complexity.
One rule applies from the start regardless of team size: nobody searches for numbers in the meeting. Everything built around that grows with the team.
| Team size | Applies now | Can wait |
|---|---|---|
| 10–20 people | Pack exists and goes out before the meeting. Action items are written down. | Formal pre-meeting check-ins, closing calendar, data aggregation protocol |
| 20–50 people | Plus: informal pre-meeting check-in with team leads | Standardised department templates, strict closing date |
| 50+ people | Full process: data aggregation, closing date, formal pre-meeting check-ins, narrative set before the meeting |
Preparation checklist
The following checklist describes the full process from around 30 to 50 people. For smaller teams the starting point is simpler: prepare the pack, send it 48 hours in advance, fix action items in writing after the meeting.
| When | Task |
|---|---|
| Day 1–2 after month end | Aggregate data: request management accounts from the accountant, export ad costs, pull CRM data, reconcile payroll |
| Day 3–5 after month end | Freeze numbers, communicate closing date to all stakeholders |
| Day 6–8 | Prepare management pack (actuals, forecast, variance commentary) |
| 48h before meeting | Send pack to all participants |
| 24h before meeting | Pre-meeting check-in with each team lead (15–20 min) |
| 24h before meeting | Follow up on open action items from last month |
| Meeting day | Communicate agenda and timing at the start |
| After meeting | Fix action items in writing and send within 2 hours |
Conclusion
Whether Finance is seen as a number supplier or a decision partner is not settled in strategy workshops. It is settled in the 60-minute meeting that happens every month. And it is settled in the days before it.
The monthly management review is not a reporting format. It is a decision format. The difference lies in preparation: aggregate data early, send the pack with enough lead time, align with team leads beforehand, set the narrative before someone else draws the wrong conclusions. Those who do this run the meeting. Those who do not moderate it.
The process rarely runs smoothly the first time. The first review with a pack and pre-meeting check-ins takes longer than expected. Not every team lead comes prepared, and the agenda does not always hold to the time blocks. The second meeting runs better. By the third, the whole team knows what it is bringing, and the meeting starts working for the team, not against it.
Anyone who wants to start today does not need the full checklist. A pack that goes out 48 hours before and action items fixed in writing at the end are enough to begin. The rest grows with the team.