Understand
Clarify the precise question the prototype needs to answer.
Product design and prototyping
Validating an idea before investing in a full build
A prototype exists to answer one precise question — not to impress, but to find out if the idea holds up.
Business context and need
The problem this solves
Building a full version before validating an idea with real users is one of the most expensive ways to learn it doesn't work. This service makes sense ahead of a larger project, when the question isn't yet "how do we build it" but "is it worth building at all."
From scoping through evolution
How it moves forward
Each stage turns uncertainty into a verifiable decision.
Design
Build only what's necessary to test that question.
Build
Deliver a navigable or functional prototype, not just static mockups.
Evolve
Document what the test revealed, to guide what comes next.
Frequently asked questions
Useful answers before getting started
Clarification on scoping, timelines, collaboration, and the next step.
Some foundations may be reusable, but a prototype is primarily built to learn quickly. A production product then needs access control, real data handling, testing, architecture, accessibility, and maintenance. The proposal states what is exploratory and what is built to last.
Possible deliverables
- Interactive or functional prototype
- Validation report based on real feedback
- Recommendation on next steps (build, adjust, or stop)
Quality principles
- The prototype tests a real question, not a feature checklist
- Feedback is gathered from real potential users when possible
- The outcome includes an honest recommendation, even when it's not to continue
What helps prepare the conversation
What's useful to prepare
- The precise question you're trying to validate
- Access to a few potential users for testing
- The budget planned for what comes next, if the prototype succeeds
Lethavia
Validate your product idea
Let's talk about the idea you're trying to validate.
Shape your product idea