Most indie hackers don’t fail because they can’t think of ideas. They fail because they ship into weak, vague, or fake demand — and only realize it after months of building.

This guide shows you how to run demand discovery for indie hackers as an ongoing habit, not a one-off validation stunt. You’ll get a concrete workflow using Reddit, X, and a basic demand log, plus ways to keep it sustainable while you’re shipping.

Why Ideas Are Cheap And Demand Is Not

You can brainstorm 50 ideas in an afternoon.

What you can’t easily see is:

• Who experiences a specific pain repeatedly
• How badly it hurts compared to everything else on their plate
• Whether they’re willing to pay to fix it
• Whether you can actually reach these people

That’s demand discovery: observing and measuring real, repeated pain and buyer intent, not just collecting cool ideas.

What Demand Discovery Is (And Isn’t)

In this context:

• Demand discovery: Systematically finding and tracking evidence of real problems, workaround hacks, and willingness to pay, across many people over time.
• Not just brainstorming: Brainstorms are about what you think is interesting. Demand discovery is about what they already prove they care about.
• Not surface-level “validation”: A tweet that gets 50 likes, a poll, or one enthusiastic DM is signal, but it’s not enough to know if there’s durable demand.
• Not copying big startups: Large companies can afford to educate markets, bundle 6 products, or monetize at scale. Indie hackers usually can’t.

If you want compounding wins as an indie hacker, you need a repeatable way to see where demand is already pulling, and then build slightly ahead of that pull.

What Counts As A Demand Signal?

Before opening Reddit or X, you need a simple definition of a “demand signal” so you don’t drown in noise.

Look for combinations of:

1. Repeated pain
   • Many people complain about the same thing over time.
   • Same core problem, different wording.
   • Example: “Keeping my Stripe and accounting in sync is a nightmare.”

2. Workarounds and hacks
   • People show their ugly spreadsheets, Zapier chains, scripts, or manual processes.
   • Any “this is stupid but it works for now” solution.

3. Explicit willingness to pay or budget
   • “I’d happily pay $X if this just worked.”
   • “We’re paying $Y for Z and it still sucks.”

4. Urgency and emotional intensity
   • Strong language: “killing me”, “I’m drowning”, “every month I…”.
   • Time-based pain: “end of month is always a nightmare”.

5. Buyer intent / “shopping” behavior
   • “What’s everyone using for X?”
   • “Is there a tool that does Y?”
   • “Alternatives to <tool> for <specific job>?”

6. Reachable, coherent audience
   • You can describe them in one short phrase: “B2B SaaS founders on Stripe,” “Notion-heavy agencies,” “Etsy sellers doing >$2k/mo”.
   • They gather in identifiable places (specific subreddits, hashtags, communities).

A single mention is a hint. A cluster of similar mentions across different people, over time, is demand.

Where To Look: Reddit And X For Demand Discovery

You don’t need complicated tooling to start demand discovery for indie hackers. You need better questions and filters.

Reddit: Deep Pain And Workarounds

Reddit is great for raw, unfiltered complaints and long-form context.

Types of subreddits to mine:

• Your target audience’s hangouts:
  • r/Entrepreneur, r/startups, r/SaaS, r/smallbusiness, r/freelance, r/consulting
• Tool-centric or workflow-centric subs:
  • r/QuickBooks, r/Stripe, r/Notion, r/obsidianmd, r/webflow, r/Shopify, r/amazonFBA
• Niche verticals:
  • r/realestateinvesting, r/personaltraining, r/etsy, r/printondemand, r/photography

Search patterns to use (manually or via Reddit search):

• "how do you manage" + <thing>
• "how do you track" + <thing>
• "what do you use for" + <thing>
• "alternatives to" + <tool>
• "is there a tool for" + <pain>
• <tool> + “frustrated” / “hate” / “sucks” / “broken”

Skim for:

• Long comments with specific context
• Screenshots or descriptions of messy spreadsheets
• Repeat questions about the same outcome (“how do you reconcile payouts?” asked in 10 different ways)

X: Real-Time Buyer Intent And Trends

X (Twitter) is noisy but great for catching:

• People actively shopping for tools
• Early gripes about new APIs, policies, or platforms
• Weak signals before they show up on blogs

Search structures that work:

• “is there a SaaS that”
• “what’s everyone using for”
• “how do you keep track of”
• {tool name} + “alternative”
• {role} + “tool stack” (e.g., “RevOps tool stack”)

Also:

• Follow a handful of “edge” accounts (operators, consultants, devs) in the niche you care about.
• Watch for repeated complaints in replies, not just the main tweet.

A tool like Miner can help here by pre-filtering Reddit and X into a daily list of pains, buyer intent, and product opportunities. But even without that, you can get far with targeted search and a basic logging habit.

Staying Sane: Scanning Without Drowning

You don’t have time to be a full-time researcher. You’re building.

So constrain your inputs:

Set Simple Time Boxes

• 20–30 minutes per day, or
• 2–3 focused 45-minute sessions per week

During that window:

• Only browse specific subreddits and saved X searches
• Don’t “just scroll”; you’re hunting for demand signals, not entertainment

Create Saved Searches

On Reddit:

• Save queries like:
  • site:reddit.com "is there a tool for" + "Stripe" + "payouts"
  • subreddit:saas "how do you track" "churn"
• Re-run them weekly; sort by “new” or “top past month”.

On X:

• Save advanced searches:
  • "is there a tool for" (stripe payouts) -giveaway -job -hiring
  • "what does everyone use for" (onboarding emails)

Rules of thumb:

• Ignore high-level debates (“is AI overhyped?”).
• Ignore one-off hot takes without replies.
• Focus on detailed threads with multiple people chiming in and describing their reality.

The Core Artifact: Your Demand Log

If you don’t capture what you see, you’ll keep “rediscovering” the same ideas and never build conviction.

You need a simple demand log. Don’t overthink it: a spreadsheet, Notion table, or markdown file is enough.

Suggested columns:

1. Date
2. Source (Reddit/X, link)
3. Audience (who is this person? short label)
4. Direct quote (copy-paste the key sentence)
5. Pain type (e.g., “reporting”, “onboarding”, “reconciliation”, “compliance”)
6. Workaround (what they do today)
7. Demand signals (pain intensity, workaround, budget, buyer intent)
8. Frequency (how many times you’ve seen this same pain)
9. Willingness to pay (none / implied / explicit $)
10. Reachability (easy / moderate / hard to reach this audience)
11. Idea / direction (how this might translate into a product)
12. Score (simple numeric priority)

Example structure in Markdown or CSV:

Date,Source,Audience,Direct quote,Pain type,Workaround,Demand signals,Frequency,WTP,Reachability,Idea,Score 2024-04-03,Reddit r/SaaS,"Indie SaaS founder","Reconciling Stripe payouts with my bank + QuickBooks is a monthly nightmare",Reconciliation,"Manual spreadsheet; copy-pasting from Stripe and bank","Repeated pain; workaround; strong language",3,"Implied (time is $$)",Easy,"SaaS to automate Stripe-to-accounting reconciliation",8

The log is your memory. Over weeks, patterns will emerge: you’ll see clusters of similar pains and audiences.

A tool like Miner essentially delivers a pre-structured version of this log to your inbox daily, with pains and opportunities already tagged, which you can then merge into your own system.

Concrete Example: From Messy Thread To Clear Demand

Let’s walk through turning raw noise into structured insight.

Step 1: Spot The Thread

Suppose you find a Reddit post on r/SaaS:

“Every single month I spend half a day reconciling Stripe payouts with my bank statements and QuickBooks. Export CSVs, clean them up, manually match refunds and disputes… it’s a nightmare. Is there a tool that just does this?”

Replies include:

• “Same here. I have a grotesque Google Sheet with like 10 tabs.”
• “We pay our bookkeeper extra just for Stripe recon.”
• “Tried ToolX but it breaks every time Stripe changes something.”

Step 2: Log The Raw Signals

You add an entry to your demand log:

• Audience: “Indie/B2B SaaS founders on Stripe”
• Direct quote: the main complaint
• Pain type: “Financial ops / reconciliation”
• Workaround: “Spreadsheets; extra bookkeeper time”
• Demand signals:
  • Repeated pain (monthly)
  • Strong language (“nightmare”)
  • Workarounds (spreadsheets, extra bookkeeping spend)
  • Buyer intent (“is there a tool that…”)
• Frequency: maybe “1” for now, to be updated as you see more
• Willingness to pay: implied (they’re paying with time and bookkeeper fees)

Step 3: Watch For Repeats

Over the next 2–3 weeks you see:

• Two more Reddit threads complaining about Stripe + accounting
• A tweet thread: “What does everyone use to reconcile Stripe with Xero?”
• A founder in a podcast mentioning “our month-end close is brutal because Stripe reporting sucks”

You update Frequency to 4 or 5.

You also add new entries if new audience segments show up, e.g., “Agencies billing through Stripe.”

Step 4: Clarify The Job-To-Be-Done

From your log, you rephrase the problem in your own words:

“For small SaaS businesses using Stripe, monthly reconciliation between Stripe, bank, and accounting software is an error-prone, time-consuming process that nobody wants to own.”

You note potential product directions:

• Narrow, focused tool that:
  • Pulls Stripe payouts automatically
  • Maps them to accounting categories
  • Flags mismatches (refunds, disputes, fees)
• Or:
  • Layer on top of existing accounting tools (QuickBooks/Xero plugin)

You haven’t built anything yet. You’re just stacking evidence of demand.

Basic Scoring: Turning Signals Into Priorities

At some point, you’ll have more opportunities in your log than you can build. You need a simple scoring model.

Don’t over-engineer this. Use a 1–5 or 1–10 scale for each of:

1. Frequency: How often do you see this pain across independent people?
2. Intensity: How emotional/urgent is the language?
3. Willingness to pay: Are they paying today (with money or lots of time)?
4. Reachability: Can you find and talk to these people easily?
5. Founder fit: Do you understand this domain and/or want to work in it?

Example scoring (1–5, then sum):

• Stripe reconciliation:
  • Frequency: 4
  • Intensity: 4
  • WTP: 4
  • Reachability: 4 (lots of SaaS founders on X/Reddit)
  • Founder fit: 3 (you understand SaaS finances decently)
  • Total: 19/25

Compare with a different idea from your log, like “AI tool for summarizing every Slack channel across the company”:

• Frequency: 2 (few real complaints, lots of hype)
• Intensity: 2
• WTP: 2 (no budgets mentioned)
• Reachability: 2
• Founder fit: 5 (you like AI)
• Total: 13/25

You might personally like the AI idea more, but your demand log tells you where the pull actually is.

A tool like Miner effectively hands you a pre-scored list of pains and opportunities daily, based on Reddit and X conversations. You can still apply your own scoring, but you’re starting from a high-signal shortlist instead of raw feeds.

From Demand Notes To Real Product Bets

Demand discovery isn’t the same as picking a product. It feeds into it.

Here’s how to go from “pile of notes” to “concrete bet”:

1. Group By Audience + Pain Theme

In your log, filter by:

• Audience: “SaaS founders on Stripe”
• Pain type: “financial ops / reconciliation”

You might end up with 8–15 rows all pointing to similar pains.

2. Write A One-Page Problem Brief

For the strongest cluster, write:

• Who it’s for
• What problem they have
• How they solve it today
• Why those solutions suck
• Evidence you’ve seen (copy-paste a few quotes from your log)

Example:

SaaS founders using Stripe struggle with month-end financial reconciliation. They export CSVs from Stripe and their bank, manually clean and match transactions, and often pay bookkeepers extra. This process happens monthly, feels painful (“nightmare”), and shows up repeatedly on Reddit and X. Existing tools (generic accounting software, ToolX) are brittle or overkill.

This document is a forcing function: if you can’t write it clearly, you probably don’t understand the demand well enough.

3. Outline Narrow Solutions, Not Big Platforms

Instead of “Stripe financial platform,” think:

• “Tool that reconciles Stripe payouts with QuickBooks in one click”
• “Service that sets up and maintains reconciliation for you (tool + ops)”

Each is a bet you can test with conversations, mockups, or mini-tools.

4. Test Language, Not Just Features

Use what you captured in your log as marketing copy:

• If people say “nightmare” and “half a day every month,” put that on a landing page:
  • “Stop wasting half a day every month reconciling Stripe in spreadsheets.”

Share this page in the same places you found the pain. Watch for:

• Replies asking “when is this live?”
• People DMing you
• People asking pricing before it even exists

This is higher-fidelity than random “what do you think of this idea?” tweets, because it’s grounded in real phrases actual sufferers used, not your imagination.

Building A Habitual Demand Discovery System

The real payoff comes when demand discovery becomes rhythm, not a sprint.

Here’s a lightweight system you can actually maintain.

Weekly Rhythm (Manual Version)

1. Daily (10–20 minutes)
   • Check saved Reddit/X searches.
   • Add 2–5 entries to your demand log.
   • Tag them with audience + pain type.

2. Weekly (30–60 minutes)
   • Review your log.
   • Merge duplicates; update frequency counts.
   • Re-score your top 5–10 opportunities.
   • Update one problem brief with new quotes or insights.

3. Monthly (60–90 minutes)
   • Pick 1–2 opportunities to push forward with:
     • Customer calls
     • Landing pages
     • Simple prototypes or scripts
   • De-prioritize ideas that haven’t gained new signals.

The key: don’t wait until “I need a new idea” to do this. When that moment comes, you want a warm pipeline of validated pain you’ve already been tracking.

Adding An Accelerator Like Miner

If manually trawling Reddit and X feels like too much, you can offload part of it:

• Miner’s daily brief scans noisy Reddit and X conversations and sends you:
  • Validated pains
  • Buyer intent (people shopping for tools)
  • Weak signals worth tracking
  • Ranked product opportunities

You can treat Miner’s email as:

• Input into your own demand log (copy over items that fit your interests)
• A way to watch new niches or pains without searching for them manually
• A “safety net” that keeps your demand discovery running when you’re heads-down building

You still own the decisions. Miner just reduces the time from “firehose of posts” to “shortlist of interesting signals.”

Avoiding Common Failure Modes

As you build this habit, watch out for these traps.

1. Overfitting To One Loud User

Danger signs:

• One charismatic person complains loudly about a niche problem.
• You over-weight their opinion because they’re famous or you like them.

Guardrail:

• Don’t move a problem into “top priority” unless you’ve seen multiple independent people express similar pain.

2. Chasing Vague Trends

Danger signs:

• You’re building “an AI thing” because everyone is.
• Most of your evidence is hype (“AI will change everything!”) rather than specific pain.

Guardrail:

• Only log items that include concrete jobs-to-be-done and workarounds, not just buzzwords.

3. Confusing Interest With Intent

Danger signs:

• People say “cool idea” or “I’d use that” but never commit to paying, introducing you to their team, or giving you real data.

Guardrail:

• In your log, distinguish:
  • “Nice noise” (likes, retweets, hand-wavy praise)
  • “Real intent” (pricing questions, “when can we try this?”, offering data)

4. Treating Discovery As A One-Time Checklist

Danger signs:

• You validate an idea once, build for 6–12 months, and never revisit whether demand is evolving.

Guardrail:

• Keep updating your log even after launch:
  • Are new pains adjacent to your current product?
  • Are old pains disappearing because of platform changes?

This is how you avoid becoming a “stale tool” nobody needs in 2 years.

Start Small, Let It Compound

Demand discovery isn’t mysterious. It’s mostly:

• Looking in the right places
• Knowing what signals to watch for
• Writing them down in a structured way
• Re-reading your own notes and acting on them

As an indie hacker, you don’t need sophisticated research ops. You need a habit you can sustain while you’re also coding, marketing, and supporting users.

Here’s a minimal version you can start this week:

1. Create a simple demand log (sheet or Notion).
2. Set 3–5 saved searches on Reddit and X around audiences you know.
3. Spend 20 minutes a day logging 2–3 real pains you see.
4. Do a 45-minute weekly review to score and cluster them.
5. Commit to one concrete bet to explore each month.

If you want higher-signal inputs with less manual scanning, layer in a tool like Miner’s daily brief to feed you pre-filtered Reddit and X conversations. But your edge doesn’t come from the tool — it comes from the discipline of ongoing demand discovery.

Stop optimizing for idea quantity. Start optimizing for evidence of demand. The compounding advantage for indie hackers isn’t building faster; it’s building where the pull already exists.