How to build an MVP in 6 weeks (and what you have to cut)
A 6-week MVP isn't a marketing slogan — it's a constraint that forces good decisions. Here's the week-by-week playbook we use to ship real products in 42 days.
Why 6 weeks is the right deadline
Most teams treat the MVP timeline as something to negotiate. They shouldn't. A 6-week deadline isn't a stretch goal — it's a forcing function. It's short enough to keep scope honest and long enough to ship something a real customer will pay for.
Twelve-week MVPs become twenty-week MVPs. Six-week MVPs ship in eight if something explodes. The difference is in the cuts, not in the optimism.
Week 0: Pick the wedge, not the platform
An MVP that tries to be a platform is a 9-month project wearing an MVP costume. Pick the single workflow that demonstrates your value, write it on one page, and put a paywall in front of it.
What "wedge" actually means
A wedge is the smallest piece of your product that someone would pay for tomorrow. Not the most complete version. Not the most defensible. The smallest one that produces money.
Week 1: Design the spine
Three days. Not three weeks. The deliverable is not pixel-perfect screens — it's flows that show how a real user moves from "signed up" to "paid". Edge cases get sketched. Polish waits.
What to design
- The signup-to-first-value flow
- The pricing/billing flow
- The one workflow that delivers your wedge
What to skip
- Settings pages no one will visit before month six
- Multi-step onboarding that "feels premium"
- Custom design systems before you have a design language
Weeks 2–4: Build like adults
An MVP is not an excuse for bad code. The codebase your first engineering hire inherits should be typed, modular, and observable from the start — see our take on web platform engineering for what that looks like in practice.
The fastest way to wreck a 6-week timeline is to write 12 weeks of code in 4. So we sequence ruthlessly:
- Week 2: auth, tenant model, billing scaffolding
- Week 3: the wedge workflow end-to-end
- Week 4: onboarding, empty states, the unhappy path
Week 5: Onboard your first 10 customers
If onboarding requires a Loom and a calendar invite, that's fine — but you should be sitting next to those first customers learning what breaks. Every bug they hit teaches you which 1% of remaining work matters.
Week 6: Charge real money
An MVP without payment is a prototype. The single most informative event in your company's life is the first time someone hands you a credit card. Don't postpone it. Wire Stripe billing from day one and let week 6 be the moment your bank account proves the thesis.
What we always keep
- Auth, billing, and analytics — wired from day one
- Observability you'd want at 10x the traffic
- A clean codebase that hire #1 won't quit over
The hard part isn't the deadline
It's the cuts. Six weeks is enough — if you spend it on the things that matter and get ruthless about the things that don't.
If this is the engagement you are trying to run, our Build your MVP work follows the same discipline. Tell us what you are shipping and we will reply with a written scope.