Quarterly Business Review (QBR) Presentation

QBRs serve two entirely different purposes depending on who's in the room. An internal QBR is a performance accountability meeting: what did we commit to, what did we deliver, what are we changing. A customer-facing QBR is a relationship and value demonstration meeting: here's what we accomplished together, here's what's possible next quarter.

Both require different slide structures, different tones, and different definitions of success. Mixing them — running the same deck for internal reviews and customer meetings — produces a presentation that's too operational for customers and too thin for executives.

This template covers both types separately, then addresses the structural elements they share.

Internal QBR: Structure and Template

The internal QBR deck is the operating rhythm of an executive team. Its job is to create shared understanding of performance, surface the root causes of misses, align on changes, and set commitments for the next quarter. An internal QBR that doesn't produce changed behavior is a reporting exercise, not a management tool.

Slide 1: Quarter at a Glance

A single scorecard slide with every major metric from the quarter: revenue, bookings, retention, pipeline, product milestones, and team headcount. Each metric shows actuals vs. plan. Color-coded performance (green/yellow/red) lets the room quickly orient on where the discussion should focus.

This slide is often the most contentious to design because it requires agreement on what the most important metrics are. If your leadership team argues about what belongs on this slide, that's a valuable argument to have — it surfaces misalignment about what the business is actually optimizing for.

Slides 2-3: Revenue and Pipeline Deep Dive

Two slides dedicated to revenue performance and forward-looking pipeline. For SaaS companies:

Revenue slide: ARR bridge (opening ARR → new bookings → expansion → contraction → churn → closing ARR), NRR, and gross margin trend. The bridge format makes it immediately clear whether the business is growing from strength (high new and expansion) or struggling with retention (high contraction and churn).

Pipeline slide: pipeline by stage, pipeline coverage ratio (pipeline / quota), average deal size trend, and sales cycle length trend. Coverage under 3x at the start of the quarter is a leading indicator of a miss. Sales cycle extension is an early signal of buyer hesitancy or qualification problems.

Slides 4-6: Departmental Review

One slide per major function — Sales, Marketing, Customer Success, Product, and Engineering — covering three elements: what we said we'd do, what we did, and what we're changing.

What we said we'd do: the specific OKRs or goals committed to last QBR. These should be quoted verbatim from last quarter's deck. Changing the wording between quarters to make outcomes sound more positive than they are is a red flag.

What we did: actual results against those commitments. Wins deserve brief recognition; misses deserve honest analysis. "We said we'd launch feature X by Q3. We launched it in Q3+6 weeks because the integration was more complex than scoped. Here's what the scope assessment missed and how we've changed our estimation process."

What we're changing: the forward-looking adjustment. Not a list of activities — a specific change to strategy, process, or resource allocation that addresses what the data revealed. If last quarter's miss doesn't change anything next quarter, the QBR is theater.

Slides 7-8: Root Cause Analysis

Two slides — one for the biggest miss, one for the biggest underperformer by segment or region. Root cause analysis is the highest-leverage part of the internal QBR and the most commonly rushed.

Five-why structure on a slide: Start with the symptom (NRR dropped 8 points), work backward to root cause (enterprise customers are churning faster than mid-market), then to mechanism (enterprise customers on legacy pricing plans have significantly different onboarding and CSM coverage than new enterprise customers), then to systemic fix (we're migrating legacy enterprise accounts to new success model over Q4).

The goal is to move from "we missed because of market conditions" (diagnosis that changes nothing) to "we missed because of X in our process and we're changing X to Y" (diagnosis that changes behavior).

Slide 9: Q4 Commitments

A specific, measurable commitment table for the next quarter. Each commitment should have: the goal, the owner, the measurement criteria, and a note on what enabling resources or decisions are required.

This slide is reviewed at the start of next quarter's QBR as the "what we said we'd do" section. Commitments that are consistently vague or consistently revised signal that the leadership team doesn't trust the planning process — worth surfacing and fixing before it becomes a cultural norm.

Slide 10: Decisions Required

A short list of decisions that require leadership or board input that aren't within the management team's standing authority: headcount above budget, a strategic acquisition or partnership, a pricing change, or a go-to-market pivot. This closes the QBR with actionable outputs rather than a vague "great discussion."

Customer-Facing QBR: Structure and Template

The customer QBR has a different objective: demonstrating that your product or service is delivering value, deepening the relationship with executive stakeholders, and creating alignment on what success looks like in the next quarter. It is a strategic relationship meeting, not an operations review.

Customer QBRs that are structured as status reports — here's your ticket volume, here's your usage stats, here's your SLA performance — produce disengagement, not expansion. Executives who attend customer QBRs are evaluating whether the relationship deserves continued attention, not reviewing operational metrics they already get in monthly reports.

Slide 1: Executive Summary

One slide with the three to four most important things that happened in the quarter. Lead with value delivered, not activity completed. "Your team reduced manual reconciliation time by 40%, equivalent to 2.3 FTE hours per week" is a value statement. "We completed 47 support tickets and maintained 99.4% uptime" is an activity statement.

The executive summary is also where you surface any significant changes in your platform, roadmap, or relationship team — anything that affects the customer's planning.

Slide 2: Success Metrics Review

A review of the success metrics defined at the start of the engagement or at the last QBR. This is why success metrics matter: if you defined them together at the beginning, this slide shows progress toward shared goals. If you didn't define them, this slide is where you propose them.

Good success metrics are specific, owned by the customer, and tied to business outcomes: reduced time to close an audit, lower cost per processed transaction, higher Net Promoter Score from the customer's own customers. Bad success metrics are activity-based (number of features used) or unilaterally defined by the vendor without customer input.

Slides 3-4: Value Delivered

Two slides showing specific, quantified outcomes from the quarter. Use the customer's own metrics — data from their environment, not industry benchmarks or vendor estimates.

If you have access to customer operational data, show the before/after. If you don't, use what the customer's team has told you: "Based on your team's estimate of 4 hours per analyst per week spent on manual export, and 25 analysts on the platform, that's approximately 100 hours per week recovered — roughly $280K annually at an average fully-loaded analyst cost of $140/hour."

The specificity matters. An executive who can put a number on the value of your product in their organization is an executive who will advocate for renewal when procurement asks questions.

Slide 5: Roadmap Update

A brief summary of what you're shipping in the next two quarters that's relevant to this customer. Frame it in terms of their use cases and the outcomes it unlocks, not in terms of product features. "This quarter's release enables your team to automate the monthly variance analysis that currently takes three days — we'd like to schedule a configuration session in the first two weeks after launch."

Don't share roadmap items that aren't relevant to this customer. A healthcare customer doesn't need to see the financial services features you're building. Selective sharing signals that you know their business well enough to filter.

Slide 6: Next Quarter Plan

The forward-looking commitments: specific initiatives, rollout milestones, adoption goals, and success metrics for next quarter. Get explicit alignment on these in the meeting — not as a passive reading of a slide, but as an active conversation about priorities.

"We're proposing three focus areas for Q4: completing the integration with your ERP, expanding platform access to your regional teams, and reaching 80% weekly active user rate among your current licenses. Do these match your priorities?"

Customers who set joint priorities with vendors are more likely to achieve outcomes and attribute those outcomes to the partnership.

Slide 7: Expansion Conversation

If the customer has use cases not currently covered by their subscription — additional users, additional product modules, a new department — the QBR is the natural place to raise expansion. Frame it as a customer outcome, not a sales pitch.

"Based on what you've described about the operations team's workflow in our conversation today, we think there's an opportunity to extend what finance is doing to operations — that would expand the value we're delivering significantly. Want us to put together an analysis of what that would look like?"

This slide should not include pricing. It should identify the opportunity and propose a next step. Moving from QBR to commercial conversation in a single meeting is possible but requires that the customer raises it — not the vendor.

Elements Common to Both Types

Preparation: The Non-Slide Work

A QBR deck is the artifact; the preparation is the work. For customer QBRs, this means reviewing support tickets, usage data, and health scores before the meeting, and identifying two to three specific stories of value delivered that can be made concrete with data. For internal QBRs, this means every department head reviewing their own data honestly and identifying their own misses before walking into the room.

QBRs where leaders are surprised by their own metrics are QBRs where the management reporting process is broken. The deck shouldn't reveal new information — it should organize information everyone already knows into a shared framework for decision-making.

Slide Count and Meeting Length

Internal QBR for a 30-person company: 15-20 slides, 90-120 minutes. Customer QBR with an executive sponsor: 10-15 slides, 60-90 minutes. Customer QBR with an operational stakeholder: 8-12 slides, 45-60 minutes.

QBRs that run long almost always do so because root cause analysis was skimped — the meeting went deep on metrics and shallow on causes, producing discussion but no decisions. Allocate more time to the slide 9 equivalent (what are we changing) and less to reciting numbers from slides 3-5.