QBRs Are Necessary. They Are Not Sufficient.

Start with the case in favour, because it's real.

A QBR is where you do the things that need a scheduled, prepared conversation with the right people in the room. Reviewing progress against the outcomes the customer bought your product for. Surfacing roadblocks that individual users would never escalate. Aligning on the year ahead. Getting in front of an executive sponsor who won't take an ad-hoc call. Producing the evidence that supports a renewal or an expansion case.

None of that happens by itself, and none of it is well served by a reactive alert. If you're not running QBRs, start — they're a core part of how proactive customer success can curb churn in the first place.

The failure isn't holding them. It's treating them as the mechanism that catches problems.

Most customer success teams run on playbooks. Playbooks are reasonable — they make the work repeatable and let you support many customers with few people. But at volume, they harden into a calendar, and the calendar quietly becomes the whole strategy.

"Just doing a QBR every quarter isn't that helpful. Or it might be helpful, but isn't necessarily specifically tailored to the needs of that customer or that individual within the customer with their pain points at that point in time."

Read that carefully, because the nuance matters: "it might be helpful, but isn't necessarily specifically tailored." The objection isn't to the review. It's that a conversation scheduled three months in advance can only be tailored to what you knew three months ago.

Stated plainly:

"Mostly we are stuck on quarterly QBRs and an annual renewal and that's the only time we bother speaking to the client. And it should be the other way around."

Four scheduled conversations a year, one of which is about money — and eleven weeks of silence between each of them. That silence is where churn is decided, and it's the gap that most broad SaaS churn rate solutions skip past in favour of general tactics.

The way I think about the difference:

"That to me is like dropping off the goods at the end of the driveway and leaving the client to go out there and drag them all the way back into their home — as opposed to delivering them, unpacking them, getting rid of all the garbage, and setting it all up so it's perfect."

Both are technically delivery. Only one is service.

A drip sequence satisfies the obligation to stay in contact without necessarily helping anyone. A QBR does something more substantial — but only on the day it happens. White-glove service means knowing what this customer has been doing continuously, and turning up when that knowledge is useful. Sometimes that's the QBR. Often it's a Tuesday in week six.

And it cuts both ways. If everything's fine, the right move is to leave them alone:

"I'm not doing a QBR when you don't need one. I'm only interacting with you when you truly want some help and I'm truly adding value."

There's a credibility cost to the alternative that people underestimate:

"I'm not doing a QBR just so I can upsell you. You're not showing up at a QBR thinking they don't really care about me. They just want my money."

If every scheduled conversation carries a commercial agenda, customers learn what the meeting is for. They stop preparing, send someone junior, and eventually stop attending — and you've lost the QBR as a useful instrument precisely when you needed it.

That's worth dwelling on, because it's how QBRs get devalued. The meeting itself is fine. Loading it with work it can't do — being the only time you ever look at the account, and the moment you raise every commercial ask — is what turns it into a ritual both sides endure.

Here's the part that should worry anyone running renewals, and it's arithmetic rather than opinion.

A customer disengages in month three. Their usage declines through months four, five and six. The QBR in month six is a perfectly good meeting — but the customer's own team may not yet know they're in trouble, so they say things are fine. The next real signal is the renewal in month eleven — exactly the failure mode I've written about in The Renewal Engine: treating the renewal date, not the relationship, as the trigger for action.

"If you wait till a month before the renewal and they've been upset and not using the product for 6 months, this is a big problem."

By that point you're not doing customer success. You're doing damage limitation on an outcome that was decided months earlier — negotiating with someone who has already mentally left, and probably already looked at alternatives.

Almost every fixable churn cause has a window. Budget pressure can be met with a smaller plan. A departed champion can be replaced with a new one you train. Unrealised value can be addressed with targeted enablement. All of those work in month four. None of them work in month eleven.

This is the precise claim: the QBR isn't wrong, it's late. A quarterly rhythm means the average problem waits up to six weeks for a scheduled conversation, and a problem the customer hasn't yet recognised waits until it's visible enough to raise — by which point the window is usually closed.

So keep the QBR and add the thing it structurally cannot provide: continuous visibility into the same usage signals that power usage-based billing — the trigger for an unscheduled conversation is a usage trend.

"If I'm doing a renewal, sometime before that renewal, I would look at the current trend."

What you measure depends on the product — active users, depth of engagement, feature consumption — the kind of usage data I've covered in Beyond Checking In and in the power of SaaS product analytics for boosting retention. What matters is comparing it to history. How does this quarter compare to last quarter, or this year to last year?

Then the discipline of not over-reacting. A falling trend is a prompt to investigate, not a conclusion:

"Just because the trend is down doesn't necessarily mean that there is a problem, right? Could be — well, hang on, let's go back and look at last quarter, last year. Oh yeah, same thing. Maybe it's seasonal."

Some businesses are quiet in August. Some slow down at year end. Knowing your customer's rhythm is the difference between a useful intervention and an anxious phone call about nothing.

But some causes are specific and urgent:

"Did a key contact leave and that key contact was the one that was constantly using the product day in day out? Right? Well, this could be a challenge for us... We need to get someone back in here using our product and seeing value in it."

A departed champion is one of the most reliable churn predictors there is, and it's invisible in aggregate account metrics. It shows up as a modest dip in overall usage — while your entire internal advocacy has quietly disappeared.

The practical shift is from reviewing data on a schedule to being alerted by it when something changes. This is where tooling matters, and it's why we built Zengain's Retain module around a traffic-light system — a red flag when a downward trend appears, early enough to act on.

"Retain will send you an alert when a downward trend is happening right, and at that point you can jump in."

The difference is who initiates. A dashboard requires someone to remember to look, which at fifty accounts per CSM means nobody looks until something forces them to — usually the QBR or the renewal. An alert arrives whether or not anyone remembered, and it arrives in week six rather than month eleven.

Note what this does for the QBR rather than instead of it. Walking into a review already knowing that usage dipped in week six, that you addressed it, and that engagement recovered is a completely different conversation from walking in and asking how things are going. The signals make the scheduled meeting better, not redundant.

The same logic applies to the upside, which teams forget:

"Why wait a whole year to the renewal to try and upsell a client? … Your CFO wants that cash right now. Your commission is paid right now. It's not paid in a year."

If an account's usage is climbing in month four, that's the moment to expand it — the same early-expansion argument I make in upsell and cross-sell techniques, and the reason usage trends connect directly to net revenue retention. Waiting until the next QBR to have a conversation the data already justified is a strange way to run a business — and it's the same structural problem as the churn case, just with the sign reversed.

One more pattern, because it's common right now and almost entirely preventable.

Budgets are under pressure. Customers are reviewing every line item. Some of them will cancel not because your product failed, but because the price stopped fitting.

"Do we just ignore them till renewal and they're like, 'Yeah, I couldn't afford it, so I just cancel'? Or do we say, 'Hey, you know, we've got a model here. We could get you into a little less expensive, a few less seats. How would that work out for you?'"

A smaller contract is better than no contract, and considerably better than a competitive displacement — which is exactly why it's worth having flexible pricing options ready before the conversation happens, not during it. But that conversation only happens if you know the pressure exists before the customer resolves it by leaving. If the next scheduled touchpoint is ten weeks away, you usually find out afterwards.

Keep the QBR, and protect what it's for. Strategic alignment, executive access, evidence for renewal and expansion. Don't load it with every commercial ask, or it becomes a meeting people avoid.

Add signal-triggered conversations between reviews. Trend changes, feature abandonment, champion departure, approaching limits. Those are the moments something is genuinely at stake, and they don't wait for your calendar.

Be willing not to contact people. If an account is healthy, leave it alone. Scarce attention should go where it changes an outcome — and customers notice when you only appear with something worth saying.

Use the signals to improve the QBR. Arriving with a specific account narrative — what changed, what you did, what it produced — is what makes the meeting worth the customer's time.

Check whether you can see any of this. Most teams can't. That's an instrumentation problem, and no amount of CS process compensates for not knowing what your customers are doing between reviews.

Churn is rarely a surprise. It's usually a trend nobody was watching, discovered during a conversation scheduled for other reasons, at a point where the only remaining option is a discount.

So run your QBRs. They do work that nothing else does. Just don't ask them to be your early warning system, because a meeting scheduled in advance cannot tell you what changed last week.

Necessary, and not sufficient. Both halves of that matter.