Christian Idiodi's Reference Customer Method for Product-Market Fit

The framework

Build with a countable set of people, not a market

The target counts are specific: six to eight reference customers in B2B, fifteen to twenty-five in B2C. The number is not arbitrary, and the reason it exists is the whole insight.

How to apply it

How do you run the reference customer method?

Six moves. The discipline is refusing to widen the group when progress feels slow, and refusing to count someone who has not actually vouched for you.

1. 1

   Pick one target market and stay in it.

   Reference customers only work if they resemble each other. If you find yourself customizing for someone outside the segment, that is a signal to go find more of the right people rather than to broaden the definition.

2. 2

   Recruit to the number, not to the first yes.

   Six to eight in B2B, fifteen to twenty-five in B2C. Idiodi is explicit that reaching that output can mean working with thirty or fifty people, because most will not convert into genuine references.

3. 3

   Build with them, not for a persona.

   These are named people you design alongside. The commitment is mutual: they get a product shaped around their actual problem, you get a continuous read on whether the thing works.

4. 4

   Run the four risks against real people.

   Every solution carries value risk, usability risk, feasibility risk and viability risk. Idiodi puts value and viability squarely on the product manager, and calls value the one most teams skip.

5. 5

   Count only the people who will vouch publicly.

   The test is not satisfaction, it is reputation. A reference customer is someone who will tell a peer to buy it, which is a far higher bar than a good survey answer.

6. 6

   Treat the count as the product-market fit signal.

   When the target number of people will put their name behind the product, you have evidence. That same group then becomes the word-of-mouth engine for the customers after them.

This is the failure mode the number exists to prevent. One enthusiastic design partner is indistinguishable from a market of one, and a product built entirely around them is a consultancy with a login screen.

Boundary conditions

When it works, when it fails

The four risks are why this method is more than customer friendliness. Idiodi separates them cleanly, and puts two of them on the product manager rather than on design or engineering.

Worth knowing where this sits against the other dominant discovery school. Teresa Torres optimizes for rhythm: interview somebody every week, whoever the product can recruit, and let the habit compound into an opportunity solution tree. Idiodi optimizes for depth with the same small group until they will vouch for you. Breadth catches problems you did not know to ask about; depth produces a reference list you can sell with. The teams that struggle are usually doing neither and calling a stakeholder meeting research.

The sources

Where Idiodi discusses this