A Quarterly Business Review is a scheduled conversation between your customer success team and a customer's executive team to review value delivered.
The QBR is the single largest recurring touchpoint between a vendor and its enterprise customers. Its stated purpose is to review the last quarter's value delivery and align on next quarter's priorities; its real purpose is to keep the buying committee informed enough that renewal is a formality and expansion opportunities surface naturally. Customers agree to QBRs because their executives need visibility into vendors they're paying six or seven figures; they cancel QBRs when the meeting becomes a slide deck the vendor could have emailed. The design goal: every QBR should give the customer something they couldn't get by reading their own dashboard.
From the customer: the economic buyer or their designee, the day-to-day owner (usually a director-level operator), and a senior executive sponsor if the account is strategic (>$250K ARR). From the vendor: the customer success manager (facilitates), an AE (if expansion is on the table), and a senior executive (VP or above; scale down for smaller accounts). Anti-pattern: showing up with 6 people from your side to the customer's 2 — signals over-investment and creates awkward dynamics. Match or under-index headcount.
(1) Value delivered last quarter (10 min) — specific outcomes: hours saved, revenue influenced, incidents avoided, users adopted. Numbers, not adjectives. (2) Adoption and usage patterns (10 min) — what's being used, what isn't, where are the missed opportunities. (3) Customer priorities for next quarter (15 min) — this is the customer talking, not you presenting. Ask what's changing in their business and what they need from you. (4) Roadmap alignment (10 min) — how your near-term roadmap intersects their priorities. Be honest about what's not coming. (5) Escalations and risks (5 min) — anything unresolved that needs executive attention. Total: 45-60 minutes. If you can't cover it in that time, split into two meetings.
Two weeks before: pull adoption data, calculate ROI or value metrics, review support tickets and product feedback, check the health score. Draft the outcomes summary. One week before: send the customer a proposed agenda and outcomes summary — ask them what they'd add, remove, or emphasize. This transforms the meeting from vendor performance to joint conversation. Day of: brief your executive sponsor for 15 minutes on the account, the people in the room, the two things you need them to say, and the one thing not to promise. Prep is 3-5 hours per QBR; done well, that time is repaid in renewal probability.
Not a mascot. The executive sponsor's specific jobs: (1) demonstrate the vendor's investment in the account, (2) unblock roadmap or support issues the customer would normally have to escalate for weeks, (3) build a peer relationship with the customer's executive so future escalations have a warm channel, (4) ask strategic questions the CSM can't credibly ask ('what would make you renew for three years instead of one?'). The exec should speak roughly 15-20% of the meeting — enough to matter, not so much they dominate. Skipping exec involvement for accounts above ~$100K ARR is a common under-investment; adding an exec to every SMB QBR is a common over-investment.
Two failure signals: (1) customer routinely reschedules or sends junior stand-ins — the meeting isn't delivering value they can't get elsewhere. Diagnose: are we bringing real insight, or reciting metrics they can see in-app? (2) attendance grows on the vendor side, shrinks on the customer side — asymmetric investment is a leading indicator of a stalled relationship. Fixes: reduce cadence to bi-annual for accounts where quarterly is too frequent; replace the standing QBR with 'insight sessions' triggered by specific data (usage anomaly, new capability launch); reserve executive attendance for accounts where it's earning its keep.
Investor directory · Fundraising library · Articles A–Z · Company funding database