You probably have a long list of product ideas, and every week Twitter/X or Reddit adds ten more. The real problem isn’t coming up with ideas—it’s choosing one based on evidence instead of vibes.

This guide walks through a scrappy, repeatable demand research framework for product ideas that you can run manually in a few hours per week. You’ll use Reddit and X to capture real language, log signals in a simple sheet, and turn that into a score you can use to rank ideas. Tools like Miner can later automate a lot of this, but the logic stays the same.

What “Demand Research Framework” Means Here

For solo founders and small teams, a demand research framework is:

A simple, repeatable way to collect, log, and score real-world demand signals for each product idea, so you can compare ideas objectively.

It is not:

• A huge market research report
• A full-blown TAM/SAM/SOM analysis
• A 60-slide deck for a board meeting

It is:

• A short list of demand signals you care about
• A habit of scanning real conversations (Reddit, X, etc.)
• A spreadsheet where each idea gets a score based on those signals

Your goal: move from “I feel like this idea is hot” to “This idea scores 68/100 on demand, and this other one scores 34/100, here’s why.”

Why You Need This Before Writing Code

When you skip structured demand research:

• You over-index on the last conversation you had
• You chase whatever is loud on X this week
• You build for “people like me” instead of people with urgent problems and budgets

A simple demand research framework for product ideas helps you:

• Compare 5–20 ideas on the same criteria
• See which ideas have evidence of pain and buyer intent
• Decide what to validate with MVPs, landing pages, or presales
• Kill weak ideas earlier, before you sink months into them

You don’t need to be perfectly “data-driven.” You just need enough structure that you can explain, to yourself, why Idea A beats Idea B.

The Core Demand Signals To Track

Keep this small and sharp. You can always add nuance later.

Here’s a battle-tested starter set of demand signals:

1. Problem severity – How painful is the problem when people describe it?
2. Urgency – Do people need a solution now or “someday”?
3. Frequency of complaints – How often does this pain show up?
4. Explicit buyer intent – Are people actively looking for tools or posting “what should I use?”
5. Budget / willingness to pay – Are price and budgets mentioned, or is it all “free hack” talk?
6. Quality of existing solutions – Are people happy, or constantly complaining about current tools?

You’ll eventually score each idea 1–5 on each of these.

Simple Definitions And Scales

Use simple language so you can move fast.

Problem severity (1–5)

• 1 = Mild annoyance, “would be nice to fix”
• 3 = Frustrating, slows them down, but they cope
• 5 = Critical, blocks revenue/time, “I’m screwed if this doesn’t work”

Urgency (1–5)

• 1 = “Some day I should improve this”
• 3 = “I need to fix this in the next few months”
• 5 = “I’m actively searching today / this week”

Frequency of complaints (1–5)

• 1 = One-off rant you never see again
• 3 = You spot it weekly in your niche
• 5 = Constant surface area; you see it everywhere once you look

Explicit buyer intent (1–5)

• 1 = Only describing pain, no talk of tools
• 3 = Vague asks like “any tools for X?”
• 5 = “What’s the best paid tool for X?” “Happy to pay for something that does Y”

Budget / willingness to pay (1–5)

• 1 = “I’m not paying for this”, “any free options?”
• 3 = “I’d pay if it actually worked”
• 5 = “We spend $X on this today and it sucks”, “We’d pay a premium if…”

Quality of existing solutions (1–5, reversed)
Higher = worse existing tools, better for you.

• 1 = “I love Tool Z for this; it’s perfect”
• 3 = “Tool Z works but has annoying gaps”
• 5 = “All the tools suck / I built my own hack because nothing works”

You can add more later (e.g., market size, integration complexity), but this set is enough to start ranking.

Turning Reddit And X Into Demand Data

You don’t need fancy APIs. A browser, search box, and a bit of discipline goes a long way.

What To Search For

Pick 3–5 product ideas you already have. For each idea, brainstorm 3–7 phrases people might use when they complain about the underlying problem.

Example idea: “Analytics for small community-led SaaS”
Phrases to search:

• “community analytics is a mess”
• “hard to track community engagement”
• “any tool to measure community activation”
• “how do you track community contributions”

Now search on:

• Reddit: site:reddit.com "community analytics is a mess" (or within specific subreddits)
• X: use native search with “community analytics” filter:replies or “community analytics” -marketing

For each idea, also mix in:

• "any tools for X"
• "tool for X" OR "software for X"
• "how do you manage X"
• "struggling with X"
• "solution for X"

You’re looking for natural language, not startup-speak.

Where To Look On Reddit

Useful subreddits depend on your target user, but common starting points:

• /r/Entrepreneur, /r/startups, /r/SaaS, /r/indiehackers
• Niche subs like /r/personalfinance, /r/Teachers, /r/smallbusiness, /r/dataengineering

Within threads, scan for:

• Complaint clusters – multiple people saying “same” / “this is killing me”
• Tool comparisons – “I tried A, B, C, they all fail at…”
• Price talk – “we pay $X for Y and it still doesn’t do Z”
• DIY hacks – “I glued together Airtable + Zapier because nothing exists”

These are all demand signals you’ll log.

Where To Look On X

On X, search terms like:

• "any tools for" + [problem]
• "what do you use for" + [workflow]
• "how do you manage" + [problem]

Then use filters:

• min_faves:5 or min_faves:20 to find non-trivial engagement
• filter:replies to see actual conversations

Look for:

• People tagging multiple tools and debating pros/cons
• Replies that say “I built something for this” (indicates recognized problem)
• Replies like “I’d pay for that” or “I’d switch if X did Y”

A tool like Miner can automate this sweep by continuously watching Reddit and X for repeated pain, buyer intent phrases, and weak signals, then delivering a daily brief. But you can absolutely start by running these searches manually.

How To Capture Signals In A Simple Sheet

Use whatever’s easiest: Google Sheets, Notion, Airtable, or even a text doc with tables. The key is consistency.

Create a sheet with:

• One tab: Ideas
• One tab: Evidence

Ideas Tab

Columns:

• idea_id – short code like IDEA-1
• idea_name – “Community analytics for SaaS”
• who – target user (role, niche)
• problem – one-sentence problem description
• notes – free-form notes

Example:

Evidence Tab

This is where Reddit/X threads get turned into demand signals.

Columns:

• idea_id – which idea this supports
• source – reddit or x
• url – link to the thread/post
• snippet – copy-pasted quote of the relevant text
• problem_severity (1–5)
• urgency (1–5)
• frequency (1–5) — your sense of how common this is becoming
• buyer_intent (1–5)
• willingness_to_pay (1–5)
• existing_solutions_quality (1–5)
• notes – any context

You don’t need to fill every column for every snippet; leave blanks if it’s unclear.

Example row:

Run this log for each idea for an hour or two. Aim for 10–20 meaningful snippets per idea, not hundreds.

Building A Simple Scoring Model

Once you have evidence, you want to summarize it into numbers per idea.

Step 1: Aggregate Per Idea

For each idea, compute an average (or median) for each signal across its evidence rows:

• avg_problem_severity
• avg_urgency
• avg_frequency
• avg_buyer_intent
• avg_willingness_to_pay
• avg_existing_solutions_quality

You can do this with AVERAGEIF in Sheets:

=AVERAGEIF(Evidence!A:A, "IDEA-1", Evidence!D:D)

(Adjust ranges for the right columns.)

Step 2: Decide Weights

Not all signals are equal. For early-stage SaaS, a reasonable starting weight set might be:

• Problem severity: 25%
• Urgency: 20%
• Frequency: 20%
• Buyer intent: 15%
• Willingness to pay: 10%
• Existing solutions quality: 10%

You can encode this as:

demand_score = 0.25 * severity + 0.20 * urgency + 0.20 * frequency + 0.15 * buyer_intent + 0.10 * willingness_to_pay + 0.10 * existing_solutions_quality

Given each component is 1–5, the total will also be between 1–5. If you prefer a 0–100 scale, just multiply by 20.

Step 3: Example Scores

Let’s say you have three ideas:

• IDEA-1: Community analytics for SaaS
• IDEA-2: Simple invoice reminder bot for freelancers
• IDEA-3: AI tool for summarizing long Discord channels

After logging Reddit/X evidence, your aggregated scores might look like:

Even in this fake example you can see:

• Idea 2 edges out Idea 1 on buyer intent and willingness to pay
• Idea 3 has high severity for a niche of users, but low urgency and weak buyer intent

Now your roadmap conversation changes from “I like Discord AI stuff” to “Invoice bot and community analytics both show stronger, broader demand right now.”

Using Scores To Rank And Decide

The point of the demand research framework for product ideas is not perfection. It’s to make tradeoffs explicit.

Once you have demand scores:

1. Rank by demand score
   Sort your ideas by demand_score. Top 2–3 are your “A-tier” candidates.

2. Overlay your constraints
   Add columns for build_complexity and distribution_edge (1–5 each). Sometimes a slightly lower-demand idea is still better if you can build and distribute it way faster.

3. Define decision rules
   For example:
   • If demand_score >= 75 and build_complexity <= 3, move to landing page test
   • If demand_score between 60–75, run more research or narrower positioning
   • If demand_score < 60, archive or park the idea

4. Plan your next test
   For your top idea, decide one concrete next step:
   • Build a waitlist page and post it into the same Reddit/X threads (if allowed)
   • DM or email people who complained and ask for a quick call
   • Run a simple presale or pilot offer

The scores don’t choose for you; they force you to justify going against them.

Example: Running The Framework In A Weekend

To make this feel real, here’s how a solo builder could run this in 4–6 hours.

Friday evening (1–2 hours)

• List 5 product ideas you’d actually consider building
• Set up the Ideas and Evidence tabs
• For each idea, brainstorm 3–7 search phrases

Saturday morning (2–3 hours)

• For each idea, do targeted searches on Reddit and X
• Capture 10–20 solid snippets per idea in Evidence
• Score each snippet on severity, urgency, etc. as you go

Saturday afternoon (1 hour)

• Aggregate averages per idea
• Calculate demand_score for each
• Rank ideas and pick one “lead” and one “backup”

Sunday (optional)

• Sketch your first test: landing page, outreach, or prototype
• Write down what would count as “good” demand signals from that test

After that, you can maintain the sheet with 30–60 minutes of research each week, adding new evidence as it appears.

If you want the scanning part handled for you, a tool like Miner can feed you a daily brief of high-signal Reddit/X threads that match your themes, with pain, intent, and opportunity already extracted. You still apply your own scoring and judgment—but you skip hours of raw searching.

Keeping The Framework From Becoming Overwhelming

The fastest way to kill this habit is to make it too heavy. Keep it lean.

• Limit your idea list – Score 3–7 ideas at a time, not your entire brain dump.
• Limit your signals – Start with the six signals above; don’t add more until you’ve used them for a few weeks.
• Limit your evidence – 10–20 strong snippets per idea beat 200 low-signal bookmarks.

Think of this as a “scrappy scoreboard,” not a full research department.

Iterating On Your Framework Over Time

Your first version won’t be perfect. Good.

Treat your framework like a product:

• Adjust weights based on outcomes
  After 2–3 ideas, look back: which ideas “scored high” but fizzled? Which scored lower but performed? Adjust weights accordingly (maybe buyer intent matters more than you thought).

• Add/remove signals
  If you repeatedly see a pattern like “team size” or “regulatory pressure” mattering, add it as a signal. If one signal never moves the needle, drop it.

• Tighten your niches
  You might realize “small agencies with 3–10 people” has very different dynamics than “solo freelancers.” Split your scoring by segment.

• Automate parts you trust
  Once you like your framework, you can start automating data collection. This is where products like Miner help: they continually scan Reddit and X, detect repeated pain and buyer intent language, and surface ranked opportunities as a daily brief. You stay in control of the framework; Miner just feeds it cleaner, faster input.

The framework is a living artifact. Every idea you test should give you feedback on whether your scores predicted reality.

Putting It All Together

To recap the demand research framework for product ideas:

1. Define your demand signals – Severity, urgency, frequency, buyer intent, willingness to pay, and existing solutions quality.
2. Mine Reddit and X – Search for real complaints, tool discussions, and budget talk related to each idea.
3. Log evidence in a simple sheet – One tab for ideas, one for supporting snippets with 1–5 scores.
4. Aggregate and score – Compute average signal scores per idea and roll them into a 1–5 or 0–100 demand score.
5. Rank and decide – Sort ideas, apply your constraints, and pick specific next tests.
6. Iterate and optionally automate – Refine weights and signals over time; use tools like Miner to keep your pipeline of fresh, high-signal conversations full.

You don’t need perfect data to make better decisions—you just need a simple, consistent way to turn messy social chatter into a structured, comparable view of demand.

Start with three ideas, one spreadsheet, and one weekend. The next product you ship will have a much better shot at actually being wanted.