01
v1 boundary
What must be in v1, what we deliberately skip, and why.
MVP
MVP development that can actually test demand
Not a Figma prototype and not a full product on an MVP budget. A first working version: one flow, real users, a measurable outcome.
What we do
02
Core flow
One path from entry to outcome — no side quests “just in case”.
03
Production stack
Code you can grow. Not a throwaway draft you will rewrite in a month.
04
Launch and signal
How we will know demand is real: events, feedback, the next step.
What’s included
- Product workshop
- UX of the core flow
- v1 design
- Frontend and API
- Basic analytics
- Launch
How we build an MVP
01
Hypothesis
What demand we are testing and what counts as success.
02
Slice
The smallest flow, roles and data.
03
Build
Interface, logic and the integrations the flow cannot live without.
04
Release
Ship to real users and collect signal.
Prototype, MVP or full product
Prototype
Pictures and a clickable mock. Useful to align the idea — useless as a market test.
MVP
A working product with one flow. Enough for people to use it, pay, or honestly walk away.
Full product
Roles, billing, admin, scale. Worth it after the MVP hypothesis holds.
Related cases
Frequently asked questions
How is an MVP different from a prototype?
A prototype shows how it might look. An MVP is a working product with one flow that people can already use.
Can the MVP grow into a full product later?
Yes, if we do not cheap out on architecture. We do not ship throwaway code “for three weeks”.
How long does an MVP take?
It depends on the flow and integrations. We give a real answer after the brief — not a blind “two-week MVP”.