A QBR the client can use

Book around a business question

Ask what will change in the client's business before the next review. Hiring, a lease expiry, an application replacement or a new site gives you something concrete to plan around. Invite the person who can decide on that work, and put the question in the invitation. A fictional purpose: "Choose how to support the warehouse opening before staff move in."

Adam Hannemann distinguishes a business conversation from a tactical service recap.^[1] His starting cadence is one review per year for each $1,000–$1,500 of monthly service spend.^[1] Treat that as one planning option. Adjust for your agreement, the client's availability, renewal dates and pace of change; bring a review forward when a real decision cannot wait. The public r/msp discussion includes different approaches to cadence.^[3] Agree the service promise rather than assuming "QBR" obliges every client to an identical quarterly meeting.

Prepare the decisions before the charts

Pull the previous action list first. Ask each owner whether the promised outcome happened, what is blocked and what the client needs to decide. Then collect the service themes and deadlines that change the next plan.

Keep a small evidence pack:

• Prior commitments, with an outcome or blocker beside each.
• Recurring service friction and affected work, checked with the client contact.
• Equipment, licensing or application deadlines with a source and date.
• Standards exceptions that need a decision.
• Roadmap options with dependencies and a cost basis.

Conduit's QBR preparation recipe separates business narrative from detailed operational totals.^[2] Put ticket counts in the supporting material unless they answer the meeting's question. A higher ticket count alone says little about the client's experience. Check whether the client opened more sites, whether the reporting population changed, and whether the same fault kept returning.

Use the same 45-minute agenda

This is the agenda used in the free kit and working sheet:

• 8 minutes: business changes and prior commitments.
• 10 minutes: service friction.
• 20 minutes: roadmap and options.
• 7 minutes: decisions, owners and next steps.

During service friction, ask which interruption affected work and what a satisfactory fix would look like. An urgent failure needs an immediate owner; a routine ticket question can receive a callback without consuming the roadmap discussion. Explain that handoff to the client.

For the roadmap, compare doing the work now, phasing it and deferring it where deferral is feasible. Show dependencies and the consequence of waiting. If discovery is incomplete, ask for a discovery decision rather than making up a price.

Use the final seven minutes to read back the decisions. "Sounds interesting" belongs under interest, not purchase approval. Record approval, deferral, rejection or further discovery, then follow the client's agreed approval route.

Where to keep the follow-through

Use the client record and action queue in your PSA, whether that is Autotask, ConnectWise PSA or HaloPSA. These are examples, not required products. Look for prior review actions, open service commitments and contract dates; verify the fields and permissions in your version. Autotask documents contract balance/expiration and revenue/cost/profitability report groups.^[4] Those reports can supply context, but somebody still needs to check that the population and dates fit this meeting.

Send a short decision note after the review. Put each action into the queue its owner checks. At the next meeting, return to that note and ask whether the completed work achieved the expected result.