Dollar-Driven Discovery
Test the dollar potential of a hypothesis, not just whether customers 'like' the idea
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 3
- Confidence
- 90%
A high-signal customer discovery method that tests the dollar potential of a hypothesis rather than politely chatting. It runs in three phases: identify extreme value (in a non-leading way), confirm ability to pay, and quantify willingness to pay. It's built to avoid 'happy ears' — the founder's bias toward hearing what supports what they already want to build — because customers are nice, polite, and bad at predicting their own behavior.
Origin
First Round Capital's customer-discovery methodology, taught by Todd Jackson as the second session of the PMF Method program. The fair/expensive/prohibitive pricing question is credited to Madhavan Ramanujam (Simon-Kucher), author of Monetizing Innovation.
Core principles
- 01Customers are good at describing their problems but bad at predicting what they'll use or buy
- 02'Interesting' is a polite way of saying no; look for 'wow' statements or demonstrated behavior instead
- 03Ask concrete, non-speculative questions so people answer honestly
- 04The best customer already has the problem, knows it, is looking for a solution, or has tried and failed to build one
- 05Ask about problems and value independent of what you're building, in a non-leading way
How to run it
- 1
Identify extreme value (non-leading)
Independent of your product, ask about the person's top goals and what's hard about them. Then float the outcome and watch the reaction. You're hunting for a 'wow' statement — 'if that works I'd sign up for the waitlist today' — or demonstrated interest (asks to meet again next week, wants to show colleagues, asks for the deck).
Pro tip Have them tell you quickly what stands out as valuable — it makes my product better, drives business success, saves money, or reduces risk. Fast, specific articulation of value is the signal.
Watch out Avoid 'happy ears': the founder's trap of cherry-picking the things a customer says that support what you already want to build.
- 2
Confirm ability to pay
Establish that budget exists. Ask whether they're currently looking for or building a solution, where a budget would come from, and how the team decides on third-party tools. The best answer is an existing budget — a competing tool that can be displaced, or engineers already assigned to the problem.
Pro tip You won't get the cleanest answer, but look for a known process (this manager approves up to X; above 50k requires comparing three alternatives) rather than pure ambiguity.
- 3
Quantify willingness to pay
Ask what they pay for the current tool, whether they'd pay more or less for yours. Then use the three-price ladder: ask the fair price, then the expensive price, then the prohibitively expensive price for the described solution.
Pro tip The 'fair price' is them angling for a deal; the 'expensive price' is what they'll actually pay for a genuinely good product; the 'prohibitive price' is the true ceiling. Anchor on the expensive number.
Watch out Match your demo fidelity to the product: Lattice sold on Figma mockups, Looker required a real-data demo, Vanta required actually doing the manual work — know which yours needs before the call.
In the wild
Jackson runs the method on Lenny in real time: he asks Lenny's top three goals, what's hard about them, then floats a service ('we'll help you find the 500 best guests and guarantee they show up'). Lenny responds 'I'd pay a lot of money for that' — a wow statement with a hint of 'does that really work,' which Jackson identifies as the exact positive signal to look for.
→ Illustrates that a wow reaction plus skepticism about feasibility is a buy signal, whereas 'that sounds kind of interesting' is a polite no.
Common mistakes
Taking 'interesting' as encouragement
When a customer says a product idea sounds 'interesting,' that is a polite no, not validation.
Asking customers to speculate about future behavior
People can't reliably predict what they'll buy or use; asking them to imagine future usage yields low-signal, misleading answers.
Talking to too few people
You've only spoken to enough customers once you can predict 70-80% of what the next person will say because you've heard the patterns so clearly.
Is it for you?
Best for
B2B founders doing early customer discovery who need to distinguish real dollar demand from polite enthusiasm before writing code
Not ideal for
Bottom-up/consumer contexts where purchase decisions are individual and impulse-driven, so structured B2B budget/procurement questions don't apply
From the transcript
“how do you test the dollar potential of a hypothesis”
“the Trap that we call Happy ears”
“the word interesting is a polite way of saying no”
“what is a fair price you would pay for this thing that I just described to you”
“the expensive price is the one that they would actually pay”
From the episode
A framework for finding product-market fit
Todd Jackson (First Round Capital)