← All posts · 2026-07-24

How to run an IT QBR clients actually read

A quarterly business review should take you an hour to prepare and leave the client more confident in you than before the meeting. Most QBRs do neither. They take an afternoon to build and the client spends the meeting politely waiting for the slide count to run out.

Lead with the score, not the tickets

Clients do not care how many tickets you closed. They care whether the things they pay you to protect are healthy. Open with a one-page scorecard: five to ten metrics, each with a target, a current value, and a clear hit-or-miss status. Let the whole quarter be legible in ten seconds.

Pick metrics the client can act on

A good QBR metric passes two tests: the client understands it without a glossary, and if it goes red there is an obvious next conversation. Patch compliance, backup success rate, phishing test failure rate, and mean time to resolve all pass. Alert noise counts and internal tooling stats usually fail.

Keep the same format every quarter

The value of a QBR compounds when Q3 looks like Q2. Same metrics, same order, same grading. Trends become visible, and the client learns to read the report instead of relearning it. This is also what makes renewals easy: four consistent scorecards are a track record, not a sales pitch.

End with three recommendations, priced

Close with what you would fix next and roughly what it costs. Red metrics make this section write itself, and it turns the review from a report into a pipeline. If everything is green, say so and recommend nothing. That builds more trust than inventing work.

Spend your hour on the conversation

The prep should be data entry, not design work. If assembling the deck takes longer than the meeting, the tooling is the problem, not the metrics.