Bret Taylor
The future of careers, coding, agents, and more, covering product design, team leadership, and product strategy and execution.
Episode
He saved OpenAI, invented the “Like” button, and built Google Maps: Bret Taylor on the future of careers, coding, agents, and more
Summary
Bret Taylor — inventor of Google Maps and the Like button, former co-CEO of Salesforce, and chairman of OpenAI — traces the arc from his first product failure (Google Local) to his conviction that agents and outcomes-based pricing are the inevitable future of software. He explains why agents are fundamentally different: they accomplish jobs autonomously rather than helping someone do a job, making productivity gains measurable and enabling entirely new business models.
Key Takeaways
Agents are the new apps and outcomes-based pricing is the new SaaS model. Sierra charges per 'resolution,' not per seat, because AI can autonomously complete jobs for the first time.
To get real productivity gains from AI coding tools, root-cause every bad output and fix the context gap that caused it (usually via MCP). Treating Cursor as autocomplete misses 80% of the gains.
When building a new product, don't digitize what came before — find the native capability of the new medium. Google Local failed as a digital Yellow Pages; Google Maps succeeded by making the map the canvas.
The biggest mistake first-time founders make is being single-issue voters based on their own skillset — engineers think product fixes everything, business founders think partnerships do.
Study CS, but hold the act of coding loosely. What persists is systems thinking — understanding complexity, architecture, and what's hard — not the keystrokes.
Notable Quotes
“I'm probably out of my depth here, but it's essentially MCP because that's how you provide context to Cursor. And I think that almost always when you have a model making a poor decision, if it's a good model, it's lack of context. And so, you really want to find the intersection of your particular product and code base with the context available to these coding agents and systems and fix it at the root is the principle here.”
“I think that's going to end up this vestige of the past, almost like the human calculators at NASA before the computers were invented, like wow, a person was a calculator? Whoa, that's fun. Tell me that story. I think just what I was good at will no longer be useful in the future or certainly not valuable in the future and that's okay. So I think we need to have a really loose view of it, but the idea that you shouldn't study these disciplines, it's like people say, I don't want to study math because I'm not going to use it in my career for X. Well, studying maths is quite important. It teaches you how to think. It teaches you how the world works, physics, math, and I think computer science especially, at least the foundations of it, will continue to be the foundations of how we build software and understanding that when you're interacting particularly with something that's smarter than you, producing code you might not completely understand how you constrain it and how you get it to produce these outcomes. I think it will require a lot of sophistication actually.”
“There is some risk to the tooling market because it's pretty close to the sun. So, if you look at the infrastructure as a service market and the cloud tooling market like the Confluent and Databricks and Snowflake, a lot of the Amazon and Azure and others have competing products in those areas because they're very adjacent to the infrastructure itself and every infrastructure provider is trying to differentiate by moving up the stack and you're right there.”