I know successful (>10M revenue) companies who have mocked up a brochure and sold it this way. Their thought was "if they don't bring out a credit card right away you aren't solving a pain, you dont have a product".
I know successful (>10M revenue) companies who have mocked up a brochure and sold it this way. Their thought was "if they don't bring out a credit card right away you aren't solving a pain, you dont have a product".
Consumers/users ALWAYS get screwed in those type of scenarios. I don't believe in taking risks with other people's money.
1. Create mockup/demo/realistic brochure/non-functional physical prototype 2. Go to your target market. Count number of targets 3. Try to sell them the product at the target price 4. Once they hand over their credit card etc, just hand it back. 5. Tell them thanks very much for their support, but this was a test so you can make sure the market wants the product, if they want we can contact them when/if the product is ready. 6. Do your stats. What proportion of the target market you sampled bought the product. Extrapolate to the estimated population to get an idea of how many units you can sell. [rinse and repeat to make your product more attractive to the market]
It's the only way I have ever heard of turning a snake-oil, soothsayer business plan into one that can statistically show the uptake of your product in the market.
I refuse to believe that there is no other way of conducting a market study other than resorting to sneaky, dastardly little tactics. Why? because there ARE other ways.
Also, nice strawman, I obviously did not counter with "conduct NO market studies/surveys" - I came back with "that's dishonest and I don't believe in it".
Funny, how I have set up services (granted, not products) that made me money and I did not have to resort to cheap little deceptive tricks.
I would rather have a product I can be statistically confident is going to sell because users have wanted to pay for it. There's no debating whether it's right for the market or not.
Thanks for the discussion by the way, this is fun :). If you do have a better way I'd love to know.
I am seriously curious to know how many times you have seen that work. I would think that many people would resent the tactic and retaliate by not purchasing your product, or they would lose their trust in you (and rightly so, you done suckered them once) and therefore respect. It's interesting to note how many thousands of products have been researched, developed, and taken to market to great success, without deception tactics.
I guess we will agree to disagree on the ethics. I personally don't find it any different than deceptive advertising that is used in the majority of sales channels worldwide, the many deceptive claims of products overstating the benefits, understating negatives etc.
I simply refuse to do it because others are, and believe that successful market studies can be carried out without deceptive tactics.
This general attitude and outlook on my behalf actually mostly derives more from sheer pride than from any sort of assumed moral superiority - I simply can't sleep at night if I think that I applied or relied on anything other than my own merit to achieve something, and deceptive/slick tactics make me feel as though I cheated because I was unable to do it the hard way . . . that kind of thing.
I will close by conceding that I may be wrong about this, however, I might also just end up identifying more user needs in a highly accurate manner with my approach, which is conducive to even greater profits.
How dissapointing. I have seen PHP do better than this. This is depressing.
I had/have the same aversion to selling things that don't exist that you have. But honestly, I think that the next time I do a startup, I'm going to do it that way. I get really sick of speculatively building things that nobody wants. Why not make sure they want it first and then build it?
Plus, two of my favorite startups - DropBox and RescueTime - both used this approach (though perhaps with a little less dishonesty - they clearly marked it "demo"), and their products are better for it.
Often times first thing I want to do is jump into code, and it's the last thing you should be doing. Proving the market is critical, and the only way you can prove it exists (for most companies) is to fake sell.
When people tell you, I would buy it if it had this feature, they are often lying. Unless they are willing to pony up their credit card, you haven't solved the problem imho.
I think that the objective is a market study, for which I believe there are some tried and tested methods, although it occurs to me that in this field those may not apply as so many other things, however if that is the case, then I believe "how to find out what the users want without selling vaporware/other questionable tactics" is a worthwhile problem to tackle in and of itself.
Selling vaporware is to me similar to using users as unwitting beta testers, I don't believe in it, I think we should be upfront like the examples you cited: if it is a beta let people know, if it is vaporware, let people know, if it is a demo, let people know.
In my opinion it's the ethical thing to do, not just for you but for your users. Why bother creating a product if it's never going to get traction in the market? You won't be able to afford to support it well, and it won't develop into a great business unless you get significant revenue. This is more unethical for the users, as you'll have to fold or let is stagnate. Why risk it?