Most indie products don’t fail because the idea is “bad.” They fail because the builder misread demand, rushed through validation once, and then shipped into a shallow puddle of pain.

Demand discovery is the boring name for the thing that actually keeps you out of that trap: a repeatable way to spot real user pain, see where money wants to go, and decide which ideas deserve your build time.

This guide walks through a concrete demand discovery process for product ideas that a solo founder or small team can actually run every week, without turning into a full-time researcher.

Why Demand Discovery Matters More Than Clever Ideas

You can always brainstorm more ideas. You can’t get back six months spent building one nobody urgently wanted.

Common failure patterns:

• Building on vibes: “I’d use this” replaces “People are already trying to solve this and failing.”
• Copying competitors: Cloning another SaaS without understanding what demand they see, from whom, and at what price.
• One-off validation: Running a survey or posting a landing page once, getting a few positive signals, then ignoring demand for the next six months.

Demand discovery is not idea generation. It’s the ongoing habit of:

• Collecting evidence of pain, intent, and willingness to pay
• Structuring those signals so you can compare opportunities
• Using them to decide what to explore, what to prototype, and what to kill

The goal here is not perfection. It’s to have a usable demand discovery workflow that runs in the background while you ship.

What Makes A Demand Discovery Process Usable

A process is only useful if you can stick with it. For indie hackers and lean teams, that means:

• Lightweight: 30–90 minutes per week, not a research PhD.
• Repeatable: Same steps each time; you can pause and resume without rethinking everything.
• Time-bounded: Clear start/stop so you don’t fall into infinite browsing on Reddit and X.
• Integrated: Feeds directly into what you build next, not a separate “research folder” you never open.

A one-time research sprint might help you pick your initial direction. A process keeps your map updated as markets and tools (especially AI) move.

Think in terms of a simple system:

• Input sources: Where you listen (Reddit, X, customer calls, support tickets, community Slack, etc.).
• Signal types: What you look for (pain, intent, urgency, workarounds, willingness to pay).
• Logging: How you capture the raw signal (notes, quotes, links) so it’s not lost.
• Scoring: How you evaluate and compare opportunities.
• Decision checkpoints: When a signal triggers deeper exploration or a build decision.

The rest of this article fills those pieces in.

Defining Your Demand Signals

You’re not just “reading Reddit.” You’re hunting specific signal types.

Here are core signals that actually matter, with examples you’ll see in Reddit threads and X posts.

Repeated Pain Points

Same problem, many people, over time.

Examples:

• Reddit: “Anyone else struggling to keep track of which AI tools we’ve tried with each client? Our Notion is a mess.” (10+ replies with “same” / “following”.)
• X: Multiple founders complaining about churn from users who never complete onboarding.

What to look for:

• Multiple posts across weeks/months
• Different users describing the same underlying problem
• Threads with comments like “this” / “subscribed” / “this is killing me”

Explicit Buyer Intent

People saying they want to pay or actively looking to buy.

Examples:

• Reddit: “Is there a tool that automatically summarizes customer support calls into actionable tickets? Happy to pay if it’s good.”
• X: “Anyone paying for something to track API usage limits across all their integrations? Send recs.”

What to look for:

• “Is there a tool…”
• “Happy to pay…”
• “What are you using for…”
• “Looking to buy…” / “Paid tool recommendations for…”

Workaround-Heavy Workflows

People hacking together spreadsheets, Zapier flows, scripts, or manual processes to survive.

Examples:

• “Right now I export Stripe data to CSV, clean it in Google Sheets, then manually paste into our reporting dashboard every Monday. This sucks.”
• “We duct-taped Airtable + Make + three scripts to do this. It breaks every week.”

What to look for:

• Long-winded descriptions of multi-step processes
• Words like “hacky,” “janky,” “manual,” “every week I have to…”
• People sharing screenshots of gnarly spreadsheets or automations

Willingness To Pay

Not just intent, but concrete signals about budgets and tradeoffs.

Examples:

• “We’d happily pay $100/mo if something could keep our AI prompts versioned and synced across the team.”
• “My team wastes 5–10 hours a week copying data between tools. Even a $200/mo tool would be worth it.”

What to look for:

• Mention of price ranges (“I’d pay”, “worth $X/mo”)
• Comparisons (“cheaper than hiring another ops person”)
• Comments like “we’d pay for this today”

Urgency / Time Cost

How costly or stressful the problem feels.

Examples:

• “End of month is a nightmare; I stay up until 2am reconciling invoices.”
• “If we miss a client renewal because of this, it’s a five-figure loss.”

What to look for:

• Time mentions: “every day”, “every week”, “hours”, “all-nighter”
• Stakes: “we lose deals”, “we get churn”, “data breaches”, “fired”
• Emotional language: “hate”, “stressful”, “keeps me up”, “panic”

Interesting Complaints vs Real Demand

Not every complaint is demand.

• Interesting complaint: “I hate that Slack doesn’t have X theme.” Low stakes, cosmetic, no workarounds, no time cost.
• Real demand: “Our support queue is overflowing because we can’t route tickets properly; we’re losing customers weekly.”

Useful filters:

• Is there a repeat pattern across multiple people?
• Are they investing time/money in workarounds?
• Are there consequences if it doesn’t get solved (lost time, money, reputation)?
• Do they show willingness to pay or actively search for a solution?

If yes to 2–3 of those, treat it as a strong demand signal.

A Step-By-Step Demand Discovery Process For Product Ideas

Here’s a concrete process you can run as a solo founder or small team.

Assume you have 1–1.5 hours per week. Adjust as needed.

Step 1: Clarify The Domains You Care About

You don’t want to scan the entire internet. Narrow your focus:

• Target users: “B2B SaaS teams under 50 people”, “AI agency owners”, “creator businesses”.
• Workflows: “billing & reporting”, “customer support”, “AI prompt management”, “content production”.
• Industries: “Dev tools”, “healthcare”, “e-commerce”.

Pick 1–2 domains where:

• You understand the context enough to parse problems
• You have skills that map to solutions you could plausibly ship
• You’d be willing to spend 1–2 years if the demand is real

Write these down at the top of your demand discovery tracker.

Step 2: Choose Your Primary Input Channels

You want a small set of high-signal sources you can check regularly.

Examples:

• Reddit: Specific subreddits aligned to your domain (r/SaaS, r/startups, r/devops, r/marketing, r/Entrepreneur, niche subs like r/etsy, r/Notion, etc.).
• X: Keyword searches and lists focused on your target users (e.g., “CSM”, “RevOps”, “AI consultants”, “Shopify devs”).
• Your own data: Support tickets, feedback emails, sales calls, onboarding questions.
• Communities: Slack/Discord groups, paid communities where your users hang out.
• Direct interviews: Short calls with people in your target domain.

Pick 3–5 channels to start. Default heavily to places with unsolicited conversations (Reddit, X, communities), not just replies to your own content.

Step 3: Set A Weekly Demand Discovery Cadence

Design a loop you can actually keep.

Two realistic options:

• Option A: Two sessions per week, 30–45 minutes each
  • Session 1: Scan and capture signals
  • Session 2: Review, score, and decide next actions
• Option B: Daily micro-loop, 15–20 minutes
  • 10 minutes scanning
  • 5–10 minutes logging + quick scoring

Book these in your calendar like you would meetings. No multitasking. No “just scrolling.”

Step 4: Create A Simple Capture System

You need somewhere to put signals so they accumulate over time.

Use whatever you like (Google Sheets, Notion, Airtable). Don’t over-engineer it.

Minimal fields:

• Date
• Source (Reddit / X / Support / Call / Community)
• Link or Context (thread link, call note, ticket ID)
• Quote (copy-paste the key part, lightly cleaned)
• User Type (“SaaS founder”, “support manager”, “e-comm ops lead”)
• Problem Summary (your 1–2 sentence description)
• Signal Type (pain / buyer intent / workaround / willingness to pay / urgency)
• Intensity (1–5)
• Frequency (count of similar instances you’ve seen)
• Fit With You (1–5; skills, interest, network)
• Notes / Hypothesis (early idea: “maybe a reporting tool that auto-summarizes Stripe + Paddle?”)

Example row:

• Source: Reddit (r/SaaS)
• Quote: “I spend 3–4 hours every Friday manually compiling MRR/ARR charts for my investors from Stripe and PayPal exports.”
• User Type: SaaS founder (10–50 customers)
• Problem Summary: Founders waste hours manually aggregating revenue metrics from multiple payment processors.
• Signal Type: pain, workaround (manual spreadsheet), urgency (weekly), time cost
• Intensity: 4
• Frequency: 3 (similar posts logged)
• Fit With You: 5 (you’ve built analytics tools before)
• Notes: “Potential tool: low-friction revenue reporting + investor update generator.”

The act of writing these down forces you to think more clearly about what you’re seeing.

Step 5: Define A Basic Scoring Model

You don’t need a perfect model. You just need consistency.

Create a simple 1–5 score for each core dimension:

• Frequency (how often you see this problem)
• Intensity (how painful/urgent it feels)
• Buyer Intent (how much people show willingness to pay / tool search)
• Fit (how well this problem matches your skills, interest, and network)

You can then compute a simple Opportunity Score:

• Opportunity Score = Frequency + Intensity + Buyer Intent + Fit (max 20)

Rough interpretation:

• 16–20: Strong opportunity; consider deeper validation soon.
• 11–15: Worth keeping on the radar; wait for more signals.
• 7–10: Interesting, but probably a distraction right now.
• <7: Parking lot. Only revisit if you see a new pattern.

You can tune the weights later (e.g., double-weight Fit if you’re constrained).

Step 6: Add Decision Checkpoints

Decide in advance what happens when scores cross certain thresholds. That prevents you from forever “collecting more data.”

Example rules:

• When an opportunity hits 16+:
  • Run a deeper validation loop (5–10 short interviews / DMs).
  • Spin up a quick landing page describing the problem and possible solution; drive a small amount of traffic to see sign-ups/waitlist.
  • Draft 2–3 solution concepts; validate which resonates most.

• When an opportunity sits at 12–15 for 4+ weeks:
  • Review what’s missing (e.g., no buyer intent yet?).
  • Decide: actively seek more signals (e.g., targeted outreach) or demote it.

• When something stays <10 for a month:
  • Archive it. Don’t delete; just move to a “parking lot” section.

This turns raw signals into concrete next steps: more research, prototype, or kill.

Step 7: Review And Prune Regularly

Once a week (or at least once every two weeks):

• Sort your tracker by Opportunity Score.
• Look at the top 3–5 problems.
• For each:
  • Confirm you still see fresh signals.
  • Check if your understanding of the user and workflow is solid.
  • Decide if it’s ready for deeper validation, a test project, or should wait.

Prune aggressively:

• Merge duplicates (similar problems phrased differently).
• Archive low-score opportunities.
• Keep the active list short (5–10 problems), or you’ll drown in options.

The point of this demand discovery process for product ideas is to keep a living “opportunity backlog” that stays aligned with reality, not your mood.

Using Reddit And X As High-Signal Inputs

Reddit and X are excellent for demand discovery because they’re full of unsolicited pain and semi-public buyer intent.

How Reddit Fits

Reddit gives you longer, more detailed descriptions of workflows and frustrations.

Use it to find:

• Long-form venting posts about recurring problems
• How people currently work around those problems
• Honest reactions to existing tools

High-level search patterns:

• "[your domain] is killing me" (e.g., “invoicing is killing me”, “onboarding is killing me”)
• "how do you keep track of [workflow]" (e.g., “how do you keep track of client feedback”)
• "what are you using for [task]" (e.g., “what are you using for customer health scores”)
• Subreddit-specific complaints and weekly threads (e.g., “What’s annoying you this week?”)

When you find a strong thread:

• Log the original post and 2–5 key comments as separate entries if they represent different angles or user types.
• Capture concrete quotes; don’t summarize everything into generic “support is hard.”

How X Fits

X is noisier but great for:

• Rapid weak signals (emerging pain points, new AI workflows)
• Buyer intent (“any recommendations for…”, “what’s everyone using for…”)
• Sentiment around existing tools (“we’re ripping out X and moving to Y”)

High-level search patterns:

• "anyone using" + [tool / workflow]
• "tool for" + [problem]
• "looking for a way to" + [reduce / automate / track] + [workflow]
• Follow lists of your target users and watch what they complain about at end-of-quarter, launches, renewals, etc.

When you see a pattern (e.g., several AI consultants complaining about client reporting), log each distinct example and bump the Frequency score.

Plugging These Signals Into Your System

Each time you sit down to scan:

• Set a 20–30 minute timer.
• Pick 1–2 subreddits and 1–2 X searches.
• Capture only the top 3–5 strongest signals you see (quality > quantity).
• Log them immediately in your tracker with scores.

This keeps Reddit and X as inputs into your demand discovery workflow, not endless rabbit holes.

Where Miner Helps With Reddit And X

Manually scanning Reddit and X works, but it’s easy to miss patterns and forget to keep up.

A tool like Miner fits here:

• It turns Reddit and X conversations into structured signals (pain, buyer intent, weak signals).
• It sends you daily briefs you can skim in a few minutes.
• It highlights repeated pain and emerging themes without you manually searching.

You can treat Miner as an input source for your capture system: when a brief surfaces a relevant opportunity, log it, score it, and let your process handle the rest.

Keeping The Process Sustainable

The biggest risk isn’t doing demand discovery wrong; it’s stopping after two weeks.

A few practical rules to keep your demand discovery process for product ideas sustainable:

Time-Box And Batch

• Hard time limits: 20–30 minutes for scanning, 20–30 minutes for review/score.
• Batch by channel: one session for Reddit, one for X, one for your own data.
• Use timers and shut the tab when time is up. If you find something interesting, log it and move on.

Tie Discovery Directly To Build Decisions

Demand discovery should change what you build, not just inform a Notion document.

Examples:

• Greenlight: When an opportunity hits your score threshold and you have at least 3–5 real people you can talk to, run a micro-validation project (landing page, prototype, pilot).
• Pivot: If the problem you’re currently building for consistently scores lower than another opportunity (over several weeks), consider narrowing, repositioning, or switching.
• Kill: If you go weeks without seeing fresh signals for the problem you’re building around, seriously question whether it’s worth finishing.

Make these rules explicit so you’re not just rationalizing your current build.

Embrace Small Bets

Instead of betting everything on one idea:

• Keep an active “top 3–5” opportunity list.
• Run small validation projects for 1–2 of them over 2–4 weeks:
  • Landing pages with clear problem statements
  • Simple Typeform for waitlist / qualification
  • Quick scrappy MVPs for a narrow slice of the problem
• Use your demand discovery tracker to decide which bet to explore next, rather than chasing whatever you saw on X that morning.

This reduces the emotional load: you’re not searching for “the one idea,” you’re continually testing where demand seems strongest.

When To Bring In Miner

Manual demand discovery works fine at small scale. You outgrow it when:

• You’re tracking multiple domains or user types.
• You can’t keep up with the volume and speed of Reddit/X conversations.
• You find yourself skipping your weekly loop because “searching Reddit feels like work.”

Miner slots in at the top of your funnel:

• It acts as a daily brief that feeds your tracker with high-signal opportunities, repeated pain points, and buyer intent pulled from Reddit and X.
• It keeps an archive of signals you can revisit when you’re choosing a new direction or making a bigger bet.
• It helps you notice weak signals early (e.g., emerging AI workflows, new compliance pain) without living on social media.

You still own the process: defining domains, scoring, making build decisions. Miner just keeps the stream of signals fresh and structured so your loop stays alive.

Putting It All Together: Your Version 1.0 Process

Here’s a simple checklist you can implement over the next 2–4 weeks:

• Define 1–2 domains you care about (users + workflows + industries).
• Pick 3–5 input channels (mix of Reddit, X, and your own customer data).
• Create a basic tracker (Sheet or Notion) with fields for source, quote, problem, signal type, intensity, frequency, fit, and opportunity score.
• Schedule a recurring cadence:
  • 1–2 short scanning sessions each week
  • 1 review/decision session each week
• Use a simple scoring model (Frequency, Intensity, Buyer Intent, Fit) and set thresholds for:
  • Deeper validation
  • Prototype/MVP
  • Archive/kill
• Commit to pruning weekly so your active opportunity list stays small and sharp.
• If you want help keeping the pipeline full, connect a tool like Miner to feed you curated Reddit/X signals into your existing system.

You don’t need a perfect system. You need one that you actually run.

Design your version 1.0 of this demand discovery workflow, run it for a month, and then adjust. The compounding effect of four weeks of structured signals will beat another month of building on vibes.