Building in public. One person, AI-native, every industry. Writing about what actually works when you stop hiring and start building.
strategy
Every solo builder hits the same wall. Not a revenue wall or a skill wall. A time wall. There are 168 hours in a week, and after you subtract sleep, eating, exercise, and whatever passes for a personal life, you're left with maybe 50-60 productive hours. When the
tool-review
WordPress powers 43% of the web. That number gets cited in every CMS comparison as if popularity were a recommendation. It's not. Popularity is inertia. And for a solo builder choosing a publishing platform in 2026, inertia is the enemy of a clean stack. Ghost handles blogging, newsletters,
infrastructure
One file defines your entire stack. One command starts it. One command updates it. That is the whole deployment strategy, and for a solo builder running 1-5 projects, it is the only one you need. Docker Compose takes a YAML file that describes your services, volumes, networks, and environment variables,
ai
There is a moment in every solo builder's AI journey where the relationship changes. You stop asking the model questions and start giving it tasks. The interface looks the same. The economics are completely different. Most people who use AI are still in tool mode. They open a
strategy
A solo builder who bills $150/hour and works 30 billable hours a week makes $234K a year. On paper, that's a strong number. In practice, it means that every week without a client is a week without income. Every vacation is unpaid. Every slow January is a
tool-review
I used to run Spotlight for search, Rectangle for window management, Flycut for clipboard history, TextExpander for snippets, and a handful of Automator workflows for scripts. Raycast replaced all five. It's free. That's not a marketing claim. I uninstalled four apps in the same week I
infrastructure
Cloudflare sits in front of your site, the browser shows a padlock, and you assume your traffic is encrypted. For a lot of solo builders running self-hosted infrastructure, that assumption is wrong. The padlock means your visitor's connection to Cloudflare is encrypted. It says nothing about what happens
ai
Every solo builder hits the same wall with AI. You paste context into a prompt, get a useful response, and then the next conversation starts from zero. The AI has no memory. It doesn't know your clients, your conventions, your past decisions. You're doing the same
strategy
Venture capital has a specific thesis: fund a hundred companies, expect ninety to fail, and make all the money back on the ten that hit. This is a perfectly rational strategy if you're the one writing checks. It is an absolutely terrible strategy if you're the
tool-review
ffmpeg does the work of five SaaS subscriptions from a single command line. Video compression, audio extraction, thumbnail generation, format conversion, batch processing. If you're creating any kind of content as a solo builder and you're not using it, you're either overpaying for tools
infrastructure
Every solo project I run has the same problem at some point: the deploy process is whatever I remember it being. SSH in, pull the latest code, restart the service, hope nothing broke. It works until it doesn't, and it doesn't at the worst possible time.
dispatch
Every solo builder starts with the wrong stack. Not wrong in the sense of broken or stupid. Wrong in the sense of theoretical. You pick tools based on what you think your workflow will look like, and that mental model has almost no relationship to what your workflow actually becomes