Before building, you should check:
] Do they have a problem?
] Do they know they have a problem?
] How much of a problem is it for them?
] Who, exactly, has the ability to act on this problem?
] What language do they use to describe the problem?
] Do they have any requirements that aren't obvious to me? Can I incorporate them into what I'm building?
If this sounds like marketing, it is, but it's the good sort.
] Building something people don't actually want is a perennial problem.
Rather than trying to sell what you have, figure out what they want. Then you'll know whether to:
] Change who you're talking to
] Change how you're talking about the product
] Modify the product
] Abandon ship
ID: 2784
NAME: why-no-one-wants-to-buy-my-app
DESCRIPTION: Developer builds solution to problem but no one is buying? what happened?
AUTHOR: article.author/s
EDITOR: article.editor/s
PUBLISHER: article.publisher/s
STATUS: Write
PRIORITY: 0
OWNER ID: 75