How to Find a SaaS Worth Building for Solo Founders
Solo founders face a specific idea discovery problem. You do not have a co-founder to challenge your assumptions. You do not have a VC network surfacing warm deal flow. You do not have a team of domain experts running competitive analyses. You have yourself, your experience, and your time.
That constraint is also your edge. You can move faster than a team. You can decide immediately. You can build the thing that actually solves your own problem without committee approval. But only if you find the right problem first.
This guide is specifically for solo founders — the mechanics of idea discovery that work when you are one person trying to find a SaaS worth dedicating one to three years of your life to building.
Why Most Solo Founders Look in the Wrong Places
The default idea discovery playbook — browse Product Hunt, read startup Twitter, look for "ideas lists" — produces ideas that are either already built by well-funded teams or too abstract to validate without significant research investment.
These sources optimize for novelty and surface-level appeal. They do not optimize for the specific constraint that defines solo founder success: you need an idea where your personal insight gives you an unfair advantage over teams with more resources.
That insight comes from one of two places: your direct experience with a problem, or your direct access to a community of people with that problem. Ideas sourced from anywhere else require you to build that insight from scratch — an expensive, slow process when you are doing it alone.
The Solo Founder's Unfair Advantage
As a solo founder, your sustainable advantages are:
- Speed — you can decide and ship in days, not weeks
- Personal domain knowledge — deep expertise in a problem space you have lived
- Community trust — relationships in a specific community that would take a team months to build
- Low overhead — you can profitably serve a market that would be too small for a VC-backed company
Idea discovery should start by asking: which of these advantages applies to which problem? Not: which problem is the largest market?
The Four Sources of Solo SaaS Ideas
🔧 Source 1: Your Own Workflow Frustrations
The most reliable solo founder idea source is a problem you personally experience repeatedly — one that costs you time, money, or significant annoyance, and for which no good solution exists.
The advantage here is immediate: you understand the problem deeply, you know what the ideal solution looks like, and you can validate demand by asking people in your situation if they share the same frustration.
How to mine this source: Track every moment in the next two weeks where you think "there should be a tool for this" or "why is this so unnecessarily hard?" Keep a running list. At the end of two weeks, review which items appear repeatedly or cause the most friction.
💼 Source 2: Your Former Industry or Employer
Most solo founders leave behind a deep well of domain knowledge from their career. The workflows, tools, and manual processes in your former industry that you know are broken — that knowledge is a genuine competitive asset.
Industries with high concentrations of good SaaS opportunities: industries that are large but unsexy (logistics, legal, construction, healthcare administration, insurance), industries where existing tools are old and beloved by users but terrible by modern standards, and industries where the buying process requires speaking to humans because the alternatives are too bad to sell self-serve.
How to mine this source: List every tool you used in your last job that you wished was better. List every process that was still done in spreadsheets that should have been software. These are potential SaaS opportunities where you have insider knowledge competitors do not.
🗣️ Source 3: Community Pain Points
If you are deeply embedded in an online or offline community — a professional group, a niche hobbyist community, a local business network — you have access to real pain points that outsiders cannot easily see.
Community-sourced ideas have a built-in early adopter network: the community itself. This is one of the most powerful positions for a solo founder because you can validate, build, and distribute within the same group.
How to mine this source: Spend 30 minutes reading the last month of posts in 2-3 communities you already belong to. Filter for complaints, recurring questions about tools or processes, and workarounds people have built themselves. The workarounds especially are gold — they prove someone cared enough to build a solution, which means the problem is real.
📊 Source 4: Existing Product Gaps
Look at products in markets you understand that have strong user bases but consistently poor reviews in specific areas. This is not about copying a product — it is about finding the specific problem an existing product fails to solve, and solving only that problem much better.
How to mine this source: Go to G2, Capterra, or Trustpilot and read 50 negative reviews for the market leader in a space you know. Filter for complaints that appear in more than 10% of reviews and that existing tools have not fixed despite years of feedback. Each recurring complaint is a potential SaaS opportunity.
The Three Filters for Solo-Scale Viability
Once you have a list of candidate ideas, run each through these three filters before investing any build time. This filter process should take less than a day per idea.
Filter 1: Can You Reach the Customer?
You do not have a sales team or a marketing budget. Every customer you acquire in the first year will come from communities you already belong to, people who already trust you, or search traffic you build over time.
Ask: Do I know where these customers spend time online? Can I get in front of 50 of them in the next 30 days without spending money? If the answer is no, the distribution problem may be harder than the product problem — and that is a dangerous combination for a solo founder.
Filter 2: Is the Problem Recurring and Painful Enough to Pay?
Solo SaaS viability requires recurring revenue. That means recurring pain. A problem that someone experiences once a year is much harder to monetize than a problem they feel every week or every day.
Ask: How often does this problem occur? What is the cost of not solving it — in time, money, or stress? Would someone pay $X per month to make this problem go away? What is a realistic monthly price, and how many paying customers do you need to reach your income target?
Filter 3: Can You Build the Minimum Version Alone?
The minimum version of your product needs to be buildable by one person in a reasonable timeframe — typically 4-12 weeks for the first paying version. Ideas that require machine learning infrastructure, large data sets, complex integrations, or hardware are generally not solo-founder-viable without specific technical expertise.
Ask: What is the absolute smallest version of this product that delivers the core value? Can I build that version alone in the next 90 days? If not, what would need to be removed or simplified to make that true?
Your 2-Hour Weekly Idea Discovery System
If you do not have a clear idea yet, run this weekly system for 4-6 weeks. It compounds — each week builds context that makes the next week's observations sharper.
30 minutes: Community observation
Read 2-3 communities in spaces you know. Record any complaint, workaround, or "why doesn't a tool exist for this" moment you see. Do not evaluate — just record.
30 minutes: Competitor review mining
Pick one product in a category you understand. Read 20 negative reviews on G2 or Capterra. Extract the recurring complaints. Add them to your running list.
30 minutes: Personal friction audit
Review your own workflows from the past week. What took longer than it should? What required manual work that felt like it should be automated? What did you do in a spreadsheet that you wished was a proper tool?
30 minutes: Idea filtering
Take your running list. Eliminate any idea that fails the three filters immediately. For the survivors, write one sentence describing the customer, the problem, and the recurring cost of that problem. The clearer that sentence, the more viable the idea.
After 4-6 weeks of this system, you will have a short list of ideas that are grounded in real problems, accessible markets, and your genuine domain knowledge. That is the starting point for real validation — and real building.