Willingness-to-pay language in threads is noisy. Treat "I'd pay" comments as hypotheses until budget, role, and timeline appear - or until a call confirms.
Best for: founders pricing early B2B SaaS from public research.
Pair with WTP signals post for true-positive patterns.
Ten false-positive patterns
| # | Pattern | Why it misleads | Validate with |
|---|---|---|---|
| 1 | "Shut up and take my money" | Meme culture | Ignore for pricing |
| 2 | "For my side project" | Hobby budget | Ask use case + day job |
| 3 | "Students would pay" | Non-buyer segment | Interview working pros |
| 4 | "We should switch" | Individual lacks authority | Ask who signs |
| 5 | "Too expensive" at $5 | Wrong segment | Clarify company size |
| 6 | Currency / region mismatch | PPP confusion | Segment by geo |
| 7 | "I'd pay if it had X" | Feature wish, not WTP | Prioritize X vs price test |
| 8 | Competitor price anchor only | Comparison, not demand | Ask current spend |
| 9 | Vague "enterprise would buy" | Speculation | Named accounts or skip |
| 10 | Affiliate / promoter praise | Incentivized | Check post history |
Conceptual background: Willingness to pay (Wikipedia) - not a substitute for pricing experiments.
True-positive hints (quick contrast)
- Names current tool spend ("paying $400/mo for X")
- Mentions renewal date or procurement timeline
- Asks invoice / PO / SOC2 (B2B buying process)
- Founder or ops lead with company email in profile (still verify)
Validation ladder
1. Thread quote → hypothesis
2. DM/call: who pays? → authority
3. Pilot / prepay / LOI → evidence
4. Paid plan at scale → pricing validated
Do not skip rungs 2–3 because thread sounded excited.
Research workflow
- Search WTP-ish phrases (alternatives mining).
- Tag each hit: false positive / maybe / strong.
- Interview 5 strong only.
- Run pricing page test before annual plan changes.
Use Search to sort by intent - saves reading every meme thread.