A tool that syncs two accounting apps. An extension that cleans up data exports. A service that pings you when a price changes. These products have no funding and no team, and some of them out-earn their creator's old salary.
It is probably the model best suited to a Solopreneur, and the most misread: people take it for a failed SaaS when it is a distinct strategy with its own rules.
Definition
A micro-SaaS is subscription software addressing a single, precise problem for a deliberately narrow market, run by a team of one or two with no outside funding.
None of the three criteria is decorative:
- A single problem. Not a suite of tools, one function that works.
- A narrow market. Small enough that large players will not bother.
- A tiny team. Which forces radically different technical and commercial choices.
The economics
A funded SaaS chases a huge market because it has investors to repay. A micro-SaaS chases the exact opposite: a market narrow enough that nobody big will move in.
Take a product at €30 a month. Two hundred customers make €6,000 in MRR (monthly recurring revenue), or €72,000 a year. To a venture fund that is a rounding error. To one person it is a comfortable income arriving every month. The same figure means completely different things depending on the cost structure behind it.
That is the model's main protection: your market is too small to justify a well-funded competitor attacking it. The niche is not a constraint you endure, it is the moat.
What separates the two
| Conventional SaaS | Micro-SaaS | |
|---|---|---|
| Target market | As broad as possible | Deliberate Niche market |
| Funding | Often external | Bootstrapping |
| Goal | Fast growth | Fast profitability |
| Product scope | Expanding | Deliberately frozen |
| Support | Dedicated team | The founder |
The last row matters most. Support is what actually caps a micro-SaaS: a product with two thousand customers and a confusing interface becomes unliveable long before it becomes rich.
Finding an idea that holds
Micro-SaaS ideas that work rarely come from brainstorming. They come from three places:
Your own trade
A task you have done by hand every week for two years is a validated idea. You know the problem, the vocabulary, and where the other people who have it hang out.
Gaps in a big tool
Large platforms deliberately leave holes, because covering a marginal use case is not worth their time. Those holes are the raw material of micro-SaaS.
Repeated complaints
Professional forums and trade groups contain requests phrased word for word. A complaint that recurs ten times in the same terms is a Value proposition the market already wrote for you.
Frequently asked questions
How many customers does it take to live on?
The arithmetic is direct: divide your target monthly income by your subscription price, then add a margin for Churn rate and fees. At €30 a month and a €3,000 target, that is a hundred paying customers, sustained over time.
Can a micro-SaaS become a big SaaS?
Sometimes, but aiming for that from day one throws away the advantage. The choices that make a micro-SaaS viable, narrow scope and tiny costs, are exactly the ones you would have to undo to grow. Better to commit to the format and decide later.
How do you protect against copycats?
Not through technology, which gets copied in weeks. Protection comes from the customer relationship, domain knowledge and presence wherever your market gathers. In a market of a hundred people, being the one they know is worth more than any feature.
Should I talk about it before building it?
Yes, as early as possible. An MVP (minimum viable product) shown to thirty people in the trade teaches you more in a week than six months of silent development. Our Claude Code course starts from exactly that format: a narrow scope, built fast, shipped before it is perfect.