One Person Company

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

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

A solo founder wakes up already behind. There’s the product to build, the customers to answer, the books to square, the marketing nobody’s doing, the bug that shipped last night. Six jobs, one seat. Most people call this a focus problem and reach for a timer or a todo app. It’s not a focus problem. It’s a structure problem. You’re not failing to do six things at once because you’re undisciplined — you’re failing because six things are the wrong number. The solo founders who make it work don’t get faster at juggling. They stop carrying five of the six balls. ...

The build-vs-buy debate is the oldest argument in software, and for years it was boring math: build if the license would cost more than the engineering. AI broke that math. When a solo builder can scaffold in a weekend what used to take a quarter, the cost case for reusing something — a library, a SaaS tool, an open-source project — quietly stopped being the deciding factor. What replaced it is a quieter question: who owns this thing when it matters? That’s not a cost question. It’s a custody question — and it’s the one that actually decides, in practice, whether your one-person company survives its third year. ...

For most of startup history, “who’s your co-founder?” wasn’t really a question. It was the first box on a checklist, right after “what’s your idea?” A single founder who went it alone would hear the same first line every time — you’ll wish you had a team — as if a co-founder were insurance you’d bought, not a person you’d now be legally and emotionally tied to for a decade. ...

Until very recently, “solo founder” was a phrase investors said with a wince. It read as couldn’t find a co-founder — a red flag on a term sheet, a polite rejection from an accelerator. Going it alone was the backup plan, not the point. That stigma is now dead, and it didn’t die by argument. It died the way stigmas actually die: the numbers stopped supporting it, and the people closest to the numbers changed their minds. This is the receipts post — the outcomes that are now public, and what they actually prove. ...