When a QBR Goes Off the Rails

Byadmin

The Quarterly Business Review is the most overthought deck in SaaS. It takes too long to prepare, its value is hard to quantify, and once the novelty wears off, attendance quietly drops until you’re presenting to a calendar invite and two people who forgot to decline.

The uncomfortable truth is that QBRs don’t work well for most of your book of business. Customers who are growing steadily don’t need them. Customers who are in trouble need more than them. As a touchpoint, the format was designed to be a conversation starter, but somewhere along the way, it became a ritual no one wants to cancel, and no one actually looks forward to.

Here’s how to fix it.

The Biggest Challenges

The customer stops showing up

If attendance is dropping, the most honest diagnosis is this: you are asking for valuable time and delivering a cookie-cutter report. A single hour times a VP’s billing rate is real money. People stop showing up because the math stops making sense.

The problems are usually one of three things. You are targeting the wrong people. You are delivering the wrong content. Or you have considered automating the emailing of the report, which would validate every suspicion your customer already has about its value and turn it into a glorified newsletter nobody reads.

The fix is to work backward from one question: is this interesting enough that someone would actually want to attend? If the answer is no, change the format before you change the deck.

One approach that works: flip the model entirely. Instead of a vendor presenting to a customer, make it a cross-company session where both teams present to each other’s management. The dynamic changes completely. Another option is to abandon the quarterly cadence and replace it with two meaningful KPIs delivered weekly, or a single handwritten email per month. Fewer touchpoints, more signal, more relationship.

They take too long to prepare

QBRs eat CS team time that should be going toward actual customer outcomes. If building the deck requires manual data collection every quarter, that is a process problem dressed up as a content problem.

The rule is simple: if you cannot auto-generate the baseline deck with the right company name, attendees, and metrics, you are not ready to run QBRs at scale. Automation should handle 90% deck, so your team can spend time on the parts that actually require human judgment.

What belongs in the deck, and what should be auto-populated:

  • Customer goals and how they measure success. This should be captured at onboarding and pulled automatically. The KPIs should tie to these.
  • Progress on initiatives you own. Metrics, wins, and any active risks or blockers.
  • An honest read on the relationship. How the account team actually thinks things are going, not just the green/yellow/red health score.
  • Roadmap items relevant to this customer.

The rest should be handled in a conversation:

  • Churn risk signals and growth opportunities. Named, not implied.
  • What you need from them
  • Follow-up

How Do You Know If They Are Working?

This one is easy. Look at the follow-ups. The downstream behavior is the only signal that matters.

You will likely leave with a list of follow-ups. How many result in pipeline? How many reduce risk of churn? How many deepen the partnership in a quantifiable way (such as co-marketing, a case study, or similar). If your QBRs are generating follow-ups that lead somewhere, they are working. If they end with “great call, talk next quarter,” they are not.

The QBR is a great tool for the right customer. Do them when they deepen the relationship. For everyone else, find a touchpoint that fits the relationship you actually have, not the one the template assumes.