The key points
- Four to eight weeks for a deliberately focused first version.
- Scope is the biggest lever: fewer features means a shorter build.
- Integrations and data migration lengthen the build.
- Launch is the start of learning, not the end of the project.
What decides where in the range you land?
Scope, almost entirely, which is why deciding what features an MVP includes matters more than how fast anyone codes. A product with one core flow lands near the short end; one with several user roles, payments and integrations sits near the long end. Each additional role, integration or screen adds build and testing time, and the instinct to include just one more feature is how an eight-week plan becomes sixteen.
What slows an MVP down?
Unclear decisions, late feedback and shifting scope. If the person who approves work is not available, or the goal changes mid-build, the work waits or is redone. Third-party dependencies matter too: payment providers, messaging platforms such as the WhatsApp Business API and other services can need approvals that no developer controls. A native mobile app adds another wait, because each release goes through Apple and Google store review.
- Scope that grows after sign-off
- Decision-makers who are slow to review
- Integrations needing external approvals
- Migrating data from spreadsheets or older systems
What happens after launch?
Launch is when learning begins. The product goes to real users, you watch what they do and the roadmap is adjusted by their behavior. Our MVP development service includes a technical roadmap for the next version and three months of support, so the first changes that real usage demands are covered. Beyond that, plan for the support a startup needs after launch.
A typical MVP timeline
Ideation and scoping
Agree the one assumption to test and the smallest build that tests it. About three days.
Prototype
Turn the core flow into something you can click through and refine before building. About one week.
Build
Develop the working product in sprints with regular demos. Three to six weeks, depending on scope.
Launch and iterate
Deploy to real infrastructure, put it in front of users and begin responding to what they do. A few days.
Keep your MVP timeline honest
- Is the first version limited to one core assumption?
- Who approves each stage, and how fast can they respond?
- Which integrations are essential rather than convenient?
- Is there data to migrate, and in what condition?
- What is the plan for the first week after launch?
Sources
Rules and guidance this answer relies on. Policies change, so check the current version before acting on it.