The Six-Week MVP: How to Scope Ruthlessly

The most expensive words in software are "while we're at it." Every failed MVP we've rescued died the same death: a six-week idea scoped into a six-month build.

One job, done excellently

Your MVP has one job: validate the riskiest assumption about your business. Write that assumption down. Every feature that doesn't test it gets cut — not postponed to "phase 2," cut, because phase 2 will be redesigned by what you learn.

The walking skeleton

Week one ends with a deployed app: auth, one core screen, CI/CD, monitoring. It does almost nothing — but it does it in production. Every week after adds muscle to a skeleton that already walks. Integration risk collapses when integration happens first, not last.

Buy everything that isn't your product

Auth is a solved problem. Payments are a solved problem. Email, file uploads, analytics — solved. Your differentiation lives in exactly one place, and every hour spent rebuilding solved problems is an hour stolen from it.

Weekly demos, no exceptions

A demo every Friday to real stakeholders. Not screenshots — clicking through the deployed product. This cadence surfaces misalignment in days instead of months, and the discipline of "demoable every week" quietly enforces good scoping.

What six weeks buys you

Not a polished product — a validated one. Real users, real behavior, real evidence for your next investment decision. That evidence is worth more than any feature you cut to get it.