There is a particular kind of awkwardness, familiar to every founder who has ever shipped a meaningful update to a product, that has nowhere good to go on most launch platforms. You ship a v2. You want to talk about it. You also want to keep the social proof, the comments, and the upvotes you earned the first time. The traditional answer, submit a brand-new entry and pretend the old one never happened, is not a great answer. The relaunch flow on LaunchLoop is our attempt at a better one.
Why it matters
AI products, in particular, iterate fast. The model under the hood changes; the interface changes around it; the pricing changes; the audience sometimes changes too. The old launch model, one shot, one entry, punishes teams that ship meaningful updates a few months later by treating those updates as either invisible or as awkward duplicates. The relaunch flow lets you go back on the loop with a clean slate, while keeping all the history that came before.
How a relaunch works
The flow itself is short on purpose. From your account page, you pick the product you want to relaunch and step through three screens: new visuals, a new version label, and a changelog entry written in your own words. The changelog is required, not because we like paperwork, but because a relaunch without context is, in our experience, the single fastest way to confuse the people who supported you the first time.
Each relaunch can earn its own badge
Reaching the top of the loop with a relaunched product earns its own stamped badge, distinct from the original. We treated this as non-negotiable: a relaunch is a real event, not a re-run of an old one, and it deserves its own credential.
Built-in changelog
Every relaunch automatically generates a public changelog entry on your product page, so visitors can see exactly what is new since the last version. It is the same surface, mechanically, that powers the page you are reading right now. We like the symmetry: the platform and the products on it both ship in public, in the same format.