Key points:
* Learn to be ruthless about throwing away work
* Reduce your scope
* Use patterns and keep your code organized
* Build what people are asking for
* Learn to be ruthless about throwing away work
* Reduce your scope
* Use patterns and keep your code organized
* Build what people are asking for
If you have any product at all and a decent website you can hopefully at least get people to talk to you and they will ask if your product can do X,Y,Z. Even if your product is pretty basic you can at least tell them that you would like to learn more about X,Y,Z so that you can build that and be ready to say yes to the next potential customer who has the same question. This is probably a better approach than calling up CEOs and asking "What are your problems?" They have 1 million problems. You need to start with a MVP and ask what problems they have which seems somewhat related to the MVP