The idea needs to win people over
Users, stakeholders, or investors need to understand and experience the idea before full development begins.
Users, stakeholders, or investors need to understand and experience the idea before full development begins.
Interaction logic, user flow, or usability needs to be tested with realistic tasks before implementation begins.
The value, interaction, and technical requirements of an AI idea need to become tangible before significant time and budget are invested.
We plan functional variants and AI prototypes in two-week sprints. The number depends on the open question and the required level of realism. Before work begins, we agree the question to test, the testing scope, timeframe and price.
The clickable variant tests flow and use. The functional version tests behaviour and feasibility. The AI variant shows how the system responds to different inputs. Their purpose is a sound decision, not production operation.
The formats can build on each other, but they do not have to. What matters is which question you need to answer next.
You get a testable version, findings from the assessment and a reasoned recommendation.
The idea becomes tangible as one connected experience instead of existing only in slides, requirements, or isolated screens.
You see what people understand, where they struggle, and which assumptions need to change before further investment.
Tested flows, prioritised features, and technical insights create a concrete foundation for further development or handover.
The idea becomes tangible as one connected experience instead of existing only in slides, requirements, or isolated screens.
You see what people understand, where they struggle, and which assumptions need to change before further investment.
Tested flows, prioritised features, and technical insights create a concrete foundation for further development or handover.
The clickable version represents flow and use realistically without being fully programmed. An alpha already includes selected functional parts and runs internally. An MVP takes responsibility for real use for the first time. It therefore belongs to new development, not to prototyping.
Yes. Depending on the question, we first simulate the behaviour or connect a suitable model. What matters is whether we need to test value and interaction first or already assess response quality, data, and technical limitations.
Yes. We build the test version around realistic tasks, content, and states. The insights feed directly into structure, UX, UI, and the next scope.
It can then become a first version that is usable in production. We continue that initiative under Develop a new digital product, including implementation and launch. Alternatively, we hand over the design, specification, and findings to your engineering team.
An idea, a problem, or an open question is enough. Finished requirements are not necessary. In the first conversation, we define the goal, users, existing foundations, and which version makes sense next.
A focused clickable version can be created within a few weeks. Functional and AI variants depend more strongly on scope, data, and integration. After the initial assessment, you receive a realistic timeframe.

Marco or someone from the team will get back to you, within 24 hours on working days.