Hey Product Hunt friends, I built Launchpack because launch prep has a weirdly annoying failure mode: by the time your product is ready, the story is scattered everywhere. It is in worklogs, meeting notes, changelogs, Git commits, screenshots, customer quotes, and half-written posts. Then launch day arrives and you are staring at a blank Product Hunt form trying to compress weeks of work into a tagline. Launchpack turns that mess into a structured launch kit. What it generates: - Product Hunt tagline and short description. - Maker first comment. - Launch FAQ. - X, LinkedIn, and email drafts. - 30-second demo script. - Launch checklist. - Receipts that connect strong claims back to the source notes. The receipts are the part I care about most. Generic AI copy is easy. Credible launch copy is harder. If the kit says something bold, I want the maker to see where that claim came from and decide whether it is actually launch-worthy. The app is intentionally simple: - Free and open source. - Runs as a static GitHub Pages app. - No account. - No backend. - Local deterministic fallback by default. - Optional OpenAI-compatible AI Engine for LM Studio, Ollama, llama.cpp, vLLM, LocalAI, LiteLLM, or your own remote proxy. - The AI Engine is optional because not every maker wants to send launch notes to a third-party service. You can use the public app, fork it, self-host it, or point it at a local model running on your laptop. I would love feedback on three things: 1. Would you trust the generated launch kit as a real first draft? 2. Which import should come next: GitHub releases, Notion docs, or meeting transcripts? 3. Does the AI Engine setup feel clear enough for local model users? Thanks for taking a look. I will be here all day answering questions and shipping fixes.

Launchpack

Turn messy worklogs into Product Hunt launch kits

Turn messy worklogs into Product Hunt launch kits