5 ms·
The most important lesson to learn from this successful "launch" is that they iterated on their product for seven months of beta before officially launching it.
by chatmasta 12y ago
The most important lesson to learn from this successful "launch" is that they iterated on their product for seven months of beta before officially launching it. How often do you see "Show HN's" of half-finished side projects with no actual customers? All the time. And the feedback is rarely good. Even if it is, the percent of qualified leads will likely be drastically lower than if you release a refined product, since people will quickly realize its rough state and promptly forget about your product.
The lesson is here to chillllll. Wait. Hold on. You don't need to "launch" your product as soon as v1 is deployed to Heroku. HN, product hunt, and Techcrunch will still be here in seven months. Don't waste your window of opportunity for "launching" by announcing an extremely rough, underdeveloped product. Hold out until you have customer feedback and have refined it sufficiently. Then, the leads you get will be infinitely more valuable.
- hayksaakian 12y ago> Hold out until you have customer feedback and have refined it sufficiently. Then, the leads you get will be infinitely more valuable. I think what you're getting at is suggesting that people do a soft launch or a private launch of their minimally viable product. (I agree with this). You can't get "customer feedback" unless you have "customer(s)".
- lsc 12y ago>You can't get "customer feedback" unless you have "customer(s)". Yeah, but my experience is that the feedback from people that are actively trying to help you is less valuable than the feedback of people telling you what they actually want and would pay for. It's the difference between "I would pay for X" and "I think that other people would pay for X"
- dang 12y agoI know you're talking about product launches, but you reminded me of something I've been wanting to clarify about Show HN. I hope it's ok if I share it here. It's not exactly off-topic, since Show HN is definitely for product launches—but it's for other things too. The way Show HN has evolved over the years, the bar for it is naturally low. Show HN is for something you've made that other people can try out and talk with you about in the thread. That can be anything from a first project or weekend hack to a feedback-honed product like you've described above. The only rules are (a) you made it and (b) it works. By "it works" I mean that it isn't a landing page or an email signup or a fundraiser, but rather something other people can play with and give feedback and ask questions about. That definitely includes new products, but also other things. Who knows what people might come up with! It just has to be interesting. A risk with setting the bar too high is that some users will feel like contributing isn't for them. We want to avoid that. There are many talented people who maybe haven't done anything of their own yet, or haven't yet shared what they've done, or who suffer from that curse of our field, impostor syndrome. It's painfully easy to look at the polished work of others and think, "I could never do that". One reason we want Show HN to be welcoming to all levels of work is so there will be plenty of examples where people think, "I could do that". Not as in "meh, that's nothing," but in the DIY spirit of "hey, me too". But the main reason is that many kinds of things—including seemingly trivial things—can be interesting. There's a secret relationship between the high and the low. They thrive together. Masterful paintings are wonderful but first sketches are interesting too, especially in a workshop or a studio, which is the kind of place we want HN to be. Besides, first sketches have a way of turning into something masterful later. Most won't, but some will, and we love it when HN helps that happen.
- rl3 12y agoMaintaining control of your launch is important as well. I recall seeing discussion on Product Hunt recently where founders were worried about their product being submitted without their knowledge, effectively launching them before they're ready in a beta/soft launch state. Obviously that would be bad, but it's potentially even worse, because (as far as I know) you only get one shot at Product Hunt. If this has actually happened or not, I'm not sure. There were a lot of founders worried about it though. Per the discussion, I believe rrhoover said they're looking into ways to address that, and the prevailing consensus was to lock down your beta. Some other ideas were additional provisions in beta tester NDAs, and Product Hunt implementing some type of blacklist system to prevent premature submissions. Personally I would just have a bare minimum public-facing website during beta, though it seems that this would inhibit your ability to get beta users unless you're either well connected or your product is hyped. Of course, this same phenomenon has been happening with HN for years now, the difference being it's much more rare because HN isn't laser-focused on new products, and its submission volume is massive.
- notastartup 12y agoyou have a valid point here but isn't the whole purpose to get the product in front of people's eyes as soon as possible to validate?