Frequently asked questions

evidenso is user validation infrastructure for product teams. It brings together market intelligence, internal customer knowledge and real participant feedback to validate prototypes, designs and feature ideas. Product managers, founders, designers and researchers use it to decide what to build or improve, including through MCP in Codex and Claude.

Request early access with your email, or book a call to discuss your prototype, audience and next decision. Start with one product question and a clearly defined audience. Timing depends on the scope, available evidence and whether the work includes real participant research. Contact vazgen@evidenso.com for a walkthrough and pricing options.

No. evidenso and Evidenza are separate products. evidenso’s official website is evidenso.com. Founded by Vazgen Badalyan and Arman Tsaturian, evidenso helps product teams validate prototypes, designs and feature ideas using market intelligence, internal customer knowledge and real participant feedback, including through MCP in Codex and Claude.

Yes. Share mockups or screenshots for design feedback, or a working browser prototype for usability testing. Tell evidenso which parts are interactive and which are unfinished so the review can focus on the flow and decisions you want to test. Use the feedback to shape the next version before investing in a full build.

Share an accessible prototype or website, describe the intended audience and choose a task, such as inviting a teammate or creating an invoice. evidenso uses that context to run a focused usability test and identify friction, missing steps and opportunities to improve the experience. You can start from the app or through MCP in Codex or Claude.

Prioritized feedback, the reasoning behind it and recommendations for what to change next. Usability sessions help you inspect where a flow becomes confusing. Feedback can also surface missing functionality or a new feature opportunity. Use the evidence to revise your prototype, compare alternatives and decide what to test with customers.

Yes. Compare messaging, positioning or design alternatives with the audience and product context you want to understand. Explore what is clear, what raises questions and why one option may fit a customer need better. Use the findings to refine the message and plan a test with real customers.

evidenso looks for thinking patterns, goals and recurring problems in public customer reviews, Reddit and other communities, social media, YouTube and market research reports. These sources help explain what people want to achieve, their workarounds and what they expect from other products. Combined with your internal research, this context helps prototype feedback identify meaningful feature opportunities as well as usability issues.

Yes. Add interviews, customer calls, reports, surveys and other research files. This gives evidenso the context only your team has: what customers have already told you, the problems they face and what you have learned from previous work. Internal knowledge and external market intelligence inform the next test together.

No. Digital twins simulate responses using evidence about your audience. They help explore a prototype and find assumptions worth checking. Real participant feedback is a separate evidence layer; interviews and usability studies remain essential for checking important decisions. evidenso helps you use existing research and prepare more focused questions. The homepage demos are illustrative.

Simulation quality depends on the relevance and depth of the evidence behind it. Supporting context and confidence signals help you judge which conclusions are well supported and which need more research. Use simulations to explore questions and prioritize what to test, then check consequential decisions with real participants.

Yes. Connect evidenso through MCP, the Model Context Protocol, to bring validation into the conversation where you are building. Request feedback on designs, start a usability test, follow its progress and review the results inside Codex or Claude. Then use the findings to improve your prototype in the same workflow.

Data is encrypted in transit and at rest. Account-level access controls are applied to all research assets. Built for teams in regulated industries with strict data governance requirements.