MVP to MLP: The Real Distance Most Founders Underestimate

5 MINS

Everyone in product talks about shipping the MVP. Almost nobody talks about the painful, unglamorous work that happens between the MVP and the Minimum Lovable Product — the version where the user actually wants the product to exist tomorrow. At Jobizo I lived in that gap for almost two years. It taught me more than any course ever did.

The MVP isn't the product, it's the question

We launched our MVP in record time. It worked. Users could sign up, browse, transact. Investors clapped politely. We started celebrating.

A month later we realised: the MVP was a question, not an answer. It told us whether the core loop existed at all. It didn't tell us whether anyone would come back. The retention numbers were honest about that.

The MVP-to-MLP bridge is built on the second visit, not the first. That's the metric I now look at first when I see anyone's launch.

The full-stack transition nobody puts on a slide

Going from MVP to MLP at Jobizo meant a full-stack transition — the kind of work that doesn't make for a good demo. Migrating tech debt. Rewriting parts of the auth flow. Re-architecting the schema we'd hacked together at launch.

It also meant rebuilding parts of the product that worked, on purpose, because they wouldn't survive the next 10x. That's the call most teams get wrong. They keep extending what works for too long, then have to rebuild it under pressure.

If a flow can't survive 10x usage, replace it before it has to.

If a screen has three feature requests in a row, it's the wrong screen.

If your engineers say "let's just patch it for now" twice in one week, you owe them a refactor sprint.

Investor pitches teach you what your product actually is

Pitching during Pre-Series A was the most clarifying thing that happened to the product. VCs ask the questions your team has stopped asking. Why this market? Why now? Why you? What's the wedge?

Before the pitch, our roadmap was a feature list. After the pitch, it was a thesis. Every feature had to earn its place against the wedge. About a third of the backlog quietly died — and the product got better.

The lesson: even if you're not raising, do a fake pitch every quarter. Make the team defend the roadmap from first principles. The features that survive that conversation are the ones worth building.

What I look for now in any 0-to-1 product

After Jobizo, OYO, Swiggy, and Zomato, here's the checklist I run through whenever I touch a 0-to-1 product:

Is the core loop completable in under 3 minutes by a first-time user? If not, you have a research problem, not an onboarding problem.

Is the second-action conversion above 30%? Below that, no growth channel will save you.

Can the user articulate what the product does in one sentence after using it once? If they can't, neither will their friends.

Does the product feel slightly broken in a way you find charming, or in a way you find embarrassing? Charming is fine. Embarrassing is a launch blocker. The MLP is the version that passes all four. Most "MVPs" you see in the wild fail two of them and ship anyway. That's why the graveyard is so crowded.

What I'm carrying forward

I'm now at Auctane on shipping and logistics products — a different domain, but the same playbook. Find the loop. Make it survive 10x. Pitch it to someone hostile. Ship the version that's lovable, not just minimal.

The bridge between MVP and MLP is where most products die. It's also where the good ones get good.

What Building AI Photography at OYO Taught Me About Useful AI

Hrishi skipped presentations and built real AI products.

Hrishi Swaroop Bhatnagar was part of the March 2026 cohort at Curious PM, alongside 17 other talented participants.