A couple of ideas:
1 - Fake door concept to measure intention before building it
2 - Interview customers, better to speak than surveys so you can get the details
3 - After launch, look at Analytics and users recording to understand what they did
We can validate our idea through market research, customer interviews, or by testing a minimum viable product (MVP) with a small group of target customers.
"Just ship it" kinda works, but what I find is you're gonna build 100 apps and out of that, 5 to 10 get successful. I find that wastes time a lot!
What I do instead is listen out to people complaining about a feature (or lack thereof) in a forum or discussion. If it's a problem that frustrates people frequently, then I would ask two questions:
1. "Can I build a tool to solve this problem?"
2. "Would someone with this problem buy my tool to solve it?"
The second question can be answered by talking to those people to see if they would be interested in a solution you build.
There is no single validation to all products. The closes is user adoption, and that can only be determined once you ship it. You tell your idea to 1000s of people and they will say wow, but non of these 1000 people would actually know if they are actually going to use it or not until they get hands on experience. So once you have your MVP ready, ship it and talk to people. Listen listen and listen. Understand what users are saying and what they are not saying. Thats how you validate it.
Validating a SaaS product idea is like figuring out the perfect pizza toppings - you need to test different flavors with your target audience to see what they crave the most!
Fusionos.ai