How to Make a QBR Presentation

The quarterly business review is one of the most common recurring meetings in a company, and yet one of the easiest to get wrong on slides. Internally, a QBR is how a team reports to leadership: here is what we said we'd hit, here is where we landed, here is why, here is the plan. Externally, especially in customer success and account management, a QBR is how you show a client the value they are getting and align on priorities for the relationship going forward. Both versions share the same backbone even though the audience and the tone differ.

What makes a QBR distinct from a general status update is the comparison built into it: goals set at the start of the quarter versus results at the end. That comparison is the spine of the whole deck. Everything else — the KPI trends, the wins, the misses, the learnings — exists to explain that gap, not to replace it. A QBR that skips the goals-vs-results framing and jumps straight to a metrics dashboard leaves the audience to do the hardest part of the analysis themselves.

A QBR is also forward-looking, not just a retrospective. The last third of the deck should set up the next quarter with specific priorities, targets, and — where relevant — a clear ask of the people in the room, whether that's budget, headcount, a decision, or a client's continued investment. A QBR that only looks backward is a report; a QBR that also looks forward is a plan.

1. Cover slide. The quarter, the team or account name, the date, and who is presenting. Simple, but it frames what follows — get the quarter and scope unambiguous from the first second.

2. Executive summary. One slide, three or four bullets: did we hit our goals, what is the headline win, what is the headline miss, and what are we asking for. Busy stakeholders should be able to leave after this slide and still know the shape of the quarter.

3. Goals vs. results. Restate the goals set at the start of the quarter, side by side with actual results. This is the anchor slide of the whole deck — every later slide should trace back to explaining a number here.

4. KPI dashboard. Three to six core metrics, each shown against its target and its trend over the last few quarters, not just this one. Pick the metrics that actually explain the goals-vs-results gap, not every number you track.

5. Wins. What went well, quantified and attributed to a cause you can repeat. A win without a "because" is just a good quarter you got lucky on.

6. Misses and challenges. What fell short, stated plainly, with the honest reason. This is the slide people remember whether you handled well or dodged.

7. Market or account context (optional). External factors that shaped the numbers — a market shift, a competitor move, a client reorg. Use this to explain, never to excuse.

8. Learnings. What you now know that you didn't last quarter, and what you are doing differently because of it. This is the slide that proves the review changed something.

9. Next-quarter plan. Specific priorities and targets for the coming quarter, tied directly to the wins, misses, and learnings you just covered.

10. Risks and asks. What could derail the next-quarter plan, and what you need from the room — budget, headcount, a decision, a client's sign-off — to hit it.

11. Close and appendix. A one-line summary and a clear next step, with detailed data tables and backup charts held in an appendix rather than the main line.

The goals-vs-results slide only works if the goal is the one you actually committed to. It is tempting, when a number falls short, to quietly reframe the target — but stakeholders who were in the room last quarter will notice, and it costs more credibility than the miss itself. Write down the original goal at the start of the quarter and hold yourself to that exact number in the review.

Resist the urge to show every metric you track. A QBR is not a data dump; it is an argument for why the quarter went the way it did. Pick the three to six KPIs that best explain the goals-vs-results gap — pipeline generated if the goal was revenue, activation rate if the goal was retention — and cut the rest into an appendix. If a metric doesn't help someone understand why the headline number moved, it doesn't belong on the main dashboard slide.

Trend lines beat single numbers almost every time. A metric shown only for this quarter tells you where you landed; a metric shown across the last four to six quarters tells you whether that's a blip, a trend, or a new normal. This is also where chart choice matters: a simple line or bar chart with the target marked as a reference line does more work than a table of numbers, because the audience can see the gap instead of calculating it.

Put the "why" directly on or beside each metric, not in a separate narrative slide the audience has to mentally reconnect. A KPI slide that just shows "MRR: $412K, target $450K" leaves the room guessing; "MRR: $412K vs. $450K target — enterprise renewals slipped two weeks into next quarter" tells the whole story in one line. The goal of a QBR metrics slide is not to display data, it is to make the data make sense.

A win is only useful if it is repeatable, so attach a cause to every one you present. "Churn dropped to 4%" is a fact; "churn dropped to 4% after we moved onboarding calls to day three instead of day ten" is a lesson the rest of the org can act on. Quantify wins wherever you can and be specific about what drove them — the specificity is what separates a genuine highlight from a slide that just feels good to present.

Misses deserve the same directness. The instinct in front of leadership or a client is to soften a miss until it barely reads as one, but audiences can tell, and the deck loses credibility the moment they suspect spin. State what fell short, by how much, and why, in plain language — "we missed the activation target by 6 points because the new signup flow shipped three weeks late" — and resist pairing it with an immediate excuse. One honest miss slide builds more trust than five overly positive ones.

Learnings are the slide most QBRs skip, and it is the one that proves the review was worth having. A learning is not "we should communicate better" — it is a specific, falsifiable change: "we're moving QBR prep to a shared doc two weeks out instead of a deck built the week of, because three of the last four decks were rushed." If your learnings slide could have been written after any quarter, it isn't specific enough to be useful.

Sequence matters here too. Lead with wins to set a fair tone, move into misses while the audience is still engaged rather than fatigued, and land on learnings so the deck ends on what changes next rather than on the bad news. That order keeps a QBR feeling like an honest review instead of either a victory lap or a confession.

The single biggest mistake is not making goals-vs-results the centerpiece. Some QBRs bury the comparison in a footnote or split it across five different metric slides, forcing the audience to reconstruct the story themselves. Put the goal next to the result, on one slide, early in the deck, and make sure every following slide clearly connects back to it.

A close second is vanity metrics — numbers that went up and feel good to show but do not connect to the goal that was actually set. Total signups, page views, or "engagement" can look impressive while the metric that mattered, like qualified pipeline or net revenue retention, quietly missed target. Every metric slide should earn its place by explaining the goals-vs-results gap, not by looking good in isolation.

Presenting a miss without a reason is its own failure mode, and so is over-explaining a win with excessive caveats that undercut it. Both come from the same instinct: managing the room's emotional reaction instead of just reporting what happened and why. State the number, state the cause, move on — the audience trusts a deck that treats them like adults more than one that's clearly trying to manage them.

Finally, a QBR that ends without a specific ask wastes the meeting it took to assemble. "Thanks for listening" or a generic "let's keep pushing" gives the room nothing to act on. Close with a named decision, resource, or commitment you need, and from whom, by when — that is what turns a review of the past quarter into a plan for the next one.

A QBR usually already has its raw material sitting somewhere: a metrics spreadsheet, last quarter's deck, a CRM export, or a written report from a department lead. Eazy is built to start there. Drop in a PDF, Word doc, Excel or CSV file, or a web link and Eazy reads it into editable content instead of asking you to copy numbers into a prompt or rebuild slides from a blank grid. You can also draft a first pass directly from a prompt if you're starting closer to scratch, then shape it from there.

Either way, the document is the source of truth. Write the goals-vs-results framing, the KPI notes, the wins-and-misses language, and the next-quarter plan as real structured content — headings for each section, bullets for the specifics, slide dividers where one topic ends and the next begins — the same order covered in the outline above. Because you are writing rather than prompting, it is easy to get the goals-vs-results comparison and the honest miss language exactly right before anything gets designed.

When the content is right, design is a separate, later step: every slide is designed for you and on-brand by default, and you can apply a theme to restyle the whole deck in one click if you want a different look for a different audience, like an internal review versus a client-facing one. If leadership asks you to update one KPI or reword a miss after the meeting, change that line in the document and only the affected slide rebuilds — the slides that already looked right stay untouched.

For the metrics dashboard specifically, get the chart choice right before you design it: a trend line with the target marked usually communicates a QBR number better than a bare table, and a bar chart works well for comparing this quarter against several past ones side by side. When you're ready to present, export the finished deck to PDF or PPTX — free early access includes credits and no watermark, so the QBR you build is the one you actually hand to the room.