(public).sospep.subjects ~ view article ~ why-no-one-wants-to-buy-my-app

<h1 style="text-align: center;">title</h1>
<h2>[WHAT]</h2>
<ol>
<li>]&nbsp;</li>
</ol>
<h2>[WHY]</h2>
<ol>
<li>]&nbsp;</li>
</ol>
<h2>[WHERE]</h2>
<ol>
<li><strong><span class="comment"><span style="color: #000000;">&gt;Why do people want everything for free when other have put a lot of effort on making it?&nbsp;</span></span></strong></li>
<ol>
<li>I don't think that's the problem. People will pay if what you build solves their problem. More specifically, they'll pay if they see that what you build solves their problem.</li>
</ol>
<li>
<p><strong>Before building, you should check:&nbsp;</strong></p>
</li>
<ol>
<li>
<p>] Do they have a problem?</p>
</li>
<li>
<p>] Do they know they have a problem?</p>
</li>
<li>
<p>] How much of a problem is it for them?</p>
</li>
<li>
<p>] Who, exactly, has the ability to act on this problem?</p>
</li>
<li>
<p>] What language do they use to describe the problem?</p>
</li>
<li>
<p>] Do they have any requirements that aren't obvious to me? Can I incorporate them into what I'm building?</p>
</li>
</ol>
<li>
<p><strong>If this sounds like marketing, it is, but it's the good sort. <br /></strong></p>
</li>
<ol>
<li>
<p>] Building something people don't actually want is a perennial problem.</p>
</li>
</ol>
<li>
<p><strong>Rather than trying to sell what you have, figure out what they want. Then you'll know whether to:</strong></p>
</li>
<ol>
<li>
<p>] Change who you're talking to</p>
</li>
<li>
<p>] Change how you're talking about the product</p>
</li>
<li>
<p>] Modify the product</p>
</li>
<li>
<p><span style="color: #000000;">] Abandon ship</span></p>
</li>
</ol></ol>
<h2>[WHEN]</h2>
<ol>
<li>]</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li>]</li>
</ol>
<h2>[HOW-TO]</h2>
<ol>
<li>]</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>]</li>
</ol>
<h1 style="text-align: center;">&nbsp;</h1>

~ view article ~ Chapter] ch-902-strategy FROM [ Book] startup-guide IN [ libraries] business