How to Scope an MVP in 48 Hours
Most founders overbuild their MVP. They want the analytics dashboard, the multi-tenant role system, and the dark mode toggle before they have a single paying customer. Here is the exact framework we use to strip a product down to its core value proposition.
The "One Thing" Rule
Your MVP should do exactly one thing remarkably well. If you are building a tool for scheduling tweets, the MVP should literally just schedule tweets. Not analyze them, not generate them with AI, just schedule them.
When a client comes to us with a 20-page feature document, our first exercise is the highlighter test. We take a yellow highlighter and say: "Highlight the ONE feature that, if removed, makes this product completely useless." Everything else goes into Phase 2.
Timeboxing the Scope
We enforce a strict 48-hour scoping period. Here is how we break it down:
- Hours 0–12: Brain dump. The client explains everything they want. We write it all down without filtering.
- Hours 12–24: The purge. We aggressively cut features. We ask "Can we do this manually behind the scenes for the first 100 users?" If yes, it is cut from the code.
- Hours 24–36: Technical mapping. We map the remaining features to a database schema and API routes.
- Hours 36–48: The handshake. We present the stripped-down scope. It is usually 30% of the original request, but it can be built in 4 weeks instead of 4 months.
"If you are not embarrassed by the first version of your product, you've launched too late." – Reid Hoffman
Handling the "But what about..." objections
Founders get nervous when you cut features. "But what if a user forgets their password?" Use an email magic link login—no password reset flow needed. "What if they want to cancel their subscription?" Tell them to email you.
Write code for the happy path first. Build the administrative tools only when the manual pain becomes unbearable.
Conclusion
Scoping an MVP is an exercise in discipline, not engineering. By forcing constraints and embracing manual processes early on, you save thousands of dollars and months of development time. Ship the core, see if people care, then build the rest.
Frequently asked questions
- How long should it take to scope an MVP?
- At Aqib Ops we cap MVP scoping at 48 hours of focused work, split across brain-dump, feature purge, technical mapping, and a final scope handshake with the founder.
- What is the 'One Thing' rule?
- Your MVP should do exactly one thing remarkably well. Highlight the single feature that, if removed, makes the product useless — everything else moves to Phase 2.
- How do you decide what to cut?
- We ask 'Can we do this manually behind the scenes for the first 100 users?' If yes, it's cut from the build and replaced with a human in the loop until the manual pain becomes unbearable.
- What about password resets, cancellation flows, and edge cases?
- Replace them with magic-link login and 'email us to cancel.' Build administrative tooling only when the volume of manual work makes it cheaper than not having it.
- How long should an MVP take to build after scoping?
- A properly scoped MVP should ship in roughly 4 weeks. If it can't, the scope is still too big — go back and cut more.