MVP: Not an Incomplete Product, but a Discipline
An MVP is not an incomplete product, it is a discipline. What do you build in the first version of an app, and what do you defer? With real examples and filter questions.
MVP — "Minimum Viable Product". But most people read this as an "incomplete product". They read it wrong. An MVP is a discipline. It is the honest answer to this question: "What is the smallest set of features this app absolutely needs in order to survive?" The answer is not "incomplete", it is focused. An MVP represents courage, not weakness.
The Wrong Way to Think About an MVP
"Let's keep features minimal in the first version and add more later." — This is procrastination, not discipline.
"We're just testing for now, it's fine if it doesn't quite work." — An MVP will work, just within a narrow scope.
"It has to have everything the competitors have." — The essence of an MVP is the exact opposite — picking the single most important thing the competitors do.
The Right Way to Think About an MVP
"What is the primary value of this app? We deliver only that value."
"Does the user see a benefit within the first 30 seconds?" — If yes, the MVP is ready.
"If I remove this feature, does the core purpose of the app break?" — If no, the feature should be deferred.
Example: How to Choose the MVP for a Delivery App
A hypothetical full-version delivery app might include these features: user accounts, social login, email verification, saved addresses, current location, restaurant listing, category filtering, search, menus, options, cart, payment (Iyzico + cash on delivery), installments, wallet, courier tracking, live map, ratings, reviews, favorites, coupons, campaigns, loyalty program, notifications, order history, restaurant panel, courier app, admin panel. This full version takes 8-12 months to build.
The right MVP version looks like this: email login (social login later), a single address (multiple addresses later), restaurant listing and basic search (category filter later), a simple menu and cart, Iyzico only (cash on delivery later), a static screen for courier tracking ("on the way") — live map later, ratings and favorites all later, notifications only for order status, restaurant panel limited to an order list screen. This MVP takes 10-12 weeks to build. And the MVP delivers value to the user — they can pick a restaurant and order food. Everything else is decoration.
3 Filter Questions for MVP Discipline
Ask these in order for each feature:
- Does the app do its job without this feature? If yes, defer it.
- Is this feature the first source of revenue? If no, defer it.
- Will adding this feature take more than 2 weeks? If yes, simplify it or defer it.
A feature that passes all three filters goes into the MVP. One that doesn't goes into v2.
What Happens After the MVP?
In the 4-6 weeks after the MVP goes live, you collect real data: which screens users enter, which features they use, where they get stuck. What to build in v2 is decided based on this data — not on guesswork. In most MVPs, half of the features people said they'd "add later" are never added — because user data shows they were unnecessary. That is months saved.
Who Needs MVP Discipline?
New founders: With a limited budget, the fastest path to learning is an MVP.
Corporate innovation projects: An MVP is used to take a small risk inside a large company.
Those pivoting a product: When changing direction, you test with an MVP instead of pouring resources into a full product.
Common Mistakes When Building an MVP
Not putting the scope in writing. Saying "let's build an MVP" is not enough — which 5 features it will have must be written down. Otherwise, the scope keeps expanding during development.
Trying to perfect the MVP. By definition, an MVP can be rough — being "good enough" for the first user is sufficient. Leave the polishing for v2.
Not waiting for user feedback. Don't start planning v2 immediately after the MVP ships. First collect real user feedback.
Presenting the MVP as a "beta". Users don't care about the difference between "MVP", "beta", and "finished product". For them there is only "an app that helps me" or "an app that doesn't". The MVP has to work.
MVP Recommendations for the Turkish Market
Iyzico or PayTR is an MVP requirement. Launching into the Turkish market with Stripe alone is hard — without a local payment system it's hard to build trust.
Turkish language support must stay in the MVP. You can't run tests in Turkey with an English-only interface.
Cash on delivery can be dropped from the MVP. But online payment must work.
A KVKK privacy notice must be in the MVP. It cannot be deferred.
App Store and Google Play descriptions should be written in Turkish.
Conclusion
An MVP is not weakness, it is courage. It is understanding a lot by building a little. The sentence "I want all of it" usually leads to the same result as "I want none of it" — because an app that does everything either becomes too expensive, ships too late, or is of no use to anyone.
CU Studio starts every new project with MVP discipline. The scope document clearly spells out what comes now and what comes later. If you'd like to talk about your project: hello@custudio.com.tr