Question to test
We define the question that justifies the prototype: a path, an interaction, or a new way of showing content.
Services › Web design and development › AI prototyping
AI prototyping
We build clickable prototypes to discuss paths, interfaces, and features in concrete form before committing to full development.
AI speeds up exploration and makes it possible to test more alternatives in less time. Judgment still determines which question the prototype needs to answer and which decisions are worth validating before moving forward.
An idea is easier to discuss when it's clickable.
A prototype helps make decisions without pretending the product is already finished.
Scope
We choose only the screens and states needed to answer that question.
Content
We use representative material, and sensitive or clinical data are replaced or used under agreed conditions.
Interaction
A clickable version detailed enough to show how the path behaves, with the level of fidelity the decision requires.
Variants
AI helps explore alternatives quickly, and we compare them based on judgment, feasibility, and project needs.
Decision
The prototype ends with a conclusion: what stays, what gets dropped, and what still needs research before moving on to design or development.
How it works
First we define which decision the prototype should help resolve.
Hypothesis
We write down what we want to test and what we would need to observe to consider the idea useful.
Minimum path
We select the screens and data needed to build a coherent experience without overbuilding.
Prototype
We use design tools and, when it helps, AI to speed up the build and explore variants.
Review
We test the path with the people who have to decide on it or use it.
The result is documented before moving to the next level of investment.
FAQ
How long does a prototype take?
Building the prototype takes days. What varies most is defining what gets tested and coordinating the sessions.
Can the prototype be used as a website afterward?
Not directly: it doesn't have the security or performance of a production website. What gets reused are the decisions about paths, structure, and content.
Can the company's real documents be used?
Yes, the ones the company authorizes for the test: product pages, catalogs, technical documentation. Patient data, never.
Who is it tested with?
With the team that will use or maintain the site and, when possible, with healthcare professionals or distributors who already use the company's materials.