Why I built ReleaseLog — and why your users are leaving without telling you
Most indie founders build great products and tell nobody.
They fix bugs, add features, improve their product every week. Their users have no idea. They find out by accident. Or they don't find out at all. And then they churn quietly, without explanation, because the product felt abandoned even when it wasn't.
That's the problem ReleaseLog exists to solve.
Users churn when they don't know about features that would have kept them. A user who submits a feature request and watches it move from Planned to Shipped doesn't churn the same way a passive user does. The product doesn't have to be perfect. It just has to feel alive.
ReleaseLog gives your users three things they're not getting right now:
A public changelog so they know what changed. A public roadmap so they know what's coming. A feature request board so they feel heard.
The AI writing assistant turns rough notes into polished updates in seconds. Subscribers get notified automatically every time you publish. The embeddable widget puts a "What's New" button directly inside your product so updates reach users in the moment, not in a separate tab nobody remembers to visit.
No annual contracts. No enterprise pricing. Free to start. $12/month after that, AI included.
If you've ever wondered whether a user left because they didn't know about something you'd already built, the answer is probably yes.
