The most common timeline question we get is simple: how long? The honest answer is six to sixteen weeks — depending on what you are actually asking someone to build.
A scoped MVP with one user type and three to five core features takes six to ten weeks. Add a second user type, a payments layer, or a custom admin and the range moves to ten to sixteen weeks. Six months almost always means scope was never defined — or the quote lowballed to win the job.
The gap between six weeks and six months is almost never about speed. It is almost always about what was in the brief before the clock started.
What actually drives an MVP timeline
Three variables explain most of the variance between a six-week build and a sixteen-week one.
User types. A product with one user type is roughly a quarter of the complexity of a product with two. Add an admin dashboard that a third class of user operates — moderation, data review, approval flows — and you have added a third permissions model, a third set of views, and a third surface to design. Each additional user type adds three to four weeks.
Third-party integrations. Each integration is a moving part with its own failure modes. Stripe takes a week to integrate correctly — longer if subscriptions, refunds, and webhooks are involved. A video transcription API, a calendar sync, a CRM handoff: each is a week not spent building the core product. Founders underestimate this by 2× on average.
Admin complexity. "We just need a simple admin" is the single most expensive sentence in MVP development. A simple admin in practice means user management, data tables with filtering and export, audit logs, content moderation, and a permissions system. Plan for two to four weeks even on a small build.
Week by week: what actually ships in each phase
This is a realistic 8-week build. Not the optimistic version — the honest one.
| Week | What ships |
|---|---|
| 1 | Architecture and database schema. Dev environment established. First route working. |
| 2 | Core authentication complete. User flow skeletons. First staging URL sent to founder. |
| 3 | Primary feature in progress. External API integrations wired if any. |
| 4 | Primary feature working. First founder review session on staging. |
| 5 | Secondary features. Scope cut conversation if anything is at risk. |
| 6 | UI polish. Error states and edge case handling. |
| 7 | QA and staging walkthrough with real data. |
| 8 | Production infrastructure. Cutover. Launch. |
Builds with more complexity — a marketplace, two user types plus admin, anything real-time — run the same shape but weeks three through six expand. For how cost tracks against timeline by tier, see What an MVP costs in 2026.
When is six months an honest estimate?
There are builds that genuinely take six months. A regulated product — healthcare, fintech — with compliance requirements. A marketplace with a complex trust layer. A product replacing a legacy system with a live migration. We have shipped several of these.
But six months is almost never honest for a first product with a single user type. When it appears in a quote, one of four things is usually true:
- The agency is running your project part-time alongside other clients.
- The scope was never defined in writing, and the timeline absorbs the ambiguity.
- The agency is building v3 when you asked for v1.
- The quote lowballed the price and padded the timeline to absorb overruns.
Ask to see the milestone plan in writing. If the agency cannot break six months into four to six defined milestones — each with a deliverable you can click on staging — the estimate is a placeholder, not a plan.
MVP vs v1: the distinction that changes the quote
An MVP is the smallest surface that lets you answer one question: do people want this?
A v1 is the product you build after they do.
Most founders who ask for a six-to-eight-week build are asking for an MVP. Most agencies quoting six months are pricing a v1 they have not said out loud. That gap is where most timeline arguments live, and where the expensive scope misunderstandings start.
The test: what is the one action a user must complete for this product to be worth opening? Everything that does not feed that action is v1 scope. If the agency's plan has features that do not serve that action, the timeline is being spent on the wrong product.
Timeline heuristics
- Six weeks is honest for a simple, single-user product. One user type. Standard auth. Three to five core features. No complex integrations.
- Ten to twelve weeks is honest for a two-sided product. Two user types. Payments. Basic admin. This is the modal first MVP.
- Fourteen to sixteen weeks is honest for complex scope. Three user types or more. Marketplace logic. Compliance requirements. Live migrations.
- Any estimate without a milestone plan is a guess. Push for a written scope with deliverables at each milestone before the contract signs.
A realistic timeline is not a slow build. It is a scoped one. The builds that finish in six weeks almost always had a hard scope conversation in week one. That conversation is worth more than any estimate.
Written 2026-06-23 by Naman Barkiya.