Tiny Changelog
A changelog and release-note tool for small SaaS teams.
Turn rough release notes into clear product updates customers can understand.
Launch readiness sample
81%
example score
Original brief input
A changelog generator for small SaaS teams that ship often but do not have a product marketing workflow.
Positioning
A practical release communication layer for founders who ship often but do not want a heavy product marketing process.
MVP scope
Project workspace, release editor, changelog page, AI polish, tags, scheduled publish, and social snippets.
Launch angle
Share before-after examples of messy commit notes turned into clear release posts.
Generated asset preview
This is the kind of package a full BSLaunchKit project can expand into.
Landing page copy
Hero
Turn rough release notes into customer-ready updates.
Subheadline
Tiny Changelog helps small SaaS teams publish clearer product updates without adding a heavy marketing process.
Product Hunt pack
Tagline
AI-assisted changelogs for small SaaS teams that ship often.
Maker comment
This is for founders who ship every week but struggle to communicate what changed in a way customers understand.
Lead tracker preview
A simple starting point for tracking outreach, replies, and first opportunities.
| Lead | Source | Signal | Status |
|---|---|---|---|
| Devtool founder | X/Twitter | Posts weekly release threads | Warm |
| B2B SaaS team | No public changelog yet | Qualified | |
| Open-source maintainer | GitHub | Needs release summaries | Research |
Full AI build prompt
A complete prompt that can be pasted into Codex, Cursor, Claude Code, or another coding agent to scaffold the product.
Build a production-ready SaaS called Tiny Changelog. Goal: Create a changelog and release-note tool for small SaaS teams that ship often but do not have a product marketing workflow. Stack: - Next.js App Router with TypeScript - Prisma ORM with PostgreSQL - Auth.js authentication - Stripe for subscriptions - Tailwind CSS and shadcn/ui - Markdown editor with preview - OpenAI integration for polishing release notes Core data models: - User: id, name, email, image, createdAt - Workspace: id, ownerId, name, slug, createdAt - Project: id, workspaceId, name, slug, publicUrl, createdAt - Release: id, projectId, title, slug, status, summary, markdownContent, publishedAt, createdAt, updatedAt - ReleaseItem: id, releaseId, type, title, description, impact - Tag: id, projectId, name, color - ReleaseTag: releaseId, tagId Pages: - Dashboard: recent releases, drafts, published releases, quick create - Projects: list and create projects - Project settings: name, slug, public changelog URL, brand color - Releases: list with draft/published filters - Release editor: title, summary, release items, markdown editor, AI polish button - Public changelog page: SEO-friendly list of published releases - Release detail public page: title, date, tags, markdown content - Billing: Stripe checkout and portal AI polish flow: - User writes rough release notes or imports bullet points - AI returns clearer customer-facing copy - Preserve technical facts and avoid exaggerated claims - Provide three tone options: concise, friendly, technical - User can accept, edit, or discard the AI version UX requirements: - Make it easy to go from rough notes to published changelog in under five minutes - Show a split editor/preview layout on desktop - Provide templates: bug fix, new feature, improvement, deprecation - Add empty states that guide the user to create the first release - Public changelog must look clean and trustworthy Business rules: - Public pages show only published releases - Drafts are private to the workspace - Slugs must be unique per project - Users can only access workspaces they own or belong to Acceptance criteria: - A user can create a project, draft a release, add release items, polish the notes with AI, publish a public changelog entry, and share the public URL - The app must be responsive, type-safe, and include server-side authorization checks