What This Template Is For
A business review is the meeting where you present your product's performance, progress, and plans to leadership. It is different from a sprint review (which covers what shipped) or a roadmap review (which covers what is planned). A business review connects product work to business outcomes: revenue, retention, growth, and strategic position.
Most PMs prepare for business reviews by scrambling to pull metrics the day before, assembling a deck that is half status update and half roadmap preview, and hoping nobody asks a question they cannot answer. This template replaces that scramble with a structured preparation process that produces a clear, defensible narrative backed by data.
The template covers six sections: performance summary, key metrics deep-dive, progress against plan, risks and blockers, resource asks, and forward-looking priorities. For the meeting itself, see the quarterly business review template which structures the actual agenda. For ongoing stakeholder updates between reviews, the status update template provides a lighter-weight format.
When to Use This Template
- Before monthly business reviews with your VP or CPO. Monthly reviews focus on recent performance, near-term risks, and tactical adjustments. Preparation takes 1-2 hours.
- Before quarterly business reviews with the executive team. Quarterly reviews focus on strategic progress, trend analysis, and resource allocation. These are higher-stakes and require 2-3 hours of preparation.
- Before board updates that include product. Board-level reviews require a different level of polish and conciseness. Use this template to prepare the raw material, then distill it into the board product update template.
- When you need to justify a budget increase or headcount request. A well-prepared business review that shows strong performance and clear resource constraints is the most effective way to secure investment.
- After a significant product event. Post-launch, post-incident, or post-pivot business reviews require structured preparation to ensure you present a balanced view of what happened and what comes next.
How to Use This Template
- Start preparation 3-5 business days before the review. Rushing the night before produces a deck full of raw numbers without narrative. You need time to gather data, spot patterns, and build a story.
- Fill in the metrics section first. Numbers are facts. Start with what happened. The narrative flows from the data, not the other way around.
- Build the narrative around 2-3 key themes. Do not present 15 disconnected data points. Group findings into themes like "activation is improving but retention is flat" or "enterprise pipeline is strong but mid-market is softening." Themes are what leadership remembers.
- Prepare for the hard questions. For every metric that missed target, have a root cause and a plan. For every risk you flag, have a proposed mitigation. Leadership respects PMs who anticipate questions.
- Keep the presentation to 15-20 minutes. Reserve the rest of the meeting for discussion. A 45-minute presentation with 5 minutes for questions signals that you are hiding behind slides.
- Send a pre-read 24 hours before the meeting. For quarterly reviews, send the metrics summary and key themes in advance. This lets attendees come prepared with informed questions instead of asking clarifying questions that waste meeting time.
The Template
Part 1: Review Metadata
Review Type. [Monthly / Quarterly / Ad-Hoc]
Review Date. [YYYY-MM-DD]
Period Covered. [YYYY-MM-DD to YYYY-MM-DD]
Prepared By. [Name, Role]
Audience. [VP Product, CEO, CTO, CFO, etc.]
Pre-Read Sent. [Yes/No, Date]
Part 2: Executive Summary (One Page)
Write this last. It should be a 3-5 sentence summary that a busy executive can read in 30 seconds and understand the state of the product.
Overall Assessment. [On Track / Needs Attention / At Risk]
Summary.
[3-5 sentences covering: how the product performed against plan, what the biggest win was, what the biggest risk is, and what you need from leadership.]
Key Numbers.
| Metric | Target | Actual | vs. Target | Trend |
|---|---|---|---|---|
| [Primary metric, e.g., MRR] | [Up / Down / Flat] | |||
| [Secondary metric, e.g., Activation Rate] | ||||
| [Third metric, e.g., NPS] |
Part 3: Performance Deep-Dive
Revenue and Growth
| Metric | Last Period | This Period | Change | Target | vs. Target |
|---|---|---|---|---|---|
| MRR / ARR | |||||
| New Revenue | |||||
| Expansion Revenue | |||||
| Churned Revenue | |||||
| Net Revenue Retention |
Revenue Narrative.
[2-3 paragraphs. What drove the numbers? What surprised you? What are you watching?]
Engagement and Retention
| Metric | Last Period | This Period | Change | Target | vs. Target |
|---|---|---|---|---|---|
| DAU / WAU / MAU | |||||
| Activation Rate | |||||
| 30-Day Retention | |||||
| 90-Day Retention | |||||
| Feature Adoption (key feature) |
Engagement Narrative.
[2-3 paragraphs. Which cohorts are improving? Where is drop-off happening? What experiments are running?]
Customer Satisfaction
| Metric | Last Period | This Period | Change | Target | vs. Target |
|---|---|---|---|---|---|
| NPS | |||||
| CSAT | |||||
| Support Ticket Volume | |||||
| Avg. Resolution Time | |||||
| Top Support Category | n/a | n/a | n/a |
Satisfaction Narrative.
[1-2 paragraphs. What are customers praising? What are they complaining about? How does qualitative feedback align with quantitative metrics?]
Part 4: Progress Against Plan
| Initiative | Status | Target Completion | Current Progress | Notes |
|---|---|---|---|---|
| [Q-level initiative 1] | [On Track / At Risk / Blocked / Complete] | [Date] | [% or milestone] | |
| [Q-level initiative 2] | ||||
| [Q-level initiative 3] | ||||
| [Q-level initiative 4] | ||||
| [Q-level initiative 5] |
Shipped This Period.
- [Feature/capability 1]: [One-sentence impact summary]
- [Feature/capability 2]: [One-sentence impact summary]
- [Feature/capability 3]: [One-sentence impact summary]
Slipped or Deprioritized.
- [Item]: [Why it slipped, new target, or why it was deprioritized]
Part 5: Risks and Blockers
| # | Risk / Blocker | Severity | Likelihood | Impact if Unresolved | Proposed Mitigation | Owner | Status |
|---|---|---|---|---|---|---|---|
| 1 | [High/Med/Low] | [High/Med/Low] | [Open/Mitigated/Escalated] | ||||
| 2 | |||||||
| 3 |
Escalations for This Meeting.
[List any items that require a leadership decision or intervention. Be specific about what you need: a decision, a resource, a conversation with another team, an exception to a policy.]
Part 6: Resource Asks
| # | Request | Justification | Impact if Not Funded | Estimated Cost | Priority |
|---|---|---|---|---|---|
| 1 | [Must Have / Should Have / Nice to Have] | ||||
| 2 | |||||
| 3 |
Part 7: Forward Look
Next Period Priorities (Top 3).
- [Priority 1]. [One sentence on what, why, and expected outcome]
- [Priority 2]. [One sentence]
- [Priority 3]. [One sentence]
Key Bets and Experiments.
- [Experiment 1]: Hypothesis, success criteria, timeline
- [Experiment 2]: Hypothesis, success criteria, timeline
Decisions Needed by Next Review.
- [Decision 1]: [Context, options, deadline]
- [Decision 2]: [Context, options, deadline]
Preparation Checklist
Use this checklist 3-5 days before the review to ensure you are ready.
- ☐ All metrics are pulled and validated (cross-check analytics vs. backend data)
- ☐ Metrics targets are documented (what did we commit to this period?)
- ☐ Narrative themes are identified (2-3 max)
- ☐ Root cause analysis is complete for any metric that missed target
- ☐ Risk register is current (new risks added, resolved risks removed)
- ☐ Resource asks are sized and justified with evidence
- ☐ Forward priorities are aligned with the broader company plan
- ☐ Executive summary is written (do this last)
- ☐ Pre-read is drafted and scheduled to send 24 hours before the meeting
- ☐ Backup slides or data are prepared for likely follow-up questions
Filled Example: Series B SaaS Collaboration Tool
Context. A PM at a Series B collaboration platform ($18M ARR, 120 employees) prepared for a quarterly business review with the CEO, CTO, and VP of Sales. The product had a strong quarter on revenue but activation rates were declining.
Executive Summary
Overall Assessment. Needs Attention
Summary. Q4 revenue exceeded plan by 8% ($4.9M vs $4.5M target), driven by enterprise expansion. However, new user activation dropped from 34% to 27% over the quarter, and if the trend continues, it will reduce pipeline conversion in Q1. The activation team has identified the root cause (a redesigned onboarding flow that removed the guided setup wizard) and a fix ships in Week 2 of Q1. We need a decision on the API platform investment by January 15 to hit the Q2 launch date.
Key Findings
The review revealed three themes. First, enterprise expansion was the growth engine: 73% of new revenue came from existing accounts upgrading. Second, the onboarding redesign that was intended to reduce time-to-value actually increased drop-off at the workspace setup step by 40%. Third, the API platform has been in planning for two quarters and needs a go/no-go decision to stay on the published timeline.
Key Takeaways
- Lead with the narrative, not the numbers. Numbers belong in the appendix and in the pre-read. The presentation should tell a story about what happened, why, and what you are doing about it. Executives remember stories. They do not remember that activation was 27.3%.
- Prepare for the questions you hope nobody asks. If retention is down, you will be asked why. If a project slipped, you will be asked what went wrong. Prepare honest answers before the meeting. Saying "I will look into that and follow up" more than once erodes confidence.
- Size your resource asks in business terms. "We need two more engineers" is a cost statement. "With two engineers, we can ship the API platform in Q2 instead of Q3, which enables an estimated $1.2M in integration-driven revenue" is a business case. Use the business case template for larger investment requests.
- Track your predictions. At each review, note what you predicted would happen next quarter. At the following review, check whether it happened. Over time, this builds credibility. The Product Strategy Handbook covers how to think about longer-term strategic bets and their measurement.
About This Template
Created by: Tim Adair
Last Updated: 3/5/2026
Version: 1.0.0
License: Free for personal and commercial use