Ask HN: Which market testing tools have you found useful?
I admit it: I've made the typical developer mistake more than once of building a product that I thought was "cool, and easy to whip together with Rails." I've said things like, "I'm sure that we'll be able to find users for it after we can show it to people."
I'm finally over that mentality, and from now on I will only build products after collecting thorough data that demonstrates a market need. So, I'm wondering what tools hackers here have found especially useful for finding markets and testing viability of digital products (web services, apps).
6 comments
[ 4.6 ms ] story [ 33.3 ms ] threadBTW- only building apps where there is a market need is a surefire way to stifle creativity and lose interest. Start up a project on GitHub for fun that does something cool and do that to get your creative juices flowing. Then don't abandon it. There was a study a few years ago that found that the majority of "successful" free or open source projects have a developer associated with them that only started that one or two free or open source projects (ever).
In general your time should be spent: 50% problem team - finding more facts about the problem you are solving. 50% solution team - building a very minimal product(aka mvp) based on current data problem team has discovered.
This kind of work should get you into a feedback loop where you not only research but also test - these two together should make you move faster and wiser.
feel free to ask more.
Wouldn't that require a lot of insider information as well as connections within those companies?
I guess my question was a lot less daring - how would one approach task of finding problems/needs within reasonable reach of his own social or geographical vicinity, such as identifying a small-to-medium businesses niche and approaching those, based on the assumption that it's easier to approach this kind of businesses.
Thanks!