Solo founders: how do you handle changelogs, maintenance notices, and status updates today?
I’m trying to understand how small SaaS products handle post-launch communication before building any more features.
For your current product:
Where do you publish release notes?
How do you announce scheduled maintenance?
What do you do when there’s an outage or degraded service?
Are you using separate tools, building these features yourself, or mostly handling them manually?
I’m especially interested in the awkward parts — duplicated updates, tools that feel too expensive for a solo project, or operational pages that never get maintained.
I’m building a lightweight tool around this problem, but I don’t want to assume that combining these functions is automatically useful.
What are you using today, and what would make you switch?
Trending on Indie Hackers
One thing that stood out to me is that you're questioning whether these are actually separate jobs or just different moments of the same conversation with users.
Sometimes products feel fragmented because the workflow is fragmented, not because the functionality is.
That’s exactly the distinction I’m trying to understand.
A changelog, maintenance notice, and status update may look like separate features, but from the founder’s side they often start with the same action: something changed, and users need to know about it.
The fragmentation may come from having to rewrite or republish the same information across an in-app notice, a public page, and a status channel.
In your current workflow, do those updates come from one source and get reused, or are they still handled as separate tasks?
That's a good question.
I do have a perspective on it, but I don't think I'd do it justice in a public comment thread.
I'd be interested in continuing the conversation by email if you're open to it. What's the best email to reach you on?