By Siddharth GangalA useful sales QBR does not spend a quarter’s attention in 90 minutes. It converts evidence from weekly forecast, pipeline, coaching, and operating cadences into a small set of structural decisions. The output is not a deck. It is an approved decision log, action register, and next-quarter operating contract.
Direct answer. Prepare the quarter actuals, a frozen forecast snapshot, pipeline movement, funnel cohorts, capacity and people evidence, prior actions, and explicit decision requests. In the meeting, separate results from forecast, pipeline from forecast, coaching from performance administration, and observations from decisions. End with one owner and date for every action.
HubSpot’s sales QBR guide distinguishes this internal review from a customer success QBR and includes KPIs, reflection, current pipeline, and future planning. This template adds formula definitions, snapshot discipline, a decision log, worked example, and sign-off.
Define the sales QBR as a decision forum
A QBR is for decisions that are too structural for a deal review and too evidence-dependent for an offsite brainstorm. It should answer: What happened? Why? What has changed? What will we stop, start, or resource differently? Who owns the change, by when, and what evidence will show it worked?
Do not use the QBR to clean CRM fields, inspect every deal, read slides, surprise reps with performance concerns, or negotiate metric definitions. Those are prework or recurring management jobs. Use the forecast review meeting for expected-period revenue and the sales pipeline management cadence for deal flow. The quarterly forum decides what those repeated observations require the organization to change.
| Review | Primary question | Typical output |
|---|---|---|
| Forecast review | What will close in the period, and what changed? | Forecast submission, risks, deal actions |
| Pipeline review | Is enough valid demand moving through stages? | Deal priorities, cleanup, creation actions |
| Coaching review | Which observable behavior should improve next? | Practice plan and follow-up evidence |
| Sales QBR | What does the quarter require us to change? | Decisions, investment, owners, next-quarter plan |
Complete the prework before the meeting
Freeze the packet before the meeting. RevOps owns extraction and definitions; finance reconciles recognized or booked results as appropriate; managers validate opportunity state; enablement and people leaders prepare behavior and capacity evidence. Each presenter adds a written conclusion and decision request, not another chart.
- Results: quota, closed won, bookings or revenue basis, new/expansion split, segment, product, region, rep, and prior-quarter comparison.
- Forecast: timestamped submissions by category, adjustments, actual outcome, error, bias, slippage, and material assumption changes.
- Pipeline: opening and closing snapshots, new, won, lost, increased, decreased, moved in/out, overdue, aging, stage cohorts, sources, and coverage.
- People and capacity: headcount, productive capacity, ramp stage, territory or account load, activity-to-outcome conversion, coaching themes, absence, hiring, and systems friction.
- Learning: wins and losses with evidence, competitive patterns, pricing exceptions, product gaps, experiments, and customer or market changes.
- Control: prior decision and action status, unresolved risks, data-quality exceptions, and decision requests with options.
Freeze currency, fiscal period, bookings/revenue rule, opportunity inclusion, cohort dates, stage mapping, source mapping, and timezone. Label late edits. A dashboard that changes during the meeting cannot function as shared evidence. Use the sales team metrics guide to assign owners and keep operational, outcome, and quality measures distinct.
Run this 90-minute sales QBR agenda
| Minutes | Section | Owner | Required output |
|---|---|---|---|
| 0–5 | Purpose, decisions, definition changes | Sales leader | Scope and decision rights confirmed |
| 5–20 | Prior actions and quarter result | RevOps + finance | Accepted actuals and unresolved reconciliation |
| 20–35 | Forecast accuracy and next-quarter view | Managers | Assumptions, gaps, corrective decisions |
| 35–55 | Pipeline creation, movement, conversion | RevOps + marketing/sales | Bottleneck and owner identified |
| 55–70 | People, capacity, enablement, process | Managers + enablement | Support, hiring, coverage, or workflow decision |
| 70–82 | Strategic options and risks | Decision owners | Approve, reject, defer with missing evidence |
| 82–90 | Read-back and sign-off | Facilitator | Decision log, actions, owners, dates accepted |
The facilitator stops status narration and protects decision time. The recorder writes decisions live. A parking lot needs an owner and disposition date; otherwise it is a deletion queue disguised as follow-up.
Review results and forecast with explicit formulas
Show formulas next to values and preserve snapshots. Microsoft’s current forecasting documentation combines pipeline activity, categories, quotas, and hierarchy rollups and frames forecasts as a regularly reviewed planning tool. Salesforce defines a forecast as expected sales from a gross opportunity rollup and documents Pipeline, Best Case, Commit, and Closed categories. Your category names can differ; definitions cannot drift mid-quarter.
- Attainment % = closed won ÷ quota × 100. State bookings or revenue basis and currency.
- Absolute forecast error % = |forecast − actual| ÷ actual × 100. When actual is zero, report currency error rather than divide by zero.
- Forecast bias % = (forecast − actual) ÷ actual × 100. Positive is over-forecast under this convention.
- Win rate = won ÷ (won + lost) × 100. Define the opportunity cohort and exclude still-open deals.
- Average sales cycle = sum(close date − defined start date) ÷ closed deals. Also show median when a few long deals distort the mean.
Do not replace the deal-level artifact with a QBR slide. The sales forecast template provides categories, monthly and quarterly rollups, reconciliation, accuracy, and sign-off. The QBR should inspect recurring bias and decide what changes.
Diagnose pipeline creation and conversion
Pipeline is the stock and movement of open opportunities; forecast is the subset expected to close in a defined period. Keep them separate so weak creation cannot hide behind two large commit deals.
- Pipeline coverage = eligible open pipeline ÷ remaining target. State eligible stages, horizon, segment, and whether amount is unweighted.
- Stage conversion = cohort advancing to next defined stage ÷ cohort entering stage × 100. Do not mix snapshot inventory with a cohort denominator.
- Pipeline creation = accepted new opportunity amount during period. Define accepted, exclude reopenings or transfers, and segment by source.
- Slippage rate = period-start open deals moved beyond period ÷ period-start open deals due in period × 100. Show amount and count.
- Stage aging = snapshot date − most recent valid stage-entry date. Compare with a defined service level, not an invented universal benchmark.
Salesforce’s pipeline guidance says regular reviews should establish accountability, timed actions, and stage exit criteria. The QBR asks whether repeated pipeline failures require changes to targeting, qualification, coverage, marketing, product, enablement, or systems.
Turn people evidence into support decisions
Use people evidence to choose support, not to stage public performance theater. Aggregate team patterns in the QBR; address individual employment matters through the appropriate private process. For each observed gap, separate capacity, skill, process, tool, data, territory, incentive, and management causes.
| Evidence | Possible decision | Proof next quarter |
|---|---|---|
| New cohort below discovery certification | Add calibrated practice and delay independent calls | Rubric pass plus live behavior sample |
| Strong activity, low valid-connect rate in one territory | Audit data, coverage, channel, and time windows | Valid-number and connect cohorts |
| Late-stage losses cluster on security | Move security discovery and evidence earlier | Time-to-security-start and unresolved requirements |
| Managers spend review time correcting CRM state | Fix definitions, write ownership, and workflow controls | Correction minutes and data accuracy |
Use a written sales coaching plan for observable skill work. Do not infer skill from aggregate output alone; inspect call, message, CRM, or deal artifacts under a consistent rubric.
See a worked QBR example
Worked example: a 10-rep team closes $1.84M against a $2.00M quarterly quota. Attainment is $1.84M ÷ $2.00M = 92%. The final submitted forecast was $2.10M, so absolute error is |$2.10M − $1.84M| ÷ $1.84M = 14.1%, and bias is +14.1% under the stated convention.
The closed cohort contains 23 won and 31 lost opportunities. Win rate is 23 ÷ (23 + 31) = 42.6%. The next-quarter target is $2.20M; $0.40M is already closed, leaving $1.80M. Eligible open pipeline is $5.40M, so coverage is $5.40M ÷ $1.80M = 3.0×. This is not automatically healthy: 48% of that amount sits in one segment whose prior-quarter cohort converted at 18%.
The pipeline movement view shows $3.1M created, $1.84M won, $1.7M lost, and $1.2M moved out. Review notes show repeated security stalls in the high-value segment and 14 of 20 affected deals entered formal security review after proposal.
Decisions: require a security discovery question before solution validation; provide an approved security packet at that point; run a two-week workflow pilot with the enterprise pod; keep next-quarter hiring unchanged until creation and stage conversion are observed for four weeks. Actions: RevOps adds the stage evidence field by August 15; security approves the packet by August 18; enablement certifies the pod by August 22; the VP reviews the cohort September 5.
The example does not claim that 3.0× coverage or 42.6% win rate is universally good. It demonstrates how fixed formulas, segmentation, qualitative evidence, and decision rights connect.
Capture decisions and actions
Write the decision before the action.
| ID | Decision | Evidence | Owner | Effective/review date | Reversal trigger |
|---|---|---|---|---|---|
| D-01 | [Approved choice and scope] | [Packet page/query/artifact] | [One accountable owner] | [Dates] | [Observable condition] |
| ID | Action | Supports | Owner | Due | Acceptance evidence | Status |
|---|---|---|---|---|---|---|
| A-01 | [Deliverable, not “follow up”] | D-01 | [One owner] | [Date] | [Artifact or tested outcome] | Open |
Send the read-back within one business day. Owners correct transcription, not renegotiate accepted decisions by silence. Review actions in the normal weekly operating cadence and bring only structural exceptions back to the next QBR.
Print and sign off the sales QBR
SALES QBR: quarter ___ · scope ___ · currency/basis ___ · snapshot ___ · facilitator ___ · recorder ___ · decision rights ___.
RESULT: quota ___ · actual ___ · attainment formula/result ___ · wins/losses ___ · segments explaining variance ___.
FORECAST: submission/date ___ · actual ___ · error ___ · bias ___ · slippage ___ · assumption changes ___.
PIPELINE: remaining target ___ · eligible pipeline ___ · coverage ___ · created ___ · stage conversion ___ · aging/slippage ___ · bottleneck ___.
PEOPLE: capacity ___ · ramp ___ · observed behavior gap ___ · system/process constraint ___ · support decision ___.
DECISIONS: IDs ___ · approved/rejected/deferred ___ · evidence ___ · owners ___ · review/reversal triggers ___.
ACTIONS: IDs ___ · deliverables ___ · one owner each ___ · due dates ___ · acceptance evidence ___.
SIGN-OFF: sales leader/date ___ · RevOps/date ___ · finance/date ___ · affected function/date ___ · unresolved reconciliation ___.
The signed page is the QBR’s canonical output. Archive it with the frozen packet, calculation notes, decision log, and action register. Next quarter begins by reading the prior commitments—not by rebuilding the story from memory.