How long does it actually take to build an MVP?

Every founder’s first estimate is 4 weeks. Their second estimate, after their first bad experience, is 6 months. The truth for most MVPs is somewhere between — and depends heavily on the product shape.

Here’s the timeline math we use.

The five buckets

Not every MVP is the same size. These buckets cover 90% of what we ship.

Marketing site (1-3 weeks)

Static or WordPress. 5-10 pages. Contact form, blog, portfolio. No login, no payments, no dynamic content beyond a CMS.

What eats time: Copy and photography. Design decisions. Real numbers to put on the site.

Typical: 2 weeks from brief to live if content is ready.

Marketing site with a lead-heavy flow (2-4 weeks)

Same as above plus: pricing calculator, quote configurator, booking, or a multi-step lead form wired to a CRM.

What eats time: Business logic for the calculator or configurator. Integration with the CRM or email system. Testing every branch.

Typical: 3 weeks.

Web app / dashboard (6-10 weeks)

Login, roles, database, one or two core flows working end to end, admin surface. Think: internal ordering portal, class management platform, small SaaS MVP.

What eats time: Auth + roles + permissions (always more than expected). Data model iteration. Real user testing surfacing edge cases in week 5-6.

Typical: 8 weeks.

Mobile app (10-14 weeks)

Flutter or React Native. Login, core flows, real backend (Supabase, Firebase, or custom), push notifications, deep linking. Ship to Play Store and App Store.

What eats time: Store submission process (~1 week alone). Device testing across Android versions. Payment integration if applicable. Push notification setup and testing.

Typical: 12 weeks.

Superapp / platform (14-24 weeks)

Multiple modules — mobile + admin web + backend. Multiple user roles. Complex workflows. Real inventory or scheduling. Think: dealer superapp, exam platform, healthcare booking + admin.

What eats time: Integration between modules. Real data seeding. Multi-role permission testing. Client’s own team getting up to speed on the admin panel.

Typical: 18 weeks.

What eats time (that founders always underestimate)

• Auth + roles + permissions — ~1 week for anything non-trivial
• Payment integration + testing — 4-6 days
• Push notification pipeline — 2-3 days
• App store submission + review — 1-2 weeks for iOS on first submission
• Email delivery infrastructure — 2-4 days including SPF/DKIM/DMARC
• Analytics + error tracking wiring — 2 days
• Client content plugging — always double the estimate

What can be parallelized

If you have a design and engineering team running in parallel from day one, you can shave 25-30% off the timelines above. That’s what studio Full Build engagements do:

• Week 1: discovery (both)
• Week 2-3: design finalizes screens while engineering scaffolds infra + auth
• Week 4-6: engineering builds against agreed designs
• Week 7-8: polish + QA
• Week 9-10: prod deploy + hyper-care

If design and engineering are sequential — designer ships, then engineer starts — add 3-4 weeks.

Why the ‘3-month MVP’ is almost always a lie

The “3-month MVP” that sales decks promise usually assumes:

• Scope is fixed and won’t grow (it will)
• Design is already done (it isn’t)
• Client feedback comes back fast (it doesn’t)
• No app-store submission required (there is one)
• No paid integrations (there are three)

Every one of those assumptions adds a week. Five assumptions = five weeks over. That’s a 3-month MVP that ships in 5.

The honest ranges

• Marketing site: 2-3 weeks
• Marketing site with logic: 3-4 weeks
• Web app / dashboard MVP: 8-12 weeks
• Mobile app MVP: 12-16 weeks
• Superapp / platform MVP: 18-24 weeks

Give yourself a 20% buffer on top of these. Anyone quoting significantly less either misunderstood the scope or is going to hand you something incomplete.