← All founder workflows

How to find a micro-SaaS idea worth building (without waiting for inspiration)

Find a micro-SaaS idea by searching where paid problems are already documented rather than brainstorming: app-store and review-site one-star complaints, job postings describing manual work, community threads asking for a tool, and your own former job. Then filter every candidate on four criteria — reachable buyer, existing spend, narrow scope, and no incumbent giant. Most ideas fail the filter in minutes, which is the point: idea generation is a search problem with a high rejection rate, not a creative act.

7 days $0 to run6 stepsUpdated 2026

The workflow

0/6 done

  1. Review sites and app stores publish install counts, prices and one-star reviews. Every repeated complaint about a paid product is a documented problem with a buyer who has already proven they will pay. Collect thirty complaints across a category in an hour; the ones repeated by twenty different customers are candidates, and they arrive pre-worded by the market.

  2. A posting for someone to "manually reconcile daily reports from three systems" is a company describing a budgeted problem in detail. Salary tells you what the problem is worth — a $45k role doing one repetitive task means the company will consider a few thousand a year to remove it. Job boards are the least-mined idea source available and they are free.

  3. Subreddits, Discords and forums for a specific profession are full of people describing exactly the software they wish existed. Search that phrase plus the profession. Frequency is the filter: a request that appears once is one person, a request that appears monthly for two years is a market with nobody serving it.

    Competitor research
    Input
    "is there a tool that" + veterinary practice management, last 2 years
    What comes back
    23 recurring requests, 3 appearing more than five times: automated recall reminders that respect practice hours, splitting invoices across insurers, and syncing lab results into records. All three have paid incumbents in human healthcare and none targeted at small vet practices.

    What this step looks like when it is done properly — the free Idea Validator covers the same ground as part of its research.

  4. Domain knowledge is the most underrated advantage a bootstrapped founder has: you know the vocabulary, the workflow and the person who signs off. Ideas from your own former industry validate faster because you can reach buyers who already trust you. The reason founders skip this source is that the problems feel boring — boring is what people pay for.

  5. Reachable buyer, existing spend, narrow enough to build alone, no incumbent giant serving it well. Most candidates fail at least one in under five minutes, and that speed is the value of the filter. Aim to reject twenty ideas before you keep one, because the alternative is spending three months finding out what a five-minute check would have told you.

    Idea ValidatorFull tool
    Input
    Automated recall reminders for small veterinary practices that respect practice hours
    What comes back
    GO to a validation test. Reachable buyer (practice managers answer the phone), existing spend (practice-management suites cost $200–$600/mo), narrow scope, and incumbents are human-healthcare-first. Next step is ten practice-manager calls, not a build — confirm the reminder failure costs them appointments.

    Run it yourself — free, no signup:

    Who it's for, what it does, what they pay. The more specific the sentence, the sharper the read.

  6. Maintain a running document of candidates with the source and the date. Ideas that keep resurfacing from independent sources are the ones worth testing, and having a list removes the pressure to commit to the first exciting thing. The founders who ship good micro-SaaS are not the ones with better ideas — they are the ones who rejected more of them, faster.

Questions founders ask about this

Where do good micro-SaaS ideas come from?
From documented, already-paid-for problems: one-star reviews of existing tools, job postings describing manual work, repeated community requests, and your own former industry. Brainstorming produces ideas nobody has budgeted for.
How do I know if a micro-SaaS idea is too small?
Count the reachable buyers and multiply by your real annual price. A niche under roughly $5M of total market rarely supports a full-time income after a realistic 1–5% share — though it can still make an excellent side business.
Should I build in an industry I know nothing about?
It is harder, though not impossible. Domain knowledge shortens validation dramatically because you know the vocabulary and can reach buyers who trust you. Without it, budget considerably more time for customer conversations.
How many ideas should I reject before picking one?
Twenty is a reasonable working ratio. The four-part filter kills most candidates in minutes, and a high rejection rate is what stops you spending months on the first idea that felt exciting.
Is it bad if someone is already building my idea?
Usually not — it proves demand and gives you a real competitor to differentiate from. The dangerous case is a well-funded incumbent already serving your exact segment well, which the four-part filter is designed to catch.

Next, founders usually do this

The tools used above have their own pages — Idea Validator — and the SOP SOP: Validate a SaaS idea in 7 days runs the same ground in more depth. Also worth reading: the Nine Lives Doctrine, and real verdicts from ideas kitty has run this workflow on.

kitty.build runs this entire workflow for you

Every step above — the research, the competitor read, the numbers, the honest verdict — is what nine specialist AI boards do automatically when you feed her an idea. She will tell you to kill it if it deserves killing. First idea is free.

Feed her an idea — free

No card · Failed tasks are free · Your repo, your domain, your revenue