Indie makers don’t lack ideas. You scroll X, lurk in niche subreddits, see a dozen “what if we built X with AI?” posts every week, and your notes app is overflowing.

The real problem is different: you have almost no evidence about which ideas have strong, real demand.

You likely have:

• limited time (building, shipping, probably a day job),
• a tiny audience (no big mailing list to survey),
• no research team or survey panel,
• and a backlog of half-built experiments that never found traction.

This article lays out a practical, repeatable workflow for demand research for indie makers: how to mine public conversations (especially Reddit and X) for concrete demand signals, log them, score them, and turn them into product opportunity statements you can actually test.

You can run everything here manually with a browser, a spreadsheet, and a notes app. Tools like Miner simply automate the scanning and help you see more signals with less time, but the workflow itself is the same.

What “Demand Research” Means For Indie Makers

For indie makers, “demand research” is not a 60‑page report, panel survey, or formal market study.

A useful, simple definition:

Demand research is the habit of systematically looking for evidence that real people are struggling with a problem, trying to solve it, and willing to pay for a better solution.

That means:

• collecting recurring complaints and pains,
• spotting buyer intent (“what tool do you use for…?”),
• noticing DIY hacks and spreadsheets people built,
• and checking if people mention budget, urgency, or switching tools.

It is very different from:

• “I had this cool idea in the shower”,
• “my friend said they would use this”,
• or “I saw one tweet about this once”.

Intuition and vibes are useful for exploring. But if your build time is limited, you want to make sure at least some of your projects start from demand, not just inspiration.

Why “Vibes-Only” Ideas Are So Risky

Most indie products die quietly because there was never enough real demand behind them.

Typical pattern:

1. You see a trend (AI, no‑code, crypto, whatever).
2. You imagine a clever product.
3. You build for weeks or months.
4. You ship to silence. Maybe a few curious makers try it, but no one cares enough to pay or keep using it.

What went wrong? Usually one of:

• The problem wasn’t painful enough.
• The problem was rare or niche in the wrong way.
• People had already found an “okay” solution and didn’t care to switch.
• The people who cared most weren’t in your reachable audience.

Demand research is how you reduce those risks before you commit big chunks of time. It’s not about certainty (you’ll never have that); it’s about shifting the odds in your favor with a few hours of structured listening and logging every week.

Where To Listen: High-Signal Places For Indie Demand

If you’re solo or in a tiny team, you can’t boil the internet. You need a shortlist of high-signal places where your target users complain, ask, and compare tools in public.

For most indie hackers and SaaS builders, these are:

• Reddit: topic-based, long-form, semi-anonymous complaints and confessions.
• X/Twitter: fast-moving, opinionated, with lots of “I wish there was a tool for…” posts.
• Niche communities: Discord servers, Slack groups, specialized forums.
• Product reviews: G2/Capterra, App Store, Chrome Web Store reviews.

In this guide, we’ll focus on Reddit and X because they are:

• searchable,
• rich in context,
• and already where you probably spend time.

Think of them as a giant, always-on user interview feed.

Setting Up A Simple Demand Research Log

Before you start searching, set up a minimal capture system. If you don’t log and structure what you find, you’ll forget it.

Use whatever you’ll maintain:

• a simple spreadsheet (Google Sheets, Notion database, AirTable),
• or even a text file/notes app with a consistent template.

For a spreadsheet, start with columns like:

• ID – simple increment (1, 2, 3…)
• Problem summary – one sentence in your own words
• Original quote – copy/paste from Reddit/X
• Source – reddit, x, etc.
• Link – URL to the thread or tweet
• Audience – who has this problem (e.g., “solo SaaS founders”, “freelance designers”)
• Signals – pain, buyer_intent, workaround, weak_signal
• Severity – 1–5
• Frequency – 1–5
• Urgency – 1–5
• Willingness_to_pay – 1–5 (if you see hints)
• Notes – any extra thoughts or related ideas
• Opportunity_score – formula based on the scores above

You can refine as you go, but starting with a simple structure beats a pile of untagged bookmarks.

Demand Research For Indie Makers: A Step‑By‑Step Workflow

Here’s a concrete weekly workflow you can run in 60–90 minutes.

1. Pick 1–2 audiences you care about.
2. Run targeted searches on Reddit and X to surface pain and buyer intent.
3. Skim quickly for strong signals; ignore most noise.
4. Log the best signals in your research log.
5. Score and rank opportunities.
6. Turn the strongest ones into clear opportunity statements.

Let’s go through each step with specific queries and examples.

Step 1: Choose A Specific Audience

“Everyone who uses AI” is not an audience.

Work with something like:

• “solo SaaS founders using Stripe”
• “freelance designers working with clients”
• “Notion power users running small teams”
• “indie newsletter writers”
• “Zapier/Make/automation fans”

You can have more than one in your head, but for one research session, pick one. It makes searching and filtering easier and your notes more coherent.

Write your current target at the top of your log: Audience: solo SaaS founders or similar.

Step 2: Run High-Signal Reddit Searches

Reddit is brutally honest. People:

• complain in detail,
• confess their struggles,
• and ask “dumb” questions they wouldn’t post on LinkedIn.

Use Google or Reddit’s own search with specific patterns.

Basic Reddit Search Patterns

Assume your audience is “freelance designers”.

In Google:

• site:reddit.com "freelance designer" "how do you manage"
• site:reddit.com "freelance designer" "is there a tool"
• site:reddit.com "freelance designer" "I hate doing"
• site:reddit.com "freelance designer" "how do you handle"
• site:reddit.com "freelance designer" "frustrated with"
• site:reddit.com "freelance designer" "I’m stuck"

Or if your audience is “SaaS founders”:

• site:reddit.com "SaaS founder" "how do you manage"
• site:reddit.com "Stripe" "I hate reconciling"
• site:reddit.com "B2B SaaS" "client onboarding is a nightmare"
• site:reddit.com "API docs" "so confusing"

Generic phrases that often reveal pain:

• "I hate doing"
• "I’m so tired of"
• "is there a tool for"
• "how do you manage"
• "how do you track"
• "what do you use for"
• "this takes me hours"

Mix these with your audience or domain keywords:

• freelancer,
• agency owner,
• Notion,
• Zapier,
• cold email,
• SaaS,
• indie hacker,
• etc.

Example Reddit Snippets And What They Mean

Example 1:

“I’m a freelance designer and I hate chasing clients for feedback. I send Figma links, Loom videos, emails… and still end up with 3 different comment threads. Is there a tool that centralizes this or is everyone just dealing with this chaos?”

Signals:

• pain – “hate”, “chaos”
• buyer_intent – “is there a tool”
• workaround – multiple tools used
• audience – freelance designers

Example log entry:

• Problem summary: Designers have fragmented client feedback across Figma, Loom, email.
• Original quote: [paste the snippet + link]
• Audience: freelance designers
• Signals: pain, buyer_intent, workaround
• Severity: 4 (strong frustration)
• Frequency: 3 (you might see similar posts)
• Urgency: 3
• Willingness_to_pay: 3 (asking for a tool, not explicitly about budget)
• Notes: potential “client feedback inbox” that integrates Figma, Loom, email; check if similar tools exist.
• Opportunity_score: auto-calculated (e.g., average of Severity+Frequency+Urgency+WTP)

Example 2:

“Indie SaaS founders: how do you manage failed payments and dunning? I hacked together some Stripe webhooks but it’s brittle and I always forget to follow up manually.”

Signals:

• pain – brittle hack, forget to follow up
• buyer_intent – implicit (“how do you manage”)
• workaround – Stripe webhooks + manual follow-up
• audience – indie SaaS founders

Example log entry:

• Problem summary: Indie SaaS founders struggle to manage failed payments and follow-ups reliably.
• Signals: pain, workaround
• Severity: 4
• Frequency: 4 (this appears a lot)
• Urgency: 4 (direct revenue impact)
• Willingness_to_pay: 4 (it’s about money recovery)
• Notes: Many tools exist; opportunity maybe in “indie‑friendly, low‑code dunning” or better education.

You’re not judging yet whether you’ll build this. You’re just collecting and scoring evidence.

Step 3: Run Targeted X/Twitter Searches

X moves quickly and is noisier, but it’s great for:

• spur-of-the-moment rants,
• “I wish there was a tool for…” tweets,
• people sharing their workflows and hacks.

Use X’s search with keywords plus signal phrases.

For “indie hackers building SaaS”:

• "I hate doing" "invoicing"
• "is there a tool" "Stripe payouts"
• "how do you manage" "churn"
• "what do you use for" "user feedback"
• "this takes me hours" "cold email"
• "I wish there was a tool" "Notion"

You can also mix in hashtags or identities:

• #indiehackers "I hate"
• "as a solo founder" "how do you manage"
• "freelance designer" "client feedback"

Example X snippet:

“as a solo founder I spend more time screenshotting Stripe dashboards for my updates than actually talking to users. is there a simple way to auto-generate a weekly metrics digest?”

Signals:

• pain – time wasted
• buyer_intent – “is there a simple way”
• audience – solo founders
• workaround – manual screenshots
• job_to_be_done – share metrics updates

Log it like before. Over time, you’ll see patterns.

Step 4: Skim Threads For Demand Signals, Not Just Opinions

You’ll see a lot of:

• generic rants (“everything sucks”),
• hot takes,
• advice threads.

You’re looking for a few specific signal types:

• Pain – “I hate…”, “this is so frustrating”, “I’m stuck”, “this takes forever”.
• Buyer intent – “is there a tool for…”, “what do you use for…”, “any recommendations for…”.
• Workarounds – custom spreadsheets, Zapier automations, scripts, Notion dashboards.
• Switching behavior – “I moved from X to Y because…”.
• Budget / willingness to pay – mentions of cost, “I’d pay for…”, “we spend $X/month on…”.

When you open a thread:

1. Read the original post.
2. Scan the top comments (sorted by “top” or “best”).
3. Ask:
   • Is there a clear problem?
   • Is it recurring (do multiple people chime in “same here”)?
   • Are people actively seeking solutions or just venting?
   • Are they building hacks or paying for suboptimal tools?

If yes, consider logging it. If it’s just a rant with no clear problem or solution search, move on.

You’re optimizing for signal density, not completeness.

Step 5: Tag And Log Findings Quickly

You don’t need to log every detail. You need consistent, light metadata.

A simple manual workflow:

1. When you see a good signal, copy the relevant quote + link.
2. Drop it into your spreadsheet with:
   • a 1‑sentence Problem summary,
   • Audience,
   • Signals tags (e.g., pain, buyer_intent),
   • and rough 1–5 scores for Severity, Frequency, Urgency, WTP.
3. Add a short Notes line with any ideas or context.

Aim for 5–15 high-quality entries per session, not 200 half-baked notes.

If you do this consistently for a few weeks, you’ll build your own small “demand archive”.

Tools like Miner essentially do this at scale for you: scanning Reddit and X for specific audiences, extracting posts with clear pain/buyer intent, tagging them, and ranking them by signal strength. The point of this article is that you can start manually today, then decide later whether to offload the tedious part.

Step 6: Score Opportunities With A Lightweight Formula

You don’t need a perfect scoring model. You need something better than “this feels cool”.

Use four core dimensions:

• Severity – how painful is the problem when it occurs?
• Frequency – how often does it occur?
• Urgency – do people need it solved now or “someday”?
• Willingness_to_pay – do they indicate they’d pay, or is it something they tolerate?

Each on a 1–5 scale is usually enough:

• 1 = low, 5 = very high.

Example:

• A mild annoyance that happens weekly with no mention of budget might be:
  • Severity 2, Frequency 3, Urgency 2, WTP 1.
• A problem that blocks revenue and people actively search for tools:
  • Severity 5, Frequency 4, Urgency 4, WTP 4 or 5.

Define a simple formula in your spreadsheet, e.g.:

Opportunity_score = (Severity + Frequency + Urgency + Willingness_to_pay) / 4

Or weight some factors more:

Opportunity_score = (Severity * 0.4) + (Frequency * 0.3) + (Urgency * 0.2) + (WTP * 0.1)

You don’t need to overfinesse it. The goal is ranking:

• See your top 10 opportunities by score.
• Notice clusters (e.g., lots of high-score problems around “client communication”).
• Ignore the bottom of the list unless something still intrigues you.

Miner’s daily briefs do a variation of this: aggregating and ranking demand signals so you don’t have to eyeball hundreds of posts.

Step 7: Turn Signals Into Product Opportunity Statements

Raw posts are messy. You want to convert them into clear statements you can test.

A simple template:

[Audience] struggle with [problem] when [context]. They currently [workaround], which leads to [negative outcome]. They show [signals of demand].

Example, using our freelance designer snippet:

Freelance designers struggle to manage scattered client feedback when presenting design iterations. They currently juggle Figma comments, Loom videos, and email threads, which leads to missed comments, delays, and frustration. They show demand through posts asking “is there a tool for this?”, DIY workflows, and repeated complaints about feedback chaos.

Another, from the dunning example:

Indie SaaS founders struggle to manage failed payments and dunning when they rely only on basic Stripe tools. They currently stitch together webhooks and manual follow-ups, which leads to churn and lost revenue. They show demand through repeated threads on how to handle dunning, mentions of recovered revenue, and willingness to buy tools in this space.

Drop these statements into a separate tab or doc called Opportunities. Include:

• a link back to your log entries,
• your Opportunity_score,
• and potential solution angles.

This is what you work from when you consider:

• building an MVP,
• launching a landing page test,
• or running deeper interviews.

From Opportunity To MVP: Simple Next Moves

Demand research is only step one. To move from opportunity statements to actual products:

1. Pick 1–3 top opportunities by score and your personal interest.
2. Validate slightly deeper:
   • search specifically for that problem + “how do you manage” + “what tool do you use”,
   • check existing tools, their reviews, and pricing,
   • maybe ask a clarifying question in a subreddit or on X.
3. Run a tiny validation experiment:
   • a landing page describing the problem and your proposed solution,
   • a waitlist form,
   • a manual “concierge” version of the product with a couple of users,
   • or a super small feature prototype.

Your demand research gives you the raw material to write clear copy:

• “If you’re a [audience] and you’re tired of [problem] happening every [frequency], this helps you [better outcome] without [common workaround].”

Even if you use a tool like Miner to supply you with daily high-signal opportunities, you still need to choose which ones fit your skills, interests, and reach.

Making Demand Research A Weekly Habit

The worst mistake is treating demand research as a one-off pre-launch task.

For indie makers, it works best as a recurring habit:

• 1–2 sessions per week,
• 30–45 minutes each,
• focused on listening and logging, not selling.

A simple weekly cadence:

• Monday: 30 minutes scanning Reddit for your core audience.
• Wednesday: 30 minutes on X searches + logging.
• Friday: 30 minutes reviewing your log, updating scores, and writing 1–2 opportunity statements.

Over weeks, you’ll:

• build a personal demand archive,
• notice patterns (e.g., “everyone hates X but tolerates Y”),
• and have a backlog of validated problems ready when you have time to build.

If you find the searching and logging part tedious or you want more volume than you can manually scan, this is where Miner fits: it’s a paid daily brief that does the mining across Reddit and X for you and delivers ranked, evidence-backed opportunities and weak signals worth tracking. You keep control of what to pursue; you just offload the grunt work of finding and structuring the signals.

Putting It All Together

In practice, demand research for indie makers looks like this:

• Decide who you’re listening to this week.
• Search Reddit and X with specific, pain-focused queries.
• Skim threads for clear signals: pain, buyer intent, workarounds, budget.
• Log only the strongest examples with short summaries and scores.
• Rank opportunities using a simple scoring formula.
• Turn your top signals into concise opportunity statements.
• Feed those into small validation experiments and MVPs.
• Repeat weekly so your intuition is shaped by real evidence, not just vibes.

You’ll still take bets. You’ll still chase ideas that excite you. But instead of starting from “cool tech” and hoping users show up, you’ll start from problems people already have and already talk about.

Whether you continue doing this manually or bring in a tool like Miner to handle the scanning and extraction, the underlying skill is the same: becoming the kind of indie maker who listens systematically to the market before committing months of build time.