SaaS Churn Risk Briefing Studio v1.0

Install

Start with the ZIP package, then choose the AI tool workflow that fits your setup.

1. Download saas-churn-risk-briefing-studio.zip (5.8 KB).
2. Open the package and read SKILL.md, plus any included references, templates, or scripts.
3. Use the instructions directly in any AI tool that supports reusable instructions, project knowledge, custom agents, or uploaded reference files.

For Claude Code, unzip into ~/.claude/skills/ so the folder lands at ~/.claude/skills/saas-churn-risk-briefing-studio/, then reload Claude Code. For Claude.ai, upload the same ZIP from Customize → Skills.

Use with other AI tools

This package is not locked to one vendor. If your AI tool does not support Claude-style skills, copy the core instructions from SKILL.md into the tool's custom instructions, project prompt, agent setup, or reusable prompt library.

• Upload or paste any included reference files as project knowledge where your tool supports it.
• Keep the output format from SKILL.md intact so results stay predictable.
• Run a small test with your own data before using the workflow in production.

Compatibility depends on the features your AI tool provides. Treat scripts as optional local helpers unless your environment can run them safely.

Claude installation reference

You’re staring at a dashboard. The account has flat login counts, a few overdue support tickets, and an NPS score that’s been slipping for two months. Something is off, but you can’t point to one thing. By the time the renewal call happens, you’re explaining away trends instead of getting ahead of them.

Quick scan

• Best for: Customer success managers and account leads in B2B SaaS
• Output: A one-page retention brief with risk drivers, evidence, and playbook suggestions
• Inputs: Usage data, support tickets, NPS/CSAT surveys, optional notes from last QBR
• Time saved: 30–60 minutes per at-risk account
• Main caveat: Requires at least basic usage and support data – not a replacement for human judgement on relationship strength

What it does

The SaaS Churn Risk Briefing Studio is a reusable AI workflow skill that audits a single account against a structured set of churn indicators. It doesn’t just flag “high risk.” It builds a narrative brief that names the risk drivers, attaches the specific evidence from your data, and recommends one of several plays your team can execute immediately.

The skill was designed for B2B SaaS environments where accounts have multiple users, tiered plans, and a help desk. It handles both quantitative signals (login frequency, feature adoption, downgrade events) and qualitative inputs (support ticket sentiment, NPS verbatims, account manager notes) and weaves them into a consistent, manager-readable format.

When to use it (and when to skip)

Use it when:

• You’re doing an account health review ahead of a QBR or renewal.
• A key account shows ambiguous signals – usage is fine but support volume is up, or vice versa.
• You want to align internal teams around a unified retention brief.

Skip it when:

• The account is already in active churn (you need a fire drill, not a briefing).
• You have no usage data or support history to feed in – the skill needs signal, not speculation.
• You’re evaluating hundreds of accounts at once (the skill works one account at a time; batch triage would need a different tool).

How to install and use

1. Download the skill ZIP from this page.
2. Place the saas-churn-risk-briefing-studio folder inside your AI workflow skills directory (usually ~/.claude/skills/).
3. Open a Claude Code session and activate with: claude skill run saas-churn-risk-briefing-studio.
4. Follow the interactive prompts: paste or describe the account’s usage summary, import recent support ticket snippets, and share the latest NPS/CSAT verbatim.
5. The skill will walk you through a series of checks, then produce a final retention brief you can copy into your CRM or share with your team.

A concrete example

A mid-market SaaS company had an account with steady daily active users but a sudden drop in key feature adoption and two support tickets mentioning slow response times. The CSM pasted the last 90 days of usage, three support threads, and the most recent NPS comment (“It’s okay, but competitor X feels faster now”).

Skill output (abbreviated):

• Risk Level: Medium-High
• Primary Drivers: 1) Key feature abandonment (Reports module usage dropped 70%). 2) Competitive mention tied to perceived slowness.
• Evidence: [Timeline of Reports usage decline + verbatim NPS quote]
• Recommended Play: “Competitive Defense + Executive Touch” – schedule a CTO call to address performance concerns, share relevant roadmap, and create a 30-day success plan around Reporting workflows.
• Supporting Plays: Offer a dedicated support channel for the next 30 days; propose a feature training session for power users.

The CSM used the brief to prep the account executive and engineering lead before the call. The account renewed three weeks later.

Limitations

• Data quality matters. If your usage data is incomplete or support tickets are poorly categorized, the risk assessment will be less precise. The skill flags where it’s working with limited signal.
• It won’t replace relationship insight. A risk brief can’t capture informal champion sentiment, political dynamics, or a contract renewal that’s already decided. Use the brief as a starting point, not the final word.

Download the skill to stop reading dashboards and start building retention briefs your whole team can act on.

Related skills

• B2B Lead Scorecard Builder – score inbound leads by fit, urgency, and next action.
• Env Doctor – audit environment variables and deployment configs for common missteps.

Related skills

Skills that pair well, or that you'd reach for instead:

Review this skill