How to Build a QBR Dashboard

A QBR deck often turns into forty slides of screenshots from a spreadsheet, and the meeting turns into someone reading the numbers on those slides out loud while the room waits for the one number that actually matters. The review is supposed to answer four questions: how did the business do, what moved that outcome, where does the pipeline stand for next quarter, and what happens next. A wall of tables can technically contain all four answers, but it does not make the room find them.

A QBR dashboard is a small set of charts built to answer those four questions before anyone opens their mouth. It is not one chart type, it is a sequence: the number the room is being judged against, the bridge that explains how it moved, the forward-looking read on the pipeline, and a scorecard for the underlying health metrics, closed out with a look at what the team is building next. This is a guide to building that sequence, chart by chart, and putting it together into something a room can read in the first two minutes of the meeting instead of the last twenty.

What a QBR dashboard needs to do
Step 1: Open with the growth number
Step 2: Show the bridge that explains it
Step 3: Add the forward-looking read
Step 4: Close the loop with a KPI scorecard
Step 5: End on what is next
Assembling and exporting the set
The mistakes that make a QBR dashboard fail
A few QBR dashboard structures worth copying
The two-minute version

What a QBR dashboard needs to do

A QBR dashboard fails when it is built around what data exists rather than what the room needs to know, in order. The room needs an answer to four questions, in sequence: how did the business do against what was expected, what forces moved that number in either direction, what does the pipeline say about next quarter, and what is the team building in response. Answer them out of order and the meeting spends its first ten minutes reconstructing context it should have had on slide one.

No single chart answers all four questions, which is why a QBR dashboard is a small set of different chart types working in sequence rather than one dense chart trying to do everything. A growth chart answers the first question, a bridge chart answers the second, a funnel answers the third, and a scorecard answers the fourth. Closing on a short look at what comes next turns the review from a postmortem into a working meeting. Each chart does one job, and the sequence between them is what turns four separate visuals into a single narrative the room can follow without someone standing over it explaining what it means.

Step 1: Open with the growth number

Every QBR is judged against one number before anything else gets discussed: revenue, MRR, active accounts, whatever the business actually tracks against a plan. Open with that number as a growth trend, this quarter next to the last several, so the room sees direction before it sees detail. Do not explain the number yet. The room needs to see where it landed before it is ready to hear why.

Which chart to use depends on the business. A subscription business showing recurring revenue is usually best served by an MRR chart, and the guide to building one covers the new, expansion, contraction, and churn components worth tracking underneath it. A business without a recurring core is often better served by a straightforward revenue growth chart, and the guide to building that version covers choosing an honest time frame. Either way: one chart, one number, no secondary metric competing for attention on the same slide.

Step 2: Show the bridge that explains it

The bridge answers the question the growth chart raises but does not answer: what actually moved the number. A waterfall chart stepping from last quarter's total through new business, expansion, churn, and contraction to this quarter's total shows the room the composition of the change, not just its size. The guide to building a waterfall walks through the revenue bridge structure directly: anchoring the two totals, ordering the steps, and reconciling the arithmetic before anyone presents it.

This is the slide that earns or loses credibility for the rest of the meeting. A bridge that reconciles, start plus every step equals end, tells the room the numbers can be trusted. A bridge that does not reconcile, or one that quietly buries a bad number inside a vaguer step to dodge a hard question, gets caught by someone in the room doing the arithmetic in their head, and the rest of the deck gets read with suspicion after that.

Step 3: Add the forward-looking read

Everything up to this point has looked backward. The funnel is where the dashboard turns forward and shows whether next quarter's number has a reasonable chance of landing. A funnel chart through the pipeline stages, leads, qualified, proposal, closed, shows where volume is dropping and whether the top of the funnel is wide enough to produce next quarter's target. The guide to building a funnel covers prepping stage data so the drop-offs reflect the actual sales process rather than a simplified version of it.

Skip this chart and a QBR becomes a report on what already happened with no read on what is coming, which is a common reason these meetings feel like a formality rather than a working session. A room that can see the pipeline can ask a useful question about it before the quarter is over, instead of finding out at the next QBR that it was thin.

Step 4: Close the loop with a KPI scorecard

A business tracks more than one number, and the scorecard is where the rest of them live without each getting its own slide. A KPI scorecard puts churn, activation rate, net revenue retention, whatever the operational metrics are for the business, on one screen with a clear read on each: on track, at risk, or off plan. It is a status check, not a story, and it belongs after the narrative slides, not before them, because a room that has not yet seen the growth number and the bridge has no context for whether a secondary metric moving is good or bad news.

Keep the scorecard to the metrics the room actually acts on. A scorecard with twenty rows gets skimmed, not read, and the two or three numbers that actually change a decision get lost in a list built to look thorough rather than to be useful.

Step 5: End on what is next

The last question a QBR needs to answer is what the team does with what the first four slides just showed. A short roadmap slice, the now and next columns rather than the full year, gives the room a place to land: here is what changed, here is what we are doing about it. The guide to building a roadmap covers choosing a time horizon and a layout that fits either a single team or several working in parallel.

This slide is often the one cut for time, and it is the one worth protecting. A QBR that ends on the scorecard leaves the room with a status update and no sense of what happens because of it. Ending on a short, honest look ahead is what turns a review of the past quarter into a decision about the next one.

Assembling and exporting the set

With the five pieces chosen, growth chart, bridge, funnel, scorecard, roadmap, putting the set together follows the same workflow each time.

Build each chart in its own generator, using the same color and font theme across all five so the set reads as one deck rather than five unrelated exports.
Keep every chart to the one job described above. Resist the urge to add a secondary metric to the growth slide or a status column to the bridge; that is what the scorecard is for.
Order the exports growth, bridge, funnel, scorecard, roadmap, and keep that order in the deck. The sequence is doing real work.
Export each piece by destination and assemble.

The destination sets the format:

Presenting live, in the room or on a call: an MP4 for each chart, playing in as you reach that part of the story, keeps the room's attention on the point you are making rather than the whole slide at once. This is the format QBRs are built for; almost nobody is reading this on their own time.
Sending ahead of the meeting, for a board or an investor update: static PNG exports read cleanly without narration, since the recipient is moving through it alone and needs each chart to stand on its own.
Archiving in a wiki or a shared drive for reference after the meeting: SVG keeps every chart sharp regardless of how it gets resized later.

A QBR dashboard exported as five loose files is still five files. Naming them in presentation order and keeping the same visual theme across all five is what makes them read as a single deck instead of a folder of unrelated charts.

The mistakes that make a QBR dashboard fail

A QBR dashboard breaks down in a handful of predictable ways.

Leading with the scorecard instead of the growth number. A wall of status indicators with no context reads as noise until the room has seen the number it is meant to support.
A bridge that does not reconcile. The fastest way to lose the room's trust in every other chart on the deck.
No forward-looking chart at all. A dashboard of only backward-looking charts turns the meeting into a report on a quarter that is already over.
A scorecard with too many rows. If everything is tracked, nothing is prioritized, and the metrics that actually matter get buried in the ones that do not.
Cutting the roadmap slide for time. The slide most likely to get dropped is the one that gives the meeting a reason to have happened.
Five charts, five different color themes. Built separately over a week by different people, they stop reading as one narrative and start reading as five unrelated exports stapled together.

A few QBR dashboard structures worth copying

Take the sequence above and adjust which charts you drop or keep depending on the room.

The standard five-chart deck

Growth chart, bridge, funnel, scorecard, roadmap, in that order. This is the version for the primary quarterly review with the full team or leadership present, where the room has time for the full narrative from where the number landed through what happens next.

The board-ready short version

Boards rarely need all five. A growth chart, a bridge, and a short roadmap slice cover what a board actually asks: where did we land, why, and what are we doing next. The funnel and the full scorecard are useful detail a board can request if it wants them, but leading a board meeting with all five slows down a room that came for three answers, not five. The investor update generator is built for exactly this shorter sequence.

The team-level QBR

A single team's quarterly review swaps the business-wide growth chart for a metric that team owns, and often swaps the revenue bridge for a headcount bridge if the story that quarter is about hiring and attrition rather than revenue. The funnel becomes optional depending on whether the team has a pipeline of its own, and the scorecard narrows to the handful of metrics that team is actually measured on. The sequence still holds: land the number, explain it, look forward, close with what is next.

The two-minute version

The whole method, condensed:

Open with the one growth number the room is judged against, nothing else on that slide.
Show the bridge that explains what moved it, and check that it reconciles before anyone presents it.
Add a forward-looking funnel so the meeting says something about next quarter, not just the last one.
Close operational detail into one KPI scorecard, kept to the metrics that actually change a decision.
End on a short roadmap slice, now and next, so the meeting produces a decision rather than just a status update.
Keep the same color theme and export order across all five so they read as one deck, not five unrelated charts.

A QBR dashboard is not the whole spreadsheet made prettier, it is the four questions the room actually has, answered in the order they are asked, with a fifth chart at the end that gives the meeting somewhere to land. Build the five pieces in sequence, keep each one to its one job, and the review stops being forty slides someone reads out loud and starts being a meeting the room can follow without a narrator.

Build the whole QBR set without leaving one tab. Paste your numbers, pick each chart, export the set as MP4, PNG, or SVG. No design skills, free to start. Create your first chart free →