Churn-risk alert
Weekday mornings, paying accounts that look at risk (failed payments, usage drops, cancel at period end) with the score's reasons. Read-only; never touches billing.
- Installs
- 0
- Runs (30d)
- 0
- Active builders
- 0
- Trend
- —
Uses
Tools: mcp:stripe, mcp:posthog, skill:founder-metrics, skill:founder-mrr-churn
Triggers: Weekdays at 9:00 AM
Definition (YAML)
id: founder-churn-risk
name: Churn-risk alert
category: founder
tagline: Weekday mornings, paying accounts that look at risk (failed payments, usage drops, cancel at period end) with the score's reasons. Read-only; never touches billing.
steps:
- "Pulls failed payments, cancellations and renewals from Stripe"
- "Adds usage drops from PostHog when connected"
- "Scores each paying account and lists the reasons"
requires:
- kind: mcp
id: stripe
catalog: plugin:stripe
name: Stripe
why: Failed payments, cancellations, downgrades and renewals, through Stripe's official MCP server (OAuth). Read-only.
- kind: mcp
id: posthog
catalog: plugin:posthog
name: PostHog
optional: true
why: Active users per account for the usage-drop signal.
- kind: skill
id: founder-metrics
why: Definitions, read-only rules and source citations.
- kind: skill
id: founder-mrr-churn
why: The transparent at-risk score and its signals.
triggers:
- kind: schedule
cron: "0 9 * * 1-5"
install:
enabled: false
agentMode: Ask
speed: balanced
runMode: queued
autoApproveTools: true
maxRunMinutes: 15
replyStartsWith:
- "## Churn risk"
prompt: |
Score paying accounts for churn risk as of {{date}} using section 4 of the founder-mrr-churn skill (the simple churn model) and the founder-metrics rules.
Stripe through the `stripe` MCP server: failed or open invoices in the last 30 days, cancel_at_period_end, downgrades in the last 60 days, annual renewals in the next 45 days. Usage through the `posthog` MCP server if it is installed: active users per account this week vs their prior 4-week average. A source that is not connected is named once; never start a connection flow or ask for an API key.
Reply with only this Markdown, starting with "## Churn risk":
## Churn risk · {{date}}
**At risk (score ≥ 4)** — account, MRR, score, reasons, suggested owner action.
**Watch (2–3)** — account, MRR, score, top reason.
**Totals** — accounts scored, MRR at risk.
**Sources** — queries and windows.
If nothing scores 2 or more, reply "## Churn risk · {{date}}" and "No accounts at risk today."
Read-only: never refund, credit, retry a payment, change a subscription or contact a customer. Suggested actions are for me to take.Agent script
Score paying accounts for churn risk as of {{date}} using section 4 of the founder-mrr-churn skill (the simple churn model) and the founder-metrics rules.
Stripe through the `stripe` MCP server: failed or open invoices in the last 30 days, cancel_at_period_end, downgrades in the last 60 days, annual renewals in the next 45 days. Usage through the `posthog` MCP server if it is installed: active users per account this week vs their prior 4-week average. A source that is not connected is named once; never start a connection flow or ask for an API key.
Reply with only this Markdown, starting with "## Churn risk":
## Churn risk · {{date}}
**At risk (score ≥ 4)** — account, MRR, score, reasons, suggested owner action.
**Watch (2–3)** — account, MRR, score, top reason.
**Totals** — accounts scored, MRR at risk.
**Sources** — queries and windows.
If nothing scores 2 or more, reply "## Churn risk · {{date}}" and "No accounts at risk today."
Read-only: never refund, credit, retry a payment, change a subscription or contact a customer. Suggested actions are for me to take.