PETER DIRICKSON

The Software House of One

How a single engineer can ship like a five-person team with Claude Code and a spec discipline.

November 18, 2026·11 min read·
AgencySDD

I have a day job. I have a daughter. I run a vacation rental in Brazil. I produce deep house at 11pm. And in the last fourteen months, I've shipped six AI-native products through Frenti, my one-person agency.

This is not a productivity flex. It's a thesis about what one engineer can do now that couldn't be done before — and what discipline makes that possible.

The thesis is: with agentic coding and spec-driven development, the bottleneck on a one-person agency has moved. It used to be implementation. Now it's clarity.

The shift

Five years ago, the limit was hands on keyboards. You couldn't write a backend, a frontend, an admin panel, an editorial pipeline, and a marketing site in a quarter, alone. Today you can — but only if you can hold the whole product in your head clearly enough to describe it in spec.

The Workshop wasn't a UI experiment. It was the only honest way to show what one person plus agentic coding (AI) can actually do.

Spec-driven development isn't about writing more documentation. It's about removing ambiguity from the build before code is written, so the assistant doesn't have to guess.

What a spec actually looks like

A spec for me is four fields: Intent, Constraints, Context, and Acceptance criteria. Together they fit on one page. The Intent is one paragraph in plain English. The Constraints are the non-negotiables (stack, conventions, what not to touch). The Context links to whatever else the coding agent needs to read. The Acceptance criteria are testable — usually a checklist.

claude --dangerously-skip-permissions \
  --read CLAUDE.md \
  --read specs/P-01.md

That command, against a clear spec, ships a feature.

What changes when implementation isn't the bottleneck

Three things, in order of how disorienting they were:

  1. Your throughput becomes embarrassing. I shipped Pico in a week. AskBahia's content pipeline in three days. The Software House of One is real.

  2. You start refactoring your own thinking. Because the spec is now the artifact that matters, you spend more time on framing than on code. This is actually harder than coding — you can't bullshit a spec.

  3. You lose the excuse of "I didn't have time." That was the old excuse. The new one is "I didn't have the clarity yet." More honest, more vulnerable.