Entrepreneurial Hypothesis Testing — Notes

IIM Bangalore BBA in Digital Business and Entrepreneurship · Term 4 · 5 modules, 106 topics.

Module-0 Introduction to the Course

Introduction to the Course

This module introduces Entrepreneurial Hypothesis Testing — a course that moves beyond theory to require each student to take one idea seriously and build a real startup during the term. The core message: entrepreneurship can be taught as a systematic method, just like the scientific method. Success depends not on the initial idea but on disciplined execution and learning from real customer interactions.

The Entrepreneurial Method: Why This Course Exists

Creative destruction — the process by which entrepreneurs replace old industries with new ones — has produced nearly every convenience we take for granted (laptops, air conditioners, cameras). However, entrepreneurship was long treated as an art accessible only to the lucky or uniquely gifted. That is changing. Just as the scientific method democratised discovery, an entrepreneurial method can be unpacked and taught, reducing waste and heartache while increasing the probability of building something valuable.

Not everyone who learns the method will launch a unicorn (just as not every science PhD becomes a Nobel laureate), but understanding the method equips you to make better decisions under uncertainty.

Swimming analogy – you can learn stroke technique and breathing theory on land, but you must get into the water to actually swim. Similarly, you can study frameworks in class, but the greatest learning occurs only when you start working on a real idea — treat this course as an experiment.

No prior idea is "good" or "bad" at the start. The way you systematically develop the idea — testing, learning, pivoting — determines its eventual viability.

Traditional approach	Entrepreneurial method approach
Focus on solution/features first	Start with a large problem, then narrow down
Resist change in plans	Expect to pivot; "start again" is part of the process
Keep idea secret	Talk freely – execution matters, not secrecy

Key takeaways

Entrepreneurship is not magic; it can be taught as a repeatable method.
Theory alone is insufficient – you must take action (start a real venture).
No idea is inherently good or bad; systematic development reveals its value.
The goal is learning, not initial success.

Course Assignment: Build a Real Startup

Pick one startup idea and work on it throughout the course. This is not a simulation — you are expected to have paying customers by the end. The experience will change how you see commerce, whether you eventually start your own company, join a startup, or work in a large corporation.

Rules for picking your idea:

Think problem-first. Do not list features or imagine a perfect solution. Start with a large problem that many people share.
Keep it simple. Complex solutions often cause failure. Avoid "my future app will do X, Y, Z".
Nobody will steal your idea. Talk about it freely. Ideas are cheap; execution is everything.
Be ready to pivot. If your initial approach isn't working, start over — that is the nature of entrepreneurship.

Exam tip: The single most important thing to get out of this course is evidence of execution — something you built, real conversations with customers, and ideally revenue. That learning stays with your CV forever.

Key takeaways

The assignment is real: build a startup with paying customers during the course.
Begin with a broad problem, not a narrow solution.
Embrace constant iteration – failure is fine, learning is mandatory.
Execution trumps the idea; openness speeds up learning.

Module-1 From Idea to Testable Hypothesis

Activity: Reflection on Startup Failure

It is commonly stated that 90% of startups fail. Before progressing to formal frameworks, students are prompted to reflect on why startups fail — using only their own knowledge, without external research. The goal is not correctness but to surface collective intuitions.

This exercise sets the stage for the module: transforming raw ideas into testable hypotheses requires first understanding the common pitfalls.

Key takeaways

The 90% failure statistic is a widely cited starting point.
Personal reflection and peer discussion build a foundation for later analytical tools.
No single correct answer is expected; the exercise reveals diverse perspectives on entrepreneurial failure.

What is a Startup?

A startup is best defined by Steve Blank: a temporary organization in search of a sustainable, scalable business model.
The term “temporary” highlights that startups are not yet permanent — they exist to discover whether their offering will be adopted.
This inherent uncertainty makes failure a natural part of the process, not a stigma.

The Search for a Business Model

A startup must eventually earn more than it spends, but it operates with a longer time horizon.
The core challenge is search — testing hypotheses about customers, value proposition, and revenue.
Hypothesis testing (the focus of this module) is the tool used to navigate that search.

Failure as Part of Learning

Failure is not abnormal; it is akin to falling while learning to cycle.
Founders should be willing to reset — start afresh with an open slate when evidence shows the current path is wrong.

Case Study: Juicero (2016–2017)

Raised ~$120 M.
Aim: provide fresh juice on demand via a proprietary machine and sealed packets.
Shut down within a year — a high‑profile failure despite significant funding.

Case Study: Ziva Technologies vs. Justdial

Both companies tackled hyperlocal search on mobile in India — a real problem — but took very different approaches.

Aspect	Ziva Technologies	Justdial
Solution	Complex software for mobile search (structured database, retrieval algorithms, 2G optimisation).	Simple phone‑based call centre: “Call 4747… and we’ll give you the information.”
Outcome	Product built, money raised, but users did not adopt → failed.	Massive adoption, IPO, scaled profitably.

Why did Ziva fail while Justdial succeeded?
The key insight: “We fall in love with the solution and not the problem.”

Ziva fell in love with building a technically brilliant solution (database, retrieval, phone compatibility).
Justdial fell in love with the problem — how do people find local information? — and solved it with what was already available (cheap phone calls + yellow pages + call centres).

Exam tip: The phrase “fall in love with the problem, not the solution” is a cornerstone of startup methodology. Expect it in any question about why a venture failed despite a seemingly good idea.

Key takeaways

A startup is a temporary organization searching for a scalable, sustainable business model.
Failure is inherent and should be treated as learning — resetting is part of the process.
Common mistake: focusing on a clever solution rather than deeply understanding the real problem.
Compare Ziva (complex tech, no adoption) vs. Justdial (simple process, massive success) — same problem, different orientation.

The Three Major Challenges

Early-stage startups face three fundamental problems that can derail them before they gain traction:

Building a product nobody wants – The team invests significant time, money, and energy into a product that the market does not value. Examples include Webvan, Joost (Josera?), and Ziva — interesting concepts that failed to attract sufficient demand.
Being too early into the market – The solution addresses a real problem, but the market is not ready to adopt it yet. Customers will only realise the problem exists years later.
Wrong solution for the right market – The team correctly identifies a painful problem in an attractive market but develops a solution that does not actually solve it well.

In essence, early-stage entrepreneurship is a struggle between building something nobody wants, timing the market prematurely, or mismatching solution and problem.

Planning vs. Starting

A central tension in new ventures is whether to plan extensively or start immediately and learn by doing.

The “Just Start” Trap

A common mantra is “don’t overplan, just jump in and figure it out as you go.” While there is some truth to this, it can be dangerously oversimplified.

Swimming analogy: Being pushed into the water without any preparation (the “just start” approach) can be traumatising. The learner may panic, swallow water, and develop a lifelong fear. In contrast, a structured scientific method — first practising breathing technique on the poolside, then gradually entering shallow water — builds confidence and skill. The lean startup methodology mirrors this: you must be in the market (the water) but with a systematic approach.

The Rain Dance of Corporate Planning

Formal business plans in highly uncertain environments are often an illusion of control.

“Most corporate planning is like a ritual rain dance — it has absolutely no effect on the weather that follows, but it makes everybody who engages in it feel as if they are in control.”

Planning is useful only when the environment is static and predictable.

Certainty vs. Uncertainty

Scenario	Approach	Example
High certainty, predictable environment	Business plan – precise path, minimal deviation	Rocket launch: exact trajectory, no margin for error
High uncertainty, chaotic environment	Test and learn – plan a bit, do a bit, reflect	Driving on Indian roads (especially monsoon in Bangalore): unexpected obstacles (kids, animals, autorickshaws, potholes) require continuous adaptation

Planned methods work well in industries that have been stable for decades (e.g., diamonds, steel, gold). But startups operate in high‑uncertainty contexts where rigid plans fail.

The Correct Mindset: Test and Learn

Instead of pure planning or pure starting, use an iterative loop: plan a little, execute, think about the results, then plan again. This is the essence of the lean startup approach — formulating and testing hypotheses systematically.

flowchart LR
    A[Plan a bit] --> B[Do a bit]
    B --> C[Think / analyze]
    C --> A

The goal is to reduce uncertainty by learning what works and what does not — without wasting resources on unvalidated assumptions.

Exam tip: The swimming and rocket/driving analogies are often used to contrast the lean method with the traditional business plan. Remember that the lean method does not reject all planning — it advocates lightweight, iterative planning in the face of uncertainty.

Key Takeaways

Early startups fail for three reasons: product-market mismatch, being too early, or solving the right problem with the wrong solution.
“Just start” without any structure can be counterproductive; a systematic, hypothesis‑driven approach (lean startup) is safer and more effective.
Traditional business plans are suited for static, predictable industries but fail in dynamic, uncertain environments.
The lean method follows a test-and-learn loop: plan → do → think → repeat.
Analogies (swimming, rocket vs. driving) illustrate the need for market immersion paired with a scientific process.

Introduction to Hypothesis Testing

Hypothesis testing is the core of evidence-based entrepreneurship (also called Lean Methodology). Instead of building a product on guesswork, startups must uncover and test their underlying assumptions early. A hypothesis makes ideas explicit and testable — turning vague beliefs into something that can be proven or disproven with data.

Lean principle: Every startup begins with assumptions (e.g., “there is a need for this solution”). The goal is to run experiments that produce evidence, then use that evidence to pivot or persevere.

The Customer-Problem-Solution (CPS) Triad

The highest-level hypotheses any venture must address come from the Lean Canvas: Customer Segment, Problem, and Solution. These three elements form the CPS Triad, acting as a “North Star” to guide all subsequent testing.

flowchart LR
    C[Customer Hypothesis<br/>Who experiences the problem?]
    P[Problem Hypothesis<br/>What pain or job?]
    S[Solution Hypothesis<br/>What solves it?]
    C --> P --> S

Hypothesis	Question	Example (from IIMB DBE)
Customer	Who is experiencing the problem?	Young people across India who lack access to high‑quality undergraduate education
Problem	What pain or job are they facing?	Education does not meet industry demands; limited local options force students into conventional streams
Solution	What would solve it?	An online, flexible degree program that leverages NEP’s multiple‑exit policy, offered at lower cost

Each of these three can be unpacked into multiple micro‑hypotheses. For example, “Customers will pay ₹200/month for a focused study app” is a micro‑hypothesis derived from the solution.

Structure of a Testable Hypothesis

A proper hypothesis must be falsifiable: you must be able to collect evidence that could prove it false. Its structure follows a simple template:

We believe that [customer segment] has a problem with [pain/job to be done], and will [action] if offered [solution].

Clear belief about the world
Specific enough to be proven true or false
Testable with interviews, behaviour, or experiments (e.g., willingness to pay, sign‑ups)
Actionable – the result informs a decision

Example: Zoojoo.be (meditation/mental health app)

Hypothesised that users would pay for a future product.
Test: posted on Reddit meditation with two existing features, offered lifetime access for $75.
100–200 people paid. Validated demand with real money — not just stated interest.

Prioritize the Riskiest Hypothesis

Not all assumptions are equal. Prioritize the hypothesis that, if wrong, invalidates the rest — this is the riskiest assumption. Test it first to avoid wasting resources on less critical parts.

Don’t fall into confirmation bias (only seeking evidence that supports your belief).
Do design experiments that give the most honest signal on the highest‑risk assumption.

Exam tip: When designing an experiment, ask: “What would disprove my hypothesis?” If you can’t answer that, the hypothesis is not falsifiable — and therefore not testable.

Case Study: IIMB’s Digital Business & Entrepreneurship (DBE) Program

The DBE program was built on a set of untested assumptions that were later refined through feedback (though not formal hypothesis testing). Key assumptions in the CPS Triad:

Customer: Young Indians want a long‑term online degree because quality undergraduate education is unevenly distributed.
Problem: Existing programs are outdated, don’t match industry needs, and limit student choice.
Solution: Online delivery reduces cost, removes geography barriers, and aligns with NEP’s flexible exit options. Content should blend digital technologies, business skills, and entrepreneurial mindset.

Evidence gathered:

Interviews with IIT Madras, alumni, faculty, tech schools, board.
Feedback on content direction (liberal arts vs. digital + management).
Observation: early students were attracted by the IIMB brand; team hoped content would also be a driver.

Takeaway: Even without formal hypothesis statements, the process of assumption‑identification and evidence collection mirrors the Lean approach.

Activity Prompts (applied to your own work)

CPS Triad & Hypothesis Statements
Take five venture ideas. For each, create a CPS triad and write testable, falsifiable hypothesis statements for customer, problem, and solution.
Failure Analysis
Identify major company failures (Indian and global). Analyse: What untested assumptions led to the failure? Which hypotheses were wrong? Use the framework to be constructively critical — not dismissive — of others’ ideas.

Key takeaways

Hypothesis is the bridge between assumption and evidence; it must be falsifiable.
The CPS Triad (Customer, Problem, Solution) provides the high‑level hypotheses that guide a venture.
Each high‑level hypothesis can be broken into micro‑hypotheses — choose the riskiest to test first.
Test with experiments (e.g., willingness to pay, sign‑ups) not just opinions.
Avoid confirmation bias – actively seek disconfirming evidence.

Business Model Canvas (BMC)

A business model describes the rationale of how an organization creates, delivers, and captures value. This three-part framework is the foundation of the Business Model Canvas.

Business model definition (verbatim from lecture)
"A business model describes the rationale of how an organization creates, delivers and captures value."

Every successful business must simultaneously address all three:

Create value – the product or service itself.
Deliver value – making customers aware, enabling purchase, and physically or digitally delivering the offering.
Capture value – earning revenue that exceeds costs.

Neglecting any one of these (e.g., focusing only on creation and postponing delivery or revenue) is only sustainable if the venture has large external funding; for most firms, all three must be integrated from the start.

Why Lean Canvas Exists

The Business Model Canvas (BMC) is the original framework; the Lean Canvas is a derivative adapted for early‑stage startups. The BMC assumes some understanding of business operations, which early‑stage entrepreneurs may lack. The Lean Canvas modifies elements to reduce that required knowledge. However, the BMC itself remains useful for:

Existing businesses
Large corporations
Family businesses
Even lean startups (with adaptation)

The Nine Building Blocks of the BMC

The BMC breaks a business model into nine components:

Customer Segments
Value Proposition
Channels
Customer Relationships
Revenue Streams
Key Resources
Key Activities
Key Partnerships
Cost Structure

Each block contributes to one or more of the three value dimensions (create, deliver, capture). For example:

Value Proposition → create value
Channels & Customer Relationships → deliver value
Revenue Streams & Cost Structure → capture value
Key Resources, Activities, Partnerships → enablers for all three

flowchart LR
    A[Business Model] --> B[Create Value]
    A --> C[Deliver Value]
    A --> D[Capture Value]
    B --> E[Value Proposition]
    C --> F[Channels]
    C --> G[Customer Relationships]
    D --> H[Revenue Streams]
    D --> I[Cost Structure]

Exam tip: Any exam question on business models will expect you to articulate all three components – creation, delivery, capture – not just the product. The nine BMC blocks are the standard decomposition; be ready to map a given business example onto them.

Key takeaways

A business model = create + deliver + capture value.
The Business Model Canvas is the original, with nine building blocks; Lean Canvas is a startup‑focused variant.
The nine blocks are: Customer Segments, Value Proposition, Channels, Customer Relationships, Revenue Streams, Key Resources, Key Activities, Key Partnerships, Cost Structure.
All three value dimensions must be addressed simultaneously for a viable business (unless heavily funded).

Customer Segments

Customers are the heart of any business. The Customer Segments building block answers: For whom are you creating value? Who are your most important customers? Several archetypes exist, based on the distinctiveness of the audience:

Segment Type	Description	Example from lecture
Mass market	No segmentation; one product for everyone with minor variations.	Apple Mac Air – few chip / hard-disk options, essentially the same product for all.
Niche market	Small, specialised customer segment. Ideal for starting a business.	A wedding-catering service focused on Telugu weddings – tailored to community-specific tastes (many pickles, powders).
Segmented market	Customers with different needs; the company offers distinct value propositions to each.	Car market – different models for different buyer needs.
Diversified	Two unrelated customer segments served by the same company.	Amazon – e‑commerce on one side, cloud computing (AWS) on the other.
Multi-sided platforms	Two or more independent customer segments that interact through the platform.	Uber (riders & drivers), Amazon (buyers & sellers).

Key takeaways

Customer segments define who the business serves.
Start with a niche to focus limited resources.
Multi-sided platforms serve interdependent groups.

Value Proposition

The value proposition is the most important block – the bundle of products or services that create value for the chosen customer segments. Common types:

Value Proposition	What it delivers	Example
Newness	Something that didn’t exist before.	Ethical investing – avoid animal-testing or unsustainable companies.
Performance	Better, faster, quicker.	FedEx – rapid parcel delivery vs. normal post.
Customisation	Tailored to individual needs.	Bespoke fashion – “it fits very well because it’s customised.”
Getting the job done	Pay for outcome, not ownership.	Hilti – subscribe to heavy equipment; get the latest tool for each job.
Design / Aesthetics	Visually appealing.	Symphony air coolers (elegant vs. industrial), Su-Kam inverters (sleek vs. ugly lead batteries).
Brand / Status	Social signal.	Rolex watch – “jewellery that men wear”, Apple products as status symbols.
Price	Low cost, no frills.	Southwest Airlines – cheapest, no peanuts.
Risk reduction	Lower chance of negative outcome.	Organic food – no pesticide residues.

Key takeaways

Value proposition explains why customers choose you.
It can be functional, emotional, or social.
Multiple types can be combined (e.g., design + brand).

Channels

Channels describe how a company reaches customers to deliver the value proposition. Two broad modes:

Direct: own salespeople, own website, own retail stores.
Indirect: partner stores, franchisees, wholesaler → distributor → retailer.

Channels have five phases (in order):

Awareness – How do customers learn about the product?
Evaluation – How do customers assess the value proposition?
Purchase – How do customers buy?
Delivery – How is the product or service delivered?
After-sales – What happens after purchase?

Key takeaways

Choose a channel mix that balances reach and cost.
Each phase needs its own mechanism – don’t skip evaluation or after-sales.

Customer Relationships

Customer Relationships define how the company interacts with customers – for acquisition, retention, or boosting sales. Relationship types:

Type	How it works	Example
Personal assistance	Human interaction during purchase or use.	Car dealership (salesperson explains features), higher‑education fairs.
Dedicated personal assistance	Dedicated person for a specific time period.	Gym trainer – available during your session only.
Self-service	Customer does everything autonomously.	Automated restaurants in Japan (touchscreen orders), Airbnb.
Communities	Users interact with each other; company may use data.	PatientsLikeMe – patients share experiences; anonymised data sold to drug companies.
Co‑creation	Customers create content/platform value.	YouTube, Instagram, Facebook – user‑generated content fuels the platform.

Key takeaways

Relationships can be human, automated, or community‑driven.
Co‑creation turns customers into producers – powerful but risky (platform dies if users stop posting).
Communities can generate revenue from data (e.g., drug companies).

Revenue Streams

Revenue Streams are how the business captures value from customers. Two broad categories: one‑time purchase (buy‑and‑go) and recurring revenue (habit‑forming or consumables).

Revenue Model	Description	Example
Asset sale	Sell ownership of a physical product.	Car, house, land – customer owns it completely.
Usage fee	Pay per use.	Hotel room (pay per night).
Subscription	Recurring fee for ongoing access.	Netflix, curated vegetable box delivered weekly.
Lending / Renting / Leasing	Pay for temporary access.	Rent the Runway (clothes), camping gear rental.
Licensing	Permission to use intellectual property.	Software licensing (e.g., Microsoft Word).
Brokerage fee	Percentage of a transaction.	Uber, e‑commerce platforms.
Advertising	Revenue from ads shown to users.	Google (search ads).
Auction	Price determined by bidding.	eBay, flower markets.
Donations / Crowdfunding	Voluntary payments.	Kickstarter – many people give small amounts.

Pricing Mechanisms

Two main families:

Fixed menu pricing: predetermined, not negotiable.
- List price (e.g., flat bus fare ₹2.30).
- Product‑feature dependent (base + add‑ons).
- Customer‑segment dependent (basic / premium tiers).
- Volume dependent (discounts for bulk).
- Buffet (all‑you‑can‑eat flat fee).
Dynamic pricing: changes based on demand, time, or negotiation.
- Real‑time market (airline tickets, Uber surge).
- Negotiation / bargaining (local markets).
- Auction (stock exchange, flower auctions).

Key takeaways

Recurring revenue (subscription, razor‑blade model) creates long‑term value.
Pricing must align with value proposition – e.g., “cheapest” requires cost discipline.
Dynamic pricing increases revenue from high‑demand periods.

Key Resources, Key Partners, and Cost Structure

These three blocks form the “efficiency” side of the canvas.

Key Resources

What assets are essential to deliver the value proposition?

Physical: location, factories, equipment.
Intellectual: people, licenses, brand.
Financial: cash from investors or bootstrapping.

Key Partners

Who helps make the business model work?

Suppliers, distributors, strategic alliances, joint ventures.
“Crazy quilt” in effectuation: building partnerships as you go.
Example: coffee company using a dairy plant’s spare capacity for 3 days – converts fixed cost to variable cost.

Cost Structure

Costs incurred to operate the business model.

Fixed costs: rent, salaries – do not change with output.
Variable costs: raw materials, per‑unit production – change with volume.
Economies of scale: cost per unit falls as volume grows (e.g., Rameshwaram – small menu, many outlets).
Economies of scope: cost advantage from variety (e.g., Benki Tools – everything for coffee lovers, but limited to few stores).

Bootstrapping tip: Convert fixed costs to variable costs (e.g., rent equipment by the day instead of buying it). This reduces upfront risk.

The Canvas Fold — Product vs. Market

If you fold the Business Model Canvas vertically, you get two sides:

Right side (Market) : Customer Segments, Customer Relationships, Channels, Revenue Streams → how you generate value from customers.
Left side (Product/Operations) : Key Partners, Key Activities, Key Resources, Cost Structure → what it takes to create that value.

Value Proposition sits in the middle, bridging both.

For a profitable business:

$\text{Revenue (right side)} > \text{Cost (left side)}$

If not, the business model is “negative” – value is created but not captured.

Key takeaways

Understand which resources are critical and how to acquire them (buy vs. partner).
Fixed → variable conversion (bootstrapping) frees up cash for startups.
The canvas forces alignment: the cost side must be less than the revenue side.

Buyer Persona

A buyer persona is a fictional representation of the target customer, built on research and assumptions. Its purpose is to force the product team to empathise with who actually experiences the problem — for whom is this a real need?

If everybody is your customer, then nobody is your customer.
Chisel down to a specific segment; a solution may later serve others, but start narrow.

Components of a persona

Component	Examples
Demographics	Age, occupation, income, location
Goals & motivations	What they are trying to achieve
Frustrations / pain points	Problems they face that the solution could address
Preferences	What kind of solutions appeal to them

The more detail you add, the easier it becomes to talk to real people who match that persona and validate (or invalidate) your assumptions.

Why persona matters

Prevents falling in love with the solution instead of the problem.
Focuses value‑proposition design: does the offering resonate with that specific person?
Avoids the trap of building something nobody wants.

Worked example: Vegetarian tour of South India

The founder and his friend created a month‑long food tour through South India. Their persona was:

Not a first‑time visitor to India (already seen the Delhi/Taj Mahal circuit).
Excited by authentic, non‑touristy experiences — eating on banana leaves, travelling in normal buses, staying in simple places.
Willing to eat spicy food and tolerate some discomfort for a genuine cultural immersion.

This narrow persona guided every decision: where to advertise (alternative‑perspective magazines in the Netherlands), how to filter participants (dissuasive dinners to scare away the wrong crowd), and what experience to deliver (no air‑conditioning, no five‑star hotels).

Result: They attracted a small group (15–16 people) who truly appreciated the offering and became word‑of‑mouth evangelists.

Key takeaways

A persona is a fictional, research‑based representation of the target customer.
Include demographics, goals, pain points, preferences.
The narrower the persona, the easier it is to validate and resonate.
Chisel down – if everyone is your customer, no one is.

Customer Journey Map

A customer journey map visualises the steps a customer goes through when interacting with a product or service. It reveals pain points, emotional highs and lows, and opportunities for improvement — helping refine the value proposition.

Stages of the customer journey

The lecture identifies five core stages:

Awareness – How does the customer discover you exist?
Consideration – How do they evaluate your offering against alternatives?
Purchase – What influences the decision to buy?
Use – What is the actual experience of using the product/service?
Post‑use – What happens after? (e.g., word‑of‑mouth, repeat purchase)

flowchart LR
    A[Awareness] --> B[Consideration]
    B --> C[Purchase]
    C --> D[Use]
    D --> E[Post-use]
    E --> A

Purpose

Identify pain points and emotional highs/lows at each stage.
Generate opportunities for improvement – the map is not static; it must be updated as you learn.
Align the value proposition with the customer’s actual decision‑making process.

Worked example (continuing the food tour)

Stage	What they did	Insight gained
Awareness	Advertised in a Dutch magazine for alternative/trade‑fair readers.	Their target persona read such publications.
Consideration	Invited prospects to dinner at Robert John’s house; actively tried to dissuade them (“food is very spicy, no AC”).	They wanted only people who were genuinely excited despite the warnings.
Purchase	Provided a clear itinerary: third‑class train/bus, simple hotels, no five‑star.	Buyers were second‑time India travellers seeking authenticity.
Use	Travelled slowly (e.g., 2.5 days from Vizag to Vijayawada), stopping at local eateries (Subbayya Mess in Kakinada).	The experience matched the promise – emotional high.
Post‑use	Participants told friends; subsequent tours had better filters and improvements.	Word‑of‑mouth became the main acquisition channel.

The journey map helped them refine their persona and the offering over successive tours.

Key takeaways

A customer journey map covers awareness → consideration → purchase → use → post‑use.
It highlights pain points and emotional highs/lows at each stage.
Use it to identify opportunities for improvement and to re‑evaluate the value proposition.
The map is iterative – you often get it wrong the first time.

Buyer’s Utility Map

The Buyer Utility Map (BUM) is a strategic tool that evaluates how a product or service delivers value across six utility levers and six experience stages. It systematically identifies pain points in current market offerings and uncovers opportunities for innovation — whether for a startup, an existing company, or a large corporation.

Intuitively: think of every interaction a customer has with a product (from deciding to buy to throwing it away) and every way the product can make their life better. The map forces you to find gaps where you can improve or create entirely new value.

The 6×6 Grid: Utilities × Stages

The map is a 36‑cell matrix: one axis lists 6 utility levers, the other lists 6 experience stages. Each cell represents a potential innovation opportunity.

Utility Levers	What it means	Example (from lecture)
Productivity	Helping the customer get more done in less time	—
Simplicity	Making a task easy to understand or execute	Simplifying the process of going abroad
Convenience	Reducing effort or friction	Home delivery vs. in‑store purchase
Risk reduction	Lowering uncertainty or potential loss	Increasing warranty period
Fun & image	Providing enjoyment or social status	—
Environmental cleanliness	Minimising ecological harm	Biodegradable packaging, waste segregation

Experience Stages	Description
Purchase	Making the buying decision and transaction
Delivery	Getting the product to the customer
Usage	Using the product for its intended purpose
Supplements	Additional items or services needed alongside the product
Maintenance	Keeping the product in working condition
Disposal	Getting rid of the product after use

How to Create Value: Three Strategies

The map is not just a diagnostic — it’s a generator of new value propositions. There are exactly three ways to use it:

flowchart TD
    A[Identify pain point in a stage] --> B{How to create value?}
    B --> C[New utility lever in the same stage]
    B --> D[Same utility lever in a different stage]
    B --> E[New utility lever in a new stage]
    C --> F[E.g., add risk reduction at usage stage by extending warranty]
    D --> G[E.g., extend convenience from purchase to delivery via home delivery]
    E --> H[E.g., add environmental cleanliness at disposal stage, as Saahas does]

New utility in the same stage — Use a utility lever the customer isn’t currently getting at that stage.
Example: Usage stage already offers simplicity; you add risk reduction by offering a longer warranty.
Same utility at a different stage — Apply a utility lever that already exists in one stage to another stage where it’s absent.
Example: Convenience at purchase (easy checkout) → also convenience at delivery (home delivery).
New utility in a new stage — Combine a utility lever not used before with a stage where no one is providing that utility.
Example: Environmental cleanliness at disposal — Saahas picks up waste, segregates it, and recycles/composts responsibly.

How to Use the Map

Analyse each stage of the customer’s experience.
Evaluate how your current offering addresses each utility lever (or how competitors do).
Identify gaps — pain points customers express.
Brainstorm ways to fill those gaps using the three strategies above.

The process is enriched by combining BUM with two other tools:

Persona – define the target customer’s goals and pain points.
Customer journey map – map the stages and identify frustrations.

🛠 Practical tip: Start with a paper draft. Then ask ChatGPT to fill all 36 boxes. But ChatGPT tends to over‑fill — you must refine by deleting irrelevant cells. Use the AI output as a starting point, not a final answer.

Worked Example: Saahas (Waste Management on Campus)

Pain point in disposal stage: Online food delivery produces enormous plastic and paper waste — “when I look at the dustbin… so many boxes to throw.”
Innovation: Saahas (now Hasiru Dala) provides a convenient and environmentally clean disposal service.
- They pick up segregated waste.
- Biodegradables sent to composting.
- Electronics handled separately.
- Plastic, paper, glass, metal reused or recycled.
Value creation strategy: This is a new utility (environmental cleanliness) in a new stage (disposal) — a completely new lever that competitors weren’t addressing.

The campus stays “super clean” because the disposal stage is no longer a pain point.

Exam tip: The three strategies for creating value with the Buyer Utility Map are a classic exam question. Know them cold — and be ready to give a real example for each (e.g., Saahas for new utility in new stage, home delivery for same utility different stage, extended warranty for new utility same stage).

Key takeaways

The Buyer Utility Map has 6 utility levers (Productivity, Simplicity, Convenience, Risk Reduction, Fun & Image, Environmental Cleanliness) and 6 experience stages (Purchase, Delivery, Usage, Supplements, Maintenance, Disposal).
Each cell in the 6×6 grid represents an opportunity for innovation.
Value is created in exactly three ways: new utility in same stage, same utility in different stage, and new utility in new stage.
The map is used together with personas and customer journey maps to refine customer interviews and pinpoint gaps.
Use AI tools like ChatGPT as a brainstorming aid, but always refine the output to focus on real pain points.

Module-2 Experiment Design & MVP Testing

Blue Ocean vs. Red Ocean

Blue Ocean and Red Ocean are metaphors for market spaces.
Red Ocean represents all existing industries — crowded, competitive, with companies fighting over the same customers (like sharks in bloody water).
Blue Ocean represents unknown market space — uncontested, with demand created rather than fought over.

The core idea: even in existing businesses, you can create entirely new spaces by shifting focus from beating competitors to creating new value for buyers.

Definition – Blue Ocean: markets that do not exist today. Red Ocean: all industries in existence.

Why the construct matters (intuition)

Startups often think about “doing something new”, but many blue oceans arise from re-imagining an existing service (e.g., maternity care → a joyous experience, not a clinical one).
You don’t need a radical technology; you need a different value proposition that makes competition irrelevant.

Blue Ocean vs. Red Ocean – key differences

Dimension	Red Ocean Strategy	Blue Ocean Strategy
Market	Compete in existing markets	Create uncontested market space
Competition	Beat the competition – be number one	Make competition irrelevant
Demand	Exploit existing demand	Create and capture new demand
Value–cost trade-off	Choose differentiation OR low cost	Break the trade-off – differentiation AND low cost possible
Activity system	Align firm’s activities with strategic choice of either low cost or differentiation	Align activities in pursuit of differentiation and low cost
Focus	Cost or value	Value innovation – leap in value for buyers

Cornerstone: Value Innovation

Value innovation is the central pillar of blue ocean strategy.

Shift focus from competing to delivering a leap in buyer value.
Make competition irrelevant by offering something so different that existing rivals become obsolete.

Exam tip: Value innovation ≠ technology innovation. It’s about what buyers value, not what engineers invent.

The ERRC Model (Eliminate – Reduce – Raise – Create)

A practical framework to craft a blue ocean:

Eliminate – factors the industry has always competed on but no longer add value.
Reduce – factors that are over‑delivered relative to what buyers really need.
Raise – factors that should be pushed well above industry standard.
Create – factors the industry has never offered – this is where new demand comes from.

flowchart LR
  A[Industry conventions] --> B[Eliminate what's unnecessary]
  A --> C[Reduce over‑served factors]
  A --> D[Raise under‑served factors]
  A --> E[Create never‑offered factors]
  B & C & D & E --> F[New value curve → Blue Ocean]

Cloudnine (maternity hospitals)

Problem: Childbirth is joyful, but hospitals are quiet, scary, clinical places.
Blue ocean created: A dedicated mother‑child hospital that engages the family from the first trimester – exercises, nutrition, cohort, father included. Created a new category (mother‑child healthcare) where earlier only general hospitals existed.
Result: Multiple cities now have such specialty hospitals. Cloudnine became one of the largest.

Y Combinator (startup accelerator)

Before: Incubators in academic institutions, long programs.
Blue ocean: 3‑month program with smart founders, top mentors, a demonstration day – created the accelerator category.
Outcome: Changed global entrepreneurship; spawned Airbnb, Dropbox, Reddit, Meesho, RazorPay, etc.

Yellow Tail (wine)

Problem: Wine labels are complex (grape, vintage, vineyard, tasting notes). Most buyers just want a drink – they find selection confusing.
ERRC applied:

Eliminate	Reduce	Raise	Create
Too many wine variations (grapes, vintages)	Complexity and emphasis on prestigious vineyards	Affordability, simplicity	Demand from beer/spirit drinkers

What they did: Only red or white wine, slightly sweeter (friendly to casual drinkers), fun marketing (football ads, “uncomplicated”). Made wine selection easy.
Result: Became the most‑drunk wine in the US for decades.

Other mentions (context only)

Uber – blue ocean in taxi services.
Airbnb – blue ocean in accommodation.
Araku Cafe – value from shade‑grown sustainable coffee; made competition irrelevant.
Darshini / Rameshwaram (Bangalore) – quick‑service restaurants for South Indian breakfast (stand, eat, go – cheap, fast, hygienic).
Heritage hotels (Neemrana) – converted palaces/havelis into premium stays; created a new segment before Airbnb.

Key takeaways

Blue Ocean = new markets; Red Ocean = existing, competitive markets.
Blue ocean strategy centers on value innovation – leap in buyer value that makes competition irrelevant.
The ERRC framework (eliminate, reduce, raise, create) helps systematically design a new value curve.
Successful blue oceans often come from rethinking an existing industry (maternity, wine, travel) – not from inventing a new technology.
Competition is not the enemy; lack of value innovation is.

Coffee: How declining consumption created a growing market

Between 1950 and 2004, per‑capita coffee consumption in the US fell from 41 gallons/year to 24 gallons/year — nearly halved. Yet coffee sector revenues grew from $28 billion to$ 47 billion between 1990 and 2010. The apparent contradiction is resolved by the emergence of new categories that attracted smaller, higher‑paying customer segments.

The evolution of coffee categories is framed as three waves:

Wave	Description	Example
First Wave	Coffee consumed in cafés (historical, from Ethiopia through Arabia, Istanbul, Beirut, Cairo)	Traditional coffee houses
Second Wave	Coffee moved from cafés to homes → mass‑market home brewing	Instant coffee, percolators
Third Wave	Specialty coffee — emphasis on origin, roasting, grinding, filtering, fermentation, and complex flavor profiles	Single‑origin, pour‑over, espresso variations

Third‑wave coffee has fragmented into countless sub‑categories: single‑source, peaberry, high altitude, shade‑grown, sustainable coffee. Each commands a premium.

Example: Nespresso
Nestlé’s Nespresso initially struggled. It succeeded only after positioning as an exclusive, niche experience — hard‑to‑get boutiques, premium pods (~₹100 per pod in India). It created a category of “high‑convenience, high‑quality espresso at home/work”.

Example: Araku Coffee (India)
Araku positioned itself as shade‑grown, sustainable coffee — contrast with Brazilian coffee linked to Amazon deforestation. It created a category that appeals to ethically‑conscious, premium buyers. “If you want the best coffee without cutting forests, there’s only Araku.”

How new categories create new markets in other industries

The principle extends far beyond coffee:

Industry	New Category	Originator	Effect
Yogurt	Greek yogurt	Chobani (US)	Created a $bn category in the US. Epigamia tried the same in India but didn’t replicate success; high‑protein yogurt may be next.
Eggs	Free‑range, super‑premium eggs	Happy Hens (India)	Normal egg ₹6, premium ₹10, Happy Hen ₹25 — still high demand.
Milk	Ethical, traceable milk	Akshayakalpa (Bangalore)	Created a new space in a milk‑surplus, highly contested market (Amul, Nandini, etc.).
Confectionery	Healthy lollipop	GO DESi (NSRCEL)	Imli Pops, Kacha Aam Pops – less sugar, natural ingredients (imli, jaggery). Parents prefer them over sugar‑laden lollipops.
Business incubation	Incubator with childcare	(Lecture example)	Women entrepreneurs unable to attend standard incubators due to childcare gaps. Allowing children in classes created a loyal, repeat community.

Identifying a category opportunity

Ask:

Which group’s problem is not being addressed by existing offerings?
How can you create a space where you become the center of that category?

Categories do not require completely novel inventions. Repositioning or bundling attributes (e.g. “first‑wave → third‑wave”, “lollipop → healthy pop”) can carve out a fiercely loyal customer base.

Key takeaways

A new category is a blue ocean strategy applied to market spaces.
Categories can emerge even in declining consumption, as coffee illustrates – smaller, higher‑paying segments are the key.
Successful categories address unmet needs (childcare in incubators) or combine attributes into a superior proposition (sustainable + premium).
Incumbents in crowded markets (milk, eggs) can be disrupted by redefining the category (ethical, free‑range, traceable).
To spot categories: study local communities, identify people whose problems are ignored, and imagine what “center of that space” would look like.

MVPs as Antidotes to Failure

Ventures fail not only because of a bad product, but also because they are too early for the market. The classic example is Better Place (2007), which built a network of battery-swapping stations for EVs in Israel. The core assumption – that battery swapping would accelerate EV adoption – was correct, but the timing was so premature that the venture collapsed and set back EV conversations for years. Tesla succeeded later by positioning EVs as luxury, not utilitarian. The lesson: correct assumptions can still lead to failure if the market is not ready.

The Probabilistic Nature of Entrepreneurship

Entrepreneurship operates under uncertainty, not calculable risk. One common belief is that first ventures often fail, and the experience gained makes subsequent attempts more likely to succeed (e.g., second or third ventures at NSRCEL). This makes entrepreneurship a probabilistic game – more attempts increase the odds of eventual success. However, there is a method to mitigate uncertainty systematically, beyond traits like hustle or risk-taking propensity (the myth that only IIT/IIM founders succeed is an "urban legend").

The method involves moving through three stages of fit:

Problem-Solution fit
Solution-Product fit
Product-Market fit

Failure can occur at any stage. Even when a market exists, the solution-to-product transition can fail (e.g., Ziva and Justdial). The goal is to fail fast, fail smart – incur small, recoverable failures that teach quickly.

Exam tip: The "too early" failure mode is distinct from "bad product". Being early means the assumption is correct but the market timing is off – a key nuance in understanding venture failure.

Minimum Viable Product (MVP) as a Learning Tool

An MVP is the simplest version of an idea that allows you to learn something important from customers. It is not a mini version of the final product; it is a low-cost experiment to test one risky assumption at a time. This aligns with the corridor principle – once you enter a specific corridor (path), you may not be able to return, so test cheaply before committing.

MVPs can be used to test any element of the Business Model Canvas (or Lean Canvas): customer channels, pricing, partnerships, value proposition, etc. The focus is on learning, not on launching.

MVP Property	Common Misconception
Tests one risky assumption	Cuts all features
Low-cost, fast	Builds a stripped-down product
Generates customer learning	Generates revenue

Dropbox MVP Example

Dropbox’s first MVP was a simple explainer video showing how the product would work. The team measured whether people signed up for a waiting list. This validated demand before building the complex product.

Key takeaways

Ventures can fail because they are too early, even with correct assumptions.
Entrepreneurship is probabilistic; systematic experimentation improves odds.
Three fit stages: problem-solution → solution-product → product-market.
An MVP is a low-cost experiment testing one assumption, not a mini product.
Corridor principle: test early to avoid irreversible commitments.
Dropbox’s video MVP validated customer interest without writing code.

Types of MVPs

An MVP (Minimum Viable Product) is the smallest, cheapest experiment that tests a specific hypothesis about a problem, solution, or willingness to pay. Different MVP types de‑risk different assumptions. Entrepreneurs have developed several canonical forms:

MVP Type	What It Tests	Classic Example (from transcript)
Landing Page MVP	Interest / demand	Dropbox: a landing page with signup button → thousands joined waitlist before any code.
Concierge MVP	Solution value (manual delivery)	Zappos: founder manually bought and shipped shoes after taking pictures at local stores.
Wizard of Oz MVP	Behavior as if automated (back‑end manual)	Early food delivery apps: customers thought they ordered via system; founders phoned restaurants.
Paper Prototype	Usability & desirability	Fintech apps: paper sketches used to observe where users stumble.
Video MVP	Concept explanation (cheaply)	Mentioned as a type; no transcript example.

Landing Page MVP

Presents a simple website or email describing the proposed service and asks for sign‑up / interest. No product is built until demand is confirmed.

Dropbox – Created a landing page explaining cloud storage with a signup button. Thousands joined the waitlist in 24 hours – validated demand before writing a single line of code.
Zoojoo.be – Sent PowerPoint decks to HR departments describing a health‑improvement app. Gauged interest without building any software.
Amagi (Impulse Soft) – Emailed potential clients asking if they needed Bluetooth drivers. Only started development after receiving “yes” replies.
Zoojoo.be (upgraded) – Used Photoshop mockups to simulate a real app. When a client expressed interest, they asked which features mattered most and built only those first.

Exam tip: A landing page MVP can be as simple as an email or a mockup. The goal is to learn whether the problem is real, not to deliver a polished product.

Concierge MVP

The service is delivered entirely manually. The customer experiences the full proposed value while the founder does all backend work by hand.

Zappos – Nick Swinmurn took photos of shoes at local stores, posted them online; upon order, he bought and shipped the shoes himself.
Flipkart – Copied book images from the internet; when a customer ordered, founders bought the book from Sapna Book House, wrapped it, and sent it via speed post. They also distributed pamphlets to acquire repeat customers.
BigBasket – Uploaded grocery pictures; collected orders, bought in bulk at Metro Cash & Carry, sorted manually, and delivered using rented tempos.
Drop Cafe – Offered free coffee in Koramangala via Facebook posts. When demand surged (200 → 400 people), they tested willingness to pay at ₹80 – demand fell to 75, revealing that customers would pay but expected hot coffee, a logistics challenge.

Wizard of Oz MVP

The front end appears fully automated, but all operations are performed manually behind the scenes.

Early food delivery apps – Customers thought orders were processed by a system, but founders manually called restaurants and coordinated couriers.
Unifor (course case) – Posted notices asking customers to call; staff entered data manually and returned information, making the process seem automated.

Exam tip: Wizard of Oz is ideal for testing an automated experience before building the technology. The key is to fake the automation convincingly.

Paper Prototype

Sketches on paper (or an iPad) used to test user flows and interface design. Observers note where users stumble.

Fintech apps – Early versions tested flows by placing paper sketches in front of users; cheap, fast, and revealing.
Modern equivalent: interactive iPad mockups that users can touch.

Choosing the Right MVP

Match the MVP to the riskiest assumption:

Risk to Test	Recommended MVP
Is the problem real?	Landing page / interviews
Does my solution solve it?	Wizard of Oz or Concierge
Will customers pay?	Pricing test / pre‑orders

The core principle: never build a product without testing the riskiest assumption first.
Build in conversation with customers, use MVPs to guide decisions, and iterate.

Product‑Market Fit: The Ultimate Goal

When even zero marketing spending cannot kill demand, a product has achieved product‑market fit.

Thumbs Up (Parle, later acquired by Coca‑Cola) – Coca‑Cola tried to kill the brand (stopped advertising, reduced production), but demand remained so strong that they were forced to relaunch it. This demonstrates extreme product‑market fit.

Key Takeaways

MVPs are experiments, not scaled‑down products. Each type tests a different hypothesis.
Landing page / email MVPs test demand; Concierge tests solution value; Wizard of Oz tests automated experience; Paper prototypes test usability.
Never build a full product before testing the riskiest assumption.
Use the matching framework: problem → landing page; solution → concierge / Wizard of Oz; payment → pre‑orders.
Product‑market fit occurs when demand persists even with zero marketing – illustrated by Thumbs Up.

Structuring an MVP Testing Experiment

Every MVP test needs a deliberate structure — without it, you get noise, not insight. The goal is to reduce uncertainty as fast and cheaply as possible.

The three essential components

Component	Question answered	Example
Variable	What exactly am I testing?	A landing page with a sign-up button
Metric	How will I measure the outcome?	Sign-up rate = sign-ups ÷ unique visitors
Criteria	What result counts as validation?	≥20% of visitors sign up for early access

The criteria sets a quantitative threshold. In the Rent the Runway case, the founders didn’t just ask “will people rent?” — they tracked what was rented, how items were returned (condition, timeliness). Each metric fed back into venture design.

Exam tip: A criterion with no number is not a criterion. Always define the threshold before running the test.

Test cards — document your experiment

A test card formalises the three components above into a single sheet that forces clarity and makes the experiment reproducible.

Field	Content
Hypothesis	“At least 10% of visitors will click ‘Rent Now’.”
Test description	Landing page with a single CTA button; drive 1,000 visitors via ads.
Metric(s)	Click-through rate (CTR)
Success threshold	CTR ≥ 10%

Writing it down prevents memory bias — people tend to remember results that confirm their hopes and forget disconfirming ones. A written card provides evidence others can audit.

Learning cards — turn data into action

A learning card is the reflection step after a test.

What did we learn?
Did it confirm, refute, or partially confirm the hypothesis?
If partial: what revision to the hypothesis is needed?
What will we change next?

A learning card ensures every experiment leads to a concrete next step — not just a pile of data.

The entrepreneurial learning cycle

flowchart LR
  H[Hypothesis] --> M[MVP Test]
  M --> L[Learning]
  L -- confirmed --> H2[Refine or expand hypothesis]
  L -- refuted --> H3[Reject / pivot]
  L -- partial --> H4[Revise hypothesis]
  H2 --> M
  H3 --> H
  H4 --> M

Each loop reduces uncertainty. The faster and cheaper the loops, the higher the chance of building a successful venture — this is failing smart: spending little to learn a lot.

Exam tip: The phrase “faster and cheaper your loops” is a core principle of lean startup. It ties directly to the concept of build-measure-learn feedback loops. Be ready to explain why speed and cost matter for survival.

Key takeaways

Every MVP test must define a variable, a metric, and a success criterion.
Test cards document the hypothesis, test, metric, and threshold before you run the experiment.
Learning cards force post-test reflection and a decision (confirm, refute, or revise).
The hypothesis → MVP test → learning cycle is the engine of scientific entrepreneurship.
Each iteration reduces uncertainty; aim for fast, cheap loops to maximise learning per unit cost.

Customer Development

Customer development is the process of systematically discovering whether a product solves a real problem that customers are willing to pay for. The core mistake entrepreneurs make is falling in love with the solution instead of the problem – leading to products nobody wants or products introduced too early.

Why Customer Development Matters

Zero to one vs. one to n: inventing something new (zero→one) does not automatically translate into a scalable business (one→n). Example: Google created search but DoubleClick (acquired) figured out monetisation via AdWords. Similarly, current AI has buzz but hasn’t yet achieved one→n – analogous to the late-1990s internet euphoria before the dot-com bust.
Peter Drucker: “The purpose of a business is to create a customer.” No customers = no business.
In a startup, no facts exist inside the building – only opinions. Validation must come from customers, not from friends, teammates, investors, or market research. Data trumps opinion.

Exam tip: The phrase “no facts inside the building” is a hallmark of Steve Blank’s customer development methodology – expect it in exam questions about early-stage validation.

The Edison Phonograph: A Classic Caution

Edison invented sound recording (the phonograph) but had no idea what to do with it. His ideas:

Record dying words for remembrance.
Audiobooks for the blind.
Answering machine for telephones.
Music recordings – though he worried artists would lose income.

This shows that even a breakthrough invention requires customer development to find a viable application.

Core Principles

Principle	Meaning
Marketing myopia	Defining a business by product features (“my app does X”) instead of customer benefits (“solves Y”).
Loss aversion	People prefer to avoid losses over acquiring gains (losses feel ~2× more powerful). Therefore, frame solutions around reducing pain, not just adding benefits.
Falsifiable hypothesis	Convert intuition and enthusiasm into testable market-driven facts. Use data to corroborate, pivot, or abandon the business model.
Qualitative before quantitative	Early stage: in-depth interviews only. No surveys, no questionnaires.

The Customer Development Process (Steve Blank)

Identify initial customers – determine if the opportunity is important to them.
Conduct qualitative interviews – open-ended, no pitching.
- Do not ask: “Would you like to buy if something like this existed?” (yields false positives).
- Ask: “What are the challenges you face? How are you currently solving it?”
Use qualifying questions – filter for actual target customers.
Example: For a left-handed product, ask “Are you left-handed?”.
Seek proof – get an email, a commitment to buy, or an expression of interest (“Let me know when you launch”).
Close with a referral – “Do you know anyone else with this problem?” A referral is a form of validation.

Interview Techniques

Open-ended questions only – get them talking. Example: “What’s hard about being a freelancer?”
Flip to advice – “As an expert, what do you think?” (reduces perceived selling).
Record if permission is given (e.g., “as part of an IIMB program”).
Use ChatGPT (or similar) to refine question lists – check for yes/no traps.

flowchart LR
    A[Formulate falsifiable hypothesis] --> B[Qualify & interview target customers]
    B --> C{Get real proof?}
    C -->|Yes – email, intent, referral| D[Corroborate – proceed to MVP]
    C -->|No – vague interest or rejection| E[Pivot or abandon hypothesis]

Exam tip: Validation ≠ asking “Do you like it?”. Real proof is a concrete action (email, payment promise, referral). If they say “I’ll buy if you have it,” that’s proof.

Key takeaways

Customer development prevents building products nobody wants by focusing on the problem first.
Zero→one does not guarantee one→n; commercial viability requires separate discovery.
Inside the startup there are only opinions; data must come from customers.
Early-stage interviews are qualitative, open-ended, and avoid pitching.
Use qualifying questions, seek proof, and ask for referrals to validate demand.

Module-3 Evidence, Interpretation & Inference

Evidence, Interpretation and Iteration

Customer interviews generate raw data — what people say, what they do, and what they don't do. The goal is to interpret that data honestly, iterate based on evidence, and avoid the cognitive traps that lead startups to build the wrong thing.

Quantitative Evidence

When you have a website, a landing page, or any prototype, track metrics that reveal user behaviour. These give cold, numerical signals.

Metric	What it shows	Example from transcript
Conversion rate	Percentage of visitors who complete a desired action (e.g., sign up, click CTA)	15 out of 100 converted – may be good if segment is undefined; weak if segment is specific
Click-through rate	Fraction of visitors who move from one page to the next	–
Time on page / engagement	How long users stay; heat maps show where they focus	–
Sign-up rate	Number of people who leave their email (“let me know when you start”)	Dropbox used this as strong evidence of demand
Revenue & unit economics	Too early for MVP stage, but relevant later	–

Numbers are context-dependent. A 15% conversion rate might be high when you are still searching for a customer segment, but low when you have already targeted a specific group (e.g., pediatricians).

Qualitative Evidence

Numbers tell what happened; qualitative cues tell how people feel and whether you are onto something.

Listening for signals – enthusiasm, urgency, unsolicited suggestions (“This is a problem, but not this — it’s that”).
Do not prompt for expected answers. Let the signals emerge naturally.
Politeness as noise – especially in cultures with high power distance (e.g., India), people say nice things to avoid disappointing you. False praise is not a signal.
Commitment, not compliments – look for actions: giving an email, agreeing to a follow-up, paying even a small amount.

Exam tip: Watch what people do, not what they say. An email id or a ₹100 payment is worth more than a hundred “brilliant idea” comments.

Cognitive Biases to Watch For

Every entrepreneur carries biases that distort interpretation. Recognising them is critical.

Confirmation bias – hearing only evidence that supports your hypothesis. Actively seek disconfirming evidence (prove yourself wrong).
False positive bias – interpreting polite agreement as genuine interest. The transcript notes that people in high–power-distance cultures often tell you what you want to hear. Later, when you follow up, they say “I didn’t want to disappoint you.”
Sunk cost fallacy – continuing because you have already invested time, effort, or money, not because the evidence says it is working. Cultural fear of failure makes this worse in India. If the evidence is clear, cut your losses and start fresh.

Testing Hypotheses: Three Outcomes

When you test a specific hypothesis (e.g., “Pediatricians will pay ₹500/month for this tool”), the evidence leads to one of three conclusions:

Hypothesis supported – great; test the next assumption.
Partial evidence – hypothesis was vague or incomplete; refine it and test again.
Hypothesis not supported – reject it and decide what to do next.

Pivot, Persevere, or Abandon

Based on the evidence, choose a path:

flowchart LR
    A[Evidence gathered] --> B{Outcome?}
    B -->|Hypothesis supported| C[Persevere – double down]
    B -->|Partial evidence| D[Refine hypothesis & iterate]
    B -->|Not supported| E{Decision}
    E --> F[Abandon – cut losses]
    E --> G[Pivot – course correction]

A pivot is a change in one or more of the core elements:

Customer segment – you thought A was your customer, but B shows more interest. Example: Chumbak initially sold magnets to international travellers; after airports charged high rent, they pivoted to Indian youth on Facebook.
Feature set – zoom in on one key feature or zoom out to a broader problem.
Business model – who pays may differ from who uses. Example: Big Basket discovered that NRIs (paying customers) ordered groceries for their elderly parents in India (users). They started advertising in the US.

Exam tip: Pivot is not failure. It is a course correction toward a better opportunity. The worst choice is to ignore evidence because of sunk costs.

The Learning Card

Disciplined documentation turns interviews into actionable insights. After each interview, create a learning card with:

What we tested – clear hypothesis statement.
What we observed – actual results (quantitative & qualitative).
Key insights – what changed your understanding.
Next steps – what to do next based on evidence.

This feeds directly into the Build–Measure–Learn loop: build a minimal prototype (MVP), measure customer response, learn, and iterate.

Guiding Principles

Get out of the building. Talk to real users about their real problems – not your friends, family, or mentors.
Watch actions, not words. A quick exit from an interview is a signal. A willingness to give contact details is a signal.
Look for commitments, not compliments. “You are the next Steve Jobs” is worthless; “Here is my email” is gold.
Know your biases. Use tools like ChatGPT to check the data for signs of your own confirmation bias.
Pivot or persevere based on evidence – not on hope, effort, or time invested.

Key Takeaways

Quantitative metrics (conversion, click-through, sign-up) give cold evidence; qualitative cues reveal true interest.
Three cognitive biases sabotage interpretation: confirmation, false positive, sunk cost.
Hypothesis testing leads to accept, refine, or reject – then pivot, persevere, or abandon.
Learning cards formalise insights and feed the Build–Measure–Learn loop.
Trust paying customers above all; be alert to politeness as noise.
“The quick and the dead” in startups: be clever and alert, not stubborn.

Entrepreneurial Market Validation & Customer Discovery

The Corridor Principle states that opportunities multiply once you commit to a specific path. You cannot see the adjacent corridors until you start moving down the first one. This directly connects to hypothesis testing in venture creation: each experiment opens new testable questions.

The Distinction: Problem-First vs. Solution-First

Most first-time entrepreneurs fixate on a solution (a technology, an app). Experienced founders start by searching for a real, painful problem that a paying customer segment will fund.

Approach	Focus	Likely outcome
Solution-first	"I have a cool tech idea"	Building something nobody will pay for
Problem-first	"Where is a customer pain that matters?"	Iterating toward product-market fit

The transcript's guest explicitly searched across education, family communication, and customer support before landing on the latter — because paying customers existed there.

Market Dimensions: The "Paying Customer" Filter

A market is not simply many users. A viable market for a new tech product requires:

Willingness to pay — users who will exchange money for the solution
Ability to reach — repeatable channels to acquire customers predictably
Repeatability — the buying pattern must be replicable across many customers

The guest's key lesson: "India has never been a great market for software products as a buyer." For a software startup, developed markets (US, Europe, Australia) offer higher willingness to pay, established buying systems, and productivity as a top-of-mind concern. This is an unfair advantage for a founder who can build from India but sell abroad.

Customer Discovery: Structured Experimentation

The guest conducted 75–100 calls before starting his second venture. The process:

Pick a geography (decide which market you will serve)
Identify 2–3 problem statements in that market
Call potential buyers through network, LinkedIn, referrals
Ask only about the problem: Is this a top-3 problem in your company? Does your CEO/board talk about it?
Ask about willingness to pay: $10/month or$ 1000/month?
Build a prototype based on patterns in the answers
Test the prototype with the same people: "Would you buy this?"

Use time-boxed experiments with explicit outcomes and reviews — not random tinkering.

flowchart LR
    A[Pick geography & problem] --> B[Call 75-100 buyers]
    B --> C[Analyze: Is it a top-3 problem?]
    C --> D{Will they pay?}
    D -->|Yes, consistent pattern| E[Build prototype]
    D -->|No/Weak| F[Pivot to different problem]
    E --> G[Test prototype with same buyers]
    G --> H[Refine or commit]

The Hill to Die On

Once you have evidence that (a) the market is large enough, (b) customers will pay, and (c) you have an unfair advantage, commit to that specific niche. Resist the temptation to solve all 50 sub-problems — pick 1 or 2 and go deep. The "hill to die on" means ignoring competitor funding news, new entrants, and self-doubt, staying focused on that customer segment.

Narrow niche example: Bulk e-signature connected to workflows (not generic e-signature competing with DocuSign). Solve one workflow perfectly.
Expansion happens naturally: one solved problem → trust → customer asks for the next related problem → corridors open.

The Corridor Principle in Action

"Unless you start the first corridor, you would not know what are the subsequent corridors."

Once inside a market with the right dynamics (willingness to pay, buying systems), solving one problem reveals many more:

E-signature → contract management → obligation tracking → income share agreements connected to bank systems
Each new corridor is a larger revenue opportunity

The guest observed this at Freshworks: each fundraise doubled or quadrupled their addressable market because they kept discovering deeper needs.

Common First-Time Founder Mistakes

Over-reliance on network for a new venture (the network may not match the new problem)
Building a "mother platform" that solves everything day one
Premature focus on branding/IP instead of getting 10 customers who would stop what they're doing if you left
Treating a global website as a global company — better to target 2 cities explicitly
Ignoring the "time to pay" dimension — some markets have usage but no revenue repeatability

Key Takeaways

Validate paying customer existence before building anything. A market of users ≠ a market of buyers.
Customer discovery must be structured: talk to 50–100 potential buyers, focus on the problem, not your solution.
Time-box experiments and review outcomes — don't iterate just because you have energy.
Pick a hill to die on: a narrow problem in a large market where you have an unfair advantage.
The Corridor Principle means commitment reveals more opportunities — but only if the market fundamentally works (willingness to pay, repeatable acquisition).
For tech/SaaS, developed markets (US, Europe) still offer 1000× the buyer readiness compared to India.
Talent and culture are non-negotiable for survival through crises (e.g., COVID). Early hires matter enormously.

Module-4 Testing in Action

Idea Validation: The “Step Zero” Framework

Most entrepreneurs jump from idea to execution without first establishing whether the idea itself is worth pursuing. This “step zero” – deliberately validating the business case before committing resources – is the single most overlooked phase in venture building. It answers: Is this the right problem to spend the next five years solving?

Why “Step Zero” Exists

The worst outcome for a startup is not failure but the ”land of the living dead” – enough revenue to keep the founder interested but no growth for years. Many founders spend 5–7 years on an idea that was never strong enough, because they never tested it early. Step zero forces a founder to engineer the idea – not just execute on it.

The Five Characteristics of a Viable Idea

Any idea selected as a venture should pass all five tests below. Founders typically fail at one or two.

Characteristic	Key Question	Heuristic / How to Test
1. Urgent job	Is the customer’s task critical enough that they will act now?	Customers willing to pay on a promise shows urgency.
2. Unsolved pain	Is there an acute problem in getting that job done?	Existing workarounds indicate pain – but only if they are painful.
3. Differential value	Can you create enough value beyond existing solutions?	Customers switch only if the new solution is multiples better (not just incrementally).
4. Switching cost	How hard is it for the customer to move from their current solution?	High switching costs (e.g., data migration, training) kill adoption even for superior products.
5. Market dynamics	Is the market large enough, growing, and accessible?	Ability to reach customers, their willingness to pay, and total addressable market.

Exam tip: Switching cost is the dimension founders most often ignore. Even if your solution is better, inertia and existing integrations can block adoption. A customer’s “we already have a workaround” is a red flag.

Validation Heuristic: Getting Paid on a Promise

The strongest signal of idea validity is customers paying money on the promise that you will solve their problem – before you have built the product.

Example 1 – Zoojoo.be (first venture)

Created a 20-page slide deck with 20 features.
Cold-called CHROs at large enterprises, pretending the product already existed.
Result: Three customers (Mindtree, Unisys, Sonata Technologies) issued purchase orders for only 4–5 features, before any code was written.
This validated urgency, pain, and differential value simultaneously.

Example 2 – Aware (second venture)

Built an app with only one foundation course; listed 50 more courses as “coming soon”.
Offered a lifetime subscription for $15 (a one-time payment).
Result: 750 paid subscribers in the first 45 days (target was 100).
The speed and volume of paying customers confirmed a real market.

Exam tip: The bar for a “pay-on-promise” test should be high enough to hurt. $15 for a lifetime subscription is meaningful;$ 1 is not. The willingness to part with real money is the gold standard.

The Danger of Validating a Single Idea

If you only test one idea, you will always find enough positive signals (a few interested customers, encouraging comments) to keep going. Confirmation bias is massive. The solution: generate multiple ideas in parallel and test them all.

With one idea → you will always find a reason to continue.
With five ideas → you get a clear winner: some ideas will get many meetings, others very few; some will yield paying customers quickly, others not at all.

Process:

Generate ideas – divergent exploration (see below).
Define each idea – articulate the job, customer, and value proposition.
Establish validation criteria – e.g., “I need 100 paying customers in 60 days”.
Validate – run the same cheap test (pay-on-promise) across all ideas.
Select – the idea that passes all five characteristics most convincingly.

flowchart TD
  A[Generate 5-10 ideas] --> B[Define each idea clearly]
  B --> C[Set validation criteria]
  C --> D[Run pay-on-promise test for ALL ideas]
  D --> E{Which ideas hit criteria?}
  E -->|None| B
  E -->|One or more| F[Select best based on 5 characteristics]
  F --> G[Commit to building]

Sources of Ideas

No single source is sufficient. Use divergent exploration:

Personal experience – problems you have faced.
Current trends – new technology (e.g., AI) enables new solutions.
Online communities – Reddit, Product Hunt, Quora – observe recurring complaints.
Mentors and experts – their field knowledge reveals white spaces.
Structured ideation – e.g., generate 75 ideas before settling on one (Prof. Bhagavatula’s class exercise).

The same resources will produce different ideas for different people because what excites them varies.

Entrepreneurship Mindset (for students and early hires)

Not everyone needs to start a venture immediately, but the entrepreneurial mindset is valuable in any role. The single most important capability: ability to learn on one’s own (coachability + self-directed curiosity).

In a startup with scarce resources, you are expected to pick up problems and solve them without hand-holding.
Larger organizations also benefit from this mindset – they expose you to deeper industry problems that you might later solve as an entrepreneur.

Recommended job experience: Sales or any customer-facing role. It:

Destroys the fear of reaching out and being rejected.
Forces you to understand the customer’s perspective and product value.
Accelerates learning about urgency, pain, and switching costs.

Exam tip: For students, the best preparation for entrepreneurship is to work in sales or customer-facing functions, then move to a startup or large company for domain exposure. Avoid the trap of only building product without talking to customers.

Key Takeaways

Step zero is idea validation before any product building. Ignore it at your peril.
Five characteristics of a viable idea: urgent job, unsolved pain, differential value, low switching cost, attractive market dynamics.
Pay-on-promise is the strongest validation signal – pre-sales from real customers.
Validating multiple ideas in parallel prevents confirmation bias.
Ability to learn on one’s own is the most critical entrepreneurial capability; sales experience is the best single job to build it.

Entrepreneurial Testing in Action: Key Principles from Pradyun P Rao

This conversation with Pradyun P Rao, founder of Alaiy, extracts how entrepreneurial testing really works — not as a textbook sequence, but as a mindset of relentless action, asking, and closing. Every example is a real-world test of a hypothesis: will someone pay for this?

The Mindset: Testing Is Not Linear

Entrepreneurial testing is not a tidy five-step process. Pradyun frames it as a startup owner’s manual — you read the whole thing once, then flip to the relevant chapter when stuck. Key mental models:

Do things that don’t scale (Paul Graham). Example: manually managing social media comments for local businesses, then building a dashboard only when the manual process became painful. The automation emerged from the work, not from a plan.
Effectual logic (Saras Sarasvathy). Pradyun constantly asks: Who am I? What do I know? Whom do I know? — and then acts with affordable loss. Example: his first paid project (content writing for a doctor) was simply leveraging his writing skill, not a grand business plan.
Hypothesis testing is causal — but it’s used when stuck, not as a daily ritual. You test only the specific uncertainty blocking progress.

Exam tip: The lecture directly contrasts effectuation (bird-in-hand, affordable loss) with causal hypothesis testing. You will be asked to map Pradyun’s actions to these frameworks. For instance, his “cold emailing 10–15 people a day” to find a first customer is effectual (leverage who you know, keep trying), while his later virtual try-on product test for a fashion client is causal (hypothesis → experiment → cash).

The Core Testing Practice: Ask & Exchange

Pradyun’s single most repeated action is asking — for meetings, for work, for introductions. He overcomes the fear of asking by framing it as value exchange:

“What would it take for you to give me access to resources?”
He offered to sneak friends into IIMB in exchange for completing the entrepreneurship course — a clear trade.

Example	What was asked	Value offered	Outcome
First paid gig (content writing)	Doctor friend’s friend	Factual, researched content	₹4,500 (after discount)
Attending VC session with GPA cutoff	Wrote to dean, class teacher, cell	Eagerness to learn	Granted entry
First meeting with Hombale Films	“Can I come?”	Built a fan engagement site	Million-user campaign
Meeting Saras Sarasvathy	Joined lunch, asked about the cooking example	Genuine curiosity	Advice: “Why aren’t you starting your company?”
Delhi meeting with future mentor	“Can I meet you Dec 30?”	Dedication (flew on own money)	Anchor customer & investor

Key insight: money is the easiest signal of value. If someone you don’t know pays you, that’s a validated hypothesis. Pradyun calls it “the first value exchange” — better than a parent’s praise.

Breaking Into Circles (Networks)

Smart people cluster in small closed circles. To test ideas, you must break into the right circle:

Start locally (school, college, Bangalore’s entrepreneurial ecosystem).
Keep climbing: school → district → city → national → international (like chess prodigies).
Diversity over hierarchy: hang out with people from different fields (theatre, tech, film, retail). You never know which trough will become the next wave.

Pradyun’s circle-breaking tactics:

Go to events where you’re not invited.
Overstay your welcome.
Offer something in exchange (skills, time, enthusiasm).
Follow up relentlessly (he sent cold emails until one converted).

Responsibility & Closing

Closing is the hardest part. Pradyun emphasizes: take a task, finish it, and communicate the completion. This builds trust faster than raw intelligence. Example: when asked to build a dashboard, he delivered a working prototype, then offered an improved version without being asked. That led to the Salaar campaign.

Exam tip: “Closing” is a human skill, not a technical one. In interviews or case studies, expect questions like: How does Pradyun’s behavior illustrate the importance of reliability in early-stage testing?

Learning from Failure (Headwinds)

Pradyun’s biggest test failure: the sixth semester AI video project. After the Salaar success, he chased a bigger high → client vanished → lost all prior earnings → lost friends, collaborators, almost broke. How he recovered:

Spent 7–8 weeks at home reading, learning fundamentals (GPU compute, AI theory).
Turned the failure into a college capstone (paper published in Malaysia).
Came back stronger: that knowledge became the foundation of Alaiy.

Pattern: Failure is not the end; it’s a source of deep learning if you have the time and grit to reflect.

From Service to Product: The Alaiy Evolution

Alaiy started as a “product studio” — building custom solutions for paying clients (virtual try-on, ERP automation, e-commerce tools). Only after multiple validated projects did they build their own product, Alister (AI-powered online selling platform). This is an iterative pivot: service → product → possible transition to pure product.

Key milestones in testing:

Period	Activity	Testing method	Outcome
2nd semester	Freelance content writing, social media management	Direct customer payment	Validated demand for copywriting
3rd semester	Hackathon wins (Election Commission, college)	Pitch & demo against competition	Leadership & team-building confidence
5th semester	Salaar fan engagement site	Customer-paid project with technical complexity	Reputation, money, network
6th semester	AI video project (failed)	Hypothesis that AI video would be big	Client vanished, lost money, deep tech learning
Post-internship	Cold outreach to NSRCEL founders, 30+ meetings	Causal: pitch → demo → convert	Only 1 conversion (fashion virtual try-on)
Jan–Jun	Hired first team, built for anchor customer	Effectual: use existing relationship → deliver → get more work	Stabilized at 13 people, ₹10L/month salary bill

Key Takeaways

Testing in action is messy: you combine effectual (who am I?) and causal (hypothesis) thinking depending on the uncertainty.
Asking and closing are the two most underrated entrepreneurial skills — they create opportunities that formal search processes miss.
Money is the best validation signal: if a stranger pays you, you’ve passed a real test.
Break into circles by offering value and overpreparing; don’t self-select out.
Failure is a learning asset: the sixth-semester crisis turned into the technical foundation of Alaiy.
Scale manually first: “Do things that don’t scale” leads to automation ideas that actually fit the real problem.