0
0 Comments

I kept finding out about churn too late — so I built the tool I wished existed

The pattern was always the same. Stripe would ping me — someone cancelled. I'd open the app, scroll back through their activity, and see it: they'd stopped logging in two weeks ago. Feature usage had dropped off the week before that. The signs were all there. I just wasn't watching.

I build small SaaS products. I hit this with my own app and kept hearing the same thing from other founders — and every time, the fix felt obvious in hindsight. If I'd just reached out a week earlier, I might have saved it.

The tools built for this problem are either too expensive (Gainsight starts at £1k/mo), too complex (dashboards I'd have to remember to check), or too magical (black-box health scores that don't tell me why someone is at risk).

So I built SubSignal. It does three things:

  • Watches login frequency and Stripe signals

  • Fires when a customer breaks a threshold you set yourself

  • Sends one email every Monday — who went quiet, why, and one suggested action per account

No dashboard. No scores. Just a list, a reason, and an obvious next step.

It's live at sub-signal.com. Free up to 10 customers, no card required.

I'm currently looking for founders to use it and tell me what's broken. If that sounds like you, drop a comment and I'll send you a one-pager that explains exactly what's involved before you commit — no obligation until you've read it.

posted toAvatar for product SubSignal
SubSignal