Is WBR different from a staff meeting?

Yes. Staff meetings are for org-level communication, decisions, and updates. WBRs are for metric-driven business review. Some teams combine; better practice is to separate so each has a clear purpose.

Full exec team plus 1-2 folks from ops/analytics presenting data. 6-12 people is the right range. Larger groups shift to broadcast mode and lose the challenge/debate quality that makes WBR valuable.

Should the CEO run it?

At earlier stages yes. Post-Series C, most companies rotate the chair or have COO/Chief of Staff run it. The CEO attends but doesn't need to drive.

Weekly Business Review (WBR): Agenda, Metrics

A Weekly Business Review is a 60-90 minute leadership meeting that reviews the previous week's metrics against plan, surfaces problems early.

Weekly Business Review: The Operating Rhythm Every Scaling Startup Needs

The Weekly Business Review (WBR) is a standing 60-90 minute leadership meeting where the exec team reviews the previous week's key metrics against plan. Popularized by Amazon (Jeff Bezos ran WBRs personally for years), it's now standard practice at operating-focused SaaS companies. Done well, it catches problems weeks before they'd otherwise surface. Done poorly, it becomes a status-reporting theater that wastes exec time.

The core principle

Every metric shown must have a plan/target and a variance. 'Signups were 1,200 last week' is useless. 'Signups were 1,200 vs plan of 1,500, a 20% miss driven by paid channel underperformance' is a WBR-quality data point. The variance is what triggers discussion; the raw number is decoration.

The standard deck

Typical WBR deck: (1) Executive summary — 3-5 bullets on the week's story. (2) Top-line metrics — bookings, revenue, cash, headcount, all vs. plan. (3) Funnel metrics — leads, MQLs, opps, close rate, pipeline. (4) Product/engagement metrics — DAU, activation, retention cohort. (5) Team-level deep dives (rotating). Total pages: 15-30. Owner: RevOps or Chief of Staff prepares; each metric has a named owner who narrates their section.

The right cadence and length

Weekly is right for most operating metrics — daily is noise, monthly is too slow to intervene. 60-90 minutes is standard; below 60 doesn't allow enough depth, above 90 loses attention. Same day and time every week, protected on all calendars, no cancellations unless the meeting has ceased to serve a purpose (in which case kill it deliberately, don't let it die by attrition).

How to keep it useful

Kill vanity metrics — if a metric never generates discussion, it doesn't belong. Kill deep-dives that duplicate other forums (product review, forecast call). Rotate spotlight sections so the team learns each other's context. Take real notes and track action items across weeks — 'we said we'd fix this three weeks ago, what's the update?' is what makes WBR generate action rather than reports.

When it stops working

Signs the WBR has gone stale: (a) everyone reading pre-reads for the first time in the meeting, (b) same 2-3 people talking every week, (c) action items from prior weeks never revisited, (d) exec team dreading Mondays. Fix by resetting the format (shorter deck, more discussion, clearer owner accountability) — don't just cancel.

Frequently asked questions

Is WBR different from a staff meeting?: Yes. Staff meetings are for org-level communication, decisions, and updates. WBRs are for metric-driven business review. Some teams combine; better practice is to separate so each has a clear purpose.
Who should attend?: Full exec team plus 1-2 folks from ops/analytics presenting data. 6-12 people is the right range. Larger groups shift to broadcast mode and lose the challenge/debate quality that makes WBR valuable.
Should the CEO run it?: At earlier stages yes. Post-Series C, most companies rotate the chair or have COO/Chief of Staff run it. The CEO attends but doesn't need to drive.

Related fundraising guides (40)

Investor directory · Fundraising library · Articles A–Z · Company funding database