Mohalla
Project Doc

Urban Indian residents have no reliable, structured way to communicate with their neighbors. Every existing tool fails the neighborhood use case in a different, damaging way.

Four primary archetypes shaped every product decision — from onboarding friction to feed structure to marketplace prioritization.

A structured breakdown of the MVP requirements, user stories, and technical scope that governs the Mohalla prototype build.

Seven features. Each chosen because it directly answers a critical user pain point. Each validated against one question: Does this make a resident's neighborhood life better?

Five primary navigation areas, accessible from a persistent bottom nav bar. Designed to match the mental model of how residents actually move through community life.

Mohalla occupies a currently uncontested white space — verified, India-first hyperlocal community. No existing product delivers the full combination of neighborhood identity, local commerce, and community infrastructure.

A product case study examining the design decisions, PM methodology, and market timing that make Mohalla defensible.

The original hypothesis was clear: urban Indian residents — especially in apartment societies — have no dedicated structured platform for neighborhood communication. The void is filled by chaotic WhatsApp groups, inefficient notice boards, and informal word-of-mouth. This is a structural, tool-based problem — not a cultural one. Indians deeply want community. They've just never had the right product to experience it digitally.

Research across 4 user archetypes (apartment residents, working parents, PG students, local service providers) surfaced consistent pain: WhatsApp overload, no trust layer, no service discovery, poor event communication. The key insight: the problem is not desire — it is tooling. People want neighborhood community. The product just doesn't exist yet.

Three concepts were evaluated: a society management app (too utilitarian — limited daily use), a local marketplace app (too transactional — no community layer), and a general social network (too broad — no differentiation). Mohalla won by combining all three under one location-verified umbrella. The Nextdoor model validated the concept at scale. Mohalla's differentiation is its India-first architecture: apartment society structure, multilingual design, RWA integration, and hyperlocal commerce — none of which Nextdoor can replicate.

Every feature was evaluated against one question: Does this directly make a resident's neighborhood life better right now? Features that required baseline community density to deliver value (AI moderation, admin dashboard, multilingual UI) were explicitly deferred. The resulting MVP is the minimum complete neighborhood experience: join → verify → post → explore → connect. Nothing more, nothing less.

The GTM is deliberately narrow and focused. The goal in Phase 1 is not millions of scattered users — it is to activate whole neighborhoods at once, creating immediate community value.

Mohalla's engagement is built on hyperlocal relevance — every notification, every post, every feature is anchored to the user's actual neighborhood. This is the core retention mechanism.

North star and supporting metrics designed around community activation — not vanity growth numbers.

Revenue mechanisms must feel like genuine value additions — never intrusive ads or paywalls. Zero monetization in MVP. Revenue introduced only after sustainable engagement is established.

Every risk was identified and paired with a specific mitigation before a single screen was designed.

From MVP to a fully featured neighborhood operating system — each phase unlocks only after the previous one achieves its activation threshold.