You lost 3 customers this week. You just don't know who yet.

Yes. ChurnCast uses a restricted, read-only Stripe API key that you create and scope yourself. We can read customer and subscription data. We physically cannot charge anyone, issue refunds, or modify a single record in your Stripe account. We never see raw card numbers, CVVs, or bank details because Stripe never exposes them to anyone, including you. Revoke our access in one click from your Stripe dashboard at any time.

Those are brilliant analytics tools. They show you dashboards: MRR, churn rate, LTV, cohort curves. ChurnCast is the opposite shape of product. We don't show you graphs. We tell you which specific customer to email this week, why they're at risk, and what to say to them. Baremetrics tells you churn went up. ChurnCast tells you Sarah hasn't logged in for 31 days and here's the email to send her.

Honest answer: it's rule-based, not machine learning. It combines signals that correlate strongly with churn in early-stage SaaS (failed charges, long inactivity, declining usage, short tenure with recent friction) and produces a score. It may miss edge cases and may sometimes flag customers who were never going to leave. But it catches the most common patterns, and for a solo founder with no CS team, "catches the obvious ones" is infinitely better than "catches nothing because nobody is looking."

ChurnCast is more valuable at that scale, not less. When you have 20 customers, losing one is 5% of your MRR. Losing two is a noticeable hit. At 20 customers you probably know each by name, which makes a targeted intervention email land harder and convert better than at any larger scale. Small SaaS is exactly who this was built for.

No. The emails are suggestions, not sends. ChurnCast never touches your mailbox or emails your customers on your behalf. You get a drafted email per at-risk customer: edit it, personalise it, copy it into your email client, send it, ignore it, or bin it entirely. They're a starting point to save you the 10 minutes of staring at a blank compose window trying to figure out what to write.

Stripe lets you create restricted API keys with granular permissions. The key you paste into ChurnCast has read access to customers, subscriptions, invoices, and charges, with no write access to anything. No ability to create, update, delete, charge, refund, or modify. If someone compromised our database tomorrow, the worst thing they could do with your key is look at the same data you'd see in your own Stripe dashboard.

Yes. One click in the billing page, no cancellation form, no retention call, no awkward email exchange. If ChurnCast stops being useful, you leave. We hate friction-based retention and refuse to build it. Not happy in the first 30 days? Email us for a full refund.

Any currency Stripe supports. ChurnCast reads whatever currency your subscriptions are billed in and displays it as-is. USD, EUR, GBP, AUD, CAD — if Stripe handles it, ChurnCast handles it.