How to find a micro SaaS idea
The good ideas are not hiding. They are sitting in someone's spreadsheet, in a two-star review, and in the job ad for a role that exists only because software does not.
The short version
- Boring industries are underserved because founders build for people like themselves.
- A spreadsheet in production is an unbuilt product with a validated user already on it.
- The best ideas are features, not platforms. One workflow done properly beats a suite done thinly.
- Big tools leave gaps on purpose. What is too small for them is exactly your size.
- Pick a market you can reach. An idea you cannot find buyers for is not an idea.
What makes a good micro SaaS idea?
One painful workflow, for one identifiable group, that they currently handle with a spreadsheet, a contractor, or a tool that does it badly. Small enough to build alone in weeks, specific enough that the buyer recognises themselves in the first sentence of your landing page.
The word that does the work there is identifiable. "Small businesses" is not identifiable: you cannot find them, they have nothing in common, and they do not gather anywhere. "Independent physiotherapy clinics in the UK" is a group with directories, associations, forums and a shared vocabulary.
Where do micro SaaS ideas actually come from?
Four places: work you have done yourself, spreadsheets running real processes, features that large tools have declined to build, and industries nobody in tech finds interesting. In all four the problem already exists and is already being paid for, badly.
| Source | Why it works | Example shape |
|---|---|---|
| Your own past job | You know the vocabulary and the pain | The report you built manually every Friday |
| Spreadsheets in production | Validated workflow, terrible interface | Shift rotas, client trackers, stock counts |
| Feature requests refused | Demand with a named owner | "We have no plans to add this" threads |
| Unglamorous industries | Almost no competition | Plant hire, dentistry, freight, funerals |
The spreadsheet test: if a business runs something important on a spreadsheet that one person maintains and everyone fears breaking, you have found a product with its users already onboarded.
Should the idea be original?
No, and originality is usually a warning sign. If nobody has built anything adjacent, the most likely explanation is that nobody wants it. Being the specific option in a market that already exists is a far better position than being the only option in one that does not.
The differentiation that works at this size is not a new category. It is being obviously built for one group: their words, their workflow, their integrations, their pricing shape. A generic tool with a settings page cannot compete with a tool that arrives already configured for how you work.
How do you narrow a big idea into a small one?
Take the broad tool and cut everything except the single workflow that hurts most, then pick one industry to serve with it. "Project management" becomes "handover checklists for small construction firms". The cut is what makes it buildable alone and sellable at a real price.
A useful constraint: if you cannot describe the product in one sentence without the word "and", it is still too big. Every "and" is another month of build and another reason the buyer cannot tell what it is for.
How do you know an idea is too small?
When the arithmetic does not close. Multiply a realistic price by the number of buyers you could plausibly reach in a year. If that number is not worth the months it costs, the idea is too small, and that is a calculation to do before building, not after.
| Price / month | Customers for $2,000 MRR | Feasible alone? |
|---|---|---|
| $9 | 222 | No: support load alone breaks it |
| $29 | 69 | Hard, but possible in a defined niche |
| $79 | 26 | Yes |
| $149 | 14 | Yes, if the problem is expensive enough |
Notice that the fix for a too-small market is usually a higher price, not a bigger market. Serving fourteen businesses properly is a real job; chasing two hundred and twenty is a different company.
Frequently asked questions
Do I need domain expertise?
It helps enormously, and it is the most transferable advantage a solo founder has. If you have done a job, you know which parts of it are stupid.
Is B2B better than B2C for micro SaaS?
Usually. Businesses have budgets, tolerate higher prices, churn less and can be found through directories and associations. Consumers are cheaper to reach and far harder to charge.
What about AI wrapper products?
A thin wrapper around a model has no defensibility and gets copied in a weekend. A wrapper around a model plus a specific workflow, data and integrations for one industry is just software, and that is fine.
How many ideas should I consider?
Enough to have a shortlist, then commit. The failure at this stage is not choosing badly; it is never choosing, and spending a year comparing options that would all have worked.
Can I build for a market I cannot reach?
No, and this is the most common fatal flaw. Before you commit, name three specific places the buyers gather. If you cannot, the idea is unreachable no matter how good it is.
The system behind this, written down
Everything above is the map. The Income Loop is the work inside it: modules 0–6 from the problem you solve to the offer that pays for it, plus ten traffic paths: the deeper post banks, the content sales systems and the full software build sequence, in one place.
Get The Income LoopNot ready to pay for anything? The Basic Income Loop is free and includes a complete seven-day starter for Threads, Instagram or software, enough to find out which one suits you before spending anything.