A Weekly Business Review is not a status meeting. It's a decision-making meeting.
The difference: status meetings share data. WBRs turn data into action.
This guide covers the structure that works.
What Is a WBR?
A 30-minute weekly meeting where leadership reviews key metrics, identifies problems, and makes decisions.
Who attends: CEO, functional leaders (Sales, Product, Finance, Marketing) When: Same time every week (e.g., Monday 9am) Duration: 30 minutes max
The Agenda (30 minutes)
1. Dashboard Review (5 min)
Scan the metrics. Are we on track?
Format:
Revenue: $2.5M / $2.4M target ✓
Churn: 2.1% / target <2.5% ✓
CAC: $350 / target <$400 ✓
Cash: 12 months runway ✓
[All green or mostly green? Move to exceptions. Red items? Dig in.]
If most are green, move on. You're not in crisis mode.
2. Exceptions & Deep Dives (15 min)
Pick 1-2 red or yellow items. Go deep.
Format:
ISSUE: Conversion rate dropped 15% this week
- CEO: "What happened?"
- Marketing Lead: "We implemented new landing page, it's underperforming."
- Discussion: "Let's revert and A/B test next week. Keep the old one live."
- Action: Marketing lead owns revert, A/B test launch
- Owner: Marketing
- Deadline: Wednesday
Rules:
- One issue at a time
- One person drives discussion (the function head)
- Identify root cause (not just "it's bad")
- Leave with a decision and owner
- Set a deadline
3. Forecast & Lookhead (5 min)
Are we on track for month-end? Quarter-end?
FORECAST:
- Revenue on pace for $9.5M this month (target $10M)
- At risk if sales pipeline doesn't close 3 deals by Friday
ACTION: Sales lead prioritizes those 3 deals
4. Blockers & Asks (5 min)
What does the team need?
BLOCKERS:
- Engineering: Need product hire approved (blocking feature launch)
- Sales: Need marketing to boost pipeline (short on SQL)
DECISIONS NEEDED:
- Approve engineering hire? (CEO signs off yes/no)
The Metrics You Review
Non-negotiable (every WBR):
- Revenue
- Churn
- CAC
- Cash runway
- Key product metric (e.g., engagement)
Rotating (one per WBR):
- Week 1: Sales pipeline & conversion
- Week 2: Marketing & customer acquisition
- Week 3: Product & engagement
- Week 4: Finance & profitability
This prevents meetings from becoming data dump marathons.
The WBR Cadence
Monday Morning:
- Prep: Finance pre-populates dashboard Friday (24-hour lag is acceptable)
- Meeting: Review metrics, identify exceptions
- Output: 3-5 action items with owners and deadlines
Wednesday Check-in (optional):
- Quick sync on critical exceptions
- "Did we fix that conversion rate issue? Yes/no."
- Unblock if needed
Friday Retrospective (optional):
- Did we execute on action items? (yes/no/partially)
- What would have helped us move faster?
A Real WBR Example
MEETING: Weekly Business Review
TIME: Monday 9:00-9:30am
ATTENDEES: CEO, Sales Lead, Product Lead, Finance Lead
DASHBOARD (5 min):
CEO: "All metrics are green. Moving on."
- Revenue: $2.5M ✓
- Churn: 2.1% ✓
- CAC: $350 ✓
- Engagement: Up 8% ✓
- Runway: 12 months ✓
DEEP DIVE (15 min):
Finance Lead: "One issue. Payment processing fees spiked 12% last week. Margin pressure."
CEO: "Why?"
Finance: "Stripe changed pricing. We're moving to a new processor."
Product Lead: "How long?"
Finance: "Integration complete by end of week. Savings: $20K/month."
CEO: "Who owns it?"
Finance: "I do. Deadline: Friday."
[Noted. Move on.]
FORECAST (5 min):
Sales: "We're on pace for $9.5M this month. Need 2 more closes to hit $10M."
CEO: "Likely to close?"
Sales: "70% confidence on both."
CEO: "Let's check Wednesday if we closed."
BLOCKERS (5 min):
Product: "Need engineering headcount approved. Blocking 2 feature launches."
CEO: "Approved. Offer out by Friday."
Sales: "Need 50 more SQL this week."
Marketing: "Running paid campaign starting tomorrow. Expect 60."
Sales: "Perfect."
[Meeting ends with 3 action items, owners, deadlines]
What Makes a Good WBR
✓ Focused: Review top metrics, not everything ✓ Decisive: Every red item gets an action and owner ✓ Accountable: Owners commit publicly to deadlines ✓ Fast: 30 minutes max (forces discipline) ✓ Recurring: Same time, same group, every week
❌ Not: A status dump of every department ❌ Not: A forecasting exercise (WBRs are backward-looking, weekly planning is forward-looking) ❌ Not: A place to escalate blame ("marketing didn't hit targets")
Running It Effectively
Before the meeting:
- Dashboard populated Friday (24 hours lag is ok)
- Pre-read sent Sunday evening
- Everyone comes prepared
During the meeting:
- CEO runs it, keeps time
- One speaker at a time
- No tangents
- Decisions documented
After the meeting:
- Action items sent within 1 hour
- Progress tracked against deadlines
- Wednesday check-in on critical items
Action Items: The Format
Every action item needs:
- Issue: What's the problem?
- Action: What are we doing?
- Owner: Who?
- Deadline: When?
- Success metric: How do we know it's fixed?
Example:
Issue: Conversion rate dropped 15%
Action: A/B test old vs. new landing page
Owner: Marketing lead
Deadline: Test launches Wednesday, results Friday
Success: New page >= old page conversion
Checklist
- ✓ Scheduled same time every week
- ✓ 30 minutes max
- ✓ Key metrics reviewed
- ✓ Red items get one owner and deadline
- ✓ CEO or leader runs it
- ✓ Action items documented
- ✓ Follow-up on previous week's items
- ✓ No tangents or politics
- ✓ Forecast discussed
- ✓ Blockers escalated
The Bottom Line
A WBR turns metrics into decisions.
Every item that's red gets one person accountable and a deadline.
Every week, the team knows:
- How we're tracking
- What's wrong
- Who's fixing it
- When it's fixed
That's alignment. That's how companies scale.
Hold your WBR like it matters. Because it does.