I'm Zviad, founder of Signify, a platform that helps people e-sign and manage documents.
We're preparing for our first launch here: AI chat that lets you literally talk to your documents. It explains legal jargon, answers "what am I actually signing?", no stupid questions, ask whatever you need.
Until then I'm around, exploring and supporting interesting launches here.
Everyone says to test demand before you build. We didn t. We built the product first, like a lot of people do, and only afterward found a fast way to test the part we d skipped.
What we re testing now isn t really the idea - it s the positioning: Does someone landing on our page understand what the product is? Does the offer make sense? Does the pricing feel right? We use a paid research panel (Prolific, though there are others like Wynter, PickFu and Lyssna) to put the page in front of people who match our audience. They read it and answer a short questionnaire: What do you think this does? Do you understand it? Does the price seem fair? You pick the audience, they review, you pay per response. A few hours to prepare, results back the same day.
It's been most useful for catching where people misread the offer - something our existing users can t really tell us, because they already understood it well enough to sign up. We ll use this approach for landing page changes from now on, and we ll run these tests before building the next thing rather than after.
How do you test whether people understand your product or your idea before you commit to it?
CookieYes
