A micro SaaS is small software for one narrow job. Customers pay monthly or yearly to keep using it. One person or a small team runs it without outside funding. A solopreneur can ship a thin version with AI coding tools, then judge every public revenue post by its date and its author.
A solopreneur starts and runs a business with no employees. You own the offer, you do the work, and the business has to fit one life. A freestyle entrepreneur builds that business around a life, not a life around a business. Search spells it micro SaaS, micro-SaaS, and microsaas. Same idea: a narrow product you can still check. Wider offers live in the one-person business ideas guide. This page is how to find a micro SaaS idea you could run.
What micro SaaS means
Tyler Tringas, on May 11, 2016, wrote “Micro-SaaS is a term that I use to describe my business, Storemapper,” “a simple app that helps merchants add a store locator to their website.” The shift he cared about was the bill: “customers pay monthly or annually for continued access,” and “The software is a service, rather than a thing they buy once.”
He added that “micro” just means small. The business he then described aims at a niche, is run by one person or a small team, keeps costs small, stays narrow, serves a small dedicated user base, and takes no outside funding. “Hence, Micro-SaaS.” His label, that day. Not a Census category.
On January 7, 2021 he wrote “I think I coined the term ‘Micro-SaaS'” and “maybe somebody else did it first.” Micro, for him, was “the scope of the problem being solved”: work “a solo founder or very small team” could finish. About seven years earlier he did not think that team could build a direct Salesforce, Heroku, or Airbnb competitor. A niche product was the size he meant. By that definition, he wrote, “everything is a Micro-SaaS now,” because off-the-shelf tools had widened the attempt. He called the change the Peace Dividend of the SaaS Wars. That is a January 2021 argument.
He also refused a formula. “I won’t claim to be a world expert.” “I’ve built exactly one successful Micro-SaaS business,” with “a slew of other failed businesses” behind it. “Nor will I make any guarantees that anything I have done is replicable.”
Three ways the same job can get paid
Our comparison. The first column follows his May 11, 2016 lines. The service column is the fixed-scope offer on the productized service page.
| Micro SaaS | A large software company | A productized service | |
|---|---|---|---|
| What the buyer gets | Software for one narrow job | A broad system | You, on a fixed scope |
| How they pay | Monthly or yearly, to keep access | Often a subscription, at company scale | A price for that delivery |
| Who has to be there | One person or a small team, no outside funding | Staff, and often investors | You, each time |
| What stays with you | Product, support, and the list | A department per function | The hours |
Say you keep books for a few shops. The repeated job is three documents they forget before month-end. The service is you chasing those files for a fixed fee. The software is a page where the files land, plus a reminder that fires only after you wrote the rule. He still killed the zero-hour story. In 2016 he wrote “I doubt it’s possible to get it down to zero” and called that finish line the mythical “passive income.” He also called the model “possibly the most powerful lifestyle business model” right then. Both lines are dated May 11, 2016.
Do micro SaaS businesses make money
Some founders publish figures. A figure is one person, one date. Not a median. Not your plan. He would not guarantee his path, and he put his own success count at one.
On May 11, 2016 he wrote that Storemapper “now generates over $250,000 in annual recurring revenue.” That “now” is the chapter’s day. This run fetched no later Storemapper revenue, so none appears here. The same chapter: he quit a job in 2011 for a cleantech software startup, it launched and raised money, and “in early 2014, we shut it down.” He wrote “we.” That firm was not solo. Storemapper, as he tells it, was a side project beside a consulting and software practice for ecommerce startups. By January 7, 2021 the post opens with “I’m an investor now.” The revenue line is a point on a timeline.
Photo AI, dates kept on the figures
Pieter Levels posted two notes on his site. The longer public write-up is the Pieter Levels profile. Neither post states a headcount, so this page invents none.
On March 6, 2026 he wrote “photoai.com is a 40,870 line file called index.php,” then “$105,000/mo revenue” and “$80,000/mo profit.” Self-reported, unaudited, that product, that day. The Photo AI site, fetched November 12, 2026, sells a subscription for AI photos of you, made at home. “You can cancel your subscription at any time.” “Every type of membership receives a certain amount of credits every month.” Monthly and yearly plans are there. No price is copied onto this page.
September 23, 2026 is a different set, and easy to mash. The post opens with “Passed $10M/y in revenue + investment gains this year.” Business revenue is a separate sentence: “My business revenue has remained very stable at about $200K-$250K/mo.” Investment returns, he wrote, have now surpassed that. “It’s now about 94.5% profit!” follows a cost cut he described as “by vibecoding my own replacements.” He added that “most investment gains are unrealized (I never sell!)” and said to “keep that with a big grain of salt.”
Keep them apart. Ten million includes investment gains. The monthly band is business revenue. March is one product, months earlier. The vibecoding line is his year, not a margin for a new app.
How to find a micro SaaS idea
Storemapper was one job, a store locator, next to ecommerce work he already did. The filters below are our guide, not a revenue forecast.
| Test | Keep it | Set it down |
|---|---|---|
| One sentence | The job needs no second product | The sentence says “platform” or “and also” |
| You have seen it | The job already shows up in your work | You found it on a list |
| It does the job | A stranger finishes inside the software | They must “fill it up with stuff” |
| You can answer | Support fits hours you have | It needs a team you lack |
“Fill it up with stuff” is his phrase from January 7, 2021, for empty SaaS: a login, blank rows, and the buyer still does the work.
The bookkeeping job, one sentence: shops upload the three month-end files, and the page shows what is missing. The sentence to drop adds invoicing, payroll, and a forecast for every small business. That is several companies. He had already separated a Salesforce-sized product from a very small team.
The number comes after the sentence. When you still do the job by hand, use the freelance pricing guide. A subscription is the continued access he described, and the figure still has to be one you can say aloud. Write the hosting bill, and any model or API bill, before an assistant drafts a pricing table.
Is SaaS growing or dying
The question sits next to this keyword. The pages fetched here describe cloud spending, which is not your niche app.
Gartner’s abstract, “Forecast: Public Cloud Services, Worldwide, 2023-2029, 4Q25,” published December 15, 2025, says GenAI demand will “drive public cloud growth to 20.7% in 2026,” with “annual spending reaching $1.49T by 2029.” Public cloud is wider than SaaS. The full report is behind a login. Gartner says there that its publications are opinions and should not be construed as statements of fact.
No worldwide SaaS-only rate for 2026 was on the pages fetched. Australia was. The May 11, 2026 Gartner release says software-as-a-service “remains the largest spending category” for Australian organizations in 2026, “forecast to reach almost A$16.4 billion.” “This 13.8% increase marks slower growth over 2025,” which that release ties to license optimization, slower seat growth, and tighter application portfolio scrutiny. Its table, Gartner (May 2026), lists SaaS at 14,386 million Australian dollars in 2025, up 15.0 percent, and 16,377 million in 2026, up 13.8 percent. Total Australian public cloud spending there is 33,619 million Australian dollars in 2026, up 17.9 percent. Australian dollars. Australian buyers. Not a survival rate for a US store locator.
Those forecasts still show growth, with Australian SaaS slower than the year before. They do not make a niche app true.
Ship the thin version with AI coding tools
Staff an assistant the way the AI for solopreneurs page does. You decide the job and the facts. A tool drafts. You check before a stranger clicks. As of November 12, 2026, two coding-agent products are examples, not a ranking.
Cursor’s agent docs, fetched that day, describe an assistant that can “complete complex coding tasks independently,” “run terminal commands, and edit code.” “Restoring a checkpoint reverts files only,” and “use Git for permanent version control.”
GitHub’s Copilot-in-IDEs page, fetched the same day, says “GitHub Copilot integrates with supported IDEs to help you throughout the development process.” In agent mode you stay present “while you review changes and redirect it as it works.” Same page: “GitHub Copilot can generate code that matches code in public repositories on GitHub.com.” A match is your call. Keep it only if you have the right.
On September 23, 2026 Levels wrote that he cut costs “by vibecoding my own replacements.” His year, not a log to replay, and not a reason to replace billing with an untested draft. Repeat mail, a failed upload or a renewal, belongs in the AI automation guide. The agent may draft the reminder. You own the rule that sends it.
You decide, AI drafts, you check
Paste a fact sheet. Ban new statistics, customers, and prices. Delete any sentence that was not on the sheet.
| Job | You decide | AI drafts | You check |
|---|---|---|---|
| The idea | The job, the buyer, three things you will not build | Ways the job shows up in a workday | Each idea matches work you have seen |
| The thin product | The screens, and which files may change | Those screens only | You click the path; the diff matches; Git has it |
| Page and price | What it does, what it refuses, the price, how to cancel | Copy that stays on the sheet | No new revenue, customer, or rank |
| Support | The answer you will sign | A reply from that answer | Steps match the product, then you send |
| The list | Who may hear from you, and that you will write | One broadcast from the sheet | You read it; no drip you have not built |
Price, support, and the list
The price is one sentence: what access includes, what it costs, how they stop. A footnote of exceptions means you are still inventing the job per buyer. Costs you pay go on the sheet first. A price lifted from another homepage does not. That is why none is printed here.
Support stays yours. The agent may draft the reply. You check it against the product you shipped, then you send it.
People waiting for the launch, and people who already pay, belong on a list you control. For that list, we like Kit for this: it’s free up to 10,000 subscribers. Partner link · T&Cs apply. Kit’s help center, updated September 23, 2026 and fetched November 12, 2026, says “The Free plan costs $0 per month” “for as long as you stay under 10,000 subscribers,” with “Up to 10,000 email subscribers,” “Unlimited forms and landing pages,” and “Unlimited email broadcasts.” “Email sequences” are on the paid plans. Past 10,000, “You’ll need to upgrade to a paid plan to keep sending.”
The pricing page, fetched the same day, says “up to 10,000 subscribers, for free.” Over a plan’s limit, “we’ll automatically upgrade it to the next subscriber tier.” It also says “There are no sending limits on any of our plans at Kit.” That line is how many emails you may send, not a free plan past the cap. The pages disagree, so both are here. On the free plan, write a broadcast and read it. A sequence that sends itself is paid. Our recommendation. Nothing fetched says Tringas or Levels uses Kit.
A first week
Our plan for a team of one. Not a study. Not a promise that anyone pays.
Monday. One sentence: the job, the buyer, three things you will not build. Two products in the sentence means you cut.
Tuesday. Sketch the screens. Leave price blank until the cost sheet has bills you pay, or the service version already has a price you defend.
Wednesday. The coding agent gets those screens only. Click every path. Read the diff. Commit in Git. Public-code matches you cannot source come out.
Thursday. Fact sheet: does, refuses, price, cancel. The page is drafted from the sheet. Strike any customer, savings figure, or rank that was not on it.
Friday. One person who has the job walks the path, or you finish a test payment. If you cannot, it is not ready. One note, read by you, to people who asked. No email course you have not built.
Takeaway
One narrow job, sold as continued access, small enough that you still check it. Tringas set that shape in 2016, argued in 2021 that scope had widened, and would not guarantee the money. Levels dated his figures, and the September post keeps business revenue apart from investment gains. You decide. A coding agent drafts. You click, you read the diff, you keep the list.
- Hold the 2016 definition, and date “everything is a Micro-SaaS now” as his 2021 argument.
- Read each money post for date, author, and investment gains mixed in.
- Take the idea from a job you have seen. Ship that job’s screens only.
- Charge a number you can say aloud. Send email you have read.
Grab the free One-Person Business AI Stack checklist when you want a one-page list of what you decide, what software drafts, and what you still check yourself.
Sources
- Tyler Tringas, “Chapter 1: What Is Micro-SaaS & Why Should You Read This,” May 11, 2016, fetched November 12, 2026. Definition, Storemapper, the $250,000 ARR line, the 2011–2014 startup, and the no-guarantee lines.
- Tyler Tringas, “2021 SaaS Market Predictions,” January 7, 2021, fetched November 12, 2026. Coining, scope, and empty SaaS.
- Pieter Levels, March 6, 2026 post, fetched November 12, 2026. Index.php line, revenue, and profit.
- Pieter Levels, September 23, 2026 post, fetched November 12, 2026. The $10 million line, business revenue, profit, vibecoding, unrealized gains.
- Photo AI, photoai.com, fetched November 12, 2026. Cancellation line and monthly credits. No prices copied.
- Gartner, “Forecast: Public Cloud Services, Worldwide, 2023-2029, 4Q25,” published December 15, 2025, abstract fetched November 12, 2026.
- Gartner, “Australian public cloud forecast, May 11, 2026,” fetched November 12, 2026.
- Cursor, “Cursor Agent,” fetched November 12, 2026.
- GitHub Docs, “GitHub Copilot in IDEs,” fetched November 12, 2026.
- Kit Help Center, “The Kit Free plan,” updated September 23, 2026, fetched November 12, 2026.
- Kit, “Pricing and plans,” fetched November 12, 2026.