Scope
MVP in 7 Days: What That Actually Buys You
What can genuinely be built in a week, what cannot, and how to scope a seven-day MVP so it proves something instead of just existing.
We sell a seven-day MVP, so here is the honest version of what that means — including what it does not include.
What fits in seven days
- One user type, one core job, done properly end to end.
- Sign in, the main flow, a way to pay if payment is the point, and email notifications.
- A real database, deployed on infrastructure you own, with your repo.
- Enough polish that a stranger can use it without a walkthrough.
What does not
- Three user types with different permissions.
- Deep integration with something we do not control (a bank, an ERP, a GDS).
- Offline sync, or anything requiring conflict resolution.
- Migrating your existing data.
How to scope one so it works
| Instead of | Scope this |
|---|---|
| “A marketplace” | One seller listing, one buyer ordering, one payment |
| “A CRM” | Leads in, one pipeline, one reminder that fires |
| “A learning platform” | One course, one student, one completion certificate |
What happens on day eight
You put it in front of ten people. Most teams then discover the second feature they planned is not the one users ask for. That discovery is the actual product of the week — the software is how you get it.
If you would rather build the first version yourself, our guide to building an MVP by chatting with AI covers the same scoping discipline.
Questions
Is a 7-day MVP production ready?
It is real software on real infrastructure that real users can use. It is not hardened for scale or edge cases on day seven — that is the next piece of work, and we will tell you which parts need it.
What do you need from us to start?
Ninety minutes on day one, and someone who can answer questions during the week. Vagueness costs more days than complexity does.
