"How long will it take?" is usually the second question a founder asks us, right after "how much will it cost?". The two are tied together: time is the biggest driver of cost, and scope is the biggest driver of time.
The short answer: a focused MVP usually takes 8–12 weeks. A complex platform — multiple apps, integrations, AI, or compliance — takes 3–6 months. The longer answer depends on a handful of decisions you control. Here is how the time actually breaks down.
The five phases of building an app
1. Discovery and scoping (1–2 weeks)
This is where you decide what not to build. A good discovery phase ends with:
- A clear statement of who the first users are and the one job the product does for them
- A prioritised feature list split into "launch", "soon after" and "later"
- A technical approach — platforms, stack, integrations
- A milestone plan and a fixed quote
Skipping discovery rarely saves time. It moves the arguments about scope into the middle of the build, where every change costs more.
2. Design (2–4 weeks, overlapping with the build)
Design starts with user journeys and wireframes for the core flows, then moves to high-fidelity screens. On a well-run project, engineering starts on the foundations — authentication, data model, infrastructure — while design finishes the details. Design and build should overlap, not queue up one behind the other.
3. Build (4–10 weeks for an MVP)
This is the bulk of the timeline. Work happens in weekly sprints, each ending in a demo of working software. What makes the build longer:
- More platforms. Web only is fastest. Web + iOS + Android + an admin panel is effectively four surfaces, though cross-platform tools like React Native share most of the mobile code.
- More user roles. A two-sided marketplace (customers and providers) is close to two products.
- Integrations. Payments, maps, calendars, EHRs, CRMs — each one adds setup, edge cases and testing.
- AI features. Model choice, data preparation and evaluation all take time beyond the interface.
4. Testing and launch preparation (1–2 weeks)
QA should run throughout the build, but the last stretch is for end-to-end testing, performance checks, analytics, and — for mobile apps — App Store and Play Store submission. Store review can add a few days, so plan for it.
5. Post-launch iteration (ongoing)
Launch is when you start learning from real users. Budget time in the first month for fixes and quick improvements based on what you see.
Typical timelines by product type
| Product | Typical timeline |
|---|---|
| Focused web MVP (one user type, one core flow) | 6–8 weeks |
| Web + mobile MVP with an admin panel | 8–12 weeks |
| Marketplace or multi-role platform | 3–4 months |
| Complex platform (AI, integrations, compliance) | 3–6 months |
For a real example: Clean Fanatics went from concept to production in three months — a React Native customer app, a React web app, and a Next.js admin that automates staff assignment, scheduling and payouts.
Five ways to ship sooner
- Pick one user and one job for version one. Every extra persona multiplies flows, edge cases and testing.
- Buy, don't build, the commodity parts. Authentication, payments, email and analytics all have excellent off-the-shelf services.
- Keep the admin panel plain. Your internal team can live with a simple interface for the first few months.
- Decide quickly. The most common cause of delay isn't engineering — it's waiting on feedback and approvals. Weekly demos with a single decision-maker keep things moving.
- Fix the scope, flex the details. Agree the milestones up front, then let the team adjust how each feature works as you learn.
Red flags in a timeline estimate
- A precise estimate before any discovery. Nobody can responsibly promise "7 weeks" for a product they haven't scoped.
- No working software until the end. You should see and click through real progress every week.
- No time for testing or store review. Those weeks exist whether or not they're in the plan.
The bottom line
Most MVPs can ship in 8–12 weeks if the first release is small, decisions are quick, and one team owns design and engineering together. If you'd like a realistic timeline for your product, tell us what you're building — or read our guide to what an MVP costs.