The Quarterly Business Review is a comprehensive performance assessment that brings the executive team together for two to three hours at the end of each quarter. Its purpose is to evaluate financial results, analyse key performance indicators, celebrate wins, examine losses, and set strategic priorities for the quarter ahead.
A well-run QBR bridges the gap between daily operations and long-term strategy. It forces leadership to step back from tactical work, look at the business holistically, and make informed decisions based on data rather than intuition. The format is deliberately structured to prevent the session from becoming a loose discussion or a parade of vanity metrics.
The QBR also serves as a critical input to board meeting reporting, investor updates, and annual planning. When conducted consistently, it creates a quarterly rhythm that compounds organisational learning. Each review builds on the previous one, making it easier to spot trends, track the impact of strategic bets, and hold leaders accountable for commitments made ninety days prior.
A quarterly business review is essential for any organisation that has moved beyond the startup phase and needs structured performance management. This framework is particularly valuable when:
| Role | Responsibility |
|---|---|
| CEO / Managing Director | Opens with strategic context, facilitates priority-setting discussion, and closes with commitments for next quarter |
| CFO / VP Finance | Presents financial performance including revenue, margins, cash flow, and budget variance analysis |
| CRO / VP Sales | Reviews pipeline health, win/loss analysis, deal velocity, and revenue forecast accuracy |
| VP Marketing | Reports on demand generation metrics, CAC trends, brand health, and campaign ROI |
| CTO / VP Engineering | Covers product delivery, technical debt status, platform reliability, and roadmap progress |
| VP Customer Success | Shares retention rates, NPS scores, expansion revenue, and escalated account risks |
| VP People / HR | Reports on headcount, attrition, hiring pipeline health, and employee engagement data |
| Chief of Staff (optional) | Facilitates the session, manages the clock, and captures action items and commitments |
| Duration | Activity | Owner / Notes |
|---|---|---|
| 15 min | Opening and strategic context | CEO frames the quarter: market conditions, competitive landscape, company-level highlights |
| 30 min | Financial performance review | CFO presents P&L, revenue breakdown, margin analysis, cash position, and budget variances |
| 20 min | Sales and pipeline review | CRO covers bookings vs. target, win rate trends, average deal size, and forecast for next quarter |
| 15 min | Product and engineering update | CTO reviews shipped features, roadmap progress, uptime metrics, and technical investments |
| 15 min | Customer health and retention | VP CS presents churn analysis, NPS trends, logo retention, and net revenue retention |
| 10 min | People and culture | VP People shares headcount changes, regrettable attrition, and engagement survey highlights |
| 15 min | Wins, losses, and lessons learned | Open discussion: what worked, what did not, and what the team should carry forward |
| 20 min | Strategic priorities for next quarter | CEO facilitates: agree on 3-5 company-level priorities with owners and success criteria |
| 10 min | Action items and closing | Chief of Staff captures commitments; CEO closes with a summary of agreements |
A B2B SaaS company with 150 employees and 12 million in ARR holds its Q1 review in the first week of April. The CFO opens the financial section by noting that revenue grew 8% quarter-over-quarter, slightly below the 10% target. Gross margin improved by two percentage points due to infrastructure optimisation work completed by the engineering team.
The CRO presents the win/loss analysis and highlights a pattern: three enterprise deals were lost to a competitor that launched a self-serve trial in January. The VP of Product confirms that a similar trial experience is on the H2 roadmap but not yet prioritised for Q2. The CEO asks the group to evaluate whether accelerating the trial feature should become a Q2 priority, given the competitive pressure.
After a focused discussion, the team agrees to pull the self-serve trial into Q2 as the number-two company priority, behind only the data migration project required by a regulatory deadline. The VP of Engineering commits to a scoping exercise within two weeks, and the CRO agrees to provide the product team with detailed competitive intelligence from the three lost deals. These commitments are logged with specific deadlines, and the Chief of Staff will track them through the weekly leadership sync until the next QBR.