Automated validation tool that finds real complaints & paid-but-broken tools for indie SaaS

Everyone says "validate your SaaS idea" and then hands you a list of generic survey questions. That’s not validation. That’s a vibes poll. Real validation for indie SaaS is: - finding real complaints people have already written - checking if they pay for broken tools anyway - confirming the pain is frequent, not once-a-year - proving they have a budget without you convincing them You don’t need 1,000 responses; you need 20 people who are already bleeding cash and patience on bad software. I built SaaSScout to automate that detective work so I can focus on building instead of tabbing through 15 sites. If that sounds useful, play with it here → https://t.co/vFUx1dGyAP

How to validate a SaaS idea in 48 hours without asking a single "would you pay for this?" question. Step 1 – Start from pain, not features. Pick a job-to-be-done ("schedule client calls", "hand off copy to designers", "monitor churn"), not a cool technology. Write down the *moment of frustration* your user feels. Step 2 – Map the current behavior. What are people using today? Spreadsheets, Notion, email, a hated incumbent SaaS? Search for "<tool> alternative", "<tool> vs", and "is <tool> worth it". You’re not looking for praise; you’re hunting for patterns of dissatisfaction. Step 3 – Go to the complaint reservoirs. Reddit, G2, Capterra, GitHub issues, support forums. Screenshot 20–30 specific complaints. Tag each by: trigger (what happened), user type, and consequence (lost time, lost money, lost trust). Step 4 – Quantify the signal. If you see the *same* complaint across 3+ channels and 3+ user personas, that’s not noise. That’s a wedge. Estimate how often that moment happens per user per month and how expensive it is in time or cash. Step 5 – Design a narrow fix, not a grand platform. Your v1 should surgically remove one recurring pain, in one workflow, for one clear segment. If your idea requires your user to change 5 other tools just to adopt you, it’s not an MVP, it’s a migration. Step 6 – Pitch back the frustration. When you finally talk to users, don’t lead with features. Lead with the exact sentence they could’ve written in those 1-star reviews. If they lean in and say "that’s exactly my problem", you’re on the right track.