Customer validation
Find out who will commit before you build more.
From an idea or months into a build, I help you get real evidence from customers, then decide what to build.
What is customer validation?
Customer validation is evidence that the people you are building for will commit to what you are making: their time, access to their users, a pilot or money. Compliments and survey answers do not count.
The strongest evidence comes from design partners, customers who commit to shaping the product before it is finished.
Where you might start
Starting from an idea
Nothing built yet is the cheapest moment to find out whether anyone else wants the problem solved.
See the founder pathAlready deep in a build
Months of work, and nobody outside the team has committed to it yet. I find out who would, and what they need first.
See the founder pathInside a product team
A backlog full of opinions. The next big item goes in front of real customers before more capacity goes in.
Validation on your real backlogHow a validation loop runs
I run it with ProtoVibing™, my validation method. You do the work with me in every loop, so you can run the next one yourself.
-
Idea
Turn a fuzzy idea into a bet someone could prove wrong: a named customer and a specific problem.
You leave withA one-liner, a target customer and a hypothesis.
-
Plan
Look at the market and the alternatives, then scope the smallest thing worth testing.
You leave withMarket context and a test scope.
-
Create
Build only what you will test: a throwaway prototype, nothing more.
You leave withA prototype that exists to be killed.
-
Test
Write the go or no-go rule first, then run 8 to 12 conversations with real customers.
You leave withAn interview guide and real transcripts.
-
Synthesize
Find the patterns in what people said and did, and grade the bet against the rule.
You leave withA synthesis and a graded bet.
-
Iterate or commit
Every loop ends in a written decision: sharpen the bet and run again, or commit and build.
What you have at the end
- A bet that survived real customers
- A customer profile grounded in interviews
- Transcripts and the patterns in them
- A tested prototype
- Opportunities validated, or killed early
- A decision you wrote down before testing
Why I start here
I learned this the expensive way, and every engagement since starts with it.
- Nashville, 2008
- Founded a music-industry marketplace. It failed, and taught me why validation comes first.
- 9x founder
- Started or co-founded nine companies.
- Meta
- Seven and a half years leading product, including the launch of Oculus for Business.
“Before discovering ProtoVibing, I had ideas but no systematic way to validate them with customers. Now I understand how to conduct proper customer discovery, validate pain points, and test assumptions before building features. I strongly recommend this to anyone who wants to validate product‑market fit.”
Questions people ask
What is the difference between customer discovery and customer validation?
Discovery is learning the problem: who has it and how they live with it today. Validation tests whether they will commit to your answer. Every loop does both.
How many customer conversations do I need?
Usually 8 to 12 in a loop, with the go or no-go rule written before the first one. Over time, most founders need five to ten design partners.
Do I need anything built?
No. The prototype in each loop is deliberately throwaway and built only for what you are testing. If you have already built a lot, we start from what you have.
What if the evidence says stop?
Then you stop or change the bet, and it cost you one loop instead of another six months of building.
How long does it take?
A loop is short by design. In the six-week Product Accelerator, a product team runs five loops. A design partner program usually runs three to six months, ending in a decision to buy, scale or stop.
Can I learn the method with other founders?
Yes. The group cohort runs on scheduled dates: you work through the method with other founders while I teach.
Can you lead the product while we do this?
Yes. With hands-on product leadership I join your team one to two days a week for three to six months, and validation runs through all of it.
Thirty minutes, free.