Why QBRs Are a Lagging Indicator of Churn (And What to Track Between Them in HubSpot)

Quarterly business reviews are still treated as the primary moment to assess account health. By the time a QBR happens, the renewal decision has often already shifted. This article explains why the QBR is structurally a lagging indicator, and which HubSpot signals to monitor in the 90 days between QBRs to catch renewal risk while it can still be reversed.

Quick answers

Why is a QBR a lagging indicator of churn?: A QBR reports on a quarter that has already happened. By the time the meeting is scheduled, the engagement decline that predicts churn has already occurred for 60 to 90 days. The QBR confirms the risk, it does not detect it early.
What should you track between QBRs in HubSpot?: Between QBRs, track four fields per account in HubSpot: last inbound reply date, count of upcoming meetings, count of completed meetings in the last 30 days, and contract end date. The combination of these four reveals renewal risk weeks before the next QBR.
How often should account health be evaluated in HubSpot?: Account health should be evaluated on a continuous schedule, not on a quarterly cadence. A 60 minute scan cycle on the four core engagement fields catches risk the day it appears, not the quarter after.
Can a QBR be replaced by automated signals?: A QBR cannot be replaced by automation, but its purpose changes. With continuous signal detection, the QBR becomes a strategic conversation about value delivered, not a reactive review of declining engagement. The risk surfacing happens in HubSpot tasks between meetings.
What is the cost of relying only on QBRs?: Relying only on QBRs means churn risk is detected on average 60 to 90 days late. For a B2B SaaS account with a 12 month contract, that is 25 percent of the lifecycle spent in undetected risk. Most renewal losses trace back to engagement decline that started in this window.

The structural problem with QBRs

A QBR is a review, not a detection mechanism. It summarizes a quarter that has already closed. By the time a customer success manager prepares the deck, three months of engagement data already exist, and any decline inside that window is now historical.

For a typical 12 month B2B SaaS contract, the gap between QBRs covers 25 percent of the customer lifecycle. If a renewal decision shifts in week 4 of a quarter, the QBR will surface it in week 13 at the earliest. Nine weeks of recovery time are lost.

What actually changes between QBRs

Renewal risk is not built in the QBR. It is built in the silent weeks in between, where four specific signals shift one by one.

Inbound reply cadence: the customer stops responding within their normal window.
Meeting pipeline: the next meeting is no longer scheduled, or gets rescheduled twice.
Stakeholder breadth: only one contact remains active, the original champion has gone quiet.
Contract proximity: the renewal date enters the 90 day window without a renewal motion in the deal pipeline.

All four are already in HubSpot. None of them are surfaced by the standard company view.

The detection rule that runs between QBRs

If contract end date is within 90 days, AND there is no upcoming meeting, AND no inbound reply in the last 30 days, AND the active contact count has dropped below 2 → flag the account as at risk and create a HubSpot task for the owner.

This rule runs every 60 minutes against every company record in the portal. It does not wait for the next QBR slot on the calendar. The output is a task on the owner's HubSpot queue, not a slide in a deck.

Example: an account that looks healthy at QBR Q2 and churns in Q3

QBR Q2 (week 13): green status, contract renews in 6 months, all metrics on track.
Week 16: primary champion leaves the customer company, no replacement looped in.
Week 19: last inbound reply, then silence.
Week 22: scheduled call gets rescheduled twice, then dropped.
QBR Q3 (week 26): meeting cancelled, account flagged red, renewal already lost internally.

Between week 16 and week 26, the rule above would have triggered on three separate days. Each trigger creates a task. None of them required waiting for the next QBR.

Where the QBR still matters

Continuous detection does not remove the QBR. It removes the diagnostic burden from it. With renewal risk surfaced through HubSpot tasks during the quarter, the QBR is no longer the place to discover problems. It becomes the place to confirm value delivered, align on the next quarter, and reinforce the relationship at the executive level.

From quarterly review to continuous detection

The shift is from sampling account health four times a year to evaluating it every hour. The data already exists in HubSpot. The only thing missing is the rule that runs against it on a schedule.

Sighub applies this rule to every account in your HubSpot portal on a 60 minute schedule and creates a HubSpot task for the company owner the moment risk is detected. Read next: HubSpot Engagement Gaps or Why HubSpot Tasks Are the Missing Layer.