The MVP Misunderstanding
Most founders think an MVP is a slow, small version of their full vision. It is not. An MVP is the smallest thing you can build that tests the most important assumption about your business.
If your core assumption is "people will pay to use this," your MVP needs payment infrastructure. If your core assumption is "users will engage daily," your MVP needs the engagement mechanic. Everything else is scope creep disguised as quality.
What Two Weeks Actually Allows
In two focused weeks, a team of two can ship:
- A full authentication flow (sign up, login, password reset)
- One or two core user workflows that test your primary value proposition
- Basic data persistence and retrieval
- A production deployment with a real domain
- Stripe payment integration if monetization is the assumption being tested
What two weeks does not allow: complex reporting, mobile apps, third-party integrations beyond what is essential, and admin tooling for edge cases that will not exist until you have 100 users.
The Specification Prerequisite
The two-week constraint only works with a tight specification going in. We require: defined user flows (not wireframes necessarily, but clear descriptions), identified data entities and their relationships, a list of integrations with documentation links, and a clear success criterion.
Teams that arrive with "we want something like Airbnb but for boats" do not ship in two weeks. Teams that arrive with user stories, example inputs and outputs, and a clear definition of what done looks like — those teams ship.
How We Prioritize
For every potential feature, we ask three questions:
- Is this required to test our core assumption?
- Can we manually handle this for the first 100 users?
- Does a user fail their primary task without this?
If the answer to 1 is no and 2 is yes, it does not go in the MVP.
After Launch Is When the Real Work Starts
The MVP is not the product. It is the data collection mechanism. The value is not in what you built — it is in what you learn from real users interacting with real software. That learning shapes version two, which is where most successful products are actually born.
Ship in two weeks. Learn for two more. Build what the data tells you.