Strategic Business Reviews: the QBR, rebuilt on evidence

The quarterly business review most MSPs run is a night of copy-paste: export a ticket count, screenshot a chart, write a summary that says "we had a great quarter" because nobody has time to check. Current builds the review as a magazine instead — a print-quality PDF assembled from the records you already keep, shaped by a short builder that only asks the questions your systems can't answer. Every number on it traces to a live feed, and every risk carries evidence chips a partner could ask about.

You'll find it at Partners → Business Reviews (the page itself is titled Strategic Business Reviews). This article covers how a single review gets built and what lands on its pages. For running the program across a book of partners quarter after quarter — the library, filters, and starting the next one — see "Running your SBR program quarter to quarter."

A finished review reads like a magazine issue, not a slide dump: a cover, an agenda, up to fifteen chapters in a deliberate arc, and any appendix pages you attached. The agenda numbers itself from what's actually present: when a chapter has no data for this partner this period, it drops, and the agenda and page folios renumber as if it were never there.

• ＋Cover — your logo (with your favicon as a small mark beside it), the partner's name, the period, and two or three headline stats. Two, when only two qualify — the cover is never padded to three.
• ＋Agenda — each chapter's title with a one-line promise of what it answers, plus a line for each appendix document you attached.
• ＋The quarter on a page — the hero ticket total, split into the times their people asked for help and the issues your monitoring caught on its own, with an AI-written synthesis and up to four pull stats.
• ＋The value ledger — the quarter's invisible work priced in plain arithmetic: monitoring catches, quarantined phishing, and outage-class saves, converted to hours and money using constants your workspace controls (see below).
• ＋The partnership scorecard — four to six tiles, a satisfaction pull-quote you approved in the wizard, and a "how we work" band in your own words.
• ＋How you compare — service — the partner against anonymous peer medians from your own book, drawn as dot-plots: first response, after-hours share, critical-priority share, positive-survey rate.
• ＋How you compare — fleet & AI — the same treatment for the fleet measures and Copilot adoption.
• ＋Security posture — coverage, detections, and identity hygiene, including the MFA coverage figure you confirmed in the wizard when no feed could read it.
• ＋Fleet health — led by the device-maturity gauge: a 300–850 score, read like a credit score, over a fleet-age histogram whose buckets always sum to the real endpoint count.
• ＋Hardware lifecycle detail — the exact machines behind the fleet numbers, worst first: hostname, model and OS, age, and a warranty or OS state for each, plus the roadmap initiative a device is already attached to. When the fleet is bigger than the page, a note says how many more devices sit past warranty — the list is trimmed, never the type size.
• ＋Backup & continuity — the proof strip: up to six real, dated boot-verification screenshots of recovered systems (with no screenshots it falls back to the verification log — never stock imagery), plus the recovery drill you recorded and cloud seats protected. Screenshots appear on reviews built from August 6, 2026 onward; an older pack picks them up the next time you refresh or rebuild it.
• ＋What we're watching, priced — one to three fully evidenced risks, each with evidence chips and a price column, over the warranty runway for the next eight quarters.
• ＋Where you're exposed — the coverage map: every offering in your catalog for this partner, filled when their agreement lines match it and hollow when they don't, with the in-place and not-covered counts above it, and up to three featured gaps beside it carrying what each one leaves open, how often their own team raised it, and your target price when one is set.
• ＋The road ahead — the roadmap as a quarter-by-quarter timeline: each row under the quarter it's planned for, with its price, status, and a why-line that traces to a record, and one-time and per-year totals summed separately.
• ＋The budget picture — quarters of forward IT spend from your lifecycle feed's budget forecast, split into contracts and subscriptions, roadmap initiatives, and the replacement backlog, with per-quarter totals, an overdue-backlog callout, and a grand total. Appears when a budget forecast exists for the partner.
• ＋The AI opportunity — its own page: a value-per-year lead grounded in the partner's seat count and the plays you chose to put on the table, with the factors printed beside the figures.
• ＋Your team + next steps — the people behind the account and the next review on the calendar. The one chapter that can never drop.
• ＋Appendix — the PDFs you attached in the wizard, printed one page per sheet after the closing chapter.

The ledger chapter turns invisible work into money, and the conversion factors are yours rather than ours. In Settings → Branding, your workspace sets the minutes returned per monitoring catch, per quarantined phishing email, and per outage-class save, plus your published downtime cost per hour. Sensible defaults ship out of the box so a day-one pack works, and every priced line prints its factors — the count, the minutes, the rate — so a customer can redo the arithmetic on a napkin. The ledger prints in your workspace currency.

The downtime line carries one more rule. If you record the customer's own cost of downtime in the wizard, that figure is used and labeled as theirs. If you don't, the pack uses half your published default — and states the halving on the page — rather than valuing their downtime at a number nobody agreed to.

The two comparison pages answer the question every partner asks — "is that normal?" — from your own client book. With five or more similar-sized customers, you get a true peer comparison: dot-plots of the partner against the anonymous cohort median. No peer is ever named, each measure states how many peers reported it, and a measure too few peers have data for stays off the page.

With a smaller book, the pages neither fake a cohort nor silently vanish. They switch to a fallback: the partner against their own last quarter — the same measures, trending — optionally alongside a clearly labeled industry framing written as general context, never dressed up as a measurement from their record. Any external figure these pages cite carries its named source, printed with the number.

Between the priced risks and the road ahead sits a page that reads like a coverage review. It lists every offering in your catalog for this partner, grouped the way you grouped them under Manage offerings, and marks each one filled when their live agreement lines match it or hollow when they don't. Two counts sit above the map: how many are in place and how many are not covered. The marks come from the same nightly match that powers the Whitespace grid, so the page and the grid can never disagree about a partner.

Up to three gaps are featured beside the map, loudest ask first. Each card names what the gap leaves open, in the partner's terms: the AI's own line when the review's analysis raised that offering, otherwise the description you wrote for the offering, and always yours to rewrite in the builder. Under it, when their own people have raised the topic, a line says how many tickets and emails mentioned it in the last 90 days. The count is the whole of it: the messages themselves never print. When you have set a target price for the offering, the card ends with it, per unit, per month, for example "From $6 per seat a month". With no target price the card carries no money at all. The estimate the Whitespace grid shows for a gap is worked out from what your other partners pay and never appears on a partner's page.

Building a review is twelve short steps, grouped the way the printed review reads — set the stage, what we delivered, what we're watching, where we go next, wrap up — with the full step list visible the whole way so you always know where you are. The rule the builder lives by: it never asks you to re-type something a system already knows, and every skip tells you exactly what falls off the page.

1. 1
   1. Data check

   A feed wall shows what's connected for this partner and period — each feed with its live record count or the exact consequence of its absence ("no surveys — the CSAT tile and pull-quote drop"). The only hard stop is a window with zero service-desk tickets; everything else builds from what exists. If backup devices aren't yet mapped to this partner, the backup line says how many, so a thin proof strip is explained before you build.
2. 2
   2. Review window

   Pick the period — quarter, month, annual, or any custom range of 30 days or more — confirm the descriptor line under the partner's name on the cover (leave it blank and the line drops — no placeholder), and set the seat count the pack states its per-seat numbers against.
3. 3
   3. Timeline & facts

   The step that asks for what no feed can read, and every box is optional: pick the quarter's timeline moments from the auto-ranked candidates (the top ones come preselected) or add your own, record the partner's own cost of downtime if you know it, log a recovery drill if you ran one, confirm MFA coverage when no security feed could read it, and put the backup proof strip in the order you want it told. Dates use real date pickers and money uses real money fields — no free-text guessing at formats.
4. 4
   4. Cover numbers

   Choose the cover's stats from the qualified list only — a stat that didn't clear its qualification bar is never offered. The cover carries two or three; it is never padded to three.
5. 5
   5. Customer quotes

   Pick the satisfaction verbatims worth quoting. By default a quote is attributed to the survey, never to a person — naming someone requires you to confirm their consent, quote by quote.
6. 6
   6. Risks & prices

   One to three complete cards — two strong cards beat three padded ones. A complete card has a title, the story in plain words, and at least one evidence chip pointing at a real ticket or asset; an unevidenced risk can't be saved. A price from a real quote wears a QUOTED chip; anything else reads "By quote" or "Included" — the wizard will not print a made-up price. With no risk candidates at all, the chapter drops and the step says so instead of dead-ending you.
7. 7
   7. Coverage gaps

   The Where you're exposed page, on by default whenever this partner has a gap. Switch it off, feature up to three gaps (the loudest asks come pre-selected), leave an offering off the map when it does not apply, and rewrite a card's "what it leaves open" text over the suggested line. The counts, the ask numbers and the target price are read from the record and are not editable here.
8. 8
   8. Roadmap

   Prefilled from your lifecycle plan and banded by quarter. Add your own items, set each row's quarter, price (one-time or per-year), and status, and hide anything that isn't ready — a hidden row stays in the builder but doesn't print. Lifecycle rows can be hidden but never deleted, and any row can carry a short detail line and the devices behind it. The road-ahead page prints whatever ships here.
9. 9
   9. AI plays

   The AI page you put on the table. Check the plays worth proposing to this partner — each shows why you'd raise it and what the partner's page will say — and the page's headline and lead figure follow your selection. With nothing checked, the page drops rather than printing a generic pitch.
10. 10
    10. Decisions & next review

    Record the decisions you're asking the room for — pre-seeded from your roadmap choices, then yours to trim, reorder, or rewrite — and schedule the next review, pre-filled when an upcoming meeting is already on the calendar.
11. 11
    11. Attachments

    Attach the PDFs you already hand out — a project one-pager, a detailed device list — and each prints after the closing page, one sheet per PDF page, with its own line on the agenda. Up to 15 pages per document. Nothing attached means the review ends at the closing page.
12. 12
    12. Preview & save

    A full preview of the real sheets, run through a layout lint — character budgets, the footer reserve, sheet overflow, colliding text, type below the legibility floor. The lint gates the save, so a pack that would print broken never leaves the building.

Print / PDF produces the magazine, and Live mode presents the very same thing: a full-screen deck for the conference-room TV where every chapter in the pack is one slide, drawn from the same numbers the PDF prints — one source of truth, so the deck can never disagree with the document you leave behind. Appendix pages present too, one slide per page, after the team close, exactly where they print. The stage is dark, in your brand colors, and the drop rules hold on screen exactly as they do on paper: a chapter with no data has no slide, and the deck renumbers as if it were never there. Move with the arrow keys or by clicking either side of the screen; a chapter rail along the bottom shows where you are, and clicking any chapter jumps straight to it. Reviews built before the magazine redesign present in the same deck; there is no old format left to fall back to.

A built pack stays click-to-edit sentence by sentence — the figures stay computed from the record and can't be typed over, so the pack can never contradict its own numbers — and because Live reads the same edited pack, a sentence you polish before the meeting shows on stage too.