Hacker News new | past | comments | ask | show | jobs | submit login

This is a common mistake: building a product based on assumptions, and not on the market's demand. I've learned not to add a feature before I have someone who paid an advance. Secondly: your product might be to overwhelming and doing to much; experience has thought me that complicated products are a though sell. Try to reduce it to it's most basic use-case, and sell that (a simple app that doesn't require any explanation at all). Once you have paying customers you'll be able to upsell by offering your more advanced features. People are reluctant to change, so you need to expose them gradually.



>This is a common mistake: building a product based on assumptions, and not on the market's demand. I've learned not to add a feature before I have someone who paid an advance.

I first came across this sort of advice here:

The Montana Mogul: RightNow CEO Greg Gianforte (Part 1)

http://www.sramanamitra.com/2008/07/31/the-montana-mogul-rig...

Interesting story. RightNow was later sold to Oracle, IIRC, for a good amount.

Greg used a similar technique to what you advise.


The part of the interview series about Brightwork (Greg's first startup) and their telesales process and why McAfee acquired them, is also interesting.


Thanks for the tip!


You are right. I am currently building another product, which is lite version of what I have and which is applicable to broader market: not just wine farmers, but all farms and consttuction companies.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: