Most QBRs are 90 minutes of slides nobody reads, ending with vague action items nobody owns. The customer leaves without learning anything new. The CSM leaves without an expansion path. The next quarter looks identical.
A QBR is not a status update. It is a forcing function for value reinforcement, executive alignment, risk surfacing, and expansion. Run it well and it is the highest leverage hour you spend with a strategic account each quarter.
This post covers what a QBR is and is not, the types of QBRs, a 7 section agenda, who should be in the room, the most common mistakes, and how to operationalize QBRs in Salesforce.
What QBR means
QBR stands for Quarterly Business Review. The phrase has two distinct uses depending on context.
Customer facing QBR
A formal review with the customer's executive team and the seller's account team. The point is to reinforce value delivered, surface risks, align on the next quarter, and uncover expansion paths.
This is the QBR most B2B sellers and CSMs run. It is what most of this post covers.
Internal QBR
A leadership review of a function (sales, marketing, product) inside the company. Each leader presents results, plans, and asks. Usually owned by the CFO or COO.
Same name, different ritual. Internal QBRs follow a different agenda focused on results, headcount, and budget.
The two should not be confused. A customer QBR is about your customer's business. An internal QBR is about yours.
What a QBR is not
Three things QBRs are not, even though most teams default to running them this way.
Not a status update
Status belongs in monthly check ins and the customer success platform. If the agenda is mostly "here is what we did this quarter," the customer's executives will skip the meeting next time.
Not a roadmap pitch
The customer wants 5 to 10 minutes of roadmap, not 45. If half the deck is product preview, the meeting is a sales pitch with a different label.
Not a single function meeting
A QBR with only the CSM and the buyer's program manager is a check in. A real QBR includes the executives who can decide on expansion, escalate risks, and approve scope changes.
When all three of those failure modes show up, the QBR turns into theater. Both sides go through the motions and nothing changes.
QBR types
Three useful distinctions within customer facing QBRs.
Account specific QBR
The most common form. One customer, one account team, one agenda. Focused on the specific account's outcomes and plans.
Run for top 10 to top 50 accounts depending on team size. The depth justifies the effort.
Team or program QBR
A single customer with multiple programs or business units. Each business unit gets its own short section, with a wrap up across the portfolio.
Common in strategic accounts where the seller has 3 to 10 active workstreams.
Vendor portfolio QBR
The customer reviews multiple vendors back to back, often as part of a broader procurement or vendor management ritual. The seller gets 30 to 60 minutes.
Constraints the agenda. The seller has to deliver value reinforcement, the headline expansion ask, and risks within tight time.
The first type is the default. The other two require adjustments to the standard 7 section agenda.
The 7 section QBR agenda
A QBR runs 60 to 90 minutes. The agenda has seven sections, weighted by importance.
Section 1: Business outcomes (10 minutes)
Open with the customer's stated business outcomes from the original deal. Restate them.
Then map the last quarter's progress against each outcome. Use the customer's metrics, not yours.
If the original outcome was "reduce time to onboard new vendors by 30 percent" and the last quarter delivered 18 percent, that is the data point. Not "we delivered 14 features."
Section 2: Value delivered (15 minutes)
Quantify the value. Dollars, hours, headcount, risk reduction. Whatever the buyer's CFO would care about.
The format that works: outcome, baseline, current state, value to date, projected annual value.
Example: "Onboarding cycle. Baseline 11 days. Current 7 days. Value to date $340K in faster supplier activation. Projected annual $1.4M."
This section is where the customer's executive sponsor decides whether the relationship is worth defending. Make it specific. Make it verifiable. Cite the customer's data, not yours.
Section 3: Risks (10 minutes)
Surface the risks. Not just product risks, all risks.
- Adoption risk. Are people using it?
- Integration risk. Are upstream and downstream systems holding up?
- Sponsor risk. Is the executive sponsor still in role and engaged?
- Budget risk. Is the budget secure for next year?
Most teams skip risks because they are uncomfortable. That is the wrong instinct. Risks surfaced in QBR are risks that get fixed. Risks surfaced at renewal are risks that lose the deal.
Section 4: Expansion opportunities (15 minutes)
The single most underused section in the standard QBR.
Walk through the whitespace. Other divisions, other use cases, other modules, other geographies. For each opportunity, name the sponsor on the customer side and the next concrete step.
This section is where most expansion revenue gets seeded. If the QBR ends without one named expansion path, the QBR was a status update.
For the planning side that feeds this section, see our account planning process coverage.
Section 5: Roadmap (10 minutes)
Not a feature dump. Three to five items most relevant to this customer's outcomes.
Tie each roadmap item to a specific customer use case. If the customer cannot see how the roadmap improves their outcome, do not show the roadmap item.
End the section with one or two items where the customer can be design partner or beta. This is how you build the next QBR's value story.
Section 6: Executive alignment (10 minutes)
Bring the executives into the conversation. The buyer's executive sponsor and the seller's executive sponsor each get five minutes to speak.
The buyer's executive talks about strategic direction and what the next 12 months look like. The seller's executive reaffirms commitment, named resources, and any escalation paths.
This section is the relationship insurance policy. When something breaks at the operational level, the executive relationship determines whether the issue gets fixed or becomes a churn event.
Section 7: Asks (10 minutes)
End with explicit asks. Both sides.
The seller asks for: introductions to other divisions, reference participation, case study agreement, beta sign up, faster decisions on the expansion path.
The buyer asks for: faster product fixes, additional training, executive escalation, pricing review.
Document both lists. Owner. Due date. This is what gets followed up in the next 30 days.
Who should be in the room
A QBR with the wrong attendees is a meeting nobody benefits from.
From the customer side
- Executive sponsor (VP or C level). Required.
- Operational owner (Director or Manager who runs the day to day). Required.
- One or two power users or program leads. Required.
- Procurement or vendor management. Optional, useful for vendor portfolio QBRs.
From the seller side
- CSM. Required.
- Account executive. Required.
- Executive sponsor (VP+). Required for top 20 accounts.
- Solution architect or technical lead. Optional, brought in for technical sections.
The mistake most teams make is sending too many sellers and too few buyers. Five sellers and two buyers is not a QBR. It is a pitch.
A good ratio is 1 to 1 or 2 to 3 (sellers to buyers). The buyer side should always have at least one executive.
For more on the seller's side of the relationship, see our take on the key account manager role.
Common QBR mistakes
Five mistakes that show up across hundreds of QBRs.
Mistake 1: No executive in the room
The buyer sends the program manager. The seller sends the CSM. The meeting becomes a status review. No expansion gets discussed because nobody in the room can approve expansion.
Fix: make the executive presence a precondition. If the executive cannot attend, reschedule.
Mistake 2: All slides, no conversation
The CSM walks through 40 slides. The buyer nods. Nobody talks.
Fix: cap slides at 15. Drive conversation at each section. The QBR is a meeting, not a webinar.
Mistake 3: Value claims with no data
The deck says "delivered significant value." The buyer's CFO has no idea what that means.
Fix: every value claim has a number, a baseline, and a source. If you cannot quantify it, do not claim it.
Mistake 4: No expansion path
The agenda has no expansion section. Or it has the section but nobody talks through specific opportunities.
Fix: section 4 is mandatory. Walk in with two to three specific expansion paths and the named sponsors for each.
Mistake 5: No follow up
The QBR ends. The action items go into nobody's calendar. The next QBR starts with the same risks unaddressed.
Fix: every action item has an owner and a date. The CSM logs them in the CRM the day of the QBR.
How to operationalize QBRs in Salesforce
A QBR is only as good as the workflow that supports it. Five components in a working operationalization.
Component 1: QBR readiness checklist
Two weeks before the QBR, the CSM completes a readiness checklist:
- Outcomes confirmed with the customer.
- Value calculation reviewed with finance or operations.
- Risks logged in the account plan.
- Expansion paths drafted with named sponsors.
- Executive sponsors confirmed both sides.
The checklist lives on the account record.
Component 2: QBR template tied to account plan
Sections 1 through 7 of the QBR pull directly from the account plan. The QBR is not a separate document. It is a view of the account plan filtered to the QBR audience.
This kills the duplicate work problem. The CSM does not maintain the plan and the QBR deck separately. The plan is the source.
Component 3: Action items as Salesforce tasks
Every QBR action item becomes a Salesforce task assigned to an owner with a due date. The tasks roll up to the account record and the executive dashboard.
Action items that miss their due date show up in the next QBR's risk section.
Component 4: Executive dashboards
The CRO and the head of customer success see a portfolio dashboard:
- QBRs scheduled in the next 30 days.
- QBRs completed in the last 90 days.
- Accounts overdue for QBR.
- Expansion paths surfaced in QBRs by quarter.
That dashboard turns QBRs from a CSM ritual into a portfolio metric.
Component 5: QBR cadence by tier
Strategic accounts: quarterly. Always. Mid market accounts: quarterly or semi annual based on revenue. Long tail: annual or pooled into team office hours.
The cadence has to match the revenue. Forcing a quarterly QBR on a $25K ARR account is a waste of both teams' time. For more on tiering, see our account planning best practices breakdown.
For a deeper walkthrough of how to run customer facing QBRs, see our guide to QBRs for sales.
Related reading
Bring this into Salesforce with CRUSH
QBRs run on account planning data. The outcomes, the value, the risks, the expansion paths, all live in the account plan. The QBR deck is the executive view of that plan.
Prolifiq CRUSH is account planning, relationship mapping, whitespace analysis, and mutual action plans built natively in Salesforce. The QBR sections pull straight from the plan. The action items become Salesforce tasks. The expansion paths become opportunities. Nothing lives in a stale slide deck.
If you want your QBRs to actually drive expansion and retention, see CRUSH.
