Loading course details…
Fetching the latest program information for you.
Fetching the latest program information for you.
The hardest problem in Indian product work is that people are polite. They will tell you they like it and never come back. Fifty days of discovery that separates behaviour from stated preference, MVPs where trust is complete before features are, and thresholds set before you measure rather than after.
For founders who keep hearing "this is great" and keep seeing flat retention.
Twenty customer conversations, all encouraging, none of which predicted that nobody would sign up.
Structured problem interviews that separate observed behaviour from aspirational answers, and synthesis that grades confidence accordingly.
Six months of building, a feature list nobody asked for, and still nothing in a user's hands.
A scoped MVP where the core is functional and trust and payment are complete, because in India that is what decides whether anyone transacts.
A vague sense that things are working, based on a chart that only goes up because spend does.
Validation thresholds committed to before you measure, and cohort and funnel analysis read for cause rather than comfort.
Whoever argued hardest last week decides what gets built next.
RICE, ICE, value-effort and Kano applied with a real confidence bar, and must-haves sequenced before delighters.
Ten modules of five lessons each, from customer discovery through MVP and testing to product-market fit, prioritisation and analytics.
Built for founders who need decision-ready tools, not passive reading.
One per lesson, saving your work — interview guides and synthesis boards, MVP scoping canvases, prioritisation scorers, cohort and funnel analysers.
Interviews designed around aspirational-response bias, segment prioritisation across metro and Tier 2/3, and usability testing recruited over WhatsApp with neutral facilitation.
User stories with acceptance criteria covering language, device, connectivity and trust — the constraints that decide whether an Indian user completes a flow.
Jobs-to-be-Done validation with pre-committed thresholds and SOM-first market sizing, so a result cannot be reinterpreted into a yes after the fact.
Clean, verified, segment-aware tracking with funnel and cohort analysis, and a growth experiment cadence rather than a backlog of untested ideas.
Discovery is not a phase you finish. Come back at each new segment, each new market and each new product line.
Real lessons from the course. Each one opens by telling you exactly what you will have finished by the end of it.
The Art of Problem Interviews in India Morning briefing: why this is Day 1, and why most founders skip it You are about to spend the next 50 days building a product. The single most expensive mistake you can make is the one you make today…
TAM SAM SOM Analysis for Indian Markets Morning briefing: the question every investor asks, and most founders answer badly You have a validated problem and a defined beachhead segment. Today you answer the question that decides whether…
Feature Prioritization for Indian Products Morning briefing: the discipline of saying no Validation is complete. You know the problem, the segment, and the single job your product will be hired to do. Now the temptation begins, and it is…
Low-Bandwidth Product Design for India Morning briefing: your product runs on the network your users have, not the one you have Your MVP is live and generating real behaviour. Module 4 is about making the product genuinely work for Indian…
User Testing Fundamentals for India Morning briefing: watching beats asking, especially in India Your iteration loop (Day 20) runs on analytics and feedback — the what and the volunteered why. User testing gives you the deeper, harder-won…
Understanding Product-Market Fit Morning briefing: the thing every startup is really chasing For thirty days you have built discovery, validation, a product, and a team that improves itself. Today, opening Module 7, you turn to the…
Prioritization Frameworks for Indian Startups Morning briefing: prioritisation is the core discipline of a resource-constrained startup You have a validated, scaling product (Module 7). But a scaling Indian startup faces a permanent,…
Product Analytics Fundamentals Morning briefing: the measurement foundation under everything For forty-five days you have measured things — PMF (Module 7), feature impact (Module 8), growth experiments (Module 9). Every one of those…
Eight capabilities the course is built to leave you with.
Why it matters: Run a repeatable customer discovery system for the Indian market — structured problem interviews that separate behaviour from aspirational-response bias, segment prioritisation across metro and Tier 2/3, and insight synthesis that grades confidence on observed behaviour rather than stated preference.
Why it matters: Validate problems using the Jobs-to-be-Done framework calibrated for Indian consumers, with pre-committed validation thresholds set before measuring, defensible SOM-first market sizing that avoids informal-economy and digital-overestimation TAM traps, and a go/no-go decision grounded in evidence.
Why it matters: Produce product requirements and a living roadmap — user stories with acceptance criteria covering language, device, connectivity, and trust; a now-next-later roadmap oriented around outcomes with honest confidence levels; and audience-specific views that align stakeholders without over-committing to dates.
Why it matters: Design and run a usability testing plan for India — small, segment-representative samples recruited over WhatsApp, neutral facilitation that resists rescuing, an observed-versus-stated note discipline, and prioritised, evidence-backed findings that convert into shipped changes.
Why it matters: Establish an agile operating rhythm suited to Indian teams — a fitted methodology (Scrum, Kanban, or Scrumban), holiday- and festival-aware capacity planning, hierarchy-aware estimation and retrospectives, and velocity read as a planning tool rather than a performance metric.
Why it matters: Build a prioritisation and pricing system — RICE/ICE/value-effort/Kano applied with a high confidence bar and must-haves-before-delighters sequencing, plus India-native pricing (researched willingness-to-pay, UPI/EMI-aware models, INR-native levels) tested behaviourally rather than by stated intent.
Why it matters: Stand up product analytics and a growth experiment cadence — clean, verified, segment-aware tracking; funnel and cohort analysis read for curve shape; a high-velocity, India-calibrated experiment loop across acquisition, activation, retention, and monetisation; and a data-driven culture that lets evidence override opinion.
Indicative market rates for the work this course teaches you to do in-house. Ranges vary by city, agency and scope — treat them as a comparison, not a quote.
What founders pay for this, piece by piece
Price is inclusive. No GST is charged.
Scope an MVP and build a prototype fit for Indian users — a trust-and-payment-complete core (functionality at ~70%, trust at 100% — directional), the right MVP type (manual, concierge, Wizard-of-Oz, or WhatsApp-first), and mid-range Android as the design baseline for low-bandwidth, data-cost-aware conditions.
These outcomes are educational and directional; figures such as the 70/100 MVP split are illustrative rules of thumb, not standards. Where pricing, payments (UPI/EMI), data-handling, or labour/HR practices touch regulation, verify the current position on the official portal (e.g. RBI, MCA, DPIIT, GST) or with a qualified professional before acting.
Fifty days from encouraging conversations to evidence, a scoped MVP, and thresholds you set before you measured.
1 year access · 50 lessons · 50 interactive tools · 3-day refund