← Back to the Agent Playbook
Interactive walkthrough · Play C-05

Watch the Renewal Risk Radar catch churn inside HubSpot

Click through how a custom HubSpot agent reads usage, tickets, champion changes and engagement, scores renewal risk with a plain-language explanation and sends each CSM their at-risk accounts every Monday.

7 steps~3 minutesUse ← → keys

Click the numbered orange boxes in the guide to jump to each part of the screen. Illustrative mockup with fictional data.

How the Renewal Risk Radar play works

Renewal Risk Radar is a custom HubSpot agent that scans upcoming renewals every week, scores churn risk from six signals, explains each score and delivers at-risk accounts with recommended actions to the right CSM.

The problem

Churn signals live in tickets, usage data, email and job changes, and nobody connects them until the renewal conversation. CSM health scores are opinions updated monthly, so accounts marked Green churn with little warning.

How the play runs

  1. Read ticket volume and sentiment, usage trends, champion status, last exec touch, open commitments and billing
  2. Score risk 0 to 100 and explain the score in plain language with evidence
  3. Post at-risk accounts with recommended actions to each CSM in Slack every week
  4. Generate a renewal brief with value delivered, risks and asks
  5. Act through a human playbook defined for each risk tier

What JayOh builds

Risk signals and weights backtested on your churn history, the scheduled custom agent, Slack digests, renewal prep briefs and a tiered CS playbook.

What we measure

  • Gross revenue retention (GRR)
  • Net revenue retention (NRR)
  • High-risk accounts actioned within 7 days
  • Renewal rate by risk tier

Guardrail

Pair the radar with a human playbook for what CSMs do next. The agent finds risk; people save accounts.
HubSpot agentCustom agent + Data Agent
TeamCustomer Success
Timeline2 to 4 week build
RunsWeekly, 120–150 days out

Renewal Risk Radar FAQ

How can HubSpot predict churn risk?

A custom agent can combine usage properties, help desk tickets and sentiment, engagement history, champion job changes and billing data into a weekly risk score for each upcoming renewal.

Why explain the risk score?

A number alone rarely changes what a CSM does. An explanation with evidence, like usage down 41% and the champion gone, tells them exactly what to fix.

Does the agent contact customers?

No. It informs the CSM and leadership. Customer conversations, success plans and renewal terms stay with your team, guided by a playbook for each risk tier.

How far ahead should renewal risk be scanned?

Usually 120 to 150 days before renewal, which leaves enough time to rebuild a relationship or fix a product issue.

Related plays

Want churn risk on your CSMs' radar every Monday?

We backtest the signals on your churn history, build the agent and digests, and run it on your next 120 days of renewals.