Ask any founder what the hardest part of building a startup is, and you’ll hear the same two answers repeated: “finding product-market fit” and “understanding what users actually want.” These two phrases are so commonly used in startup circles that they almost sound like clichés, yet most early-stage founders fail at both.
The real world is full of products that were beautifully executed, well-funded, and technically excellent-but nobody cared enough to use them. It is not enough to have an idea, a team, and a roadmap. You must have a product that solves a real problem for a real person in a way that feels natural, delightful, and indispensable.
In this article, we’ll explore the deeper truth about product-market fit and how to build products users love-drawing from a modern case study, classic startup mistakes, and relatable examples for the Indian entrepreneurial ecosystem.
How Real User Behavior Reveals the Truth
1. Product-Market Fit Is Invisible When You’re In It
There’s a myth among founders that product-market fit will feel like a thunderclap moment: the day your product “clicks” and the market erupts in applause. Reality is more subtle. Even generational companies have struggled to recognize it early.
A recent example comes from Granola, an AI meeting notes tool founded by Chris Pedrick. When Granola launched, they expected feedback, churn, and uncertainty. Instead, users integrated it into their workflow from day one. But here’s the twist-the founders didn’t recognize they already had product-market fit. They spent six months debating whether the product was “good enough” to matter.
It took time, user interviews, and observing consistent behavior before they realized users were telling them through actions-not words-that the product had become essential.
Interestingly, the same thing happened during Facebook’s early days. Before Facebook became a social juggernaut, the founders were simultaneously experimenting with a file-sharing product. Even they didn’t immediately recognize that the social graph they had built was the thing users desperately wanted. When the world’s best-performing startup founders struggle to detect product-market fit, you shouldn’t expect it to be obvious when it happens to you.
2. What Product-Market Fit Actually Looks Like
Marc Andreessen famously defined product-market fit as:
“being in a good market with a product that can satisfy that market.”
That’s accurate but incomplete for modern startup builders, especially in India, where price sensitivity, behavior change, and trust barriers create unique dynamics.
A more useful variant is:
Product-market fit is when users keep coming back without being pushed.
Here are the real-world signs to watch for:
✔ Users return on their own
You aren’t chasing them with SMS, push notifications, or discounts.
✔ They tell other people
Organic referrals and word-of-mouth multiply faster than paid marketing.
✔ They depend on the product
Not just enjoy it, but need it to complete important tasks.
✔ Feedback shifts from “why should I use it?” to “can you also add this?”
The conversation moves from justification to expansion.
✔ Growth becomes cheaper
Paid CAC drops because existing users become distribution channels.
This pattern showed up in India with products like:
• Notion (India’s startup ecosystem)
• Razorpay (founders → MSMEs → developers)
• Zoho (bootstrapped SaaS → global market)
• WhatsApp (no marketing → mass adoption)
WhatsApp is particularly instructive. In 2013–2016, Indian telcos offered “unlimited WhatsApp packs,” and usage exploded. Nobody did workshops or sales calls to convince users to adopt messaging. That’s product-market fit.
3. Why Talking to Users Is Non-Negotiable
Many first-time founders treat user interviews as a chore. They string together surveys, feedback forms, and analytics dashboards hoping to “understand” the market indirectly.
But real product insight happens through direct, uncomfortable, continuous contact with users. Chris Pedrick calls this the lifeblood of product building.
Talking to users serves two purposes:
1. Shape discovery – understanding what solution is actually needed
2. UI/UX clarity – understanding how users interpret the product
The second point is surprisingly underrated. A product that works academically may break emotionally when placed in a real user’s hands. There’s a famous user test where a participant tries inserting shapes into matching holes. They put a square block in a square hole-success. Then they pick up a circular block and try forcing it into the square hole again. To the designer’s horror, it fits because the holes were larger than expected.
The user wasn’t wrong-the design was misleading.
This problem happens across SaaS and consumer products every day. An Indian fintech founder once told me:
“Users do not behave logically. They behave habitually. If you break habits, you lose adoption.”
For example, early versions of UPI apps failed in Tier-2 cities because users didn’t understand QR codes. Only when UPI apps began integrating tutorials, assisted onboarding, and merchant incentives did adoption scale. Today, India processes more UPI transactions annually than the US processes credit card payments-proof that habit alignment matters.
4. Build Fast, Get Feedback Faster
Speed matters not because time is valuable (although it is), but because memory decays. If you take a month to get user feedback, you won’t even remember why you made certain design decisions.
Early-stage product development should be characterized by:
✔ fast iteration
✔ small experiments
✔ frequent user exposure
✔ ruthless simplification
Granola used an approach common in Silicon Valley but rare in Indian startups: onboarding 2–3 users per day and observing them directly. Once learnings became repetitive, they scaled.
5. Explore vs. Exploit: A Playbook for Product Building
Granola’s development lifecycle can be divided into two strategic phases:
Phase 1: Explore
The team:
• added features
• experimented with interfaces
• prototyped wildly
• collected friction points
The goal in exploration is not perfection. It’s discovery. It is similar to entering a dark forest with a torch-you reveal the map by walking, not by theorizing.
Phase 2: Exploit
Once they identified what truly mattered to users, they:
• cut 50% of features
• simplified the product
• polished the experience
• improved speed and stability
This two-phase approach answers a core startup dilemma:
“When do we stop exploring and start scaling?”
The answer:
When adding new users generates more insight than adding new features.
In India, several successful startups followed this identical pattern:
• Razorpay started as a simple payment gateway for startups → then expanded to payroll, capital, taxation, banking stack.
• Zerodha started as a low-cost brokerage → then polished UX → then built Coin/Kite/Varsity ecosystem.
• Dunzo discovered hyperlocal delivery demand → then optimized fleet, batching, and ops speed.
Exploration finds demand. Exploitation converts demand into a scalable business.
6. Why You Shouldn’t Build Exactly What Users Ask For
User requests are often misleading. Users are experts in their pain-not in the solution. Henry Ford captured this perfectly:
“If I had asked people what they wanted, they would have said faster horses.”
Founders must decode requests into true underlying needs. A SaaS user asking for “more customization” often means “I don’t trust your defaults.” A logistics customer asking for “tracking features” really means “I need peace of mind.”
This gap explains why feature checklists fail. Many Indian founders build “laundry list SaaS” thinking more features = more value. But real product value comes from clarity, not volume.
7. Building Products With Soul
One unique idea from Granola’s philosophy is that products should feel like they have soul-a coherent, intentional, aligned personality. Products that feel disjointed reveal the internal chaos of their creators. Conway’s Law famously states:
“Organizations design systems that mirror their own communication structures.”
When you see a product where every screen feels like it was built by a different person, it’s usually true. Indian founders underestimate how much cohesive design and consistent UX influences adoption-especially in SaaS.
Notion, Figma, Slack, and Cred understood this early: design is not decoration-it is persuasion. It makes users stay long enough to form habits.
8. Behaviors → Not Opinions → Define Reality
One of the most important lessons in product development is this:
“Never rely on what people say. Rely on what people do.”
In user interviews:
• compliments are unreliable
• intentions are unreliable
• opinions are cheap
• behaviors are expensive
A user saying “I would totally use this” is meaningless. A user actually returning tomorrow to use it again is priceless.
This insight transformed how Granola defined a “user.” They counted only users who:
• created a new meeting
• with at least 5 minutes of transcription
• on that day
Everything else was noise.
This prevented the most fatal startup disease:
self-delusion.
Conclusion: The Founder’s Real Competitive Advantage
In the end, product-market fit isn’t luck, magical instinct, or genius. It is earned through:
• relentless curiosity
• obsessive user focus
• humility before the market
• speed of learning
• willingness to cut complexity
Aspiring Indian entrepreneurs often treat funding, ideas, and networks as the keys to startup success. But the real competitive advantage lies elsewhere:
The founders who learn fastest win.
If you can talk to users, observe their reality, ignore empty praise, ship quickly, iterate ruthlessly, and simplify continuously-you increase your odds dramatically.
Product-market fit is not a finish line. It is a transition-from search mode to scale mode. And building products users love is not a one-time effort. It is a lifelong practice.
