Skip to content
a16za16z

Amazon CEO Andy Jassy on the $220 Billion AI Buildout

Amazon expects to spend roughly $220 billion in CapEx in 2026, yet CEO Andy Jassy says the company is still leaving meaningful AI demand on the table. He believes the buildout could ultimately help make AWS a $1 trillion annual run-rate business. Andy joins a16z co-founder Ben Horowitz and Erik Torenberg to discuss why AI demand is growing so quickly, how Amazon decides how much infrastructure to build, and why lower inference costs could unlock broader enterprise adoption. They also discuss how AI is reshaping Amazon itself, from smaller teams building products faster to reimagining Alexa, and why Andy sees cybersecurity, human judgment, and critical thinking as increasingly important in the AI era. Timestamps: 00:00 Intro 00:47 Five years as CEO: from pandemic overbuild to the AI boom 09:38 How much AI CapEx is too much? 15:44 Is the backlash against data centers fair? 20:56 AI demand as a barbell, and the capacity crunch 28:12 Annapurna Labs and Amazon’s custom chips 33:36 Why Amazon invested in Anthropic and OpenAI 37:14 Smaller teams, faster security: rebuilding orgs for AI 46:29 Rebuilding Alexa and reinventing existing products 53:06 Advice for an 18-year-old 56:36 How Amazon avoids spreading itself too thin Resources: Follow Andy Jassy on X: https://x.com/ajassy Follow Ben Horowitz on X: https://x.com/bhorowitz Stay Updated: If you enjoyed this episode, be sure to like, subscribe, and share with your friends! Find a16z on X: https://twitter.com/a16z Find a16z on LinkedIn: https://www.linkedin.com/company/a16z Listen to the a16z Show on Spotify: https://open.spotify.com/show/5bC65RDvs3oxnLyqqvkUYX Listen to the a16z Show on Apple Podcasts: https://podcasts.apple.com/us/podcast/a16z-podcast/id842818711 Follow our host: https://x.com/eriktorenberg Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see http://a16z.com/disclosures.

Erik TorenberghostBen Horowitzhost
Oct 23, 20261h 0mWatch on YouTube ↗

EVERY SPOKEN WORD

  1. 0:00 – 0:47

    Intro

    1. SP

      Even spending $220 billion this year, we're leaving a meaningful amount of demand on the table. We always leave a certain amount for on-demand, but '26 is obviously sold out. '27 is largely sold out. A good chunk of '28 is sold out. The financial markets are saying, "Oh, there's not enough money in the world to finance these things." Everything we do in the world today, stock market, banking, healthcare, they're all using data centers. Our job is to try to figure out how to have as much capacity as we can. We have an opportunity to help across so many more customer experiences and make their lives better and easier every day. The big labs being willing to pay almost anything for power, cooling, chips. Well, [chuckles] maybe we should buy out the old guys and sell them to the new guys 'cause they'll pay us whatever.

  2. 0:47 – 9:38

    Five years as CEO: from pandemic overbuild to the AI boom

    1. ET

      Andy, welcome to the podcast. It's great to have you.

    2. SP

      Thanks for having me.

    3. ET

      So it's, uh, you're, you're five years into running Amazon, and, uh, you've done a lot, uh, s-since being here, and, and a, a lot is, is, is coming out as, as CEO. You know, right now, you know, t-two hundred and twenty billion dollars in, uh, in, in CapEx spend, you know, AWS grow-growing twenty, twenty-eight percent. The, the, you know, there-there's a lot that you've, you've achieved. H-how do you think about the ambition in 2026 as it relates to Amazon, uh, relative to, uh, 2021 wh-when you took over formally as CEO?

    4. SP

      Oh, 2021 feels, um, so long ago. [chuckles] It feels like, you know-

    5. BH

      Eight lifetimes

    6. SP

      ... a decade ago. Yeah. But, uh, you know, it's-- as you know, the world changes fast and, uh, you know, uh, if you compare it to 2021, you know, our, our overall top line's, you know, about eighty percent higher. AWS business about, you know, almost three times bigger. Our ads revenue is about two and a half times bigger. So the, the business has just, you know, grown quite a bit, and I, I think there are a few things that have really happened. You know, I think pretty quickly after I started in the role, which was on the tail end of the pandemic, in our retail business, we ended up with a real cost to serve challenge where we had built-- we had basically doubled the size of our fulfillment network, uh, that we'd built over twenty-five years. We doubled the size of it in about eighteen months, and then we built a last-mile transportation network the size of UPS in about twenty months. And whenever you build that quickly, um, you end up with all sorts of things that you, you don't have optimized, and we-- our cost to serve and our fulfillment network were not what we wanted. And, you know, it, it created a lot of challenges and angst and a lot of people at that time, I remember it was just a year or so, or a little less than a year into starting the job, people said, "Boy, what a terrible time to start," and-

    7. ET

      Mm-hmm

    8. SP

      ... "What bad luck." And, y-you know, I think in retrospect, it was really a great time to start and a, and a, and a real blessing because it allowed us to consider a bunch of things that we probably wouldn't have considered for many years, but they were really good ideas for our customers and for the business. And the biggest of which in our fulfillment network ended up being that we regionalized a flat national network, a fulfillment network in the US. We regionalized it, so we got items much closer to customers, which turned out to, to both lower our cost to serve because with shorter transportation distances while getting items to customers much more quickly. And that reevaluation of our most closely held beliefs during that time when we were struggling on cost to serve really unleashed, um, speed of delivery and a lot of demand in our retail business and a big piece of why we've grown as fast as we have there. You know, and of course, pretty quickly thereafter, just how AI exploded further on the scene. It's not like AI was new. I mean, we have been a-all doing machine learning for a long time, and there've been lots of waves of AI that were supposed to be the real tipping points. But, you know, you, you get to 2023, and, and you really see with generative AI a huge difference. And I would say our AWS business was growing really quickly at that point. Um, you know, we have the, you know, with the broadest functionality by fair bit and stronger operational performance and security and, um, you know, and I think a, a type of partner ecosystem that's different. We were the clear leader, and we felt like that business could be a few hundred billion dollars of, of revenue over a long period of time, figure over ten years. Now, we look at what's happening with AI and how, you know, every customer experience we know of is gonna be reinvented, um, with inference and AI. We actually think the AWS business, not only is it growing really rapidly, I mean, last quarter, we grew thirty-six point seven percent year over year on a hundred and sixty-nine billion-

    9. ET

      Wow

    10. SP

      ... dollar annual revenue run-rate business. Just the opportunities today are really striking. And, you know, I, I think if you layer on top of that the, you know, the seeds that we have of new businesses, whether it's, you know, how the team has progressed our Prime Video business, which is now, you know, a large and profitable business, or the low Earth orbit satellite we're building with Amazon Leo, or our autonomous driving ride-hailing service with Zoox, or our healthcare business, or what we're doing in robotics. You know, we just, we have an opportunity, I think, to help so many more customers across so many more customer experiences and make their lives better and easier every day. And, and, and that mission of trying to make customers' lives better and easier every day really unifies everything we're doing across the company.

    11. BH

      So, so a couple, couple of follow-ups on that. So one, you know, you kind of mentioned when you're building out the fulfillment network so fast that it's gonna be a little inefficient. It's gonna be, you know-- When you go that fast, there's some sloppiness to it. How do you-- And then you, you mentioned there was kind of angst around that internally. Like, from a CEO perspective, like, how do you communicate what you're doing without, like, lowering the cultural standard of, you know, I mean, A-Amazon's known for its excellence in operating efficiency, being frugal, all these kinds of things. But here you are going like, "We're gonna build UPS," and like that [chuckles] And so how-

    12. SP

      Yeah

    13. BH

      ... do you reconcile those?

    14. SP

      Well, what's interesting is, you know, we have this set of leadership principles that a lot of people know about. We have these 16 leadership principles, and a lot of these leadership principles, uh, you know, they, they're supposed to really-- and they do govern the way we think about operating as a team and, and culturally. But there are several that are in tension with one another, and sometimes people are confused with about that. But the reality is it just reflects the way the real world works. It-- nothing is, is really perfectly clean.

    15. BH

      Yeah.

    16. SP

      You're always making trade-offs. So if you go back to that time when we made the decision to build out the fulfillment network and the last mile transportation network that aggressively, that quickly, the question from the, you know, the team was facing is, we know if we go this fast, it's gonna be really hard. It'll probably be more expensive than if we went slower. Um, we will probably not get everything as, uh, optimally as we would if we went slower, but customers and sellers really need it. Like, so are we gonna actually shade on the side of, uh, enabling-- 'ca-remember back then-

    17. BH

      Mm-hmm

    18. SP

      ... in the early part of the, of the pandemic, we-- the-- no physical stores were open. I mean, if you look at the role Amazon played in everybody's lives-

    19. BH

      Yeah. It was

    20. SP

      ... during the pandemic, it, it wa- it was very seminal. And so we had to ask ourselves, are we gonna build fast and maybe not as optimally as we can with the trade-off of serving customers and sellers who are trying to, you know, also have businesses that, that, um, sustain themselves or not? That's the first decision you have to make, and we decided, as we, we almost always do, to sh- to shade on the side of customers. You know, and then it was, um, it was fairly obvious, uh, that w- as we were building, it was obvious that not everything that we were planning was going perfectly. We had a lot of-- You know, our fulfillment team was more in the office than most of the rest of the company, but still a lot of people that have to participate in a lot of the designing and the planning and the assessing, you had people all over the place and, and remote. And, uh, you know, and then now you're balancing the combination or the, or the tension of, uh, bias for action or speed and, um, you know, relentlessly high standards, which means you deliver at the cost structure and the delivery, um, and the design that, that, you know, you'd always planned for. And so again, you have to make trade-offs. We made the trade-off to s- to side with customers and to move quickly to be able to serve sellers and consumers, and we thought there'd be some amount of cleanup. Now, did we know exactly how the, how the topography would work out in, in the way it did? No. And there were certain things that, um, that we didn't have optimized that I'm not sure we foresaw wouldn't be optimized. But if you have good metrics and if you're a culture that's a truth-telling culture, which, you know, that is another really important part of our culture is that, um, we are-- you know, we get the data on the table, we get the issues on the table, we're direct with one another. We don't allow people to paper over issues. If you have that type of culture, it's, it's fairly obvious in the metrics, and it's fairly obvious in the discussion. And then you just have to go about figuring out, uh, how you want to improve it and which pieces are just kind of small productivity things and which are architectural pieces. We went back and really re-architected key parts of the network after we got, you know, that capacity installed that, you know, we, we-- was probably at the time for that team was, was maybe eight or nine on their list of, of priorities, but became a much higher priority in a way to actually get the combination of speed and cost.

    21. BH

      Yeah. Oh, fascinating. Um, you know,

  3. 9:38 – 15:44

    How much AI CapEx is too much?

    1. BH

      you, you kind of like at the beginning, you know, when you started A-AWS, you like [chuckles] started AWS, the-- i-it was kind of build it and they will come and that, you know, okay, you're building all this infrastructure and then you're gonna rent it. Um, and so they needed to come or you'd be in a lot of trouble. Uh, but this is that at a much bigger scale in that, um, you, you and others, but like I, I would say primarily you [chuckles] or, or at least you're, you're certainly one of the biggest players are building data center, uh, and chip capacity so fast that like the financial markets are saying things like, "Oh, there's not enough money in the world to finance these things." And then, uh, you know, and we just kind of saw that skittishness in like the core weave debt market and equity markets and so forth. Um, and so how do you know like how much is too much on that build-out given the demand is so steep and you're growing so fast? Um, and then there's a contention, um, for that supply chain that you're, you're kind of fighting for to get, you know, your cooling and power and chips and all that.

    2. SP

      Yeah, it's a very good question, and I wish there was an equation-

    3. BH

      [chuckles]

    4. SP

      ... um, that would make it simple. It would save us a lot of time as a team. Yeah, I th- I would say in the first wave of cloud, you know, when we started AWS, uh, it was-- I mean, there was a little bit of, uh... We didn't know if people would use it, um, so build it and they will come. But, but we had very good signals inside the company, which at the time, you know, this was around the years, you know, the early part of the 2000s. We had, um, teams that were not moving nearly as quickly as we wanted them to, even though we felt like relatively we moved quickly. But for us, we just couldn't understand why it took so long. And it just turned out that our, our product teams were spending seventy to eighty percent of their time on the infrastructure pieces, which didn't differentiate them, and only about twenty percent of their time on what differentiated the product pieces. And so we, you know-- And we realized every team was doing it and reinventing the wheel. And so we, we originally conceived of AWS to allow ourselves to move more quickly internally. And, uh, we figured if we built a set of, um, high scale, high availability, low cost, highly flexible building block services like compute and storage and database and content distribution, messaging, things like that, we would be able to build much quicker in our consumer business. And then we just Said we're pretty good, relatively speaking. Technically, probably other companies have the same issues. But even before we launched externally, we had so many teams internally interested that we, we, we knew we were on the right track.

    5. BH

      Mm-hmm.

    6. SP

      Uh, I don't think any of us anticipated it would grow as fast as it did externally. On the AI side, there were, you know, as you know, there have been these different waves of people saying, "This is the time. AI is finally here." And, you know, even maybe six, seven years before the generative AI wave, people felt like it was AI's time. We built a whole bunch of AI services that actually was a pretty good business for us in the AWS side, but nothing like what we're seeing right now. Like, in the early days of AWS, we, um, we felt like we were growing really fast, and we felt good about it, and we were about a $60 million annual run rate business after three years. In the first three years of this generative AI wave, our business, um, or just our AI business in AWS is over $25 billion in run rate.

    7. BH

      Right.

    8. SP

      So it's several hundred times faster.

    9. BH

      Yeah.

    10. SP

      So it's, um, uh, we just haven't seen anything like it, and then the question becomes how much CapEx do you want to invest to go after the opportunity? And, you know, what I would tell you is, you know, we've said this year in 2026, we expect to spend about, um, $220 billion of CapEx. By the way, I'll just tell you that I remember being at leadership team breakfast, you know, 15 years ago when we couldn't believe the telco company spent $50 billion in CapEx. We were like-

    11. BH

      Wow

    12. SP

      ... "I don't really spending that much-

    13. BH

      [chuckles]

    14. SP

      ... on CapEx." So these numbers are, um, you know, they're, they're kinda mind-blowing numbers. And, um, even spending $220 billion in CapEx this year, we're leaving a meaningful amount of demand on the table. We just... The, the thing that helps us here is that we, we have really good visibility, uh, into customer demand. And so if you think about the, the CapEx investments in AWS and the way the cash cycle works, there's two macro areas. There's the investment for data centers, and then there's the investment for, uh, for servers and networking. The data center piece, you have to invest, you know, about two years in advance of when you can put servers in the data centers and start to monetize them. The good news is you only make that investment once. It's a useful life asset that's about 30 years. Um, but, um, but you make that a couple of years in advance. The server, um, and networking gear, it's only a few-- Depending on the component, it's only a few months in advance. So you have very good visibility into customer demand before you pull that trigger. And if it turns out you don't actually need the capacity to fill those data centers, you won't, you won't buy the server networking gear. That, on average, they, you know, they, they tend to break even, uh, in about three years, and they have useful lives at this point of about five to six years. And most of the deals we're doing are about five-year deals. And so when you are building as fast as we're building with so many data centers simultaneously, you're gonna spend a lot of capital, and your free cash flow is gonna have headwinds in those years until you get to that, those later stages w- you know, a few years down the road, where all those data centers are online, and they're all being monetized, and you're making back your money from the server and the network investment. But it has, because of the way the cash cycle works, it has headwinds in the early years when you're growing that fast.

  4. 15:44 – 20:56

    Is the backlash against data centers fair?

    1. BH

      So a-a-actually, on that, you know, data centers, [chuckles] going back when you started AWS, were probably the last thing in the world that you would believe would be a political issue. Um, but [chuckles] here we are. Uh, and particularly in the United States, you know, it, it's funny, and I'm sure you've experienced this, but nobody anywhere in the world is as anti-data center as the, uh, kind of U.S. politics for whatever reason. Um, so how do you... You know, how does that end up affecting this... I, I guess, is there, is there any merit to the anti-data center argument? And then, um, you know, how does that kind of inform your strategy of what you built here or, you know, and what you built in the other regions?

    2. SP

      Yeah. Well, I mean, I-I'll just give you s-some of the context that I have, or at least I believe, which is, you know, if you think about everything we do in the world today, w- you know, stock market, banking, healthcare, entertainment, shopping, education, business, you know, ride hailing. Like, everything we do is digitally driven. They're all using data centers in a very similar way.

    3. BH

      Yeah. No, everybody is... I'm anti-me. [laughs]

    4. SP

      Yeah. It's, it-

    5. BH

      I, I, I don't wanna use my phone anymore.

    6. SP

      [laughs] And, uh, and they, they all use data centers, and then that's before AI. And AI is the biggest technology transformation of our time, which I think is saying something since we've lived through the internet and the cloud and, and, um, and mobile. And so, you know, the reality is the type of infrastructure buildout we need to support the rapid growth we were just talking about on the AI side, it's... There, there hasn't been anything like it in the world and in this country since maybe when we built out the highways and bridges, you know, in the 1950s. I mean, that's the type of buildout we're going through. And the country, I think the world in general, but I'd say the U.S. specifically cannot afford not to build data centers, or we will find that another country like China will, will establish all the leadership and all the norms there, and I, I don't think any of us are gonna like that, either domestically or globally. So we have to build data centers. Now, do I think there are ways that we can be doing it better, all of us, as an industry than we have? Of course. You know, I, I think it's happening quickly, and I think everybody's learning together. But there are a number of what I would consider somewhere between, uh, myths and mistruths right now being propagated because it's, it's one of those issues where everybody... You, you have an easy villain And politically and, and sometimes opportunists like to kind of find that villain to point at. But, you know, I'll give you examples. The golf industry or the almond, um, farming industry consume way more water than data centers do. Just as a data point, our data centers, like golf courses consume two hundred times more water than all our data centers, and they consume more in two days than we do in a year in our data centers. So there's just a lot of... Like that's a good example. Or you can talk about, you know, people talk about pollution. What happens is when you, when you register new sites and you have backup generators, you have to register, uh, and show the amount if you ran all of those generators full-time at full capacity. But of course, it never happens. You only run backup generators .1 of 1% of the year, like ten hours a year for maintenance.

    7. BH

      Right.

    8. SP

      So like, you know, or, or you talk about the energy rates. You know, I- if you look in the different geographies in which we have a big data center presence, some of the energy rates have gone up, some of the energy rates have gone down. But the real issue is that as a country, we have not invested in the infrastructure of our grids the way we've needed to, like there's gonna be meaningful growth. And so something was gonna push it over to investment, and it just turns out that AI, because it's growing so rapidly, uh, and so significantly, is the thing that pushed it over. But building it out, of course, um, y- y- what you're gonna find is once you actually get that capacity, in most of the geographies, they're gonna end up, you know, the rates will flatline or go down as they have in Indiana or in Georgia or Mississippi. And so, you know, there are things that we can do that are, you know, the better. I mean, the other thing people forget about is in these, um, geographies, the big data center providers are paying a lot of tax. So look, if you look in St. Joseph Co-County in Indiana, we, we've paid about three billion dollars of tax. The communities get that money, and they get to spend it on things that really matter for those communities. So the communities get something out of it too. We've built programs like Built Together that we, you know, we just committed to another billion dollars in the communities in which we have data center pres-pr-presences over the next five years. And so, you know, I think you have to, we have to keep working on it with the communities. It has to be a public and private partnership. But the build-out is so important to the future of the country. Like imagine if we hadn't built out [chuckles] highways and bridges and, and what the economic prosperity and the capabilities of the country, um, would be. And, and we have to kinda keep it in perspective, and we have to, you know, be partners in the communities in which we, uh, build.

  5. 20:56 – 28:12

    AI demand as a barbell, and the capacity crunch

    1. BH

      Let's go back to the, the CapEx for a second. You know, the $220 billion is, you know, that's $600 million a, a, a day, um, just to, you know, put, put it in perspective.

    2. SP

      Yeah.

    3. BH

      I'm, I'm curious how you think about AI demand right now. Off, offline, we were talking about how you see it as a, a barbell, and, and maybe you can sort of situate or contextualize sort of the state of AI demand at, at the moment.

    4. SP

      Well, I mean, the first, uh, you know, the first context piece is what I said earlier, which is just, uh, I can't believe how, how big and fast AI has grown. You know, it's, it's, you know, a few hundred times faster than the beginning of AWS in the first three years. Twenty-five billion dollar run rate for us just in, in AI revenue in AWS in the first three years. So it's really large, and yet it really is barbelled if you look at how demand is. And what I would say is on one end of the barbell are, um, the, the AI labs who are consuming gobs and gobs of compute, uh, unlike anything I've seen. And, and then a f- you know, a few runaway apps, ChatGPT, CloudCode, things like that. On the other end of the barbell are enterprises who are largely using AI f- um, for cost avoidance and productivity, so automating customer service or fraud or business process automation.

    5. BH

      Mm-hmm.

    6. SP

      In the middle of the barbell are the current production workloads of enterprises. Um, uh, many of which are using AWS u- and, and using inference today, but I would say the overwhelming majority of which still aren't in any pervasive way. Like, you know, th- and that I think is gonna be the largest absolute segment of AI usage. And I think you're gonna see that. It's hard for me to predict the rate at which that'll happen. It's, you know, it's happening to a greater extent every year. But I think if you zoom out five years, five to seven years, and, and you look at what it'll be like... And I don't think it's gonna wait for five to seven years. It never happens in one fell swoop. But if you go- if you just zoom out five to seven years, I think that, um, quite a few, if not most of the enterprise applications that we use and that exist today are gonna be using inference in a pervasive way. And so there's just, there is a lot of growth in front of us.

    7. BH

      And how do you think about it? 'Cause, uh, there, there's kind of this impending data center chip memory everything shortage, uh, that's upon us in really 2027, just because, you know, everybody's building now [chuckles] but it's not gonna be ready, uh, necessarily by the end of the year, and demand's not slowing down at all. And so when faced with... How, how do you think about it when faced with like, um, the big labs being willing to pay maybe anything or almost anything for power cooling chips, you know, kind of the environment, and then you've got these kind of all been rin- been around a long time customers who are paying their regular rates, um, y- you know, to run their businesses. Uh, is there, like, any business pressure to go, "Well, [chuckles] maybe we should buy out the old guys and sell them to the new guys 'cause they'll pay us whatever. And the old guys, you know, I can't double their prices. That wouldn't be fair." Or like, how do you think about that? 'Cause it's such a-

    8. SP

      Yeah

    9. BH

      ... weird thing in that you've got people you've had in there for twenty years doing a thing that's Kind of, you know, as you say, probably going to inference, and then you've got these new guys who are, uh, like insatiable. They'll buy anything.

    10. SP

      Yeah. Yeah, it's a good question. It's, uh, um, w- you know, we don't think of it quite the way you're talking about-

    11. BH

      Mm-hmm

    12. SP

      ... but I can completely understand. There's... If you think about, there's only so much data center and power today.

    13. BH

      Mm.

    14. SP

      There's only so much memory, and I don't think that that shortage ends in 2027. I think-

    15. BH

      Yeah

    16. SP

      ... you know, I, I, I believe, you know, one of the reasons when coming back to the capital investment, why I think we can invest a lot more and it wouldn't be a bad use of, of capital is that, you know, '26 is obviously, at this point, sold out. 27 is l- largely sold out. We always leave a certain amount for on-demand in, in our inference service Bedrock or, or EC2, but largely sold out all the big chunks. A good chunk of '28 is sold out. Like, there's so much demand that, um, you know, it is, uh... And, and you can't, uh... We have-- If you think about the AI business and what we call the core business, which think of core as non-AI, they're both growing at really rapid rates right now. And you know, if, if you have only a certain amount of memory, you have to decide how much of the memory you wanna a- you know, you wanna allocate to, to HBM, you know, to the, to the acce- AI accelerators versus, um, to, um, DRAM, you know, in, into, you know, your core. So it's, uh, these are real trade-offs you have to make, but I would say that where we start on this issue is, um, being customer-focused. And for us, uh, we, you know, we have deep relationships and partnerships with our customers in AWS. And in the same way during the pandemic, unlike our competitors, who I think tried to figure out how to, how to optimize within quarters to drive revenue as much as possible in a, in a world where companies were gonna cost optimize, we took a different approach. We, you know, we proactively had our field go out and help customers figure out how they can cost optimize, even though we knew it would diminish our revenue, um, short and medium term. But, you know, we're gonna help our customers be successful 'cause our very strong belief is if we help customers over a long period of time, our business will come along with it. And that's the same thing here on the core. You know, I guess you could do calculations and decide that you have customers because of the scarcity and, and, and their willingness to pay would pay more to squeeze out your core customers. But they're, they're running their businesses on top of AWS. They're running all their core applications. We're not gonna squeeze our customers, and we're gonna make sure that they can scale. And then our job is to try to figure out how to have as much capacity as we can to allow not just our core customers, but all of our customers who wanna use us on the AI side, and people wanna use us on the AI side, um, to be able to do so and, uh, a- and do so in a way where, you know, it's su- it's sustainably economically for us as well. And so, you know, I, I wish I could tell you that I thought that the supply constraints would be just a 2027 issue. I think we'll see them in different components for several years. We are pro-- I think that we're probably putting more capacity in than anybody else 'cause we really contin-- we're, we are, um, very passionate about continuing to be the significant leader in the infrastructure and AI space like we've been. But, uh, as I said, it's, uh, you know, we're spending $220 billion or so this year, and we could spend a lot more, and it wouldn't be a bad use of, of capital. And, uh, both, you know, medium to long term, and I think we still probably wouldn't satisfy all the demand. There is just an incredible demand right now.

  6. 28:12 – 33:36

    Annapurna Labs and Amazon’s custom chips

    1. BH

      So k- kind of speaking of that, you, you did something back in 2015, uh, when you bought Annapurna Labs, which was probably before... You, you probably weren't really thinking, I mean, maybe you were, but about, like, giant AI demand in 2015, 'cause there just wasn't much AI demand in 2015. So kind of what drove that decision, and then how has it kind of paid off in this new world?

    2. SP

      Yeah. I think, you know, Anna-- the Annapurna team is one of the most talented teams and set of people I've ever had a chance to work with, and I-- it's one of the very best acquisitions we've done at Amazon in the history of the company, if not the best. Uh, and it was, uh, we foresaw some pieces, but I don't think that we... We did not make the Annapurna purchase for AI chips per se. Like, what, what, um, you know, when you get to a certain scale, uh, you start to have access and visibility to patterns of customers at very large scale that you, you th- you realize if you can vertically integrate and, um, and you could build, um, certain capabilities yourself, you'll be able to provide more value for customers and, uh, you know, and, and better economics for the business itself. So what Annapurna started as for us was just, um, on the kinda core EC2 server. We felt like we were using too much of the server for virtualization and for networking and for security and for storage, and we wanted to be able to use as, nearly 100% of the server for compute for customers. And so we, we had been working with Annapurna before we acquired them on this NIC that offloaded those components to the NIC to allow us to have as much of the server for compute as possible. And we really liked the team, and we really liked the product that we collaborated with them on together. And we, we realized we were gonna buy-- that was gonna end up being in virtually every EC2 server, and it's turned out to be in every server we have. So we originally bought it because that was gonna be a core capability of our compute capabilities, and because the team was so talented at building chips, we felt like they could probably build other chips too. And we, at that time, we had this very deep partnership, which we still have a deep partnership with this company, w- with Intel. But yeah, Intel had virtually all of the CPU share, and when you have a, a partner who has virtually all the share, they're not often thinking about how to drive price performance. They're, they're trying to think about other features that allow them to get more share and drive more revenue. By the way, it's totally understandable. These are some of the dynamics of, of how markets work. It's part of how the innovator's, innovator's dilemma, you know-

    3. BH

      Mm-hmm

    4. SP

      ... um, um, comes up. And so, uh, we had tried to, to push on price performance, and it was hard for us to get attention there. But we had customers who wanted to move more and more of their on-premises workloads to the cloud, and they wanted better price performance. And so the next thing we turned that Annapurna team loose on was to build a CPU chip, and that they built Graviton, which, um, uh, 99% of our top thousand EC2 customers use it very pervasively today. It's about 40% more price performant than other X86 processors. And so that has been hugely impactful for our customers and, and for our business. And we just, a few years ago, we saw that same movie in the AI space, where you really had one dominant provider, um, who's very good, and we have a d- we had a deep partnership with, we still have a deep partnership with, we will for as long as I can foresee. But they have giant markets and, and, and lots of, um, different products they're building and priorities, and we knew our customers needed better price performance. And that's why we, we spun out a separate team in Annapurna to build an AI accelerator, which we call Trainium, which is also about 30% to 40% more price performant than the other comparable, um, um, processors. And, you know, I think when you talk about that middle of the barbell we were just talking about, if you ask what are the, what are the things that will change that middle of the barbell to have more of those current enterprise production apps using inference? A really bi-- There are a couple things. You know, some of it is, you know, some of the talent that's comfortable doing post-training and fine-tuning and some of the talent and organizational muscle that knows how to prioritize what to go after and how to do it. But a, a big, big chunk of it is the cost of inference. The cost of inference has come down quite a bit in the last few years, but it's still an order of magnitude too expensive, in my opinion, for it to be used as pervasively as possible. Because if you're asking enterprises to rewrite their applications that use CPU today with AI accelerators, if the difference in those costs are very significant, the amount of incremental benefit they have to get from having the AI accelerators on there is a much higher bar to wanna rewrite those apps. But if you can take the cost of inference down, that bar is much lower, and all applications are gonna be better and smarter and more capable with AI accelerators and inference. So that is a really important part for customers to being able to use AI pervasively is driving the cost of inference down, and our chips business is a big piece of that.

  7. 33:36 – 37:14

    Why Amazon invested in Anthropic and OpenAI

    1. BH

      Yeah. Yeah, no, it has-- [chuckles] I, I, I can tell you from, uh, our own firm that it is, it can get very expensive. We, we had one employee, uh, spend $2 million [chuckles] in the last... Anyway, doing good work, right? [chuckles]

    2. SP

      Yeah.

    3. BH

      I was like, "Okay, this inference is not that cheap." Um-

    4. SP

      Yeah.

    5. BH

      So, you know, one of the things that you've done is you've, you, you've made some investments, um, particularly in Anthropic and OpenAI, like very large investments, I think. Like 18 billion in Anthropic and, like, 50 billion in OpenAI or something like that. And so, um, kind of what got you to wanna do that? You know, that-- and, and that, um, you know, that and kinda similar investments from NVIDIA and so forth kind of got, uh, Wall Street up in a tizzy 'cause it reminded them of, um, the bad old days of the, of the dot-com boom and so forth. Uh, how did you think about that, particularly since they are also customers, um, and y- you know, why did that make sense for you to-

    6. SP

      Both of those companies are, are, are really impressive teams and really impressive companies. And, uh, the rate at which they've grown their businesses, at least in the top line, I don't know if we've ever seen anything like it. It's, it's, it's really-

    7. BH

      Yeah

    8. SP

      ... it's unbelievable. And, you know, so to us, it's a combination of, uh, who these teams are, the, um, the technology and the models that they've built and some of the applications they've built, our belief in how transformative AI is, the fact that we believe these are gonna be two of the most successful companies in this space over a long period of time. And they're gonna be lots of-- They're not gonna-- Not everyone's gonna be a winner, but there are gonna be a lot of very successful companies in this space, you know? But we believe these will be two of them. And then, you know, the fact that we partner so closely. I mean, we-- You know, I would say that if I start with Anthropic, where we've had the longer partnership, uh, you know, we have so many customers that run Anthropic in Bedrock, in our inference service. Um, and, you know, I, I think that, um, it is-- I think customers are most successful running Anthropic in Bedrock. Um, we have had a deep partnership with them on chips, you know, where they have build-- been building on top of Trainium for a while. And I think it's been very good for Anthropic. I think it's been very good for our Trainium team. I think we've both learned quite a bit from each other. Um, so we have, you know, we have a deep partnership with them, um, where, uh, you know, both our belief in the future of AI, the belief of those companies, and the partnership, it made sense for us to make investments as part of those partnerships. You know, and then on the OpenAI side, we just had so many customers who wanted to use OpenAI and AWS, and they weren't able to do so because of their prior business arrangements that they had. And the, you know, for a long time, I think the companies had a lot of mutual, uh, respect and, and, um, and desire to work together. And so this is another one of those where over a series of, of conversations and months Uh, the ability to be able to run OpenAI, um, in Bedrock. The-- You know, we built a unique product together in the stateful runtime environment, which is how I think all agents are gonna be built moving forward. You're gonna need state. Like Anthropic, they made a, a multi-year, multi-gigawatt commitment to Trainium. Um, and we just believe that that is gonna be one of the most successful companies in the space over a long period of time. All those made it make sense for us to have deeper partnerships and, and investments.

  8. 37:14 – 46:29

    Smaller teams, faster security: rebuilding orgs for AI

    1. BH

      Switching over to kind of how you use AI to build a company. So, um, I think you said the Bedrock team rebuilt, um, your inference engine with six engineers in seventy-six days, and that would've taken forty people a year. So that, that's pretty different. Uh, and you know, Amazon is kind of famous for the two-pizza teams. [chuckles] Um, so like, like what is the org... What, what is your current organizational design thinking, um, given the technology? Because it, it does seem to really change things, and it's making... You know, we got like super, super specialized over the years with, you know, designers and product managers and, you know, front eng-engineers and backend engineers and this and that and the other. And now all of a sudden, like, everybody's a r-Renaissance person. Um-

    2. SP

      Yeah

    3. BH

      ... and so h-how do you think about that in terms of org design?

    4. SP

      Yeah, I agree with what you're saying. It's, uh, I think that the Bedrock experience that you alluded to was very eye-opening for everybody here. And when we, we spent a bunch of time sharing that story internally to, um, inspire people and remind people what's possible because over time, what ends up happen-- I mean, I started the company twenty-nine years ago.

    5. BH

      Mm-hmm.

    6. SP

      I started as a assistant product manager, and I was the product manager for, I don't know, five products. Today, when, when companies get successful, and they get bigger, and the products get bigger, you end up where, you know, a product manager works on one product, and they just own one slice of it. Like, they own pricing or they do like... Everybody becomes more specialized, and everybody accepts that that's the way you have to do business if you're building something big and successful, and it's not. And it's definitely not when you look at what's happening with AI. And, uh, you know, I even just this past, uh, if I look at the last week, um, we're, you know, we're working on some things, um, you know, around, uh, agents in our consumer business. Uh, we have a whole, a whole bunch of investments there, but we had an idea that we really liked that we agreed on Thursday we were gonna try and have, like, a real working prototype for that, again, we had four or five people who over the weekend had a, had it operating in a eighty percent, um, uh, shippable way by Sunday. Like, that is a really-- Those are different worlds that you live in. And so I think what it means for the future of organizations, um, is I, I think, number one, I, I, I think that, um, uh, we're gonna have fewer humans doing the work that they're doing today, um, in the future than we have today. You know, just if you look at the amount of coding that's being done agentically, you look at the amount of customer service and business intelligence and research, and, um, uh, you fast-forward to just thinking how spreadsheets are gonna be built, like the number of lawyers you h-- Like, I just think you're gonna have... Y-you're not gonna have no people, but you're not gonna have as many humans as we've all thrown at scale as businesses have gotten bigger in the future. There are gonna be different jobs and new jobs, some of which we know about, some of which we don't know about, that will, um, arise as AI and robotics and space develop. Like, you know, there are gonna be all sorts of, of new jobs, but we're gonna have fewer humans doing what they've done today. I think the teams will be, um, much smaller than they are right now. You know, I, I think you're gonna have smaller teams that have, um, they, they have people who can work cross-functionally. They don't only one you-- They don't only own one sliver because the models are gonna be able to get them eighty percent of the way there on a lot of these, um, different functions. I think that every team will start at a much more advanced stage than we have in the past, and so I think you're gonna be able to invent much more expansively and much more quickly. I do think there's a bunch of things that have to change. I think that, uh, you know, the, the startups starting today, most of them are starting agentically and agent nat-- you know, um, uh, y-you know, agent native, um, or AI native right from the start. All the larger companies who've been in business for a while are gonna have to figure out how to actually build at that same pace, and I think that, I, I, I think that some of them will figure it out, and, um, and you always like when you have a, a, a, a big business with a lot of capabilities and a loyal customer base. Some of them will move very slowly to figure it out, and they will be more vulnerable, in my opinion, to startups. But you're gonna-- I think you're gonna have to r-- I predict that companies will have to rewrite a, um, almost all of their code to be agentically capable. Um, they're gonna have to allow agents to be updating different pieces of code. You're gonna have to build constraints there. I think if you just look at security, uh, you know, security is-- I mean, it's kinda interesting. If you look at all of the nervousness of the last month or two about models, they are focused on the more fantastical scenarios. Um, and by the way, they're possible. Like, is it possible an evil botnet will take over, you know, everything? I mean, that's, I guess it's possible, and it's possible that you can infuse robots with, um, you know, with malicious intent. They're all possible. I personally think we're gonna figure that out together, you know, as an industry and-

    7. BH

      Mm-hmm

    8. SP

      ... private public segment. But like-

    9. BH

      I think you gotta start by paying attention to some of the things. [chuckles]

    10. SP

      Yeah. But I mean, the thing that's interesting is that I don't think that there is enough discussion about the more Immediate term risks, which are really around cybersecurity.

    11. BH

      Yeah.

    12. SP

      These models are so-- They find so many more vulnerabilities than you did before and that humans, you know, weren't finding. And, and maybe you could argue if they could or couldn't, but they just weren't finding. And so if you fast-forward then, I think that the way that applications are gonna have to be able to respond to imminent security threats is, is gonna be in minutes. You know, and today, if you think about it, you know, you find vulnerabilities, people classify the vulnerabilities, people develop patches. And then even if you do that part quick, most companies take a long time to deploy because there are all these dependencies. You're gonna have to deploy in minutes. And so if you don't actually have your applications rewritten to be able to be updated by agents, you're gonna have no chance in, in that new world. And so I just think, you know, all organizations are-- they're gonna be reinvented, and I think the companies that prioritize are gonna be in much better shape than those that don't.

    13. BH

      Yeah. And it, it seems like, you know, we, as an industry, did not do a great job of architecting everything from the big systems to, you know, embedded devices with, like, good security architecture. And the, you know, the day of reckoning is here. [chuckles] And I mean, I, I think the good news is that's a big opportunity for new companies, new efforts, um-

    14. SP

      Yeah

    15. BH

      ... people [chuckles] to do things. Uh, but yeah, it, it, it's-- Uh, uh, from what we're saying, it is the threat. Like, the theoretical, the thought experiment threats are, you know... Right. Maybe they'll happen, maybe they won't, but, but this is clear and present.

    16. SP

      Yeah. Almost every, uh, partner and customer we talk to on the AWS side, every company, um, of any size is worried about the security piece, you know. And, and, you know, we've, we've got a professional services practice where we're helping a lot of our customers, and we've built a service called Continuum that identifies a lot of these vulnerabilities and builds patches. But it's... You know, it, it's, it's easier to say than to do, and it, it actually-- Because a, a lot of companies and a lot of engineers sometimes, it isn't exciting sometimes to focus on-

    17. BH

      Yeah

    18. SP

      ... the security piece. It's easy to wait until there are problems. And if you protect data that matters, it's a bad idea.

    19. BH

      Well, and also, I think in most companies, the, you know, going back to our earlier conversation, specialization has probably been, uh, you know, the worst case in security, where you've got these very, very esoteric security engineers who don't like working with the other engineers, who, you know, are a scarce resource, and this and that and the other. And, you know, as a result, like, in most companies, in most software companies, their, their security practices just aren't that good for writing software. And I think, you know, that obviously has to change. And, you know, the good news is we have tools that will help with that, but...

    20. SP

      Yeah. And the, the good news part of it, to your point, is that you're gonna be able... You know, you have to hire pen testers. There's only so many security people you're gonna hire. There's only so many applications they can get to. The models coupled with automation are gonna allow you to get, you know, to be able to better, uh, um, pen test your entire surface, and you're gonna find things that you might not have otherwise found outside of a phook.

  9. 46:29 – 53:06

    Rebuilding Alexa and reinventing existing products

    1. BH

      So one of the things that y-you know, is, has been kind of interesting in us kind of looking at the market is you can do a lot of things with AI. One is you can, like, cut costs. You can reduce the number of accountants you have or lawyers or, or that kind of thing. Um, and there's a lot of... There's actually venture capital firms that now are like, "Okay, we're gonna go buy old companies and cut their costs." Um, and I have... That-that's never been that interesting to us 'cause we're like, "Okay, if that's your idea, you have very few ideas." [chuckles] Um, and then there's like, okay, we're gonna go build something the world's never seen before, and that's super exciting. But then there's a third thing which you've done, um, with Alexa, where you've had a product, um, a successful product, and you said, "Okay, let's, like, rethink this whole thing from the beginning, um, because we have this new platform." Y-you know, how do you get to that, and, and where does that make sense?

    2. SP

      Yeah. Well, I, I think that's actually an interesting delineation on the three, um, elements. And I, I think that organizations, as we just talked about, are gonna really change and get more streamlined. And if you, if you do it right, it will enable your really good builders in these small teams to build that second bucket you talked about, which are things that people haven't seen before. You're gonna be able to do it so... And when you have experiences like I was talking about earlier, where in four days you completely build a new idea that's, you know, eighty percent of the way there, it's so inspiring to people that they actually spend more of their free time and free thought cycles thinking about new ideas. That is, to me, is the-- it's, it's one of the most exciting parts of what's happening with AI. But I also think that for existing companies who have successful customer experiences at scale, that if they think about AI as primarily just incrementally improving the experience, they will very likely not have a-have the winning experiences three to five years from now. Because I think every single one of these experiences we know, even the ones that seem the most difficult to imagine changing, are gonna be meaningfully different with f-with AI In a few years. And so it means that if you wanna think more than incrementally, you have to find a way to get teams to um, reimagine from scratch what those applications look like if you were building it today with all the new technology available, like AI. And in s- in some cases it's-- Uh, to me, in Alexa it was f- I felt like it was fairly obvious that we had to do that. It was-

    3. BH

      Mm-hmm

    4. SP

      ... you know, the brains of Alexa were, um, really inventive at the time it was built, but the capabilities of what the brains could be were so different because of generative AI that you had to rewire the brains of Alexa if you wanted to be, you know, provide great customer experience and to be relevant over a long period of time. And so that was fairly obvious. By the way, even though it was fairly obvious, it was difficult actually with... You know, the teams, you know, are, are connected to what they've built and proud of what they've built. And, um, you know, hard-earned scars on the tenets of what works and doesn't work. And to try and get, get teams to completely start over and reimagine, it takes time. 'Cause teams will say, "Well, that's not how we've done it. We've tried that and that hasn't worked," or, you know. So, um, but I think what's harder is to take experiences, you know, take our other consumer exper-- take our retail business, or take our Prime Video business or our Fire TV business or our, you know, our Prime Music. Those experiences, they're not as obvious, um, that the technology has a much better solution today. But I, I actually believe every single one of those businesses we need to reinvent, and we have teams of people working on versions of those businesses that are totally reimagined. Now, do I think we'll get it right, um, uh, right from the get-go? Probably not. You know, uh, w- we'll find ways to iterate our way into it. But it's already yielding all sorts of, uh, new ideas and customer experiences that we think are very compelling. And then what'll be interesting is the race between do you, do you want a completely different experience that's like something-

    5. BH

      Yeah

    6. SP

      ... like a new app almost, or do those advance quick enough and you add them into the existing experience where you end up meaningfully changing the overall customer experience bit by bit over the next couple few years as you find elements that work. But I, I do think every one of these experiences has to be different in the next few years if you, if you, if you wanna be the successful leader.

    7. BH

      Yeah, that's such a tricky leadership problem. You know, it reminds me of, um, when I first st- began my career as an engineer. My boss, uh, I got into some argument with s-somebody about something, and my boss said, "Look, one thing you have to understand, Ben, is everything is up for discussion until the first line of code is written, and then it's religious." [chuckles] And, uh, I guess you experienced that with, uh, Alexa.

    8. SP

      Right.

    9. BH

      But, you know, it is, um, it is really interesting that... 'Cause all the knowledge, all the experience, all the things that went into building that original thing are now y-you're saying, "Okay, we're okay giving a lot of that up and, and going to this new world." And, uh, by the way, with the customers too, you know, you're gonna have some big set of customers that loves the current experience.

    10. SP

      Right.

    11. BH

      Yeah.

    12. SP

      Every single big transformation, at least my experience, maybe you have some examples that aren't. But e-almost-

    13. BH

      Yeah

    14. SP

      ... every big transformation requi- It's a huge change ma- Like, the technology and the product and the customer experience and the business elements have to be compelling enough to want to change, but then when that's true, it doesn't just happen. It's a huge change management. Like moving from on premises to the cloud, same type of transition where-

    15. BH

      Yeah

    16. SP

      ... lots of infrastructure leaders were really proud of what they built, and they knew it, you know, inside and out, and they were in the middle of the action, and they didn't wanna-

    17. BH

      Yeah

    18. SP

      ... learn something new or... You know, it, it's gonna be the same thing. It's the same experience I was just mentioning. It's gonna be true for, you know, trying to reinvent all your customer experiences. We're all proud of what we've built over the last-

    19. BH

      Yeah

    20. SP

      ... you know, 10 years and these experiences. And we all have 100 things that could make them better, that we're all excited about, and we spend all our waking hours working on.

    21. BH

      Mm.

    22. SP

      But think about how do I completely start over is, you know, it's intellectually and emotionally hard to do.

    23. BH

      Yeah. No, no doubt. No doubt.

  10. 53:06 – 56:36

    Advice for an 18-year-old

    1. ET

      A-a-and the-- We, uh, just incubated Horowitz and Dreesen Academy, uh, a few weeks ago to help young people prepare for this transformation we're, we're talking about. You, you, you've said how, you know, AI makes building easier, but young people still need to learn, you know, re-real expertise. I'm, I'm curious if, if you were 18 in 2026, what advice might you have for yourself about how to prepare for, for this, uh-

    2. SP

      Yeah

    3. ET

      ... transformation that we're entering?

    4. SP

      Well, I have a 25 and a 22-year-old, and so I guess the 22-year-old was 19 when this was starting to really take off. And, uh, I learned very quickly that you can't tell them not to use AI in education.

    5. ET

      [chuckles]

    6. SP

      Like, that, that, you know, that ship has left the station, or that train has left the station. And, uh, I think universities would be wise not to fight it. I, I just think it's, it's a tool that people are gonna use. And yet, at the same time, I think all young people and, and, you know, and I would say for us, where we have a lot of people who, you know, we have a writing culture, who are using AI to write, you can tell when something's been written by AI. You know, it's, it's, uh, it's not quite right. The pieces aren't put together quite right. And, you know, and so w- the advice I would give somebody young, and I gave my kids, was, "You can't run away from it, you know, and you can't wish it away." Like, you-- It, it's, um, uh, it's gonna be incredibly impactful in your life, in every experience that you, that you try and use in your work. Uh, and, and it will allow you to invent in ways that you-- that just weren't possible for us, you know, um, before it. And so you really sh- you need, you need to learn about it. You need to educate yourself about it. You need to use it a lot. You need to try it. Try Try doing things that are outside of your comfort zone. Neither of my kids were developers, but they have, you know, used AI to, to build applications. Uh, and use it as kind of the focal point of how you operate your day and how you, how you, you use, um, tools at work. But, uh, I, I don't think it replaces critical reasoning and thinking, and I, I think this is true for, um, for universities. I-- You know, in many ways, if I, if I think about, if I think about business school as an example, you would get these three cases that you ha-had to analyze every day, and you had, you had to do a lot of reading, and you had to take notes, and you had to figure out what the key issues were, and then you got all these exhibits, and you took notes on those, and then you had to kind of put together what you thought the plan should be for that company. And, you know, oftentimes there were a bunch of people who just didn't do the work. You know, they just didn't do the reading or the research or the note-taking, and that-- all that kinda goes away with AI. AI is gonna be able to kinda get everybody to that starting, that advanced starting spot much more quickly. But I would also say that the actual putting the dots and the pieces together, either to build a strategy or an approach or a plan or a new product or a new customer experience, I don't think AI is gonna, you know, do that for most people most of the time. I-- It's not that it'll never happen. I still think you're gonna need, um, human judgment and ingenuity and invention and experimentation and thinking about how all the pieces come together, uh, to end up, um, building amazing experiences and businesses. And, and so I, I, I think you wanna use the tools, and they're gonna be huge aids, but I still think critical reasoning and thinking is gonna be very important in everything we do.

  11. 56:36 – 1:00:24

    How Amazon avoids spreading itself too thin

    1. ET

      Yeah. Yeah. I-- Gear-gearing towards closing here, uh, you know, y-y-you guys are in businesses as d- as diverse as satellite connectivity, robotics, h-h-healthcare. Uh, I mean, the ambition, it, it's incredible to think this business started as, uh, you know, selling books on, on the internet, um, and, uh, and here it is now. H-How do you think about sort of, you know, either what, what threads these, these, uh, sort of diff-different, uh, sort of business lines together or how you think about what business lines are worth, you know, committing for years or how do you make sure you don't spread yourself too thin or h-h-how do you make sense of just the, the vast range?

    2. SP

      Well, uh, I'd say a few things. You know, first, uh, I think we are living in, um, in an era of three of the biggest transformations in our lifetime, and maybe ever, between AI, robotics, and space development. And they're all huge, and they all are gonna completely change, um, a number of customer experiences that we all encounter. And we are in the middle of all three of those big transformations. If you look at what we're doing in our retail business and you-- and how we use robotics and what we're doing, uh, on the AI side, you know, both in making it easier for internal and external builders to be able to, um, build successful AI applications and agents, as well as reinvent all our consumer experiences. If you think about, uh, Amazon Leo, our low Earth orbit satellite, um, constellation that we're building for the five hundred million households around the world that don't have broadband connectivity. You know, there is, there's an incredible set of transformations that are happening that, um, that we have a chance to, um, to help customers leverage in a way that makes their lives better. And, uh, you know, and, and we, we do it in a way that help, help customers but also lead to long-term sustainable businesses for ourselves as well. And, uh, we've-- you know, I think we have a chance to be much more relevant, um, in helping customers across many more areas. And that, you know, I'm not even mentioning what we're doing in grocery and what we're doing in, you know, autonomous driving, ride-hailing, and healthcare and... You know, there's, um, you know, w- the way we organize, we, we've often had over the years this internal debate, um, but also a lot of external folks have asked the same type of question, which is what's being spread too thin? I think some of that depends on a combination of how you organize yourself and what you're willing to invest. And so because we don't try and have the same group of people manage multiple businesses, and we organize in this decentralized single-thread way, if you have the right leaders and the right builders on those teams, and you have an experience that if it's big enough could move the needle, and you have a differentiated idea, and the space is not being that well-served, you have the opportunity to pursue a lot of these things simultaneously, and we, we have over a long period of time. And then it just comes down to how much you're willing to invest. You know, there are some companies, very understandably, who say, um, "We're gonna stick to our knitting. You know, we're gonna stick to the core business that we have, and we're gonna grow that." And that, by the way, can be a very successful strategy, and, um, and we are very intent on, uh, our existing businesses, continuing to grow them and build them. I think we've done so pretty successfully at a good clip. But there are so many other customer experiences that we know customers really want us to help solve that we can. They're gonna help our customers and change our business long term, and, and, you know, we'll keep pursuing those.

    3. ET

      That's an inspiring, uh, note, note to end on.

    4. SP

      Yeah.

    5. ET

      It's an endless ambition. A-Andy, thanks so much for coming on the podcast.

    6. SP

      Yeah. Thank you, Andy. Thank you for having me. I appreciate it, guys.

Episode duration: 1:00:38

Install uListen for AI-powered chat & search across the full episode — Get Full Transcript

Transcript of episode -YMMRQ1qscI

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.

iOSAndroidClaudeChromeChatGPTComing soon