
Why I'm Here
I built 30 things alone and showed nobody.
Not because I was afraid of rejection. Because I never had to. The day job paid well. The family kept me busy. The projects were mine — little worlds I could control, polish, restart. Nobody could tell me they were wrong because nobody ever saw them.
That's not failure. That's isolation wearing the costume of productivity.
Here's what the research says: 54% of founders experience burnout. 64% cite decision fatigue as a top challenge. 27% report loneliness. Only 6% report zero mental health issues in the past year. And solo founders — the ones doing this without a co-founder to share the weight — are the fastest-growing segment of new startups. One in three new companies is now built by a single person.
The tools made it possible. Nobody made it survivable.
I spent 16 years in the Army. A year in a combat zone. Six years in a drill sergeant unit. Then the FDIC, examining banks. Then Dell, shipping AI products for enterprise. I know what it looks like when someone is carrying a load alone and pretending they're fine. I've been that person. I've trained that person. I've examined the systems that fail because that person finally breaks.
Building solo is not a lifestyle flex. It's a weight. And most of the content about it — the “ship daily,” the “$10K MRR in 90 days,” the screenshots of Stripe dashboards — is a highlight reel that makes the isolation worse. You see someone else's wins and you feel further behind. You're not further behind. You're just alone, and alone is heavy.
What I actually believe
AI gave us something we didn't have before: the ability to build without asking permission. I don't need a team to ship a product anymore. I don't need funding to test an idea. The barrier between “I want to make this” and “I made this” got very thin, very fast.
That changes what's possible for people like me. I had a notebook full of ideas and a Projects folder full of half-finished builds. Not because I lacked ambition — because I lacked leverage. One person couldn't do all the parts. Now one person can. That's not a productivity gain. That's a different kind of life.
The napkin sketch becomes a working prototype in a weekend. The thing you always wanted to build but couldn't code — you can code it now, or close enough. AI doesn't care that you're not a developer. It just builds what you tell it to build.
AI makes you more you. It lets the ideas that were stuck in your head actually exist in the world. That's the part of this story I care about.
Why I'm doing this in public
Because the 30 projects died from solitude.
Not from lack of skill. Not from lack of ideas. From building alone, in silence, with nobody to tell me I was wrong and nobody to tell me I was on to something. The graveyard in my Projects folder is a monument to what happens when you build in isolation: beautiful things that nobody needed, because I never asked.
I don't want other people to follow that path alone.
Not because I have all the answers. I'm maybe one step ahead. Maybe half a step. But I've been in the room where 30 things went to die and I know what it smells like in there. And I know the exit isn't “be braver” or “ship faster.” The exit is: show someone. Let them tell you it's wrong. Let them tell you it's right. Either verdict is better than silence.
This site, this newsletter, the build log, the strategy calls — it's all the same thing: trying to create connection for people who are building alone. A sense that someone else is out here doing the same stupid, hard, exciting, lonely thing. That you don't have to figure it out by yourself even if you're building by yourself.
What this actually is
I'm not starting with a platform or a program. I'm starting with honesty. Writing what I'm learning. Sharing what's working and what isn't. Taking calls with builders who are stuck. And hoping that the honesty creates gravity — that people who recognize themselves in this will stick around, and that sticking around will make the work less heavy for all of us.
Building solo doesn't have to mean building alone.
Not networking. Not “community” as a product. Just the knowledge that someone else is out here, one step ahead or one step behind, willing to say “yeah, that's hard” instead of pretending everything is a win.
Who this is for
You took the long way here. Maybe you prototyped something over a weekend and it actually works. Maybe you got laid off and realized the excuses were gone and it was just you and the question you'd been avoiding. However you got here, you're building something and you're building it alone.
You're not 22 and fearless. You have a mortgage and kids and a life that doesn't pause while you figure this out. You're building in the margins. And you're wondering if anyone else feels the way you do — excited and terrified and a little bit alone.
I feel that way. Every day. The difference is I'm saying it out loud now. That's all this is.
The real thesis
AI scales faithfully. Make sure it's scaling the right thing.
That's true for products and it's true for lives. Point AI at a clear idea and it accelerates you. Point it at avoidance and it builds you a prettier version of hiding. The tool doesn't know the difference. You do.
So the question that matters isn't “what can AI build for me?” It's simpler and harder than that: what do I actually want to make? What would I build if I stopped waiting to feel ready?
I don't have the answer for you. I barely have it for myself. But I'm working on it in public, which is more than I did for the last thirty projects.
That's why I'm here.