Skip to content

Health Monitoring & QBRs

Health monitoring and QBRs is the governed process for turning account signals, customer outcomes, and review cadence into early visibility on churn risk, expansion potential, and post-sale forecast quality.

LLM handoff

Open this process in your own LLM

Use your own ChatGPT, Claude, or Perplexity account to pressure-test this process, understand the operating risks, and map it to your own company.

Uses your own account in each tool. No API call runs from this site.

What this process is

Health monitoring and QBRs is the governed process for turning account signals, customer outcomes, and review cadence into early visibility on churn risk, expansion potential, and post-sale forecast quality.

What usually breaks

Many teams discover account risk too late because health is reviewed episodically, scored inconsistently, or disconnected from the forecast. That creates reactive success management and weak renewal confidence.

Inline Q&A

How it is measured, tracked, and fit

SkillSystem-backed

What is this?

Health monitoring and QBRs is the governed process for turning account signals, customer outcomes, and review cadence into early visibility on churn risk, expansion potential, and post-sale forecast quality.

How is it measured?

Measure it through health-score movement, QBR completion quality, churn-risk detection timing, expansion-readiness signals, and the percentage of accounts reviewed with current evidence.

How is it tracked?

Track it through a recurring review cadence, clear health definitions, risk flags, QBR outputs, and escalation ownership when accounts move from healthy to exposed.

How does it fit into the SkillSystem?

This process anchors the post-sale observability layer in RevenueOps. It links customer evidence to churn prevention, renewal timing, and expansion quality.

Human + AI boundary

AI can assist signal summarization, anomaly detection, and QBR preparation. Humans must own customer judgment, escalation calls, and interpretation of strategic account risk.

Evidence requirements

Evidence should include customer usage or outcome signals, health-score rationale, QBR notes, risk flags, and the actions taken when health deteriorates.

What good looks like

Good looks like live health visibility, consistent QBR cadence, earlier risk detection, and post-sale decisions that improve renewal confidence instead of reacting to last-minute churn.

Linked tasks

Linked KPIs

Linked OKRs

Recommended reading

Use this process in context

This process page is strongest when you read it alongside the commercial guides, diagnostics, and operating hubs that explain why it matters.

Secondary overlays

  • ValueLogs remain the proof layer once tasks are instantiated.
  • AAA remains the maturity overlay for repeatable execution.
  • IRI remains the risk overlay that affects the valuation side of the system.

Next step

✅ Source of Truth
GFE-SkillSystem/specs/processes/PROC-REV-HEALTH-01.json