
Launch a Minimum Viable Product
Let me ask you something.
Have you ever spent months — maybe even years — perfecting a product… only to launch and hear crickets?
You’re not alone.
In my experience working with hundreds of founders across India, the US, and Southeast Asia, the #1 mistake early-stage startups make is building before validating.
That’s where the magic of an MVP — a Minimum Viable Product — comes in.
But here’s the real kicker: most MVPs fail not because they’re too small… but because they’re not built to sell.
Let’s change that.
A Minimum Viable Product is not a prototype.
It’s not a “beta” version of your final product either.
An MVP is the simplest, fastest version of your product that delivers real value to real customers — and helps you learn what works.
Think of it as your startup’s first date with the market. It’s your chance to say:
“Here’s what I think solves your problem. Am I right?”
Let’s be brutally honest: launching an MVP is not about building, it’s about validating.
Here’s what kills MVPs:
Building for months without user feedback
Solving problems no one cares enough to pay for
Adding features based on assumptions, not data
Launching to zero users and expecting traction
“If you’re not embarrassed by the first version of your product, you’ve launched too late.”
— Reid Hoffman, LinkedIn co-founder
So, how do you build an MVP that actually sells?
Let me show you.
Step-by-Step Guide to Launching an MVP That Actually Sells
Before you write a single line of code or design a single screen, ask:
“What painful problem am I solving — and for whom?”
Your MVP should address a real, urgent, high-frequency problem.
No fluff. No “nice to have” features.
Interview at least 20 potential customers.
Ask open-ended questions: “What frustrates you about X?”
Look for recurring phrases like “I wish there was a faster way to…”
Example:
Before launching Dunzo, the founders validated that urban Indians desperately needed instant errand support — not just grocery delivery.
Your MVP isn’t just a product — it’s an experiment.
So, define what success looks like.
What behavior will confirm this product solves the problem?
What conversion rate do we expect from landing page → signup → usage?
Signups or pre-orders
User activation (Do they actually use it?)
Retention (Do they come back?)
Willingness to pay
“Build it. Measure it. Learn from it.”
— Lean Startup Methodology
Here’s the secret: Your MVP doesn’t even need to be a product.
Yes, you heard that right.
Here are popular MVP types that require minimal investment:
Example:
Dropbox launched with a 90-second video before a single line of code — and got 70K+ signups overnight.
You don’t need a dashboard. Or AI. Or 15 features.
You need one thing: a core function that solves the problem.
One core action (e.g., “Order a service”)
One audience (don’t try to please everyone)
One channel (launch where your audience already hangs out)
“Don’t scale before product-market fit. Nail it before you scale it.”
— Marc Andreessen
Don’t wait to perfect it.
Get real feedback from real users.
LinkedIn groups or Twitter threads
Subreddits (like r/startups or r/IndiaStartups)
WhatsApp business groups
Product Hunt or BetaList
Cold email with a value-first pitch
Example:
An Indian SaaS startup got 500+ signups in a week by sharing a waitlist page on founder WhatsApp groups.
Here’s the golden rule:
Treat every user interaction like a classroom.
Ask:
What feature did they expect but didn’t find?
What confused them?
Would they recommend this to a friend?
Use tools like:
Typeform or Google Forms (post-use surveys)
Hotjar (user interaction heatmaps)
Calendly + Zoom (for interviews)
And remember: Every “no” is a clue to your next iteration.
Yes, your MVP can (and should) earn money.
“If no one will pay for your MVP, you haven’t validated your idea — you’ve validated that people like free stuff.”
Start with a limited-time founder deal, early-access discount, or even a one-time payment.
If you're offering real value, users will pay — even if it’s imperfect.
Example:
SaaS startups like Superhuman and Notion began by charging early adopters before building full-scale automation.
Problem: High-value credit card users in India didn’t get rewarded for good behavior.
MVP Approach:
Kunal Shah launched Cred with a referral-only beta, a clean UI for bill payments, and massive waitlist buzz — without complex reward logic.
Result?
Early validation, user obsession, and a product that grew virally before they even raised their Series A.
Solves a real pain
Built for a specific user
Delivers one core value
Tested with real feedback
Designed for iteration
Has monetization potential
If you can tick those, you’re not just building an MVP — you’re building momentum.
Let me leave you with this:
You’re not launching a prototype.
You’re launching a hypothesis, a learning loop, a conversation with your market.
So build lean. Launch early. Learn fast.
And whatever you do, build something people can’t live without.
Are you launching an MVP soon?
Share this article with your co-founder or team — and use it as your launch playbook.
Follow us on Google News