2
7 Comments

Show IH: Week 1 after launching SubSignal: what broke, what I changed, and why I'm looking for 10 honest testers

A week ago I launched SubSignal — a churn early-warning tool that sends SaaS founders a weekly email digest showing which customers are at risk and why.
Here's what actually happened.

The onboarding problem:
My first user signed up and didn't complete onboarding. I watched the drop-off point and simplified the entire flow. It's now significantly shorter. That one incomplete signup taught me more than a week of analytics would have.

What SubSignal actually does:
It connects to Stripe and optionally a JS snippet in your app. You set your own thresholds — login frequency, feature usage, payment signals. Every Monday you get one email: here are the customers showing warning signs, here's why, and a short message template to reach out to them directly.
No dashboard. No noise. Just a quiet heads-up before someone cancels.

Free tier covers up to 10 customers, no card needed — so you see a real weekly digest before deciding if it's worth paying for.

What I need:
10 founders with paying customers who are willing to try it free and tell me honestly if the weekly digest is useful. Looking for people who'll tell me when something isn't working.
If that's you: reply here or visit sub-signal.com and I'll help you get set up personally.

Thanks in advance!

posted to Icon for group Show IH
Show IH
on April 23, 2026
  1. 1

    Matheus, I took a look at sub-signal.com and I think the strongest thing here is the “no dashboard, just signal” wedge, but the page still makes people work a bit too hard before they feel the cost of waiting.

    1. The hero explains what it does, but not the financial consequence fast enough. I’d test a headline closer to “Know which customers are about to churn before Stripe tells you,” then keep the weekly email / no dashboard angle as the proof.
    2. The sample digest is promising, but above the fold it can still read like mock data. A tiny “example weekly digest” label plus one real founder outcome or real account screenshot would increase trust a lot.
    3. The “£1k–£20k MRR” qualifier is directionally good, but I’d explain why that segment is the sweet spot. Otherwise it can feel arbitrary and make some best-fit founders self-disqualify.
    4. The setup copy mentions a JS snippet and Stripe keys, but it doesn’t defuse the obvious engineering/security hesitation. A short trust block near the CTA would help, for example what data you do and don’t read, how long setup actually takes, and whether removal is easy.

    If helpful, I do very cheap conversion teardowns for founders who want this kind of homepage markup in more detail: https://roastmysite.io/go.php?src=external_manual_ih_subsignal_week1_apr26_usd_presell_hv

  2. 1

    The "one incomplete signup taught me more than a week of analytics" line really resonates — I had the same realization with my own indie app (a small Captio-style memo tool). One specific behavioral drop-off beats a week of charts.

    On the 10-tester ask: from my own community recruiting on IH and Reddit, conversion goes way up if you (a) post in the niche subreddits where SaaS founders are already venting about churn, and (b) DM warm-but-quiet IH connections directly instead of relying on the post alone. Cold post alone got me 0–1 testers. Targeted DMs based on past comments got me 4–6.

    What channels are you planning to recruit from beyond IH?

  3. 1

    Honest week 1 posts like this are the most useful thing on IH. What's your current acquisition channel — are signups coming from organic search, direct, or referral? Curious what's moving the needle this early.

  4. 1

    Interesting approach, especially the “no dashboard, just a weekly signal” part.

    I’m working in a very different space (WordPress client sites), but the pattern is surprisingly similar.

    The biggest problems don’t come from obvious events - they come from subtle behavior shifts. Clients stop logging in, start clicking things randomly, or ignore warnings… and then something breaks.

    What I’ve learned is that early signals matter more than detailed analytics, but most tools overwhelm instead of simplifying.

    Curious - how are you deciding what counts as a “risk signal”?
    Is it mostly threshold-based, or are you seeing patterns emerge from real usage already?

  5. 1

    Early testers are useful, but the best ones are usually the people who got confused, bounced, or almost paid in week 1. If you bring on 10, give each one a single job to stress, onboarding, first report, alert quality, or cancel flow, so the feedback is less vague and easier to act on. Sharing what broke publicly is also a nice filter, the people who still opt in tend to be the most helpful.

  6. 1

    This is a clean direction — especially the “no dashboard, just signal” part. That’s the real differentiator.

    One thing that stood out though: the name SubSignal feels a bit… secondary?
    Like something under the main layer, whereas what you’re actually doing is pretty core to decision-making (churn risk isn’t a side signal, it’s the signal).

    Feels like there’s a slight mismatch between how strong the value is vs how it’s framed.

    Curious — did you test other directions for the name/positioning, or did this one just stick early?

  7. 1

    Matheus, shifting from a complex dashboard to a "no noise" weekly email digest is a brilliant way to solve the notification fatigue most founders feel. By focusing on churn early-warning signals and providing direct outreach templates, you're transforming raw Stripe data into an actionable retention system that actually saves time instead of adding another task to the list.
    I’m currently running Tokyo Lore, a project that highlights high-utility logic and validation-focused tools like yours. Since you’re building the definitive platform for proactive churn management, entering SubSignal could be the perfect way to turn your current launch and testing phase into a winning case study while your odds are at their absolute peak.

Trending on Indie Hackers
The most underrated distribution channel in SaaS is hiding in your browser toolbar User Avatar 185 comments I launched on Product Hunt today with 0 followers, 0 network, and 0 users. Here's what I learned in 12 hours. User Avatar 156 comments I gave 7 AI agents $100 each to build a startup. Here's what happened on Day 1. User Avatar 98 comments How are you handling memory and context across AI tools? User Avatar 56 comments Do you actually own what you build? User Avatar 41 comments Show IH: RetryFix - Automatically recover failed Stripe payments and earn 10% on everything we win back User Avatar 34 comments