In a hypothetical pitch, the founder has spent twelve years inside the industry she wants to change. She knows who signs the purchase order, why the last vendor was fired, and which spreadsheet will survive every software migration. Our fictional investment committee has concerns. Some of this sounds like employment.
Across the table is a founder who has never worked in that industry. He sees no reason the entire thing cannot be rebuilt by November. We have concerns here too, but they photograph better.
Andrew Yeung’s public discussion of founder age prompted the question behind this essay: why does experience so often arrive in the pitch as something to apologize for? 1 The invented committee is ours. There is no evidence here that a particular investor rejected a particular founder for being old.
The age in the chart is not the age at the exit
The research is less cinematic than the dorm-room story. Azoulay, Jones, Kim and Miranda studied roughly 2.7 million founders of US businesses that hired at least one employee, using historical administrative data. The average founding age was about forty-two; for the fastest-growing one-in-a-thousand ventures, it was forty-five. Founders associated with successful exits were about forty-seven when they started, not when they sold. 23
Those distinctions prevent a very convenient misreading. This is not a finding that every great founder is forty-five, that teenage founders are bad, or that you should wait until your next birthday to start. The sample concerns employer businesses founded in 2007–2014, not all side projects or a census of today’s AI companies. Within the paper’s venture-backed firms in entrepreneurial hubs, the mean founding age was lower, around forty. The same paper contains different populations; a tweet often has room for one.
What the evidence does challenge is the lazy assumption that spectacular growth naturally belongs to the very young. Youth can bring stamina, technical fluency and fewer obligations. Those are real advantages. They are not a substitute for knowing why the customer would pay.
The apparently terrible burden of knowing things
Prior experience in the same industry was associated with stronger outcomes in the study. Its comparisons are observational: experience may travel with networks, financial resources, selection and other advantages. You cannot isolate its causal value by reading a table and issuing yourself twelve years of seniority. 3
Still, the mechanism is easy to imagine without inventing a statistic. A founder who has bought hospital software knows that a convincing demo is not a purchase. Someone who has managed a warehouse knows that a robot can be technically impressive and operationally expensive. A person who has signed a security review knows why “we’ll move fast” does not appear among its accepted answers.
Our experienced fictional founder can tell you which part of the workflow people hate and which part they hate but cannot remove. That second category is useful. It also makes the pitch less clean. The customer has regulatory obligations, switching costs and an existing system that is ugly for reasons.
The inexperienced founder offers a world without those reasons. For the duration of the meeting, everyone is happier.
Knowing the industry can also trap you
Experience has its liabilities. Experts can become attached to inherited constraints, protect old margins, or mistake a familiar process for a law of nature. An outsider may notice that a task has become unnecessary rather than designing a better version of it. Technical shifts can reward people who have not invested their identities in the previous architecture.
That is an argument for testing assumptions, not for treating ignorance as a qualification. Ask the experienced founder which industry convention is now obsolete. Ask the outsider what they learned from customers that forced them to change the product. Either answer can reveal independent thought. Neither is improved by a birthday.
A useful diligence conversation follows an actual buying decision: who experiences the pain, who approves the expense, how implementation works, and what would make the first customer leave. The goal is not to make every founder sound like a procurement officer. It is to find out whether the founder has met one.
The slide we keep out of the deck
Experience is awkward to package because much of its value consists of disasters that do not occur. Nobody applauds the founder who avoids promising a deployment date she cannot meet. There is no launch video for having understood the integration correctly.
The novice’s certainty is visible. The veteran’s judgment often looks like a qualification in the second paragraph. In a market that rewards a clean story, one can be mistaken for conviction and the other for diminished ambition.
Our fictional committee would prefer a visionary unburdened by customer reality. The customer, unfortunately, has asked for a reference.