A working prototype is not the answer yet
A polished demo can still leave a first-time user looking for the wrong button, missing the point of the screen, or abandoning the task you thought was obvious. You are close to the build. They are not. That difference is useful before the next commit gets bigger.
Fiuto gives someone outside the project a task to complete and room to explain what happened. You get the behaviour and the reason together: where they went, where they stopped, and what made sense to them.
From prototype to evidence before the next build
1. Name the decision
What would change if you knew the answer: the first screen, the onboarding path, the pricing explanation, or which direction to keep?
2. Turn it into a study
Start in Fiuto or ask your connected coding agent to create the study from the same session where you built the prototype.
3. Share it with real people
Send the link to your own customers, waitlist, community, or the people you want to learn from.
4. Read what they did and said
See whether people could complete the task, what they noticed, and the words they use to explain the friction.
5. Build the change that earns it
Send the evidence back into the next build instead of asking the agent to guess with you.
What should you test before another build?
Can someone finish the first task?
Give a new person the job the prototype is meant to make easy. A prototype test shows whether they can get through the flow and where they lose the thread. Explore prototype testing.
Do they know where to click first?
When the first move matters, show the screen and ask where they would go. A first-click test catches the wrong turn before you build the rest of the path. Explore first-click testing.
Which direction should survive?
Show the alternatives you are debating, ask people to choose, then ask why. A preference test turns taste into a decision you can inspect. Explore preference testing.
Work from where you build
Start in the web app
Describe what you need to learn, review the study, launch it, and share the link. Use this route when you want to work directly in Fiuto.
Start from your coding agent
If you are already building in Claude Code, Codex, Cursor, Lovable, v0, Replit, Bolt, or another MCP-ready tool, connect Fiuto and ask the agent to create and launch the study from the same working session.
The two routes meet in the same study. Start where the work is moving today, then use the other route when it helps.
When tracking fits an agent-built browser prototype
If the prototype runs in a browser and your agent can edit its code, Fiuto tracking can capture what respondents did inside the prototype alongside their study answers. That is useful when the route through a live prototype matters as much as the reaction afterwards.
Tracking is optional. For a static screen, a click or preference test may answer the question more directly. Learn when prototype tracking fits.
Keep exploring
Frequently asked questions
01Can I test a prototype built with Claude Code, Codex, Cursor, Lovable, v0, Replit, or Bolt?
Yes. If your builder made a web prototype, use Fiuto to turn the question in front of you into a study, share it with people you invite, and see what they did and said before the next build.
02Does Fiuto recruit test participants?
No. Fiuto does not run a recruited panel. Share the study with your own customers, waitlist, community, or the people you want to learn from.
03Can I run a prototype test from my coding agent?
Yes. Connect an MCP-ready coding agent to Fiuto, then ask it to create and launch a study from the same session where you are building. You can also start in the web app and use the agent later.
04What does prototype tracking add?
For an agent-built browser prototype whose code your agent can edit, tracking adds what respondents did inside the prototype alongside their study answers. It is optional; use the method that answers the decision in front of you.
