Notes from a one-person company

The solo SaaS used to be a stunt. A blog post would surface every few months — "I built a $30k MRR business by myself" — and the comments would split between admiration and disbelief. By 2026 it is, quietly, just a category. Maybe one in ten of the indie SaaS products I touch in a given month is run by a single person. Most of them are not novelty acts. They are real businesses.

What it actually takes to run one has changed less than the tooling around it. The tooling helps. The job underneath is still the same job.

What the tooling buys you

A solo founder in 2026 can plausibly run:

• A working web app, with auth and payments, on a managed stack with no dedicated ops time.
• A support inbox triaged by a mix of macros and LLM-drafted replies the founder edits.
• A marketing site, blog, and small content engine, with AI for first drafts and the founder for editorial judgement.
• Basic accounting and tax compliance via tools that integrate with Stripe.
• A small AI-assisted code review pipeline that catches the worst of the obvious mistakes.

This is genuinely new. It would have been three full-time roles in 2018. It is still a lot of work in 2026. But it is no longer impossible.

What it does not buy you

The tooling does not solve the part of the job that actually breaks people.

That part is sustained, multi-year focus on the same problem. The solo founders I know who are doing well are not unusually productive. They are unusually consistent. They have decided, on purpose, to work on the same product for the next five years and to refuse the distractions that would shorten the runway.

The distractions are not what you think. They are not Twitter or video games. They are the parallel project. The friend's startup that needs a hand. The consulting gig that would cover a quarter of expenses. The new feature that would be fun to build but does not move the needle.

The hardest thing about being a one-person company is that nobody else will tell you no. You have to be your own no.

The shape of the actual work

A typical week for a successful solo founder I know looks roughly like this.

• Two days of building. Real, focused, headphones-on work. Often on something that does not feel exciting.
• One day of writing — sales pages, support docs, blog posts, the occasional public reflection.
• Half a day of customer conversations — onboarding calls, churn calls, support requests that turned into something deeper.
• A few hours of admin — invoices, taxes, the quarterly tax filing, the annual whatever.
• The rest is recovery.

This is not the eighty-hour week of indie hacker lore. Eighty-hour weeks are something solo founders do in year one and never again. The ones who try to maintain it burn out by month eighteen. The ones who don't can keep going for a decade.

The unfashionable truth

The most useful thing I can tell you about running a one-person company in 2026 is that it is not romantic. It is a job. The job is well-suited to a specific kind of person, and disastrous for everyone else.

If you are someone who needs the energy of a team to do your best work, do not run a one-person company. You will hate it. If you are someone who needs the freedom of working alone to do your best work, do not join someone else's startup. You will hate that.

The solo SaaS is a specialized vehicle. The reason there are more of them now is not that AI made it easy. It is that AI removed the last few infrastructure excuses, and the people who were always temperamentally suited to this work can now finally do it. They are not a new class of founder. They have always been around. They just used to lose.