"Just validate it with an MVP first." That sentence anchored a decade of product coaching. Today it deserves a pause, because we have entered a period where building the thing is often faster than validating whether to build it.
A Silicon Valley essay titled "The Lean Startup is Dead" made the rounds recently. The argument is simple: lean startup was a methodology built on the premise that building is expensive and slow. A few years ago that held. Engineering was costly, and building the wrong thing hurt. So the sequence made sense — interview, mock up, validate, then build.
That premise broke. Sam Altman has described spending three months coding through the night on his first startup; a coding agent now does equivalent work in seven minutes. In a world where three months became seven minutes, "validate before you build" sounds strange.
The shift shows up at individual scale immediately. A daily-routine tracker that had lived in Notion for years — minimal dark mode, add and remove items from the home screen — went from idea to shipped in a single day. In an in-house setting a few years earlier, the same feature meant research write-ups, Figma mockups and engineering negotiations: several weeks. Those weeks are gone. Validation did not become unnecessary. Building became the fastest form of validation.
One number describes the other side of this. According to RevenueCat, which handles in-app subscription data, AI apps generate revenue faster than typical apps — and lose customers 30% faster. Products built in a day are being abandoned in a day.
Ash Maurya, who created the Lean Canvas, compressed the situation into one line: "The cost of building has collapsed. But the cost of building the wrong thing is exactly the same."
When building is easy, everyone builds, and near-identical products flood the same space. The difference then comes from two places: whose problem you are solving, and why anyone stays after the first visit. In the 1→10 stage, customer understanding and retention are everything — which is precisely what lean startup has argued for fifteen years.
Strategy is where you are going and why. Tactics are how you get there. "Get healthy" is a strategy. "Run every morning" is a tactic. If your knee hurts, you switch running for swimming. Changing the tactic is not abandoning health.
The same confusion is happening to lean startup. Its strategy was "learn from customers so you don't build the wrong thing." Its era-specific tactic was "validate before building," a means fitted to the constraint that development was expensive and slow. AI removed the constraint, so the tactic aged out. The strategy did not. If anything, when anyone can build fast, learning from customers matters more. Eric Ries makes the same distinction: principles persist, but tactics stay bound to the era that produced them.
So the accurate rewrite of "the lean startup is dead" is this: running died, health did not.
In the 0→1 stage, a designer's edge is no longer the hand that draws screens — AI draws them. It moves to the eye that decides what should exist: finding the problem, forming the hypothesis, and instructing AI precisely.
In the 1→10 stage, the most classical skills become scarce again. Talking to users directly, reading churn causes out of data, and designing reasons to stay. The cheaper production gets, the more clearly this work refuses to become free.
The same structure transfers to marketing teams. As the time to produce content, landing pages and ad creative drops, the bottleneck relocates rather than disappears — the pattern documented in AI got faster, so why are we still busy?. The same point runs through 12 career rules for the AI era: when tooling levels out, the remaining difference is the quality of judgment.
Lean startup did not end. The exam scope changed.
Validation did not disappear; its method changed. With build costs collapsed, building has become the fastest form of validation. But as Ash Maurya notes, the cost of building the wrong thing is unchanged — so deciding what to build matters more, not less.
RevenueCat, which handles in-app subscription data, reports that AI apps monetize faster than typical apps but lose customers roughly 30% faster. Speed of production does not translate into retention.
It holds at the tactical layer. Spending weeks validating before building was a workaround for expensive, slow development, and that constraint is gone. The underlying strategy — learn from customers so you don't build the wrong thing — remains valid and arguably more important.
As content, creative and landing page production accelerates, the bottleneck moves from execution to judgment. Defining whose problem you are solving, and designing reasons for acquired users to stay, become the most expensive capabilities on the team.
To apply what you just read to your own site, start with a free audit of where things are now.
A strategist replies within 24 hours on business days.
Waiting at the booth rarely works at B2B trade shows. How to control what you reveal, book meetings in advance, stop passersby cheaply and follow up the same night.
Can employees take prompt libraries built at work when they leave? How U.S. work-for-hire and trade secret law apply to AI prompt ownership, and what firms should do.
Four teams named four different core customers, all based on gut feel. A step-by-step way to define your core customer from repeat behavior and map your beachhead.