Bret Taylor - The Agent Era - [Invest Like the Best, EP.386]｜Invest Like the Best with Patrick O'Shaughnessy

This episode is brought to you by Ridgeline.

During my days at O 'Shaughnessy Asset Management, I was dying for a product like Ridgeline, a single cloud platform that could power our entire firm.

We once spent years on an operational project with the goal of getting our traders set up earlier in the morning.

It was grueling and incredibly impactful, but it took years.

If Ridgeline had been around then, our problem would have been solved instantly, and Ridgeline would have provided an even better solution than the one we came up with.

Ridgeline has solutions to not just save time, but to open more opportunities to make money.

With real -time visibility into positions, outstanding trades, and the cash balances, you have an intraday book of records.

That means less cash drag and more opportunity to drive alpha.

In their first month, Ridgeline enabled the customer to deploy $27 million in cash that would have otherwise remained uninvested.

By collecting data from various systems and consolidating into one place, Ridgeline simplifies the process.

Trade settlements happen faster, and therefore your team can put money to work faster.

I'm confident in saying that if you run an investment firm, you should find time to speak with them to be sure you're positioned to perform to the best of your firm's abilities.

To learn more, check out ridgelineapps .com.

That's ridgelineapps .com, or click the link in the show notes.

This episode is brought to you by Teagus, where we're changing the game in investment research.

Step away from outdated, inefficient methods and into the future with our platform, proudly hosting over 100 ,000 transcripts, with over 25 ,000 transcripts added just this year alone.

What sets Teagus apart?

It's not just the sheer volume, it's the unmatched speed at which our library expands, consistently outstripping competitors.

Our platform grows eight times faster and adds twice as much monthly content as our competitors, putting us at the forefront of the industry.

Our collection is investor -led, ensuring unparalleled quality and giving you access to questions and topics investors care most about.

Plus, with 75 % of private market transcripts available exclusively on Teagus, we offer insights you can't find elsewhere.

Forget the traditional way of doing things.

With Teagus, you have the most comprehensive, insightful and rapidly growing transcript library at your fingertips.

See the difference that a vast, quality -driven transcript library makes.

Unlock your free trial at teagus .com -slash -patrick.

Hello and welcome, everyone.

I'm Patrick O 'Shaughnessy, and this is Invest Like the Best.

This show is an open -ended exploration of markets, ideas, stories and strategies that will help you better invest both your time and your money.

Invest Like the Best is part of the Colossus family of podcasts, and you can access all our podcasts, including edited transcripts, show notes and other resources to keep learning at joincolossus .com.

Patrick O 'Shaughnessy is the CEO of Positive Some.

All opinions expressed by Patrick and podcast guests are solely their own opinions and do not reflect the opinion of Positive Some.

This podcast is for informational purposes only and should not be relied upon as a basis for investment decisions.

Clients of Positive Some may maintain positions in the securities discussed in this podcast.

To learn more, visit psum .vc.

My guest today is Brett Taylor.

Brett's resume is absurd.

He built Google Maps, famously rewriting the whole thing in a weekend.

He was the CTO of Facebook in critical years.

He founded Quip. He was the chair of the board at Twitter.

He was the co -CEO of Salesforce.

The incredible list goes on.

Now, Brett is the co -founder of Sierra, a conversational AI platform for business.

And he is the chairman of the board at OpenAI.

Together, we discuss the past, present and future of AI agents.

New programs that will begin doing incredible amounts of work for us humans in astonishing ways that are a thrill to consider.

Brett believes agents will become a meaningful part of the future and transform the ways in which we interact with technology.

We discuss a strategic approach to AI integration, the different categories of agents and their scopes and the essentials of craftsmanship.

This is a must listen with one of the great builders of our time.

Please enjoy this discussion with Brett Taylor.

Okay, Brett, so I thought of an unusual place to start with a very strange topic that probably most people won't know about, but I promise it will set the stage for many of my questions.

Can you explain the concept of the mythical man -moth?

So it's called mythical man -moth.

And it's essentially the myth that I think stereotypically a lot of folks who come from, I'll say a business school background as opposed to computer science background have about software, which is to make a software development project go faster, you should add more people to it.

And often the inverse is true.

In fact, there's some proverbial statements.

If you want to make a software project go twice, slowly add another person to it.

I think it's that truism I think is based on, I think when you're designing a very complex system, it's often individual engineers who have a system mapped out in their head that is very intricate.

And similarly, when you have really high functioning teams, whether it's early teams I worked on like Google maps or some of the folks designing some of these very powerful AI systems right now, small teams who are completing each other's sentences, so to speak, and own parts of the system and really

understand it and work in unison is a very magical and fragile team dynamic.

And adding more people often requires you add a lot more process, you add a lot more bureaucracy, you disempower some of the most advanced technologists on the team and can broadly speaking just slow things down.

And so whether you look at projects like healthcare .gov that had a billion people working on it and went very slowly, or just the classic software projects that most companies that take twice as long and cost twice as much, that's the idea of the mythical man month.

And I would say it's broadly true though, like all rules of thumb, it's just a rule of thumb and every situation is different.

And do you think that the primary reason that it's an interesting heuristic is this idea that you need to have a systems understanding or an architect's almost understanding of a system to be able to move really fast to change it or build it.

Is that the thing behind the thing that fewer people are able to keep that model in their head?

And if you start to distribute that, you lose that benefit of speed?

I think it's a few things.

So if you have a small accountable empowered team, often it means they understand the customer problem they're solving precisely, i .e.

you're not just implementing a piece of code, you're actually delivering a solution to a problem.

And I think when you have hundreds of people working on a project, often the part of the problem that you're staring at is so narrow, often you lose sight of the forest for the trees and that's part of it.

I think similarly, when you have lots of people working on a project, it requires a lot of upfront planning about how you might architect the solution just to accommodate the 100 plus people.

Imagine, let's say you're cooking dinner and you have a hundred people in the kitchen and you need to put them all to work, you're slicing the carrots, do the carrot slicer, that's your job.

But probably you have no idea what the meal is that you're producing.

But in particular, if you get in the middle of that dinner production and you realize you're doing it wrong, making changes is quite difficult as well.

And so I think that you have this combination of individuals on the team having a very narrow view of what they're doing and why, which is problematic for a variety of obvious reasons.

You end up with less agility because of just the natural overhead of coordinating between all those people and the act of needing to coordinate requires so much upfront planning that you end up with a lack of agility as well when you encounter new information either.

Maybe it's not working as well as you thought technically maybe a new customer requirement comes in.

Probably a combination of all those things and just the natural bureaucracy that comes with larger teams.

You need product managers and engineering managers and this and that and the other thing.

Whereas if you have what I think Amazon called the two pizza box team, you reduce the need for a lot of that overhead and you get a lot of those other benefits where hopefully in a smaller team, most people understand why they're doing what they're doing, not just what they're doing, which is quite

empowering and important because it enables a sophisticated engineer to find the shortcuts that he or she might not know are okay to take without knowing the actual solution that they're delivering.

And more importantly, it just enables agility.

And I think that most big systems, engineering is the act of taking science and applying it to reality.

And so much of engineering is that moment when your system meets reality, whether it's a rocket ship or a piece of software and you really need accountable high frequency decision making to make that successful.

Just to nail home this point, because I think agents, one of the things they'll do probably is enhance the power of the most powerful engineers, maybe by scary amounts, and I won't ask you about that, but just to give the people in the audience a sense of one of these stories in situ.

Everyone I ask about you brings up the Google Maps legendary rewrite story early in your career.

And it just seems like such a fun opportunity to ask you to tell us the long version of that story, bring us into the room, the context around what happened, what you did, but then explain literally what was going on, what made it possible to do something at that scale so quickly with such a small group?

Yeah, I'll start with where Google Maps came from and then talk about that rewrite story, which is, I don't know how that made the rounds on social media, but it was pretty funny.

Google Maps was a small team.

The engineering leaders were Lars and Jens Rasmussen, two Danish brothers who had started a company called Wear2 Technologies that Google had aqua -hired that had built a Windows app called Expedition, which was a really cool installable Windows app a little bit like Google Earth, but rather than being

3D mapping, it was 3D imagery.

It was just mapping.

In the process of onboarding them to Google, we had made prototypes of taking that Expedition product experience and making it work in a web browser.

And at the time, it was mind -blowingly hard.

Just for context, I'm not sure how many listeners were alive or using the internet in 2004, 2005, but most web pages were static web pages.

Google search results were 10 blue links.

Probably the most advanced web applications at the time was probably Gmail, which had launched in the middle of 2004, and a couple of products like Google Suggest, which would auto -complete as you typed, and that was the most advanced thing you had.

In trying to take this Windows application and making it work in a web browser, you could actually drag the map, click your mouse, and drag left and see the map move, which seems so simple now, but it was the first time you really had anything that interactive inside of a web browser.

Though a lot of the engineering of Google Maps was encountering the contours of what was possible in a web browser, we would crash Firefox and Internet Explorer like it was going out of style.

Luckily, a number of members of the Firefox team had actually started working at Google at the time so we could walk upstairs and building 43, I think it was, and be like, can you load Firefox in the debugger and tell us what the hell is going on here?

We'd figure out what was going on, and couldn't go back in time and patch the browser, but they'd figure out what was going on so we could work around it.

So by the time we had launched Google Maps and then subsequently added satellite imagery to it, we launched in February of 2005 and added satellite imagery in August if I'm remembering correctly.

It was just the code base was this accumulation of hard -won lessons, almost like you had started with a house that was just like a living room and added bedrooms and kitchens and different remodel stages.

And each one of them was just banging our head against the wall and trying to figure out this technical problem and like this code base had turned into this total mess.

And it was in part because we had no idea what we were doing at any stage of the project because we were literally doing research about how to actually make all of this work properly.

It sort of reached a breaking point where we were trying to get, at least this is my memory, it might be embellished through the lens of bad memory and history, but we were trying to get it work well in Safari, which was at that point a nascent web browser.

Safari has become more important because of mobile phones, but it was just a new browser on the Mac.

Half the hacks that we had just weren't working properly there.

And the messiness of that code base and all of the lessons and it was overusing XML, which was super trendy at the time, good riddance.

I don't think anyone would use it for most web things today.

It was very clear that we were building on a really crappy foundation.

I ended up with the benefit of having experienced all the hard -won lessons from the whatever six months or so we had been working on it.

I just rewrote it and I rewrote it with all the knowledge that we had accumulated.

I think the story is a little bit overblown.

I did rewrite it, but it was based on all the lessons I had learned.

So I was just like, I took all the lessons that the team had collectively learned in that time.

And I basically said, if I knew all this at the beginning, here's how I would architect the system.

And I think I would have had the benefit of having been a part of all the mistakes that we had made up to that point and the benefit of those lessons.

And I think had the luxury of starting from a blank sheet of paper with all those lessons.

And the main goal at the time was to get the bundle size, which is the size of the JavaScript your browser would have to download before showing a map down.

We got it down to like 20K uncompressed, which is pretty impressive in this day and age.

And in particular, got it working really reliably on all these different browsers.

And there was mainly just trying to get the product to grow more rapidly, but it was largely because you just don't know what you don't know at the beginning of a project.

And going back to your original question on the Mythical Man Month, if you have to go through a committee to talk about rethinking something, you'll never get it done.

And when you had this small team who with a really clear objective and some empowered people in this case, I was pretty empowered, you can do that.

It's such an interesting story because I think it becomes ultra relevant in today's world.

And you hear a lot about this, maybe the Mythical 10X engineer, 100X engineer, 1000X engineer, the leverage available to one person with a growing toolkit.

And maybe that's a great excuse to bridge the conversation into agents.

I think everyone listening will have heard that term, maybe have thought about it a little bit, have gotten excited about the prospect of some sort of autonomous agent doing work on their behalf or their company's behalf.

But it would be great for you to ground us in your definition of what one of these things is.

If this becomes a really critical part of the world of technology in the next year or two, I think it'd be great for everyone just to have a level set, simple definition from your perspective on what an agent is and does.

I'll start with maybe the academic flavor of this, but then I'll move into what I think is maybe the more, what I believe is the more relevant definition, but agent is like the word app.

There's not one definition, and I think it will be a noun that is quite meaningful in the age of AI.

The word agent in the context of AI comes from the word agency and essentially is a system that can reason and take action autonomously as the way I think about it.

And a system that is agentic is one where software and AI can reason and make decisions and take action without human intervention, which is really exciting.

It's something that is relatively new, though the idea is certainly not new.

I think the effectiveness of reasoning with AI systems has become so meaningfully better over the past couple years that I think the concept is, like many parts of AI, the ideas are not new, but the effectiveness is, and so we're living in era of agents now.

In practice, I think the word agent, just like the word app or site in the age of the web, will become important to all of us.

So one agent that I think is important is what my company, Sierra, does, which is your company's conversational AI.

And so just imagine you're a retailer.

I think you'll put as much care and attention into your AI agent as you do your website or your mobile app, or if you're a bank, and you'll put as much care and attention to your AI agent, which can help a customer look up the balance in their checking account, or perhaps be an interface to your investment

banking arm or wealth management arm, or if you're a streaming service, your agent might help people sign up for a plan or upgrade or downgrade their subscription as an example.

In that case, an agent is something like website or mobile app that's branded and it's yours, and there are parts of it that are about agency and sort of the AI definition of the word, but more importantly, it's your thing.

It's your digital asset that becomes the digital manifestation of your brand.

And that's what my company, Sierra, does, and we think that's one really important part of an agent.

Just like in 1995, the way you existed online was to have a website.

We think in 2025, the way you will engage with your customers will be your AI agent, and we think it's a really important new category.

But then taking, okay, what are the other types of agents out there?

One will be, I like to think of them as persona -based agents.

They're internally facing, they do a job.

You've talked about software engineering.

I think there'll be a software engineering agents that will work to produce software.

I was looking at a startup called Harvey, I think, that's making a legal event, which is super interesting.

And I think across many job functions, there will be AI agents that produce the output of a, whether it's a paralegal or a software engineer or an operations analyst, things like that.

So that's one. So there's your company's agent.

There's a persona -based agent that does a job.

And then the third one category, I think is probably personal agents.

So this is the agent that will work on your behalf, whether it's helping you plan a vacation or organize your calendar or perhaps triage your inbox and things like that.

I think technically they're all similar, but my guess is they're different enough in what job they accomplish for you that there's probably different companies will build those different categories of agent.

If you're building a software to be a personal assistant agent, the breadth of systems you have to integrate with is infinite because different people use different calendars and different this and different that.

And there's lots of interesting investment into that.

If you're building a coding agent, it's a much more narrow use case, but very deep.

And you're probably evaluating it based on benchmarks of the effectiveness of the software it produced and the robustness of the software it produces.

And then for Sierra, where we're helping companies build agents, it's about customer experience more than anything else.

It's everything from how does it become a brand ambassador?

How does it follow the guidelines of your different procedures?

How do you actually take all these different facets of your company, whether it's sales or service or whatever's on your website will probably be in your AI agent.

How do you actually operationally get that, manifest that as a conversational experience?

Interesting thought exercise would be across those three categories.

If we think about 1 .0, which I'll define as what's possible today with current technologies, 2 .0, which is maybe the next generation of LLMs or something from the major providers that come out and others.

And 3 .0 is more distant future, can imagine it, but not yet technically feasible or something.

How would you discuss agents at those three levels of development from your perspective?

My sense is that progress in AI will be fairly iterative with occasional jumps and capabilities.

Certainly with the original advent of chat GPT and instruction tuning, a large language model, that was a big jump.

I think GPT -4 represented a similarly big jump.

But I think in between, we'll see lots of iterative improvements to these models.

So first, I think that I think of it more as a gradient than I do steps.

I might be wrong. It's very hard to predict the future right now, but I do think of it that way.

And I think of it, if I think about the how to responsibly deploy AI, it's responsible iterative deployment.

But every step of the way, how do the creators and users of AI recognize its limitations?

How do you build in the safeguards recognizing that those limitations are real?

And how does that change over time?

And with that in mind, how do agents change?

More agency, more autonomy over time, so that right now, I think, whether it's hallucinations or jail breaks or all the different ways AI models can go hooray, they're more frequent with current models.

And as a consequence, do you probably, if you're doing this responsibly, don't want as much agency, right?

You want more smaller, more bite -sized tasks.

You look at the way software developers are using coding agents today, it is that it's maybe write a function, not write a program.

I mean, a little bit reductive.

That's why I think about it.

And if you progress forward and you have better reasoning capabilities, better tool use, you can turn up the knob on agency responsibly.

And then similarly, I think, as you think about safety in AI, as these models become more advanced, you want more advanced guardrails as well.

And especially once AI can access tools or access the internet, the surface area of opportunities to things go wrong increase as well, particularly as the models increase, there's a tension there, right?

As the models get better, you can give the AI more agency to complete tasks.

But I think the level of sophistication of the safety issues that you have to handle also get more broad and complex as well.

So my sense is over time, there'll be more powerful, have more agency effectively and be more complete in the jobs that they accomplish on our behalf.

And that would have to be commensurate with improved guardrails and safety, recognizing that as you provide an AI more agency, the surface area of things that you'll need to protect against get broader as well.

What do you think are the next most important unlocks for the power of these agents?

You mentioned their access tools, access the internet, I've heard people talk about the ability to have some sort of stored memory about you, the customer, the specific customer, or just memory in general, that doesn't just live inside of a context window, that's always refet in or something.

Are those the three things that we need to unlock the next tier of productivity out of agents?

Are there other things that you and Sierra are focused on?

I'd love to get down to the nitty gritty capabilities and roadblocks that you're thinking about and working on that might make these things as ubiquitous as you think they will be.

Yeah, I'll start with the vantage point of Sierra.

We help companies build customer facing AI agents.

Today, if you're setting up a new Sonos speaker, you can chat with an AI agent they built on our platform to help you set it up.

If you're a Sirius XM subscriber, you can chat with Harmony, which is their AI agent they built on our platform.

And if you're a Weight Watchers member, if you click on the 24 -7 live coaching tab in their app, that's an AI agent they built on our platform.

One of the things that I think is a nuanced problem that is not strictly technical in nature is just the act of actually designing conversational customer experiences is a relatively new discipline.

I remember in the early days of the internet, most websites looked like DVD intro screens, like they're very graphical, there's four big buttons.

It's really interesting to go on the way back machine and look at them.

And I would say it took a number of years to evolve and to sort of the design idioms that we recognize with websites today.

And now if you go to a retailer, they'll have a hamburger menu in the top left and the way you filter through items.

And these, they're sort of emergent from people's lived experiences, both designing and using websites.

And now you can talk to almost any web developer and they'll not only choose similar technologies to make a website, but even the design process and Photoshop or Figma to design a website, they're sort of established practices, some of which are obvious and some of which are actually subtle, like why

did this become the way these things are done?

And it's the cumulative experience we have building with them.

The difference between a website and a mobile app and an AI agent is both the breadth and non -determinism of AI agents.

So if you have a menu on a website, you can control what links are there and it's essentially multiple choice.

Here's the options available to you.

If you have an AI agent with a freeform text box, people type whatever they want into that.

And so your concept of what your customer experience is defined by you, but it's also defined by your customers by what they write in there.

It reminds me, going back to my web analogies here, reminds me of going from Yahoo directory to Google search rather than having a taxonomy of everything available, it's just freeform.

And there's a much longer tail of queries in Google than there was in Yahoo because of the expressiveness of a search box versus a directory.

And I think that that's one of the really interesting and I think exciting opportunities with conversational AI for customer experiences is it's a really authentic way to actually hear from your customers what they want from you.

And I think we've, it sort of stands to reason your website was the rails on which your customers communicate with you.

And this is so freeform that I think it's much more expressive and we've had multiple customers learn things about their customers that they didn't expect by providing this really freeform experience.

And then similarly, I think the other really interesting thing when I mentioned non -determinism is the word agent comes from agency.

And it's really how much creativity do you want to give your AI in interacting with your customers?

I think if you start from a position of control, you can say, I want to put guard rails around everything, but then your conversational customer experience is somewhat robotic.

You've essentially defined the multiple choice options of your customer's experience.

If you give your agent too much agency in the extreme case, it will hallucinate, but in the more practical case, it just might not protect your brand in the way that you want it to.

And I would say that design question is both a technology question, which obviously we're quite invested in solving and I'm really excited about some of the work we've done there.

But there's a deeper question here too.

It's actually a philosophical branding and design question as well.

And what we're trying to do at CIRA is not necessarily predefine the answers to those questions.

I think every company and every brand will have a different perspective on what's correct for their brand experience, but provide a platform that's powerful and expressive enough, whatever your answers are, personally to that question, you can build your agent on CIRA.

It's so interesting to think about the customer experience going to a website where I buy shoes or something.

I think one of your first customers was flip -flops and there's a funny story around that.

But I'm going to buy a pair of sandals, let's say on a website, and rather than click around, I just describe what I want and I can imagine like another pane on the right just starts like showing me stuff.

And then maybe I check out through this same thing as well and that's a simple version of tooling or ability to take action.

I'm curious what the hardest parts for you have been to build.

It's quite technically daunting to even think about how to build something like this, let alone one that's adjustable and tunable to my specific brand.

So talk a little bit about how hard of a technical challenge this is for CIRA.

Like the degree of difficulty you've encountered relative to say your expectation.

Yeah, it's a really wonderful question.

I think that generative AI broadly is a technology with which it's very easy to make a demo and very hard to make an industrial grade system.

And I think that's the area of technical challenge that we're really trying to dive into.

And I think it's one thing to say this system does the correct thing 90 % of the time and it's really an ink blot test whether 90 % is a really good number or a horrible number.

And it also depends on the process.

And so if it's a consumer application that was helping you with your homework, maybe 90 % is decent.

If it's something operating, revenue impacting part of your business or there's a compliance concern, it's absolutely unacceptable to be wrong 10 % of the time.

And so a lot of the challenges that we're facing are we like to say that software systems are moving from rule -based to goals and guardrails -based.

And it's a very different mental model for building software systems.

Rule -based systems, if you think about just the software development life cycle that's evolved over the past 20 years, it's really about how you make more and more robust rule -based systems.

How do you ensure that the same input produces the same output, that it's reliable, that it's stable, and that a lot of like true innovation in the way we make software to make them more secure and robust.

Now, if you have parts of your system that are built on large language models, those parts are really different than most of the software that we've built on in the past.

Number one is they're relatively slow compared to generate a page view on a website that takes nanoseconds at this point.

Might be slightly exaggerating down to milliseconds.

Even with the fastest models, it's quite slow in the way tokens are emitted.

Number two is it can be relatively expensive.

And again, it really varies based on the number of parameters in the model.

But again, the marginal cost of that page view is almost zero.

At this point, you don't think about it.

Your cost as a software platform is almost exclusively in your headcount with AI.

You can see the margin pressure that a lot of companies face, particularly of their training models or even doing inference with high parameter count models.

Number three is they're non -deterministic fundamentally.

And you can tune certain models to more reliably have the same output for the same input.

But by and large, it's hard to reproduce behaviors on these systems.

What gives them creativity also leads to non -determinism.

And she has this combination of it.

You've gone from cheap, deterministic, reliable systems to relatively slow, relatively expensive, but very creative systems.

And I think it violates a lot of the conventions that software engineers think about, have grown to think about when producing software.

And it becomes almost a statistical problem rather than just a methodological problem.

And so that's really what we've tried to solve.

We shared on our website, but we have a process we call the Agent Development Lifecycle, which is the name comes from saying the software development lifecycle, here's what you should do with these agentic platforms.

It's also, we've developed a lot of unique technology to make these systems more robust with having one AI model supervise another AI model to layer different models on top of each other to produce statistically more robust results.

And then as importantly, we've developed ways that folks who aren't experts in AI can express the behavior that they want in their agent.

You shouldn't have to be an AI expert to make an agent, just like you shouldn't have to have a PhD in computer science to make a website.

And I don't think we're there yet, but that's really what we're trying to solve.

And broadly speaking, I would say on the spectrum of fundamental research institutions like OpenAI, we're not that we're applied.

We're really thinking about how do we engineer on top of these foundation and frontier models to produce robust and reliable agents for our customers.

I love the title of this one, Kevin Kelly book, What Technology Wants.

And I'm curious what agents want.

If I'm a customer, I'm a prospective customer and I want to go work with Sierra to make the best possible version of a conversational agent for my customers to use, what can the companies provide that make the agent do the best job?

Yeah, it's a great question.

I would say that there's two types of knowledge that I think really produce a really robust agent.

One is the factual knowledge of your company.

This just grounds the agent so that it won't just make something up.

There's a pretty widely used technique called retrieval augmented generation in AI right now that effectively means rather than relying on the knowledge encoded in the model to answer questions, you present the model with knowledge maybe stored in a knowledge base or a database and say, hey, summarize

the content from here.

Don't rely on the information you've been trained on.

That has been an effective technique for two reasons.

One is that it means that you don't necessarily need to train or fine tune a model to use it with proprietary data, which is a much cheaper deployment methodology.

And it also can be effective at preventing hallucinations as well because you're effectively rather than relying on the AI to determine what it knows or doesn't know you present the AI with the knowledge that it's allowed to network.

The simple way of putting it, and that's factual knowledge.

And I would say that's necessary, but woefully incomplete because that would enable your AI agent to answer questions, but it wouldn't necessarily enable it to orchestrate a complex process or take action on your customer's behalf.

The other type of knowledge is procedural knowledge.

If a Sonos speaker stops working, what would the best Sonos engineer ask you and do to figure out whether it's a problem with your hardware, problem with your Sonos app, or problem with your wifi?

Like what is the process by which you do that?

If you're a subscription streaming service, what is the process of processing an upgrade or downgrade to your membership?

Are there different offers available based on your membership level?

Do you have a promotion running?

What's been the most effective technique to keep people a subscriber for a long period of time?

This is all the stuff that if you were a person, an expert in it, and so coming in with that knowledge of not only here's the factual knowledge for our company, but here's the processes that represent our greatest customer experiences.

What does the best salesperson do?

What does the best customer service person do?

What is the most effective marketeer at your company?

How do they describe your products?

And that's often there we work with our customers to improve when they deploy AI.

And then the third thing is just access to the underlying systems themselves.

I think the AI agents shouldn't just be about answering questions or having a conversation.

They should actually be able to take action on your behalf.

Whether that's a retailer processing a return or a subscription service changing your level of membership or connecting to the telemetry system of a consumer electronics company.

So we can say, hey, we know your device phoned home.

You're connected. We now figured out this other problem.

Or even with something like Sirius XM sending a signal down from a satellite to refresh your radio if your radio stopped working.

So three ingredients, factual knowledge, procedural knowledge, and systems integrations, I think are the three key ingredients.

And then with the right methodology, your agent can do anything that a person can do on a computer, which is just an incredible opportunity for customer experiences.

How long does one of these things take to build?

I imagine there could be quite a bit of upfront work.

Last time we talked, you described this interesting process.

I think you called it spring cleaning.

That tends to happen probably around defining process and best practices within a company.

And obviously it's super early days of this.

So I'm sure your answer will get shorter and shorter as we get better and better at this.

But just today, if you meet a new customer that wants to install one of these agents on their website or app or whatever, how long does it take start to finish for a new customer to get live?

Between one and three months, we have a model where we really hold the hands of all of our customers so that they don't need to be AI experts or experts and agents at all to get started, which is pretty unique.

I think it's a new enough technology that the last thing, I always joke, that you can build a couch by going to Home Depot, but you need to be a carpenter.

Or you can go to IKEA and all you need is an Allen wrench.

When these technologies are new, we really felt like it was important that any company, no matter how many resources they have available, can deploy them.

So we have a really high touch model so that we can get customers live as quickly as possible.

And I'm really happy with how rapidly we can do it.

Can you tell that flip -flop story from I think one of your first customers?

Yeah, one of our first customers was a shoe company and we had built the agent to handle common retail use cases.

To my memory, I might be misremembering here was things like where's my order, things like that that we expected.

The customer actually sent us one of the first conversations and it was, again, my memory might be a little off here, but I'm going to a wedding in Hawaii, what sandals will go with my bridesmaid dress?

And it was one of those things at the time, the agent was like, I can't really tell you that.

Tell me to transfer you to someone who can.

And it was really interesting to me because it illustrated the point on expressiveness that we spoke about earlier, which is whatever your conception is of what your agent will be used for, because it's free form, your customers will express themselves completely freely.

And as a consequence, you might think, I'm going to launch this agent to handle customer service, which is a great initial application, but you might find your customers are pulling you in a different direction.

But I think that's remarkable.

So many of our retail customers are doing things like product recommendations.

And you just think about the best experience you've had at a brick and mortar retail store.

Maybe you have that associate who's understanding why you're in the store, what you're looking for.

They're not too pushy, but they are really trying to listen and understand what you're trying to do.

Maybe they're offering you products you didn't think you needed.

Maybe they're steering you to the right section in the store.

That sort of consultative experience, what's so neat about conversational AI is you can scale that.

One of the things that I think is really interesting just from an economics perspective is technology fundamentally drives productivity in the economy if you're an economist.

And what I really like to think about for new technologies is what thing used to be extremely tedious and expensive that is now really cheap and effective.

And in this case, if you have 2 million customers, if you actually think of the cost of having direct conversations with all of them, it's tremendously expensive.

Usually that involves building a contact center, either in -house or with a BPO, an outsourced firm.

It probably means that you're overstaffing it to handle peak seasons.

It involves huge amounts of training for the workforce and that call center.

Every time you have a new product or new process, you need to train everybody and it becomes a huge cost for your company.

And that's why so many as consumers, it's usually pretty hard to have a direct conversation with the brands that we work with every day.

It's not because they necessarily don't want to, it's just that economically, it's really hard to make all of that work and justify that expense.

And it really depends on the margins of the business and the value you as a customer are providing, like whether you can get on the phone.

With AI, we have this opportunity to bring down the cost of a conversation down to something that's fairly marginal and it's really exciting.

We'll be able to actually have a direct personal conversation with so many consumer brands in a way that just wasn't possible before.

And I think that's much more than automating what is currently maybe a customer service interaction.

I think it's bigger than that because I think brands can have a much bolder vision for what are the conversations we want to have with our customers.

And now that the cost is tolerable, what are the areas now that we don't need to treat this as a cost center that we're trying to minimize and we can treat this as a incredibly impactful way to interact digitally with our customers.

Where are we gonna have conversations in ways that just weren't possible before?

I could imagine today, tomorrow, hitting a button that says, here's a ton of context about me so that you can do a better job serving me the right product or service or come to a faster, more efficient outcome or whatever.

When do you think that happens?

That there's more information about each individual person being served because it seems like that's the other part of this equation that would unlock magical, incredible experiences.

Like the best salesperson would know everything about me.

They would be much better suited to serve me then.

That seems like a piece that is not on my radar anyway.

I'm curious if it's on your radar.

I think we're to some degree already there, but just to reinforce your point, I always like to start with our experiences as consumers of these technologies.

And first, we all speak different languages.

Second, we're all, as you said, our relationship with different consumer brands might be in different states.

And today with AI, you can look up information about the customer.

You can tailor the experience to them.

You can speak in the language that the customer speaks in a multilingual way with a single AI agent.

Maybe someone wants to have a long conversation.

Maybe someone needs to get it out very quickly.

The agent will reflect to that urgency or reflect the tenor of that conversation.

Again, going back to my point on the cost of having a conversation, there's no need to get off the phone.

You can have as long of a conversation as the customer wants and there's not a operational reason why you need to rush someone through that conversation.

I just think of empathy through this.

And similarly, I think one of the things that's really also exciting about AI is you can take the best experiences you've provided your customer, whether it's a great sales experience or great marketing conversation, and you can scale it.

I think that if you just imagine retraining your workforce on a methodology, it's a slow and expensive process.

Not only is it hard to do, you don't want to do it frequently.

Now with AI, if you discover a technique that works either intuitively or through some measured automation, you can actually deploy it instantly.

It actually enables not only a degree of empathy and personalization that was not possible before, but as a leader of a company and a brand ambassador, you can try things more quickly.

When you find a magical moment, you can operationalize it.

There's a great book.

It's called Unreasonable Hospitality.

And it was a really interesting book conceptually to me because there's anecdotes of people having these really delightful experiences in this three -star Michelin restaurant.

They seemed like these one -off moments.

And a lot of his vision of that book is how do you operationalize that and repeat it?

And I really do believe that AI is an opportunity to do this for all of your customers and say you can scale things and have them be personalized at the same time.

And I think that is only possible with AI.

And I think it's a really meaningful opportunity for brands who lean into this technology.

What do you think about the future interplay between the three kinds of agents you talked about before?

I can imagine a world where I have a personal agent and I send them to do the shopping.

And most of the interaction between a company's Sierra powered agent is with my personal agent or something crazy like that.

Turtles all the way down.

Yeah, turtles all the way down.

This all seems incredible for like the first order reasons you've described, but it also seems like it's gonna change the way we do stuff in unpredictable ways.

And you have the front row seat here.

And so I'm just curious how you think like the interplay of this is gonna change companies, change consumer behavior.

It's like the bigger macro questions are fascinating to me.

It is a really great question.

And I'll start with the humility that it's very hard to predict the future.

In 2007, if you watched Steve Jobs introduce the iPhone, how much would have you predicted correctly about its impact on society?

What's interesting about that moment too is the intersection of technologies.

A social networks existed in 2007.

And one could argue that we didn't really fully realize the societal implications of social media until you had the smartphone and social media and push notifications.

And they all add up to a lot of the issues that I as a parent and we as society grapple with now.

So you have both the first order impact of these technologies and the second and third order, which are very hard to predict.

And like the smartphone, I think the impact of AI agents will be fairly broad and there'll be some counterintuitive implications that I'm excited to experience, but I'm not sure I can fully predict.

So that huge cap a lot.

I do think that personal agents will interact with company agents.

Clay, my co -founder Clay before and I have a bet.

I won't tell you the dates, but we have an internal bet about when the conversational traffic to our company agents will be more personal agents than people.

Like where would we cross that line?

But the fact that Clay and I have talked about it, I think reflects the depth of our conviction that this will be a meaningful part of the future of how we interact with computers.

Similarly, one of the things that I'm really interested in seeing is how we interact with the devices around us.

I thought Alexa, we have Alexa's on our countertops at home as a lot of people do.

Siri was a huge part of the Apple experience.

I would say neither platform really transforms the way I use my phone yet because I think the limitations of those platforms, which predated sort of modern large language models, it will be interesting to see how all the microphones around us turn into more full featured experiences with the prevalence

of conversational AI.

And similarly, if you look at countertop speakers, car play, things like that, how full featured can those experiences get when most of the software we interact with has fully capable conversational capabilities?

Similarly, if you've ever used Android or Apple's in car experience, it tends to be very app centric.

And I think it'll be interesting to when you have a personal agent integrated with those experiences and you can say, send an email to so -and -so about this and all these other things.

And all of a sudden, rather than queuing things up on your commute, you're actually getting work done on your commute in a completely hands -free way.

Those types of things, as I said, like the first and second effects, I just feel like the power, the surge we saw in excitement around smart speakers and all that might come back when those things are actually more effective computers as opposed to mechanisms to get the weather and turn on music as

they are at least in my household.

And then similarly, in the same way, like first iPhone apps were like flashlights and really wrote uses of the gymnastic tool and schematic things, it took a couple iterations of the App Store to get the door dashes and the Ubers and the WhatsApps.

My sense in this world of conversational AI and agents, there'll probably be some really interesting native agentic platforms and tools that come to exist as well.

And I'm excited to see those as well.

It's so interesting to think about how this changes work, people's productivity, businesses.

I'm curious about each.

We opened by talking about the 100X engineer or something.

Do you think that all of this just blows out that phenomenon of rising inequality around people's productivity that like the very best person in any field is just gonna get that much more effective and maybe capture that much more of the rewards available in that field?

Does all this technology naturally promote more, I'll call it inequality, in focus on productivity?

Like, how do you think about that?

It just seems bizarre that so many of the things you've described are really exciting.

And it just makes me wonder the profound shifts that might happen in human labor productivity and the returns to being one of the best.

Because I've seen some of these engineers working with cursor and Claude and everything, and they're able to do the work of like 10 people.

Or even like the people in the research labs at OpenAI or elsewhere, it seems like the very best people are having a disproportionate impact on the world and this might accelerate that.

So do you worry about that?

What do you think about that?

Let me start with a optimistic view of this.

And then I'll talk about maybe some of the more billions of caution that I have as well, because I think it's very multifaceted in implications.

One of the very exciting parts of AI and AI agents specifically is it removes a lot of the gatekeeping in a lot of professions.

Think about the directors that use the most special effects like James Cameron or something like that.

And the hoops that he had to jump through for the first Terminator movie, or the director of Inception in Batman, Christopher Nolan, and you look at the cost of making like Inception and you wonder if he as a 20 year old university film student had the ability through describing in natural language,

different visual effects and all of that.

Could someone with very few resources actually make a film as powerful as Inception?

When I come from the era where I strung two VCRs together to edit a movie, the every iteration of the technology has enabled YouTube creators and now TikTok creators.

And I think with these tools, it enables people with good taste and good judgment to accomplish a lot more than they could individually.

And I do think that whether it's the cost of hiring a VFX crew or the cost of even learning how to use some of these really arcane tools, that I'm hopeful that it means people from any art of the economic ladder, any country, may have the opportunity to produce really exceptional art or produce exceptional

products because there's fewer people you need to ask permission and get financing from to do so.

And I think that I'm very hopeful that by technology breaking down many of those barriers and requiring less societal permission to do things and finance things that we'll see hopefully some really meaningful new creations come from people who might not otherwise have the resources or as I said, societal

permission to do so.

I do think that depending on how you reflect the lens of equality, I think it can be a broadly equalizing technology as well.

I do think that the point on leverage that you made, which is software engineers become even higher leverage, especially the most exceptional ones is true.

I feel like the act of being, say, a software engineer is going from someone whose job it is to emit code on a keyboard to being the operator of a code generating machine.

And the people who learn how to do that really effectively will be able to operate at some incredible scale.

I broadly think that is a good thing.

I think that just writing equations on a piece of paper wasn't the job of accounting and Excel displacing that didn't necessarily change the job of the accounting department at your company.

I don't think the job of a software engineer is to type into a terminal the job of a software engineer is to produce software.

So I think these tools are broadly helping the job of software engineering become more self -actualized, more closer to what the value you're producing.

On the flip side of this, I do think that there will be like any new tool that folks who learn how to use them effectively will gain outsized value from using them.

I think the proverbial digital divide is a increase in concern because if the productivity gains from effectively using these tools is amplified just by the power of the technology, it's as important as it ever was and much more important now to make sure everyone has access to these technologies.

And then broadly, if you fast forward 30, 40, 50 years, I firmly believe that society will conform the economy around the technologies that we produced.

Just like when this country was founded, we were largely an agrarian economy.

And then we became an industrial economy and now our services economy, thanks to the evolution of technology around us.

The same will happen with AI and I'm not sure we could even recognize many of the jobs that exist on the other side, but we are status -seeking creatures.

We will create an economy around the technology that defines our society, but that transition can be quite uncomfortable.

And I think one of the things that I've thought a lot about is unlike the, say, adoption of the personal computer or the adoption of the smartphone or the adoption of broadband, those involves infrastructural investments that took place over many years, let alone the adoption of electricity, which took

even longer. This is largely a software -defined revolution, not withstanding the investment in data centers, but in terms of our adoption as consumers.

And as a consequence, I think the change will happen more rapidly because the adoption can happen as instantly as the technology becomes effective.

And I think that short term, I think it is something that we collectively, companies, research labs, governments really need to think about because it's one thing to shift from an industrial economy to a services economy over decades.

It's another thing to change the nature of our work over just a handful of years.

And that's something that I think is a really meaningful issue that I don't think has a simple solution.

In addition to what you're doing at Sierra, you're the chairperson on the board at OpenAI.

I know Sierra uses several models, eight or nine models to build this product, and I'm sure that will proliferate and improve over time.

I'd love to zoom down to the individual model level and hear your insight on where we are and where this might be going.

I had this moment with my kids where when GPT -40 came out and the audio conversational aspect of it and the multimodality of it became, I guess, new and powerful.

I just noticed like my kids use it way more as a result of being able to talk to it and ask it questions.

It's like unbelievably effective.

What do you think of that shift?

And what are the meaningful shifts happening at the model level in your opinion that people might be underestimating or underappreciating, given that these things are getting better, as you said, in a gradient way all the time with these discrete jumps.

But you have a cappered seat in many ways in AI, but at the individual model level, what is going on that's exciting to you that maybe outsiders don't fully appreciate?

I'll start with what I view as the inputs to progress in current sort of like large language models and generative AI.

There's really three axes that are continuously improving to produce these amazing experiences that OpenAI is producing.

One is the research, the algorithms, probably the most meaningful breakthrough over the past decade was the Transformers model, which was a paper out of Google called Attention is All You Need and created the current wave of excitement around AI.

And you can think of the algorithmic breakthroughs as methodologies to either enhance the scale or the speed of AI or enhance the reasoning capabilities of AI, things like that.

Number two is the data.

These large language models, the first L is large.

They're trained on a huge amount of data, not just text anymore, but also images and video that's called multimodal.

And there's a lot of questions about what data is available to train on.

I think a lot of textual content, large amount of the textual content humanity has produced has already been used in training.

They're not all of it, but there's a lot of other modalities.

There's also a lot of interesting companies working on things like simulation and data generation.

So how can you have more data to improve these models?

And the third thing is infrastructure.

So how do you apply more compute to these different training processes, either pre -training or post -training?

And I think part of the reason why we've just seen such continuous improvement from OpenAI and other research labs is all three of those were just seeing tons of investment.

Everyone, I think Nvidia is reporting earnings this week and everyone's eager to see if the infrastructure investment has continued.

All of the great minds in AI now are working on large language models, give or take.

I'm obviously being a little reductive there.

And so you're seeing just more and more of the smartest minds working on the algorithmic and methodological breakthroughs.

And then similarly, as I said on the data side, you not only are going from text to multimodality, but also some really interesting concepts of synthetic data generation and simulation and all these other things that are really exciting as well.

And the combination of all of that is even if one of them hits a plateau, you can see progress in the other.

And no one really knows when the scaling laws, which is the idea that a linear input in computing data will produce roughly a linear improvement in quality won't stop.

But because there's the smartest minds right now are working on all three of those, you're seeing just remarkable progress.

And again, not simply from open AI though, I obviously biased, but I think open AI is the leader in this space.

The thing that you mentioned that I just want to say that I've mentioned a couple of times, but I think is exciting is multimodal models.

That demo of GPT 4 .0 was so remarkable.

I had so many people text me about it, just talking about just how emotional the experience of watching that was.

A lot of people are using it in the open AI app as well.

What I love about it is it's the way a science fiction author would describe how you should interact with a computer.

We started out with punch cards, then we had mice and keyboard.

Now we have touch screens, which are feel slightly more haptic and slightly more natural.

Every time you watch a science fiction film or a movie, you're just having a conversation, right?

And it was probably the first time for a lot of people where it really felt right, but didn't have that uncanny valley feeling of I'm talking to a robot.

And I think that's really exciting.

And so obviously multimodal models to generate images and video are quite exciting, like Sora.

But I think that particular thing, which is the interface to computers, goes away.

And we can simply have a conversation to interact with software and interact with this digital world is so powerful.

I think it's going to, I don't know if you had this experience, but my grandparents are now deceased, but all but one of my grandparents skipped ever having a PC, but they did have iPads, which was interesting.

So like they had retired by the time sort of PCs became prevalent in homes and they're like, that's not for us.

We don't need a computer in our house.

When the iPad came out though, it was accessible enough and they could read the newspaper on it and all these other things that they started using it.

And it was interesting.

They sort of skipped a generation of technology.

And it was so interesting that computers were, the friction and intimidation of using a computer was too much in the era of mice and keyboard.

But the iPad, thanks to Steve Jobs and Johnny Ive was enough that this didn't feel so intimidating.

Now imagine if they were alive to see just having a conversation with everyone knows how to talk.

And we talked a little bit about the impact of AI and equality, which is a very important conversation.

I think of just the accessibility of software in this world of conversational AI is just such a tremendous breakthrough.

It's just the correct way we should interact with software and no one needs an instruction manual on how to have a conversation.

What's the end state thinking?

Is it brain computer interfaces?

And is that the end state of zero friction, man machine interaction?

It's a great question.

I think we'll see lots of experimentation there.

I say that with pause because since the introduction of the iPhone in 2007, we've seen a lot of devices from startups, Apple and Google and others that are supposed to augment that smartphone.

And it turns out the smartphone is just such a powerful universal device that does a lot of things perfectly and a long tail of things well enough that it's been very hard for any new consumer device to take over that.

I think that Silicon Valley is made for this moment of experimenting with different ways of interacting with this technology, whether it's a speaker in your kitchen counter or maybe AirPods in your ears or maybe it's brain computer interface in your brain.

And I'm not sure which of those will end up the optimal combination of accessibility and cost and convenience to represent the way like the median person uses this technology, but we have a lot of the ingredients already.

And thanks to the proliferation of consumer smartphones and others, I think we already have a supercomputer with a speaker in our pocket connected to a very sophisticated headphones.

If I had to guess right now for the foreseeable future, that will be the dominant interface, not because it's the best, but because it exists.

And in the same way, it's been hard for consumer device companies to break into, they take a slice of what your iPhone does and do it slightly better.

That it's hard when you have this really mature smartphone market, but I do think we'll see some really mind blowing experiences.

It's just hard to predict right now.

So I'm really excited to see the proliferation of R &D here.

And I think that I use the phrase, everyone's gonna have their Iron Man suit that's gonna be very personalized to them.

And the thing that I'm really excited about is I hope technology melts away from what we do.

That's not a foregone conclusion, I think, but we spend so much of our time staring at screens nowadays.

I'm not sure it's great for us personally or for our interpersonal relationships.

And I think I'm hopeful that some of these technologies will facilitate technology receding to the background despite being a lot more powerful if they've done well.

I'd love to talk about the future of business and building companies.

I've seen you write about like Cosis theorem before the joint stock companies a couple hundred years old.

Technology has often changed the nature of companies and businesses and products.

And I'm curious where you think it will change the most in the future as a result of agents, as a result of artificial intelligence and so on.

Because if I was a big company right now, I would just feel scared.

I wouldn't know specifically how to be scared because the vector of attack seems hard to predict.

But I would sure feel like, wow, the way that a normal fortune, whatever company is structured today, if I was starting a new one tomorrow, probably would think about some things differently.

So how do you think about the future of the nature of a company and building a company?

That's a wonderful question.

I do think the thought exercise which you've hinted at is what would, given the products and services your company makes, imagine a world where a huge percentage of some of the operational tasks can be automated.

What would the shape of your company be?

And what would the implications be on your business model?

Probably the most complicated second order effect will be can a new competitor emerge with drastically different profit margins than yours?

I think the reason for that is often if a company has a different cost basis, then they can compete unequally on pricing and packaging and things like that.

And so I think it could be really interesting if you have, broadly speaking, I'm having started a few companies and worked at some larger firms.

I think a lot about the sort of creative distraction in Silicon Valley.

And one thing that I think is broadly true is when there's a new technology emerges, like the internet and the web browser or the smartphone, it tends to correlate with some startups that become very large companies.

And I think the reason for that is disruption and the sort of traditional sense of the word where effectively companies built natively for these platforms can have different business models.

In the case of the internet, like Google introducing sort of app -based consumer software was like a pretty, both a meaningful technology and a meaningful business model and move more with more agility than some of the incumbents in this space.

I think the same is probably true of a lot of different markets.

If you look at what Amazon did to many of the incumbent bookselling firms with the birth of the internet.

So broadly speaking, I think, operationally, how do you think about the long -term implications of automation?

What is the shape of your company and how do you set up yourself for that?

And then secondly, if you imagined you were starting from scratch, creating some competitor, providing similar products and services, what would be the unequal advantages you'd have as a startup?

And how do you inoculate your company against that?

And I think that's gonna be the most important thing for companies who are thinking about the disruption that may come from this.

I do think incumbents have a lot of tools at their disposal, that they have existing customer bases, they have existing expertise.

And as a consequence, I've given this advice, which is, I think the most important thing companies need to do is adopt AI internally and externally.

Anyone listening can give me a call for the external use cases will help you build a customer -facing agent.

But internally, your employees should be using an officially sanctioned version of chat GPT, right?

That should be a part of how they do their jobs.

You should be thinking about not only short -term opportunities with co -pilots and the like, but saying, let's set some ambitious milestones for automation and some of these back office processes so that you can set yourself up for the future and not be on your heels when up starts that take advantage

of this. And the history is littered with companies that didn't adopt technology quickly enough, the sort of proverbial Blockbuster Netflix story.

But there's also a lot of examples of companies who adopted these new technologies quite effectively and took advantage of their scale and distribution and market expertise to adopt it.

I think it's early enough that nothing is too late, but I think it's really important to both adopt it and start developing those lessons and also strategically think about game theory out what a new competitor might do differently, particularly things that would impact your business model.

And I think those are the things that are just artists to fix more than any technology adoption curve.

Can you explain a bit about OpenAI's unique structure and the impact that you think it has on the work that it does?

Most other foundation model companies, there's different structures.

I think research labs is like a great way to talk about them or label them or something.

OpenAI has this fascinating history from nonprofit to very unique governance structure today.

What could you teach us about it and what makes it interesting to you?

So really simply, OpenAI is a Delaware nonprofit.

So what that means, so most Delaware companies are basically the fiduciaries of the company, the board serve shareholders, and that's the conventional Delaware C corporation like CIRA with a nonprofit rather than being a fiduciary to shareholders, folks like me were fiduciaries to the mission.

So fundamentally it's not about shareholder returns, it's about serving a mission.

And the mission of OpenAI is to ensure that artificial general intelligence benefits all of humanity.

It's a really broad mission.

I think that's part of the reason that OpenAI both because of the influence of chat GPT and the impact of the organization, but also that mission is a inkblot test for whomever reads it on their greatest aspirations for what could go right or could go wrong with AI.

And I think the breadth of the mission is also part of the reason why OpenAI is at the center of so much of this AI conversation.

As you alluded to on the unusual structure, a number of years ago before my time, the company created a for -profit subsidiary to raise the capital that it needs to build artificial general intelligence.

I think the, I don't want to speak for the founders, but broadly speaking, I'm not sure anyone knew when OpenAI was founded the amount of capital you would need to build AGI.

It's not really a bring on a bunch of researchers and think a lot.

It's built computers and train a lot as well.

And I joke, you can't really have a nonprofit steak dinner fundraiser and raise $5 billion.

It doesn't really work.

Notably too, as you mentioned, research labs, my understanding is that Anthropic is a B Corp, which is a benefit corporation, which means it has dual accountability to a mission and shareholders.

So I think a lot of the research labs, broadly speaking, are I think trying to recognize the importance of being mission -driven in the age of AI and really focusing on benefiting humanity, which has never been more important, while also creating a structure that can accommodate raising the kind of capital

that you need to build AGI, which is a lot more than I think anyone knew a decade ago.

One of the things that comes up a lot when you ask around about you and your story and your background is this Paul Graham essay, Keep Your Identity Small.

And if you look at the list of things you've done, not just the incredibly impressive companies, Facebook and Twitter and OpenAI and Sierra and all these others, but also the different roles that you've played, CTO, head of product, CEO, chair of the board.

It seems that you've done a good job of evolving or adapting your way through a landscape, which itself is changing quite rapidly.

And again, let others say it for you and not have to say by yourself, it seems like you are exceptionally good at that adaptability.

I'm curious what you do that makes that true.

I've told Sheryl Sandberg this story and she has no recollection of it, but I'm confident I remember it correctly.

I credit her for this adaptability and my personality.

I won't give too much detail because I'm private, but basically I was struggling a bit as CTO of Facebook and I was struggling with basically scaling.

It was probably the largest organization I had ever managed.

And Sheryl was everyone's mentor at that company.

I was probably 29 at the time.

She was the old guard and she had more experience than all of us and was not only generous with giving advice, but also would tell you the uncomfortable things you didn't necessarily want to hear, but you needed to hear on how you were doing.

And she had this very hard conversation with me basically that I wasn't holding the teams I was working.

They were working for me to high enough standard and that the reason why this project was going poorly was basically because I was trying to be heroic and do the job myself rather than grow this team underneath me.

It was a very impactful conversation for me because it was one of those, you start out dejected, like I suck, what am I doing wrong?

But I reflected on it and I was reflecting that I had gone from being kind of a technical architect, a very senior influential individual contributor to managing this big team.

And I was trying to conform the new job to me rather than inform myself to the new job.

And that was my reflection.

And I don't know if it was like the next Monday, it was soon after that I woke up every morning and thought rather than I'm at this with a strong sense of my identity and who I am, I'm gonna think every morning, what is the most impactful thing I can do today to accomplish the goals that the company

wants to accomplish?

And it worked. And the counterintuitive side effect of it was, it was delightful for me.

So I had this image of myself as a technologist and engineer and the reason why I was subconsciously trying to conform the role to my identity is I thought this is my identity and this is who I am and what makes me happy.

I found out through the act of trying to have a looser conception of my identity is not only was I better at my job, but the act of actually just having things go better was very fulfilling for me.

And it became this self -fulfilling prophecy, which is I was just focused on how do I achieve the end that I'm trying to achieve and by having a very loose concept of who I am and I was just trying to do the most impactful thing to accomplish the big picture, like what are we trying to solve?

Things started working really well and it was a reinforced to me that's actually what I care about is impact more than anything else.

And it's become something that I am very grateful for.

I'm very grateful for that hard feedback I got in a sort of vulnerable moment because I think I probably did have an overly ossified conception of my own identity and now I talk to some people who knew me on Google Maps and think of me as an engineer and I talk to some people at Facebook who think of me in that technology

leadership role. I talk to some people from Salesforce who think of me as an executive on the leadership team as COO and co -CEO and they're all right.

In those circumstances, that's who I was and I'm very comfortable putting on multiple hats and very comfortable taking them off as well when the timing is Ortiz.

Talked a lot about technology and product a bit today.

What about sales? What did you learn about world -class sales while at Salesforce?

Marc Benioff is just a remarkable, the greatest of all time in enterprise software.

I'm so grateful to have worked with him.

We're also really different and I just learned so much from him as a consequence of that.

The thing that I really appreciated at Salesforce and Marc individually is just that genuine focus on the success of customers.

It was something that there was a true accountability and I think every tech company talks about focusing on customers.

Most of the time it's lip service and it's like, how do people actually spend their time and what would your customers say about you?

It's the true measure of it.

And I saw on Salesforce the most customer -centric company I'd ever experienced and it really changed.

I thought WIP, which was a company that Salesforce acquired was customer -centric and I was like, we weren't.

I just hadn't seen great yet and so I really saw that from him.

How did they do it better than WIP?

Probably deep listening.

I think that there's a WIP, though I don't think the term had been coined yet, but it was a product -led growth company like Slack and Atlassian and others.

And as a consequence, I would say the anchor tenant of our strategy was really around the product and how we improved it.

And the concept that I don't know if we so formally articulated was the better we make the product the happier customers will be, the bigger our business will be, which is true, but that can lead to either patronizing customers.

They don't really want what they say they want.

They just don't understand the true power of these cool abstractions that we've made or all these other things and it can lead to arrogance.

And I see this a lot with really product -centric B2B SaaS companies that you're trying to convince the world of your worldview, which is really powerful when it's right, it can be quite arrogant when it's wrong.

And for Salesforce, it's just a more mature place with a really great CEO and founder.

And I just saw an organization that just constitutionally was really deeply listening to its customers.

I'm really interested in three of the values around which Sierra has built that we haven't talked about yet.

I have a way of asking about them.

I'll probably do it three times, which is how you would assess this value in another company and how you promote it in your own.

So the first one is intensity.

This value was intentional because of the market that we're in.

There's a Mark Twain quote, history doesn't repeat itself, but it rhymes.

And I think the AI boom will rhyme with the .com bubble.

And what I mean by that is that there will be a lot of hype, a lot of snake oil, but there will also be some generational firms created in this wave.

In the same way you had Webvan and pets .com, but you also had Amazon, Google, eBay, PayPal, Salesforce and others come out of it.

Similarly, I think that a lot of the ideas that we at Sierra are pursuing and companies like Amazon were pursuing the .com bubble aren't necessarily unconventional or surprising ideas like selling books online or let's apply AI agents to help with customer experience.

They're conceptually obvious, but it's all about execution.

And Amazon got to write the history books, not buy .com.

And Google got to write the history books, not AltaVista or InktoMe because of product technology, you go to market execution.

And so the idea of intensity is we know we don't have the luxury of patience.

If you're inventing a new concept, like maybe Facebook and Slack did, you exist alone because you've built a new way of doing something.

In a model where a lot of the technology is the rising tide that's lifting all boats, we could sit around and pontificate about the future and the world could move on without us.

And I think that was true in 1997.

And I think it's true now.

And we really wanted to reflect that in our values.

What do you do to up intensity inside the business?

How do you get more intensity in a business besides talk about it?

For me, it really comes down to urgency and caring about every detail.

And I think like all values, if you think about company values, is it a poster on the cafeteria wall or do you feel it?

I always bring up two of the values I really felt early on in my career at Google, don't be evil.

And it was really about how we thought about advertising and transparency around it.

I felt as a product manager at Google, we talked about it all the time.

And people were proud to do things differently than the status quo at the time.

And at Facebook though, this expression has been maybe understandably maligned, but this move fast and break things, which was the pace.

I remember going into Facebook and just feeling the pace, just feeling it.

You go in there and you're like, the first day every engineer shipped code to production and you're like, whoa, this is awesome.

This is so cool. And through the things that you do and your lived experiences at a company, you feel these values.

And so for I think about intensity, it's if there's a competitive deal, do you feel the depth with which every colleague you're working with cares about it?

When you're shipping a feature, do you just sense the urgency on getting it out there, having it be perfect in all aspects of your brand, your product, your technology?

Is there a sense of urgency and focus?

And I think like many things in a culture, you reflect what you feel around you.

And so I think it starts with Clay and me, you feel it from your colleagues and you come in and you feel that intensity and then you can reflect it back out.

What about craftsmanship, which seems maybe at first blush, a little bit in tension with intensity?

Craftsmanship is always something I've admired.

When I think of the company that represents craftsmanship, the most to me would be Apple.

There's that famous story, I think it was of Nex, not Apple, where Steve cared about the inside of the workstation, not just the outside and like how it looked.

And famously, I think cared about, list the aesthetics and layout of the factory floor.

Like any of these things, there's probably bad caricatures of these values, but what's interesting about Apple, whether you go into an Apple store or visit their website or unbox one of their products or turn it on, you can feel the craftsmanship, the details are right.

I think that this is a stereotype, but I think that if most people think about the products that are in their lives that are well -crafted, almost universally, you'd pick consumer products.

And it's in part because there's really direct correlation between sales and craftsmanship and then the consumer world, like a Sonos speaker, being just incredibly well -crafted.

In enterprise software, often the products that you use are not well -crafted.

And it's in part because typically the buyer of enterprise software is distinct from the user of enterprise software, not always.

As I mentioned, some of the product -led growth companies like Slack, that's different, but it's by and large true.

And so it become backhanded joke in software circles about the enterprise software you love to hate.

And it does the job, but it does so with such clunkiness and elegance that it's embarrassing.

I think as we're building this new type of software, which is helping companies build AI agents, the craftsmanship in every interaction with CIRA, whether it's a slide or a phone call or a document or a product, if you feel that the details are right, you have trust that we're gonna get all the details

you don't see right as well.

And we really felt that was important, particularly in a area of software that is so new and we're an upstart in this world and a startup that I think it would just help us in developing trust with what we're building and also be a place where product designers, engineers would be proud of the products

that they work on, which I think is really important.

How do you keep yourself from being overwhelmed?

I know that you care tremendously about your family and spending time with them.

You're building an ambitious business that requires intensity, which often equals time.

You're an important player in other huge businesses like Shopify and OpenAI.

That's a lot going on and I'm sure you love it all, which is a big reason that you do it and you get to learn at a crazy pace.

How do you keep the dam from breaking with all that responsibility and all that action?

I'm not sure I'm perfect at it, first of all.

I think I am like many focused and intense people not perfectly balanced in all ways, nor do I really try to be.

I always think that people's strengths and weaknesses are often strands of DNA.

They're quite intertwined.

One of the things I try to do is recognize my own strengths and weaknesses and try not to fight gravity.

I am who I am, but broadly to answer your question, how do I attempt to try to bind balance is intentionality.

So I think that especially in the age of push notifications and email, often you can let your interactions with others define how you prioritize your time.

That's a choice. If you're gonna choose to be inbox zero, that's a choice.

It's a completely rational choice, by the way, but your time is going to be a function of how many people are sending you email.

And so you're not in control of that time.

Similarly, if you have a really intense job and you wanna have dinner with your kids, have dinner with your kids, it's just a choice.

You can go home or not go home.

You can say yes to dinner meeting or no to a dinner meeting.

One of my mentors, Susan Wojcicki, just passed away and was famously would never take a dinner meeting.

So she could be home with her kids and she was the most powerful executives in Silicon Valley.

I would just say that I think a lot of people present things as choices not available to them.

And I'm not trying to be insensitive to the power hierarchy of where you work or anything like that, but everything is a choice.

And so I really tried to be self -critical and accountable about the choices of how I spend my time.

I try not to pretend that anything is not a choice.

You can quit any job.

You can abandon your family.

Probably neither or something that most people wanna do, but everything is a choice.

And so I try to not let the world happen to me.

It's very taking me a long time to get good at saying no.

It still feels painful, but I've gotten better at it.

So intentionality is the short answer.

Coming back to agents where we started, what question or questions would you encourage companies to ask of themselves on the dawn of the sort of agent era?

I'll start with maybe a broader question to ask and then talk about the first step because for whatever reason in my head they were distinctive and I wanna answer both.

So there's a author and business thinker named Clayton Christensen, who wrote a book called Competing Against Luck, which created this framework called Jobs To Be Done.

The idea of Jobs To Be Done is that as a company, you really need to say what job is my customer hiring me to do?

The example that I'm probably screwing up is they were consulting for a fast food restaurant that was trying to increase milkshake sales.

And they were saying like, how can we improve the recipe of our milkshakes to make them sell more?

They ended up doing a study where they discovered that a lot of people were buying milkshakes in the morning because it was a very portable item in a commute, easier to eat than like a sandwich when you're on a long commute and fill you up.

And then there was parents in the afternoon who were buying milkshakes to basically appease their kids.

I don't actually remember the anecdote precisely, but they started promoting milkshakes more in the morning and making smaller size for the kids in the afternoon or something and basically recognizing that changing the recipe was not going to actually increase sales because you conflated the taste of the milkshake

with what is the job your customer's hiring them to do, which is to provide sustenance on a long commute and to provide a way to make your child happy in the afternoon.

And if you frame it with the value that you're providing, you might solve a different problem than the recipe of the milkshake, which is the instinctive yet incorrect thing that you would change about a milkshake to have it sell differently.

I think in the age of massive technology disruption, it's very important for companies to understand what is the value that we're providing to our customers.

By the way, a great example of this was it was an earnings call from Netflix years ago.

I didn't hear it, but I saw a recollection of it where I think Reed Hastings mentioned that the greatest competitor Netflix at the time was Fortnite or something.

I'm probably again, screwing up, they said.

And it was because the job of Netflix wasn't to stream a movie.

The job was entertainment in the evening.

And you're going to choose between, do I want to play Fortnite or do I want to watch a film?

And it means that your main competitor might not be HBO.

Your main competitor might be this gaming platform.

So in the age of technology, I think so many companies end up organizationally and psychologically conflating what they do and the value they provide with how they do it.

And it's often a huge pitfall because you end up constraining how you respond to technology disruption through the lens of your existing delivery model or organizational model.

And the companies that have a very crystallized view of why they exist, why do our customers talk to us, what value are they getting?

It can become so much simpler to learn how to apply technology because you don't view the way things are done as precious.

You understand how you provide.

And I think that really needs to start at the top and really have an understanding.

It's uncomfortable for individual employees sometimes because maybe the thing you're doing is an artifact of the current technology ecosystem that could change.

But if you buy into that vision and have a beginner's mind about the different roles of the company, you can get on the train, right?

You can re -skill, you can find new opportunities.

So I think that's the most important thing is what is the job our customers are hiring us to do?

What will be different in the age of AI?

What will stay the same?

And how do we map a path from point A to point B?

In terms of getting started, I think the two things that I would do that are probably true across industries are number one, build a customer -facing AI agent so that your customers are experiencing an AI version of your company.

I think that's just like having a website in 1996.

You can start small.

I think I remember a lot of websites in 1996 were like, here's our phone number.

But you have a .com on your business card and I think having an AI agent is really meaningful.

And number two is open the door to using AI at your company, whether it's coding assistance, chat GBT for your employees.

Think about it just the emergence of a spreadsheet and finance.

The more your company is not only not discouraging the use of these models and day -to -day use, the more your employees will be coming to you, with really meaningful ways to improve your company works.

And I'm not sure top -down is important, but actually I'm a huge believer that, especially at larger firms, it's often the people on the ground where the real problems are, how to apply these technologies in meaningful ways and empowering and providing the structure so you can empower your employees

is just hugely impactful.

Your companies are the ones that I'm watching to see.

What is the next generation of this technology enabling?

It's been so fun to hear all the ins and outs of it here with you today and just learn from your experience.

I always ask the same traditional closing question.

What's the kindest thing that anyone's ever done for you?

My wife saying yes, that she'd marry me.

Super simple. It is.

Thank you so much for your time.

Thanks. If you enjoyed this episode, check out joincolossus .com.

There you'll find every episode of this podcast complete with transcripts, show notes, and resources to keep learning.

You can also sign up for our newsletter, Colossus Weekly, where we condense episodes to the big ideas, quotations, and more, as well as share the best content we find on the internet every week.

["The Professor of Science"]

[AI 에이전트의 시대: 브렛 테일러(Brett Taylor)와의 대화]-[Bret Taylor - The Agent Era - [Invest Like the Best, EP.386]]

📋 Summary

AI 에이전트의 시대: 기술의 새로운 패러다임과 기업의 미래

1. '신화적인 맨먼스(Mythical Man-Month)'와 소프트웨어 개발의 본질

2. AI 에이전트란 무엇인가?

3. 기술적 도전과 '에이전트 개발 수명 주기'

4. 진정한 고객 중심과 에이전트의 설계

5. 미래에 대한 전망: 기술이 배경으로 사라지는 세상

🎯Key Sentences

📝Key Phrases

📖 Transcript