01“That’s a great idea” is not data
When you describe your idea to friends, colleagues, or a supportive subreddit, most people are kind. “That’s a great idea, you should build it” costs them nothing and tells you almost nothing — it’s encouragement, and encouragement is not demand.
Real demand signals have a cost attached. The question that separates them isn’t “does this sound good?” but “has anyone already spent time, money, or effort trying to solve this?” Those are the signals that survive contact with a real launch.
02The hierarchy of demand
Picture demand signals on a ladder. At the bottom: words about a hypothetical — “I’d use that”. In the middle: behaviour around the problem — people complaining, asking, and building workarounds today. At the top: money already moving — they pay for a partial fix, or paid and quit over a flaw.
The higher up the ladder a signal sits, the more it predicts. A single “I pay $30/mo for a tool that half-solves this” outweighs fifty “sounds useful” replies, because one of them cost something real and the other forty didn’t.
03Strong signals vs weak ones
Sorting what you hear by how much it actually forecasts:
- Strong — “I currently pay for X to do this” — a live market at a known price
- Strong — a workaround they built or hacked together — unmet demand with effort already spent
- Strong — “I gave up on Y because…” — a paid attempt with the failure point named
- Weak — “that would be handy” — a free opinion about a hypothetical
- Weak — upvotes with no comments — attention, not intent
- Weak — “you should totally build that” — encouragement, the most flattering noise of all
04How the pipeline separates them
Reading for this by hand is hard precisely because the weak signals are loud and pleasant. The pipeline forces the distinction into two fields: a 0–100 pain signal for how acute the frustration is, and a willingness-to-pay tier for whether anyone described paying. A thread can be enthusiastic and still score low on both — which is exactly the “polite encouragement” pattern made visible.
Sorting the whole corpus by those fields surfaces the threads where pain is high and money is already moving, and pushes the cheerleading to the bottom where it belongs.
Go deeper on the money signal
Willingness to pay is the top rung of the ladder — here’s how to read it specifically.
How to find out what customers will pay →05The cost-of-the-problem test
Encouragement describes a future you might build; real demand describes a present that already hurts. Before you trust a signal, run it through one filter — has this person paid a cost over the problem already? Look for the markers that prove the cost is real:
- They name a price — “I’d happily pay for this” is weak, but “I pay around forty a month and still hate it” is a cost they already carry
- They describe a workaround — a spreadsheet, a script, a manual routine. Effort spent today is the clearest tell that the pain is live, not hypothetical
- They ask where to buy — “does anything do this yet?” or “what are people using for this?” is someone shopping, not someone being polite
- They quantify the damage — hours lost, deals missed, a customer churned. A person who can put a number on the problem has felt it
- They got specific unprompted — vague praise stays vague, but real pain comes with details, edge cases, and the exact moment it bit them last
Frequently asked questions
Look for cost already paid. Real demand shows up as people spending money on partial fixes, building their own workarounds, asking where to buy a solution, or quantifying what the problem costs them in time or money. Polite encouragement — “great idea, you should build it” — costs the speaker nothing and predicts nothing. Weight behaviour and money over words.
A demand signal is any evidence that people want a solution badly enough to act. Strong signals carry a cost — current spending, hand-built workarounds, abandoned tools, or someone actively shopping for an answer. Weak signals are free opinions: “that sounds handy”, upvotes with no comment, or encouragement. The stronger signals forecast a sale; the weaker ones just feel good to hear.
That gap is normal — liking an idea is free, paying for it is not. Praise measures politeness, not intent. Stop asking whether people like the idea and start looking for who already pays for a workaround, who built their own fix, or who describes the problem costing them something. Those people convert; the cheerleaders rarely do.
Validate with evidence of cost, not approval. Find where your audience already talks about the problem and read for behaviour: existing spending, workarounds, and people asking where to buy. redditx ranks public threads by how acute the pain is and whether anyone described paying, so the costly signals surface and the polite noise sinks — before you write any code.