Customer success
How to run a QBR your customers value
Who should attend, a five-part QBR agenda, the data to prepare, and how to make every QBR in your team consistent.
To run a QBR (quarterly business review) customers value, make it about their goals, not your product. Agree the attendees and the customer’s objectives in advance, prepare the data before the meeting, and follow one agenda: their goals, what was achieved against them, what got in the way, the plan for next quarter, and actions with owners and dates. Keep it to about an hour, and send the follow-up within a couple of working days. If every customer success manager runs it the same way, the review becomes something customers expect and prepare for, rather than a meeting they try to move.
This guide is for heads of customer success, account management leads and founders who want every key account reviewed properly, not only the ones looked after by the strongest CSM.
Key points
- A QBR is a business conversation about the customer’s results. It is not a product demo or a renewal pitch.
- Get a senior person from the customer in the room, and bring someone of matching seniority from your side.
- Use a five-part agenda, the same for every account, and prepare the data at least a week before.
- Show usage in aggregate where you can. Named individuals’ activity is rarely needed and raises data protection questions.
- Close every QBR with written actions, owners and dates, and open the next one by reviewing them.
What a QBR is for, and what it is not
A QBR gives the customer’s decision-makers a regular, structured view of what they are getting from you, and gives you an early warning when that value is slipping. Done well, it protects renewals and surfaces expansion opportunities as a side effect.
It is not:
- A support catch-up. Open tickets belong in the operational meeting.
- A product roadmap presentation. Mention what is relevant to the customer’s goals, nothing more.
- A sales meeting. If an upsell is right, it will come out of the plan for next quarter. Raise it there, briefly.
Who should attend, on both sides
| Customer side | Your side | Why |
|---|---|---|
| Executive sponsor or budget holder | Head of customer success or account director | Decisions about priorities and renewal sit here |
| Day-to-day owner of your product or service | Customer success manager (runs the meeting) | Knows what happened during the quarter |
| Optional: a team lead from a department you serve | Optional: account executive or |
Adds evidence of value, or scope for the next phase |
If the customer’s senior attendee drops out repeatedly, treat that as a risk signal and raise it with your own leadership. A QBR with only the day-to-day user is a useful meeting, but it is not a business review.
What a QBR should include: a five-part agenda
- Their goals (5 minutes). Restate the two or three business objectives the customer agreed with you, in their words. Ask whether they have changed.
- Results against those goals (15 minutes). What was achieved this quarter, measured the way the customer measures it: time saved, volume handled, revenue influenced, errors reduced.
- What got in the way (10 minutes). Adoption gaps, open issues, changes on their side. Be candid; customers notice when a review only shows good news.
- Plan for next quarter (20 minutes). Two or three agreed priorities, what each side will do, and how success will be measured. This is where expansion comes up, if it fits.
- Actions, owners and dates (10 minutes). Read them back before the meeting ends.
Send the agenda in advance and ask the customer to add one topic of their own. It changes the meeting from a presentation to a discussion.
The data to prepare, and where it comes from
Preparation is where most QBRs fail. A CSM building slides the night before has no time to think about what the numbers mean. Aim to have the data ready at least a week ahead.
A preparation checklist
- The customer’s agreed objectives, from the last QBR or the handover from sales.
- Contract details: start date, renewal date, products and volumes, from the CRM.
- Usage or service data for the quarter, compared with the previous quarter.
- Support history: volume, themes and anything still open.
- Health score or risk notes, if your team keeps them.
- Actions from the last QBR, with their status.
- One or two short examples of value, ideally in the customer’s own words.
A customer success platform can do much of the gathering. HubSpot’s customer success workspace, for example, is available with Service Hub Professional and Enterprise and lets teams set up health scores that grade customers on criteria tailored to the business. Whatever you use, the point is that the data comes from the same places, in the same format, for every account.
Usage data and personal data
Usage reports often list named users. Under UK GDPR’s data minimisation principle, personal data should be adequate, relevant and limited to what is necessary for the purpose. For most QBRs, team or department totals tell the story. Show individual activity only when the customer has asked for it and there is a clear reason.
Making every CSM’s QBR consistent
Consistency is what turns QBRs from a personal skill into a team process. It also makes the reviews comparable, so leadership can see which accounts are at risk across the whole book.
- One template with the five sections, fixed, and room for the account’s own content.
- A schedule in the CRM: which accounts get a QBR, which quarter, and who runs it.
- A preparation deadline, with a short peer or manager review of the deck for the largest accounts.
- A shared definition of the measures, so “adoption” means the same thing on every slide.
- Outcomes recorded in the CRM after each review: objectives, risks, agreed actions and next QBR date.
Templates and schedules only work if the CRM is kept up to date. If it is not, read how to get a sales team to keep the CRM up to date; the same approach works for customer success.
Following up: actions, owners and dates
Send a short written summary within two working days: the objectives as agreed, three to five actions with an owner and a date each, and the date of the next review. Log the same in the CRM. At the start of the next QBR, review those actions first. Customers notice quickly whether a supplier does what it said.
A QBR outline you can copy
| When | Step | Owner |
|---|---|---|
| 4 weeks before | Confirm date and attendees; ask the customer for one agenda topic | CSM |
| 2 weeks before | Pull contract, usage, support and health data into the template | CSM |
| 1 week before | Deck reviewed by manager (key accounts); agenda sent to customer | CSM, CS lead |
| Meeting | Goals, results, blockers, next-quarter plan, actions | CSM leads; executive attends |
| Within 2 working days | Written summary sent; actions and next date logged in the CRM | CSM |
| During the quarter | Actions tracked in regular check-ins | CSM and customer owner |
How often should you run a QBR?
Quarterly suits most key accounts, as the name suggests. Smaller accounts may only need a twice-yearly review, and some teams run a lighter version for them. What matters is that the cadence is agreed by segment and written into the schedule, not decided account by account.
How we can help
Our customer success and QBR work gives your team one QBR format, the data behind it and a schedule every CSM follows. A QBR template and schedule for customer success are part of the CRM, Pipeline and Forecast Set-up package, from £6,500 + VAT over four to six weeks (see pricing). For the CRM side, see CRM and tool enablement. To discuss your accounts, book a 30-minute call.
Sources
All checked on 26 October 2026.
- Use the customer success workspace (HubSpot Knowledge Base): subscriptions required and health scores.
- Principle (c): Data minimisation (Information Commissioner’s Office): adequate, relevant and limited to what is necessary.
Frequently asked questions
What should a QBR include?
The customer’s goals, results against them, what got in the way, a plan for next quarter, and actions with owners and dates. Prepare contract, usage and support data in advance, and keep product updates to what supports the customer’s goals.
How long should a QBR be?
About an hour is enough for most accounts if the data is prepared beforehand. Longer meetings tend to turn into presentations, and senior attendees stop coming.
Who should attend a QBR?
From the customer, the executive sponsor or budget holder and the day-to-day owner. From your side, the CSM who runs it and someone of matching seniority to the customer’s executive.
How do you make QBRs consistent across a customer success team?
Use one fixed template, a schedule in the CRM, a preparation deadline with a manager review for key accounts, shared definitions of the measures, and outcomes recorded in the CRM after every review.
