[enraged_camel]

Yes, but asking someone how much they would pay for it takes them almost all the way, mentally, to actually paying for it. You're basically asking them to make a verbal and very informal commitment, but that's enough to make most people think about it seriously (as opposed to saying "omg I love it!!!" just to be nice).

[wpietri]

That's not my experience; I now avoid asking hypotheticals because the results for me have been very unreliable.

I'm certainly unreliable that way. There are a number of Kickstarters where I've said, "OMG I'd pay for that!" But if I come back to it a couple of days later, I'll never actually click on the signup button. I'm even worse with things like this in person. I don't like disappointing people, so I'll try hard to find the most positive thing to say about their product.

When interviewing, I might ask people a question like, "What's a fair price for X?" But that for me would be more about the follow-up question: "How did you pick that number?" An insight into what they see as equivalent products, related value propositions, or personal value metrics would definitely help me think about pricing.

[tchock23]

Very good points here. The prevailing advice for entrepreneurs from folks like Steve Blank is that you must "get out of the building" and be physically in front of customers to interview them, but in my experience 95% of customers would never tell an entrepreneur their product/idea sucks right to their face.

As for pricing, I've found that asking people "What do you think a fair and reasonable price for X would be?," followed by the follow-up as to why, is the best way to ask about pricing (in a qualitative setting, at least).

[wpietri]

Thanks!

I think Blank is entirely right. But you have to be tricky.

At my last company we did user test every Tuesday afternoon. When seeking subjects, we looked like a research firm, not a product company. When they arrived, there was no company name on the door. The interviewer would start out asking about a variety of products to get a baseline; ours would just be one of several discussed. Eventually, because we spent more time on our stuff, maybe half the people figured out that one product was ours, but by then we generally had enough honest opinion.

[enraged_camel]

>>That's not my experience; I now avoid asking hypotheticals because the results for me have been very unreliable.

The point in this context is that, while it may still be unreliable, it would be more reliable than simply asking if they like your product. And it is the best you can do, since no one is going to actually pay for a product that doesn't exist yet.

[wpietri]

People pay for products that don't exist all the time. That's what contract software development is all about, for example. Ditto vaporware, Kickstarter, and "coming soon" features of existing products.

And, as mentioned elsewhere, people can think they are about to pay for a nonexistent product. Once you have proven willingness, there are a variety of ways you can finesse the issue of not actually having a product.