What problem does it solve?
Customer success teams often see churn signals scattered across product analytics, support tickets, and billing systems, making it hard to spot at-risk accounts before they leave. This Skill consolidates those fragmented signals into one ranked daily at-risk list with a reason and a suggested next step per account.
Core Features & Use Cases
- Multi-source signal scoring: Pulls usage trends from Postgres, support friction from Plain, and payment/renewal state from Stripe, then combines them into a single risk score per account.
- Ranked at-risk list: Posts one daily message to a Slack alert channel with each account's rank, risk level, the specific signals that fired, and a concrete next step.
- Read-only and stateless by design: Runs in a fresh session each day with read-only connectors, recomputing the full list from current data without writing to any system.
- Use Case: A daily cron fires the scan and surfaces that an account's usage dropped 34% in 30 days, has two escalated support threads, and renews in 12 days — flagging it as highest risk so a CSM can start a renewal conversation immediately.
Quick Start
Run the churn-risk scan and post today's ranked at-risk account list to the alert channel.
