Rapid Prototyping for product ideas
Turning ideas and concepts into clickable, testable prototypes, in Figma or directly as working code, fast enough to learn from and concrete enough to convince stakeholders, investors, and your own team.
What rapid prototyping actually is
A prototype is not a finished product. It is a working artifact that lets people experience an idea before anyone commits engineering hours, hiring decisions, or budget to it.
The point is not to look polished. The point is to be specific enough that the right conversations can happen: about features, flows, priorities, and assumptions. A good prototype makes vague ideas concrete. A great prototype reveals what the team did not know it disagreed about.
Prototypes are built in Figma or directly in code. For flows and structure a clickable Figma prototype is enough, but as soon as real data, calculations, or animation come into play, I build working prototypes in HTML, CSS, and JavaScript. Both can be shared via link and tested with users.
Clickable prototype or coded prototype?
A clickable prototype links screens through hotspots, so clicking a button takes you to the next screen. For most questions about navigation, information architecture, and sequence that is enough, and it is quick to build, a simple idea even in a day.
It reaches its limits when the interface changes depending on input. In the reasoning explorer for the washing machine, temperature, spin speed, and the explanation change with every item that goes into the drum. In Figma that would have been dozens of screens, as a coded prototype it was part of one working day, and the logic behind it is real.
Which approach fits is settled in the kick-off. As a rule of thumb, Figma is enough as long as the question is whether users find their way. When the question is whether they understand what the system does, it usually takes code.
When rapid prototyping fits
- An idea exists but no one is sure yet how it should actually feel or flow
- A team needs to align on a direction before development starts
- A pitch needs something more tangible than slides
- Stakeholders disagree about features and the disagreement is hard to resolve in conversation
- An MVP scope needs to be validated before it is built
- An existing concept needs a sanity check through user feedback
Not the right phase when the question is "should we build this at all" — that comes earlier, in strategy and research. And not the right phase when the product is already live and the goal is iteration — that is what UX audits are for.
What you get
Depending on the engagement:
- Clickable Figma prototype or working coded prototype with realistic interactions and content
- User flow diagrams documenting the key paths
- Component structure compatible with developer handover
- Annotations explaining design decisions and open assumptions
- Optional: a brief recording walking through the prototype for async stakeholder review
How a project typically runs
A typical rapid prototyping engagement runs between one and three weeks, depending on scope:
- Kick-off and scoping (half day to one day): clarifying the idea, the audience, the assumptions to test, and the deliverable format.
- Concept and wireframes (two to four days): translating the idea into structure, before visual design takes over.
- Prototype build (three to seven days): clickable Figma file or working coded prototype with content and interactions.
- Review and refine (one to two days): stakeholder feedback incorporated, prototype tightened for its purpose.
For simpler ideas, a clickable prototype can land in a single day. For complex multi-screen products, two to three weeks is realistic.