Community SaaS: retention loops that cut churn in 9 days
Community SaaS founder, USA
Weekly churn from 18% to 5-6% in 3 weeks. Notifications, search, and moderation shipped.
18% → 6%
Weekly churn
9
Days to ship
<600ms
Notification fanout
The situation
- A community platform for hobby groups had pulled 4,000 signups in 6 weeks.
- Then the churn graph hit 18% per week.
- The founder dug into cancellation reasons: people weren't getting notified about replies, search showed posts from a week ago, and moderators couldn't actually moderate, they could only delete.
What we did
- Live notification fanout: in-app, push, email, under 600ms
- Per-community Typesense search index with live trigger updates
- Moderator console with bans, mutes, report queues, audit log
- Reply, mention, and DM notifications across all channels
- Daily digest email for muted users
- Reactivation email when a hot thread starts in a joined community
The result
- Weekly churn settled at 5-6% within 3 weeks.
- MAU tripled in the next 60 days at the same ad spend, since reactivated users finally stayed. The founder turned ad spend back on, and the platform now sustains 12,000 weekly active members across 230 communities.
Timeline
How it unfolded
Day 1
Churn root cause + triage
Days 2-3
Real-time notifications
Days 3-5
Search rebuild
Days 5-7
Moderator console
Days 7-8
Digest email + reactivation
Day 9
Rollout + churn watch
“I was about to shut it down. 9 days later we had real notifications, real search, and our moderators had teeth. The graph turned around immediately.”
Founder · Community Platform · Lisbon, Portugal
Stack
Supabase RealtimeSupabaseOneSignalTypesense CloudResendSentry