Tag: Y Combinator

Categories
AI Startups

A New Reason to Launch

“Before you launch, the speed you can build is now mainly limited by your imagination in what you tell AI. After you launch, the AI can watch your users and make improvements on its own.”
— Jared Friedman, Y Combinator

Jared Friedman watches hundreds of founders a year navigate the gap between idea and launched product. He notices patterns the rest of us miss. And what he’s describing above is not an incremental improvement in how software gets built. It is a change in the nature of the advantage.

This is a different kind of liberation than founders have known before.

The old liberation was launch early and the market corrects your wrong assumptions. Humbling, but useful. You were still the one doing the correcting, late at night, rewriting the onboarding flow based on what the data told you.

The new liberation he’s describing is something closer to multiplication. You launch, and now there are effectively more of you. The AI is watching session replays you’ll never have time to watch. It’s noticing the drop-off after step three that you’d have caught in month four. It’s holding the pattern of a thousand user paths simultaneously and asking what they mean. Your imagination seeded the thing. Reality is now feeding it.

That observation redraws the map cleanly. Pre-launch and post-launch used to differ in degree — you knew more after than before. Now they differ in kind. Pre-launch you are the sensing organ. Post-launch you’ve grown new ones.

The founders who feel this most viscerally, I suspect, are the ones building alone or in pairs — the people for whom every previous era of building had a hard ceiling imposed by human hours. They could only read so many support tickets. They could only run so many experiments. The ceiling is lifting and the feeling is of a room getting larger.

The core advice hasn’t changed. Paul Graham was saying “launch early” twenty years ago and it was true then. What’s changed is the reason underneath it — the mechanism that makes it true now is nothing like the one he had in mind.

The advice is twenty years old. There is a new reason and it is brand new. Most people haven’t noticed the swap yet. But they will.

That window does not stay open long.

Categories
AI Stanford

The Unit of Production Just Collapsed

The lecture was a Stanford CS session, AI-native companies, Garry Tan walking through what it now takes to build something. He’d rebuilt his old startup, Posterous, in five days on a modest Claude plan. A thing that once required a team and a runway. He said it matter-of-factly, the way you describe something that’s already obvious to you and hasn’t yet reached everyone else.

The argument Tan and his colleague Diana Hu were making wasn’t really about AI. It was about the economics of effort — specifically, what breaks when the cost of turning an idea into a working thing falls by an order of magnitude.

Their framing: AI-native organizations running as closed-loop systems, agents with access to the real artifacts of work, able to iterate without the error-accumulation that comes from handoffs and headcount. Revenue-per-employee ratios of a million dollars or more, with live examples already in the YC portfolio. Document processing, logistics, voice agents for specialized workflows.

What I kept hearing underneath all of it was a quieter claim: the mental model of what a startup requires is wrong.

Or rather, it’s right about the past and increasingly wrong about the present.

The assumptions embedded in “I can’t do this alone” or “we’d need to hire for that” or “we don’t have the bandwidth” — those are load-bearing assumptions, and the load is shifting.

I have some small version of this — not as a founder, but as someone who retired into curiosity. The blog, the reading, the daily effort to keep up with what’s moving: each one is a practice in staying oriented while the map keeps changing.

What I notice is that the constraint has shifted. It’s not information anymore. It’s not even tools. It’s the capacity to ask better questions of the abundance, to know what matters when everything is accelerating.

That’s the thing I find unsettling, yet also genuinely interesting: the skills that remain irreplaceable are the hardest ones to teach, and the hardest to evaluate in yourself. Knowing what matters. Recognizing when an output is almost right and almost wrong. Setting direction in ambiguous conditions and being willing to be wrong about it. These were always the valuable things. They were just obscured by all the coordination overhead that surrounded them.

The students in that Stanford course were asked to build something called a One-Person Frontier Lab — use the best available tools to extend your own reach over ten weeks. It’s framed as an academic exercise. It doesn’t feel like one.

But I’m not building. I’m mostly watching, and thinking about what this radical new fermentation does to everything downstream — to labor markets, to what a company even is, to how we’ll organize work and meaning when the old unit of production no longer applies. Those are slower questions. But they’re the ones that feel urgent to me.

The old excuses are getting lighter. Not that everything is possible — but that the weight of the usual constraints has changed.

What you choose to build, and whether you choose to build it at all, is more purely a decision than it used to be. That’s either clarifying or terrifying, depending on the day and my mood.