The 8-Week Lie (And How We Made It True)
Three years ago, we quoted a client 12 weeks for their MVP. They panicked. We panicked. We eventually shipped in 10 weeks, exhausted.
Last year, we shipped a complete SaaS MVP in 6 weeks. Not a prototype. Not a landing page. A real product with auth, payments, dashboards, and integrations.
Here's how we do it now.
Why 8 Weeks Is Actually Possible
The secret isn't working faster. It's working differently.
Most MVPs take longer because:
- Scope keeps expanding: That "simple feature" becomes 3 weeks of work
- Decisions get delayed: Team waits for founder input on things that don't matter
- Testing is an afterthought: QA happens at the end, causing rework
- Infrastructure is custom: Building instead of using what's proven
We eliminated all four.
Week 1-2: Foundation
What We Actually Do
Day 1-3: Requirements & Design
We don't write 50-page specs. We write one page:
- What problem does this solve?
- Who has this problem?
- What does the ONE core feature do?
- What does "done" look like?
Then we design the core flow in Figma. Not every screen. Just the path from signup to value.
Day 4-10: Tech Stack Setup
We use what works:
- Next.js for frontend
- Supabase for backend (auth, database, storage)
- Stripe for payments
- Vercel for deployment
No decisions. No debates. Just "what are we using this time?"
Week 3-4: Core Feature Development
This is where most teams burn time. Here's what we do differently:
Daily Standups (Actual 15 Minutes)
Not "what did you do yesterday?" But:
- "What's blocking you?"
- "What are you working on today?"
- "Any decisions needed?"
Decisions get made in standup or immediately after. No decision waits more than 24 hours.
Feature Branches Merged Daily
Every engineer merges to main daily. This sounds scary. It's not.
If you're afraid to merge, your branches are too big. Smaller branches = faster feedback = fewer conflicts.
Week 5-6: Integration & Polish
Stripe in Week 5, Not Week 8
We've seen teams build beautiful apps and then spend 3 weeks on payments.
We implement Stripe in Week 5. If Stripe breaks, we find out while we still have time.
Same with email, file uploads, and other integrations.
We Ship to Production Early
Not staging. Not QA environment. Production.
Week 6 has the app live with a "coming soon" splash. Real infrastructure. Real data. Just hidden from users.
Why? Because production infrastructure has bugs staging doesn't catch.
Week 7-8: Testing & Launch
User Testing in Week 7
We don't wait for "perfect." We show it to 5 real users.
Not colleagues. Not friends. Users.
We watch them use it. We don't explain. We don't help. We just watch.
Launch is Week 8
Not "soft launch." Not "beta." Launch.
The app goes live. Real users. Real payments. Real feedback.
The Decisions That Make 8 Weeks Possible
We Say No Constantly
Feature request? No. Unless it's required for the ONE core feature.
Design change? No. Unless it's broken.
"Can't we just add..." No. Always no.
We Don't Optimize Prematurely
Code doesn't need to be perfect. It needs to work and be maintainable.
We don't refactor during MVP. We refactor after launch when we know what's actually needed.
We Use Existing Solutions
Authentication? Supabase Auth. Done. Payments? Stripe Checkout. Done. Email? Resend. Done.
We don't build what exists. We build what differentiates.
What Actually Gets Cut
Not features. That surprises founders.
What gets cut:
- User profiles: Basic. Name, email, avatar. That's it.
- Settings pages: Only what we must have.
- Admin dashboards: Founders can use Supabase dashboard initially.
- Mobile responsiveness: MVP is desktop-first unless mobile is the core product.
- Advanced error handling: We handle errors. We don't handle every edge case.
The Honest Timeline
8 weeks assumes:
- Clear requirements (we've done discovery)
- Responsive client (decisions in 24 hours)
- Defined scope (no "just one more thing")
- Availability (engineers not split across projects)
If any of these are missing, add 2-4 weeks.
That's not failure. That's reality.
What We Tell Founders
If you want an 8-week MVP:
-
Be clear about what you're building: Not "a project management tool." But "a tool for small teams to track tasks with deadlines."
-
Be available: We'll have questions. Answer them in 24 hours.
-
Accept constraints: MVP means minimum. You can add features later. You can't get back wasted months.
-
Trust the process: We've done this 30+ times. We know what works.
The Real Answer
8 weeks is possible. But it's not easy, and it's not comfortable.
It requires discipline, clear communication, and willingness to say no.
If you need an MVP in 8 weeks, let's talk. We'll tell you honestly whether your project fits the timeline.
