Translated from the 2026-08-14 version of the original

Is AI Breaking the Lean Startup Playbook?Patrick Collison × Harj Taggar · Guided reading notes by theme

Startup School 2026|Channel: Y Combinator|Original videoTranscript
Only the passages actually questioned and discussed in this reading session are included|Each point keeps the original English passage with a merged reading|The right column reorganizes the judgments from the session

Suggested reading path

  1. First decide what cannot be outsourced: once AI can do complex tasks, why people still need to learn, write and build their own cognitive cache
  2. Then dismantle the last-window anxiety: why a technological revolution and "act now or it is too late forever" are two different things
  3. Return to the core of lean startup: what a real user problem, an MVP and a public launch each validate
  4. Re-examine the starting point of a startup in the AI era: why niches get more crowded, and how de-correlating, anti-lean and schlep create difference and moats
  5. Finally take apart big-company competition: which organizational and execution steps lie between "able to do it" and "ultimately taking the market"

Five judgments that run through the whole piece

  • AI getting more capable does not mean human cognitive ability has lost its value
  • The technological change may be real, but "now is the last chance" needs a separate set of evidence
  • The core of lean startup is learning from reality; the MVP and the public launch are only ways of building evidence
  • AI makes development easier and also intensifies the homogenization of ordinary starting points; difference may come from less correlated, harder-to-enter starting points
  • A big company being able to do it does not mean it will choose to, organize for it, persist and finally win the market

1. Once AI can do it for us, what should people still keep for themselves

This node is not asking whether AI can complete the task, but: when AI can deliver results directly, what does university learning still provide that cannot be replaced by an on-demand lookup

Background passage

A creatively driven 16-year-old today could probably just prompt Claude to write their own Lisp dialect. Would you advise them not to do that, and still do it by hand? Is that kind of thing still valuable

Harj Taggar: Just as I’ve been hanging out here with these students, maybe the question behind it is many of them are just wondering what should they be learning at college? In this AI world, how much should they be trying to learn and derive from first principles and how much should they just outsource to the AI?

I dropped out after my first semester of freshman year and co-founded a company with Harj. That experience was a lot of fun. A few years later I went back to MIT for another year, then dropped out again to start Stripe

Why this question comes up

  1. AI's capability boundary is expanding fast: tasks that used to require long study and hands-on practice can now be completed by prompting a model
  2. The audience is in the middle of an education decision: the room is full of university students who need to decide whether to invest their time in foundational learning or use AI directly to get results
  3. The person answering took an unconventional path himself: Patrick dropped out after freshman year to start a company, returned to MIT and dropped out again to start Stripe, which makes "is finishing university necessary" a sharper question

Once these three layers of background converge, the real question is: after AI can deliver answers and finished work, which knowledge, reasoning and expressive abilities should a student still make part of themselves, and which can be outsourced to the model

Boundary: Patrick's personal story is not advice to drop out; it only forces the independent value of university learning to be spelled out again

Harj Taggar: Your most impressive achievement I would argue was Croma, your dialect of Lisp.

Patrick Collison: Compilers do it for us. We don’t mourn it too much. And so maybe in the same way we shouldn’t mourn source code.

We should just transcend the plane of instructions to Claude et al. But emotionally, I miss it.

Merged reading: in Harj's view, Patrick's most impressive achievement at the time was Croma, the Lisp dialect he designed. Compilers now do that work for us and we do not mourn it much, so perhaps in the same way we should not mourn the disappearance of source code; we only need to transcend the plane of writing instructions ourselves and hand it to Claude and the rest. Emotionally, though, Patrick misses it

Patrick Collison: My model of this is cache, the C-H, not an S-H, where Jeff Dean has this famous set of numbers that every programmer should know—bandwidths and latencies and just kind of relevant constants that you should reason about as you build systems.

Retrieving something from L1 cache is very different from retrieving from RAM, which is very different from retrieving across the network or whatever.

That’s a hell of a lot slower than knowing it in cognitive L1 cache.

And so I think even granting the full capabilities of the models, I still think there’s a pretty—I think for a long time to come, neuronal lookups will be much faster.

Merged reading: how much should students in this AI world learn and derive from first principles themselves, and how much should they outsource to AI? Patrick's model for this is the computer cache, cache and not cash. Jeff Dean has a famous set of "numbers every programmer should know", including bandwidths, latencies and the constants you have to reason about when building systems. Obviously, when you think about building any system or distributed system, the various lookups between components and their bandwidths differ enormously. Retrieving from L1 cache is very different from retrieving from RAM, which is very different from retrieving across the network. He thinks knowledge works the same way. Of course you can have an agent compute or look something up for you, but querying an agent is much slower than having the knowledge in your own cognitive L1 cache; the number of round trips of thought you can complete in your head is far greater than what you can do by whispering a question into Superwhisper or typing it out. So even granting the models their full capabilities, he still thinks that for a long time to come, neuronal lookups will be much faster

If you look in revealed preference at what companies themselves are doing, whether they’re companies like Stripe or the labs or what have you, there still seems to be an enormous premium on cognitive ability.

I think renouncing that before there’s evidence that we’ve saturated those benefits would be premature.

Merged reading: if you look at the revealed preference of companies like Stripe and the AI labs, that is, at how they actually act, strong cognitive ability still commands an enormous market premium; giving up on training it before there is evidence that we have saturated its benefits would be premature

Patrick Collison: I still write myself. I both philosophically, but also specifically, substantively dislike the writing of the models.

It’s very interesting, right? Because these can prove the Jacobian conjecture, whatever. And so clearly they’re capable of these monumental feats.

But somehow I still haven’t read the LLM essay that I’ve found super compelling.

It’s just very hard to RL in that domain because the utility function or something is kind of hard to define.

But yeah, I think writing is pretty—interpersonal communication and writing I think are so very fundamental and being able to reason sensibly in the multidimensional space of reality.

Merged reading: Patrick still writes himself; both philosophically and specifically, in terms of the substance, he dislikes the models' writing. It is interesting, because these models can do things like prove the Jacobian conjecture and are clearly capable of monumental feats, yet somehow he still has not read an LLM essay he found truly compelling. It may simply be that writing is very hard to optimize with reinforcement learning, because the utility function is hard to define. Still, he thinks writing and interpersonal communication are utterly fundamental; they require a person to reason sensibly in the multidimensional space of reality, and in a way that is hard to describe, he feels the models still fall short there. So he has never sent one of those pre-written suggestions: every tool now tries to offer them, whether Gmail or, reportedly, WhatsApp with a similar new feature, and he thinks he has still never once sent a suggested text in his life

2. The technological revolution is real; that does not mean "if you don't do it now, there will never be another chance"

This node starts from a widespread "last boarding call" anxiety: AI really is changing the world, but is that enough to prove everyone must act immediately or miss the opportunity forever

The anxiety in real life

This is something we hear very often when talking with students today: many of them seem to want to drop out en masse, partly because they worry that right now is the moment they have to seize

I think the meme going around is that if you don’t drop out and start a company and make lots of money, you’re going to be trapped in the permanent underclass.

First split one sentence into two judgments

  1. Technology judgment: AI is a real and major technological revolution that will change companies, work and society
  2. Window judgment: if you do not start a company, learn or get on board right now, every opportunity will permanently disappear in a few years

Even if the first judgment holds, it does not automatically prove the second

"You must do it right now" still needs an extra explanation: what mechanism, exactly, would make the opportunity vanish completely in a few years instead of reappearing in another form

I felt this real sense of urgency, which I think in hindsight was a bit unnecessary.

Merged reading: back then, in what felt like the pre-Cambrian era of startups, startups were far less widely known than today, even on university campuses. Patrick felt a very strong sense of urgency at the time, but looking back, that urgency was a bit unnecessary. Marc Andreessen has also talked about a version of this urge to speed-run life

I thought that a bunch of the opportunities in startups and in Silicon Valley and so forth were ephemeral and fleeting.

In hindsight, I think that was a poor intuition. It’s been pretty robustly and reliably the case over many decades that Silicon Valley has a surfeit of opportunities.

Merged reading: at the time Patrick thought many of the opportunities in startups, Silicon Valley and similar fields were ephemeral and fleeting; if they did not build it right away, three or four years later it might no longer be possible and every opportunity might be gone. In hindsight that was a poor intuition: over many decades it has been robustly and reliably the case that Silicon Valley has a surfeit of opportunities

Humanity has always had an affinity for these millenarian models of how everything will soon come to an end and be this permanent transformation of society and so forth.

Obviously, aviation was a pretty big deal, but I don’t think it was quite the sociological rewriting that some of the excitable proponents at the time imagined.

So it’s hard to predict anything, especially of the future, but I would take the under on this being the last couple of years to create a company.

Merged reading: humanity has always been drawn to millenarian models, the belief that everything as it exists will soon end and society will undergo a permanent, total transformation. There is a very good book called The Winged Gospel: after the airplane was invented, people believed civilization and even the human species were entering a new age in which everything would be completely different. Aviation was obviously a big deal, but it was not the sociological rewriting that the excitable proponents of the time imagined. So anything is hard to predict, especially the future, but on the claim that these are the last couple of years to create a company, Patrick would take the under

3. A startup is not a problem of imagination; it is building a feedback loop with reality

Stripe launched publicly after nearly two years, which on the surface seems to violate lean startup. But what should really be judged is not whether the launch was early, but when the team started letting its core hypotheses be tested by reality

Why Stripe does not look lean

I remember another unusual thing about you at the time: you did your big public launch very late, especially in the YC context, where everyone keeps stressing launch early, launch fast, then iterate in the market

Patrick Collison: We launched publicly September 2011. So almost two years after the first lines of code, after the repo was started.

First separate three concepts

  1. Lean Startup: using the Build → Measure → Learn loop to bring the most critical business hypotheses into contact with reality and correct them as early as possible
  2. MVP: the smallest viable experiment that can test the currently riskiest hypothesis; it can be a small-scale production product, a manual service or a private beta, and is not the same as a complete product for everyone
  3. Public launch: a public move to widen reach; only one means of getting feedback, not lean startup itself

Stripe's public launch was very late, but its learning from reality started very early, so it looks un-lean on the surface while actually running a textbook lean feedback loop

It’s very easy to hallucinate or to imagine some customer problem that’s not actually something viscerally felt by a person who would pay money.

Merged reading: it is very easy to hallucinate a customer problem that is not actually felt viscerally by anyone who would pay money. In building Auctomatic together, they ran into a problem first-hand: moving money and taking payments on the internet was a real pain. On one hand it looked like an obviously good idea, because nobody liked the existing ways of doing it; they were universally disliked, antiquated and full of legacy baggage. You had to fill in paperwork, go to the bank in person, the documents might as well have been written in Latin, and everything about it was terrible

We felt like the proverbial squirrels in a trench coat trying to masquerade as a real business or as serious adults, but obviously knowing nothing coming in about the space.

But I think the fact that it was grounded in such a concrete, actual, real user problem saved us.

Merged reading: they felt like the proverbial squirrels in a trench coat, trying to pass as a real company or as serious adults while obviously knowing nothing about the space when they entered it. The banks and partners did not literally laugh them out of the room, but you could almost see them feeling under the table for the button to call security, because the whole thing looked so implausible. What really saved them was that what they were doing was grounded in a very concrete, actual, real user problem

I think the thing that saved us and meant that it wasn’t a total walk in the wilderness is we had production users almost from the very beginning.

We got our first live production user in January of 2010, so two months into working or whatever. And it did very little. It was very larval and incomplete.

It was very just-in-time development.

Every week we had actual customer feedback, requests, new users coming in; we’re learning things from reality as opposed to our own hypothesized or extrapolated conception of it.

I think if you have a significant stream like that of grounding, it’s probably okay to not be launch, launch.

Merged reading: from the first lines of code to the public launch took nearly two years; had they been going to YC meetings every week, they would have been knocked on the head and told to launch long before. What really saved them and kept the development from becoming a blind walk in the wilderness was that they had real production users almost from the very beginning. In January 2010, about two months into working, they got their first live production user. The product did very little then; it was larval and incomplete. All it could do was charge a credit card. After charging one, Ross asked a very reasonable question: "How do I see all my charges?" So they built a small dashboard. Then he said, "I want to refund a payment", so they added refund support. A few weeks later he asked, "Will I eventually get this money?", which was also reasonable, so they built payouts. It was very much just-in-time development driven by demand. In short, they had production customers very early, and although the product stayed in private beta, the number of customers grew every month right up to the public launch. Every week they had real customer feedback, feature requests and new users coming in; they were learning from reality rather than from their own hypothesized or extrapolated picture of the market. Patrick thinks that as long as you have a significant stream of grounding like that, it is probably fine not to have done the big, capital-L public launch yet

4. Why a startup's starting point needs to be more different in the AI era

As AI makes ordinary software easier and easier to generate, small niches fill up faster with similar products. Founders therefore need to choose starting points less correlated with most people, and enter difficult territory that can form a moat earlier

Why the traditional path is getting more crowded

Buy traffic such as Google ads first, identify a small gap in the market, then iterate and expand from there step by step

I think you can certainly imagine that that becomes much more competitive and much more aggressively tilled, and it’s hard to find those little niches.

The counterintuitive point here

AI lowers development cost, which intuitively seems to favor quickly copying a small product, but the same thing lets large numbers of founders enter similar niches at the same time

Result: product directions that are easy to discover, easy to explain and easy to generate tend to be the ones most correlated with other founders and most prone to homogenization

AI makes starting easier but may make an ordinary starting point less able to yield an advantage, so the starting point needs to be more different

Taking these really divergent starting points where nobody else is trying to occupy that territory is maybe more—basically, maybe you have to more aggressively de-correlate in the era of AI.

Merged reading: traditional lean startup says to buy traffic such as Google ads first, find a small gap in the market, then iterate and expand from there. Today's internet is far larger than it was twenty years ago when these ideas appeared. Perhaps it is more worthwhile to start from genuinely different points, entering territory nobody else is trying to occupy; in short, in the era of AI you may have to de-correlate your choices from everyone else's more aggressively

So many of them are very anti-lean startup, right? Whether it’s the labs themselves or Anduril or you can go down the list, a lot of them have this characteristic.

Whereas now I think you can start these much more aggressive and ambitious things upfront.

Merged reading: many of the successful companies of the past decade are very anti-lean startup, whether the AI labs themselves or Anduril; a lot of them share this characteristic. And now you can start much more aggressive and ambitious things from the outset

Harj Taggar: Within YC and probably the startup world at this point, you’re famous for at least the Paul Graham term, schlep blindness.

Patrick Collison: I think PG latched onto something where there are all these menial tasks, but in the totality of Stripe, I find it so interesting.

Merged reading: within YC, and probably the whole startup world by now, Patrick is famous for what Paul Graham called schlep blindness. At least on the surface, Stripe involves a great deal of tedious grunt work that is presumably not the most intellectually interesting. Patrick thinks PG did latch onto a real phenomenon, that there are all these menial tasks, but taking Stripe as a whole, he finds it fascinating

Every business is an applied theory on how some aspect of the world works or how some market works, or if it’s a new company with a new model, that’s a contrarian thesis on some counterfactual.

Merged reading: 25% of newly formed Delaware corporations are incorporated through Stripe Atlas, after which Stripe can keep working with these companies, hear their feedback and requests, and watch some of them grow into standout successes such as Shopify and OpenAI. Every business is a theory applied to reality, explaining how some aspect of the world or some market works; a new company with a new model is a contrarian thesis about some counterfactual

5. What should a startup do if the big companies also enter the race

The most common worry is "the big company has money, people and compute; if it wants to do this, I am bound to lose". But from a big company having the capability to it actually occupying the market and taking most of the value, there is a long causal chain in between

Why this question is so common

A question that kept coming up here yesterday, and comes up often in YC batches, is people worrying that their startup idea will simply be steamrolled by the big AI labs

Patrick Collison: When we were doing Auctomatic, the question was always for our company and every other company, “What if Google does this?”

Do not jump straight from "can do" to "wins"

  1. Material capability: the big company has the relevant talent, capital, compute, brand and channels
  2. Opportunity recognition: it sees this niche problem and judges the market worth entering
  3. Strategic choice: it is willing to let this opportunity into its limited set of company priorities
  4. Organizational mobilization: it can coordinate teams, budgets, incentives and conflicts with existing businesses
  5. Sustained execution: it is willing to do the product, sales, delivery, compliance and all the tedious details well over the long term
  6. Value capture: customers ultimately choose it, and only then does it truly occupy the market and take most of the value

A big company being able to enter only proves the first link of the chain; it does not prove the last link has already happened

Will rapidly improving AI capabilities do this or will the labs specifically themselves do this?

Merged reading: people worry that their startup idea will be steamrolled by the big AI labs. Would that outcome come from rapidly improving AI capabilities, or from the labs themselves deliberately entering the space

Human organizations are complicated and it’s very hard to aggressively prosecute 100 different priorities and to deal with all the issues and interference that arises among them.

Google has done incredibly well in a bunch of specific places, but it’s not like Google has done all the things, even if in some basic material sense, Google maybe had that ability.

So I’d say that the track record of that is checkered.

Merged reading: when they were doing Auctomatic, the question for their company and every other was always "What if Google does this?" Google at the time seemed almost omnipotent, with huge amounts of top talent and nearly unlimited access to capital, servers and every kind of resource. But human organizations are complicated; it is very hard for one company to aggressively prosecute a hundred different priorities while handling all the issues and interference that arise among them. Google has done incredibly well in many specific areas, but it has not done all the things, even if in some basic material sense it perhaps had the ability. So judging by the historical record, the results of big companies entering these spaces have been checkered

Just literally LLMs will obviate a bunch of, or agentic capabilities will obviate a bunch of specific verticals or tasks or something.

Merged reading: LLMs alone may make a set of specific verticals or tasks unnecessary, and agentic capabilities may directly eliminate the need for some products or tasks

Harj Taggar: Within the YC part of the life cycle, like day zero to 90, it’s really being driven by enterprises willing to buy from startups, which is the new thing. So you can sign these new contracts within the batch.

Merged reading: back when Harj and Patrick were starting out, reaching one million dollars of annualized run-rate revenue quickly was a major achievement. In YC's day zero to day 90, growth is now mainly driven by enterprise customers being more willing to buy from startups, so a company can sign new contracts within the batch. Harj asks whether other factors are also steepening the growth curve, taking companies from 1 to 10 and from 10 to 100

Businesses everywhere are more spring-loaded to adapt and to try new things.

They have a real terror of being left behind with archaic and antiquated ways of operating.

There’s never been a better time for startups to sell and to have their products get adopted at pretty meaningful scale right out of the gate.

Merged reading: businesses everywhere are spring-loaded, more ready than ever to adapt and try new things. They have a real terror of being left far behind with archaic, antiquated ways of operating. People know that maintaining the status quo carries a very high risk, so even though adopting something new is risky, staying on the old path looks quite dangerous too. For startups there has never been a better time to sell, and a product just out of the gate can be adopted by customers at a pretty meaningful scale

There’s a fear that AI is going to be this hegemonic, centralizing, totalizing force where a small number of companies gobble up a very large share of the economy.

I think there are going to be many thousands of winners. Based on the trend lines we can see, I think we are heading towards a more decentralized world and one with more broad-based prosperity.

Merged reading: some fear AI will be a hegemonic, centralizing, totalizing force in which a small number of companies gobble up a very large share of the economy. Many of the companies at the AI frontier have already done extremely well and will surely keep doing so. But Patrick thinks there will be many thousands of winners; based on the trend lines visible today, we are heading toward a more decentralized world with more broadly shared prosperity

The order of judgment worth keeping after reading

  1. First ask whether the problem is real enough that someone would pay
  2. Then choose the smallest way of validating that brings the hypothesis into contact with reality
  3. Separate the public launch from real feedback; do not mistake the means for the goal
  4. Judge whether the product's value will be obviated outright by the next generation of models
  5. Look for technology, data, trust and organizational capability that accumulate over time
  6. Faced with "last chance" and "the big company will do it", take the causal chain apart link by link

Where this reading session finally landed

On learning: AI can outsource answers, but important knowledge still has to enter your own cognitive cache

On action: act seriously, but not in last-window panic

On startups: build a feedback loop with reality as early as possible, and choose problems whose value keeps accumulating after the models get stronger

On competition: do not only ask whether the big company can do it; judge whether it will, whether it can stay focused, and whether the model itself will make the product unnecessary

These notes are not a complete transcript; they include only the source passages actually questioned and turned into judgments in this reading session. The transcript is kept in the podcast notes / podcast transcripts folder