A realistic look at how we take a rough concept to a usable, shippable product in six weeks — and what we deliberately leave out.
Six weeks isn't a magic number — it's a forcing function. A tight, fixed window keeps everyone honest about what's truly essential. Here's roughly how the weeks tend to break down when we take an idea to a working MVP.
Weeks 1–2: clarity
We spend the first two weeks turning a fuzzy idea into a sharp one: the single core problem, the one user who feels it most, and the smallest thing that would actually help them. We design the critical flows and make the hard technical calls early, while they're still cheap to change.
Weeks 3–5: build
Now we build the spine of the product in short, visible iterations. You see something clickable by the end of week three — not a polished thing, but a real one. Each week it gets sturdier and the rough edges come off.
- Build the one flow that defines the product first.
- Use boring, proven technology so time goes into the product, not the plumbing.
- Ship to a real environment from day one — no big-bang integration at the end.
An MVP isn't a smaller version of the product. It's the fastest way to learn whether the product should exist.
Week 6: harden and hand off
The final week is for the unglamorous work that makes a demo into a product: error states, empty states, analytics, and a clear path for the next phase. What we deliberately leave out is just as important — anything that doesn't serve the core loop waits for the roadmap.