Benedict Evans on AI: As Big as the Internet, and Only as Big

Open on YouTube ↗
Overview

Benedict Evans spent years as the in-house analyst at Andreessen Horowitz and has since worked as an independent analyst, publishing a large presentation on technology trends every six months. The latest is titled AI Eats the World. In this conversation with Lenny Rachitsky, the central question is what people still aren't pricing in about AI's effect on work and life. Evans's position is that AI is a fundamental platform shift. It is also one whose outcomes we can barely predict yet, and one that history suggests we will probably come through. His short version is that it will "probably be okay."

31 min read
2:31

"As big a deal as the internet or mobile, and only as big"

Evans opens with what he calls his most controversial opinion: AI is as big a deal as the internet or mobile, and only as big a deal. People in tech who compare it to the industrial revolution push back on the second half. Evans responds that smartphones and the internet were enormous. This conversation couldn't happen without the internet, he notes.

He then pushes the internet comparison further. In his view we are in about 1997. It's very exciting, most things don't really work yet, most of what people will eventually build hasn't been built, and it's unclear how any of it will work once it does. People who have "already taken the pill" tend to assume everyone else is where they are. Evans sees a very wide distribution instead. Some people in tech have bought clusters of Mac minis and stopped using Google. Outside tech, he says, most people who use AI at all use it every week or two.

He describes the uncertainty as fractal. At the top level, AI will change everything, but he doesn't think arguing whether it is 20% or 100% bigger than the internet is productive. At the next level down, questions like whether the model labs have pricing power, whether OpenAI has won, or whether Anthropic is ahead this week look like asking in 1997 whether Excite or Yahoo would win. The answer then was generally neither. One comment on his new presentation said it was "80 slides saying we don't know." Evans calls that slightly facetious but also kind of true.

6:27

The accountant seeing VisiCalc

Asked how far we are from things being radically different, Evans says software development is already in that moment. That raises open questions about the software industry: how much people will build for themselves, and how much more software will exist. Almost nobody, he says, seriously believes you'll just vibe-code your own Stripe.

At the other extreme is a law firm. It finds all this interesting but wants to know how to use it, how to avoid becoming the next story about a filing full of hallucinations, and how many associates to hire next year.

His main analogy is an accountant seeing the first software spreadsheet in the late 1970s. Change the interest rate and every other number updates, doing a week of work in 30 seconds. For an accountant this was mind-blowing. A lawyer or journalist watching the same demo would think it was clever and that their accountant should see it, but it wasn't what they did. They might use it for a timesheet if it didn't cost $10,000–15,000 in today's money to buy the Apple II, monitor and printer. They needed a word processor, which came shortly afterwards. Evans puts software developers in the accountant's position today, with a "before VisiCalc / after VisiCalc" split that he maps to "before Claude Code / after Claude Code." Many others are using AI to varying degrees but remain slightly puzzled.

He cites survey data from the presentation showing that even among 13-to-18-year-olds, roughly 15–20% are daily users and another 20% are weekly users, while about 60% say they don't use it. He links this wide spread to the "jagged frontier": where does it work, can you tell in advance, and can you work out for yourself what to do with it.

9:57

Why the AI labs are investing in consultants

Rachitsky raises a trend Evans has written about. The labs, especially OpenAI and Anthropic, are investing in professional services, consultancies and forward-deployed engineers, even though many expected AI to wipe out consultants.

Evans jokes that a forward-deployed engineer is like an Accenture outsourced developer who works in San Francisco. His serious point is that companies don't keep spare people waiting for big new projects. They don't have idle staff to redesign their stores, figure out where stores should be, or work out why churn is too high. That's why they hire Bain, BCG or McKinsey on one side, Accenture or Infosys on the other, or branding agencies and architecture firms. A company has no reason to keep 15 architects on staff when it can hire a firm.

Reimagining every internal workflow to see what AI could automate is a project in itself: five or ten people for a month or two. Implementing it is another project, involving plugging vertical systems into horizontal ones, building new workflows and training people. Someone has to do that work. Some PE firms provide that support to their portfolio companies, and otherwise companies hire consultants or integrators.

12:41

Is it the task or the job?

This leads to the theme Evans uses to organize the "change" section of his presentation, which also has sections on capital and deployment. Is the hard part of a job writing code line by line, or making the PowerPoint, or is it something else?

Sometimes the task really is the job. Evans lives in a building with a manually operated elevator, driven with a lever by an attendant. Those jobs were automated after the 1950s and replaced by a button. More often, he argues, the relevant dynamic is price elasticity, which is what the Jevons paradox amounts to. When something gets cheaper, do you do the same for less money, more for the same money, or more for more money because new returns open up? He recalls an old joke of his: before Excel, junior investment bankers worked brutal hours, and thanks to Excel, Goldman associates now finish at lunchtime on Fridays. That obviously didn't happen. Similarly, Apple writes something like 90% of an iPhone app's code (modem drivers, graphics drivers, file system), yet we didn't end up with a tenth as many engineers.

His e-commerce analogy makes the same point. Amazon gets you the SKU if you already know which SKU you want. If you don't know which microphone to buy, Amazon probably isn't where you start. Claude Code can write the code, but which code do you want, which features, for which customer, and how will you take it to market? A McKinsey-style 75-slide deck made with Claude is, in his words, a crappy version of the real thing. Even a good one wouldn't be what clients pay for. They pay Bain to walk around the company, understand the politics, work out why something wasn't done, and talk to customers. The PowerPoint is the task, not the job.

He also looks at industries the internet hurt because two things could be separated. Record companies didn't think of themselves as manufacturers of small plastic discs, and newspapers didn't think of themselves as printing and trucking businesses. Once those functions were decoupled, they were in trouble. Often, though, the pieces can't be decoupled, or that wasn't the real problem. His presentation includes charts showing the number of accountants rising through the 20th century and again in the 21st, despite adding machines, punch cards, mainframes, databases, ERP, spreadsheets and cloud software. His conclusion is that it has to be more complicated than automation. Rachitsky adds that even the most advanced AI companies, and companies like Every whose founder Dan Shipper recently appeared on the podcast, are increasing headcount.

18:05

The "job apocalypse" and 200 years of automation

Asked about warnings such as Dario Amodei's that entry-level jobs will disappear, Evans first objects to argument from authority. If you use it, he says, the authority should be relevant. He's interested in Amodei's view of where models will go in the next six to twelve months, but not especially in his theories of labor markets and comparative advantage. Evans says he doesn't believe the cynical view that such statements are just stock pumping.

His substantive argument is historical. Every new technology automates some jobs, and through price elasticity and what it enables, it creates new ones. Around 1800, he says, roughly 90% of people were peasants worried about crop failure. Ever since, we have been automating jobs and creating new ones. You can always see the job that's going away, but not the new one, because it doesn't exist yet and often sounds silly ("railway engineer — what's a railway?"). Each round brings frictional pain: people lose jobs and towns get hollowed out. On the other side, Evans argues, we're all richer. Typesetters, telephone operators and typists largely disappeared, and he says the jobs that vanish usually look like bad jobs in retrospect.

So is AI different? One answer is speed. Evans agrees adoption is faster but attributes it to standing on the shoulders of giants. ChatGPT could reach around 900 million users because that many people were already online. When Marc Andreessen launched Netscape in 1993–94, there were only 50–100 million PCs in the world. Each wave builds on the ones before, so the internet was fast too.

21:17

Why companies won't fire everyone in two weeks

His other answer is about how organizations actually work. He calls the doomers who imagine big companies buying ChatGPT tomorrow and firing their staff two weeks later "morons." In his view their basic failure to understand the world was the starting point of all their other mistakes. Enterprise sales cycles are 18 months if you're lucky, longer than the gap between a startup's funding rounds, and even slower in sectors like aerospace or healthcare. Nobody is going to rip out SAP next week. Over three, five or ten years, sector by sector, the whole landscape may look radically different and jobs will have changed, but it will take that long.

Figuring out what to do with a new technology also takes time. He recalls Frame.io, a video collaboration company a16z looked at, though he concedes it's a weak example because it relied on cutting-edge web technology. His broader point: take ten random SaaS companies founded the day before ChatGPT launched and ask how many could have been founded at any time in the previous 15 years. The delay was someone noticing a problem inside an industry and seeing how to solve it. That didn't all happen the day after Google Docs, and it took 10 to 20 years.

23:30

"Completely different, just like everything else"

Near the end of his deck, Evans has a slide saying roughly that this will be completely different from everything else, just like everything else. It is followed by a 1950s IBM ad showing rows of men in white shirts holding slide rules, with the slogan that an IBM electronic calculator (the word "computer" wasn't used yet) is like having 150 extra engineers. Evans notes that's basically the pitch for Claude Code.

To show how much we forget, he describes making a chart of how many products American supermarkets have stocked since the 1950s. The chart's point is that barcodes let supermarkets track, and therefore stock, far more items. To make it he had to discover that the Food Marketing Institute existed, that it published an annual SKU count, and that it went back to the 1950s. In 1994 you wouldn't have known any of that. You'd have spent days and money on long-distance calls looking for a library that held the reports, or paid the Institute for copies, and two weeks later you might look at the chart and decide it wasn't interesting. For Evans it took two hours on Google. Enormous changes become invisible once they are simply how the world is.

26:06

AGI as a moving target

Rachitsky asks whether AGI or superintelligence is what makes this time different. Evans says he doesn't know. We have no theory of human intelligence, no theory of why these models work so well, and no theory of how much better they'll get, so everyone is "vibes forecasting." He's dismissive of late-night philosophizing about consciousness.

What he thinks can be observed is redefinition. He cites Larry Tesler's line that AI is whatever machines can't do yet, and once they can, it's "just software." People say image recognition or sentiment analysis "isn't AI," in the way jet airliners were once "technology" and now aren't. AGI, in his view, is being redefined to mean what works now, such as doing a certain percentage of economically valuable work. He points out that a 1975 IBM mainframe could do a meaningful share of work previously done by people. He can't tell whether superintelligence now means more or less than AGI, given how the terms have shifted. As with arguments over whether crypto is blockchain or the reverse, there's no correct answer. What matters is being clear about what you mean.

Whether we get human-level intelligence, he says, we have no way of knowing. His serious point is that you don't need to believe any of it. If models stopped improving tomorrow, this would still be an incredibly useful, world-changing technology rolled out over the next decade.

29:48

Bigger markets, and the margin structure of utilities

Rachitsky relays Marc Andreessen's view that companies can now grow far larger than before, with many more trillion-dollar companies to come. Evans ties this to Andreessen's "software is eating the world" thesis: the addressable market keeps growing as software reaches more of the economy. He gives rough install bases for each platform: peak mainframes perhaps 70,000–80,000 units, 50–100 million PCs when the internet took off, perhaps 1–1.5 billion PCs today (maybe 700–800 million consumer), and about 5.5–6 billion smartphones. A few years ago people argued we'd run out of new users. Evans says that was the wrong model, because growth is now coming from automating large new areas of the economy. He compares it to electricity spreading into factories and then into everything.

That comparison leads to his "capital" argument. He quotes Sam Altman saying AI intelligence would be sold on a meter like water or electricity, and responds that someone should explain utility margins to him. TV makers don't pay a share of your bill to the electricity company, and Bosch doesn't pay utilities a cut of each washing machine.

Evans began his career as a telecoms analyst and uses that industry as a warning. By his figures, global mobile revenue is about $1 trillion a year, mobile capex about $200 billion (around $300 billion for all telecoms, 15–20% of revenue), and mobile data consumption is roughly 1,500–2,000 times its 2010 level. Yet the stocks have gone nowhere in 25 years. He describes it as an ex-growth, low-margin commodity utility: an extraordinary piece of infrastructure where all the cool things are built by someone else. The carriers once thought they would build what people did on their phones, and in the end neither they nor Apple did most of it.

34:52

Models versus applications: cloud, not Windows

Evans sees the key question for foundation models as whether the model or chatbot does everything. The "Claude for X" products look to him like Excel's templates under File → New, while the real equivalents are billion-dollar companies. If everything has to be apps, the labs can't build all of them, just as Microsoft didn't. Then the question is whether models have leverage up the stack as Windows did, or whether this looks like AWS. A law firm buying software doesn't care which cloud it runs on, and developers don't standardize on one cloud because customers do.

Crucially, he says, models don't appear to have network effects, so there's no winner-takes-all dynamic and competition should continue indefinitely. Without radical differentiation, why would the labs have pricing power? He expects the result to look more like cloud than Windows, with three to six companies selling a commodity near marginal cost and value accruing further up the stack. He separates today's "radical price disequilibrium" from the eventual steady state. He mentions the OpenClaw developer reportedly spending $1.5 million on tokens in a month and compares it to someone getting a $50,000 mobile data bill in 2010: temporary. He acknowledges semiconductor analysts disagree, admits he is exaggerating their view, and says he looks forward to being proven wrong.

He stresses that this could be completely wrong. Anyone discussing mobile in 2000 would have missed that a "has-been PC company from Cupertino" and a search company would win. As a junior analyst in 1999, he visited a UK dot-com selling computer components online. On the train back from Birmingham, a senior banker, David Tate, summed it up: you can say "dot-com" all you like, it's a low-margin reseller with one-time sales. Evans thinks the labs are in a similar position: lots of science, but so is flat-panel manufacturing, which has won Nobel prizes and is still a low-margin commodity.

Asked what he'd invest in, Evans says he was a poor sell-side analyst, partly because he wasn't interested in share prices. He emphasizes that being right isn't the same as being early, and the right company isn't the same as the right price. Google, Apple, Meta and Amazon face questions but it's hard to see a real problem for them. He points to mobile, where some companies missed the shift entirely, like Yahoo Mail and possibly eBay, while for Google and Amazon little changed and for Meta it was great, with cameras and notifications always on hand. He says he's massively oversimplifying. He cites Steven Sinofsky's observation that incumbents always try to make the new thing a feature, and sometimes they're right.

43:09

Distribution as the moat

Rachitsky raises a recurring theme on the podcast: as software gets easier to build, distribution becomes the key asset, which favors incumbents. Evans agrees, joking with the Drake meme ("I don't like GPT wrappers, I do like harnesses"). If the product is a commodity, distribution is what matters.

His comparison is web browsers. The rendering engine can be better or worse, but the browser product is a thin wrapper around it: an input box and an output box. The last real innovation was tabs 20 to 25 years ago. Microsoft used distribution to win browsers, and then winning browsers turned out not to matter because the value was further up the stack. Today, Evans says, Google is using distribution to push Gemini. A normal user can't tell it apart from ChatGPT. Meta, which people in tech have written off, showed up in survey data between ChatGPT and Gemini even before its newest efforts, because it had "sprayed it on every surface" and the product was adequate. He reads OpenAI's late-2025 strategy of trying many things at once as a search for a flywheel and distribution before Google, Meta and Amazon make their offerings the defaults.

Apple, he says, is the last shoe to drop. Rewatching WWDC 2024, the Apple Intelligence half remains the most compelling vision of a personal AI assistant he has seen: agentic, on-device, tool-using, with no prompt injection or hallucinations and a standardized intent system across 10,000 apps. He isn't surprised Apple couldn't ship it, since nobody else has either. He wants to see what Apple shows at WWDC, possibly powered by Gemini. If so, Gemini-based features on Android and Gemini-powered Apple Intelligence on iOS would be different products, because the model is "the dumb thing underneath" and the product decisions and distribution sit on top. Apple has a billion devices able to run things on-device. Evans mocks Google's recent Android intelligence launch for coming only to its most powerful devices, meaning, as he puts it, "the five people who bought a Pixel phone." He says the launch getting so little attention shows how little people now watch Android.

48:23

The anti-AI backlash: a "big fuzzy mess"

Rachitsky notes surveys showing AI is unpopular, local opposition to data centers, and Eric Schmidt being booed at a commencement speech whenever he mentioned AI. Evans sees a mix of issues with very different merits.

Higher electricity bills are real, he says, though only in a small number of places. The water argument he calls essentially fake. Data centers mostly use closed-loop cooling, and he cites a Livermore lab study from late 2024 estimating US data-center water use at about 0.017% of national consumption. If a small town's single well is handed to a data center, that's a planning problem, not a data-center problem. By his estimate, data centers use about 5% of US energy and might grow by about one percentage point a year.

On jobs, he says economists don't know yet. Some charts suggest an effect and others don't. Employment of 18-to-24-year-olds has slowed, but apparently similarly for people with and without degrees, and in fields that look exposed to AI and fields that don't. He also points to a broader lack of data. The labs give no meaningful usage figures, not even a daily active user number for ChatGPT, which he calls "crazy." So evidence comes from academics working through BLS surveys and from consultancies and agencies surveying 20,000 people. Politically, though, none of that matters to a student who can't find a job, whatever the cause.

There are also narrower fights. Evans is, by his own admission, deliberately unkind about illustrators of young-adult romance covers upset that such images can now be generated. He also mentions culture wars among novelists and ebook writers, "AI slop," and the figure that 30–40% of new podcasts are AI-generated. He compares all this to the social media backlash, compressed in time: some true, some partly true, some false. His example of the false category is the belief that "Facebook sells your data," which he calls untrue but firmly held, invoking Jonathan Swift's line about not being able to reason someone out of a position they didn't reason themselves into. He doesn't think Trump's proposed executive order on dangerous models, driven by concerns like cyber risk, is what drives the Main Street backlash.

55:11

Every technology gives new ways to ruin lives

Evans attributes his calm partly to being British and says someone from Iran might feel differently. His view is that every technology brings change we need to worry about, and that this is constant. He recalls a wave of late-1970s books panicking about databases, half of which was true. Putting all police and government records online really was different.

He doesn't dismiss the harms. On deepfake nudes, the dumb response is "haven't you heard of Photoshop?" A 15-year-old couldn't use Photoshop to make explicit images of every girl in their school and send them around in an afternoon, and now they can. Social media promised that the only gay kid in a village could find their tribe, but so could the only Nazi or pedophile. Connecting everyone connected all the bad people and our worst instincts, and he expects AI to produce its own versions of this.

His cautionary example is the UK Post Office scandal. Post offices are mostly franchises run by small business owners, often second-generation Indian immigrants running pharmacies. A Fujitsu-built point-of-sale system had bugs that showed cash shortfalls. The Post Office treated them as theft. Hundreds went to prison, there were suicides and bankruptcies, and people lost their homes, while Post Office and Fujitsu staff testified that the system had no bugs. Evans calls it essentially 1970s technology. His lesson is that every wave of technology can ruin lives, deliberately (he cites Chinese mass surveillance) or accidentally, and we need to be conscious of that without panicking.

Kids and careers

On parenting, Evans says it depends on timing. A child entering the job market in the next year or two faces a situation where everything is up in the air. In five years, things will probably have settled down in unpredictable ways. His son is in his early teens. Many questions predate ChatGPT: the collapse of gatekeepers, trusting TikTok influencers, where you get your understanding of world events. Quoting George Carlin's line about drivers (anyone slower is an idiot, anyone faster is a maniac), he says every parent thinks they're in the middle. He has no systematic plan and would settle for his son not breaking his Chromebook again.

He won't name jobs to steer toward or away from, noting his own path from equity analyst to industry to consulting. His only framework is to find the intersection of skills you have, work those skills make you good at, and things people will pay for, and to get at least two of the three.

59:28

The question not enough people ask

Asked what question is under-asked, Evans names two. First, whether model labs will have pricing power, which he thinks many simply assume. Second, the task-versus-job question and how it plays out. He ends his deck with global recorded music revenue, which follows a U shape. It roughly halved from 2000 to about 2015, then recovered to about 75% of the inflation-adjusted peak thanks to streaming. The first half answers "what if I don't have to pay $15 for a CD to get that track?" The second answers a different question: "what if $15 a month gets you all the music there is?" New technologies start by doing the old thing, more of it, in a new place, like putting Flickr on mobile or printing out emails. Then they enable things only possible with the new technology, and eventually they redefine the question. Spotify isn't an online music store. You often only know what the question was after someone has built the billion-dollar answer, and Spotify, Uber and Airbnb all looked crazy at first.

Rachitsky notes that coding, once thought the last profession to be automated, has been transformed first. Evans uses this to criticize efforts built on the US government's O*NET dataset that score each occupation as X% exposed to AI. He calls them "deluded horseshit" for two reasons. First, it repeats the expert-systems mistake: you can't decompose a senior law partner into "17% automatable" any more than you could build a cat detector from 700 hand-written steps. Second, exposure is inherently unpredictable. In 1997 people said newspapers would benefit from lower printing bills and taxis had nothing to do with the internet. He recently saw personal trainers listed as unaffected by AI, then imagines propping up a phone and having an AI design a routine and correct his form. He concedes that might be nonsense, but that's the point.

Impact also varies. Uber, in Evans's telling, demolished the taxi business in many cities while making it much bigger. Airbnb's effect on hotels, by the numbers, is marginal: it created a separate business and perhaps slowed hotel growth. His wife flies to Milwaukee next week, arrives at 8 p.m., wants room service and a gym at 6 a.m., and drives to a client at 7. There's no chance she'll stay in an Airbnb, and half of hotel demand is business travel. Someone once complained that Evans's answer to everything is "it depends." He agrees that it does.

1:06:32

What to do about it

Evans first qualifies the reassurance. As Keynes said, in the long run we're all dead, and averages hide individuals: nobody died in World War I "on average," but a 19-year-old in 1914 had perhaps a one-in-three chance of not coming back. For associates and people hoping to become associates, the future of the professional-services pyramid is very unclear.

His only advice is not to bury your head in the sand. Declaring that you hate AI gives you a feeling of moral superiority and lets you shout on Bluesky about how evil it is. He says he's happy for you, but it won't help. What helps is immersing yourself, understanding what you can do with the technology and how it changes things, and figuring out how to be a great hire. That might still not be enough. But if a law firm is cutting associate hiring from 100 to 50, announcing in the interview that you'll never use AI is probably the wrong approach. He compares it to how he and Rachitsky had to absorb mobile and the internet.

"I'm the lawyer looking at ChatGPT"

Asked how he uses AI, Evans says he struggles with the question because he's in the lawyer's position. What he'd want automated is precise information retrieval, which he says is what AI is currently worst at. He calls that an observation, not a criticism. He uses it for proofreading, images, and redecorating his apartment, where it worked "fantastically well": repaint this room, add this light and table and rug, change the rug's color. He quotes someone's line that AI is good at what computers are bad at and bad at what computers are good at. He acknowledges that his job, synthesizing large amounts of material into new ideas at a desk all day, is unusual.

Rachitsky mentions a Pete Holmes joke that we wanted AI to clean the streets and instead it wants to make art. Evans says the general desire is for AI to do the boring things, not the fun ones. He links this to his view that a chatbot is a blank screen with a jagged edge, and the fix is wrapping it in use cases. Part of it is AI disappearing into things. He dictates most of his writing as voice memos transcribed automatically by the iPhone's built-in Notes app. He wonders whether that's still AI or just voice recognition. There's probably an LLM in there, he says, but at some point it's just automation.

He also notes that consumer AI has no breakout apps yet. He thinks the main reason is marginal cost: you can't make an app free, reach 50 million users, and then find a business model.

Convergence, and pushing past what you already know

In the lightning round, Evans recommends Jerome K. Jerome's Three Men in a Boat, which he treats as having a story for every situation. He also recommends William Cronon's Nature's Metropolis, a history of Chicago that he says reads like a book about broadband: standardization, logistics, channel conflict, network neutrality, and the point at which it became cheaper to ship cattle from New York to Chicago for slaughter and back than to slaughter them in New York. He urges tech people to read books other than The Lord of the Rings. He recently watched The Seventh Seal and found it brilliant.

He owns 20 or 30 old phones, including an Ericsson from around 1998 and Japanese phones from 2001 with a color screen and a camera, which clients lined up to see and which still charge. Before the iPhone, he says, phone design varied wildly, like cars before wind tunnels, because everyone was differentiating around a tiny gray screen. People imagined some would carry pocket PCs, some keyboards, some folding devices, and nobody expected convergence on one form.

Asked for a motto, Evans offers "it depends," then "it'll probably be okay." Rachitsky notes the "probably." He closes by describing his own challenge: the moment you really understand something is the moment you have to move on. He thinks he spent too much of last year insisting that models still hallucinate, which they do if you push them a little. But that doesn't mean they aren't useful, and the task he sets himself is to keep asking different questions.