Building a product launch platform sounds relatively straightforward.
You need products.
You need users.
You need voting.
You need a leaderboard.
Done, right?
Not quite.
Once I started building LaunchStall, I realized that the interesting problems weren't just about displaying products.
The real challenge was designing the rules around the community.
- Launches need a defined lifecycle
A product can't just be "live" forever in one giant list.
LaunchStall uses weekly editions.
Every edition runs from Monday through Sunday.
Each edition has 10 available launch slots.
That creates a predictable lifecycle:
Upcoming
↓
Launch week
↓
Community voting
↓
Weekly ranking
↓
Past edition
↓
Permanent product page
That sounds simple, but it affects almost every part of the product.
The homepage needs to know which edition is active.
The launch flow needs to know which weeks still have available slots.
The leaderboard needs to know which votes belong to which edition.
And past launches still need to remain accessible.
- Voting needs rules
A voting system is easy to build.
A voting system people trust is harder.
LaunchStall uses one upvote per person per product.
Makers also can't upvote their own launch.
The weekly ranking is based on upvotes.
The goal is to make the leaderboard understandable without requiring people to understand some complicated ranking algorithm.
- Paid visibility shouldn't secretly become paid ranking
This was another important product decision.
LaunchStall has paid plans that provide additional visibility and features.
But paid placement doesn't change a product's actual leaderboard rank.
Paid products can receive priority placement and a "Verified" indication, but the weekly ranking remains based on community upvotes.
Sponsored placements are also labelled.
I think this distinction becomes increasingly important as more product-discovery platforms monetize.
There's nothing wrong with advertising.
The problem starts when users can't tell what is organic and what is paid.
- The launch shouldn't end after seven days
Another decision was giving every product a permanent public page.
The weekly competition creates the launch event.
The permanent page gives the product a longer life.
That means a product can still be discovered after its original launch week.
- I wanted a reason for people to return
A launch platform has two sides.
There are makers.
And there are people discovering products.
If you only optimize for makers, you can end up with a directory full of products but very few people browsing them.
So LaunchStall has a daily streak system.
Members can discover products by upvoting or commenting on three products a day.
Maintaining a streak can unlock rewards that can be used toward things like launches and advertising.
The idea is simple:
Give people a reason to come back even when they aren't launching something.
- Free vs paid
I also wanted there to be a genuine free path.
Free launches require the LaunchStall badge to be displayed on the maker's website.
Paid plans remove that requirement and add additional launch and SEO features.
This creates a straightforward trade-off rather than simply putting the entire platform behind a paywall.
The part I'm still figuring out
The product is live, but I don't consider the system finished.
There are still questions I want to answer:
Is 10 products per week the right number?
How should products be discovered after their launch week?
What makes someone return every day?
How do you encourage meaningful comments instead of empty engagement?
What should the leaderboard optimize for?
Which features actually help founders get users?
Those questions are probably more interesting to me than simply adding another button to the UI.
That's one of the reasons I decided to build LaunchStall publicly.
If you're building a product yourself, I'd love to hear how you've approached product discovery and launch distribution.
And if you want to see what I'm building:
Top comments (0)