Clickable prototype
For presenting an idea and testing its user journey.
- One main journey, around 5–8 screens
- Screen design and clickable connections
- Sample data, without a working backend
Build the first thing that helps you decide what comes next.
Plan my projectThe right starting point
For presenting an idea and testing its user journey.
For real users and real data.
In a prototype, sign-in, payments and data handling are simulated. In a working release they are implemented. Mobile and combined versions have different entry prices, shown in the planner.
In practice
Goal and main user journey
Clickable demonstration
Gather feedback
Define the next version
Concrete deliverables
The proposal defines the deliverables and acceptance criteria, so both sides share a clear definition of done.
01
Goals, users, existing materials and technical context.
02
Scope, deliverables, fee and feasible schedule.
03
Agreed steps, demonstrations and feedback.
04
Verification, access and ongoing support arrangements.
No. It demonstrates screens and journeys using sample data. It does not store real customer data, process payments or contain a working business backend.
No. We clarify the goal, user and main journey together. Larger or uncertain ideas also need a defined planning scope.
The journeys and feedback inform development. A working application is a separate phase; a prototype does not automatically provide production code.
Prototype pricing depends on journeys, screens, roles and views. Working products also depend on platforms, business rules, integrations and data handling.
Yes. If the goal and scope are clear, select a working first release in the planner.
The planner opens the relevant questions and gives you a project brief and estimated budget.
Plan my project