Customer-Collision MVP Test
Put a minimum product before buyers and let behaviour test viability
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 97%
The Customer-Collision MVP Test begins by separating a hobby from a commercially viable proposition. Build a minimum viable product, then expose it to a small but real market instead of waiting for a prestigious or large-scale launch. A farmers market is Perell's example: customers can taste the product, react to it, say whether they would buy, and reveal whether the price feels high or low. The key mechanism is collision between founder assumptions and customer behaviour. Conversations provide qualitative learning, while actual purchases test whether interest converts into demand. The founder then uses that evidence to change the product, audience, or price before investing further. This makes early market contact an information system, not merely a sales event.
Origin
Kim Perell described local farmers markets as practical testing grounds where founders can validate an MVP and gather immediate customer feedback before pursuing major distribution.
Core principles
- 01Commercial viability is different from personal enthusiasm
- 02A small real market can test a large ambition
- 03Customer behaviour outranks founder opinion
- 04Early feedback should shape product and price
How to run it
- 1
Choose commerce or hobby
State whether the idea must become a viable business or can remain personally rewarding without sales. That choice determines what evidence matters.
Pro tip Write a simple pass condition before testing, such as paid purchases from target buyers.
Watch out Do not quietly change the goal after weak demand appears.
- 2
Build the minimum testable product
Create the smallest safe version that lets a customer experience the core value. Avoid adding features that do not improve the test.
Pro tip Spend only enough to make the central promise credible.
Watch out A prototype that cannot deliver the core benefit produces misleading feedback.
- 3
Find a real test market
Take the MVP to a convenient setting containing plausible customers. It need not be the biggest retailer or broadest launch.
Pro tip Prefer environments where you can observe decisions and ask follow-up questions.
Watch out Friends and supporters may not behave like paying target customers.
- 4
Capture behaviour and feedback
Record who buys, who declines, what they like, and how they react to the price. Distinguish compliments from purchase intent.
Pro tip Ask what almost stopped each buyer from purchasing.
Watch out Do not infer product-market fit from praise without transactions.
- 5
Adapt before scaling
Use the strongest repeated signals to revise the product, positioning, customer, or price. Scale only after evidence supports the core proposition.
Pro tip Run another small test after every material change.
In the wild
A founder sells a first run of sparkling tea at a farmers market rather than pitching a national supermarket. She logs samples, paid purchases, taste comments, and reactions to two price points. Customers like the flavour but repeatedly misunderstand the adaptogen benefit, so she simplifies the label and tests again the following week.
→ The founder learns what drives purchase and improves the proposition before expanding distribution.
A founder offers a manually delivered version of an automated reporting service to ten target businesses. Three pay, and all three value alerts rather than the polished dashboard in the original plan. The founder narrows the MVP around alerts before building software.
→ Paid behaviour identifies the valuable feature and avoids unnecessary development.
Common mistakes
Testing only with friendly people
Supportive contacts may praise an idea without representing target-customer buying behaviour.
Confusing compliments with demand
Positive comments are useful, but commercial viability requires evidence that customers will pay.
Going big before learning
Large distribution increases cost before the founder understands the product, audience, and price.
Is it for you?
Best for
It is best for early-stage products whose core value and pricing can be tested with a small customer group.
Not ideal for
It is not ideal for products that cannot be offered safely or meaningfully without substantial regulated development.
From the transcript
“first you have to decide is this a hobby or is this a commercially viable product?”
“So, I would say it's getting to a minimum viable product”
“There's so much information gathering you can get if you just collide your idea with the actual customer because the customer is going to dictate…”
From the episode
Episode 499: Kim Perell: Building a $235M Company from the Kitchen Table + Why Perfectionism Kills Success
Kim Perell