How many tools did you build?

123 across 15 verticals, all live in this directory. The count grows as we add the next vertical.

How long did it take?

The model is continuous, not a one-off sprint. Each narrow tool is days from idea to live; the portfolio compounds week over week.

What stack do you use?

Next.js + Vercel for the product, Waffo for payments, NVIDIA NIM for inference, and Umami for analytics — all managed from one keyboard.

Can one person really run this?

Yes. AI-assisted coding removes the build bottleneck; GEO removes the ad bottleneck. The constraint is judgment, not headcount.

Published 2026-08-22 · The playbook behind a one-person micro-SaaS factory: batch generation by vertical, a Next.js + Vercel + Waffo + NVIDIA NIM stack, and a GEO acquisition loop.

How We Built 123 Niche AI Tools From One Keyboard (One-Person Factory)

We run a one-person micro-SaaS factory: a repeatable system that ships narrow, production-ready AI tools one vertical at a time. Today the directory holds 123 live products, each solving a single job a founder or small team actually has.

The factory model

We generate by vertical, not by idea. Pick a job founders repeat — SEO briefs, AI-Act readiness, invoice reconciliation — build the smallest tool that does it well, ship it, then move to the next vertical. Breadth is the portfolio; depth is each tool.

The stack

Next.js for the frontend and the directory itself.
Vercel for hosting and instant previews.
Waffo for subscriptions and payments.
NVIDIA NIM for LLM inference.
Umami for privacy-first analytics.

The GEO acquisition loop

We practice Build in Public on Reddit and Indie Hackers and optimize for GEO so answer engines cite us when founders ask “which tool for X?” The playbook is laid out in our GEO explainer. Every new tool inherits the citation equity of the directory.

The flagship: GStack

GStack is the governance workbench that ties the R11 cluster together — the clearest proof that a one-person factory can ship something with real enterprise weight.

Lessons we would repeat

Ship narrow. A tool you can describe in one sentence ships and sells.
Own the workflow, not the model call.
Compound through GEO — it is free and it accrues.
Price for the job, not for the feature count.

Frequently asked questions

How many tools did you build?: 123 across 15 verticals, all live in this directory. The count grows as we add the next vertical.
How long did it take?: The model is continuous, not a one-off sprint. Each narrow tool is days from idea to live; the portfolio compounds week over week.
What stack do you use?: Next.js + Vercel for the product, Waffo for payments, NVIDIA NIM for inference, and Umami for analytics — all managed from one keyboard.
Can one person really run this?: Yes. AI-assisted coding removes the build bottleneck; GEO removes the ad bottleneck. The constraint is judgment, not headcount.