Running QBRs. Proving value to your largest accounts.

Who got one — and why they work

The honest baseline: we ran customer QBRs for the salmon, the tuna, and the whales — the same meaningful-ARR slice of the book that had a renewal motion — and not necessarily aligned to a renewal date. The cadence aspiration was quarterly; more often than not, reality was twice a year. That's fine. The value of the meeting doesn't come from hitting the calendar exactly — it comes from the meeting existing at all.

Why are QBRs such an effective retention tool? Because they foster stronger customer relationships, and they give you a dedicated forum to talk with a larger account about their frustrations, their pain points, the features they like, and the new features coming soon. Most important of all, they give you the opportunity to demonstrate the value of your product — on your initiative, with evidence, instead of hoping the customer notices it on their own.

What you walk in with

Our prep kit was everything you'd expect, and the customer cared about most of it: their usage data, seats and adoption, their support history, the ROI framing, our roadmap, and updates on any of their high-priority support tickets. Walking in with their own data is the difference between a business review and a sales call — you're showing them their reality, not your pitch.

And there was one item customers always wanted that vendors consistently under-prepare: the features they weren't using but should be. Every account, every time. It's the most natural agenda item in the meeting — it's free value for them, it deepens adoption for you, and it sets up the expansion conversations this meeting exists to surface.

The ROI slide — an honest accounting

Proving value to an SMB owner was a genuine challenge, and I'll say what most QBR content won't. What worked for us: showing pipeline growth, and deals won using the tool — the places where the product's fingerprints were on their revenue. But the truth is that most tools are loosely connected to ROI, and a CRM is more loosely connected than most. A real part of a CRM's value is simply having a central, organized database of all your deals and contacts — and showing that on an ROI slide is hard.

That's the rule I'd hand any CSM building a QBR deck: lead with the value you can evidence — pipeline, wins, adoption — and present the structural value honestly rather than torturing it into a manufactured number. Customers can smell a fake ROI calculation, and it costs you credibility on the slides that are real.

The room: who runs it, who shows up

On our side, the CSM who owned the account ran the review — consistent with the no-handoff ownership that ran our whole post-sale motion — and for the whales, a co-founder would sometimes join. On the customer's side, the people you need are the champion and the admin, who at SMB scale were often the same person. That's who can act on what the meeting surfaces.

And the known failure mode: sometimes the customer's sales team showed up, and the meeting would promptly turn into a feature-request avalanche. Not ideal — we made the best of it. Capture the requests, route them honestly, and steer the agenda back. It's a manageable cost, and an occasional reminder that a roomful of salespeople will always tell you what to build next.

The strategic payoff: conversations that happen nowhere else

Here's what separates the QBR from every other customer touchpoint. I can recall several QBRs where expansion opportunities surfaced right there in the conversation — "oh, I didn't know you guys did this; maybe our other team can use the tool?" Or: "I need to intro you to our team in Canada, because they could really use this."

Support tickets are operational. Email is transactional. The QBR is the one recurring forum where both sides are looking at the relationship from above — and when the customer joins you at that altitude, they start seeing places your product fits that you couldn't have seen from outside their org chart. That's retention and expansion coming out of the same ninety minutes.

The playbook for $1–10M ARR

Who earns one: any meaningful-ARR account, and any annual or multi-year contract. Run them on a regular cadence with your mid-sized and larger accounts, to the extent your CSM resources can support the strategy — an aspiration of quarterly that lands at twice a year is a working system, not a failure.

Two things have changed the math recently. First, the labor-intensiveness of QBR prep has dropped substantially with AI tools like Claude and ChatGPT — assembling the usage story, the adoption summary, and the deck no longer eats the hours it used to, which moves the break-even account size down. Second, that same leverage means even your lower-value accounts deserve some form of QBR — an automated one, perhaps a short Loom video walking through their usage, new features, and what they should adopt next. The basic QBR playbook — engaging customers by educating them on adoption, teaching new features, and articulating the value of the product — is an effective way to accomplish all of those things at once. The only real mistake is reserving it for nobody.