Skip to content
The Observatory

Foundations · 2 min read

When Agents Do the Work, the Old Failures Still Kill You

Paul Graham's essay "The 18 Mistakes That Kill Startups" is often read as a checklist for avoiding blunders, but its deeper argument is about what cannot be automated: choosing the right problem, caring about the user, and moving fast enough to matter. Those failures look different when agents are shipping code overnight — but they do not disappear.

Featuring · studied & reframed for AI-native builders“The 18 Mistakes That Kill Startups” — Paul Graham

The Marginal Niche Problem Gets Worse, Not Better

Graham's warning about founders retreating into small, safe markets is more dangerous in an era when software is cheap to produce. When building costs collapse, the temptation to spin up something narrow and hope it quietly survives intensifies — the effort feels trivial, so the risk feels invisible. But a small market is still a small market. Prototyping in hours does not change whether enough people care about the problem. The bottleneck moves from typing to thinking, and thinking about market size is exactly the judgment no agent handles for you.

Single Founder Risk Is Now a Judgment Risk

Graham observed that single founders struggle because there is no one to catch bad decisions or push back on drift. With agents running workflows, the feedback loops can feel like company — activity everywhere, tasks completing, dashboards moving. But throughput is not the same as direction. Agents execute against goals a human sets; they do not argue about whether the goal is right. The founder who outsources too much thinking to autonomous tooling is still a single founder, just one with a busier inbox.

Platform Dependence Has a New Face

Graham listed platform dependence as a structural kill shot — building on a single gatekeeper who can reprice or foreclose access. In an AI-native company, that gatekeeper is often a foundation model or an inference provider. A product that cannot function when the underlying model changes terms, raises prices, or shifts behavior has recreated the exact dependency Graham diagnosed. Designing for that risk from the start — with evals, fallback paths, and human review at critical junctures — is the architectural equivalent of not building exclusively on one app store.

"Didn't Make Something Users Want" Is Still the Root

Graham concluded that almost every failure reduces to not making something users want. Agents can generate features at speed, but speed in the wrong direction is not progress. Taste — knowing what to ask for and recognizing when the answer is good — remains the scarce skill. The founder's job is to hold that standard, refuse mediocre output, and stay close enough to actual users that no amount of agentic productivity substitutes for the signal of someone genuinely wanting the thing.

Try the Desktop OS

Explore Atlanta’s startup scene, live.

Everything you just read lives inside our Desktop OS — an interactive workspace that opens right in your browser. Its Atlanta desk maps the city’s startup scene: who’s building, what’s happening, and where. Open it and take a look.

Open the Desktop OS →