ReleaseVoice - AI Changelog Writer That Actually Sounds Like Your Brand

Every SaaS founder dreads writing the changelog — it either sounds like a GitHub commit dump or a corporate press release. ReleaseVoice takes your merged PRs and Jira tickets, learns your brand voice from past blog posts, and writes a customer-facing changelog that people actually read. Ship features and the announcement in the same deploy.

𝕏 Post Reddit HN

Difficulty

beginner

What is it?

Indie SaaS founders and small dev teams consistently skip or delay changelogs because translating technical diffs into customer-friendly copy is a context-switching tax nobody wants to pay. ReleaseVoice connects to GitHub via webhook, pulls merged PR titles and descriptions from the last sprint, ingests past changelogs or blog posts to extract brand voice, then generates a polished entry in under 30 seconds. One-click publish to a hosted public changelog page with an RSS feed and optional Slack/email notify. Fully buildable with the GitHub API, Claude API for voice-matched generation, and a simple Supabase-backed hosted page.

Why now?

The April 2026 vibe-coding wave has produced thousands of new indie SaaS products shipping features weekly with zero changelogs — the backlog of neglected changelog debt is at an all-time high and founders are vocal about it on X and r/indiehackers.

▸GitHub PR webhook ingests merged PRs and auto-groups them by feature, fix, and improvement.
▸Brand voice extractor reads 3 past blog posts or changelogs and styles all output to match.
▸One-click hosted public changelog page with RSS feed and custom domain support.
▸Email subscriber notify via Resend fires automatically on publish.

Target Audience

Solo SaaS founders and dev teams of 1-5 people — roughly 300k active indie SaaS products on the market skipping or delaying changelogs.

Example Use Case

Priya, a solo SaaS founder, merges 11 PRs on Friday, clicks Generate in ReleaseVoice, reviews the draft in 90 seconds, hits Publish, and 340 email subscribers get the update before she closes her laptop.

User Stories

▸As a solo SaaS founder, I want my merged PRs automatically turned into a customer-friendly changelog draft, so that I stop skipping release notes entirely.
▸As a small dev team lead, I want the changelog to sound like our brand voice and not a commit log, so that customers actually read it.
▸As a subscriber, I want an email when a new changelog is published, so that I stay informed without checking a page manually.

Acceptance Criteria

GitHub Webhook: done when merged PR titles appear in dashboard within 60 seconds of merge. AI Generation: done when draft matches uploaded brand voice sample and groups PRs by type. Publish Flow: done when clicking Publish makes the changelog page publicly accessible via slug URL. Subscriber Notify: done when all project subscribers receive the email within 5 minutes of publish.

Is it worth building?

$19/month x 80 users = $1,520 MRR at month 3. $49/month team plan x 50 teams = $2,450 MRR additive. Math assumes ProductHunt launch driving 500 signups at 8% conversion.

Unit Economics

CAC: $12 via ProductHunt and organic X content. LTV: $228 (12 months at $19/month). Payback: under 1 month. Gross margin: 92%.

Business Model

SaaS subscription

Monetization Path

Free tier: 3 changelog entries/month. Paid $19/month: unlimited entries, custom domain, email subscribers. $49/month: team seats, Slack notifications, Jira integration.

Revenue Timeline

First dollar: week 2 via beta upgrade. $1k MRR: month 2. $5k MRR: month 6.

Estimated Monthly Cost

Claude API: $30, Vercel: $20, Supabase: $25, Resend: $10, Stripe fees: $20. Total: ~$105/month at launch.

Profit Potential

Side income to full-time at $5k MRR with zero infrastructure cost growth.

Scalability

Medium-high — white-label changelog hosting for agencies is a natural V3 play.

Success Metrics

Week 1: 5 beta users generate changelogs. Month 2: 60 paid. Month 3: less than 8% churn.

Launch & Validation Plan

Post in r/indiehackers and r/SaaS asking how teams handle changelogs. If 20+ replies say they skip or dread it, ship immediately.

Customer Acquisition Strategy

First customer: DM 15 active indie hackers on X who recently shipped features but posted no changelog, offer 6 months free in exchange for a testimonial. Ongoing: ProductHunt launch, r/indiehackers, developer Twitter content marketing.

What's the competition?

Competition Level

Low

What's the roadmap?

Feature Roadmap

V1 (launch): GitHub sync, AI draft generation, hosted page, subscriber email. V2 (month 2-3): Linear and Jira connectors, custom domain, RSS feed. V3 (month 4+): team seats, white-label, analytics on changelog views.

Milestone Plan

Phase 1 (Week 1): GitHub webhook, Claude generation, Supabase storage live with 3 beta users. Phase 2 (Week 2): hosted page, Resend notify, Stripe billing, landing page. Phase 3 (Month 2): 50 paid users, Linear connector, custom domain support.

How do you build it?

Tech Stack

Next.js, Claude API for voice-matched copy generation, GitHub API, Supabase, Resend for subscriber notifications, Stripe — build with Lovable for UI, Cursor for GitHub webhook logic, v0 for changelog page component.

Suggested Frameworks

N/A — this is not an AI model-building idea

Time to Ship

1 week

Required Skills

GitHub webhook setup, Claude API prompt engineering for voice extraction, Supabase, Resend subscriber list.

Resources

GitHub Webhooks docs, Claude API docs, Supabase quickstart, Resend audience API docs.

MVP Scope

pages/index.tsx, pages/dashboard.tsx, pages/changelog/[slug].tsx, api/github-webhook.ts, lib/pr-parser.ts, lib/voice-extractor.ts, lib/claude-generator.ts, lib/subscriber-notify.ts, supabase/schema.sql, components/ChangelogCard.tsx.

Core User Journey

Connect GitHub -> merge PRs -> receive auto-draft in dashboard -> edit and publish in 2 minutes -> subscribers notified.

Architecture Pattern

GitHub merge event -> webhook -> Next.js API route -> PR parser -> Claude API generates draft -> saved to Supabase -> founder reviews and publishes -> Resend notifies subscribers -> public changelog page served from Supabase.

Data Model

User has many Projects. Project has many ChangelogEntries. ChangelogEntry has many PRs. Project has many Subscribers. Project has one VoiceProfile.

Integration Points

GitHub API for PR data, Claude API for generation, Supabase for changelog storage, Resend for subscriber email, Stripe for billing, Vercel for hosting.

V1 Scope Boundaries

V1 excludes: Jira integration, team collaboration, white-label, mobile app, Linear connector.

Success Definition

A solo founder who discovered the product on ProductHunt connects GitHub, generates a changelog, and publishes it to subscribers without messaging the founder.

Challenges

The hardest non-technical problem is convincing founders to pay for something they feel they should just do themselves. Framing this as a time-saving tool rather than a writing tool is the key positioning unlock.

Avoid These Pitfalls

Do not build Jira integration before 20 paying GitHub users — validate the core before adding connectors. Do not let the AI generation run without a human review step or you will ship embarrassing copy. First 10 paying customers will take 3x longer to find than building the product.

Security Requirements

Supabase Auth with GitHub OAuth. RLS on all tables scoped to user ID. GitHub webhook secret verified on every request. Rate limit generation endpoint to 10 req/min per user.

Infrastructure Plan

Vercel for Next.js and API routes. Supabase for Postgres and auth. Resend for email. Sentry for errors. GitHub Actions for CI/CD. All in one Vercel project under $50/month total.

Performance Targets

Launch: 80 DAU, 300 req/day. API response under 300ms for dashboard. Claude generation under 8s. Page load under 1.5s for public changelog.

Go-Live Checklist

☐Security audit complete
☐Stripe checkout tested end-to-end
☐Sentry live
☐Vercel Analytics on
☐Custom domain with SSL
☐Privacy policy and terms live
☐5 beta founders signed off
☐Rollback plan documented
☐ProductHunt launch post and r/indiehackers post drafted.

How to build it, step by step

1. Run npx create-next-app@latest release-voice --typescript. 2. Install @supabase/supabase-js, @anthropic-ai/sdk, resend, stripe, octokit. 3. Create Supabase schema for projects, changelog_entries, subscribers, voice_profiles. 4. Build api/github-webhook.ts to receive push events and extract merged PR titles. 5. Build lib/voice-extractor.ts that sends 3 user-pasted blog posts to Claude and returns a voice descriptor. 6. Build lib/claude-generator.ts with a system prompt injecting the voice descriptor and PR list. 7. Build dashboard page showing pending draft with edit textarea and Publish button. 8. Build pages/changelog/[slug].tsx as a public hosted page reading from Supabase. 9. Wire Resend to fire to all project subscribers on publish. 10. Deploy to Vercel, set GitHub webhook URL, add Stripe $19/month plan.

Generated

April 13, 2026

Model

claude-sonnet-4-6

← Previous

ReviewRadar - Automated Multi-Platform Review Intelligence for Local Businesses

PickLens - Computer Vision Pick Error Detector for Small 3PL Warehouses

Disclaimer: Ideas on this site are AI-generated and may contain inaccuracies. Revenue estimates, market demand figures, and financial projections are illustrative assumptions only — not financial advice. Do your own research before making any business or investment decisions. Technology availability, pricing, and market conditions change rapidly; always verify details independently.