Async QBR: how one team went from 87% to 91% renewals
One CS lead on r/CustomerSuccess (username @Late-Development-543) reported that after replacing formal quarterly business reviews with a bi-weekly written health update, their team's renewal rate moved from 87% to 91% over the following year. That is one team's self-reported experience, not a controlled study. Take it as a data point, not a guarantee.
The mechanism is worth examining regardless. QBRs are expensive to schedule and often low in information density. A bi-weekly async update is the opposite: cheap to produce, high in signal frequency, and readable on the client's schedule with no calendar negotiation required. This post covers what the switch looks like in practice, the template that makes it repeatable, and the cases where you should keep the live meeting anyway.
What makes the standard QBR expensive and low-value for most accounts
A quarterly business review consumes three to six person-hours of scheduling, prep, and meeting time to deliver information the client could read in fifteen minutes. That time cost is the first problem. Getting four to six stakeholders aligned across two organizations, on a quarterly cadence, is a logistics project before it is a success conversation.
The second problem is prep asymmetry. The CSM prepares a slide deck, pulls usage data, writes talking points. The client often arrives cold, skims the slides during the meeting, and leaves without retaining the key points. Research from Gainsight's 2026 blog frames the consequence directly: "When a customer skips a QBR, stops responding on Slack, or sends the dreaded 'we're evaluating our options' email, their decision is often already set." By the time the QBR surfaces a problem, the churn clock has usually been running for weeks.
The third problem is timing. Usage data that signals a health risk shows up in dashboards weeks before the quarterly meeting. The quarterly cadence means late intervention.
None of this means QBRs are useless. Strategic accounts, executive sponsor relationships, and major upsell conversations all benefit from live conversation. The mismatch is with the mid-tier book: accounts with stable usage, operational buyers, and renewal decisions that are made on value evidence rather than relationship strength.
What an async bi-weekly health update looks like in practice
A bi-weekly async health update is a short written report, typically 200-400 words, covering four things: a health score line, a usage summary, a health flag if one exists, and one upcoming milestone or ask. The client receives a link, reads it on their own schedule, and replies by email or comment if they have a question. No calendar invite. No slide deck. No agenda.
The cadence is bi-weekly, not monthly. More frequent than a QBR, but far lower burden because there is no meeting attached. The CSM spends fifteen minutes writing the update rather than four hours preparing for a live session. The client spends five to ten minutes reading rather than ninety minutes in a meeting room.
Delivery matters. The update should live at a stable URL the client can bookmark, not buried in a thread or attached as a PDF that gets lost. When the CSM publishes the update at the same link every two weeks, the client builds a habit around checking it. Compared to a shared Google Doc, there is no permission dialog to navigate and no version confusion about which draft is current.
The format that makes this reproducible:
| Section | Content | Word budget |
|---|---|---|
| Health score | Green / Yellow / Red with one-line reason | 10-20 words |
| Usage summary | Key activity metric and change since last update | 50-80 words |
| Health flag | Any risk, blocker, or concern (skip if none) | 0-80 words |
| Next milestone / ask | What is coming and one specific ask of the client | 30-50 words |
A typical update looks like this in practice:
Health: Green. Usage up 14% this cycle; team is on track for the Q3 adoption milestone.
Usage: 47 active users this fortnight (was 41 last cycle). The new reports feature accounts for most of the uptick. Top usage: reporting, API exports, shared links.
No health flags this cycle.
Next milestone: Q3 business review (live, 30 min) scheduled for June 18. Before then, could you confirm the attendee list? I need your VP's email to send the calendar invite.
That is the whole update. 130 words.
The 87% to 91% result: what one team reported and why it matters
One CS lead on r/CustomerSuccess reported that their team's renewal rate moved from 87% to 91% after switching to the bi-weekly async format. That is a self-reported number from one practitioner, not a peer-reviewed study.
The mechanism behind the lift is plausible even without a controlled experiment. Clients who receive a health update every two weeks do not get ambushed at renewal. They have seen their usage data, they have been told about any risks, and they have had an opportunity to flag concerns before the renewal conversation. That reduces the "I didn't realize the value" churn category, which is one of the most common reasons mid-market accounts do not renew.
ChurnZero's health score research identifies engagement health as a core input to renewal likelihood, citing responsiveness and meeting attendance as key signals. An async update cadence both tracks and improves that signal: clients who are reading the updates are engaged by definition, and the CSM gets an early warning if open rates drop.
The math compounds: on a 100-account book at $25,000 ARR each, moving from 87% to 91% retention is the difference between retaining 87 accounts and retaining 91. That is $100,000 more in annual recurring revenue, before expansion. The numbers will differ for every team. The direction of the effect is consistent with what the research on proactive customer success suggests.
How to replace your QBR with an async cadence: the full mechanics
Replacing a QBR with an async cadence requires three operational decisions: what goes in the update, how often you send it, and where it lives.
What goes in the update is the template above. Four sections, 200-400 words, fixed structure every time. The fixed structure matters because it makes the update faster to produce and easier for the client to scan. They know exactly where to look for the health score and where to find the ask.
How often is bi-weekly. Monthly is too infrequent to catch problems early; weekly risks client fatigue. Bi-weekly is the cadence that the r/CustomerSuccess community converged on most often in discussions of async CS, and it aligns naturally with two-week sprint cycles if the product team operates that way.
Where it lives is a stable URL. Write the update as a markdown file, publish it at a consistent address, and send the client that link each cycle. Tools like Gainsight and Vitally (both custom-priced, both enterprise-oriented; Gainsight pricing, Vitally pricing) can provide the health data inputs, but they are not required. The delivery mechanism is independent of the data source.
For teams that want a lightweight publishing step, Anchorify handles this with one command. Write the update as acme-health-update.md, run anchorify acme-health-update.md, and get back the same stable URL each time you update the file. The client bookmarks it once and the link keeps working. No login required on their end, no permission dialog, no version confusion. The getting started guide covers setup in under five minutes.
Sync QBR vs async health update: a direct comparison
| Dimension | Sync QBR (quarterly) | Async health update (bi-weekly) |
|---|---|---|
| CSM time cost | 3-6 hrs per account per quarter | 15 min per account per fortnight |
| Client time cost | 60-90 min meeting | 5-10 min to read |
| Scheduling burden | High (multi-stakeholder calendaring) | None |
| Signal speed | Quarterly (problems surface late) | Bi-weekly (flag issues within 2 weeks) |
| Client engagement | Variable (skipped meetings signal churn risk) | Consistent (async reads on client schedule) |
| Scalability | Low (caps CSM book at roughly 30 accounts) | High (supports 50-80 accounts per CSM) |
The trade-off that is not in the table: live meetings carry relationship signals that a written update cannot. The CS lead who sees a client's body language when discussing a competitor, or hears a tone shift when budget is raised, has information the async report does not surface. For accounts where that relationship signal is material, keep the live meeting.
When to keep the live QBR instead of going async
Async health updates work best for mid-tier accounts where the renewal decision is operational, not political. They are the wrong format for several situations.
Keep live QBRs for strategic or named accounts where the executive relationship is part of the value you provide. Keep them for accounts in active trouble, where the conversation needs to happen in real time. Keep them for major upsell conversations, where the ask is large enough to warrant a live negotiation.
The hybrid model that most experienced CS leaders land on: async bi-weekly health updates for the full book, combined with one live executive business review per year for strategic accounts and one live check-in call per quarter for any account that goes yellow or red in the health score. The async cadence handles the baseline; the live touchpoints are reserved for the moments where live conversation is actually necessary.
For customer success teams managing a large book of accounts, the async-first model is what makes 60-80 account books sustainable per CSM without sacrificing signal quality.
Frequently Asked Questions
The questions below cover the most common sticking points CS teams hit when evaluating whether to replace or supplement their QBR cadence with async health updates.
What is an async QBR?
An async QBR is a written update delivered on a regular cadence that replaces or supplements a live quarterly business review meeting. The CSM writes a short structured report covering usage, health, and next steps, then sends the client a stable link. No meeting required. The client reads on their own schedule and replies if they have questions. The "async" label distinguishes it from the standard synchronous QBR format where both parties must be present at the same time.
Does replacing QBRs with async updates hurt the customer relationship?
For mid-tier accounts with stable usage, the evidence from practitioners suggests it does not. Clients who receive regular async updates report feeling more informed, not less engaged, because they have a consistent signal rather than a quarterly data dump. The risk is with strategic or at-risk accounts where relationship signals are material; those should keep live touchpoints. The async model is not a cost-cutting measure applied uniformly; it is a cadence choice calibrated to the account segment.
How long should a bi-weekly health update be?
Between 200 and 400 words, structured in four sections: health score, usage summary, health flag, and one action item or ask. Long enough to be substantive; short enough that the client reads the whole thing. Anything longer risks the same low-read-rate problem that makes long QBR slide decks ineffective. The fixed structure is what keeps it short: once the template is set, filling it in takes fifteen minutes and the output is consistently scannable.
What tools do you need to run async health updates?
No enterprise CS platform is required. The workflow needs three things: a data source for the health metrics (product analytics, CRM, or a CS tool like Gainsight or Vitally), a writing format (markdown works well), and a stable URL for delivery. Gainsight and Vitally both require custom pricing quotes and are built for larger CS teams. For the delivery step, Anchorify publishes a markdown file at a permanent URL with one command. If the client uses comments, they can reply directly on the update page.
How do I measure whether the switch to async is working?
Track renewal rate quarter-over-quarter, and separately track whether clients are engaging with the updates. If you publish at a URL with visit analytics, use that; otherwise, watch for email replies and comment activity on each update. If clients are engaging with the updates and renewal rate is stable or improving, the format is working. If clients stop opening updates and renewal rate declines, either the content needs adjustment or the account segment is a poor fit for async.
Sources
- Gainsight: "Why Your Customers Are Already Shopping Around" (April 2026): QBR skip as a churn signal
- ChurnZero: "Customer health scores in the age of AI" -- engagement health as a renewal input
- Gainsight pricing page -- enterprise CS platform pricing context
- Vitally pricing page -- mid-market CS platform pricing context
If you want to try the async health update format, the delivery step is the easiest part to get right. Write the update as a markdown file and publish it at a stable URL with one command at anchorify.io. Free during beta. The client gets a clean, bookmarkable link. You get a record of every update you have ever sent without managing a shared folder or fighting Google Docs permissions.
Last updated: 2026-05-24