Most indie hackers, SaaS and AI builders, and lean product teams don’t fail because they can’t ship. They fail because they ship into a void. This guide lays out a concrete, repeatable playbook for demand discovery for product ideas, with a focus on turning noisy Reddit and X conversations into a pipeline of validated opportunities you can act on every week.

What Demand Discovery Is (And Why Guessing Is Expensive)

Demand discovery is the ongoing discipline of finding, tracking, and refining proof that people already care about a problem before you commit to building a solution.

In practice, demand discovery for product ideas means you:

• Listen where your market vents and experiments (Reddit, X, niche communities)
• Turn complaints, workarounds, and buying signals into structured notes
• Rank these opportunities based on pain, urgency, and reachability
• Feed the best ones into your prototype and launch pipeline

Guessing is costly because:

• Every “small” product bet still costs weeks or months of focus
• You anchor on your original idea and ignore better adjacent demand
• You overvalue polite interest (“cool idea”) and undervalue boring, recurring pain

Treating demand discovery as a one-time “validation” step is just a slower way of guessing. The goal here is different: build a lightweight weekly practice that keeps your product backlog tied to fresh demand signals.

Core Principles of Effective Demand Discovery

Before the workflow, it helps to align on a few principles. These keep you from chasing hype and help you spot real pull.

1. Recurring Pain > Vague Interest

Signals to prioritize:

• Repeated complaints about the same workflow or tool
• Detailed stories (“I spent 4 hours trying to…”)
• Multiple people piling on with “same” and “I thought I was the only one”

Signals to de-prioritize:

• “This looks interesting” with no concrete use case
• High-level “AI for X would be cool” speculation
• One-off rants with no replies, no specifics

2. Behavior > Opinions

What people do matters more than what they say.

Look for:

• People sharing manual spreadsheets, scripts, or duct-taped Notion/Zapier setups
• Threads asking for workarounds, templates, or scripts
• Mentions of tools they tried, hated, or outgrew

Each workaround is proof that the problem is real enough for them to invest time, not just talk.

3. Public Complaints Are Data, Not Drama

When someone rants about a SaaS, that’s market research:

• “This tool is too slow/expensive/rigid” → potential wedge
• “We hacked this together in-house” → unmet need with budget
• “We had to export everything to do it in Excel” → missing feature/flow

Your job is not to agree or disagree. It’s to capture the pattern and ask: “Is this a stable problem that will still matter in 12–24 months?”

4. Boring Problems Are Often the Best

The internet loves shiny “AI for X” ideas. Strong businesses often come from:

• Repetitive back-office workflows
• Compliance, reporting, billing, internal ops
• Unsexy roles: coordinators, assistants, analysts

If a workflow is boring, high-frequency, and expensive in time, it’s a prime demand discovery target.

A Weekly Demand Discovery Workflow

Here’s a practical weekly loop you can run as a solo builder or small team. Budget 2–4 hours per week, consistently.

High-level steps:

1. Define your focus for the week
2. Find relevant Reddit and X conversations
3. Filter noise and identify strong signals
4. Log findings into a simple demand log
5. Turn raw notes into opportunity statements
6. Score and rank the opportunities
7. Decide what to prototype or test next

Miner, the paid daily brief and research product this article lives on, automates a lot of the “finding” and “ranking” steps across Reddit and X. But let’s assume you’re doing it manually so you understand the mechanics.

Step 1: Define a Clear Weekly Focus

Each week, narrow your attention. “AI for everyone” is not a focus; “AI for customer support managers in B2B SaaS” is.

Define:

• ICP snapshot:
  • Role: e.g., customer success manager, indie Shopify store owner
  • Company stage/size: e.g., 5–50 employees, solo indie, mid-market
  • Environment: tools they already use, industries, constraints
• Problem space:
  • “Reporting for X”
  • “Onboarding for Y”
  • “Workflows that involve copy-paste between A and B”

Example weekly focus:

• ICP: B2B SaaS customer success managers in 20–200 person companies
• Problem space: upsell/cross-sell workflows and churn risk monitoring

This focus guides your search queries and what you consider “relevant.”

Step 2: Find High-Signal Conversations on Reddit and X

You want threads where your ICP naturally complains, asks for help, or shares workarounds.

Reddit: Where People Vent and Explain

Search within relevant subreddits using queries like:

• "[tool name]" + hate
• "how do you manage" + [workflow]
• "is there a better way" + [task]
• "what do you use for" + [process]

Subreddit types:

• Role-based: r/sales, r/Entrepreneur, r/startups, r/datascience
• Tool-based: r/salesforce, r/Notion, r/zapier, r/aws
• Industry-based: r/healthIT, r/realestateinvesting, etc.

Sort by “Top” (past month/quarter) for durable pain, and by “New” for emerging signals.

X (Twitter): Where People Complain in Real Time

Use search filters and keywords:

• "I hate" + [tool/process]
• "anyone else struggling with" + [task]
• "is there a tool for" + [workflow]
• "painful" + [process]
• Role tags and hashtags: "CSM" "churn", "revops" "forecasting"

Look for:

• Threads with multiple replies agreeing or adding detail
• People sharing screenshots of messy dashboards, sheets, or internal tools
• Questions explicitly asking for tools or solutions

If you use Miner, this is the part it can automate heavily: it continuously scans Reddit and X, surfaces high-signal conversations that match your ICP/problem space, and packages them into a daily brief so you skip manual searching.

Step 3: Filter Noise and Spot Real Pain and Buyer Intent

You’ll see a lot of chatter. You’re hunting for specific signal types.

Strong Pain Signals

Keep threads where you see:

• Specific, repeatable workflows:
  • “Every Monday I have to export data from Tool A, clean it in Excel, then send a PDF…”
• Emotional language tied to work:
  • “This is such a time suck”
  • “I’m doing this manually every week and it kills me”
• Workarounds:
  • “We built a janky internal script to handle this”
  • “We have a VA copying this over daily”

Ignore or deprioritize:

• Vague “I don’t like this tool” with no reasons
• Pure feature wishlists with no context of the job
• Hype discussions (“AI will replace X”) with no workflows described

Buyer Intent Signals

Pay attention when people:

• Ask for tool recommendations:
  • “What do you use for [very specific task]?”
• Mention budgets or trade-offs:
  • “We’d pay for something that integrates with X and Y”
  • “We tried [tool] but it’s too expensive for what we need”
• Describe switching:
  • “We moved from [tool] to [tool] because…”

Those are gold for discovering demand for your product ideas, because they show people are already in a buying or switching mindset.

Step 4: Log Findings in a Simple Demand Log

A demand log is how you turn noisy threads into a trackable asset.

You can keep this in a spreadsheet, Notion, Airtable, or whatever you like. Simplicity beats perfection as long as you can scan and sort it.

Here’s a simple column template:

• ID – unique identifier for the opportunity (e.g., CSM-REPORTING-001)
• Date Observed – when you logged it
• Source – Reddit/X (and subreddit or handle if needed)
• ICP – role + company type (e.g., “CSM, B2B SaaS, 50–200 employees”)
• Problem Summary – 1–2 sentence summary of the pain
• Job To Be Done – what they’re trying to achieve functionally
• Current Workaround – spreadsheet, script, VA, existing tool
• Pain Intensity (1–5) – how emotional/annoyed they seem
• Frequency (1–5) – how often it happens (daily, weekly, etc.)
• Buyer Intent (1–5) – evidence they’d pay or switch
• Reachability (1–5) – how easy it is to reach more people like this ICP
• Notes/Quotes – a few verbatim lines from the thread
• Potential Solution Angle – your raw idea or direction
• Status – “Observed”, “Exploring”, “Prototyping”, “Discarded”

Example row (in text form):

• ID: CSM-REPORTING-001
• Date Observed: 2026-04-03
• Source: Reddit, r/sales
• ICP: CSM, B2B SaaS, 20–200 employees
• Problem Summary: CSM spending 3–4 hours every Monday building manual churn risk and upsell reports from 3 tools.
• Job To Be Done: Build a weekly account health and upsell opportunity report for leadership.
• Current Workaround: Export CSV from CRM, customer success tool, and billing, then merge in Excel.
• Pain Intensity: 4
• Frequency: 5
• Buyer Intent: 3
• Reachability: 4
• Notes/Quotes: “Every Monday morning I lose half my day exporting data from [tools] into one monster spreadsheet…”
• Potential Solution Angle: Automated weekly account health and expansion report builder for CSM teams.
• Status: Observed

Miner effectively acts like an automated capture layer for this log: it scans, filters, and highlights repeated pain and buyer intent across Reddit and X, then you bring those opportunities into your own demand log to score and shape.

Step 5: Turn Raw Notes Into Opportunity Statements

Raw notes are messy. You need structured opportunity statements you can quickly scan and compare.

A simple opportunity statement format:

[ICP] who are trying to [job to be done] struggle because [key obstacles/pain]. They currently [workaround], which leads to [negative outcomes]. They have shown [evidence of willingness to change/pay].

Example derived from the demand log row above:

Customer success managers in B2B SaaS with 20–200 employees, who need to produce weekly account health and upsell reports, spend hours manually merging data from multiple tools into spreadsheets. They currently export CSVs from their CRM, success platform, and billing system and maintain a “monster spreadsheet,” which is time-consuming, error-prone, and delays decisions. Multiple CSMs online are actively asking for better ways to automate this process and are open to paying for tools that integrate with their existing stack.

Keep these opportunity statements in a separate view or document so you can review them without getting lost in raw quotes.

Step 6: Score and Rank Opportunities

Now you want to decide which opportunities deserve action.

Use the numeric fields in your demand log to create a simple priority score. One approach:

• Priority Score = Pain Intensity + Frequency + Buyer Intent + Reachability

You can also add:

• Strategic Fit (1–5) – how well this aligns with your skills, interests, and existing product/assets

Example:

• Opportunity A (CSM reporting)
  • Pain Intensity: 4
  • Frequency: 5
  • Buyer Intent: 3
  • Reachability: 4
  • Strategic Fit: 4
  • Priority Score: 20

• Opportunity B (AI for cold outbound message generation for SDRs)
  • Pain Intensity: 3
  • Frequency: 3
  • Buyer Intent: 4
  • Reachability: 3
  • Strategic Fit: 2
  • Priority Score: 15

Even if Opportunity B is more “exciting,” Opportunity A wins because it has higher recurring pain, clearer workflows, and better strategic fit.

Miner’s daily brief essentially delivers pre-ranked opportunities based on repeated patterns of pain and buyer intent across Reddit and X. You can use that as an input to your own scoring, especially as your backlog grows.

Step 7: Decide What to Prototype or Test Next

Once you have a ranked shortlist, the question becomes: what’s the smallest way to test pull?

For each top opportunity:

1. Clarify the core promise:
   • “Cut weekly reporting time from 4 hours to 20 minutes for CSMs.”
2. Choose a lightweight test:
   • Landing page with a clear positioning statement
   • Loom video walkthrough of a mock workflow
   • Interactive Figma prototype
3. Reach out where the signal came from:
   • Comment or DM: “We’re exploring a tool that [promise]. Would you be open to a quick call or early access?”
   • Post a follow-up thread summarizing what you’re building and who it’s for

You are not trying to close full deals on day one. You’re trying to:

• Get 3–10 qualified people to say “Yes, I want this enough to talk or pay.”
• Validate that your framing resonates (or learn why it doesn’t)

Feed the learnings back into your demand log:

• Update Buyer Intent
• Adjust Problem Summary and Job To Be Done
• Change Status to “Exploring” or “Prototyping”

Example: From Raw Threads to a Ranked Shortlist

To make this concrete, here’s how a builder might go from noisy threads to real product directions in one week.

Day 1–2: Collect Signals

Weekly focus:

• ICP: Solo and small-agency operators doing analytics for Shopify stores
• Problem space: revenue and marketing analytics reporting

You scan Reddit (e.g., r/shopify, r/Entrepreneur) and X for:

• “Shopify reporting”
• “Shopify analytics sucks”
• “how do you track” + “LTV” / “AOV”

You log 8–10 threads into your demand log. A few patterns emerge:

1. People complain that Shopify’s default reports make it hard to track LTV by cohort over time.
2. Agency owners maintain separate Google Sheets models for each client.
3. Some mention trying 2–3 analytics apps, but all feel either too complex or not opinionated enough.

You log each instance with IC, problem summary, workaround, and rough scores.

Day 3: Synthesize Opportunity Statements

You cluster threads and create 3 opportunity statements:

• Opportunity 1: “Shopify founders want lightweight cohort LTV tracking; current analytics are confusing and they resort to spreadsheets.”
• Opportunity 2: “Agencies want branded, automated performance reports to send to clients weekly without spending hours in Sheets.”
• Opportunity 3: “Marketers want to see attribution across email/paid/social, but stitching data from multiple tools is painful.”

You score them:

• Opportunity 1: Pain 4, Frequency 3, Buyer Intent 3, Reachability 4, Fit 4 → 18
• Opportunity 2: Pain 5, Frequency 4, Buyer Intent 4, Reachability 3, Fit 4 → 20
• Opportunity 3: Pain 3, Frequency 3, Buyer Intent 2, Reachability 3, Fit 3 → 14

Opportunity 2 rises to the top: recurring, painful, and strongly aligned with your skills.

Day 4–5: Design a Test

You create a simple promise:

“Automated weekly Shopify performance reports your clients actually read. Set up once, send every Monday.”

You:

• Create a 1-page landing explaining this, with a “Get early access” form
• DM 5–10 agency owners who were active in the threads you logged, referencing their comments
• Post a short X thread summarizing the problem and your idea, asking who wants early access

Results:

• 5 agency owners sign up
• 2 hop on calls and confirm they’d pay if the reports saved them 2–3 hours a week

You update your demand log with these conversations, confirming strong buyer intent. This becomes a priority product direction.

Seeing this kind of pattern repeatedly is exactly what Miner is designed to surface: it watches Reddit and X for you, connects recurring pain and buyer intent across many conversations, and feeds you a daily brief plus archive you can mine for these kinds of opportunities.

Making Demand Discovery a Habit, Not a One-Off Sprint

Treat demand discovery for product ideas as ongoing infrastructure, not an event.

Here’s a simple cadence:

Weekly (2–4 hours)

• Review new Reddit/X threads in your ICP/problem spaces
• Add 5–15 new entries to your demand log
• Update scores and statuses for existing opportunities
• Pick 1–2 opportunities to explore or prototype next

Monthly (2 hours)

• Review your top 10–20 opportunities
• Archive or mark “Discarded” the ones that repeatedly fail tests
• Identify 2–3 stable problem themes that keep resurfacing
• Align your roadmap or experiments around those themes

Quarterly (2 hours)

• Revisit your ICP and problem spaces
• Decide if you’re narrowing (more focus) or expanding (adjacent segments)
• Clean and refactor your demand log so new teammates or collaborators can understand it

To keep friction low:

• Use templates: copy/paste your opportunity statement format and demand log columns
• Automate collection where possible: use tools, alerts, and products like Miner to avoid manual searching
• Cap the scope: don’t aim to “capture everything”; aim to capture the highest-signal 5–15 items each week

Common Traps to Avoid

As you build this practice, watch out for these failure modes.

1. Overvaluing Compliments

Polite interest is cheap:

• “Cool idea”
• “I’d definitely use this”
• “This sounds awesome”

Unless it’s backed by:

• Clear pain description
• Agreement to talk or test
• Willingness to prepay or commit time

…treat it as a weak signal.

2. Chasing Hype Instead of Stable Pain

Any time a new technology wave hits (AI, crypto, etc.), social feeds fill with speculative ideas.

Ask:

• Does this solve a concrete workflow problem someone has today?
• Would this still matter if the hype died down?
• Do I see people struggling right now with the problem this solves?

If the answer is “not really,” downgrade its priority.

3. Ignoring Unsexy Workflows

Most builders are drawn to glamorous problems: growth hacks, creator tools, shiny AI features.

Make a counter-bet:

• Hunt for “annoying but necessary” processes
• Look where teams waste hours in spreadsheets or back-and-forth messaging
• Pay attention when people complain about operations, finance, HR, compliance

These spaces are often less competitive and have clearer ROI stories.

4. Treating Threads as Final Truth

A single Reddit rant is just one data point. Demand discovery is about patterns:

• Look for recurring complaints across threads, not isolated stories
• Compare what people say with what they actually do (workarounds)
• Use conversations as starting points for deeper discovery calls, not proof that your solution is perfect

Bringing It All Together

If you already ship quickly, your biggest leverage is not building faster—it’s pointing your velocity at sharper demand.

To recap the playbook:

1. Choose a weekly ICP and problem space to focus on.
2. Search Reddit and X for specific workflow complaints, workarounds, and buying signals.
3. Filter for recurring, emotionally charged, and behavior-backed pain.
4. Capture everything in a simple demand log with scores for pain, frequency, buyer intent, and reachability.
5. Distill clusters of threads into clear opportunity statements.
6. Rank opportunities based on scores and strategic fit.
7. Run lightweight tests (landing pages, prototypes, calls) with people from those threads.
8. Repeat weekly, and review monthly/quarterly to keep your backlog tied to live demand.

If you want to do this manually, the structure above is enough to get started this week.

If you’d rather spend your limited time on synthesis, prototyping, and talking to users, a research product like Miner can handle the heavy lifting of scanning Reddit and X, surfacing and ranking high-signal conversations, and giving you a daily brief plus archive of demand signals to pull from.

Either way, when you treat demand discovery for product ideas as a steady practice—not a checkbox—you stop guessing, start noticing, and give every product bet a better shot at landing in a market that’s already pulling.