Testing a SaaS idea with 500 survey responses before building
The plan is to identify real customer problems before choosing or building a SaaS product. A two-minute survey asks which repeated tasks consume the most time, which cause frustration, which paid tools remain unsatisfying, and which problems people would pay to solve.
The target is 500 high-quality responses from founders, professionals, , , and operators. The product decision would come only after recurring problems and patterns appear across those answers, rather than from feature brainstorming or trend chasing.
An anonymous summary of the findings would be shared after enough responses are collected. It remains uncertain whether a survey alone can , so feedback is also being sought on stronger ways to find a problem worth solving.
Key points
- Look for a real customer problem before writing the product.
- Ask about repeated tasks, frustrating , and disliked paid tools.
- Measure whether people would actually pay to solve the problem.
- Collect 500 high-quality responses before deciding what to build.
- Search for recurring instead of isolated product ideas.