The 3-week rule: how we scope an MVP that actually ships
Jeriel Isaiah Layantara
CEO & Founder of Round Bytes
A founder walks in with a 40-feature spreadsheet. Three months later, nothing has shipped. Sound familiar? This is the single most common pattern we see, and it almost always traces back to a scoping failure at week zero.
Our rule is simple: if we can't demo a working version of the core loop in 3 weeks, the scope is wrong.
Not the whole app. Not every edge case. The core loop, the one thing a user will do repeatedly that defines whether the product has a reason to exist. For a marketplace, it's "list and buy." For a SaaS, it's "connect and get value." For Tucope, it was "find what's nearby and connect." For Optserv, it was "run a clean payroll cycle without spreadsheets."
The 3-week rule forces three healthy conversations:
- What is the actual loop? Not the roadmap. Not the pitch deck. The user's muscle memory.
- What can we fake? Payments can be Stripe test mode. Admin can be a Notion board. Onboarding can be a Calendly.
- What do we genuinely need to learn? MVPs aren't about features, they're about retiring the riskiest assumption.
We've shipped products in two weeks. We've spent six months on a v1. The difference is almost never engineering capacity, it's clarity at scoping.
If you're about to start building something and your spec is 20 pages long, send us a note. We'll help you cut it down to two.
