How to find a SaaS idea worth building

Finding a SaaS idea is a search problem, not a creative one. Spend a week reading places where paid problems are already documented — one-star reviews of tools people buy, job postings describing manual work, and community threads asking for software that does not exist — then generate candidates against your own domain advantage and reject them fast on four criteria: a reachable buyer, existing spend, a scope you can build alone, and no incumbent serving that segment well. Expect to reject twenty ideas to keep one. The rejection rate is the procedure working, not failing.

01

Write down the advantage you are searching from

Before you look at a single idea, write two sentences: what you know that most people do not, and who you can reach this week without an introduction.

This is not a warm-up. It is the filter that makes the rest of the week productive. An idea that hangs off eight years in dental practice admin is testable on Monday, because you already have the phone numbers and the vocabulary. The identical idea handed to an outsider is a three-month research project before the first useful conversation.

If you genuinely have no domain advantage, your first move is not idea generation — it is picking a reachable audience and spending two weeks inside their forums until you have one. Founders skip this and then wonder why every idea feels equally plausible: without an advantage, they are.

02

Mine the four places paid problems are already written down

Give this two days. You are collecting complaints, not ideas.

  • One- and two-star reviews of tools in adjacent categories. Filter to the low ratings and read thirty. Complaints that repeat across twenty different customers are validated demand with a receipt attached.
  • Job postings that describe manual work — "manually reconcile daily reports from three systems". The salary tells you what the problem is worth to that company.
  • Community threads that start "is there a tool that". Search that phrase plus a profession. Frequency is the filter: a request appearing monthly for two years is a market nobody serves.
  • Your own last job. The workflows that annoyed you are the ones you can describe precisely, and precision is what makes a cold email get answered.

Write each complaint down verbatim. Those sentences become your landing page copy later — phrased by the buyer, which is better than anything you would compose.

03

Generate candidates against your advantage, not in a vacuum

Now turn the raw complaints into shaped candidates. The generator below takes what you wrote in step one and returns four ideas that each name a buyer, an existing workaround, where to verify the demand, the specific catch, and a test that costs under $100.

Run it more than once with different framings of your advantage — "I know practice managers" produces a different list from "I know how practice management software fails". Two or three runs across an afternoon gives you a candidate pool of eight to twelve.

Do not evaluate while generating. Collect first, judge in the next step. Judging as you go is how founders end up with four variations of the idea they already secretly wanted to build.

SaaS Idea Generator — free, right here

About this tool

An industry you worked in, a tool you know inside out, a group you have access to. Vague in, vague out.

How will it get built?
04

Reject on four criteria, in under five minutes each

Every candidate faces the same four questions, and most die on the first or second:

  1. Is the buyer reachable? Could you get fifty of them on a list this week without an introduction? Agency owners, practice managers and warehouse supervisors answer messages. Hospital procurement does not.
  2. Do they already spend money here? Existing spend means a budget line you compete for. No spend means you must create one, which is the hardest sale in business.
  3. Can one person build the first version? If the first useful version needs a team, it is not a bootstrapped SaaS idea.
  4. Is there an incumbent serving this exact segment well? Competitors are good news; a dominant, well-reviewed incumbent in your precise segment is not.

Aim to reject twenty candidates to keep one. Speed here is the whole value — five minutes of honest filtering saves three months of hopeful building.

05

Pressure-test the survivor with five conversations

One candidate now gets a week of real contact. Find five people who match the buyer description and ask about their process — never about your idea.

Three questions carry it: how do you handle this today, what happened the last time it went wrong, and what have you already tried to fix it? The third is the most valuable. Someone who has already bought and abandoned two tools has a budget-bearing problem and a list of reasons those tools failed.

You are listening for one thing: do they describe your problem in their own words, unprompted? Five of five is rare. Three of five is a real signal. One of five means you found something that interests you more than it bothers them.

06

Commit to a test, not to a build

End the week with one idea and one dated test — not a repository.

The test should cost under $100 and produce a yes or no inside seven days: a priced landing page with a deposit button, forty personalised outreach messages, or doing the job manually for one paying customer. Write the pass mark before you run it ("five deposits or I stop"), because a threshold set afterwards is not a threshold.

Then put the idea through a verdict tool for a second opinion before you spend the week. Triage is cheap; a quarter is not. If the test fails, you still have eleven candidates in the pool and one week gone instead of one quarter.

What automates this

kitty.build runs the researched version of this: nine specialist boards take a candidate idea, search the live web for who already sells it and what their customers complain about, and return a cited GO / PIVOT / NO-GO before you write a line of code.

Feed her an idea

Questions

How long should it take to find a SaaS idea?
About a week of deliberate search, not months of waiting for inspiration. Two days mining documented complaints, an afternoon generating candidates against your own advantage, and the rest filtering and talking to five potential buyers.
How many ideas should I reject before committing?
Roughly twenty. The four-criteria filter kills most candidates in under five minutes each, and a high rejection rate is exactly what stops you spending a quarter on the first idea that felt exciting.
What if I have no industry experience to search from?
Then your first job is acquiring a reachable audience rather than an idea. Spend two weeks inside the forums, communities and review sites of one profession until you can describe their workflow in their words. Without that, every idea looks equally plausible because you cannot tell them apart.
Is an idea with existing competitors still worth building?
Usually yes — competitors prove budget exists. The dangerous case is a well-funded incumbent already serving your exact segment well. Look for a segment their pricing floor or onboarding requirements structurally exclude.
Should I build an MVP to test the idea?
Not first. An MVP costs weeks and answers 'can I build it', which is rarely the risky question. A priced landing page and five buyer conversations answer 'will a specific person pay' in days.

Next procedures