The advice is always to “go all in.” Quit the job, burn the boats, commit fully. But most people can’t — and most people who do still need the bridge that comes before the leap. So here’s the less romantic, far more useful system: ship on evenings and weekends, in the margins, and let the calendar do the heavy lifting. The honest calendar math A side project doesn’t die from a lack of passion. It dies from a lack of time to show up consistently. So the first move is brutal and clarifying: count the actual hours. ...

Here’s a belief that quietly kills more solo products than any technical problem: “I’ll start charging once it’s good enough.” The product never gets good enough, so the charge never comes, so the product never gets a real signal about whether it matters. The fix is to flip the order entirely. Charge early. Charge small. Let the first $5 be the proof, not the goal. What the first charge actually is It’s not revenue — it’s a measurement. A stranger willingly handing over money, even a tiny amount, is the single most information-dense signal you can get about a product. It settles three questions at once: ...

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. ...

The simulator said it worked. The phone crashed. That gap, between a green test run and a bricked handset, is where on-device software actually gets built. And it’s a gap almost nobody writes about: the people who survive it are too busy shipping to blog, and the people who blog about “I built an AI voice thing” mostly stopped at the demo that only ever ran in the simulator. This is about the specific, physical reasons the simulator lies, and why shipping on real hardware is a different craft than passing tests. ...

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. ...

Something strange is happening to the cost of building with AI. Every headline says prices are collapsing — and they are. Per-token rates have fallen roughly 97% since 2023, and open-weight models now cost a fraction of the frontier ones. And yet, quietly, the bill keeps going up. Uber burned through its entire 2026 AI-coding budget by April. Microsoft revoked developers’ Claude Code licenses months after enabling them. Priceline’s contract renewal came back 4–5× more expensive. One engineer reportedly ran up a $40,000 token bill in a single month. Per-developer token consumption rose roughly 18.6× in nine months as tools drifted from “answer a question” to “agent, do the task.” ...

There’s a story every solo founder gets told somewhere along the way: go where the buyers already are. Post where the community gathers. Build your audience on the platform that’s already huge, because that’s where the traffic is. It’s good advice — right up until the platform changes the rules on you overnight. That’s exactly what happened to Reddit in August 2026, and if you’re building a one-person business today, the episode is worth understanding not for the temporary headline, but for the permanent lesson hiding underneath it. ...