Most launches I've watched, my own included, have the same shape. Day one is a screenshot, a one-liner and a link. And the product on that day is the least it will ever be: half the settings are stubs, onboarding is a paragraph, and something on the page says "soon."
Then week three happens. The bug someone reported in the comments got fixed. The empty state finally has a real example in it. The thing the maker kept apologizing for on launch day is just gone. Honestly, that's usually the first version I'd recommend to a friend.
By week three, though, nobody's looking. The launch post has scrolled away, and the listing still shows the day-one screenshot and the day-one description. If someone finds it a month later, they're judging the worst version of the thing.
A few habits I've picked up on side projects because of this:
- Write the listing like a changelog entry, not a billboard. "Does X. Doesn't do Y yet." That sentence ages a lot better than "the all-in-one platform for…"
- Date the screenshot, at least in your head. If the image is from launch week, it's probably lying by now.
- Go back on day 21 and read the listing as a stranger would. Fix the one sentence that's no longer true.
- Treat "here's what changed since launch" as a second launch. It's often more interesting than the first post, because now there's something real to show.
None of this is clever. It's just admitting that a launch is a timestamp, not a verdict.
I'm working on LaunchSignal, a place to publish new products, and this is the part I keep turning over: a listing gets written on day one but read for months. How do you keep yours honest once the launch-day traffic is gone?
Top comments (0)