Skip to main content
← All Services

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:

  1. Kick-off and scoping (half day to one day): clarifying the idea, the audience, the assumptions to test, and the deliverable format.
  2. Concept and wireframes (two to four days): translating the idea into structure, before visual design takes over.
  3. Prototype build (three to seven days): clickable Figma file or working coded prototype with content and interactions.
  4. 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.

Frequently asked questions

What does a rapid prototyping project cost?

It depends on scope. A single-screen prototype for a focused idea can be done in a day, billed as a fixed package. A multi-screen prototype with stakeholder iterations is billed by day rate × estimated effort. First conversation (30 minutes) is free and includes a rough estimate.

How much detail does the prototype need?

As much as the next conversation requires, no more. A prototype for an internal alignment meeting can be lower fidelity than one for a user test. The fidelity is set by the purpose, not by ambition. Over-polishing is the most common mistake.

Do you work from existing wireframes, or do you start from scratch?

Both. If wireframes or sketches exist, they get refined. If not, they are produced as part of the engagement. The starting point matters less than getting to a clickable result quickly.

Can the prototype be tested with real users?

Yes. Figma and coded prototypes can be shared via link and work in browsers and on mobile. They are suitable for moderated and unmoderated user testing. If a full research engagement is needed alongside, that can be added.

What happens after the prototype is done?

Three typical paths. One: the prototype confirms the direction, and the team moves into development. Two: the prototype reveals problems, and there is iteration before development starts. Three: the prototype is used as a sales or fundraising artifact, and development comes later. Most engagements include a handover document so the prototype can be picked up by the next team.

Can you also build the final product?

I do not build production-ready products, that takes an engineering team with testing, infrastructure, and maintenance. What I build are working prototypes in HTML, CSS, and JavaScript that behave like real software and serve as a reference for implementation, plus design specifications and component documentation. For implementation I work alongside the client’s engineering team or recommend developers from my network.

How is AI used in the prototyping process?

In prototyping, AI mostly does the building. Concepts, sketches, and Figma designs become a working prototype with Claude Code, which I steer and correct step by step. For the fragrance visualization that meant around thirty discarded concepts before one held up. Decisions about what gets built, how it should behave, and when it is good enough stay with me.

Do you sign NDAs?

Yes, NDAs are standard. All intellectual property from the engagement belongs to the client. With approval, the work may be used as a portfolio reference and the client name mentioned.

Ready to make your idea testable?

Book a 30-minute conversation to talk through your idea and what kind of prototype would actually move it forward.

Get in touch