How long it really takes to build an app. The truth.

"We deliver in 8 weeks." Everyone says that. Everyone delivers in 14 weeks. That's the difference between quote and reality.

A founder building a fitness MVP got "MVP in 8 weeks" promised at 4 different quotes. None delivered in 8 weeks. The fastest: 13 weeks. The slowest: 26 weeks. All 4 broke their promise.

Why? Because "8 weeks" is a marketing quote. Reality includes: design reviews, scope changes, integrations failing on first try, app store rejection, bugs found in testing. None of that is in the quote. It should be.

Honest breakdown: what takes time and why

An MVP with 5 features (auth, list, detail, profile, search) split by phase:

Week 1-2: Discovery + Design. User stories, flows, wireframes, design system, Figma mockups. Without this, you write code blindly. Realistic: 60-100 hours. Good studio: 1.5-2 weeks.

Week 3-4: Tech setup + architecture. Stack decided, repo created, CI/CD, environments (dev/staging/prod), auth integrated, database schema. Realistic: 40-80 hours. Week 1-2 in parallel with design if the team is large.

Week 5-9: Build features. This is where real code is written. 5 features × 30-50 hours each = 150-250 hours. Team of 2: 4-5 weeks. Solo: 7-8 weeks.

Week 10-11: Testing + bug fix. Manual testing, smoke test on real devices (iOS 14+, Android 9+), edge cases, performance. Realistic: 60-100 hours + bug fix (20-40% of build time).

Week 12-13: App Store + Play Store submission. Apple submission takes 24-72h, but 30-40% of apps are rejected on first submit (reasons: privacy policy, payment, IAP, copyright). Resubmit + 24-72h. Play Store more relaxed, but mid-tier review 7 days.

Week 14-22: Live + post-launch iteration. Production bugs that testing didn't catch (Apple pattern: 50-100 users surface new issues), first user feedback, urgent small fixes. Realistic buffer between weeks 14 and 22, depending on integration complexity and team velocity.

Realistic total: 14-22 weeks for a 5-feature MVP with a 2-person team. A range, not a fixed number.

Why 8 weeks is a lie

The "8 weeks" quote results from: 200 hours × 1 dev × 5 productive hours/day = 8 calendar weeks. On paper.

Reality includes:

• Client reviews (40 hours waiting per round, 3-5 rounds = 4-7 lost days)
• Design changes (20-40 extra hours if feedback comes mid-build)
• App store rejection (3-7 days per resubmit)
• Bugs found in testing (15-25% buffer minimum)
• Holidays, weekends, vacations (8 calendar weeks = 5.5-6 effective weeks)
• Third-party integrations failing on first try (Stripe webhook, Apple Pay, push notifications, typically 10-20 extra hours each)

Sum: 8 weeks "on paper" becomes 13-16 weeks real. Always. With any studio.

Anyone promising 8 weeks and delivering in 8 weeks: a) under-delivered scope, b) worked weekends (cooking the team into burnout), c) shipped without proper testing (you'll pay in post-launch bugs).

BEFORE vs AFTER: quote vs reality per scope

What you must ask before accepting any timeline

Before signing a contract with "delivery in X weeks", ask 5 concrete questions.

1. "What's included in week 0?"

Serious answer: discovery (5-10 hours of calls), wireframes + flows (15-25 hours), design system (40-60 hours), Figma mockups (40-80 hours), tech architecture decided in writing.

Bad answer: "we go straight to build from day 1".

Anyone skipping discovery writes code that will need to be rewritten.

2. "How many feedback rounds does the quote include?"

Serious answer: 3-5 rounds specified in SOW, each with client response deadline (48-72h). Big changes = written change request.

Bad answer: "unlimited".

Unlimited = chaos. It will become 12 rounds and still not done.

3. "What team is allocated to the project?"

Serious answer: 1 PM, 1-2 devs, 1 designer, allocated by percentage (50-80% of time). Names, CVs, GitHub.

Bad answer: "we have a team of experts".

Anyone not telling you names = there is no team, there is a freelancer with a subcontractor.

4. "What happens if scope creeps?"

Serious answer: written change request with hour estimate + price + timeline impact before work. Small changes (under 2h) free. Big changes = signed SOW addendum.

Bad answer: "we figure it out as we go".

"As we go" = invoice 40% over quote at the end.

5. "What's the late-delivery penalty?"

Serious answer: percentage discount from invoice per week of delay (3-5% typical) or delivery on specific date or credit for next project.

Bad answer: "doesn't apply, depends".

Anyone not accepting a penalty doesn't respect their own timeline.

Typical case study: fitness MVP with 3 quotes compared

A founder compared 3 quotes for the same 5-feature MVP.

Quote A: "6 weeks, 12,000 EUR". Accepted. Real delivery: 22 weeks. Final cost with scope creep: around 18,000 EUR.

Quote B: "14 weeks, 18,000 EUR with 5% discount per week of delay". Rejected as "too long".

Quote C: "10 weeks, 25,000 EUR, no penalty". Rejected as "too expensive".

In hindsight, quote B was the only realistic one. The studio would have delivered in 14-16 weeks with real contractual penalty. Total cost: 18,000 EUR fixed.

Instead, the founder paid the same amount for something that took 22 weeks and 5 months of frustration.

The real difference: not the price. The honesty of the timeline.

The short quote with no penalty is almost always more expensive than the long quote with penalty. Because reality finds its way.

Action plan for the next timeline you receive

1. Demand a phase breakdown. Discovery, design, build, testing, app store, post-launch. Each with allocated hours. Total must match the stated hourly rate.
2. Add 30% mental buffer. If the quote says 8 weeks, plan for 11. If it says 12, plan for 16.
3. Demand contractual penalty in the SOW. 3-5% discount per week of delay. If the studio refuses, they don't believe their own timeline.
4. Validate with 2 existing clients. "Did they deliver on time? What was the gap between quote and reality?". Their answer is your prediction.
5. Set intermediate milestones. Week 4 = final design approved. Week 8 = 50% features functional. Week 12 = full staging build. If they miss intermediate milestones, they'll miss the final one too.

Final lesson

Your app won't be ready in 8 weeks. Never. Not because the developer is lazy, but because reality includes design, feedback, app store, bugs, failing integrations.

Accept a realistic timeline (14-22 weeks for a serious MVP) or accept being lied to. There's no third option.

Now: pull out the last quote you received. Check if it includes a phase breakdown. If not, it's a marketing quote, not an engineering one. Demand the breakdown or walk away.