Value Hypothesis

What It Is

The value hypothesis tests whether a product or service actually creates value for customers once they begin using it. It is one of the two foundational Leap-of-Faith-Assumptions every startup must validate — the other being the growth hypothesis.

The value hypothesis asks: When customers use this product, does it genuinely solve a problem or satisfy a need they care about?

Why It Comes First

Ries argues that value must be validated before growth. Growing a product that does not create value simply means acquiring and then losing customers faster — scaling a failure. A high sign-up rate followed by poor retention is the clearest diagnostic signal: customers were attracted (the pitch worked) but not served (the product did not deliver).

This failure mode is extremely common. Companies optimize for acquisition metrics — signups, downloads, installs — while the value question remains untested. Acquisition is easy to measure and quick to celebrate; actual value delivery requires sustained customer engagement and is harder to observe.

Distinguishing Value from Growth

Dimension	Value Hypothesis	Growth Hypothesis
Core question	Does the product help customers?	How do new customers find it?
Focus	Post-acquisition behavior	Pre-acquisition discovery
Key signals	Retention, activation, depth of use	Viral coefficient, referral rates, CAC
Failure symptom	High churn despite signups	Stalled top-of-funnel despite satisfied users

Both hypotheses must be validated, but they answer different questions. A product that fails the value hypothesis cannot be saved by optimizing the growth engine.

What Good Validation Looks Like

Validating the value hypothesis means measuring customer behavior after first use — not intentions or satisfaction scores alone. Relevant signals include:

• Retention: Do customers return without prompting?
• Activation: Do they complete the actions that deliver core value?
• Depth of use: Do they engage with features that signal the problem is being solved?
• Willingness to pay: Will they exchange money for continued access?

Marty Cagan distinguishes between product discovery (testing whether the product is worth building) and product delivery (building it well). Value hypothesis validation is the heart of product discovery: it must happen before significant investment in delivery.

Steve Blank’s customer validation phase in the customer development methodology covers the same ground — confirming that early adopters receive sufficient value to recommend the product before attempting to scale.

Future Connections

Will connect to Growth-Hypothesis, Minimum-Viable-Product, Innovation-Accounting, Hypothesis-Pull when created.

Related Concepts

• Leap-of-Faith-Assumptions — the broader category of untested startup assumptions; the value hypothesis is the most critical
• Validated-Learning — the process by which the value hypothesis is empirically tested
• The Lean Startup - Ries - 2011 — primary source

Sources

• Ries, Eric (2011). The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. Crown Publishing. ISBN: 978-0-307-88791-7.

  • Chapters 4–5 (Experiment and Leap) — primary treatment of value hypothesis and its distinction from the growth hypothesis

• Blank, Steve (2005). The Four Steps to the Epiphany: Successful Strategies for Products that Win. S.G. Blank. ISBN: 978-0-9760994-0-2.

  • Customer development methodology; customer validation phase directly corresponds to value hypothesis testing — confirming that customers receive real value before scaling

• Cagan, Marty (2018). Inspired: How to Create Tech Products Customers Love. 2nd ed. Wiley. ISBN: 978-1-119-38716-8.

  • Distinguishes product discovery (testing value risk) from product delivery; value hypothesis validation is the central activity of discovery before investing in build

• Maurya, Ash (2012). Running Lean: Iterate from Plan A to a Plan That Works. 2nd ed. O’Reilly Media. ISBN: 978-1-449-30517-8.

  • Lean Canvas framework; explicitly names “riskiest assumption” as what must be tested first — usually the value hypothesis, because without value, no other assumption matters

• Reichheld, Frederick F. (2003). “The One Number You Need to Grow.” Harvard Business Review, December 2003.

  • Introduces Net Promoter Score (NPS) as a behavioral proxy for value delivery; a high NPS signals customers received enough value to recommend the product — a validated value hypothesis
  • Available: https://hbr.org/2003/12/the-one-number-you-need-to-grow

Note

This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.