A Series B CRO sent me a deck last quarter with the subject line "QBR." It was 84 slides. Pipeline by region. Pipeline by segment. Pipeline by rep. Pipeline by month. Pipeline by source. Win rate trend. Activity counts. A slide titled "Key Takeaways" with five bullets that said things like "continue to drive top of funnel" and "focus on conversion." Then a wrap-up slide with the words "Q4 outlook: cautiously optimistic."
I asked him one question. After the QBR ended, what did any rep do differently on Monday morning?
He went quiet. Then he said: "Honestly, probably nothing."
That is the QBR problem. Most quarterly business reviews are theater. They produce decks, fill calendars, and burn 40 hours of senior time per quarter. They do not change behavior. They do not move the next quarter's number. They are a performance of accountability, not the thing itself.
I have sat through more than 200 QBRs across B2B companies between $5M and $200M in ARR. The good ones look almost nothing like the bad ones. This is the operating model I run when a Series A or B team asks me to fix theirs.
Share of Series A and B sales QBRs in our 2026 sample where no rep changed a single account activity in the four weeks after the meeting. The QBR happened. Nothing happened next.
Why most QBRs do not change anything
The dominant QBR pattern looks like this. RevOps spends a week pulling data. The CRO spends two days building slides. Reps spend half a day each on their territory updates. Everyone gets on a Zoom for four hours. People take turns presenting their numbers. The CRO asks soft questions. The meeting ends. A recording goes in a folder nobody opens. Two weeks later the forecast looks identical.
The reason this fails is not effort. It is design. Most QBRs are built around reporting the past instead of changing the future. They answer "what happened" instead of "what do we do now." Reporting is necessary but it is the input to the meeting, not the meeting itself.
The other failure mode is the wrong audience. A 12-person all-hands QBR turns into a public performance review. Reps defend their numbers instead of asking for help. Honest conversations about a stuck $400K deal do not happen in front of peers. The meeting structure makes the truth socially expensive.
A working QBR has three properties. It is small enough that people can be honest. It is structured around decisions, not reports. And it produces a written list of commitments that anyone can hold the team accountable to next quarter.
The four QBRs you actually need
There is no single QBR. There are four different conversations that most teams cram into one four-hour meeting and do badly. Split them.
If you only run one of these, run the deal review. It is the highest impact hour you will spend all quarter. The all-hands theatrical version of the QBR can die and nobody will miss it.
Meeting 1: the number review
This is the meeting that should not be a meeting. It is a pre-read. RevOps writes a four-page document a week before the meeting. The first page is one chart and three sentences: what we forecast, what we closed, what the variance was driven by. The next three pages are the same breakdown by segment, by source, and by stage. There is no slide. There is no presentation. People read it before they walk in.
The actual meeting is 60 minutes of questions. The CRO, the CFO or finance lead, and RevOps. That is it. The agenda has three questions written at the top.
What did we get wrong about last quarter's forecast and why? What is the single biggest assumption baked into next quarter's number that could be wrong? What change to the model do we need to make based on what we just learned?
The output is one page. Not a deck. A page. It goes to the board, the leadership team, and the head of every other function. If you cannot write the story of last quarter on one page, you do not understand what happened.
I have watched companies cut their forecast variance from 22% to 8% over three quarters by running this exact format. The reason is that the meeting forces people to commit to a written explanation, which forces honesty. A slide deck lets you hide behind "macro headwinds." A one-pager makes you say "we missed because three deals slipped from segment X and we did not see the slippage coming because our stage 3 to stage 4 conversion data was stale by 11 days."
If the QBR cannot be summarized on one page, the meeting was a performance, not a working session.
The one-page output is the forcing function. It is what separates a QBR that changes behavior from a QBR that fills time.
Meeting 2: the deal review
This is the meeting that actually moves money. It is also the meeting that almost no team runs well.
The format. The CRO, the sales managers, and the AE who owns each of the top 10 open deals next quarter. Not the top 50. Ten. The top 10 by weighted pipeline value. Each deal gets seven minutes. That is 70 minutes plus a 20-minute wrap. You can do it in 90.
The seven minutes per deal is structured. Two minutes for the AE to state the deal in MEDDIC or MEDDPICC terms. Three minutes for the room to ask one question each, with rotation enforced. Two minutes for the AE to commit to two specific next steps with dates.
The killer is the questions. They are not "how is it going." They are specific. Who is the economic buyer and have you met them in person or on video. What is the buyer's compelling event and how do you know it is real. Who is championing this deal internally and what would happen to their career if it does not close. What is the single most likely reason this deal slips. What is the dollar value of doing nothing for the buyer.
If the AE cannot answer any of those questions in a sentence, the deal is not where the forecast says it is. Demote it. Adjust the number. Move on.
I have run this exact format with 11 different sales teams in the last two years. In every single one, between 30% and 50% of the top 10 deals got moved out of the quarter after the deal review. Forecast accuracy improved by 9 to 18 points the next quarter. The reps were not lying. They were optimistic. The deal review surfaces the gap between optimism and reality.
For a Series A team that runs this for the first time, it is brutal. Reps feel exposed. The fix is to make it clear that the goal of the meeting is to help the deal close, not to grade the rep. The first time I run this, I make a rule: the CRO is not allowed to make a statement, only ask questions, for the first three reps. It changes the social dynamic immediately.
If you want a deeper read on how we structure pipeline and forecast hygiene, the pipeline coverage ratio guide and our sales forecasting work both cover the data side of this in more detail.
Meeting 3: the rep 1:1 QBR
This is the meeting that managers skip first when they are busy and it is the meeting they should skip last. The rep 1:1 QBR is where you find out who is going to leave in the next 90 days, who is about to underperform for a reason nobody saw, and who is ready for more responsibility.
The format. The direct manager and the rep. 45 minutes. Quarterly. Not the weekly 1:1. A different meeting with a different agenda.
The agenda has five sections.
First, the rep's own self-assessment of the quarter. What worked, what did not, what they would do differently. The manager listens and writes it down.
Second, the manager's assessment. Specific, with examples. Two strengths the rep should keep doing. One gap the rep needs to close. No more than one. People can only work on one thing at a time.
Third, the career conversation. Where does the rep want to be in 18 months. What skills do they need to get there. What is the single thing the company can do to help. This is the question that surfaces flight risk three months before it becomes a resignation letter.
Fourth, the commitments. The rep commits to one thing they will change next quarter. The manager commits to one thing they will do to support the rep. Both go in writing.
Fifth, the rep gets to ask anything. About the company, the leadership, the comp plan, the territory. Hard questions. The manager has to answer honestly or say "I do not know but I will find out by Friday." Trust gets built in this five minutes.
The reason this matters. AE attrition costs a Series A or B company between $250K and $400K per departure in lost productivity, ramp time on the replacement, and pipeline that does not get worked. A single 45-minute conversation that surfaces flight risk early pays for itself many times over.
Meeting 4: the go-forward plan
This is the meeting nobody runs and it is the reason most QBRs change nothing. After the number review, the deal review, and the rep 1:1s, the leadership team sits down and answers one question. What three to five things will we actually do differently next quarter?
Not "drive more pipeline." Not "improve conversion." Specific operational changes. Examples from real plans I have built with clients:
We will move SDR meeting credit from "meeting booked" to "meeting held with stage 2 advance" because the data shows 41% of booked meetings never advance.
We will require every deal over $50K to have a documented champion meeting recorded in Gong before it can move to stage 3.
We will retire the bottom two outbound sequences and put all SDRs on the one that has a 4.2x higher reply rate.
We will move the territory boundary in the West region because one AE has 38% of the named accounts and the territory is unworkable.
We will hire one sales engineer because the demo-to-trial conversion is 22% lower without one and the pipeline math says the SE pays back in 11 weeks.
Five changes. Each one assigned to one owner with a date. Each one with a leading indicator that can be measured weekly. RevOps writes it up, leadership signs off, and it gets reviewed in the weekly forecast meeting for the entire next quarter.
If you do not produce this list, the QBR did not happen. You ran a status meeting and called it a QBR.
The data you actually need for a QBR
Most QBR data prep is wasted. Teams pull 30 reports and use four. Here is the minimum data set you actually need.
If your data is wrong, the QBR is worse than useless because you will make decisions based on bad signal. The number one reason QBR data is wrong is that reps do not update the CRM. The fix is not a stricter rule. The fix is to make the CRM update the easiest thing the rep does that week, with tight workflow design and automation that pulls activity from Gong, calendar, and email automatically.
We have done this for Series A and B teams using HubSpot, Salesforce, and Attio. The pattern is the same. Auto-log activity from connected systems. Use a single deal scorecard field the rep updates in 90 seconds. Run a Friday data hygiene check that flags deals with stale fields. After 30 days, CRM data is good enough to run a real QBR.
The QBR cadence I actually recommend
Once a quarter is wrong. The cadence that works is layered.
Weekly: forecast call. 30 minutes. Top 10 deals only. What moved.
Monthly: pipeline review. 60 minutes. Where is next quarter coming from. What is the gap to plan.
Quarterly: the four meetings above. Spread over two weeks. Do not cram them into one day.
Annually: strategy off-site. Two days. Different format, different output. Not a QBR.
The mistake is doing the quarterly review only at the quarter close. By then the data is locked in and you cannot change anything. Run the deal review and the rep 1:1s in the last month of the quarter, not the first month of the next quarter. You can still influence the close.
What changes when you run this
I have rebuilt the QBR process for nine companies in the last two years. Series A through Series C. The pattern of results is consistent enough that I can predict it.
Forecast accuracy improves by 8 to 15 points within two quarters. The reason is that the deal review surfaces optimistic forecasts before they hit the board.
Rep attrition drops by 25 to 40%. The reason is that the rep 1:1 QBR catches flight risk early enough to address it.
The number of operational changes the team actually executes per quarter goes from zero or one to four or five. The reason is that the go-forward plan creates a written list that gets reviewed weekly.
Senior time spent on QBR prep drops by 40%. The reason is that you replace the 84-slide deck with one-page documents and you stop trying to use a single meeting to do four different jobs.
None of this is exotic. It is just discipline. Pick a format. Use it every quarter. Write things down. Review the commitments. Most teams do not do any of this because nobody told them what good looked like and the template they copied from a sales blog in 2019 is the version with the 84-slide deck.
Want help redesigning your QBR?
We run a 30-minute QBR teardown for Series A and B revenue teams. You send the last deck, we tell you the three changes that would have the biggest impact on next quarter.
Book a QBR teardown →FAQ
How long should a sales QBR actually be?
The full set of four meetings totals about six hours of senior leadership time, spread over two weeks. The all-hands version most teams run is four hours in one day. Same total time. Very different output. The split version produces a written go-forward plan. The single-meeting version produces a deck.
Who should attend a sales QBR?
It depends on which of the four meetings. The number review is the CRO, finance, and RevOps. The deal review is the CRO, managers, and the AEs who own the top 10 deals only. The rep 1:1 QBR is the direct manager and the rep. The go-forward plan is the CRO, managers, and RevOps. There is no meeting that needs the entire revenue org in the room.
How do you run a QBR for an early-stage team with no CRO?
Same structure, smaller meetings. The founder or head of sales runs the number review with the finance lead. The deal review covers the top 5 deals instead of 10. The rep 1:1s still happen because they are the highest impact hour. The go-forward plan is three changes instead of five. You can run the entire thing in four hours total at a 10-person team.
What is the difference between a QBR and a sales kickoff?
A QBR looks backward at one quarter and decides what to change. It is operational. A sales kickoff (SKO) launches a new fiscal year or major plan change. It is motivational and educational. SKOs cover product training, comp plan rollout, and strategy alignment. They are typically two days, off-site, with the whole team. QBRs are working sessions. SKOs are events.
What software do you actually need to run a good QBR?
Less than you think. Your CRM (HubSpot, Salesforce, or Attio) for pipeline and deal data. A conversation intelligence tool (Gong, Chorus, or similar) for activity and call evidence. A shared doc tool (Notion, Google Docs, or Coda) for the one-page outputs and the commitment list. That is it. You do not need a dedicated QBR platform. The discipline is the system, not the software.
If your QBR has turned into theater and you want to redesign it so it actually moves next quarter's number, book a call and we will walk through what is broken and what to change first.