News for hackers. Stuff that matters.
Re:Sell it before you build it by paraschopra on Sunday March 29, 2009 @12:15AM (#537097)
I sort of find this idea quite weird. In this case it is interesting to note they already have a product, all they are doing is pre-selling a pro version. But when you try to apply this strategy to a new product being created, your focus often gets diluted. And if you are asking what customers want, you risk to get overwhelmed by their requests. So, it is better to sell after you have a actual (no matter how minimal) product. Frankly, I don't see a point in pre-selling, do you?
Re:Sell it before you build it by skmurphy on Sunday March 29, 2009 @02:45AM (#537180)
The question is what is the simplest or most basic product that people want to buy. If you don't merge all of the feature requests, but pick the smallest subset that prospects tell you that they will pay for, you are less likely to get overwhelmed/diluted. Once you know what the minimum feature set is you are more likely to be able to develop it, and if you have pre-sold it there is much less risk than you have developed something that you love that no one wants.

"Frankly, I don't see a point in pre-selling, do you?" If you have ever developed something that no one (or too few) people wanted to pay for you may get more cautious about developing something without assessing customer buying interest first.

Re:Sell it before you build it by rjurney on Sunday March 29, 2009 @01:33AM (#537146)
Yes. You'll build the wrong thing. Something nobody wants.
Re:Sell it before you build it by paraschopra on Sunday March 29, 2009 @01:37AM (#537148)
Or you would never build the right thing, because all your time is consumed in selling the thing that is never made.
Re:Sell it before you build it by rjurney on Sunday March 29, 2009 @02:26AM (#537169)
You aren't just selling, you are learning.

You are very unlikely to get it right based on a hunch without multiple iterations with real customers. That means that you will end up iterating whether you build it or not. So its best to first iterate without building: you get more iterations and less wasted development that way.

As the interview explores, that doesn't mean building nothing, but it does mean validating an idea first and foremost.

I understand that this can be frustrating for a developer. We tend to think, 'if we build it, they will come' and we don't like sales. But personally I've wasted too much time building elegant software... nobody much wanted, to build new stuff without validating it first.

If you "don't get" this interview, I would suggest a second listen. It contains a critical lesson.

Re:Sell it before you build it by HeyLaughingBoy on Sunday March 29, 2009 @10:04AM (#537344)
Worst case is you realize you don't have time to finish it quickly, so you buy it from someone else and sell the customers that to keep them happy while you work on the 'real' product.

I realize this approach will probably be hated on by the HN community, but for a certain set of products, it makes perfect sense.

I'll add one more thing:if you guys were selling hardware, you'd have a much greater appreciation for this technique!