Skip to content
Micro-SaaS

Part 1 · Is this real? · Lesson 1 of 13

What this actually is

One small piece of software, one narrow problem, one kind of buyer, billed every month. What that shape gives you and what it takes.

6 min read

A micro-SaaS is one small piece of software that does one narrow job for one specific kind of person, and charges them every month to keep doing it. That is the whole definition. No investors, no team, no office, no plan to be big.

The word doing the work is micro. You are not building a rival to a giant product. You are taking one job that a giant product does badly, or does not do at all, for a group small enough that nobody large has bothered.

What the monthly part means

Software as a service means your customer never owns a copy. They rent access, and the rent renews on its own until they stop it. That has two consequences and you should hold both in your head at the same time.

The good one: a sale you made in March can still bill in September without you doing anything in between. A charge can succeed at three in the morning while you are asleep. That is a property of the billing model, not a prediction about your product.

The other one: the moment someone pays, you have promised that it keeps working. When it breaks on a Sunday night, that is now your Sunday night. Renting means they can also stop renting, any month, for any reason, and you will find out from a webhook.

Why this is on the list at all

  • Serving your second customer costs you almost nothing extra. Same code, same server, no extra hours. That is what a high ceiling means here, and it is arithmetic about the shape rather than a forecast about you.
  • The work compounds. A bug you fix once is fixed for everyone who ever signs up after. Compare that to a service business, where every job starts from zero.
  • You own the thing. The code is yours, the billing account is yours, the customer relationship is yours. No platform can change its rules and delete your business overnight.
  • It is small on purpose. A product one person can run is allowed to be small forever. That is the point, not a limitation you have to grow out of.

What it is not

  • Not an app you sell once. A one-time purchase means you start every month from nothing again.
  • Not an agency. In an agency you get paid for hours and the money stops when you do. Here you get paid nothing for a long time, then possibly something without more hours.
  • Not a startup. There is no raise, no pitch deck, no board. If your plan needs someone else's money to work, this course is the wrong one.
  • Not passive. It is front-loaded. All the hours arrive first and all the questions arrive last.

The shape of a real one

Made-up examples, purely to show the shape: a single screen that tells a swim school which makeup lessons nobody has claimed this week. A tool that turns one trade's job photos into the format their insurer's portal demands. A thing that watches one spreadsheet and emails one person when a number crosses a line.

Notice how boring those are. Notice also that you cannot judge whether they are good, because you are not in those rooms. That is the tell. A well-chosen micro-SaaS looks pointless to everyone outside the niche and obvious to everyone inside it.

The test that the shape is right: you can describe it in one sentence containing a verb and a named role, and a person with that role nods before you finish. If you need a paragraph, you have not picked a problem yet. You have picked a category.

Who finishes one

People who can already write code, or who genuinely want to learn and are not just tolerating it as a toll. People who are already inside a niche and know which annoyance is real. People who can go months without revenue without panicking. People who like talking to users. People who finish things.

If you read that list and quietly failed two of them, keep reading anyway. The next three lessons are designed to give you a clean no, and a clean no this week is worth more than a stalled repo in March.

Do this next

Open a notes file. Write down three software tools you or someone you know actually pays for, and next to each, the one task it removes. Keep the file - every lesson after this one adds to it.