Benedict Evans: evaluation

Transcript context

…This episode is brought to you by our season's presenting sponsor WorkOS. What do OpenAI, Anthropic, Cursor, Vercel, Replit, Sierra, Clay, and hundreds of other winning companies all have in common? They are all powered by WorkOS. If you're building a product for the enterprise, you've felt the pain of integrating single sign-on, Skim, R-back, audit logs, and other features required by large companies. WorkOS turns those deal blockers into drop-in APIs with a modern developer platform built specifically for B2B SaaS. Literally, every startup that I'm an investor in that starts to expand upmarket ends up working with WorkOS, and that's because they are the best. Whether you are a seat stage startup trying to land your first enterprise customer, or a unicorn expanding globally, WorkOS is the fastest path to becoming enterprise ready and unblocking growth. It's essentially Stripe for enterprise features. Visit workos.com to get started or just hit up their Slack where they have actual engineers waiting to answer your questions. Work OS allows you to build faster with delightful APIs, comprehensive docs, and a smooth developer experience. Go to workos.com to make your app enterprise ready today. So, if we're in this 1997 timeline for AI, I know so much of your messages we don't know where it's going exactly at. I don't know, do you have a sense of just the timeline to, okay, now things are going to be radically changing? Where are we in that cycle? You talk about all these different cycles we've been through. How far are we from just like, "Wow, it's all different"? Well, unquestionably, we are already in that moment in software, and then there's a conversation about, well, what does Agentic and AI software development, three separate things that merge together, mean for the future of the software industry? There's one extreme which is no one really believes, which is, "hey, you'll just vibe create your in Stripe." And no one actually believes that, although briefly you don't believe that, but clearly there's a whole bunch of questions about what this means for the software industry, and how much stuff you'll be able to do yourself, or how much more software there will be. And that's one whole conversation. But the other extreme is, if you're in a law firm, this is all very interesting, but how exactly do we use this, and how do we work out how not to be the next story that we've submitted something with hallucinations in it, and how many associates are we going to hire next year? What does this mean for us? One of the analogies I used in the presentation is, imagine you're an accountant seeing the first software spreadsheets in the late '70s, and this is mind-blowing. You change the interest rate here, and all the other numbers change. And it does a week of work for you in like 30 seconds. And we can talk about what that meant for the accounting industry, but clearly if you're an accountant, this is obviously mind-blowing. But if you were a lawyer looking at that, or journalist looking at that, you'd think, "Well, that's very clever and my accountant should see this," but that's not what I do. I might use it for my time sheet next week if it didn't cost 10 or $15,000 to get the Apple 2 and the monitor and the printer to run it, which is what it costs if you adjust replacing. But that's not what I do. And you need Word processor, which actually came very shortly afterwards. And so that's sort of the moment that we're in of, there's some people like software developers are the accountant seeing VisiCalc. "Oh, my God, this changes everything." Before VisiCalc and after VisiCalc, before Claude Code and after Claude Code. A lot of other people are picking it up using it to varying degrees, but slightly puzzled. So, there's a bunch of survey data that I put in the presentation that, even if you look at like 13 to 18 year olds or something, it's still like 15, 20% of people are daily active users, and another 20% are weekly active users. And then the other 60% of those people in that demographic how on you say they are not using this. So, there's a sort of very widespread of who gets it, and a very wide... Which I think also maps, this is kind of almost a separate point, maps to this sort of jagged frontier question of, where does this work? Where does it not work? Can you tell where it's going to work? Is it intuitive to know where it would work? Can you tell after it worked? Can you work out for yourself what you would do with this? And all of those intersect with your software developer. to work? Is it intuitive to know where it would work? Can you tell after it worked? Can you work out for yourself what you would do with this? And all of those intersect with your software developer. There's a lot of other people who are like, people are having a moment or they're not, or again, we're in that kind of 1997 moment of, "Okay, what is this?"…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.