# Finding real user pain before building SaaS
> Source report: https://painfinder.app/reports/finding-real-user-pain-before-building-saas

## 1. What we're building
Build a problem-discovery and validation workspace for SaaS founders that continuously scans Reddit, niche communities, reviews, support channels, and sales calls for repeated complaints and buying intent. The product should cluster similar pain points, preserve the original wording, surface source links, and rank opportunities by urgency, frequency, and evidence of willingness to pay. It should also help founders move from signal to action by generating interview prompts, suggested outreach, and a simple validation workflow that confirms whether the problem is worth building for.

The must-have feature set is clear from the strongest asks: Reddit scanning/alerting, intent scoring, competitor complaint monitoring, feedback clustering, and a single searchable feedback repository. It also needs direct-user workflow tools: structured interview capture, call transcripts, follow-up prompts, and automatic conversion of scattered feedback into backlog-ready themes. The product should be opinionated about narrowing the wedge—showing one problem, one audience, and one buying signal at a time—rather than becoming another broad research dashboard. In practice, it would feel like a founder copilot that says, 'Here are the 3 real pains people keep repeating, here are the exact quotes, here are the people already asking for help, and here is how to validate them this week.'

**Working name:** SignalWedge
**Tagline:** Find repeated SaaS user pain + buyer intent from Reddit, then turn it into validation actions.
**Main goal:** Users leave each session with 1 actionable, evidence-backed problem cluster and a next validation step they can execute immediately.
**Target users:** Solo founders and small SaaS teams validating ideas who want faster, evidence-based problem discovery specifically from Reddit and related mentions.

**Main user result:** A single ranked problem cluster for one audience with preserved user quotes, sources, and ready interview prompts.
**5-minute outcome:** Set a few subreddits/keywords, review the top cluster, and export a validation checklist + outreach draft inputs.
**What we solve first:** Reddit-based detection → clustering of repeated pain → evidence preservation → opportunity ranking → interview prompts.
**Out of scope for MVP:**
- Full multi-source ingestion beyond Reddit (e.g., Intercom, reviews, sales calls)
- Automatic email/DM sending (we’ll export drafts and logs instead)
- Advanced competitor complaint monitoring across the web

## 2. Why this is worth building
- Verdict: **MEDIUM** (70/100)
- The evidence is unusually consistent across all chunks: founders, PMs, and operators repeatedly say the same thing—real user problems are hard to find, easy to misread, and usually hidden inside complaints or manual workflows. There is also strong cross-chunk demand for tools that monitor conversations, consolidate feedback, score intent, and guide validation before building. The repetition of this pain across many different contexts makes it a strong market-research signal. The only real caveat is that many adjacent asks are specialized, so the best product wedge will need to focus sharply on one workflow.

**Current pain:** Founders need a process to find authentic user complaints and buyer intent, but it’s time-consuming and scattered across communities. They also need the exact wording and context to validate the problem with real people.
**Current workaround:** Users manually search Reddit using complaint language/keywords, then copy threads into notes/spreadsheets and generate outreach by hand. Some try automation via scripts/zaps, but still end up doing extraction, classification, and follow-up planning manually.
**Why existing tools fail:** General social listening tools don’t transform posts into problem-first clusters with preserved evidence quotes and a validation workflow. Workflow-heavy assistants can draft messages, but founders still must manually find, qualify, and prioritize the right pain signals (instead of the system doing signal-to-action).

## 3. Must-have capabilities
### 3.1 Monitor chosen subreddits and keywords for real-time pain points
**Why:** Founders repeatedly asked for Reddit-based discovery and alerting on complaint language and niche communities.
**Evidence:** post #15330 — *"focus on specific keywords like "workaround," "how do I," and "frustrated" within niche subreddits."*

### 3.2 Find buyer-intent Reddit threads and conversations relevant to a niche
**Why:** Users want threads that show active need, not just generic chatter.
**Evidence:** post #15330 — *"search "I hate", "why does", "anyone else frustrated with""*

### 3.3 Cluster and classify feedback into repeated themes
**Why:** The product must turn scattered comments into reusable themes and categories.
**Evidence:** post #15345 — *"feedback classification"*

### 3.4 Preserve original quotes with source links and context
**Why:** The workflow needs exact wording so founders can validate the problem and cite it in outreach.
**Evidence:** post #15889 — *"share 2-3 specific problems I found in their industry with evidence from real reviews"*

### 3.5 Rank opportunities by urgency, frequency, and evidence of willingness to pay
**Why:** The product must help founders decide what is worth building, not just collect noise.
**Evidence:** post #15889 — *"Would 3 paying users commit today if I shipped this?"*

### 3.6 Generate interview prompts and follow-up questions from discovered pain
**Why:** Users wanted a workflow that converts findings into real validation conversations.
**Evidence:** post #15330 — *"what did you do about it after posting this"*

## 4. Use cases & user stories
A web app where users configure a small set of Reddit subreddits and “complaint + workaround + intent” keywords, then the system produces ranked, clustered pain opportunities with direct quotes and source links. For the top opportunity, the app generates interview prompts and a validation workflow state they can follow.

### Use cases
**4.1 A founder narrows a SaaS idea before writing code**
A solo founder wants to avoid building a feature no one wants. She sets up tracking for a few niche subreddits and complaint keywords, then the system surfaces repeated threads about a missing workflow, clusters them into one theme, and shows the exact quotes plus source links. It also generates interview prompts and a validation checklist so she can talk to 3 prospects this week before starting development.

**4.2 A growth team turns support chatter and reviews into a prioritized opportunity list**
A small SaaS team imports feedback from Intercom, reviews, and call notes into one repository. The system tags recurring complaints, highlights what users are asking for in their own words, and ranks the themes by frequency and urgency. The team then uses the follow-up workflow to contact affected users, confirm the pain, and decide which problem deserves a landing page and prototype first.

## 5. Pages & form factor
**Form factor:** Web SaaS dashboard with alerts and validation workflow
**Why:** The core job is ongoing monitoring, clustering, validation, and follow-up across many sources, which fits a browser-based workspace better than a single-surface tool. Users also explicitly want one searchable pool, alerts with context, and a workflow that turns discovered pain into outreach and validation actions.

### Pages
**5.1 Dashboard**
Primary landing page for daily monitoring, showing fresh pain signals, alert volume, and what needs review first.
Key elements:
- Hot opportunities feed
- Alert health/status strip
- Source coverage summary
- Priority ranking controls
- Saved searches / monitored topics

**5.2 Lead Inbox**
Operational queue of discovered posts, threads, and complaints that need triage, qualification, or outreach.
Key elements:
- Thread cards with source metadata
- Intent score and urgency score
- Dismiss / save / qualify actions
- Source quotes with links
- Cluster label and theme tag
- Bulk triage controls

**5.3 Opportunity Detail**
Deep view of a single problem cluster, preserving evidence, context, and why it matters.
Key elements:
- Original quote viewer
- Source link and author context
- Related threads and comments
- Pain theme summary
- Evidence-of-willingness-to-pay panel
- Next-step suggestions

**5.4 Validation Workflow**
Turn an identified pain into an explicit validation decision: interview, outreach, waitlist, or build.
Key elements:
- Go / no-go checklist
- Interview prompt generator
- Validation status timeline
- Candidate customer list
- Decision notes and approvals

**5.5 Outreach Center**
Compose and manage follow-up actions from discovered pain, including DMs, emails, and reminders.
Key elements:
- Reply composer
- Follow-up task list
- Recipient / thread context panel
- Template library
- Send schedule and reminder controls

**5.6 Search Builder**
Create and tune subreddit, keyword, and intent queries that find complaint-heavy or buyer-intent conversations.
Key elements:
- Keyword query builder
- Subreddit selector
- Complaint phrase templates
- Intent filters
- Saved searches

**5.7 Integrations**
Connect output to Slack, email, Sheets, and CRM systems so discovered problems and leads flow into the founder's workflow.
Key elements:
- Slack alert setup
- Email routing settings
- Google Sheets export
- CRM connections
- Integration status indicators

### Key functions
- **Scan monitored sources** *[on: Dashboard]*
  - Trigger: Scheduled background job or user clicks 'Run scan now'
  - Continuously checks selected subreddits and keywords for new pain signals and buyer-intent threads.
- **Build complaint query** *[on: Search Builder]*
  - Trigger: User adds a new search
  - Creates a reusable query using complaint verbs, workaround language, and niche subreddit filters.
- **Rank opportunities** *[on: Lead Inbox]*
  - Trigger: New thread ingested or user opens inbox
  - Assigns priority using urgency, frequency, recency, and evidence of willingness to pay.
- **Cluster feedback themes** *[on: Lead Inbox]*
  - Trigger: Multiple similar posts detected
  - Groups repeated complaints into problem clusters so users can see the underlying theme instead of isolated posts.
- **Open original context** *[on: Opportunity Detail]*
  - Trigger: User clicks a thread or quote
  - Shows the original Reddit post, surrounding comments, and source link for validation.
- **Save evidence quote** *[on: Opportunity Detail]*
  - Trigger: User clicks 'Save quote' on a thread or comment
  - Stores the original wording, author context, and source URL so evidence can be reused in notes and outreach.
- **Generate interview prompts** *[on: Validation Workflow]*
  - Trigger: User clicks 'Generate questions' on a problem cluster
  - Creates discovery interview prompts and follow-up questions based on the pain language in the thread cluster.
- **Send follow-up email** *[on: Outreach Center]*
  - Trigger: User approves a drafted outreach message
  - Sends an email follow-up to a prospect or interview candidate and logs the attempt.
- **Create reminder task** *[on: Outreach Center]*
  - Trigger: No response after a configured delay
  - Automatically creates a follow-up reminder so the founder does not lose promising threads or contacts.
- **Export to Google Sheets** *[on: Integrations]*
  - Trigger: User clicks export or enables sync
  - Pushes discovered leads, quotes, and status fields into a spreadsheet for downstream workflows.
- **Push Slack alert** *[on: Dashboard]*
  - Trigger: A new high-priority thread matches saved filters
  - Sends a contextual Slack notification when a new relevant pain signal appears.
- **Dismiss irrelevant signal** *[on: Lead Inbox]*
  - Trigger: User marks a thread as not relevant
  - Trains the ranking model to deprioritize similar false positives over time.

### UX details
- **Lead Inbox sorting:** Default sort should be hottest signal first, combining explicit pain language, recency, and buyer-intent wording rather than newest-first.
- **Search Builder:** Preload complaint phrase templates like 'I hate', 'why does', 'workaround', and 'frustrated' so users can start from problem language instead of keywords alone.
- **Opportunity Detail:** Show the original quote and source link prominently above the summary so validation always starts from evidence, not the model's paraphrase.
- **Validation Workflow:** Include an explicit go/no-go gate asking whether three paying users would commit before engineering starts.
- **Dashboard alerts:** Alerts should include the post quote plus enough surrounding context to judge relevance without opening Reddit immediately.
- **Lead Inbox training:** Provide one-click dismiss/irrelevant actions and use them to improve future ranking.
- **Outreach Center:** Auto-create follow-up tasks when a message is sent so every promising prospect gets a reminder path.
- **Onboarding:** Start users with a default monitored subreddit set and a sample pain cluster so they reach the first aha moment quickly.

## 6. Monetization
**Model:** (unspecified)

## 7. Competitors to beat
| Name | Why it fails | Price | Mentions |
|---|---|---|---|
| Notion | Used as a workaround or alternative, but not an ideal fit for the specific problem; also cited as an established competitor in docs space. | free/paid not specified | 22 |
| Pulse for Reddit | Used as a source of complaint discovery, implying it helps find where people are already saying 'no one sees my stuff' and buyer-intent posts; no failure noted in this chunk. | paid/unspecified | 15 |
| ChatGPT | Not a market solution itself, but used as a tool to force brutal market validation and reduce founder self-deception. | usage-based / not specified | 16 |
| Claude | Used as a general assistant to draft follow-up emails and summarize calls, but the workflow still depends on the user prompting and pasting transcripts. | paid/unspecified | 16 |
| WordPress | Seen as the default cheaper option that already satisfies many simple marketing-site needs, making custom hand-coded work hard to justify. | cheaper / 20-30x cheaper than custom per OP context | 14 |
| Apollo | Cold outreach via Apollo-generated lists had low response and required lots of time/cash; not enough on its own. | not mentioned | 12 |
| n8n | Mentioned as a workaround/automation layer rather than a full native product, implying people assemble workflows themselves. | 20 dollars a month or free hosting if you do community edition and host it yourself | 10 |
| GummySearch | Used as a Reddit discovery tool, but the commenter says manual scraping and another tool caught threads it missed, implying incomplete coverage. | $29/month or $60/month | 9 |

## 8. Distribution
- Top subreddits to launch in: r/smallbusiness, r/indiehackers, r/webdev, r/SideProject, r/startups, r/SaaS, r/Entrepreneur, r/ProductManagement, r/sales, r/marketing

## 9. Users & roles
**Primary persona:** SaaS founder validating an idea

**Roles:**
- **Founder** — Creates tracked subreddits/keywords, reviews ranked clusters, captures interview prompts, and exports outreach lists.

## 10. Data model & integrations
- (no data model extracted)

## 11. States
**Empty state:** User sees a setup screen prompting to create a query preset and run the first scan.
**Error state:** User sees a clear scan failure message and the last successful scan timestamp (no partial misleading clusters).

## 12. Analytics & metrics
- (not synthesized for this report)

## 13. Risks & open questions
- (no risks/questions extracted)

## 14. Post-launch
- See https://painfinder.app/reports/finding-real-user-pain-before-building-saas for DM-able hot leads (workarounds × buying intent).
- See https://painfinder.app/reports/finding-real-user-pain-before-building-saas for verified key quotes you can use as landing copy.

## 15. Suggested build order (3-week MVP cut)
- Week 1: §3 must-haves + §5 page 1.
- Week 2: §5 remaining pages + auth/persistence if needed.
- Week 3: §6 monetization wiring + analytics + launch checklist.

## 16. Setup hints (your stack overrides these)
- `pnpm create next-app . --typescript --tailwind --app`
- `npx shadcn@latest init`
- The agent SHOULD ask the user before committing to a stack.

## 17. How to use this file
You're an AI coding agent reading this in AGENTS.md. Your job:
1. Confirm the stack with the user (their preferences override this file).
2. Scaffold an MVP covering §3 + §5 page-1 first.
3. Defer §6 (monetization) and §14 (post-launch) until §3 ships and works.
4. Re-fetch the live PRD anytime via:
   curl https://painfinder.app/api/public/reports/finding-real-user-pain-before-building-saas/export.json?size=compact

## 18. Verbatim key quotes (top 10)
> "The best signal isn't random Reddit browsing. It's finding people IN the problem right now."  
> — Problem discovery, post #15330

> "look for patterns like people complaining about the same thing, workarounds they’ve built, or posts where they’re already paying for a solution but still unhappy."  
> — Problem discovery, post #15330

> "Validation is when they show real intent. Paying, committing time, or asking when it’s ready."  
> — User validation, post #15330

> "Reddit works but you're reading it wrong. Stop looking for complaints and start looking for workarounds:"  
> — Problem discovery, post #15332

> "look for recurring manual tasks that people are trying to automate with spreadsheets or scripts."  
> — Problem discovery, post #15332

> "I’d start by filtering subreddits like r/SaaS for phrases like 'how do I', 'extremely frustrated', or 'alternative to'."  
> — Problem discovery, post #15332

> "You're iterating on the wrong variable."  
> — Pain points & friction, post #15430

> "You skipped the step where you find that out."  
> — Customer interviews, post #15430

> "the shift happened when I stopped looking for people and started looking for publicly expressed frustration"  
> — Problem discovery, post #15430

> "The day I rewrote my landing page in the exact words my users used to describe their own problem everything changed."  
> — Pain points & friction, post #15616

## 19. Manual workarounds users cobble together (top 15)
1. **forum monitoring / pain-signal extraction** — *Manual extraction of high-intent signals from forums*
   > "we built something like this to automate this exact extraction process."
2. **business process automation** — *Spreadsheets or scripts used to replace repetitive tasks*
   > "recurring manual tasks that people are trying to automate with spreadsheets or scripts"
3. **problem discovery / validation** — *Idea generation from internal brainstorming instead of user research*
   > "I built 2 products from shower thoughts."
4. **data consolidation / reporting automation** — *Manual weekly export from multiple dashboards*
   > "someone in customer success kept bitching about having to manually export data from 3 different dashboards every week."
5. **distribution automation / directory submission** — *Manually assembling launch materials and submitting the product to multiple directories/review sites every day*
   > "I prepared some screenshots, taglines, descriptions, demo videos, and manually submitted the product to 5-10 places a day"
6. **content ops / template management** — *Manually maintaining a reusable content library for social posting*
   > "I keep a vault of hooks and templates (slideshow, UGC, and simple “wall of text” videos which is just text on an image)."
7. **pre-MVP validation** — *Selling the service and delivering it by hand before building software*
   > "The Manual 'Concierge' Service"
8. **ops automation** — *Operating a paid service manually with spreadsheets and automations*
   > "running the entire service on Google Sheets and a bunch of Zaps for his first ten paying clients"
9. **customer research CRM** — *Manual one-by-one outreach to all users for feedback*
   > "I emailed every single user personally."
10. **idea validation** — *Manual review of Reddit context for validation*
   > "You can browse the discovered pain points and ideas, see the original Reddit context for validation"
11. **outbound prospecting** — *Manually finding communities and reaching out one by one*
   > "Find out where your ICP is (eg. a specific subreddit, a discord community, a facebook group, etc) and start reaching out to people."
12. **research automation** — *Using a general-purpose AI research tool to do manual web research*
   > "I used to and still use Claude AI’s research tool"
13. **Reddit lead discovery / audience research** — *Manually searching Reddit posts and comments to identify prospects.*
   > "I had to scroll through tons of posts, read every comment, and try to figure out who might be a good fit."
14. **N/A** — *Not a software workaround; no software process described.*
   > "I spent two weeks writing my final paper for one of my courses."
15. **Academic evidence/documentation tool** — *Manual note-taking to preserve evidence of original work.*
   > "I took several pages of notes by hand."

## 20. "I would pay for…" quotes (top 10)
1. wants: better intent-first customer acquisition
   > "I’ve seen teams do the opposite (optimize channels, not intent) and then wonder why nothing compounds."
2. wants: A way to validate if enough users would commit before building
   > "Would 3 paying users commit today if I shipped this?"
3. wants: interactive LLM software or coach for idea selection
   > "I would love an interactive LLM software or coach that guided me through this process to pick the right idea."
4. wants: the free lead-finding/testing tool
   > "I need. I’m just about to go into soft lunch and one of my projects which is a Chrome extension and then also app which is already validated please DM me."
5. wants: tool that delivers ideas
   > "You can just sign up on [https://snoopsignal.com](https://snoopsignal.com) and get ideas delivered to you"
6. wants: opportunities of good companies
   > "I would like to invest so any opportunities of good companies pls share and dm me"
7. wants: advice on finding early customers
   > "Would be happy to hear advice from anyone on this"
8. wants: Reddit monitoring and lead capturing tools
   > "I want such tools that you explained"
9. wants: the audiobook mentioned as a system to run without you
   > "if anyone wants it just reply. It's genuinely useful for the stage you are describing."
10. wants: PortLume AI interview prep product
   > "I will take it for a spin when i have some downtime."

## 21. Hot leads summary
- 455 hot leads identified (users who BOTH built a workaround AND signaled buying intent)
- Tier breakdown: 26 hot / 72 warm / 357 cold
- DM-able usernames available at: https://painfinder.app/reports/finding-real-user-pain-before-building-saas#hot-leads (kept off this file for privacy — see live report)

## 22. Full competitor list (top 10)
| Name | Why it fails | Price | Mentions |
|---|---|---|---|
| Notion | Used as a workaround or alternative, but not an ideal fit for the specific problem; also cited as an established competitor in docs space. | free/paid not specified | 22 |
| Pulse for Reddit | Used as a source of complaint discovery, implying it helps find where people are already saying 'no one sees my stuff' and buyer-intent posts; no failure noted in this chunk. | paid/unspecified | 15 |
| ChatGPT | Not a market solution itself, but used as a tool to force brutal market validation and reduce founder self-deception. | usage-based / not specified | 16 |
| Claude | Used as a general assistant to draft follow-up emails and summarize calls, but the workflow still depends on the user prompting and pasting transcripts. | paid/unspecified | 16 |
| WordPress | Seen as the default cheaper option that already satisfies many simple marketing-site needs, making custom hand-coded work hard to justify. | cheaper / 20-30x cheaper than custom per OP context | 14 |
| Apollo | Cold outreach via Apollo-generated lists had low response and required lots of time/cash; not enough on its own. | not mentioned | 12 |
| n8n | Mentioned as a workaround/automation layer rather than a full native product, implying people assemble workflows themselves. | 20 dollars a month or free hosting if you do community edition and host it yourself | 10 |
| GummySearch | Used as a Reddit discovery tool, but the commenter says manual scraping and another tool caught threads it missed, implying incomplete coverage. | $29/month or $60/month | 9 |
| HubSpot | Used as an example of reconsolidation, but the post frames it as part of a trend toward fragmented tool sprawl and feature creep. | About $500/month for the whole team (upgrade trial mentioned) | 11 |
| LinkedIn | Works better than cold calling for some, but still needs content, intent signals, or video/voice to cut through saturation. | not mentioned | 10 |

## 23. Where this conversation lives (top subreddits)
- r/smallbusiness (94 posts)
- r/indiehackers (84 posts)
- r/webdev (83 posts)
- r/SideProject (83 posts)
- r/startups (80 posts)
- r/SaaS (80 posts)
- r/Entrepreneur (79 posts)
- r/ProductManagement (77 posts)
- r/sales (70 posts)
- r/marketing (49 posts)