Most people start with an idea and then go looking for someone who wants it. That's backwards, and it's why so many launches land in an empty room. Demand signals flip the order: you find the evidence that someone is already struggling, already paying, already duct-taping a workaround together, and then you build the thing that ends the struggle. A demand signal is a public trace of unmet need. Finding them is a research skill, not a creative one, which is good news if you've ever stared at a blank page waiting for inspiration.

What Actually Counts as a Demand Signal

Not every complaint qualifies. Three things have to be present:

**A specific person.** Not "users" or "businesses." A webinar host. A music producer with 300 albums. A backend dev who's fed up with CI bills.
**A specific broken workflow.** The exact step where things fall apart, described in their words.
**Evidence of cost.** Money spent, hours lost, or a workaround they built themselves.

Here's one from our scan on August 19. A webinar host paid $1,392 for a year of EasyWebinar Professional — and the reason was essentially one feature: locking the progress bar so viewers can't drag past the content straight to the offer. Specific user (course creators running paid launches), specific workflow (viewers skipping the pitch), specific cost ($1,392/year, for what amounts to a video player behavior). That's not a wish. That's a receipt.

Now compare it to "I wish bookmarking apps were better." Same topic area, zero signal. No person, no workflow, no cost.

Rank Every Signal on a Strength Ladder

Once you start collecting, you need a way to sort. Four tiers, strongest first:

**Tier 1 — Money already leaving their pocket.** The $1,392 webinar example. Someone has proven the budget exists and told you the price ceiling.
**Tier 2 — A workaround they built themselves.** Same day, we caught an independent musician trying to archive and schedule 300+ albums, hitting 503 errors, and considering running the whole thing off a Raspberry Pi with CasaOS. Nobody sets up a home server for fun when a working product exists. Building a workaround is the most expensive form of complaint there is.
**Tier 3 — The same frustration from unrelated people.** On August 19, **AI workflow persistence** came up in two separate posts and **self-hosting / minimal dependencies** across four. Different people, different subreddits, same shape of pain. Repetition across strangers is what turns an anecdote into a theme.
**Tier 4 — A stated wish with no cost attached.** Nearly worthless alone. Useful only as corroboration for a higher tier.

Most "idea lists" you see online are entirely Tier 4. That's why they don't convert.

Where to Look, and What Each Platform Is Good For

Reddit has the highest signal density, but only in the right rooms:

**r/selfhosted** and **r/homelab** — infrastructure pain. This is where the demand for a **single-binary, self-hostable CI runner** lives: developers describing GitHub Actions costs and proprietary lock-in, asking for something they can drop on a cheap VPS.
**r/LocalLLaMA**, **r/ChatGPTCoding**, **r/ClaudeAI** — the AI workflow persistence signal. People losing three hours of multi-step research because a chat session closed, then asking how to save a "mission" across sessions.
**r/SideProject** and **r/Entrepreneur** — people who already paid for a tool and resent it. The best source of Tier 1 signals.
**r/DataHoarder**, **r/WeAreTheMusicMakers**, **r/musicproduction** — bulk archive and upload pain.
**r/webdev**, **r/smallbusiness** — the boring, high-willingness-to-pay stuff.

Sort by New, not Top. Top is what's popular; New is what's currently hurting. Search these phrases inside a subreddit: `"is there a tool"`, `"any alternative to"`, `"I gave up on"`, `"currently doing this manually"`, `"had to write a script"`.

Hacker News is where you read the comments, not the posts. Under every Show HN, someone lists what the tool doesn't do — that's a free gap analysis from a technical buyer. "Ask HN: what do you use for X" threads are the same thing in reverse. HN skews toward developer tools and self-hosting, which is exactly why the CI runner signal shows up there too.

Product Hunt is best read from the bottom. Skim the lukewarm comments and the follow-up questions on launched products. Someone who signed up and churned will tell you precisely which missing feature caused it, and that missing feature is often a whole product.

YouTube comment sections under tutorials are underrated. If a video called "How to bulk upload your music catalog" has forty comments asking how to set scheduled release dates, you've found a demand signal with a built-in audience.

How to Read a Signal Once You've Got One

**Find the workaround, not the complaint.** The complaint tells you what annoys people. The workaround tells you what they'll pay to stop doing.
**Count independent sources.** One post is a person having a bad day. The same pain from four unrelated people in a week is a market.
**Check the frequency of the pain.** Annual pain gets tolerated. Daily pain gets paid for. "My AI session closed and I lost my work" happens every day.
**Ask why it doesn't exist yet.** Sometimes the answer is "nobody noticed." Sometimes it's a real wall. Deep search across saved bookmarks and Instagram saves is a genuinely strong signal, but it needs platform access that X and Instagram restrict. That constraint is both why it's still unsolved and why it's hard. Know which one you're walking into.

Signals That Look Real and Aren't

**Feature requests aimed at an existing product.** If they want Notion to add one thing, they want Notion, not you.
**"Someone should build X" with no attempted workaround.** Talk is free.
**Real pain, no budget.** Students and hobbyists have plenty of both problems and reasons not to pay.
**Already solved.** Before you get excited, spend ninety seconds searching. Half of what looks like an opportunity is a product that exists with bad SEO.

Make It a Weekly Habit

Thirty minutes, three platforms, one doc. For each signal log four fields: the quote, the link, who the person is, and what it's costing them. Do that for a month and you'll stop having ideas and start having evidence. The person who ships the webinar player, or the bookmark indexer, or the tiny CI runner isn't smarter than you. They just read the receipts first.

This is exactly what we do at 1U4X every day: scan Reddit, Hacker News, Product Hunt, and YouTube for demand signals and rank them by pain level. If you'd rather skip the thirty minutes, the results are waiting for you.

Demand Signals: What They Are and How to Find Them