Solo Founder

Most advice about the first hire answers the wrong question. It tells you who to hire — an engineer, a generalist, a contractor first. Or it hands you a feeling: you’ll know it’s time when you’re drowning. Neither is decision-grade. “You’ll know” is not a number, and the person who feels most like drowning is often the worst person to be making a hiring call. The question that actually has data behind it is narrower: what predicts whether the hire works out? And the honest answer, from the two best datasets available, is not timing. ...

For most of the history of shipping software, a solo builder could answer one question with a single, static number: “what does this cost me a month to run?” You tallied a server, a database, a couple of SaaS subscriptions, rounded up, and you were done. The number was flat. You built to it and forgot it. That number is now fiction. The tools you build on stopped charging you a flat rate and started charging you by the meter. GitHub Copilot — the most common AI coding subscription on the planet — moved to usage-based billing on June 1, 2026: every plan now draws down monthly “AI Credits” pegged at one cent each, with the old automatic fallback to a cheaper model removed entirely. Anthropic now estimates the average developer burns $13 per active day in Claude Code token spend — up from $6, doubled in one quiet docs edit. Flat-rate is over, and the solo builder is the one who feels it hardest because there’s no CFO to absorb the surprise. You are the CFO, the engineer, and the one who pays. ...

“Solo founder” used to be a phrase investors said with a wince. It read as couldn’t find a co-founder — a red flag on a term sheet. Going it alone was the backup plan, not the point. That framing is now dead, and it didn’t die by argument. It died the way framings actually die: the data stopped supporting it. This post is about the two datasets that killed it — and about the one number in them that most people quoting these stats get backwards. ...

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

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

Every blog that tells you to “hire your first contractor” is written by someone who profits when you do. The staffing agencies, the fractional-CXO marketplaces, the “done-for-you” studios — they all want the same transaction, and their advice bends toward it. That’s the first thing to understand: hire advice has a sales team behind it. So here’s the receipts-first version, built from the actual numbers solo founders report, not from a vendor’s funnel. ...

There’s a quiet new feeling in the solo-builder world that nobody has a good name for yet. It’s not burnout — burnout is when you’re exhausted from the work. This is different. You’re fine. You’re shipping more than you ever have. And yet the list keeps getting longer, not shorter, every single week. You can probably feel it right now: you finished the thing that was at the top of the list this morning, and by lunch there are three new things where one used to be. It’s not that you’re slow. If anything, you’re faster than you’ve ever been. So why does it feel like you’re falling behind at your current speed? ...

Ask a solo founder how they set their price, and most will admit they didn’t. They picked a number that felt defensible, rounded it to something clean, and moved on to the part they actually enjoy. Pricing is the chore nobody wants to do — and it’s the single highest-leverage dial a one-person company has. Here’s the thing the “raise your prices” advice never explains: for a solo founder, the number matters less than the model. Whether you charge $9 or $29 a month is a rounding decision. Whether you charge recurring at all — versus a one-time license, versus per-seat, versus usage — is a strategic one. And the data is finally clear on which direction wins. ...

There’s a specific loneliness to solo-founder burnout that the “self-care” advice never captures. In a team, when someone burns out, other people notice. A colleague sees the late commits. A manager flags the energy drop. Someone says “you’re doing too much.” A solo founder burns out in silence — because the person who would normally notice is the same person who’s burning out. That’s not a character flaw. It’s a structural fact of the one-person company, and it has a name. The World Health Organization codified burnout as an occupational phenomenon — not a medical condition, but something with a precise, three-part definition that’s worth actually reading, because naming the thing is the first step to fixing it. ...