Good SaaS ideas rarely arrive as lightning bolts. They are usually hiding in ordinary work: a recurring spreadsheet, a weekly reconciliation, a handoff everyone hates, or a risk managed through reminders and luck. The opportunity appears when the same pain repeats for a specific kind of customer.
Look for work people have normalized
People do not always describe a painful process as a problem. They may call it the way things are done. Watch for teams copying data between systems, creating elaborate spreadsheets, chasing approvals in chat, rebuilding the same report, or paying specialists to organize information that already exists elsewhere.
The best clues combine frequency and consequence. A minor annoyance repeated every day can become expensive. A rare process can also matter when failure creates legal, financial, operational, or reputational risk.
Search where customers describe the work in their own words
Customer language is more valuable than founder language. Reviews, forums, professional communities, support threads, job posts, implementation guides, comparison pages, and public discussions reveal what people try, what they dislike, and what outcome they actually want.
Record the exact job, customer, trigger, workaround, consequence, and desired outcome. Do not collect complaints as entertainment. Cluster them until you can see one repeated workflow that a focused product could improve.
- Repeated complaints about the same step or limitation.
- Workarounds involving spreadsheets, email, copy-and-paste, or extra staff.
- Requests for integrations, automation, reporting, or simpler setup.
- Buyers combining several products to complete one job.
Use your founder strengths as a search filter
Looking inward does not prove demand. It helps decide where to look. Your previous roles, industry knowledge, trusted relationships, technical abilities, and access to communities can make certain markets easier to understand and reach.
A founder who knows the buyer's language can recognize subtle pain, reject unrealistic solutions, and recruit early users faster. This is founder–market fit in practical terms. Outside evidence still has to support the opportunity, but your strengths make the research more efficient and the first sale more believable.
Turn a pain cluster into a focused product hypothesis
A useful hypothesis names one customer, one painful workflow, one outcome, and one reason current alternatives fall short. For example: a product for small compliance teams that automatically assembles recurring audit evidence because their existing tools store activity but do not produce a review-ready proof package.
That statement is narrow enough to research. You can identify buyers, inspect alternatives, estimate value, find communities, and define a small workflow. 'A smart platform for businesses' gives you none of those advantages.
Rank ideas by proof, not novelty
Novelty can be exciting, but repeated pain, existing spending, reachable buyers, a clear competitive opening, and a feasible first product are stronger signals. A familiar problem with a sharp wedge is often more promising than an original concept that requires teaching customers why they should care.
The output of idea research should be a short list of opportunities with evidence and tradeoffs—not an endless brainstorm. The purpose is to make a decision you can defend and test.