Emerging Technology · Technology Prototypes & MVPs
Test the idea before you build the whole product.
We take an idea through concept, wireframes and a clickable prototype to a minimum viable product, with a clear question to answer at each stage. The goal is evidence from real users while the cost of change is still low.
Common risks
Building too much, too early
Full build before validation
Months of work go into features nobody asked for.
Unclear MVP scope
“Minimum” grows until it is no longer minimum.
Prototype treated as product
A demo is put in front of customers without the engineering a live system needs.
What is included
Staged, with a decision after each
- Problem and scope definitionUsers, the problem, and the one question the prototype must answer.
- Wireframes and flowsStructure and user flows, reviewed before design or code.
- Clickable prototypeInteractive prototype for user feedback.
- MVP definitionCore feature set, deliberately limited, with a backlog for later.
- MVP buildWorking product with core functionality, hosted for real users.
- Feedback and next stepsWhat was learned, and what to build, change or stop.
Deliverables
What you receive, and the limits
You receive
- Scope and success questions
- Wireframes
- Clickable prototype
- MVP feature list and backlog
- Working MVP (if you proceed)
- Findings and recommendations
Boundaries
- A prototype is not production software, and we say what is missing.
- An MVP has limited scope and may need rework to scale.
- We cannot guarantee market success.
- Each stage can be a stopping point.
How it works
One decision per stage
You can stop at any stage with something concrete.
Define
Problem, users, key question.
Wireframe
Flow reviewed with you.
Prototype
Tested with a few users.
Scope the MVP
Smallest useful version agreed.
Build and learn
MVP released and feedback gathered.
Questions
Common questions
Do we need a full MVP?
Not always. A prototype test can answer the question for less cost.
Can the prototype become the product?
Sometimes parts can be reused, but we are upfront about what has to be rebuilt.
How long does an MVP take?
It depends on scope. We agree a timeline after the definition stage.
Who owns the code?
You do, subject to the agreement.
An idea you want to test first?
Tell us the idea and who it is for. We will reply with what we would test first.