At 100 people, the quarterly business review has usually calcified into a ritual nobody quite believes in. The Chief of Staff spends the better part of two weeks building forty slides. Each department head gets ten minutes to walk through their section. The slides say green. The room nods. Three weeks later, half of what was presented turns out to have been optimistic, and nobody is surprised.
The problem is rarely the people in the room. It is the agenda, and the fact that the agenda runs on hand-assembled narrative rather than real execution data. Here is a QBR agenda that fits in three hours and does not require a fortnight of slide-building to prepare.
The three-hour agenda, time-boxed
Time-boxing is the whole game. An untimed QBR expands to fill a day and still skips the hard conversation. Here is the structure that holds:
- Prior-quarter scorecard (30 min). Every OKR and KPI, scored. Owners speak only to the reds and the genuine surprises. Greens are read, not presented.
- What we learned (20 min). The bets that genuinely changed how you understand the business. Learning worth carrying forward, not a recap of activity.
- Capacity reality check (25 min). Where bandwidth actually went last quarter versus where you said it would go. This is where the honest conversation about over-commitment happens.
- Next-quarter priorities (45 min). Proposed goals, each with a single named owner and an explicit statement of what it trades against.
- Dependencies and risk (25 min). Cross-team dependencies, and the goals currently running on hope.
- Decisions and commitments (15 min). Written down, owned, dated. If a decision leaves the room only in people's memories, it did not happen.
That is roughly two hours forty of content. The rest is breaks. A 100-person company does not need a full-day offsite to review a quarter. It needs three focused hours and a scorecard people trust.
What to cut
Most QBRs are bloated with content that feels responsible and changes nothing. Cut the department round-robin, where each function narrates its quarter in sequence regardless of whether it is on track. Cut any slide that restates a number already on the dashboard. Cut the retrospective on goals that died mid-quarter; note that they died and move on. Cut the pre-read that gets read aloud.
The test for every agenda item: does this change a decision? A section that cannot alter what the company does next quarter is a status update, and status updates do not belong in a QBR. They belong in the monthly business review, which is exactly why the monthly beat matters. A company that runs a real monthly review walks into the QBR without surprises, because the reconciliation already happened.
Run it off execution data, not slides
The reason QBR prep takes two weeks is that someone is manually reconciling what the goal tool says with what actually happened in the work tools. The dashboard claims a key result is at 70 percent. The Chief of Staff knows the two projects behind it are stalled, so the slide gets an asterisk and a caveat. Multiply that by forty goals and you have a fortnight of detective work.
When progress is derived from the real work rather than self-reported, the scorecard assembles itself. You walk into the QBR already knowing which goals have active work behind them and which are running on narrative. The meeting becomes an exercise in judgment rather than verification. This is the idea behind building the QBR around traceable work: the review reflects execution because it is wired to execution.
The failure modes to watch
Four patterns quietly kill a QBR at this size.
Green-washing. Everything is green because nobody wants to present a red. A quarter with zero reds is a dishonest scorecard, not a triumph.
No decisions. The review ends and everyone feels informed, yet nothing was actually decided. A QBR with no written decisions was a status meeting wearing a suit.
Slide theater. The quality of the presentation becomes the metric. Beautiful slides and animated builds with nothing underneath. Effort spent on the deck is effort stolen from the thinking.
Reviewing goals with no work behind them. A goal gets discussed for ten minutes and it emerges that no one touched it all quarter. That is a capacity and ownership failure, and it should be named as one, not smoothed over.
A good QBR is short and decision-dense. It sits inside an operating cadence where the monthly review has already absorbed the surprises, and it runs on execution data that makes the scorecard true by default. Vindaris exists to make that scorecard build itself, so the quarter you review is the one that actually happened.
FAQ
How long should a QBR be for a 100-person company? About three hours, time-boxed hard. That is enough to score the last quarter and set the next one if the data is ready before the meeting starts. Companies that run all-day QBRs are usually using the length to compensate for a scorecard nobody trusts.
What is the difference between a QBR and a monthly business review? The monthly review is reconciliation and course-correction within a quarter. The QBR scores the quarter that ended and sets goals for the one beginning. If your monthly review is doing its job, the QBR contains no surprises, only decisions.
Who should own the QBR agenda? The Chief of Staff or COO builds and runs the agenda, but the CEO owns the goal-setting portion. Keep the ownership clear: one person runs the clock, and the CEO drives the decisions about what the company commits to next.