1
0 Comments

Scratching your own itch or build what people want.

As a founder am sure we all heard to build something that the user needs and avoid build it and they will come strategy. But logically thinking if you have a problem that none of the existing solutions solve then what do you do.

Sure the simple next step would be to make an MVP landing page and see if others have the same problem. But what if the key benefit of your project is related to the UX of the app.

For example what if you find all the mailing services complicated such as MailChimp and Convertkit and you think this is not up to the level of an average non-marketer level and you think you can dumb it down and make the UX 10 time better. Again this is just an example.

In this case your not validating if the market needs a mailing service startup cause you know there are 100's of them, so the market exists. you are trying to solve the problem of complex UX as a user of the existing solution.

So what do you do now? Make the app. Make the mockup or wireframe and get feedback?

The right answer is always "it depends". :-) But for me its to go ahead and build it, not because once I build it the users will come but because I seriously believe there is no end to improve to existing products.

All startups have an advantage existing incumbents don't. You can pivot, change, and adapt. You don't have to the existing model you need to follow and people like new things. Change is the only constant.

What every solution your building, the journey will be long and tuff. Having it solve your own problem will make it a bit more comfortable.

Presently am working on a crypto trading scanner (tradeplan.co)after having lost some money due to a lack of such a tool during early 2018. Do check it out if you trade crypto or interested in crypto.

Cheers,

on May 29, 2020