"MVP in 6 weeks" makes a great headline, and plenty of agencies promise it. Here's the honest version: six weeks is genuinely achievable, we ship on that timeline, but only under specific conditions. When those conditions aren't met, six weeks quietly becomes four months, and nobody warned the founder. This post is the warning.
What 'MVP' actually means (and what founders often mean)
An MVP is the smallest product that lets real users complete one core journey, so you can learn whether anyone wants it. It is not version 1.0 of your full vision with slightly fewer features. The most common cause of blown timelines isn't slow developers, it's an 'MVP' scoped as a finished product: three user roles, chat, payments, admin dashboard, and notifications, all 'essential'.
“If your MVP has more than one core user journey, it's not an MVP, it's a roadmap wearing a trench coat.”
What realistically fits in 6 weeks
- One core user flow done properly, e.g. browse → book → pay, or record → track → view progress
- Sign-up and login (email + one social/Apple login)
- A clean, professional UI built from a design system, polished, not award-bait
- One backend with a real database, ready to grow (not a throwaway prototype)
- iOS and Android simultaneously, this is why we build in React Native
- Basic analytics so you actually learn something from launch
- App Store and Google Play submission, including the review process
What does NOT fit in 6 weeks
- Real-time chat or video calls, deceptively hard to do well; add weeks, not days
- Marketplace mechanics with two user types, each with their own flows, that's two MVPs
- Complex custom payment logic: subscriptions with trials, split payments, refund flows
- Custom AI features beyond straightforward API integrations
- 'Like Instagram, but for X', social feeds, follows, and moderation are a product in themselves
- Pixel-perfect custom animations on every screen, save them for v2, when you know people want v1
None of these are impossible. They're just not six-week items, and anyone who says otherwise is planning to have that conversation with you in week five.
The week-by-week reality
- Week 0 (before the clock starts): scoping workshop, we cut the feature list together until one core journey remains. This is where the six weeks are won or lost.
- Week 1: wireframes to final UI design of the core flow; backend foundations and project setup run in parallel
- Weeks 2–4: core build, the app takes shape, and you see a working build weekly, not screenshots
- Week 5: the unglamorous 20% that takes 80% of tears, edge cases, error states, slow-network behavior, testing on real devices
- Week 6: polish, store assets, submission, and the review buffer (Apple can take from a day to a week, and no agency on Earth controls that)
The conditions that make or break the timeline
- Decisions in 24–48 hours: when we ask 'A or B?', a three-day silence costs three days, there is no slack in six weeks
- One decision-maker: 'let me check with my co-founder, cousin, and investor' is the timeline's natural predator
- Scope is frozen after week 0: every 'small addition' mid-build costs double, build time plus disruption
- Content exists: app name, logo direction, and legal texts can't materialize in week 6
So is 6 weeks right for you?
If you can describe your product's core in one sentence, accept that v1 will be missing things, and commit to fast decisions, six weeks is realistic, and it's how you get real user feedback while your competitor is still perfecting their feature list. If your idea genuinely needs a marketplace, real-time features, or heavy custom logic, the honest timeline is 10–14 weeks, and we'd rather tell you now than in week five. Bring us your feature list and we'll tell you, specifically and for free, what fits in six weeks and what should wait for version two.
