The economics of a one-person studio

So people keep asking me some version of "how does the math work" on this, and I never have a clean answer, because the math changed shape on me while I wasn't looking.

Here's the old economics of building software, the one I grew up believing. The expensive thing was making it. Engineers were the cost center. Every feature was weeks, every app was months, and the whole game was about squeezing more output out of that scarce, expensive labor. You raised money mostly to buy time — other people's time, or your own runway so you could afford yours. Building was the wall you paid to climb.

That wall is basically gone for me now. I've put out seven products. Not seven features — seven whole products: tab., CreatorLens, Confluence, Maison, Fundability, CommunityHQ, App Marketing OS. One person. The building part of that, the part that used to be the entire cost, has collapsed to something close to free. Not literally free, but so cheap relative to what it used to cost that it stopped being the thing I budget around.

So if building got cheap, where did the money go? Because it didn't disappear. It moved.

The first place it moved is small and boring and I want to name it anyway, because nobody talks about it: the stack. A one-person studio doesn't have salaries, it has subscriptions. Claude Code and the model behind it. Vercel for the web apps. Expo and App Store Connect for the iOS ones. Supabase and RevenueCat under tab. Each one is a line item that shows up every month whether I ship or not. Individually they're nothing. Together they're the actual, literal cost of running the studio — the closest thing I have to payroll, except it's paid to tools instead of people. I'm not going to make up a number here because I don't track it tightly enough to quote you honestly, and a made-up figure would be worse than none. But the shape is real: my costs are a stack of small recurring bills, not a team.

That's the part that got cheap. Here's the part that didn't, and this is the whole point.

The expensive resource in a one-person studio isn't labor anymore. It's attention. And attention doesn't scale, it divides. I can build the eighth product this weekend — the marginal cost of making it really is near zero now. But I cannot carry eight products for free. Every live thing is a thing that can break at 2am. Every app is an App Store review cycle, a support question, a dependency that goes stale, a login that stops working when some API I don't control changes underneath me. tab. is live, which means tab. is never really "done" — it's a thing I'm on the hook for. The cost of building it was a weekend. The cost of owning it is forever.

So the real unit economics of this studio isn't cost-per-feature. It's how many things one person can keep alive before the carrying crushes the making. And that number is way smaller than the number of things I can build. That gap — build-a-lot, carry-a-few — is the entire tension I live in now.

It's why most of what I've made sits built-but-not-shipped on purpose. Confluence works. CreatorLens works. I could push both live this month. I haven't, and it's not laziness, it's economics. Shipping isn't the finish line, it's the moment a project moves from the cheap column (built once) to the expensive column (carried forever). Every launch is me signing up for a permanent little tax on my attention. So I've gotten stingy about it. I'd rather have five real things I actually stand behind than eight I'm quietly neglecting.

The thing that surprised me most is what the scarce resource turned out to be. I assumed it'd be money, or time, or even the AI credits. It's none of those. It's judgment. Deciding which of the seven deserves the next weekend. Deciding that a working app isn't ready. Deciding to not build the shiny new idea because I already have more surface area than I can defend. When making is free, choosing is the whole job, and choosing badly is the only way left to actually go broke — not in dollars, in attention.

So the honest economics of a one-person studio: building costs almost nothing, running costs a stack of small subscriptions, and the real budget — the one that's always overdrawn — is me. My attention, my willingness to say no, my capacity to carry a thing well instead of ship a thing fast.

I don't have a spreadsheet that makes this look tidy. I have seven things, a handful of monthly bills, and one increasingly protective attitude about where the next weekend goes. That last part isn't a cost line. But it's the only number that actually decides whether this works.