What is micro-SaaS? Definition, examples, and how a small product gets found

Micro-SaaS is a software subscription business small enough for one person, or a very small team, to build, run and support, usually aimed at a narrow niche and a specific job. No funding, no sales team, no plan to become a platform. The goal is a product that earns a good living for its maker, not a company that needs to grow to survive.

What makes a SaaS "micro"

• One or two people. The founder builds it, supports it and markets it. Contractors for design or a launch, at most. Headcount is the clearest line between micro-SaaS and a startup.
• A narrow problem. Not "project management" but "invoicing for freelance translators". Not "analytics" but "privacy-friendly analytics for indie sites". The niche is what makes the product buildable and findable by a small team.
• Bootstrapped and profitable early. No outside capital, so the product has to cover its costs within months. Monthly recurring revenue is the only number that matters.
• Often built on a platform. A Shopify app, a Slack integration, a Chrome extension, a Notion template with a backend. The platform brings the audience; the micro-SaaS fills a gap in it.
• Deliberately small. A few thousand to a few tens of thousands of dollars a month is success. Many makers run two or three side by side rather than growing one.

It is not a hobby project and it is not a startup. A hobby project has no paying customers; a startup has investors and a growth plan. Micro-SaaS is the space in between, and the reason it exists at all is that building software got cheap enough for one person to do the whole thing.

Micro-SaaS examples

The products people point to when they explain the model share the traits above: a narrow job, a tiny team, and years of quiet profitability.

• Carrd, a one-page site builder run by a solo founder. One clear job (a simple page, fast), a free tier that does the marketing, and a paid tier for custom domains and forms.
• Bannerbear, an API for generating images and videos from templates, built and run by a founder with a very small team. A developer-facing niche, found through content and integrations rather than ads.
• Nomad List and Remote OK, a pair of community and job-board products run by one person, famous for shipping in public and for a stack simple enough for one maker to maintain.
• Plausible Analytics, privacy-first web analytics from a two-person start. It grew past micro-SaaS size by staying focused on one job and one audience, and it is the clearest example of "alternative to X" positioning working: the product is sold as the simple, privacy-friendly alternative to Google Analytics.
• Simple Analytics, the same niche from a solo founder, which shows the pattern repeating: one narrow promise, a public roadmap, and a listing everywhere someone searches for an alternative.

Notice what is missing: none of them needed a launch to become known. They were found, over years, on the pages people already search: comparison sites, "alternative to" queries, the platform's own marketplace, and a handful of communities.

Where micro-SaaS ideas come from

Lists of "50 micro-SaaS ideas" are mostly other people's leftovers. The ideas that work come from proximity to a problem:

• A job you have done by hand. The spreadsheet you rebuilt at three employers, the script you keep rewriting, the report a client asks for every month. If you have done it manually, others are doing it manually too.
• A gap in a platform you already use. Search the Shopify, Slack, Notion or Chrome Web Store marketplaces for the thing you wanted and did not find. Platforms are the largest source of narrow, paying niches.
• A big tool's most-hated feature. Read the reviews of a market leader on G2, Capterra or AlternativeTo. Every "I only use it for X" and "I wish it just did Y" is a micro-SaaS.
• A community's recurring question. The subreddit or Discord where the same "how do I..." comes up weekly is telling you what to build and where to announce it.

Validate by asking for money early: a landing page, a waitlist, a pre-order for the first ten customers. Ten people paying beats a thousand saying they would.

How a micro-SaaS gets found

This is the part most makers underinvest in, because the product was the fun part. With no budget and no audience, distribution comes from being present wherever someone is already searching for what you do:

1. The "alternative to" pages. Complete listings on AlternativeTo and SaaSHub, with the alternatives field filled in carefully. A micro-SaaS is nearly always the small, simple or cheaper alternative to something big, and that is exactly the query these sites rank for.
2. The startup directories. The well-rated list is an afternoon's work once you have a launch package: permanent listings, the first backlinks, and a steady trickle of visitors. Free queues first, launch boards second, as laid out in how to submit your startup to directories.
3. The platform marketplace. If the product is a Shopify app, a Slack integration or an extension, the marketplace listing outranks every directory. Do it first and do it properly.
4. One launch, not a campaign. Product Hunt and, if the product is technical, Show HN. A day of attention and a permanent page. The SaaS launch checklist is enough preparation.
5. Search content for the niche. A handful of pages answering the exact questions your customers ask, written once. In a narrow niche, a few good pages rank.
6. The first hundred users, by hand. Email every signup. The plan is in how to get your first 100 users.

Two things change once you run more than one micro-SaaS. Listings drift: pricing changes on the site and thirty directories still show the old number. And the second product rarely gets listed as widely as the first, because the form-filling was tedious the first time. Both are solved the same way: keep one package per product as the source of truth and resubmit from it. That is what Launch to Win for micro-SaaS founders is built around, and the multiple products playbook goes through the routine.

The economics, briefly

Costs are hosting, a payment processor, a few tools and the maker's time. Pricing is usually a low monthly fee, a higher annual one and, increasingly, a lifetime deal for early customers. Churn is the enemy: a narrow product that solves a recurring job keeps customers; one that solves a one-off job has to keep finding new ones. Most makers who publish their numbers describe the first year as reaching a few hundred dollars a month, then the slow compounding of listings, content and word of mouth doing the rest.