Are Users Paying — or Just Being Polite?

People are nice. Especially to founders who are clearly passionate about their ideas.

This niceness is the enemy of honest product validation. When you ask someone "would you use this?" the social dynamics of the conversation — your enthusiasm, their politeness, the implicit expectation of positive feedback — all conspire to produce a "yes" that means nothing.

Founder bias in feedback

Founders are the worst people to collect product feedback because: - Their enthusiasm is contagious and leading - Users feel social pressure to be supportive - The founder's interpretation of feedback is filtered through confirmation bias - Negative feedback gets unconsciously minimized; positive feedback gets amplified

Politeness distortion

The Politeness Distortion Factor: in most product feedback conversations, the response is approximately 40% more positive than the respondent's actual opinion. This isn't deception — it's social lubrication. People genuinely want to be helpful, and in most social contexts, being helpful means being encouraging.

Willingness vs ability to pay

"Would you pay for this?" and "Here is the payment page" test entirely different things.

• Willingness: A hypothetical assessment that costs nothing to express
• Ability: An actual resource allocation decision that requires trade-offs

The gap between stated willingness and actual payment behavior is one of the largest and most consistent findings in consumer research.

The payment friction test

The most honest validation signal is payment before the product is complete:

1. Can you get a letter of intent with a dollar amount?
2. Will someone pre-pay for beta access?
3. Will someone sign an annual contract before all features exist?
4. Will someone pay more than the introductory price?

Each level of payment friction provides stronger evidence than any amount of verbal feedback.

Real commitment signals

Signals that indicate genuine commitment (not politeness): - Time investment (spending hours in your product without being asked) - Referrals (telling others without incentive) - Integration (connecting your product to their workflow) - Complaints (caring enough to tell you what's wrong) - Switching cost acceptance (leaving a competitor to use you)

How this decision shapes execution

Building on polite feedback leads to products that are pleasant but not essential. The execution path optimizes for likeability rather than necessity, creating products that generate positive reactions in demos but don't survive the transition to paid, recurring usage. Payment is the filter that separates courtesy from conviction.