The MVP Question: How Basic Is Too Basic, And Why It Depends on Who's Buying
There is a version of lean startup thinking that has done real damage to a generation of founders.
It goes like this: ship fast, ship rough, fix it later. The MVP is supposed to be embarrassing. If you are not ashamed of it, you launched too late.
Reid Hoffmann said it. Thousands of accelerator mentors repeated it. And a lot of first-time founders took it as permission to build something that did not actually work, did not actually solve the problem, and did not actually deserve a second look from the people they handed it to.
Here is what that advice misses. There is a difference between minimum and poor. And there is a difference between a B2C app and a B2B enterprise tool. And there is a very important difference between a market that will tolerate friction and one that will not.
Getting these wrong does not just slow you down. In some contexts, it ends the conversation permanently.
Minimum Viable Does Not Mean Minimum Acceptable
The word that matters in MVP is not minimum. It is viable.
Viable means it works. It means the person who uses it gets the outcome they came for. It means the core promise of the product is delivered, even if everything around it is stripped back, manual, or rough around the edges.
What you cut in an MVP is scope. What you cannot cut is function.
A food delivery app that crashes on checkout is not an MVP. It is a broken product. A SaaS dashboard that loses data is not lean. It is a liability. Minimum means you have removed every feature that is not essential. It does not mean the essential features are half-built.
This is the distinction Gate 6 of the Entreprenerds curriculum is built around. Before you design your MVP, you identify your key assumptions. Before you build, you test them. The MVP is the vehicle for that test, and a vehicle that does not move cannot tell you anything.
B2B and B2C Are Not the Same Problem
This is where the "ship it rough" advice causes the most damage.
In B2C, you are often selling to individuals making low-stakes decisions. A consumer trying a new app has low switching costs and low expectations of polish at the early stage. If your product is interesting enough, they will tolerate friction. If it breaks, they might come back. The feedback loop is fast and the cost of a bad first impression, while real, is recoverable.
In B2B, you are selling to a professional making a decision on behalf of an organisation. The stakes are different. The scrutiny is different. The Decision Making Unit — the economic buyer, the champion, the end user — is evaluating not just your product but your credibility as a vendor.
If your MVP crashes in a demo, you do not get a second meeting. If your data handling is visibly insecure, the procurement team kills the conversation. If the interface looks like it was built in a weekend, the economic buyer questions whether you will still be around in twelve months.
This does not mean your B2B MVP needs to be a finished product. It means the parts you show need to work flawlessly, and the parts you have not built yet need to be invisible. Know what your buyer will see and make that exceptional. Everything else can wait.
You Do Not Always Get a Second Shot
The MVP-as-learning-tool framing assumes the market is patient. Some markets are not.
Enterprise procurement cycles run quarterly or annually. If you get a meeting with the right Economic Buyer and your product does not meet a basic standard of reliability, you are not in the running again until next cycle, if at all. The person who advocated internally for giving you a chance has used up political capital. They are unlikely to do it twice.
Consumer markets have their own version of this. In categories where trust is the product, fintech, health, education, a poor first experience does not just lose a user. It creates an active detractor. And in communities where your target customers talk to each other, which they always do at 19–24, one bad experience travels fast.
The question to ask before you launch is not: is this good enough to ship? It is: is this good enough to survive first contact with the people whose opinion matters most?
How to Balance It
This is the practical question. How do you hold the tension between moving fast and meeting the standard?
Start with your riskiest assumption, not your full feature list. Your MVP should be designed to test one thing — the assumption that, if wrong, collapses the business. Build only what is needed to test that. Everything else is scope you do not need yet.
Define your MVBP before you define your MVP. The Minimum Viable Business Product is the smallest version of your product that a real customer will pay for, use, and return to. Use this as your quality floor. If what you are building would not clear that bar, you are not building an MVP — you are building a prototype. Prototypes are internal. MVBPs face the market.
Match your quality standard to your buyer's tolerance. A consumer fintech product needs bank-level security from day one. A B2B analytics tool needs clean data and a reliable export function. A service business needs consistent delivery and a working payment process. Know your buyer's non-negotiables and treat those as fixed constraints, not future features.
Use manual delivery before automation. Some of the best MVPs in history were not products at all. They were founders doing manually what the product would eventually do automatically. This is not a shortcut — it is the fastest way to learn whether the outcome you are promising is actually worth having.
The Real Lesson
The MVP is not a low bar. It is a precise bar.
It is the minimum required to generate real evidence about whether your product creates real value for real people. Set it too low and the evidence is worthless. Set it too high and you have spent capital validating things that did not need validating yet.
Gate 6 of the Entreprenerds curriculum teaches you to find that bar - to identify your assumptions, test them deliberately, and build only what the test requires.
The founders who get this right do not ship embarrassing products. They ship precise ones.
Gate 6: Design & Build Your Product is part of the Entreprenerds 10-Gate curriculum — a structured path from first idea to launched venture. Explore the full curriculum at entreprenerds.uk
