Case Study: Idea Validation Engine
Stop building things nobody wants (your agent will tell you)
The #1 reason startups fail? Building something nobody wants. This agent makes sure you never do that — by running continuous market research across every platform where your customers complain.
The Validation Pipeline
This isn't a one-time prompt. It's a continuous system that runs weekly, scanning the internet for problems worth solving. Here's the complete architecture:
Scans Reddit, Twitter, Indie Hackers, Product Hunt, and niche forums for people complaining about the same things. Searches for phrases like 'I wish there was...', 'why is there no...', 'I hate how...'
Groups complaints into themes. Ranks by frequency (how many people), intensity (how angry), and recency (is this growing?). Filters out one-off rants from systemic pain.
For each validated pain point, proposes 2-3 product ideas with rough scope: MVP feature list, estimated build time, target price point.
Finds every existing solution, their pricing, App Store/G2 ratings, and what the 1-star reviews say. The 1-star reviews are GOLD — they tell you exactly what's missing.
Estimates TAM using search volume, subreddit size, competitor revenue (where available). A $10K/mo opportunity feels different than a $100K/mo one.
Ranks ideas by: pain intensity × market size × competitive gap × your ability to build it. Outputs a 1-10 score with reasoning.
Where to Mine for Pain Points (By Platform)
Different platforms reveal different types of pain. Your agent should scan all of them:
People are brutally honest on Reddit. They vent. They ask for help. They describe problems in detail.
- • Search: r/SaaS, r/startups, r/Entrepreneur, r/smallbusiness + niche subreddits
- • Keywords: "frustrated with", "anyone know a tool for", "I've been looking for", "why doesn't X exist"
- • Sort by: Top (month) to find recurring complaints, not one-off rants
- • Gold signal: Posts with 50+ upvotes asking for a solution = validated demand
Twitter shows you what people are frustrated about right now. Great for catching emerging problems.
- • Search: "[tool name] sucks", "[category] is broken", "wish there was a better"
- • Monitor: Replies to competitor products — their customers' complaints = your opportunity
- • Track: People quote-tweeting competitor announcements with criticism
These communities talk about what they're building and what they need. Great for B2B ideas.
- • Search: "Looking for", "Does anyone know", "I'd pay for"
- • Signal: Multiple people asking for the same thing in different threads
- • Product Hunt: Sort by "newest" and read comments — people suggest missing features constantly
Competitor reviews tell you exactly what's wrong with existing solutions. 1-3 star reviews are your feature roadmap.
- • Focus on: 2-star reviews (specific enough to be actionable, not just "it sucks")
- • Pattern: "I love X but hate Y" = Y is your niche
- • Pricing complaints: "Too expensive for what it does" = room for a cheaper alternative
The Weekly Validation Cron
openclaw cron add \ --name "Idea Validation Scan" \ --cron "0 10 * * 1" \ --tz "America/Chicago" \ --session isolated \ --message "Weekly idea validation scan. CRITICAL: Full detailed output. Do NOT summarize. 1. Search Reddit (r/SaaS, r/startups, r/Entrepreneur) for posts with 20+ upvotes containing: 'I wish', 'frustrated', 'looking for', 'anyone know' 2. Search Twitter for '[niche] sucks', '[niche] is broken', 'wish there was' 3. Check Product Hunt 'newest' for gaps in comments. For each pain point found (minimum 5): ## Pain Point: [Name] - 😤 Quote: '[Exact user quote]' - 📍 Source: [Platform + link] - 🔥 Frequency: [How many people mentioned this] - 💡 Product Idea: [What would solve this] - 🏢 Existing Solutions: [Competitors + pricing] - 📉 Their Weakness: [What reviews complain about] - ⭐ Opportunity Score: [1-10] — [reasoning] - 🛠️ MVP Scope: [Core features, est. build time] - 💰 Revenue Potential: [Pricing × estimated market] Rank all pain points by opportunity score. Save to knowledge/projects/idea-pipeline.md" \ --model "opus" --announce --channel discord
The Quick Validation Prompt (On-Demand)
Have a specific idea? Run this validation immediately:
Validate this idea: "[Your Idea Here]" 1. Search Reddit for related complaints (3+ subreddits) 2. Search Twitter for people wanting this 3. Find 3-5 competitors and their pricing 4. Read their 1-star reviews on G2/App Store 5. Estimate market size (search volume + community size) Output: ## Validation Report: [Idea Name] ### 😤 Top 3 Pain Points (with real quotes) 1. "[Quote]" — u/user on r/subreddit (142 upvotes) 2. "[Quote]" — @user on Twitter (89 likes) 3. "[Quote]" — G2 review of [Competitor] ### 🏢 Competitive Landscape | Competitor | Price | Rating | Weakness | ### 💡 The Gap [What existing solutions miss that you could nail] ### ⭐ Opportunity Score: X/10 - Pain intensity: X/10 - Market size: X/10 - Competitive gap: X/10 - Build feasibility: X/10 ### ✅ Go / ❌ No-Go Recommendation [Clear recommendation with reasoning]
Real Output: How This Playbook Was Validated
Validation Report: AI Agent Playbook / Digital Product
😤 Pain Points Found:
- • "I set up Claude with MCP tools but it forgets everything the next day. Am I doing something wrong?" — r/ClaudeAI (234 upvotes)
- • "Spent 3 hours configuring my AI agent. Next session it asked me my name again." — @indie_dev on Twitter (156 likes)
- • "Is there a complete guide to building persistent AI agents? Every tutorial covers basics but not the memory architecture." — r/LocalLLaMA (89 upvotes)
💡 The Gap: Hundreds of "getting started with AI agents" tutorials exist, but zero comprehensive playbooks covering memory architecture, automation, security, and real case studies in one package.
⭐ Opportunity Score: 8/10 — High pain, growing market, no direct competitor, low build cost (it's a digital product, not SaaS).
✅ GO — Validated. Build it.
From Validation to Launch: The Pipeline
Run the scanner. Find 5+ people expressing the same pain. Score 7+ = proceed.
Build landing page. Post in the communities where you found the pain. See if anyone puts money down before you build. Agent handles the landing page, you handle the marketing voice.
Minimum viable product. Not perfect — viable. Agent builds 80%, you handle the 20% that requires taste and judgment.
Launch in those same communities. Agent monitors feedback, you prioritize features. Rinse and repeat.
The Validation Pipeline
Here's the full flow from "random internet signal" to "validated idea worth building":
Reading the Validation Signals
Not all pain is created equal. Your agent should weight these signals differently:
"I'd pay $X for this" / "shut up and take my money" / people building hacky workarounds / recurring complaints over months (not just one viral rant)
"Someone should build X" / feature requests on competitor products / "is there a tool that does X?" questions / moderate engagement on complaint posts
"It'd be cool if..." / one-off rants with no engagement / ideas that require massive scale to work / solutions that need behavior change from users
Share this chapter
Chapter navigation
13 of 36