Iโm 19. Launched my first SaaS 5 days ago. 0 users. Devs donโt pay for changelogs. Here is my pivot plan. ๐
Hey everyone, ๐
A few days ago, I launched Logvoidd (an automated GitHub changelog generator). I got some amazing advice from this community, but the harsh reality hit me: 0 active users.
The hard lesson I learned: Devs don't hate writing changelogs enough to adopt a new tool. Most either use simple commit tools or just don't care.
But Iโm not giving up or scrapping my code. My backend works perfectly. Now, I just need to aim it at a problem where money or reputation is actually on the line.
Iโm pivoting. Here are 3 directions I can take my existing engine. Which of these solves an actual "bleeding-neck" problem for you?
- The Freelancer Client Report ๐ผ
Translating your technical commits into professional, plain-English weekly progress reports for non-technical clients. (Goal: Look like a pro and get your invoices paid without the manual communication overhead).
- The Founder "Friday Update" ๐
Auto-generating crisp, non-technical weekly update drafts for your stakeholders, angel investors, or team members based purely on what code you shipped this week.
- The Indie Hacker Marketing Engine ๐ฑ
Turning your weekly GitHub commits into auto-generated SEO blog posts or Twitter/X "build in public" threads, so you can market your product without actually writing marketing copy.
My question to you:
Roast these options. Which one of these would you actually use in your workflow, and which ones are just another "nice to have"?
I'm ready to iterate. Thank you! ๐
Posted Apr 5, 2026, 2:53 AM UTC