How long to build an MVP: can it really take 15 days?
How long to build an MVP depends mostly on scope. An MVP can be built in 15 days when the scope is small, decided upfront and stays closed. That’s what we sell: about 300 build hours or less, for one core workflow with login, billing and admin. Larger products take longer, and we won’t promise 15 days for them.
Reviewed by Anubhav Gupta, Bespoke Devs · Updated
How long to build an MVP: what has to be true for 15 days
- You can name one core jobIf you can’t say in a sentence what customers pay for, scoping won’t finish in two days.
- You make decisions quicklyDesigns are approved in week one. A slow reply on a 15-day schedule costs a noticeable share of the time.
- The scope closesNew ideas wait for a later version. See fixed price vs time and materials.
- No unknowns in the coreCommon features such as login and Stripe billing are well understood. Research problems aren’t, and nobody can schedule them accurately.
- Your accounts are readyDomain, Stripe and any API access should be available when the build needs them.
What fits, and what doesn’t
| Usually fits | Usually doesn’t |
|---|---|
| One web app with login, billing, dashboard and admin | Multi-tenant systems with complex permissions |
| An LLM feature with a clear job, if the rest stays small | AI as heavy research, or custom models |
| A couple of standard integrations | Native mobile plus web together |
| A marketing site with schema and a sitemap | Two-sided marketplaces with payouts |
When 15 days is the wrong goal
If you don’t know what the first version should do, moving fast only gets you to the wrong place sooner. Talk to customers first. And if you’re in a regulated field, or handling health or financial data, compliance work can take longer than the build. Speed isn’t the priority there.
Common questions
Yes, if the rest of the scope is small. Design is part of the 15 days, and you approve it in week one. A web app with login, Stripe billing, admin, email and one API comes to about 296 build hours with no designs, which only just fits.
Add up the build hours in [our calculator](/tools/mvp-cost-calculator). We treat about 300 as the limit. A mobile app alone is about 160 hours and marketplace payouts about 64, so either one uses up a large share of that.
We’ll tell you on the call. You can cut scope, supply your own Figma file to save design time, or get a custom quote with a longer timeline.
It means fewer features. Testing is scheduled for days 13 and 14. Ask any builder, including us, what they test and how.
Our rough estimate for a typical MVP is 10 to 14 weeks with a freelancer and 7 to 12 weeks with an agency. See [the full timeline](/saas-mvp-development/questions/how-long-does-an-mvp-take).
Keep reading
- SaaS MVP developmentWhat’s included, what it costs and how a 15-day build works.→
- How long does an MVP take?The day-by-day plan, and rough timelines for other routes.→
- Fixed price vs time and materialsWho carries the risk, and how scope discipline protects a launch date.→
- Freelancer vs agencyCost, timeline and risk compared, including when the freelancer wins.→
Tell us what you’re building.
Takes under a minute. We come back with a scope and a fixed price.
- Reply within 24 hoursA real person reads every brief.
- Fixed scope, fixed priceYou get a written proposal, no hourly billing.
- You own the codeFull ownership of code and assets at launch.