---
title: "How to build churn-risk & renewals prep with Claude & Rig"
description: "Score renewal risk across product usage, support tickets, CRM and finance, then auto-assemble the renewals or QBR pack so CSMs walk in prepared. A step-by-step guide to building it yourself on your own data with Claude and Rig."
canonical: "https://rig.so/apps/churn-renewals"
format: markdown
---

[All apps](https://rig.so/apps)

Customer SuccessDashboardWorkflow

# Churn-risk & renewals prep

Spot at-risk accounts before the renewal call

Score renewal risk across product usage, support tickets, CRM and finance, then auto-assemble the renewals or QBR pack so CSMs walk in prepared.

Runs on![Zendesk logo](https://img.logo.dev/zendesk.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=44&format=png&retina=true)![Stripe logo](https://img.logo.dev/stripe.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=44&format=png&retina=true)![Salesforce logo](https://img.logo.dev/salesforce.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=44&format=png&retina=true)

[Build this on your data](https://app.rig.so/signup)[Book a demo](https://rig.so/book-demo)

Renewal risk · next 30 days

Acme CorpUsage −42% · 3 tickets92

Globex71

Initech38

QBR pack generated ↗

## The problem

The health score in your CSP only sees a slice of the picture. The real churn signal is spread across product usage, support load, payment history and CRM notes, and CSMs find out an account is at risk far too late.

## Built from Rig's building blocks

Rig is not a fixed template. It is a set of building blocks, and this app is one way to assemble them. Take what you need, then shape the workflow around your own pain.

Sync product usage, Zendesk, Stripe and the CRM

Context layer defines what 'at risk' means for you

A workflow scores every account and assembles the renewal pack

A health dashboard CS can ask questions of in Claude

## How to build it

1. 1
   
   ### Connect the churn signals
   
   Bring product usage, support tickets, billing and CRM into Rig so risk is judged on everything, not just the CSP's score.
2. 2
   
   ### Define your risk model
   
   In the context layer, set the signals that predict churn for your product, declining usage, ticket spikes, failed payments, and weight them your way.
3. 3
   
   ### Score and assemble
   
   A workflow scores every account nightly and auto-builds the renewals or QBR pack, so CSMs open a finished brief instead of a blank doc.
4. 4
   
   ### Make it interactive
   
   Publish a renewal-risk dashboard CSMs can interrogate in Claude. Adjust the signals as you learn what really drives churn, the model is yours.

## The outcome

CSMs see risk weeks earlier and walk into renewals prepared, lifting gross retention instead of firefighting.

[Build your own version](https://app.rig.so/signup)

## More Customer Success apps

[Account health · Globex Inc78HealthUsage+18%Support−2 ticketsSpend+£4kExpansion readyPropose Tier 3DashboardAccount health & expansionOne health score across product, support and financeA live account health view that blends usage, support load and revenue signals to flag churn risk early and surface the accounts ready to expand.![Segment logo](https://img.logo.dev/segment.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=36&format=png&retina=true)![Zendesk logo](https://img.logo.dev/zendesk.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=36&format=png&retina=true)![Stripe logo](https://img.logo.dev/stripe.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=36&format=png&retina=true)How to build](https://rig.so/apps/account-health)

---

- [This page as HTML](https://rig.so/apps/churn-renewals)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)