For customer success

Replace Your QBR With a Bi-Weekly Async Health Update.

The QBR is a 60-minute ceremony that gets cancelled. An async health update is a document your customer reads on their schedule. Anchorify is the format.

Try it free Read the docs

What changes with async health updates

.

Per-visitor analytics

See who opened the update, how long they spent, and how far they scrolled. Know before the renewal conversation whether your champion actually read it.

v

Version history

Every bi-weekly update is snapshotted automatically. Customer contacts can compare this period to last period. Renewals become a review of progress, not a memory test.

@

No calendar coordination

Send the URL. The customer reads it when they have 10 minutes. No 30-minute pre-brief, no exec attendance problem, no rescheduling chain.

#

Stable URL, update in place

One URL per customer, updated bi-weekly. Forwarding it to a new stakeholder always works. No broken links, no PDFs with wrong dates.

Versus Gainsight and friends

Anchorify Gainsight
Customer-facing health doc at a URL ✓ ✗
No-account reading for customers ✓ ✗
Per-visitor open tracking ✓ ✗
Version history per document Unlimited (all plans) ✗
Bi-weekly publish workflow One command No native workflow
Public pricing Free (beta) Requires sales contact
Free tier ✓ ✗
CLI or API publish ✓ ✗
Health score tracking No (bring your own metrics) Yes (core feature)
CRM integration ✗ ✓

FAQ

What goes in the bi-weekly health update?
Five sections cover the essentials: health score (red/yellow/green with one-line rationale), key metrics this period (usage, support tickets open, NPS trend), wins (one to three specific things the customer achieved), open items with owners and due dates, and next steps. The whole document fits in 400 to 600 words. Customers read it in under five minutes.
Can I keep running QBRs and add async updates, or is it one or the other?
Both approaches work. Some CS teams run one formal QBR per year at renewal time and replace the other three quarters with async updates. Others drop QBRs entirely for their SMB segment while keeping them for enterprise. The async update replaces the quarterly ceremony that exists mainly because the team felt obligated to have a meeting.
How do I share the update only with my customer contacts, not the public?
Set the share to members-only visibility from the dashboard. Customer contacts sign in with Google to read it. That is the same friction as Google Docs comments. You can also add a password for accounts where even sign-in is not wanted. See /docs/visibility for the full options.
Does this work for enterprise accounts with multiple stakeholders?
Yes. Publish one URL per account. When a new stakeholder joins, forward the same URL. They can read the current update and scroll through version history to see the account narrative over time. For accounts where different stakeholders should see different content, use separate project URLs per stakeholder group.

Replace the ceremony with something customers actually read.

Free during beta. One command from markdown to customer URL.

Sign in with Google See the docs