Churnahead watches the subscriptions in your Stripe account. Every morning at eight it emails you the customers likely to cancel, why, and one thing to do about each.
Read-only access to Stripe, five minutes to connect. Free up to 25 paying customers.
10 accounts, $2,782/mo on the line. Each one arrives with the reason, the money, the date and one thing to do.
High risk
Cancellation scheduled for Nov 24. Said: too expensive (“Too pricey for a team of three now that the promo ended.”)
Next step: Ask what's missing and offer a quick call, a pause, or a lower plan.
Cancellation scheduled for Nov 25. Said: missing features (“We needed an accounting export and it never shipped.”)
Next step: Ask what's missing and offer a quick call, a pause, or a lower plan.
Medium risk
Disputed a $891 charge from Sep 13.
Next step: Reach out today: find out what went wrong before they leave for good.
Trial ends Oct 30 (in 2 days) with no payment method on file, worth $199/mo. Customer for 9 days.
Next step: Offer a quick setup call and make sure they know how to add a card.
Subscription is past due.
Next step: Send a friendly note with a link to update their card.
Payment failed (3 attempts), $58 outstanding since Oct 21.
Next step: Send a friendly note with a link to update their card.
Billing dropped from $980 to $490 (−50%) on Oct 13.
Next step: Check in: did the team shrink, or is something not working?
Refunded in full: $5,389.92 on Oct 15.
Next step: Reach out today: find out what went wrong before they leave for good.
In month 3 as a customer: 7 of 12 past churns on monthly plans happened in that month (18% of customers who reach it cancel, against 3% in a typical month).
Next step: Check in before the month most customers leave in: show them what they'd lose and what's next.
Discount ends Nov 6: price goes from $99 to $198/mo.
Next step: Tell them the price is changing before the invoice does, and remind them what they get.
10 accounts at risk ($2,782/mo)
Cancellation scheduled for Nov 24. Said: too expensive (“Too pricey for a team of three now that the promo ended.”)
Next step: Ask what's missing and offer a quick call, a pause, or a lower plan.
Mark contacted · Mark saved · Snooze 14 days
Cancellation scheduled for Nov 25. Said: missing features (“We needed an accounting export and it never shipped.”)
Next step: Ask what's missing and offer a quick call, a pause, or a lower plan.
Mark contacted · Mark saved · Snooze 14 days
Disputed a $891 charge from Sep 13.
Next step: Reach out today: find out what went wrong before they leave for good.
Mark contacted · Mark saved · Snooze 14 days
Trial ends Oct 30 (in 2 days) with no payment method on file, worth $199/mo. Customer for 9 days.
Next step: Offer a quick setup call and make sure they know how to add a card.
Mark contacted · Mark saved · Snooze 14 days
Subscription is past due.
Next step: Send a friendly note with a link to update their card.
Mark contacted · Mark saved · Snooze 14 days
Payment failed (3 attempts), $58 outstanding since Oct 21.
Next step: Send a friendly note with a link to update their card.
Mark contacted · Mark saved · Snooze 14 days
Billing dropped from $980 to $490 (−50%) on Oct 13.
Next step: Check in: did the team shrink, or is something not working?
Mark contacted · Mark saved · Snooze 14 days
Refunded in full: $5,389.92 on Oct 15.
Next step: Reach out today: find out what went wrong before they leave for good.
Mark contacted · Mark saved · Snooze 14 days
In month 3 as a customer: 7 of 12 past churns on monthly plans happened in that month (18% of customers who reach it cancel, against 3% in a typical month).
Next step: Check in before the month most customers leave in: show them what they'd lose and what's next.
Mark contacted · Mark saved · Snooze 14 days
Discount ends Nov 6: price goes from $99 to $198/mo.
Next step: Tell them the price is changing before the invoice does, and remind them what they get.
Mark contacted · Mark saved · Snooze 14 days
Opened from the morning email. The links work without signing in.
One restricted key with Read access, or one click that asks Stripe for read-only access. This is everything that comes in, what stays, and what goes out.
Never writes: no refunds, no cancellations, no changes.
Never card numbers or bank details.
Never to your customers.
Stripe
Connected and syncing. Disconnecting keeps the synced data until you reconnect or delete it below.
Connected
With a restricted key you pasted · since 28 Oct 2026
Restricted key
rk_live_••••••••••••••••••••
Give it Read access to Customers, Subscriptions, Invoices, Charges and PaymentMethods, plus Customer portal so the setup check can see whether customers are asked why they cancel. Nothing else. Secret keys (sk_) aren't accepted.
Setup check
Delete synced data
Disconnects Stripe and deletes everything synced from it: customers, subscriptions, invoices, charges, scores, outcomes, alerts, backtests and past digests.
Trial ends Oct 30 with no card on file: 35 points, plus 10 for a customer nine days old. At 25 an account makes the morning list, at 50 it goes to the top. Add the card and see.
Card on file
45/100, medium risk
Connect Stripe and the rules replay your last twelve months. On the demo workspace they flagged 92% of the $6,713/mo lost, a median of 30 days before the customer left.
Left in October, $116/mo. Downgraded.
Flagged 30 days early, medium
Left in July, $1,592/mo. Downgraded.
Flagged 30 days early, medium
Left in June, $174/mo. Cancellation scheduled.
Flagged 15 days early, high
Left in May, $796/mo. New customer, then downgraded.
Flagged 30 days early, medium
Left in May, $116/mo. New customer only.
Missed
Left in April, $1,089/mo. New customer, then downgraded.
Flagged 30 days early, medium
Left in April, $163/mo. Annual renewal coming.
Missed
Left in March, $297/mo. Payment failed, then canceled.
Flagged 89 days early, medium
Left in March, $1,791/mo. New customer, then canceled.
Flagged 27 days early, high
Left in February, $294/mo. New customer, then payment failed.
Flagged 29 days early, high
Card expiry history isn't kept by Stripe, so that rule is shown as not measurable, never as a miss. Yours runs on your own history the moment you connect.
Every account starts on Free: up to 25 paying customers, with the list every Monday. Past that, Starter is $39 a month up to 500 customers, and Growth is $99 up to 3,000. Every feature is on every plan, billed monthly by card.
Read, and nothing else. Either connect in one click, which asks Stripe for read-only access, or paste a restricted key with Read access to Customers, Subscriptions, Invoices, Charges and PaymentMethods (plus Customer portal, if you want the setup check). Secret keys aren't accepted. The key is encrypted at rest.
No. It emails you, or posts to your Slack. What you say to the customer, and whether you say anything, is yours.
Yes. One button on the Connect page disconnects Stripe and deletes everything synced from it: customers, subscriptions, invoices, charges, scores, outcomes and past digests. Disconnecting without it keeps the data, so a new key picks up where the old one stopped.
The first sync starts the moment you connect, and the backtest is ready when it finishes. After that it syncs every day. With one-click connect, a cancellation or a failed payment also rescores the account within a minute.
No. Every signal comes from billing data Stripe already keeps, so there is nothing to install in your product.
They chart the churn you already had. This names the customers who are about to leave, with the reason, while there is still time to talk to them.
Yes. Every account in the email and in Slack has links to mark it contacted, mark it saved or snooze it for 14 days. They work without signing in, and each one asks you to confirm first, because mail scanners open links.
A contact older than 30 days closes itself: saved if the customer still pays, churned if not. The dashboard keeps the revenue saved and lost over the last 30 days.
You can mute any rule that doesn't fit your business, and the backtest shows how each one would have done on your own history. The points themselves are fixed, so every score stays explainable.
Yes. It runs from one Docker Compose file, with Postgres, for a single Stripe account or for many workspaces with sign-in by email.
We email you a sign-in link. Connect Stripe read-only in the next step, and the first sync and the backtest start at once.