Steve Blank: The World Outside The Classroom Changed, The Class Didn’t 

15 years after designing his Lean LaunchPad class, Steve Blank looks outside the classroom at how AI has upended venture capital, product development & customer adoption. Third of 4 parts

Lean startup evangelist and Lean LaunchPad pioneer Steve Blank: “While we need to teach founders to ‘think deeply,’ we also need to teach them ‘to act quickly’”

Editor’s note: Third of a four-part series. Read part 1, The Year AI Came For Us: Teaching Entrepreneurship Will Never Be The Same; and part 2, AI Killed The MVP – Long Live The IUP. Part 4 will be published October 1. For more about Steve Blank and Lean LaunchPad, read The Man Who Disrupted Entrepreneurship Education Says AI Just Disrupted Him.

The Lean LaunchPad has successfully accommodated 15 years of evolution of technology and markets – until now. AI is not only changing our classroom; it is changing everything outside the classroom.

I needed to understand those external changes so the class could change with it. 

The class I designed in 2011 focused on teaching founders how to understand a company’s entire business model, not just the product features and customers. However, there were four important elements outside a classroom or a startup that would affect its success. 

  • Venture capital (how much startups could raise, when they could raise and who they could raise it from)
  • How startups built their products (core tech platforms and development tools) 
  • The cost of building products (time to market, team size, capital requirements) 
  • Customer Adoption (how did they evaluate, buy, deploy and use products. And the speed in which they did that. And customer build versus buy criteria.)

The Lean LaunchPad class was designed to teach founders to use Lean Methods to derisk their new ventures — all while emulating the speed and tempo of 2011 startups. 

The sidebar below summarizes what each of those types of companies looked like in 2011 compared to 2026. Skip this if you have a good memory. The bottom line is that the world is a very different place and operates at a different pace from when I first designed the class, changes that AI has dramatically accelerated.  

The 2011 World For Startups The 2026 World For Startups
Startups overall
·       AWS had just made computing into a utility; the cloud lowered the cost of starting a company.

·       Agile was replacing Waterfall with short releases, customer feedback, pivots, but teams still assembled much of the application, deployment, monitoring, analytics and integration stack themselves.

·       Startups failed by building something nobody wanted. The limiting resources were engineering capacity and cash burn.

·       Agile is disappearing, iterating the product is faster than the sprint cadence it was built to manage. AI agents write most of the code; a spec becomes a working product in days.

·       Creation is now cheap and everyone has the same leverage. What is scarce: attention and distribution, proprietary data and workflow depth, production capacity, and the evidence regulators, clinicians and payers will accept.

·       In Life Sciences the lab compressed; the clinic didn’t.

Enterprise software
·       Selling seats. 12–18 months in one- or two-week sprints; engineers hand-wrote the code, tests, docs and deployment scripts.

·       At product/market fit: 15–30 people, most of them engineers, burning $5M – $10M a year.

·       Priced as annual seat licenses; customers tolerated long implementation cycles because everyone did.

·       Moat: the time it took to write the code, plus switching costs, sales relationships and ecosystem.

·       Seed rounds, new and small ($500K–$1.5M from the first micro-VCs), gated on a working product, reference customers and a repeatable, scalable enterprise-sales model.

·       Selling work/outcomes. Teams of 3-10 reach revenue that used to take 50; $1M revenue per employee is a real benchmark.

·       Funding went barbell: bootstrap to revenue or raise $50M for compute and distribution. Nobody raises for engineering headcount (deep tech and biotech excepted).

·       AI redefined unit economics. Inference costs have shifted, margins are pressured, pricing playbooks are failing; founders run product-led growth and enterprise sales at once.

·       Buyers expect workflows automated and compressed; they design-partner, pilot in days and pay for outcomes rather than seats. The product is increasingly an agent doing part of a workflow.

·       Discovery now asks, What is the job, the cost per completed unit of work? Who defines “done correctly,”? What errors are tolerable, which systems and data an agent touches, which approvals stay? How are decisions audited? Who owns governance, which budget pays, how many humans stay in the loop?

·       Defensible Moat: proprietary data, workflow depth, distribution, access rights, a calibrated eval set, moats of integration, data, compliance, reliability, brand, regulatory evidence, deployment learning — not the code.

Consumer software
·       The iPhone 4S had just shipped; the app store revolution was just starting to take off.

·       5–10 people could design, build and market a polished app in 3–9 months.

·       App stores, Facebook, rankings and press were new enough to earn meaningful organic distribution. Growth hacking and A/B testing were emerging crafts.

·       Monetization deferred for years while investors funded user growth. Instagram was the poster child; VC flocked to B-to-C.

·       Creation is cheap, attention is hard. The Instagram outcome is the expectation: 1–5 person teams reach millions of users, solo founders run eight-figure ARR, AI generates the product and the growth loops.

·       The catch: thousands of AI-built lookalikes launch every week, users compare every interface to a frontier chatbot, retention and loyalty are zero.

·       Discovery means mass creation and testing of problem framings, value propositions, onboarding flows and distribution hypotheses — a full-stack machine to test product, acquisition and retention.

·       “Users now, money later” is no longer funded outside genuine network-effect bets; revenue is expected almost immediately.

·       What survives: network effects, brand, taste. Everything else can be cloned in a weekend and will be.

Hardware
·       Hardware was a category VCs avoided. It required physical prototypes, tooling, manufacturing bets, long supply chains: 25-100 people and 12-36 months before the first customer ship.

·       Simulation sat at the end as verification; truth came from physical prototypes. A failed prototype meant new parts, revised tooling and another 12-week China tooling cycle. Build, test, break, rebuild.

·       CAE tools were $30K–$50K a seat and outsourced if done at all. Nothing resembling a digital twin.

·       Simulation is moving to the front. AI-assisted design, simulation, digital twins and software-defined hardware get a team of 10-30 to the first article; AI works through CAD alternatives, test plans, suppliers and failure modes before committing to tooling.

·       The physical world still imposes truth: a simulation is a hypothesis, not a shipment. In 2011 a simulation explained why a prototype broke; in 2026 the prototype tests whether the simulation was right.

·       Money flows to defense and dual use. Working out of the box is table stakes; hardware is judged on its software, improved over the air; the Department of War demands commercial iteration speed.

·       Moats: deployment data, accreditation, production capacity. Building at scale is scarce again.

Therapeutics / Life sciences
·       It took 10 years to get to the clinic. Startups would license an asset out of academia (small molecules, antibodies); build a screen, find hits, nominate a lead, then developability, PK/PD, tox, formulation and manufacturing controls.

·       Decisions ran on small datasets and repeated wet-lab experiments, in sequential handoffs from biology to chemistry to preclinical to clinical.

·       12-25 core employees; animal studies, manufacturing and trials outsourced to CROs and CMOs.

·       A handful of specialist life-science VCs, milestone-gated Series A. Built to license or sell — the IPO window had been shut since 2008.

·       The lab compressed, the clinic didn’t. Foundation models, in-silico screens and simulation do in weeks what the wet-lab loop took years; sequential handoffs collapse into iterative loops run in software.

·       Not compressed: wet-lab validation, clinically meaningful endpoints, representative data, safety evidence, regulatory review. Trials, regulators, payers and reimbursement run on institutional clock speed. China now owns more than 50% of drug development.

·       When candidates are cheap and trials are not, the scarce skill is choosing the endpoint, indication and evidence package a regulator will accept, a clinician will act on and a payer will pay for.

·       Discovery of stakeholders matters more than discovery in the lab.

Medical devices
·       The FDA was the bottleneck. 12-25 core people, 18-36 months or longer: user needs, requirements, CAD, breadboards, prototypes, bench tests, V&V, clinical work, manufacturing transfer, on a 510(k), De Novo or PMA path.

·       Firmware embedded and deterministic; connectivity a secondary feature.

·       FDA slow and unpredictable, so startups went to Europe first; US approval followed years later.

·       Device VC was fleeing over regulatory and reimbursement risk; 5-7 years to meaningful revenue.

·       Critical transition: from a prototype that worked once to a manufacturable device that works repeatedly.

·       Reimbursement is the new bottleneck. Regulation governs the device lifecycle; cybersecurity is required; simulation crossed from design aid to regulatory evidence.

·       Raising money, hitting a 510(k), selling to a strategic all has gotten harder. Clearance is no longer the constraint, payment is. 

·       TCET covers roughly five breakthrough devices a year; automatic Medicare coverage was never implemented.

·       FDA PCCP allows AI-enabled medical devices to receive updates without requiring a new marketing resubmission.

·       You can clear an AI device relatively cheaply and still have no payment mechanism. Early-stage device funding is really hard.

·       For Lean LaunchPad: in regulated markets evidence is part of the product. Discover what each stakeholder accepts as proof before optimizing the thing being proved.

Looking at this comparison several things jump out:

  • Bottlenecks for adoption and scale still exist, they’ve just moved elsewhere.
  • Product/Market fit needs market-specific targeted end points
  • Customers are willing to be design partners
  • Finding defensible moats is critical

PRODUCT/MARKET FIT NEEDS SPECIFIC TARGETS

When I looked at this table it struck me that for 15 years, we used the term “product/market fit” as a one-size-fits-all phrase to describe the intersection between Stakeholders and the product features they needed/wanted. It managed to cover end users, influencers, recommenders, requirements writers, regulators, etc. across deep tech, life science, defense. Up until now it worked well enough. 

Today, product/market fit is evolving. In enterprise software it is becoming Agent/Outcome fit; in hardware, digital twins and physical-world models; in life sciences, computationally tested endpoints. When we next teach the class, we will replace generic product/market fit with category-specific evidence: outcome/agent fit for enterprise, mass creation and testing for consumer, digital-twin-to-physical fit for hardware, endpoint clinical evidence fit for life sciences, and testing with standardized or validated external assessments for education.

AI ENABLES FASTER TIME TO MARKET

While we need to teach founders to “think deeply,” we also need to teach them “to act quickly.”

To do that, the second half of the class will ask teams to acquire one or more Design Partners as evidence of Customer Validation. A Design Partner is a co-developer who first provides feedback, data, workflow access, and real-world testing in exchange for early access, preferential terms, or influence over the product. The partner commits scarce resources: staff time, data, integration effort, permissions, test environments, changes to workflow and the ability to influence the product. 

In Part 4, we’ll look at how all the pieces fit together to create a new Lean LaunchPad Course design.


Entrepreneur-turned-educator Steve Blank is an adjunct professor at Stanford University and co-founder of the Gordian Knot Center for National Security Innovation. He has been described as the Father of Modern Entrepreneurship. Credited with launching the Lean Startup movement and the curriculums for the National Science Foundation Innovation Corps and Hacking for Defense and Diplomacy, he’s changed how startups are built; how entrepreneurship is taught; how science is commercialized; and how companies and the government innovate. Read his blog here.