Stop Calling It an MVP

I need to get something off my chest.

That thing your team has been building for the last nine months? The one with the custom design system, the real-time notification engine, the admin dashboard that only two people will ever see, and the OAuth integration with four different providers "just in case"?

That's not an MVP. That's a full product with the word "minimum" taped over the logo.

The Viability Trap

Here's where teams get stuck: they confuse "viable" with "complete." An MVP doesn't need to be something you'd put on the App Store homepage. It needs to answer exactly one question: does anybody actually want this?

If you can't answer that question in under eight weeks of build time, you're not scoping an MVP. You're scoping a product and lying to your stakeholders about the timeline.

What Minimum Actually Means

I worked with a fintech startup last year that wanted to "validate" a new lending product. Their MVP spec was 47 pages. Forty-seven. It included fraud detection, a custom credit scoring model, and a white-label partner portal.

We threw the spec away. Built a landing page, a Typeform, and a Slack integration that pinged the founder every time someone applied. Took four days. They had their answer in two weeks — and it wasn't the answer they expected, which saved them about $800K in build cost.

That's what minimum means. It means you're embarrassed by it. If you're not a little embarrassed, you over-built.

The Real Problem

The MVP theater happens because nobody wants to be the person who shipped something ugly. Product managers want to show polish. Engineers want to show craft. Designers want to show taste. Executives want to show the board something impressive.

None of those people want to show something that looks like it was built in a weekend — even if that's exactly what the business needs.

So the "MVP" scope creeps. Eight weeks becomes fourteen. Fourteen becomes six months. And by the time you ship, the market has moved, the budget is burned, and you've validated nothing except your team's ability to over-engineer.

The Fix

Next time someone says "MVP," ask them one question: what is the single cheapest experiment that would tell us if we're wrong?

If the answer involves a custom backend, you're already off track.