Almost every founder has a full vision for their product — the complete feature set, the polished experience, the version that handles every use case. The question isn't whether that version is worth building eventually. It's whether it's the right place to start.
What an MVP actually is
An MVP (minimum viable product) isn't a stripped-down demo, and it isn't a rough prototype that falls apart under real use. It's the smallest version of your product that lets a real user complete the core thing your idea is about — genuinely usable, just narrow in scope.
The key word is "viable," not "minimum." A viable version has to actually work.
Why building the full product first is risky
Building everything at once means you don't find out whether the core idea works until the very end of a long, expensive process. If an assumption turns out to be wrong — about what users want, how they'll use the product, or what they'll pay for — you find out after building the whole thing instead of after building the smallest testable version of it.
When a full product approach makes sense
This isn't a rule that applies to every situation. If you already have strong evidence the core idea works — validated demand, an existing customer base, or a direct replacement for a process you already run manually — a more complete first version can make sense. The decision should follow from how much is already known, not from how big the vision is.
How we help you decide
During Discover and Define, we look at:
- What's already validated vs. what's still an assumption
- What the riskiest unknown in your idea actually is
- What the smallest version would need to include to test that unknown
That gives us a scope for version one that's honest about what still needs to be learned — not the biggest version we could justify building.
The bottom line
Build the smallest useful version, not the biggest possible version. It's not a shortcut — it's how you find out what's actually worth building before you invest in building it.
Ready to figure out your version one? Let's define your MVP.