Launching tomorrow, would love your honest take
by•
Hi everyone, I'm Mustafa, a product designer from Göteborg.
For the past few months I've been building Loyaltide. The idea came from a simple observation: most customers who cancel leave signals in Stripe weeks before they go. A card that fails. A downgrade. A cancellation scheduled for the end of the month. The data is there, it's just buried under thousands of events nobody reads.
Loyaltide connects to Stripe read-only and gives every customer a churn risk score from 0 to 100, with the exact reasons behind it. Your dashboard tells you who to contact first and how much time you have left, and a morning email lists who needs you today. You can see how many of your customers are at risk before you pay anything.
It launches on Product Hunt tomorrow. I'm not looking for hype, I'm looking for honest feedback from people who run subscription businesses:
1. How do you catch churn today, if at all?
2. Would a risk score with reasons change what you do, or is it just another dashboard?
Any answer helps. Thanks for reading.
22 views
Replies
Honest take from a subscription app: most of my subscriptions come through the App Store and Google Play, where Stripe isn't involved at all, so a Stripe only tool would see a slice of my customers. Reading store events through RevenueCat or Adapty webhooks would make it relevant to every mobile app maker here. On your second question, a score alone would be another dashboard for me, but "who to email today and what to say" would change what I do. For the Stripe slice, a failed card is the clearest signal there is, and the fix is usually a friendly email with an update link rather than a discount. Good luck with the launch!
@gbasovv Thanks George, this is exactly the kind of answer I was hoping for.
You're right on the mobile side. Loyaltide is Stripe only for now because I'm focusing on B2B SaaS first, but RevenueCat is on my list and your comment moves it up.
The second part hit home. "Who to email today and what to say" is where I'm taking it next: each at-risk customer gets a suggested message based on the reason, like the friendly card update email you described for failed payments.
Curious: when a card fails on your Stripe side today, do you send that email yourself or rely on Stripe's automatic retries?