Demand Signals: What They Are and How to Find Them

Most product ideas die because they started as ideas. A demand signal starts somewhere else: a real person, on a real thread, describing a problem they already tried to solve and failed at. That gap is the whole game. Ideas come out of your head. Demand signals come out of someone else's frustration, timestamped, public, and searchable.

We run a scan across Reddit, Hacker News, Product Hunt, and YouTube every day. Here's what a real signal looks like, where they cluster, and how to tell one apart from noise.

What Actually Counts as a Demand Signal

Three parts. If one is missing, it's a comment, not a signal.

1. **A specific person doing a specific job.** "Developers want better tooling" is noise. "Voice agent developers who need an STT, LLM, and TTS combination that stays under 500ms latency and $0.01 per 1k tokens" is a signal. You can picture that person. You know which threads they read.
2. **A workaround that already failed.** Real demand shows up as a postmortem. Someone tried to use the SBB website's filter system to find a specific Swiss train journey, couldn't express what they actually wanted, and posted about it. The failed attempt is the proof of intent.
3. **A named constraint.** No Python. Runs on Apple Silicon. Must be free. Must satisfy DSGVO. Constraints are what turn a vague wish into a spec, and they're usually the hardest part of the build, which is exactly why the gap still exists.

Our scan on 2026-08-21 surfaced one that hits all three: an independent musician archiving 300+ albums, needing bulk upload with per-release scheduled dates, running on a Raspberry Pi, for free. Specific person, failed workaround, hard constraints. That's the shape you're hunting for.

Where Signals Cluster, Platform by Platform

Each source tells you something different. Read them for different reasons.

• **Reddit** is where the pain lives. r/selfhosted and r/homelab produce a steady stream of "is there an open source alternative to X" posts. On 2026-08-21 alone, four separate posts asked for self-hosted replacements for paid tools including DocuSign, CCleaner, and Lightroom. r/LocalLLaMA is the highest-density source we've found for local inference pain: people post exactly which model, which hardware, and which step broke. r/SaaS and r/Entrepreneur are weaker for technical signals but strong for commercialization ones, like the non-technical founder trying to turn an AI prototype into something sellable and getting stuck on regional compliance documentation.
• **Hacker News** is where you check whether the problem is hard. Show HN comments will tell you within an hour if a category is crowded, if the technical approach is wrong, and who already tried it. Use HN as a filter, not as a source.
• **Product Hunt** tells you what's getting funded and how it's priced. If three launches this month attack the same workflow, demand is real but so is the competition. Read the comments for what the product doesn't do.
• **YouTube** is underrated. Tutorial comments are full of "this worked until step 6" and "how do I do this on Windows." A high-view tutorial with a repeated failure point in the comments is a product brief.

How to Tell Real Pain From Mild Annoyance

We tag every opportunity with a pain level, and that tag matters more than the idea itself. High pain means the person is blocked right now and has already spent time on it. Medium means they'd switch if something better existed, but they're not bleeding.

Signals that pain is high:

• They mention hardware they bought or a subscription they're currently paying for
• They list what they already tried, by name
• Multiple people reply "same" with their own variation of the problem
• The thread is a question, not a link. Questions are demand. Links are supply.

The self-hosted e-signature request is a good example of medium pain. OpenSign already exists, so the demand isn't for the software, it's for a containerized package with a setup guide that doesn't eat an afternoon. Still buildable, still sellable, but the wedge is packaging, not product.

Compare that to the local audio AI request: one cross-platform runtime for voice cloning, TTS, STT, and voice conversion, with no Python dependency and no cloud. Nothing packages that today. Higher pain, higher difficulty, much bigger prize.

Turning a Signal Into a Product Shape

Once you have a signal, run it through four questions before you write any code:

1. **What's the smallest version that removes the constraint?** For the voice agent example, that's not a platform. It's an API that takes latency and cost targets and returns the recommended model combination. One endpoint.
2. **Does the signal repeat?** One post is an anecdote. Our theme tracker flagged self-hosted alternatives across four posts and developer tooling for complex workflows across three, in a single day. Repetition across days is the real validation.
3. **Who pays, the poster or their employer?** r/selfhosted regulars mostly don't pay. Small business owners processing legal documents do. Same category, completely different business.
4. **Can you reach them where you found them?** If the signal came from a subreddit, you already have your first distribution channel. That's the underrated half of demand signal research: the source of the problem is usually the source of your first hundred users.

Build the Habit, Not the Backlog

Thirty minutes, three times a week, beats a monthly deep dive. Sort a few relevant subreddits by new, not top. Top shows you what's popular. New shows you what's still unsolved. Save every signal with four fields: date, link, the constraint, and the target user. After a month you stop seeing individual posts and start seeing patterns, and the patterns are where the opportunities actually are.

That daily scan across Reddit, Hacker News, Product Hunt, and YouTube is what 1U4X runs automatically, with pain levels and recurring themes already tagged. Worth a look if you'd rather spend your hours building than reading threads.