Framework

The 10 Uncomfortable Conversations Rule

You do not deserve to write a single line of code until you have survived ten customer conversations where you genuinely tried to be told no. Validation is evidence that bruises — not vibes that confirm what you already believe.

How it works

  1. 1Prepare your questions in advance. Ask without bias. Build a system of records for weak and strong signals.
  2. 2The goal is not to confirm your hypothesis. The goal is to stress-test it until it either breaks or holds.
  3. 3Polite interest is a weak signal. Urgency, specificity, willingness to pay, and a request to be notified are strong signals.
  4. 4When a potential customer simply changes the subject — that is a clear signal there is no problem to solve for them.
  5. 5Ten conversations is a floor, not a ceiling. Keep going until patterns stop surprising you.

Hear it on the podcast

Stop Building. Do This First.Listen to the episode

More from this episode

Get the next framework first

One email a week with the frameworks, tools, and founder stories from the podcast. Free.

More frameworks for Finding & Validating Ideas

The Tight Circle Photo Sharing ThesisPeople share photos freely when the social environment is tight, secure, and trusted — not because the product is good, but because the people around them feel safe.The Three Checkbox FrameworkBefore building any AI product, three boxes must all be checked: (1) distribution on the cap table — equity to people already inside your target market's networks, (2) defensible IP — proprietary data, SOPs, or formulas that cannot be replicated with another model call, and (3) an industry expert involved. If you cannot check all three, the project does not start. Not pauses — does not start.The 'Have To' Startup TestDon't start a company to start a company. Wait for the observation you cannot not pursue. That's the one you'll have the most fun with and the best shot of building well.Stop, Listen, RelaunchBefore rebuilding in a complex domain, spend serious time — months, not weeks — doing nothing but listening to the people who live inside the problem: customers, practitioners, adjacent experts. Technology is the easy part. The hard questions — who do you serve, how do you make money, why does this product deserve to exist — must be answered first. Building before you have those answers is borrowing against a debt you will repay at maximum cost.The Third-Party Truth AuditHave a neutral outsider interview users, observe them using the product, and deliver a prioritized action list of bottlenecks blocking revenue. Founders cannot get honest feedback directly: customers soften criticism to protect the founder's feelings, and founders get defensive and hear what they can manage rather than what is being said. A third party removes both distortions and surfaces the real picture.The B2G Pivot FrameworkWhen you have users but no anchor, it's not a product problem. It's a customer depth problem. Go vertical, raise the price, and let the credit card prove the market.