Quarterly Business Reviews — Complete Guide

Written by Alex Raymond, founder of AMplify and author of The Growth Department.

‍

A Quarterly Business Review is the strategic-altitude meeting you hold with a customer outside the day-to-day work, where both sides step back from tickets and timelines to talk about where the relationship is going. Most teams run it as a presentation. The QBR is better understood as a test: of whether the customer is committed, whether the relationship has the altitude to grow, and whether the renewal is real. How the customer shows up tells you more than anything on your slides. This page covers what a QBR is, how to prepare for and run one, what customers actually want from it, and how to read what it tells you.

What is a QBR (Quarterly Business Review)?

A QBR is the strategic-altitude meeting that operates outside the tactical layer of an account. It is not a status update, a project check-in, or a delivery review; bugs, change requests, and project management items belong in the regular operating cadence. The QBR is for the big-picture, forward-looking conversation: where the customer is trying to go, what is changing in their world, where the relationship grows next, and what could put it at risk. When tactical items eat the meeting, the QBR is broken.

The meeting matters because of what it reveals. A few times a year, this is when you find out whether the customer treats the relationship as strategic or as a line item, and that read is worth more than anything on your slides.

What QBR stands for, and why the name doesn't matter

QBR stands for Quarterly Business Review, and the name is the least important thing about it. Plenty of these are not quarterly at all. Some teams run them annually, some twice a year, some on whatever rhythm the account calls for. People call them all sorts of things: strategy reviews, annual reviews, business reviews, executive reviews, Annual Strategic Planning Meetings. The simplest approach is to bucket them all under QBR, since that is the lingo most people know. If a customer's culture is allergic to "QBR," call it whatever fits. What matters is the substance: a real strategic conversation with the customer, held at altitude, on a deliberate rhythm.

Anthony DeShazor, then leading Customer Success at the donation platform Givelify, ran his as Executive Business Reviews (EBRs), and picked that term on purpose to keep a frequency out of the name so the customer could set the cadence. The label was a tool, not a rule. The work underneath it was the same as a QBR done well.

What is a QBR for? Keep, Grow, No Surprises

The purpose of a QBR is to serve all three jobs of Account Management at once: Keep, Grow, No Surprises. It is where retention risk surfaces before it becomes a churn event, where expansion opportunity surfaces before a competitor finds it, and where the No Surprises discipline gets executed in front of you instead of in a post-mortem. That makes it the most effective risk-management and opportunity-identification instrument most teams have, rather than a courtesy off to the side.

Most leaders treat the QBR as a routine keep-the-customer-happy exercise. It is a foundational touchpoint. Account plans, segmentation, and risk management are non-negotiable on the internal side of the function; the QBR is the non-negotiable instrument on the external side, a fundamental part of a Post-Sale strategy rather than an item to get around to.

The economics are the reason to take it seriously. A renewed dollar costs roughly thirteen cents to earn; a new-logo dollar costs more than a dollar, at negative gross margin, with a payback period that often runs past two years. Existing customers deliver the profit, and the QBR is where that profitable revenue gets protected and compounded. The full economic case for the function lives on The Growth Department page.

Why most QBRs fail

Most QBRs are boring, backward-looking, and about the vendor. The team shows up with thirty slides recapping the last ninety days: tickets closed, bugs resolved, features shipped. The customer sits through it thinking the same thing every time. This could have been an email. They already know what happened. They lived it. Reporting it back to them is a use of an executive's hour that the executive resents.

Anthony DeShazor, who ran Customer Success at Givelify, says it straight: most QBRs are built for the vendor, not the customer. They exist to let the team show its work and prove it deserves to be there. Customers feel that, and a meeting built to make the vendor feel safe gives them no reason to attend. So they stop attending.

The failure shows up as a cascade of cancellations. Seventy-two hours out, the senior person drops. Forty-eight hours out, someone has the flu. Day-of, a contact joins twenty minutes late from an emergency somewhere else. The honest read is uncomfortable: if the meeting mattered to them, they would be there. When they are not, it is because the team is not giving them a reason to be, which makes it the Account Manager's failure, not the customer's. That is hard to hear, which is exactly why most teams keep running the same QBR and wondering why nobody comes.

How to think about QBRs: from presentation to test

The difference between a failing QBR and a strong one is a difference in what the meeting is for. Five reframes get a team there.

Obligation to opportunity. The old posture treats the QBR as a chore, a quota of twenty meetings a year to bash through. The new one treats it as a chance to spend an hour with people you can genuinely help. People make time for an expert who helps them get somewhere they want to go.

Data dump to curated insight. The old QBR is twenty-five to forty slides of dashboards, with pride taken in the volume. The new one puts the data in the appendix and brings the two or three things that actually matter. The customer hired the team to separate signal from noise, not to read the noise aloud.

Monologue to dialogue. The old QBR is the Account Manager talking for fifty-nine of sixty minutes, usually out of nervousness. The new one is a conversation the Account Manager facilitates, aiming for the customer to talk at least half the time.

Defense to offense. The old QBR is a justification: every slide is evidence the team has been good, every gesture an unspoken plea not to be fired. The new one is leadership, because the customer bought wanting guidance toward a result, and passive reads as weakness. This reframe connects to the deeper posture work in The Growth Department Mindset.

‍

About us to about them. The old QBR opens with a photo of the office, a map of global locations, the new senior hire, the industry award. The new one is about the customer's goals, challenges, and friction points from the first minute. The test is simple: open the deck and look at the first ten slides. If they are about the team, the meeting is about the team, and the customer knows it.

What customers actually want from a QBR: The Access, Insights, Alignment framework

The Access, Insights, Alignment (AIA) framework names what customers actually want from a QBR: access to the company's experts, insight they can't get elsewhere, and alignment around their outcome. Ask the executives who sit through these meetings, and the answers converge on those three.

Access is the customer's desire to meet the smart people behind the product, the ones they otherwise never see: the engineer, the product leader, the researcher, the executive. This is why the rule is to not show up solo. A customer who gets the same two faces every quarter is getting a relationship review, not access to the company's brain trust.

Insights are the information and perspective the customer cannot get anywhere else: pattern recognition from the team's work across many customers, a forward-looking read on what is coming, the two or three things distilled from the noise. Not a fifty-page report. Judgment applied to their situation.

Alignment is the customer's need to know that the problem they bought the team to solve is the problem the team wakes up thinking about. They want to feel that their use case sits at the center, not off to the side, that the team is putting their outcome first instead of splitting attention across a hundred others.

‍

Brad Englert spent years as the Chief Information Officer at the University of Texas at Austin, sitting on the receiving end of vendor QBRs, and he wanted exactly those three things. He liked the vendors who showed up already knowing the university's published values and priorities, the kind of thing that takes five minutes to look up. The ones who had not bothered were wasting his time. He wanted access to the smart people, and he wanted to know how he compared and what was coming. That is a senior buyer telling you what he wanted when the meeting was for him.

For an operator, Alignment means measuring what the customer actually cares about. At Givelify, DeShazor built the review around whether nonprofits were turning one-time givers into repeat ones, helping their donors become the most generous version of themselves, instead of around transaction fees and dollars raised. The QBR stops being about the vendor's output the moment it gets built around the customer's outcome.

A useful diagnostic: score yourself one to ten on your QBRs, then score how the customer would score you, and look at the distance between the two numbers. The distance is the work.

How to prepare for a QBR

Preparation is where the QBR is won or lost, and most teams under-invest in it. The work has five parts:

The pre-QBR audit. Review every artifact on the account: the account plan and whether it is current, voice-of-customer notes, satisfaction data, usage, the org chart, any value-tracking metrics. If those artifacts do not exist, the team has an Account Management hygiene problem larger than the QBR.
The internal stakeholder sync. Talk to everyone on your side who has touched the account since the last review: support, product, marketing, implementation. The meeting goes wrong the moment the customer mentions a conversation they had with a colleague ten days ago that the Account Manager knows nothing about.
The prior-commitment audit. Go back to the last QBR and check what the team committed to. Did it happen? The only person who has not forgotten what the team promised last time is the customer, and they are watching to see whether the team does.
The blind-spot list. Before the meeting, write down what the team does not know: the open questions, the hypotheses to test, the things to confirm. That list becomes the spine of the questions asked in the room.
Coaching the customer to prepare. Customers have only ever been participants in QBRs; they have never run one. Send materials in advance, tell them what is needed, ask them to talk to their own leadership beforehand. The first time, the customer looks confused. By the third, they show up with their own preparation, because they have learned the meeting is worth it.

Jim Richmond, Chief Customer Officer at Smartling, does something sharp with prep. His team walks in with a written guess at what the customer values, then asks the customer to correct it. An outsider made the guess, so it is usually wrong, and that is the point. People will jump in to fix the record and show off what they know about their own business. A wrong guess put on the table openly pulls more out of a customer than a careful open-ended question does.

Who should attend a QBR

Three rules govern who comes:

Every attendee adds value, on both sides of the table. No passive observers, no one along just to listen in. If someone is there, they have a role, and the team that brings three people who contribute beats the team that brings six who watch.
Seniority should match across the table. If the customer brings a C-suite executive and the team brings a junior contact, the executive feels the meeting is below their altitude and checks out. Bringing senior people of your own is also the access customers are looking for in the first place.
Who the customer sends tells you the most. A team can run a flawless agenda and still be in trouble if the customer sent a junior stand-in for the people who actually decide. The reverse is true too: a senior attendee who engages is a stronger signal than any health score. Look at who showed up before you read anything else.

There is a way this goes wrong that hides in plain sight. A leader rolls out QBRs across the whole customer base, proud of the new discipline, and never asks who the meetings are actually with. Pressed on it, the honest answer is usually whoever will take the call. A QBR with whoever answers is activity dressed up as the meeting. It gives you none of the read the meeting exists to give.

What a QBR agenda should contain

A strong QBR agenda contains four things:

Co-created items, not a vendor script. Send a draft to the champion and ask what to add; customers rarely arrive with their own items, but asking enrolls them and turns the meeting into a shared object. If the customer will not engage on the agenda at all, that itself is a flag.
Protected strategic altitude. The most common way a QBR collapses is the tactical hijack, where day-to-day issues eat twenty minutes and crowd out the strategic conversation the senior people came for. Joanna Hagelberger handles it cleanly: she tells the customer those tactical items are important, offers thirty minutes that week to deal with them, and keeps the QBR at altitude. A QBR that goes tactical makes the team look small in front of the customer's leadership.
A small, consistent metrics block. A short slice of the customer's own metrics belongs on every agenda, so both sides track the same numbers over time. It is a slice of the meeting, with the bulk of the time going to the conversation about what is ahead.
Pre-read materials, sent in advance. Tell the customer directly that the deck is a pre-read and the meeting is for discussion. Putting the work of reading on the customer adds friction, and the friction increases commitment. The hour together is too valuable to spend narrating slides everyone could have read alone.

How to run the QBR meeting

The skill the meeting demands is facilitation, not presentation: run a conversation, pull every voice in, name what people are avoiding, and make room for the customer to talk. A useful target is an eighty-twenty split, the team presenting twenty percent of the time and the conversation filling the rest. A team talking eighty percent is presenting, and the customer has checked out.

What drives that conversation is the voice-of-customer question: open-ended, forward-looking, strategic, and about the customer rather than your product. "How do you feel about our product?" earns a platitude, because the customer reads what the team wants to hear and reflects it back. Build your strong questions so the customer cannot guess the answer you want: what is the biggest priority your board is discussing, what has changed in your strategy for the year ahead, what would it take to make you a ten-year customer, and if the renewal were today, would the answer be yes.

A few mechanics make the questions work:

Set up the big question with a preamble so it never lands cold and the customer has a moment to raise their own altitude.
Send the most strategic questions in advance. The more strategic the question, the more notice the customer needs to answer it well.
Let the silence sit. When a question lands and the customer goes silent, wait. They usually fill it.
Ask "what else?" and stop talking. After a first answer, the second and third answers are the honest ones.

When a risk surfaces in the meeting, say so right then rather than note it silently and press ahead. "You sounded concerned about that a moment ago, can we talk about it?" Raising the hard topic builds trust and surfaces information that would otherwise walk out the door. One override holds above all of this: if something is broken when the QBR happens, abandon the agenda and spend the time on the thing on everyone's mind, because running a polished review while an operational fire burns costs credibility the team cannot easily rebuild.

How to read the QBR: the signals that matter

This is the payoff. Teams run QBRs to be polite and then never stop to ask what the meeting just told them. The signals are sitting in plain view: who showed up, when, whether they read the materials, whether they paid attention, whether they asked real questions, whether the conversation turned toward the future or stayed stuck in the past. Each one is data about whether the revenue will be re-earned.

Some signals are loud enough to override everything else. A customer who ghosts the QBR is not a scheduling hiccup; every indicator on the health score should go to red. A junior person sent in place of the executive who used to come is a message, and so is an executive who walks out after twenty-five minutes. This is the meeting telling you the truth, and your job is to act on it rather than finish the agenda and run the debrief like everything is fine.

The risk categories worth listening for are specific:

Engagement risk shows in the room itself, in attention, attendance, and the quality of the questions.
The silent detractor is the unhappy stakeholder who is not saying so. A complaint raised out loud is good news, because it is now visible and workable; the dissatisfaction nobody voices is the one that festers.
Organizational change risk is the highest-priority category of all, because nothing ends a relationship faster than the executive sponsor leaving. Its variants, senior turnover, a new leader with a competitor's history, an acquisition, a new strategy, all force the team to re-earn a relationship it thought was secure.
Value risk shows when the customer cannot articulate what the product is doing for them.
Operational risk is the broken promise and the missed timeline.

Each one is a thing to hear and name, not a box to tick.

Jim Richmond goes after this early. His top number is gross revenue retention, and there is a note stuck to the wall in front of his desk that says "only bad news," because gross retention can only fall from a hundred percent, so the job is to catch the risk while it is still fresh enough to fix. He wants the team to celebrate fresh bad news. It is the same idea as the silent detractor: the surprise you catch in the QBR is the one you can still do something about.

The QBR is also where growth surfaces, as long as the team is listening rather than pitching. The questions that open opportunity are about the customer's wider organization: what has changed in their strategy for the year, what other teams have the problem the team is already solving, who else inside the company is wrestling with it. It helps to ask about the customer's own customers, because the promises the customer made downstream are where the next problem worth solving usually lives. Surface the opportunity and name it, then follow up separately. The QBR is not the place for a demo or a pitch.

The Risk Register

The Risk Register is the operational artifact that turns risk listening into a system. The per-account version records, for each risk:

The risk, named clearly.
Severity, high, medium, or low.
Indicators, the observable signals.
A resolution plan, with a named owner.

The global version rolls every account's risks into a portfolio view sorted by severity, reviewed on a recurring cadence in a meeting some teams call a get-to-green meeting, which should include the CFO or a designate, since the CFO owns the revenue forecast and can free the resources to address what surfaces. A risk that lives only in someone's head is not a system. The Risk Register is how the team stops holding that weight alone and how patterns across accounts become visible, since one customer's early warning is often another customer's coming problem. The mechanics live on the Commitment page and the operating rhythm that sustains them on the Cadence page.

How to follow up after a QBR

Almost nobody follows up on a QBR well, which makes disciplined follow-up one of the cheapest ways to stand apart. It has three parts:

The internal debrief, the same day or the next, structured rather than casual. Everyone who attended joins, because everyone heard something different and each holds their read with full confidence. The debrief reconciles those reads into one account of what happened, what risks surfaced, and where the opportunities are.
The QBR scorecard, rating the meeting on a few simple dimensions: how engaged the customer was, whether the conversation felt aligned, whether the team delivered value, whether the customer is open to what comes next. Tracked over time, the scores turn engagement and value into visible trends across an account. Almost no team does this, which is exactly why doing it is an edge.
The joint commitment plan, the artifact both sides walk away owning: the team commits to specific actions by specific dates, and so does the customer. A follow-up where the team has fifteen action items and the customer has none is a team back on defense.

Feed whatever the debrief surfaced into the Risk Register, and book the next QBR before the customer leaves the room, while it is easy to commit rather than a calendar to chase later.

How to tell if a QBR went well

A QBR went well if the team left it knowing whether the renewal is real and whether the relationship has the altitude to grow. A landed deck or an impressive demo are presentation outcomes, and you judge a QBR as a test, not as a presentation.

Here is what tells you it went well:

The right people attended and engaged.
The conversation spent most of its time on what is ahead.
The customer talked at least half the time.
A risk got named and worked rather than buried.
Both sides left owning specific commitments.

Score the meeting against those dimensions and watch the trend across quarters: a QBR that scores well and keeps climbing means the team is re-earning the relationship, while one that looked polished but told the team nothing it can act on was a performance, no matter how good.

How often should QBRs happen?

Not every account needs a QBR every ninety days. The quarterly clock in the name is a convention, and treating it as a requirement is a fast path to burnout and to thin meetings the team did not have the energy to make worthwhile. Cadence should follow potential and value, not the calendar.

Segment the portfolio and set the rhythm to match. Kristy Devantier, who leads the account function at TaleWind Digital, runs her strategic reviews on a tiered cadence, four times a year for the highest-potential accounts, twice for the middle, once for the rest. Justin Strackany, formerly Chief Customer Officer at SecureLink, tiered his book into managed, strategic, and executive accounts, with an internal executive sponsor attached to the top tier and the heaviest cadence reserved for the accounts with the most at stake. Both are working off the same math: a small share of accounts produces most of the growth, so your deepest attention belongs on the accounts with real upside. Stretching the interval on a steady account so you can actually prepare for a high-potential one is the right trade. The goal is not more QBRs. It is the right QBR with the right customer at the right altitude.

For a leader installing this across a team, the failure to plan around is the rollout that becomes theater. A leader pushes QBRs across the whole base, the team books whoever will take the call, and the program produces activity without the read it exists to give. The fix is to manage two things at the portfolio level rather than count meetings. The first is attendance quality: track whether the right seniority showed up on the accounts that matter, because a tiered cadence only works if the top tier is actually getting senior engagement. The second is the QBR scorecard, rolled up across the book, which turns a pile of meetings into a trend a leader can act on, and which feeds the global Risk Register that a CCO reviews with the CFO. A count of completed QBRs only tells a leader the team is busy, while the scorecard and the Risk Register tell a leader whether the revenue is safe.

The pattern across the practitioners

Anthony DeShazor pulled the whole thing together at Givelify. He rebuilt the Executive Business Review around the customer's outcome instead of the vendor's output, talked about consistent donors instead of transaction volume, and asked customers for two focused hours a year. The team beat its growth target eight quarters running, hitting eight to ten percent against a four percent goal most of the time. He will tell you that the customers who sat through an EBR did not churn, and in the next breath that the harder, more telling work was getting the resistant ones to show up at all, the ones it took six or seven months to land. That is the test in practice: who shows up is the signal, and earning that is the job.

Joanna Hagelberger ran the same play on the growth side. At Vertafore she took one account from fifty thousand dollars to ten million in annual recurring revenue, a two-hundred-fold jump, and then did it again at a different account, two hundred thousand to five million. It started with a question she asked in a strategic review: where do you want to be in five years. The customer had never been asked that, went away to whiteboard an answer, and came back with bigger ambitions than the relationship had ever held. That is the question a backward-looking QBR never gets around to asking.

What this means for the function

The QBR is the highest-return instrument a Post-Sale team has for reading whether the revenue will be re-earned, and the excuses for letting it slide are getting more expensive. The team that decides AI has changed the job, that customers do not need to be called, that nobody travels or gets together anymore, is giving up the one read that tells it the truth about its accounts before the renewal does. Run the QBR as a test, read what it tells you, and act on the signal while there is still time to act.

‍

About the author Alex Raymond is the founder of AMplify and the author of The Growth Department, the operating standard for the function that delivers most of a company’s revenue. He spent a decade building Account Management and Customer Success systems with B2B companies before founding AMplify, where he works with Post-Sale leaders on installing the Growth Department Method. He hosts the Account Management Secrets podcast.