Use case
Validate a SaaS Idea Before You Build
Validate a SaaS idea by researching whether the workflow problem it solves already shows up as a recurring complaint, interviewing people who currently do that workflow manually or with a worse tool, and confirming they’d switch before building the software.
The challenge with SaaS ideas specifically
SaaS ideas are especially easy to overbuild before validating because the workflow being automated usually already exists in a clunky form, such as a spreadsheet, email, or a tool used for something it wasn’t designed for. That makes it tempting to assume the problem is obvious. It may be real, but how painful it is and for whom usually become clear only after research.
Validation process for a SaaS idea
- 1
Define the specific workflow problem
Name the exact task people currently do badly, rather than the category of software you want to build.
- 2
Research current discussion
Look for complaints about the current tools/spreadsheets/manual process people use for this workflow today.
- 3
Identify pain points and existing workarounds
Find out what specifically breaks down, and what people currently tolerate instead.
- 4
Test the switching question
Ask people what it would take for them to abandon their current approach. Don’t ask only whether your described solution sounds good.
- 5
Evaluate the evidence
Decide if the pattern is strong enough to scope a focused MVP, or if the problem needs to be narrowed further.
How FirstSight helps
Map each step above directly onto FirstSight: describe the workflow problem, and it searches public discussion for people already struggling with it, surfaces the pain points and workarounds it finds with an evidence-strength read, and generates the specific questions to validate the switching behavior in your own interviews.
Example output
For "an app that helps small teams track project costs without a spreadsheet," FirstSight might surface recurring complaints about spreadsheet version conflicts and manual reconciliation errors, rate the pain-point clarity high, and recommend interviewing people who’ve recently abandoned a cost-tracking spreadsheet.
Ready to move from guessing to evidence?