4 ms·
It's a little backwards. What you're proposing is a little like building a house to see if a customer likes enough to buy it, without letting them pick a layou
by j45 14y ago
It's a little backwards.
What you're proposing is a little like building a house to see if a customer likes enough to buy it, without letting them pick a layout/blueprint they like, or the conversation that goes into the blueprint of ensuring the customer would want the house.
First, find a target customer. Learn what their painpoints are. See if they're willing to pay for that painpoint. Then, build something to sell to them. This allows you to explore multiple hypotheses, instead of going to them with your idea that ends in a yes or no. By involving customers from the get go, they are more engaged, invested and committed, especially if it could make their life easier.
You will find that this path will reveal to you a completely different set of priorities and pain points that would be small to do, but have a huge impact, which is a great basis for an MVP.
By doing it doing it in reverse, you're hoping you take a stab at it and it pans out, at the expense of not doing the idea development upfront before writing a single line of code. The best way to "market" is to do it as you explore what to do and build a mailing list. Share your journey through a blog focussing on the life and business problem you're solving (not your code or tech breakthroughs).
Learn about your customer instead of guessing your way through what someone might want. Having domain knowledge in a field that you build something for could be helpful but you still have to validate, first, if anyone will pay for it. That's the scary, and what makes it a real business (self sustainable and makes money for you).