Micro-SaaS

The uncomfortable ratio

Ask a hundred people who attempted a software product what went wrong and the answers cluster hard. Almost nobody says the software did not work. Almost everybody says nobody came.

This is the central asymmetry of micro-SaaS. Building is the part that feels like progress, is entirely within your control, and can be done alone in a quiet room. Distribution is uncomfortable, depends on other people, and produces no visible output for weeks. So technical founders spend eighty per cent of their effort on the twenty per cent of the problem that was never the constraint.

The correction is unpleasant but simple: before writing code, decide specifically how the first hundred customers will find out this exists. Not "content marketing" — which forum, which search term, which integration directory, which twenty people you will message personally. If you cannot answer that concretely, building the product will not help.

Why small is the strategy, not a limitation

The instinct is to build something ambitious. For a solo founder this is close to suicidal, and narrowness is the actual advantage.

A large competitor cannot justify building a feature that serves four thousand people. You can, because four thousand customers at $40 a month is a life-changing business for one person and a rounding error for a company with two hundred staff. The niche that is too small to be worth attacking is precisely where a one-person software business is safe.

Narrowness also fixes the hardest problems for free. Marketing becomes easy because you know exactly where those people gather. Support becomes easy because everyone has the same problem. The product roadmap becomes obvious because every customer wants the same next thing.

The founders who struggle most are usually building something horizontal — a tool "for teams" or "for businesses" — where there is no specific person to find and no specific problem to solve better than anyone else.

Churn is the number that decides everything

Growth gets the attention. Retention determines the outcome.

Consider two products both adding 20 customers a month at $50. One loses 3% of customers monthly, the other 10%. After two years the first is at roughly $17,000 MRR and still climbing; the second has flattened around $9,000 and will not go higher, because new customers only replace the ones leaving.

The second business is not growing slowly. It has stopped growing, and adding more marketing spend will not change that — it will just increase the size of the leak.

High churn nearly always means the product is not deeply embedded in how the customer works. Tools people set up once and forget churn quickly. Tools that hold their data, integrate with their workflow, and would take a day to migrate away from do not. Designing for that at the start is far cheaper than fixing it later.

The realistic timeline

Month one to three: talking to people, building the smallest version, first paying users if you are moving fast and already know the market.

Month four to twelve: the hard part. Revenue in the hundreds. Constant doubt about whether this works. Most people quit here, and most of the ones who quit were closer than they thought.

Year two: if the product found a real problem, compounding starts to show. Customers refer others, search traffic accumulates, and MRR that took nine months to reach $2,000 reaches $6,000 in the next six.

Year three and beyond: the business either has genuine product-market fit and grows largely on its own momentum, or it has plateaued and is a modest, pleasant income that will not become more. Both outcomes are acceptable; expecting the first within twelve months is not.