One Person Team

There’s a question every solo builder answers eventually, usually by getting it wrong once: Which answers am I allowed to act on without checking? Not “which tasks can AI do” — that’s a capability question and the answers change every few months. This is a sorting question, and it doesn’t change with the model. It changes with the task. The framework — and why it isn’t the article Let me be honest up front, because we do this on every post: the grading framework itself is not new, and it is not ours. Regulators, enterprise security teams, and academic groups have all published versions of it. Microsoft’s agentic-risk guidance says require approval for high-risk or irreversible actions. A recent DeepMind paper on delegation names reversibility as the axis that decides how much authority you can hand over. Practitioners publish permission matrices grading actions by blast radius × reversibility × stakes. If you want the general framework, those sources will serve you better than a solo-builder blog, and I’ll list them at the bottom so you can check them. ...

The agent reported success. The job “completed.” Then the next step in your pipeline received nothing, and you spent an evening chasing the mystery. Here’s the liberating truth most solo builders don’t reach until it costs them: your agent’s failures are almost never dramatic. They’re mechanical, and mechanical means diagnosable. The bug was one missing closing bracket. The fix was reading one number in a log file. There is no genius in it — and that’s exactly the good news. ...

Everyone building on AI now is asking the same question: which model? And it’s the wrong question, because the model is the one part of your stack you don’t own, can’t keep, and will be forced to swap the moment a cheaper one ships. What you can own is everything that wraps around it. The memory. The rules. The decision boundaries. The list of things you’ve already verified and never have to verify again. ...

The agent said the tests pass. The commit is pushed. The deploy finished. As far as the summary in your chat window is concerned, the feature is done. Then you actually click the link and the page is a blank white screen. This is the most expensive sentence a solo builder learns the hard way: “done” is a claim, not a fact. And when your team is a handful of AI agents working through a chat interface, the gap between “claims done” and “is done” stops being an edge case and becomes the whole game. ...

A solo founder hit the Top 50 on Product Hunt last week. The launch went perfectly — hundreds of upvotes, real momentum, the kind of day most indie hackers dream about. Then they checked their signups. Zero. Not “low.” Not “disappointing.” Zero. That story is more important than any success headline, because it’s the typical story. An analysis of 50 failed solo founder projects — combed from post-mortems on Indie Hackers, r/SaaS, and Hacker News — found the #1 cause of death wasn’t bad ideas. It wasn’t technical debt. It wasn’t even running out of money. ...

There’s a new job title forming, and it doesn’t exist on any org chart. Fortune named it in March 2026: the supervisor class — developers whose primary value is no longer writing code but orchestrating the agents that write it for them. This isn’t a prediction. It’s already the daily reality for the fastest solo builders. And it changes something more fundamental than how fast you ship. It changes what you are. ...