Most MVPs take 8 to 16 weeks from kickoff to a release that real users can try, with 2 to 4 weeks of discovery and design before development starts. Marketplaces, anything with payments, and regulated products sit at the longer end. The single biggest cause of delay is not engineering, it is slow decisions.
Founders usually ask about timeline for one of two reasons: an investor meeting, or a competitor. Both are good reasons to want a date, and both are bad reasons to accept a date that a team cannot keep. This post explains where the weeks go in an MVP build, what stretches them, and how to protect the date you were given.
What does a typical MVP timeline look like?
| Phase | Typical duration | What happens | What you decide |
|---|---|---|---|
| Discovery | 1 to 2 weeks | Define the problem, the user, the one thing the MVP must prove. Scope the first release. | What is in, what is out. |
| Design | 2 to 4 weeks | User flows, wireframes, then the visual interface. Often a clickable prototype. | Approve flows and screens. |
| Development | 6 to 10 weeks | Backend, front-end, integrations, built in short cycles with demos every one or two weeks. | Feedback on each demo, fast. |
| Testing and launch | 1 to 3 weeks | Bug fixing, performance checks, app store submission and review, production setup. | Launch criteria and go-live date. |
Add those up and a focused MVP lands at 10 to 19 weeks including discovery. A team that promises four weeks for a product with accounts, payments and an admin panel is either describing a prototype or has not read your brief.
What makes an MVP take longer?
- Scope creep. Every "while we are at it" feature costs days and pushes the date. The most disciplined founders keep a written list of ideas for version two and leave it alone.
- Slow decisions. A design waiting a week for approval is a week lost. Agree at the start who decides and how quickly.
- Integrations with unknowns. A partner's API that turns out to be undocumented, or a payment provider that needs weeks to approve your account.
- App store review. Apple's review can take a few days, and a rejection adds a cycle. Plan for it and submit early.
- Content and data. The product needs real text, images, prices and categories. If those come from you, they are on the critical path.
- Compliance. Healthcare, finance and children's products need security work and sometimes external review.
What makes it faster?
- One platform first. Web or one mobile platform, not all three.
- Ruthless scope. If the feature does not prove the core idea, it waits.
- Off-the-shelf services for authentication, payments, notifications and analytics.
- A clickable prototype before code. Changing a screen in a design tool takes an hour. Changing it after it is built takes days.
- Weekly demos with a founder who shows up. The fastest projects we have run had a decision maker in every demo.
How long do common MVP types take?
| MVP type | Typical build | Why |
|---|---|---|
| Content or community app | 8 to 10 weeks | Accounts, feeds, profiles. Mostly known patterns. |
| Booking or scheduling platform | 10 to 14 weeks | Calendars, availability rules, payments, notifications. |
| Two-sided marketplace | 14 to 20 weeks | Two user roles, listings, search, payments with payouts, disputes. |
| Fintech or healthtech | 16 to 24 weeks | Identity verification, compliance, audit trails, security review. |
What should you do while the MVP is being built?
A build phase is not a waiting room. The founders who launch well use those weeks to line up the first hundred users, write the onboarding emails, set up analytics goals, prepare the app store listing and start the conversations that will fill the first month after launch. When the product ships, they have somewhere to put it.
How 7L handles timelines
After discovery we commit to a fixed timeline and budget for the first release, and we hold ourselves to it. You see progress in regular demos and you know exactly which decision is needed when. If you have a date you need to hit, talk to us early, because the cheapest way to make a date is to scope for it from the start.
Frequently asked questions
Can an MVP be built in four weeks?
A prototype can. A product with real accounts, data and payments that you would put in front of paying customers usually cannot, unless the scope is a single feature and the team already has the building blocks.
Does a clickable prototype slow the project down?
It adds a week or two up front and typically saves more than that later, because screens are corrected before they are built. It also gives you something to show investors and early users months before launch.
How long does app store approval take?
Apple usually reviews within one to three days, sometimes longer, and a rejection means another cycle. Google Play is usually faster. Submit a test build early so account and compliance questions surface before launch week.
What if I need to change scope during the build?
Changes are normal. The rule is that every addition either replaces something of similar size or moves the date. A good partner will show you that trade-off in writing before agreeing.
How soon after launch should I plan the next release?
Immediately. The first two weeks of real usage will tell you more than the previous three months. Keep budget and team availability for a follow-up release within four to six weeks of launch.