Your Micro-SaaS Niche Is Too Cheap, Not Too Small

Plausible Analytics runs out of Tartu, Estonia, with about five people, no outside funding, and roughly $1 million in annual revenue. The product does one job, counting website visitors without cookies, without collecting personal data, and without shipping anything to Google. Plausible started in 2019 when Uku Täht wanted an analytics setup his own company could live with, and that single wedge held. Around it, the micro-SaaS segment is projected to grow from about $15.7 billion in 2024 toward $59.6 billion by 2030, and the advice columns have spent years arguing that staying small is itself the strategy. The revenue data inside those niches suggests small is the shape of the business rather than the reason it works.

Narrowness Isn't the Variable That Decides Anything

One revenue tracker that follows more than 8,000 bootstrapped software products reports that 3,787 of them show visible revenue. Among those, average monthly recurring revenue is $4,298, the median is $145, and only about 6.1% clear $10,000 a month. Read that spread twice, because it maps the whole business model in a single line. Almost everyone in the middle band picked something narrow, and narrowness didn't save them.

What separates the top of that distribution is the size of the bill the customer was already paying to cope without you. European privacy rules had turned the free default into a legal argument businesses were having with their own clients, and a tool that made the argument disappear for the price of a lunch was cheap next to a lawyer's letter. That's a niche with money inside it.

You can see the same pattern across categories. Developer tooling and compliance-heavy software run 70% to 85% gross margins and charge between $99 and $500 a month per account, because the alternative on the buyer's side is a contractor, an audit finding, or an internal spreadsheet maintained by somebody's assistant. Creator-facing utilities mostly sit at $9 to $29 a month, because the alternative is free and nobody holds a budget line for it. The number of customers you serve isn't what sets your price. What those customers pay today does.

Price Against the Workaround, Not the Competition

Founders usually price by opening three competitor pricing pages and landing somewhere in the middle. That anchor is weak, because your real competitor is a manual process that appears on no pricing page anywhere. A ten-person accounting firm doesn't weigh your tool against a rival tool. It weighs your $149 a month against the twelve hours a week a junior staffer spends copying numbers between two systems.

You can find that number without guessing. Job postings in the niche list the tasks you want to automate, and freelance marketplaces list what those tasks cost by the hour. If a three-clinic dental group advertises for a part-time claims coordinator at fifteen hours a week, you're looking at a recurring cost in the thousands each month, which makes a $250 subscription easy math. If the same group has nobody doing the job at all, you're looking at a wish rather than a budget.

Some niches look promising for exactly the wrong reason. Nonprofit tech and sustainability reporting have low competition and thin budgets, and low competition often just means the money isn't there. That doesn't make them unbuildable, but it changes the shape of your business, because you'll need many more accounts at a lower price or a funder with a mandate to pay. The filtering instinct that separates a real niche from a sympathetic audience matters more here than the size of the field.

Build the Smallest Surface Area That Touches Money

Bannerbear works as an architecture reference for this. Jon Yongfook built an API that auto-generates images for social posts and ecommerce banners, and by his own public accounting the product passed $1 million in annual recurring revenue in September 2025, run by one person on a stack of Rails, Redis, ImageMagick, and AWS. The output is an image. There's no sprawling workspace attached to it, because the job never asked for one.

The rule that keeps a solo product profitable is easy to state and hard to follow. If a feature doesn't move money or remove a named risk for the one customer type you serve, it doesn't ship yet. Team permissions, admin dashboards, notification settings, and a preferences page with eight tabs all cost you maintenance forever and earn nothing in month one. A focused product can launch in four to twelve weeks, while every extra surface becomes a support ticket you personally answer at 11pm.

None of this is an argument for shipping something fragile. Spend the extra month on the tedious reliability work inside your lane instead of widening the lane. Handling the messy edge case in the file format your customers actually send beats adding a second export option nobody requested. You'll notice the difference in churn long before you notice it in your feature list.

Distribution Is a Place, Not a Channel

Plausible didn't grow by outspending Google. The company published comparisons, migration guides, and a lawyer-reviewed assessment of whether Google Analytics was lawful in Europe, all aimed at searches its buyers were already typing into a browser. When your niche carries a specific anxiety, you can write a hundred pages about that anxiety and rank for most of them. The cost is writing time rather than a media budget.

Bannerbear's growth came largely through Twitter/X and developer communities, plus search content, and that pattern repeats across solo software. One public place where the users already gather, worked consistently for years. If you're building for practice managers, that place might be a Slack group or an annual conference. If you're building for warehouse operators, it might be a Facebook group with 4,000 members. Find the room before you write code, because the way people talk in that room will shape what you build.

Paid acquisition usually fails at this scale for a dull reason. A $39 product can't absorb a $180 customer acquisition cost, and narrow audiences are hard to target. In a market of 7,000 identifiable businesses, a purchased list and a well-researched cold email sequence often beats every ad channel combined, and all it requires is a list of names and a reason to write to them.

The Moat Is Usually Paperwork and Retention

Data moats and community moats are the fashionable answer to the question of what survives the next model release. For a small company, the more reachable moat is administrative: the audit log, the reconciliation report, the two-year history, the integration that feeds your customer's accountant every month. Those assets are dull, they're specific to one industry's rules, and they're the reason a customer stops shopping around.

Vertical software has outperformed horizontal peers on retention for years, and the reason is structural rather than technical. When your tool holds the reconciliation history a clinic needs if it gets audited, leaving costs more than the subscription. When your tool is a nicer interface over data the customer can export in one click, leaving costs nothing. Plausible gets the same effect on a slower clock, because its customers' compliance position improves with every month they stay.

Regulation is the most dependable generator of expensive, specific problems, because it moves slowly and it creates deadlines. European privacy enforcement built Plausible's wedge, and something similar is happening right now in whichever industry you're closest to, whether that's a reporting requirement or a data retention rule. Those moments create a buyer with a date on the calendar and a budget attached, which is a better starting point than a market that looks large on a slide.

Plausible's business exists because a rule made the free option legally awkward for a lot of European companies, and five people in Estonia were willing to fix that one thing properly. If you're choosing a niche this month, the useful question isn't how few customers you can serve without starving. It's whether you've found a group already paying in hours, invoices, or risk to live with a problem your software removes. Without that invoice, you don't have a niche. You have a product with a signup page and no reason for anyone to reach for a card.