What should I do next? Just keep building or stop and seek validation firstly?

Zhao Naomi
4 replies
Hey hunters, I recently working on a product called Demokit. It provides a library of product demo videos to indie hackers and startup teams to watch excellent videos of different types and analyze the video scripts through AI technology, enabling users to learn about the production ideas of these videos, providing inspiration for their own product demo video creation, reducing the difficulty of video production and improving efficiency. My current confusion lies in whether just providing users with text scripts for reference can really bring them value. I'm thinking if I could provide a simple web-base video editor and present the scripts as video templates, allowing users to directly edit them, would it be better? However, doing so would extend my development cycle, which makes me uneasy. I don't know if this is meaningful or not, and I'm afraid that users don't actually need it and I've spent too much energy on it. And personally, I prefer to use tested video scripts as a reference and my familiar video editor to complete the video creation. I need to understand the opinions of ohters in order to further improve and develop this product. I hope this product can bring value to indie hackers and small startup teams, and I need your feedback and suggestions. Thank you for your time and help. If you have any ideas or suggestions, please share them in the comments section. I would really appreciate your feedbacks on what to do next. Thank you!❤️❤️

Replies

Maël Harnois
I'd say the hard part is to not overthink it. What you want is to have user's feedback ASAP. You could even launch your product on PH with just a landing page, in order to seek validation / early feedback and collect few emails of people you could interview. The last thing you want to do is over engineer the solution - here your added value lies in creating the script, so a V0 / MVP could simply be a tailor made script for a specific use case the user would describe. So you build it simple, make it cheap and see how people react to it.Then based on feedback, upgrade with features (like video editor etc), rise the prices, launch again. 🔁 That's how I'd proceed :) Enjoy building !! 💪
Zhao Naomi
@maelus Thank you very much for your sincere suggestions, they have been very helpful for me. You are right, I should build it simple first.
Ruby Bryant
I've developed a few features for my app and am unsure if I should continue building or take a pause to seek validation, so I'd love your thoughts on striking the right balance between innovation and feedback!
Zhao Naomi
@rubybryant555 Actually this is something I often struggle with. listening too much to user feedback can make my product too niche-focused, which can eventually lead to monetization difficulties and failure. Perhaps we should establish a maximum feasible product boundary line first, so we can identify which functions we should not develop, unless users vote for them with coins.