What is XYZ hypothesis?

A numeric demand statement, X% of market Y will pay $Z within a time bound, tested with the cheapest possible prototype until it comes back true 70–90% of the time, before anything real gets built.

Why does XYZ hypothesis matter to a founder?

Roughly 99.5% of projects fail, and most fail because founders build before they know whether anyone will pay. The XYZ hypothesis forces the belief into a number that can be wrong, and the test collects first-hand data from real target customers rather than surveys or industry reports. Money is the only signal that counts; a prospect willing to write a check for something is the pass condition.

What are the common mistakes with XYZ hypothesis?

Writing a hypothesis without a dollar figure or, for long sales cycles, without a time bound. Testing with surveys and interviews instead of asking for money. Collecting full price during the test instead of anchoring the real number and discounting it. Treating engineering feasibility as part of the test; that question comes after demand.

XYZ hypothesis

CONCEPT · LAST REVIEWED 2026-09 · SOURCED FROM 1 SESSION, AUG 2026

The XYZ hypothesis, borrowed openly in the session from The Right It by Alberto Savoia, is a belief about demand written as a number: X% of market Y will do Z, where Z contains a dollar figure and, for slow-cycle businesses, a deadline. “5% of mid-size logistics operators will pay $5K within 60 days.” Then you build the cheapest artifact that can test it, today an AI-generated demo built in hours, and put it in front of real target customers.

Why it matters

Only money separates polite interest from demand.

From the room

“Money is the most important signal. They better be willing to write you a check for something, or you probably aren’t on the right path.”

— Serial founder, category-defining e-signature company · session, Aug 2026

The bar: the hypothesis should come back true 70–90% of the time across enough prospects to matter. While testing, anchor the real price and discount it: “This is a $1,000 product; because you’re early, pay $100 now, and respond as if I’m going to charge you $1,000.” Once it passes, the next steps in the same session were the fatal flaw analysis (call everyone who died on this hill) and a no-ask pressure test with investors before writing real code.

Where founders get it wrong

No dollar figure or time bound.
Surveys instead of checks.
Full price during the test.
Testing whether you can build it before testing whether anyone wants it.

Numbers from the room

Figure	Value
Project failure rate cited	~99.5%
Hypothesis pass bar	True 70–90% of the time
LTV:CAC to proceed	4:1 (3:1 is the investor floor)

Go deeper

Validate demand before you build is the full method.
Related concepts: Price-to-pain ratio, Customer development.