MVP, Landing or Video?

hi @Ilaiszp, I started to review your MVP website.

The first thing that's a bit jarring (eye strain) for me are the sub-headers, the text is too narrow making it difficult to read. I am viewing the website on a desktop browser with monitor/pixel width of 1920, however resizing to mobile width didn't have an effect on the text styling.

I'd suggest making the font widths greater. Example sub-headers:

• Unleash the Dolphin!
• Unlock product opportunities!
• Democratize feedback insights!
• Early birds, catch the Dolphin – join our Beta!

I think the text width of the main header "Find insights without navigating the sea of feedback." looks good and should be the same for the sub-headers below.

Regarding the content of your website, I'm not very familiar with "product insights" but it's not clear to me what the product accomplishes.

• Are you targeting a particular type of business or just any business?
• What type of data are you looking to provide insights for the customer business?

I kept digging a little deeper and saw some of the feedback posts (e.g. from "Product Manager", "Chief Product Manager", and "Product Lead") about analyzing customer feedback. I later noticed in the main header it talks about feedback, but it wasn't obvious the first time around and still not clear if that's the focus.

My suggestion would be to revisit your header and mission statement to emphasize "customer feedback" aspect of the product. Or if I'm off the mark, identify the emphasis and hone in. Additionally, you could update the "How it works" for Step 2 to say "Upload customer feedback" instead of just "Upload your data".

I'd be happy to help provide suggestions if you can confirm I'm getting warming with my assumptions.

(edit) After browsing other posts, I discovered another post tagged for "Ideas and Validations" (post/building-an-alternative-to-manual-user-feedback-analysis-it-s-10x-faster-and-it-s-a-dolphin-13a0cb09ac) where you explain more about it being "customer feedback" focused. I'm confirmed in my suggestions above. Hope you find help in my suggestions!

@Ilaiszp - Sorry for not answering your question in my first reply.

For the ideas that I've had, I've tripped myself up on this question too. As a builder, I'm always tempted to build an MVP first. Not only that, but I also tend to come up with more technically focused ideas that might be beyond my immediate skills to implement (but don't seem impossible to do).

So for that reason, I'm tempted to build an MVP just to prove my idea would even work. It has gotten me spinning in circles whether to push on the idea validation side or building an MVP to see if I could service the customers in the first place.

(edit) This post might be applicable as it touches briefly on some of your questions: /post/how-did-you-validate-your-idea-before-fully-committing-to-it-484e2dd4d9