zhongyongxu

Strong agree — clicks > surveys, and behavior > opinions.

The gap I'm trying to fill: before you have the live MVP (and before you invest in heatmaps/recording infrastructure), how do you know which workflow is worth building?

Video prototypes are the "pre-MVP" behavior test — show the experience, see if they click "I'd pay for this" vs just "interesting."

Curious: When building UXWizz, did you validate the "self-hosted vs cloud" decision with video prototypes, or did you ship and learn from early user behavior?

Feels like your tool captures the truth post-launch, mine tries to predict it pre-launch. Complementary approaches.

Great questions—you're right to ask.

1. Who am I: jone, ex-tplink engineer, spent 3 months building a feature that got 0 sales. Painful lesson. Now trying to solve that for others.

2. Expertise: Not an expert in video/sales. That's why I'm talking to people like you first instead of building a platform. Currently learning by doing—first 3 validations are free in exchange for brutal feedback.

3. Fraud: Valid concern. My current process: - Typeform/Google Forms (you own the raw data) - You pick the channels (your Twitter, your Reddit, your email list) - I screen-record every response coming in - Deliverable: raw CSV + my analysis, not just a "trust me" PDF

   You're right that "public" without transparency is worthless. 
   What would make you trust the data?