The 0→1 Craft

The MVP Is a Conversation, Not a Product

MR
Mrinal Rai
5 min read

The MVP Is a Conversation, Not a Product

In the early days of Intugine, we were obsessed with the artifact. We wanted the dashboard to be pixel-perfect, the API documentation to be exhaustive, and the logistics tracking algorithms to be state-of-the-art from day one. We treated the Minimum Viable Product as a final exam—a test we had to pass with flying colors. We were wrong. We spent six months building features for problems our customers hadn't even articulated yet.

If you are building B2B SaaS in India, the reality is stark: your customer doesn't care about your roadmap. They care about the fact that their consignments are stuck at a warehouse in Bhiwandi and they have no idea why. When you approach an enterprise client, an MVP is not a piece of software; it is a hypothesis you are testing through a live dialogue. It is an opening gambit in a long-term negotiation about their operational reality.

Why we get the MVP wrong

Most founders view the MVP as a 'lite' version of their vision. They scale back the features, strip the UI, and hope for the best. That is a tactical error. A truncated version of a bad product is still a bad product. Instead, think of your MVP as a sequence of questions:

  • Can we solve this specific bottleneck in your daily operations?
  • Is this data actionable, or is it just noise?
  • Does this integration save you an hour of manual effort, or does it add two hours of reconciliation?

Each version you ship is a question. Each time a supply chain manager at a Tier-1 FMCG company clicks a button—or refuses to—they are giving you an answer. If you view the product as an artifact, you take rejection personally. If you view it as a conversation, rejection is just data.

The most successful MVPs I have seen do not aim to replace a workflow; they aim to become the most important part of the conversation happening in the control tower.

The shift from features to feedback loops

At Intugine, we once shipped a feature that tracked vehicle health metrics. It was brilliant engineering. It wasn't until we sat with the operations head that we realized the dashboard was useless because their main problem wasn't engine heat; it was driver compliance. We had built a feature for the wrong conversation. The software worked, but the product failed.

To fix this, we stopped shipping features and started shipping provocations. We would show up at a client site with a rough draft of a report and ask, 'If you had this data daily, what would you fire your vendor for?' That question opened doors that a slick demo video never would. The artifact becomes irrelevant the moment you realize that the value is in the insight the software uncovers, not the software itself.

Practical steps for a conversational build

If you want to treat your development cycle as a dialogue, you need to change how you build:

  • Ship before you feel ready, but only if you are present to see the reaction. Never push a release on a Friday evening if you aren't going to talk to your users on Monday morning.
  • Use your product to generate questions. If your users aren't asking you to change things, you aren't shipping anything worth using.
  • Measure 'time to insight' rather than 'number of features.' How quickly can your user get from a chaotic situation to a clear decision?

Stop trying to impress with the depth of your code. Start trying to earn the right to influence your customer's workflow. An MVP is a fragile thing, but a conversation can build a business that lasts a decade. Build the dialogue, and the product will eventually take care of itself.

saaszero-to-oneproductmanagementstartupsscheduled30
Join the Chronicle
Get essays, reflections, and builder wisdom — delivered rarely, crafted carefully.
Continue Reading