Digital product prototypes
Test the idea before building the whole thing.
A prototype turns an early product idea into something people can see, use and discuss. It helps you test the journey, align the team and plan development with far more confidence, before the expensive decisions become difficult to change.
The problem
Useful ideas still need testing.
A product can sound perfectly clear in a meeting and mean something different to every person in the room. Prototyping makes the assumptions visible: who the product is for, what they need to do, how each step connects and where the awkward questions are hiding.
That does not remove all risk. It removes a great deal of avoidable risk.
Who it is for
- Founders preparing an early product idea.
- Organisations exploring a new service or internal tool.
- Teams seeking funding or stakeholder approval.
- Product owners clarifying a complicated workflow.
- Organisations replacing a manual process with a digital one.
- Teams that need a stronger brief before appointing developers.
Common project types
- Customer or member portals.
- Booking and ticketing journeys.
- Internal workflow tools.
- Mobile app concepts.
- Data dashboards.
- Marketplaces, directories and service platforms.
The process
The prototype process.
The work moves from a shared definition towards something people can use, question and hand over.
-
Define the problem
Who the product is for, what it solves and which assumptions to test first.
-
Map the journey
Tasks, decisions, screens, edge cases and points of uncertainty.
-
Simplify the scope
The essential first experience separated from the eventual wish list.
-
Design the interface
Responsive screens and a coherent component system, detailed enough to feel real.
-
Make it interactive
Screens connected into a clickable prototype, mapped on the right device.
-
Test and learn
Feedback gathered, changes recorded and reasoning made visible.
-
Plan development
Scope, functional notes and a development roadmap for a more realistic estimate.
What you receive
Everything a developer needs to start well.
- A concise product definition.
- Priority user journeys.
- Wireframes and interface designs.
- A responsive design system appropriate to the prototype.
- An interactive prototype.
- A record of feedback and resulting changes.
- Functional notes and edge cases.
- A recommended development roadmap.
- A handover session for the team or chosen developer.
Practical principles
Real enough to learn from, light enough to change.
-
A prototype is
A realistic representation of the experience, designed to test the idea and support planning. It creates confidence about what should be developed.
-
A prototype is not
A finished, secure or production-ready application. Buttons may simulate actions and integrations may be represented rather than built.
-
Measurable proof
We record what was tested, with whom, what changed and which important questions remain.
Practicalities
A focused engagement.
-
Timing
A focused prototype engagement takes 6 to 10 weeks, depending on complexity, journeys, visual detail and whether user testing is included.
-
Investment
Prototype projects start at €5,000 plus VAT. Full software development is priced separately and is not implied by the prototype fee.
Make the idea real enough to question.
Tell us what you want the product to help people do. We will help define the smallest useful prototype and the decisions it needs to test.