Indie SaaS doesn’t usually die from lack of ideas. It dies from months spent building the wrong one.

Guessing feels fast. You hack on something that sounds cool, ship a polished v1, tweet a launch thread… then silence. That’s not just demotivating; it’s expensive MRR you’ll never see and time you don’t get back.

This is where demand research comes in. Not as a "corporate research process", but as a lightweight habit that helps you see where demand already exists before you commit months of coding.

The goal of this guide: give you a practical, next-4–8-weeks playbook for demand research for indie saas founders. Something you can run alongside a day job, freelancing, or an existing product.

What Demand Research Actually Means For A Solo Founder

For a solo or tiny team, "demand research" is:

• Systematically collecting real-world signals that people have a painful problem
• Understanding who feels that pain, how often, and how urgently
• Using that evidence to prioritize what to explore, prototype, or kill

It is not:

• Running a giant survey that 12 people fill out
• Asking friends if your idea is "cool"
• Scrolling Twitter/Reddit until you "feel" like there’s demand

Think of it as building a personal radar. You want to continuously answer: where is demand already trying to express itself, and can my skills intersect with that?

You can do the entire first version of this with:

• One spreadsheet
• One notes app
• A handful of saved searches and feeds
• A weekly recurring calendar block

Tools like Miner can later automate the "sit in Reddit/X all day" part, but the process is the same.

The 4 Core Questions Your Demand System Must Answer

If you strip away tactics, good indie SaaS demand research boils down to 4 questions.

1. Where are people already complaining?

You’re looking for raw, unpolished pain:

• "I’m losing clients because my scheduling tool keeps double-booking."
• "Our internal docs are a mess; I can’t find anything."
• "I’m manually copy-pasting Stripe data into a spreadsheet every week."

Places to see this:

• Reddit threads in your niche (r/freelance, r/indiehackers, r/smallbusiness, r/devops, etc.)
• X/Twitter replies and quote tweets on tools in your space
• Support forums, GitHub issues, app store reviews

If nobody is complaining, be suspicious. Either the problem isn’t painful, or you’re looking in the wrong room.

2. Who has the problem, and do they have budget?

"Freelancers" is not specific enough.

You want clarity like:

• "US-based design freelancers charging $2–5k per project"
• "Agencies with 5–20 employees managing client projects in Notion"
• "Shopify stores doing $20–100k/mo"

These details matter because:

• B2C users might complain loudly but never pay
• Tiny hobby projects may have real pain, but no budget
• Mid-sized businesses often have both urgent problems and willingness to pay

When you log a signal, always capture who it’s from, not just what they said.

3. How urgent and frequent is the pain?

One-off annoyances are weak signals. Recurring pain is gold.

Ask:

• Is this happening weekly or daily?
• Does it cost them time, money, or reputation?
• Do they hack together ugly workarounds?

Examples:

• Weak: "Once a quarter I need to export this data and it’s annoying."
• Strong: "Every day I manually merge Excel sheets from 3 tools, and if I screw up, we send wrong invoices."

Your goal: prioritize recurring, high-stakes problems over low-level annoyances.

4. What are they already doing to solve it?

Demand shows up as behavior, not opinions.

Look for:

• Paid hacks (paying a freelancer, using a duct-tape stack of tools)
• Time-consuming workarounds
• Homegrown scripts, spreadsheets, or internal dashboards
• Existing tools they complain about but still pay for

If they’re already spending time or money to solve it, that’s strong evidence the problem matters.

A Lean Demand Research Stack You Can Set Up In One Evening

You don’t need a big system. You need something you’ll actually use.

1. A single "Demand Log" spreadsheet

Create a sheet with columns like:

• Date
• Source (Reddit, X/Twitter, Slack, forum, call)
• Segment (who: "Notion-using agencies", "Stripe SaaS founders")
• Problem statement (raw quote or paraphrase)
• Frequency (daily/weekly/monthly/rare)
• Pain type (time, money, reputation, emotional stress)
• Existing workaround/tool
• Willingness to pay (guess: low/medium/high)
• Signal strength (1–5; rough gut score for now)
• Idea link (if it maps to a specific SaaS idea you’re tracking)

Keep this simple. You can refine columns later; the point is to capture signals, not organize your life.

2. A quick-note inbox

You’ll see signals when you’re not near the spreadsheet. For that:

• Use a notes app (Apple Notes, Obsidian, Notion, whatever)
• Add one pinned note called Demand Inbox
• Dump screenshots, quotes, links, and impressions

Once a week, you’ll triage this inbox into your Demand Log.

3. Discovery feeds (manual)

Set up a few focused feeds:

• Saved Reddit searches:
  • "hate" + <tool>
  • "is there a tool" + <job>
  • "how do you manage" + <process>
• X/Twitter:
  • Advanced search for phrases like "how do you track", "this tool is so buggy", "is there a simpler way to" plus niche keywords.
• Any niche Slack/Discord communities you’re part of.

If you already use a tool like Miner, this is where you’d plug in your interests and let a daily brief surface the best complaints and buying signals. If not, bookmarks and saved searches are fine.

4. Validation tools

You don’t need fancy UX tooling to validate demand early:

• Calendar app for quick calls
• Lightweight survey (Typeform, Tally, Google Forms) if needed
• A landing page builder (or a simple HTML page + Stripe payment link)
• Email list tool or bare Mailchimp/Substack for collecting interest

A Weekly Demand Research Routine For Indie SaaS (4–Week Plan)

Here’s a concrete routine you can run in ~2–3 hours/week.

Week 1: Set up and start collecting

Goal: Launch the system and get your first 20–30 signals.

1. Set up the Demand Log and note inbox.
2. Pick 2–3 target segments you understand reasonably well (e.g., "freelance developers", "Notion-using agencies", "small Shopify brands").
3. For each segment, spend:
   • 20–30 minutes scanning relevant Reddit subs
   • 20–30 minutes scanning X/Twitter conversations and replies
4. Capture:
   • Direct problem statements
   • Complaints about existing tools
   • "Is there a tool for…" posts
5. Add at least 20 entries to your Demand Log. Don’t worry about perfect scoring yet.

Week 2: Clean up and start scoring

Goal: Turn noise into a more structured view.

1. Triage your note inbox into the Demand Log.
2. For each entry, assign:
   • Frequency: daily/weekly/monthly/rare
   • Pain type: time, money, reputation, emotional
   • Willingness to pay: low/medium/high (your best guess)
3. Add a first Signal strength score (1–5) based on:
   • How often it recurs in your feeds
   • How intense the language is ("hate", "desperate", "losing clients", etc.)
   • Whether you see obvious paid workarounds
4. Keep collecting 5–10 new signals across your channels.

By the end of week 2, you want 30–50 logged signals and rough scores.

Week 3: Cluster and talk to humans

Goal: Group pains into themes and validate with actual conversations.

1. Cluster your log:
   • Add a Theme column (e.g., "client scheduling", "internal docs search", "Stripe reconciliation").
   • Group similar problems under the same theme.
2. Identify the top 3 themes by:
   • Number of signals
   • Average signal strength
3. For each of the top 3 themes:
   • Reach out to 3–5 people for short calls
     • On Reddit/X, reply or DM:
       "Saw your comment about <problem>. I'm exploring a tool to help with exactly that. Would you be open to a 15-min call to walk me through how you handle it today?"
4. On calls, ask:
   • "Walk me through the last time this happened."
   • "What do you currently do to handle it?"
   • "What goes wrong with your current process?"
   • "If this magically went away, what would change for you?"
   • "Have you looked for tools? Which ones? Why didn’t they work?"
5. Log call notes as separate entries linked to the same Theme.

You’re not pitching. You’re validating the problem depth and understanding real workflows.

Week 4: Quick validation loops

Goal: Run 1–2 fast experiments on your top theme.

For your strongest theme:

1. Write a very specific problem statement:
   • "Small agencies using Notion to manage projects struggle to keep client deliverables visible; they lose track and have awkward client conversations."
2. Create a simple landing page:
   • Headline: state the problem plainly
   • 2–3 bullets of the outcome (not features)
   • An email capture or "Request early access" form
3. Share it where your signals came from:
   • Reply to relevant threads with a helpful message plus your page if appropriate
   • DM people from your calls
   • Post in a relevant community, but lead with value and context
4. Track:
   • Clicks / page views
   • Email signups
   • Replies that say "I need this now" vs polite interest
5. Optional: Pre-sell
   • Offer a discounted early adopter plan or paid pilot to 3–5 people
   • If you get 2–3 yeses from your exact target segment, that’s a strong signal

This is "validation enough" territory for a small v1.

Turning Messy Signals Into A Ranked Opportunity Backlog

Now you have themes, calls, and maybe some landing page data. How do you decide what to work on?

Use a simple scoring model that you can apply in 10 minutes.

A lightweight demand score

For each theme, score 1–5 on:

• Pain intensity (1 = mild annoyance, 5 = people say "this is killing us")
• Frequency (1 = rare, 5 = daily)
• Monetization potential (1 = users resist paying, 5 = obvious money/revenue impact)
• Segment clarity (1 = vague, 5 = very specific and reachable)
• Personal fit (1 = outside your expertise/interest, 5 = perfect overlap with your skills)

Example:

• Theme A: "Internal docs search for small tech teams"
  • Pain intensity: 4
  • Frequency: 4
  • Monetization: 3
  • Segment clarity: 5
  • Personal fit: 4
  • Total: 20

• Theme B: "Habit tracker for anyone who wants to read more"
  • Pain intensity: 2
  • Frequency: 4
  • Monetization: 1
  • Segment clarity: 2
  • Personal fit: 5
  • Total: 14

You don’t need precision; you need a consistent way to compare ideas so you stop bouncing between them.

Add a Demand score column to your backlog sheet, and sort descending. The top 1–2 themes are your candidates for a focused validation sprint.

Strong vs weak signals (with examples)

Strong signal examples:

• Multiple people in the same segment independently describe the same problem
• They’re already paying for a tool and complaining about it
• They use harsh, emotional language ("hate", "nightmare", "keeps breaking", "we lose money when…")
• They hack together scripts/spreadsheets to cope
• They’re willing to jump on a call unprompted to talk about it

Weak signal examples:

• One person casually mentions an annoyance
• Idea comes from your imagination, not observed behavior
• Lots of likes/retweets on your "idea tweet" but no one joins the waitlist
• People say "Cool idea!" but ignore your request for a call or demo

When ranking SaaS ideas by demand, favor strong signals even if they’re less exciting than your pet idea.

When Is An Indie SaaS Idea "Validated Enough" To Build V1?

You’ll never have perfect certainty. But you can define a clear "good enough" bar.

For a focused v1 (4–8 weeks of build time), look for something like:

• 10–20 demand log entries pointing to the same theme from different people
• 5+ people who match your target segment and have:
  • Confirmed the problem on calls
  • Described painful, recurring workflows
• A landing page with:
  • Visitors from your target niche
  • 10–30% of them opting in for early access (from warm traffic like DMs and niche posts)
• At least 2–3 people saying some version of:
  • "If you can solve X and Y, I’d happily pay $Z/mo"
  • Bonus: they agree to a pre-order or pilot

Red flags:

• Interest is vague: "Yeah that would be nice" but no one gives specifics
• People won’t commit to a call
• People suggest adding it to an existing tool instead of paying separately
• The problem is real but "we already have an internal script that works okay"

If you don’t hit your bar after a few weeks of effort, you have options:

1. Narrow the segment (e.g., "Notion-using agencies" instead of "people with messy docs")
2. Adjust the problem framing to what they actually complain about
3. Kill or shelve the idea, and move to the next highest scoring theme

Killing an idea with evidence is a win. It frees you to work on something with better odds.

Keeping Demand Research Going While You’re Building

Once you start building, demand research should shrink but not stop.

A minimalist ongoing habit

• Weekly (30–45 minutes):
  • Review your feeds or daily brief (e.g., Miner or your saved searches)
  • Add any new relevant signals to your Demand Log
• After every user call:
  • Log 2–3 sharp problem quotes
  • Update your understanding of frequency/urgency
• Monthly (1 hour):
  • Re-score your themes with new data
  • Check if any new patterns are emerging
  • Confirm that what you’re building still matches the strongest pains

This helps you avoid shipping v1 and then realizing the problem shifted or you misunderstood it.

How a tool like Miner fits in

As your time gets tighter, manually scanning Reddit and X/Twitter becomes a bottleneck. This is where a curated daily brief helps:

• Miner turns noisy Reddit/X conversations into a short daily email of:
  • Validated pain points
  • Product opportunities
  • Buyer intent ("we need a tool for…", "what do you use for…")
  • Weak signals worth tracking
• You can skim the brief, drop relevant items into your Demand Log, and stay plugged into your niche with <10 minutes a day.

You still own the judgment and the process; Miner just makes the raw discovery step less time-consuming.

Putting This Into Action In The Next 48 Hours

To make this real, here’s a concrete checklist you can complete in the next two days:

• Create your Demand Log spreadsheet with the columns listed above
• Set up a Demand Inbox note
• Choose 2–3 specific target segments you understand
• Set up 3–5 saved searches on Reddit and X/Twitter
• Block 1–2 hours per week on your calendar labeled Demand Research
• Log your first 20 signals
• Pick one theme and schedule 2–3 short calls

From there, follow the 4-week routine:

• Week 1–2: Collect and score
• Week 3: Cluster and talk to humans
• Week 4: Run 1–2 quick validation experiments

Demand research as an indie SaaS founder doesn’t have to be heavy or academic. With a simple system and a weekly habit, you can stop guessing, start building what people are already trying to pay for, and give your next SaaS a far better shot at real revenue.