a16z Podcast - Cloud Wars, Company Wars, and Innovating Through Change

Episode Date: September 7, 2022

In this episode from October 2021, Michael Dell, founder and CEO of Dell Technologies and one of the longest serving founder-CEOs in the technology industry, joins a16z general partner Martin Casado, a16z co-founder Marc Andreessen, and host Sonal Choksi on the occasion of Michael’s book, Play Nice to Win: A CEO’s Journey from Founder to Leader. There are lots of challenges in being public while trying to innovate, and limits to being a private company as well; but it's rare to see a company go public then private then back to public again. As is the case with Dell Technologies, one of the largest tech companies -- which went private 2012-2013 and then also pulled off one of the most epic mergers of all time with Dell + EMC + VMWare 2015-2016 (and which we wrote about here at the time).Is there a method to the madness? How does one not just start, but keep, and transform, their company and business? Michael, Marc, Martin and Sonal debate these questions, as well as the impact of the cloud wars, how innovation happens when a company is private and when its public (something Michael knows well, having taken Dell public to private to back to public again), whether you can actually play nice to win as a leader, and more.

How do you transform and innovate as your company grows and matures, even as the underlying technology platform shift beneath you? And what does this look like when you're a private company versus a public one? In this episode from October 2021, Michael Dell, founder and CEO of Dell Technology, and one of the longest standing founder, CEO's in tech, joins A16Z general partner Martin Casado, A16Z co-founder Mark Andresen, and host Zonal Choxy on the occasion of Michael's book, Play Nice But When. a CEO's journey from founder to leader. They debate the impacts of the cloud wars,

how innovation happens when a company is private and when it's public, something Michael knows well, having taken Dell public to private to back to public again, whether you can actually play nice to win as a leader and more. Hi everyone, welcome to the A6 and Z podcast. I'm Sonal,

and today we have yet another of our special book launch episodes on the upcoming new book titled Play Nice to Win, a CEO's journey from founder to leader, The book is by Michael Dell, founder and CEO of one of the world's largest tech companies, Dell Technologies. And while his book interweaves the journey of starting, transforming, and keeping one's company, we focus primarily on the how to keep and how to transform in this episode. We also discuss the challenges of being public while trying to innovate, beyond the behind-the-scenes stories with activist investors,

and we debate the underlying tech platform shifts from the death of the PC to the current cloud wars. So also joining this episode are A6NZ general partner Martine Casado, who is co-founder of Nicerra, which was acquired by VMware. Martine's also written a ton about the trillion-dollar paradox of cloud, which you can find at A6NZ.com slash cost of cloud. And we have A6NZ co-founder Mark Andresen who joins as well and plays Devils Advocate throughout. We begin with the Cloud Wars, then the company wars, and finally end on leadership. For context, Dell's company famously went public, then private. it and then public again. And we also referenced the write-up that we did here years ago called Making Sense of Dell plus EMC plus VMware in 2015. There were many analyses of that

deal at the time through the tech lens and there were many analyses of the complicated financing of the transaction, but we were one of the very few who dug into and analyze boat threads together to reveal a far more interesting story. You can find that at A6NZ.com slash Dell deal. As a reminder, given all the historical events and companies mentioned that none of the following should be taken as legal investment, business, or tax advice for more important details. Please see A6.Z.com slash disclosures. So, Michael, when I was reading your book, by the way, which is fantastic, I just loved it. Thank you. You're going through your psychology on particularly your belief that, like, PCs still had kind of a lot of legs and then everyone was

wrong. And I was thinking, this is the most extreme form of, like, the founders seeing truth. when everybody else doesn't, because normally the founders believe something the world doesn't, but there isn't a lot of data and there isn't a lot of experts because it's so new. But in this case, this is like incredibly mature. There's a lot of data and everybody knew. And still, you hold this contrarian view. And so I was just wondering, like, I feel in infrastructure, we're having a similar kind of dilemma now where there is this consensus view that all of infrastructure is going to be

consolidated in an oligopoly of three companies and, like, somehow all the PCs are going to disappear in the cloud, et cetera. So, like, do you feel this is kind of a similar situation, different situation, would love your views on that? So there are lots of different models that are emerging, but the idea that everything is going to one public cloud, you really don't see a lot of customers doing that. I wake up every day and I look at our daily order report from the previous day and it sort of tells me, no, that's not happening. I can tell you from my conversations with customers, they've sort of figured out it's not. not the public cloud or the private cloud, it's both. And even beyond that, it's really the edge. And, you know, infrastructure is going to continue to be distributed. Yeah, they like

the consumption models. They like the AI and ML services that the public clouds are building out. But they're not going to all be beholden to one cloud. More and more customers are thinking about what's the right place for any given workload. You've got data sovereignty issues, security issues, certainly cost issues. And look, when I look at what is about to happen with all this embedded intelligence and distributed computing being even more distributed and real time, I don't think all that's going to be concentrated. There are estimates out there that say there will be more apps and more data at the edge, and it's not going to all come back to the center of the universe.

Our partner, Peter Levine, actually wrote a piece a number of years ago, which was called The End of Cloud. His point being that all of the computing is moving to the edges, as you know, Michael, and what that means architecturally because of the processing having to happen closer to those nodes at the edge versus like going back to some centralized thing. In some ways, the end of cloud was kind of a controversial statement, at least for those not in the know. And then more recently, this idea of cloud services versus on-prem and this whole debate

that Martine and Sarah have been writing about, it was actually probably one of our most controversial posts in the last five years. And so I would love to hear you guys, you know, debate some of these technological shifts. It seems like IT goes in these kind of like collapse, expanse, collapse, expanse phases. You have like mainframes, it's kind of a collapse, then you have this kind of expanse in the PC, and then you've had like a bit of a collapsing that happened into data centers in cloud. And now it's so clear we're in an expansion phase. Like there's the Cambrian explosion around data, faster connectivity, edge compute, edge devices.

And every time you have one of these collapse expanses, the TAM grows by at least a factor of 10, normally a factor of 100. So it seems to me like the TAM is increasing. And a lot of this compute is exploding out of the clouds right now. Another way of thinking about this is, you know, the domain of technology used to be the IT department, and now it's the whole organization and the whole company. Basically everything you want to do from sales, marketing, product development, et cetera, anything in any organization, technology is the fulcrum. And that is driving a tremendous amount of demand and obviously opportunities for the industry. all these things have to be built on a foundation of some kind of infrastructure. I mean, clouds are infrastructure and AI is eating software, software is eating hardware,

but it's got to run on something, right? I actually think it's instructive to go through the historical arguments quickly on this one because the actual argument has shifted. So the first cloud wars, which I think most people remember, was literally like the cloud versus internal IT. And internal IT had old technology, you know, data centers were like, really wiring closets, and they were like museums of computer science passed, and you didn't have automated processes, et cetera. And so traditionally, we're talking like when I was a programmer

back in the early 2000s, there was a lot that you could do to reform that. And it turned out that having an alternative that somebody else managed helped. And so I would call that Cloud Wars 1.0. But in that time, infrastructure has evolved so much that that's actually not even really a problem anymore, even if you're running your own IT. So that continues to play out. But something else has happened, which I think is even more significant, which is we've gone from basically every company is a software company. Every company is a SaaS company's a SaaS. So instead of shipping software, now we run software and SaaS. And the economics of the cloud, if you're SaaS, are just really poorly understood. I mean, in the last six years,

126 companies IPO that were predominantly cloud native, 126. This is during a bull market where debt was almost free. And so we don't even know what it looks like when the market starts kind of what their margins look like, right? And so you could argue that there's a massive shift, you know, to SaaS. I would call this Cloud Wars 2.0. And now when it's SaaS, infrastructure becomes cogs, it's very, very important to have choice and flexibility, which is why Michael Dell and I have been so aligned on this for so long.

So I'll agree the other side. There we go. There we go. You guys agree with each other way too much. So I'll concede up front. Like, there's a bunch that I would probably agree on, but not admit it. So argument in three parts. So argument number one is you guys have been kind of infrastructure systems guys your whole lives.

Like I've been a software guy in my whole life. And like I took all the hardware design courses and like I kind of, you know, to use the toothpicks to prop my eyes open. I just couldn't wait to back to the compiler. And so the last thing in the world I want to do is deal with any aspect of hardware if I could possibly avoid it. Like I just want to stay as far away from it if I can. I want to be able to type things, you know, in an editor, you know, I want to basically press deploy. But I just want it to work.

And as software is the world, a software. becomes more important and more kind of comprehensively applicable in kind of every sheer human life. And as more and more people become software developers, just the sheer amount of demand for people who just want to write code and press deploy and run and certainly not ever deal with the concept of a server or a this or a that or private this or anything other than just pressing go. Like that market is going to just like continue to grow explosively.

So let me pause there and see what you guys thought. Yeah. No, I agree with that trend. And that's why we're seeing tremendous growth in basically, creating this developer-friendly environment that allows customers to deploy easily. I actually think the arguments are somewhat compatible, given the trends in how infrastructure is now being delivered on a consumption basis. And then, yeah, I guess the corollary would be you would view it as a challenge, for example,

for your company, as the environment that you're providing as a private cloud has to be as easy to develop on, has to be as easy to sort of click and go as a public cloud. Is that the way to think about it? Yeah, I think one of the other things that we're seeing is the super big organizations, I think this will flow down to large and medium-sized organizations over time, have basically said, I'm going to put my data in a neutral COLO that has incredible connectivity, and I'm going to access services from each of the major public clouds, because it's just an untenable situation to, put everything in one of these. And I actually think that Kolo model is growing faster than the discrete public cloud model itself. Just to follow on this, you think, Michael, in line with that, what happened in the pharma industry is it turned out big pharma would rather erode their own market share than drop their margins. And so the buyers propped up this company that was just made

for generics called Dr. Reddy's that was actually built for like 15% margins, et cetera. Do you think that, you know, to your co-low model, which by the way, I agree, it's a massive, massive friend. Do you think we're going to see the rise of almost like a generics type cloud that uses merchant hardware in a similar model to that? Or do you think it's going to be every enterprise does their own thing? I mean, I've seen a number of business plans like that. It feels to me like it's going to be highly distributed, particularly when you think about it globally. You know, there are data sovereignty issues that are real and significant. And with the rise of these enormous tech companies, you're seeing some nationalism push back

on the usage, even if they're making significant investments inside those countries. So it feels like it's going to be highly distributed, and that's kind of what I see. So second argument is sort of the consequences of the rise of AI and machine learning. So Michael, we'll tell you what kind of what we think, which is the nature of software development is about to change dramatically. it's going to change from basically people writing deterministic code, you know, sort of the traditional style of like first this than that and the other thing, kind of in a classic Kodneumann programming model, to writing much more software that's basically built on ML models.

So basically software systems where you dump in huge amounts of data and the neural nets do their thing and they come out with answers on the other side. And of course, we're already seeing the rise of that kind of development, you know, large parts now of the big internet companies like Google and Apple now run on these systems. As an example, like Google has re-engineered its entire search engine to run in the this model, which is a real harbinger of the future. And we're seeing it across, you know, many areas of tech, including, you know, direct discovery and tons of others.

And so a couple of things happen as that shift happens. One is just like the whole nature of development changes. As a programmer you're dealing with software at kind of a different level of abstraction. And in fact, a lot of programmers who are going to be writing against AI are not going to understand the details of how yet works. They're going to basically be writing on these high-level APIs that access these very complex algorithms kind of under the hood. And then the related thing is the demand for processing power is just going to

explode stratosphericly from here, right? Nvidia, you know, as a major beneficiary of this trend today, it's become harder, at least for a lot of consumers, to buy GPUs, even for their PCs, because those are the same chips that you want to run these AI algorithms. And so you just have this sort of massive explosion of the number of cores and the number of processors and GPUs that are going to be necessary to support this program model.

And so I think the argument would be that in this model, then you really want a cloud, right, which is you really want a super high-scale environment with a great deal of flexibility to be able to scale your processing needs, and with an increasing amount of specialized hardware in the form of these GPUs and all of the custom silicon that's coming along to support AI. And you really want higher and higher levels of abstraction for the software developers, which again involves lifting them further and further out of the nuts and bolts of how the infrastructure runs. And I'd be curious what you think of this trend for the kind of model that you're talking about. I think there are going to be workloads where the scale of the

public clouds is going to be super efficient and going to work well. But I don't think that all the organizations in the world are going to say, hey, we're creating all this valuable data and we're just going to give it to you and then we'll rent it back at whatever price you want to charge us in the future because we don't have any other options. Look, these companies are creating a lot of powerful services that customers want to take advantage of. But a lot of those AIML frameworks are not just owned by those three companies or exclusive to their public cloud infrastructure. It's a lot of open source activity there and companies, helping companies figure out how to use all their data, which we're still at the very beginning of that as an industry. Are you seeing AI demand or machine learning demand? Yeah, absolutely. It's one of the fastest growing workloads that we're seeing. you know, certainly invidia driven, and there are many others that are working in that

space too, but that's driving enormous demand for sure. Yeah, and then I think the third argument would be basically getting the nature of competition, which is it was not that long ago that it was at least taken as an article of faith, maybe incorrectly if the cloud businesses were not going to be profitable or are going to be only marginally profitable. And obviously, you guys and Martine with your work have done a great job of illustrating how actually turns out they're actually quite profitable. But you do have this dynamic, you know, Amazon, Google, Microsoft.

off, these are three now just like, you know, gigantic companies with what seems to be a very high-level determination to bash each other's brains out in this market. They're all so determined to win this more. Aren't they going to beat each other to death on pricing over the next five or ten years? And won't that result in their margins actually coming down and therefore maybe resolving some of the economic pressure routine that you wrote about? Well, I mean, I just don't think a logopolis worked that way. If you look at the actual margin profile over the last 10 years, it's gone up from about 18% to 30%, right? So it's actually increased. So while price is, dropping. That's through internal efficiencies. Margins have been increasing. And so I think whether

it's being checked by the public markets and or the internal operations of the company, it's a very, very hard thing to do for them to erode margin. And again, we have examples where you can look at. I think Big Farm is one of the best ones where, like, they would just rather seed market share to generics than drop their own margins. Listen, if oligopolis changed the way that they work, then maybe we're going to see an erosion of margins. So prices will drop 100%, but I don't think margins will. And as workloads become more predictable, so let's say you're a big SaaS company, you're a decade of billion dollar SaaS company, your margins are going to be very important as well. Your workloads are going to be predictable.

Your workloads are going to be at scale. You're going to have huge teams that know how to run platforms. You would be silly not to take some of those workloads and you collect the margin gain as opposed to Amazon. You'd just be silly not to. And I would say one more thing. It's very interesting, which is when the big three decided to start disrupting the server supply chain, they did it when the service were 50% of their cogs.

That was the point in time. It was about 2007. And if you look right now at these big SaaS companies, cloud is 50% of their cogs. So something's going to happen. Yeah. It's all owned by three companies. So I just don't really see that scenario happening. Here we are in 2021 and server demand is off the chart strong.

And if I look at the ship two addresses for those servers, it's not all to, the three companies. It's global. It's all these new kinds of workloads. And again, I think with low-latency networks coming into play, it's likely to be even more distributed in the future. So on the cloud pricing wars discussion that Martine, you and Michael were having, it struck me that you guys were actually talking about more mature companies versus like early-stage companies where part of Mark's question, at least the way I interpreted it, is that it's also about basically how you get innovation, right? Because the whole point of a startup, an early stage startup, being able to go cloud is you don't have to worry about the plumbing and all the crap.

You can just focus on innovating? So can you guys talk a little bit about the tension between the early stage model and then the transition to mature here? And by the way, Michael, I think this is really relevant to your book because it takes us to the narrative where you're really talking about what it means to go from an early stage to a mature company and then how you continue to get innovation. So let's talk about this whole debate about margins and what happens and the tension between innovating. Yeah, yeah, yeah, for sure, sure. So, you know, the cloud has a ton of benefits,

which is, you know, if you're starting a project, you can do it incrementally. You get the cost of benefits of something that's, you know, already at scale. You get all of the latest kind of software's and tools, et cetera. So if you're a new startup, it makes a ton of sense, and you're building a SaaS app or something like that, you're not for infrastructure,

it makes a ton of sense to use the cloud. Or if you're, let's say, in a big company and doing a new project and the cloud already has some tooling that your internal IT doesn't, it totally makes sense to use the cloud. So there's a lot of value in the cloud for sure. The issue is, and this is kind of where this argument is just a new argument, is we're no longer in the old enterprise world, right? It's not Cod Wars 1.0, right? We're in this world where most software is run as a service. And that's just a different world. It's a different world because you actually have people that are good at operations in your company. It's a different

world because the infrastructure actually becomes part of your cogs. And so as you get larger, the implications become more significant. And so there's a bit of a tension or a paradox right now where early on it totally makes sense to focus on using cloud workloads for some projects. But as you get larger, you're actually kind of reselling the cloud and you have to decide what to do about that. And so this is what the industry is grappling right now. And as I mentioned before, And I think this is something everybody should remember, 126 companies, IPOed in the last six years during a bull market with almost no debt. And so this is a very, very new phenomenon where we've got companies that have built entirely on the cloud

that haven't had to worry about market pressures because they're growing a lot. And they can basically raise money for free. As soon as that shifts, I think that all of them are going to have to really look at. What does it mean that 50% of their cogs are coming from one of three companies? It's a very big deal. Yeah, I agree. And the trend that we've seen is companies get to a certain size, they start to focus on this. What you also see is the startup ecosystem maturing where at some point in its journey sort of realizes, hey, wait a second, we're going to be like paying enormous rents to these public cloud guys.

And we're never going to be profitable given the cost that we're paying for infrastructure and for the egress fees and everything. else. And so then they get into a more complex analysis of their workloads and they start picking off parts. They're like, wow, this is going to cost us way less than we're paying over here in the public cloud for certain things. And look, I think the rise of Kubernetes is very much a function of this idea of people like clouds. They like cloud native software development, but they don't want to be locked into a particular infrastructure location. They start to architect to be independent of location, and we're seeing that. So it's real. Yeah, the important thing is, like, this isn't a categorical anything, right? It's much more about, like, building anything.

Like, you use whatever's best for purpose, right? And, like, as part of this kind of constraint, it's going to be kind of cost and cogs. And so, like, the more flexible the workloads are, and they're being built to be more flexible all the time than more, to Mike's point, and I think is right. They're going to be distributed. And that means that, like, some of them are not going to land on the cloud. I will leave the whole repatriation debate off the table. I'm just chuckling because I was remembering that phrase that someone shared the rise of the repatriarchy or something ridiculous.

You know, along those lines, one of the things that really struck me, Michael, in your book, you talk about as a leader of a public company, how there's always this tension. And in your case, like between profit and growth and share. And do you think that actually those three would be so aligned and that they should just all kind of go forward, lockstep? Like, why doesn't profit lead to increased growth to increase share? Can you talk a little bit about some of the tensions there? Sure. If you're going to invest heavily, it's going to drive your profits down.

And so it's always just balance of the three. and you can drive share up pretty easily. That can lower profits in the near term if you're going out and hiring a bunch of salespeople, investing in new accounts, building out new relationships. And so, again, you have to find the right balance. Now, if you've got a great business model and fantastic margin structure, they can all align very nicely, but that's not the case in every scenario. That was great.

we're going to shift into talking about the Dell EMC story. You know, you went from taking a company public to private and then back to public again. Mark is the one who made me write like with the corporate development team, the Dell EMC Primer. We did and I kind of hated him for it. I was like, what am I doing this weird finance thing and what is the tracking stock? And I was so annoyed because I'd never written anything that was like corporate finance. I ended up coming out of it the other side like in love with the whole topic. It was fascinating.

You guys did a great job with that. Thank you. Well, you guys gave us a lot of great material to work with. It was Mark's idea. He was the one who gave us the through line because I was like, Mark, what's the entire point of this? And it's all about how do you stay innovative in a market environment today? So tell us about that. Yeah, so it was quite a journey.

And you kind of have to go back to the mid-2000s when things really started to accelerate in terms of change. in the industry, it became kind of clear to us that while we'd had a lot of success up to that point, we needed to do some different things. We needed to invest in software and new capabilities. We were going to have to build and acquire a lot more IP. We started acquiring companies. And the more we did that, the less the market really appreciated the change that was going on. That was kind of painful and made us sad, certainly, because we were working really hard at it. But at some point, it became an enormous silver lighting because it created this incredible opportunity to buy the whole company back from the shareholders and really accelerate the transformation with no quarterly shot clock. And so we did that.

We just slammed on the accelerator. And we just said, all right, there's no shot clock here. We're just going to hire tons of engineers, and we're going to hire enormous numbers of salespeople, and we're just going to go for it. And we did an enormous level of investment organically inside the business, and it started to work pretty quickly. The GoPrivate was going really, really well. Cash flow was coming in.

In fact, we were, within 18 months, our net debt was like zero. which was pretty amazing. So, anyway, about a year after that, Egon Durbin from Silver Lake and I started talking about, what can we do next? We knew we needed to transform more EMC. I'd become the leader in data storage, and they had this 81% interest in VMware. And we had this idea of, wow, if we could somehow combine Dell and EMC and VMware, you would create this just amazing company.

the only problem is we needed $67 billion, right? And so we worked on that and through some very creative structuring, figured out a way to do it kind of with their money, basically, and contributing all of our own equity. And we thought it would work, but it actually turned out to be way better than we thought. So that's a quick snapshot of it. Can you put a little bit more in context, like just a little bit more about the underlying tech shifts besides just the players and the financial part? Sure. I think the backdrop for a super long time has been this incredible growth in the amount of data. And that is only accelerating, but of course you have to turn that data into something

useful. And one of the things that was happening in infrastructure and clouds was this extrapolation of the offering up to a higher level, where nobody really wanted to assess. all these components themselves. And so you had things like hyper-converged infrastructure, converge infrastructure, cloud. And if you were just a server company or just a storage company or just a networking company, you really would have a difficult time. The big thing there is customers were telling us they didn't want to be systems

integrators. They didn't want to put 20 things together. And, of course, all the other 20 things were not number one. We were number one and basically all of them, which made it super compelling and I wouldn't say easy, but it was very straightforward to go to these customers and bring them a much broader offering. Great. Martine, we all heard from the market, their reactions, but what was your reaction from the inside? I mean, you were at VMware at the time. I was, yeah. So I was running the Network and Security Business Unit and actually remember when this happened.

And what was clear to everybody within VMware was that infrastructure was becoming a battle of Titan. It was companies that owned the entire stack. It's like every single player was kind of wedded to something pretty serious. And so the only two really neutral players, it seemed, were Dell and VMware. So you have like the full kind of harper side and the full software side. And so there's a tremendous amount of excitement because it wasn't super obvious how you could play a game this big without being part of a much, much larger offering. In order to stay super relevant, like this is something like this had to happen.

But, listen, it was also crazy, scary because we didn't even know what a tracking stock was. So there was kind of a lot of education that happened along the way. You know, the other thing that was amazing was it was pretty rare that a number one business was ever for sale. And if it was for sale, it was at some ridiculous price, people were saying, oh, all infrastructure is going to go away because the cloud is here. And, you know, that turned out not to be exactly the case. It's multi-cloud. And I think the rise of the cloud also discounted where an EMC, just like earlier people had said, you know, the PC was going to go away.

There was this narrative that kind of enabled us to go private, which was at the time sort of 2012, the smartphone was really on the ascendancy and the iPad was taking off and everybody was like, oh, you don't need PCs anymore because of these smartphones and tablets. We always thought it was an and thing, not an or thing. So that demise of the PC narrative gave us this incredible opportunity to buy the company back. The GoPrivate started in 2012 and was completed in 2013. The announcement of the deal was in 2015.

It closed in 2016. That was quite a not hole to get through with Carl Icahn and other adventures along the way, which I described in the book. Yeah. So Michael, you and I have both had the rather rare sort of experience of tangling with Carl Icon over the years. And I'm very used to arguing your side of things. Let me argue his side, try to steal man his side and then see what your perspective is on this now that some time has passed. So his side of the argument, if I recall correctly, was basically a sitting CEO of a public company buying his own company is the most obvious conflict of interest in the world because you have all of the inside information and then you have control of the process. And so you in theory as the CEO can do all manner of things. things to manipulate how the company appears to be doing, what the price should be, what the stock prices and so forth. And then the bidding process and the buy process itself. And so you're basically in a position to cut yourself an amazing deal. And I haven't heard him say this, but I would imagine, you know, he might even say today, aha, I was right in a retrospect, like look how well it went post the buyout. And isn't that evidence that the original thesis was right? So

now that some time has passed, what is your perspective on that argument? And what's your perspective now on the role that activists play and your take on how that whole thing played out. Sure. So let's unpack that. First of all, I think if it works, it's easy to say in hindsight that the founder or the management team knew what they were doing and they got a great deal. But if it doesn't work, you wouldn't really say that, right? Of course, there were enormous protections that were put in place by the independent board and special committee that oversaw the process to ensure that the shareholders got the best deal possible. And in the end, Carl Icon, for all of his bluster, and he went on TV and lied about all sorts

of things, which I detail in the book, he never offered one penny more than Silver Lake and I were willing to pay for the company. What I discovered in a dinner at his house over his wife's meatloaf was that he basically didn't know anything about the company, didn't care anything about the company, actually didn't even want to buy the company. He just wanted me to pay a little bit more so he could make a little bit of money and go on to his next adventure. For him, it was just a big poker game. I asked him what his plan was and he sort of mumbled a bunch of things. So I sort of called his bluff and said, okay, well, you know, why don't you buy the company for a little bit more than I'm willing to pay

and you're going to totally screw it up and I'll buy it from you for a lot less than you pay for it? You know, that'd be a great deal for me. And it was pretty clear he was scared of that scenario. And it was another interesting thing that maybe very few people were following this, but every single share that he bought up into that point was above the deal price. So if the deal had gone through, he would have lost money. Now, he later convinced southeastern asset management, our largest outside shareholder, to sell him a bunch of their stake

at a discounted price. How he actually did that, I don't know, but if you sleep with a tiger, sometimes you wake up and your arm is eaten off. Look, I don't have a problem with activist investors. I have a problem with green mailing and basically misleading investors, which is what he did. Specific example, he sort of claimed that you could claim appraisal rights, which is a very arcane aspect of go-privates, and there was absolutely no risk. and he was saying he was going to do it, which he ended up not doing, and it was not no risk,

and he kind of knew all those things, but that doesn't stop him from going, you know, on national TV and line. And so that's Carl Icon for you. Right. I steal man his point of view, but like I said, I'm where you started on your side. So if I can steal man your point of view and tell me if you think this is right, I think it would be the ultimate expression of faith by a CEO in the business is wanting to buy the entire business. And so when the CEO scans up and says, I want to buy this thing, and for this price, it should be a massive bass signal to every other potential buyer in the world saying, like, this thing is like really valuable. This thing really matters. The CEO really believes. And so therefore, anybody with the money to do it, ought to like really pay attention to it and come in and try to bid more. And the process, in fact, supports that. Yeah, exactly. That's what happens when you start a go private. Effectively, the company is put up for sale, right? And so any number of things can happen at that point. You could. have other bidders come in. The price the stock could go up. There could be various forms of

recapitalizing the company such that a go-private is either no longer practical or necessary. So all of that could have happened. At any point, any number of buyers could have come in and said they wanted to pay more than Silver Lake and I were willing to pay. But nobody did. Was there ever a moment when you thought somebody else would come in and do that and end up buying the company? I mean, Blackstone was hanging around the hoop and talked about offering, I think it was $14 or $14.25 a share. They ultimately backed out. All the private equity firms took a pretty good look, but all except Silver Lake got pretty scared by what was going on in the PC market at the time. Windows 8 was sort of a failure, and it just played into that narrative of the smartphone and

the tablet. But with operating systems, you have effectively hardware and software working together to create systems. You've got cycles that effectively create a refresh and a new source of demand, as you get new functionality, that's true with processors, with operating systems like Windows and others, and they enable new capability. We knew that it was just a matter of time before there was a better version of Windows. These machines were getting four, five, six, seven, eight years old, and there would be enough new technology that would motivate people to replace them. I think a lot of the private equity firms basically just looked at the business as sells on a spreadsheet and didn't really understand things like operating system cycles and some of

the changes that were going on deeply enough to be able to underwrite the business. Mark asked you about lessons learned in fighting an activist. One of the things that really struck me from your book is the narrative side of that lesson in that you're not just fighting with facts. In fact, you can't fight with facts because there are many cases where you had media outlets completely misrepresenting the numbers. There were analysts misrepresenting the numbers. At one point in your book, you actually do a calculation that Carl Icon, for claiming all of his, I'm trying to get more shareholder value, actually underperformed against the S&P 500. And so the facts do not match the perceptions that are out there. So I'd love to hear your thoughts on kind of narrative lessons

for founders there. Yeah, look, Carl Icon's record speaks for itself. All you have to do is look up the stock of icon enterprises and compare it to the S&P 500 over any period you want. But that doesn't really matter. He's a magnet for media. And so he gets views. He's interesting. He's provocative. He says stuff that causes people to continue to watch.

And that's what they care about. So I think you have to be a good person and be someone that people trust and want to partner with and rely on. And when you're going through something like that, you're going to. tap into hopefully all of that equity that you've created over time with everyone. You've got to tap into the relationships that you've built to keep customers and team members and everybody focused. If you started a company today, Michael, do you think you would take it public sooner than later? Or would you wait?

You know, we went public in 1988 because we really didn't have any choice. That was the only way we could get capital to grow. I think you only want to go public if there's an objective reason to do it. Companies that go public too early, I think, are in for a bit of a rude awakening in terms of what they're subjected to. And you really have to be ready to go public. So I wouldn't be in a big hurry to go public. You know, obviously one of the big things that comes up is like the number one reason to go public is to do mergers and acquisitions. And that was a big part of your strategy in terms of thinking about how to kind of

create the company you want? What was the tension in your head between the strategy of M&A and what you were able to do inside? Like, how did you navigate? What do you build versus what do you buy? Well, ours was kind of a unique situation because we did this massive acquisition. It was highly transformative for the capabilities and the position of the company. And I think if we had been a public company, I don't think we would have been able to do that. we would have had to have votes by both shareholders and public shareholders on the acquiring side, you know, if we were public at the time, probably would not have accepted that kind of risk that, to me, look like a great opportunity. So you have to understand where your

co-investors are, whether it's public shareholders or private co-owners and make decisions appropriately. What advice, if any, would you give to the next CEO of a public company that's kind of in the position that you were in to potentially buy your own company? Is there advice you give them based on having had that experience now? Well, you better get yourself a really good lawyer and follow the proper procedure super carefully and be ready for something that is way harder than you could ever imagine. The public market doesn't like it when you try to take away their products, the public stocks, and founders are assumed to know more than the average person when it comes to buying back a company. Fortunately, this one worked out, so I guess it proves the case.

So what I was hoping to dig into, Michael, is markets transition all the time. Transformations happen periodically, and they almost always kill companies. It's very rare that leadership that gets brought in later can have to get a transformation. They can sometimes, but often they don't. And I would love your thoughts and why you think that it is. And then I was also wondering, it's kind of the second part of the question, which is every once in a while you have a leader and it's normally a founder that navigates a transformation, right? Reed Hastings famously with Netflix and you've done it now multiple times. And, you know, I was thinking, you might be the last actual like of like the great founder's standing. Is that the case? You know, Larry Ellison's still going,

depending on how you count, but yeah. Well, so, you know, Jensen and Larry Ellison, the only two others I can think of, but I don't think they've got this level of involvement. Because, like, you know, I've seen so many come and go in the last 30 years. And I think you're it. I have a quote here. I actually have a quote here. You're one of few remaining founders who's still CEO 36 years later. Like, that's amazing. 37, yeah. 37. I mean, I've just been so interesting. Like, why founders pull this off more than other CEOs. And you can believe it is because founders are special and so they see truth. And then you could also just believe

that they've got more credibility because they've got more abuse. Do you have an opinion, or maybe it's both? I think founders get some extra permission to drive change that you might not have as a non-founder. If a company is sort of doing okay,

but it needs to transform, you have to create a real sense of crisis inside the company and kind of balance, scaring, and freaking people out where if we don't do this with inspiring and motivating them about what the future can be and that's sometimes a tricky balance but to motivate change and transformation you have to strike that balance if you screw it up of course you can lose all that trust and credibility

but if you are thoughtful and are straightforward with people about what we're doing and why we're doing it, they'll run through walls with you. Okay. So the title of your book is play nice, but win. And the subtitle is a CEO's journey from founder to leader. And you have this line that you said that you were never looking for a fight, but relishing every brawl once you're in it, which I think is just fabulous. Do you think that people can really play nice to win? I mean, obviously it's a premise of your book, but do you watch Ted Lasso by any chance? You know, I just started watching it because so many of my friends have told me, you know, it's hilarious. So, yeah, I think I'm into episode four or something like that.

Okay, so you're still on season one. Yeah, still on season one. Well, I'm only asking because there's this whole now argument that people are making that we're in the Ted Lassow age of management, that managing by nice is the way that people are going to get ahead. But the thing that I find so funny about it is that the show itself is actually more entertaining because of all the assholes that are in it and the fact that you have this juxtposition of like ray kent against ted lasso and so i wonder if you have thoughts on how to deal with the assholes in the workplace in this mind of play to win so i'll tell a little story every so often i will get a group of people that are not on our executive leadership team

you know, maybe 10 or 12 people that could be the future executive leadership team. And I'll spend three or four days with them, give them each pretty big assignments. They share their work with everybody else. And I kind of see how these people would work together with me as if they were the leadership team of the company. And every once in a while, you'll see somebody in there and it's okay, this person's not helping the other people sort of only out for themselves. And thank you very much.

You'll be going to work somewhere else. And that's just how we do it. And by the way, this person had a really big job at our company before that. So I won't say who it is, obviously. What's his name, Martin Casado? No, it wasn't it wasn't Martin. Wasn't Martin. I can confirm that.

I can clarify that at front. So now your denial is special. Martine, what do you think about this whole thread? You know, it actually remind me of something, which is, you know, I've been in the industry for a while. And when it comes to reputation, Michael, I think you've managed probably to have, like, the cleanness as far as, like, being fair, being direct, being well respected. And you've done it for a very long time. And I said, actually, honestly, industry-wide. And I'm just wondering, like, is this something that you've intentionally worked on?

Or is it just kind of a natural byproduct of how you kind of navigate yourself? because I do think that people's reputations really matter in business. I think business actually follows behavior. And I think you're one of the people that you should model themselves after. Well, thank you for that. I can't claim that I actually did it intentionally. I just woke up every day and did what I thought was the right thing to do. A quick question for Mark and Michael.

Michael, do you have any regrets about leaving college to start your business? Because I think you said you did it before you were 20. And I wonder, because Mark is always the one who critiques this whole notion that people should leave college. Would you recommend the people that they leave college to start a business? You know, it's not for everybody. I mean, you have to be kind of a deviant and mischievous and a rule breaker. And that's clearly not for everybody. And it doesn't always work out.

For me, I had nothing to lose. And I could go right back to college a semester later if it didn't work. So understand your risk reward. I felt so compelled that I really had to do it and never, never looked back. Yeah, so you're very much not doing what I'm about to describe, but a lot of people do do what I'm about to describe, which is a lot of successful people basically say, oh, you know, you should do what I did, right? And you should like, you know, do this and that and everything that I did. And of course, that's just massive survivorship bias. You only hear from the people who left

college and started a business when the businesses were hugely successful. You don't hear from the people who like the businesses crash and burn in their life ran dramatically off course. completely fell apart. Yeah, I think Charles Manson also dropped out of college. But, you know, so. And much more succinct way of putting my point. Yes, exactly. And so I always get it as a little bit uncomfortable with the generalizations of how people should template their lives on extraordinarily successful people. And then I think there's another irony to it. And I think you probably agree with this. You were probably a case study of this, which is the people who are really going to do

this are not going to listen to advice anyway. Bingo. Right. So for the people who give advice this kind of thing, I'm always kind of curious as to who the advice is actually for? Well, yeah, I mean, if I had gone around and asked people, should I drop out of college, you know, where I'm like on a track to be a doctor and start this company to compete with IBM, nobody would have said yes, right? You have to be crazy. So, you know, I didn't really ask anybody, didn't really care what anybody thought to me was a good idea. That was enough. now the other thing by the time you dropped out you already had the business up and running to some extent right yeah yeah i was doing about 80,000 dollars a month in my little dorm room and you know thought

well if i had an office i could do 10 times that yeah i think that's the other thing that people really underestimate and you know your story is not i mean it's not a common story but you know mark Zuckerberg already had facebook running when he left harvard you know larry and sergey already had Google running as a search engine when they left Stanford. I didn't leave, but I just, you know, I had mosaic running by the time I started my company. Like there's this narrative of kid drops out, starts company, and magic happens that often discounts, like, kid actually already had thing working at that time, right? And so maybe the actual really relevant advice is like, get something up and running and then

basically make a decision like that, which that's such a staggeringly hard thing for most people to do that most people can't do it, but that might be actually the true backstory in a lot of these things. Much better advice. Is there also maybe like a certain pool of timing? Because one thing that struck me as well is that you talk about how there's kind of this frenzy that you were beginning to see when it came to the PC revolution. And frankly, I see that right now with crypto. And we have an intern on our crypto team who dropped out of Harvard to join the crypto team full time. And part of me is like, I think she did the right thing. Because there is something about the times that you're in where a lot of excitement and sometimes it can be bubbly. But that community coming together is actually what innovation is. So do you have any thoughts on the pull and the draw of that kind of a moment when it comes of this decision, your decision to drop out at that time?

No question about it. I think timing and the sort of energy of the moment are super important. For me, it was sort of the dawn of the microprocessor age. You know, IBM was going strong and it just seemed like that was too compelling to pass up. But how did you know, like, that it was ready? What I think is really hard to tell, and you can only tell, but in the long arc of history is whether at the beginning or the end of something, because they look the exact same.

And, you know, I've been following crypto, working, observing since 2011. And so that to me is, I think, the most confusing part is how to tell. That's the thing that I think keeps people from like the fang companies from joining crypto, for instance. I guess that's maybe another way of asking my question. Like, what was the sign? It was the $80,000 a month I was doing in my dorm room, right? That was a really big sign. and I was actually still in college.

And I was super excited also about the idea that anybody could have a personal computer. I mean, this was way back when it was a really new idea. Interestingly, the students weren't even buying PCs. It's just fascinating, the whole timing thing. One other thing along those lines. So in your book, you have a scene where you talk through all the arguments that you're going to make to institutional shareholder services, that your deal was one of the best ones possible. And some of the arguments, I'm going to quote for a minute,

you list it in a list. Number one, this is a company I started 29 years ago and have guided ever since. It's crucial now to keep it on the right path, and I care about what's going to happen long after I'm gone. Number two, you talk about industry acceleration and then, quote, transforming as quickly as possible is urgent. Change or die.

Number four, transformation is rate limited for a public company. So I could keep going. There's like more. I think you have like 16 arguments there. And oh, sorry, one more quote in another chapter. It's in a conversation with you and Egan where he says to you, quote, this isn't really a transformation. You've already done the transformation. That was a risky part.

Now is the part where you've got to grow and be on offense, which over time will create more opportunity over a longer period. So the question I have for you, and this kind of goes back to this theme of leading from public to private to public again, how do you, and this can sound very generic, but how do you manage transformation? like not just fighting to keep your company, but to change your company. What are your probably biggest lessons learned or advice for founders listening to this? Well, look, the pace of change in our industry is not slowing down. It's only going faster. It's the kind of industry, as you know, where like 80% or more of your revenues come from things that you've just introduced this year, right?

And so you have to constantly be imagining, all right, what is a successful version of our company going to be in five years? And how do we drive that change to get there? And if you're kind of stuck, you don't have the right assets, or you're trying to eke out a certain earnings per share, you can't make the investments, that's a tough place to be. To go private allowed us to reignite a lot of the risk-taking and entrepreneurial spirit inside the company, certainly invest in and acquire strong capability that put us on a totally different trajectory. And we talk a lot about where's the world going with edge and multi-cloud and 5G and all the AI and ML workloads and how do we build out that future.

This is a good note to end on. Michael, thank you for taking the time to talk with us. really glad we covered business, finance, capital innovation. It just kind of all comes together in your new book coming out October 5th, Play Nice But Win, a CEO's Journey from Founder to Leader. Thank you so much for joining us. Thank you all very much. This was a lot of fun. I really appreciate it. And thank you. Thank you. Michael, thank you for doing this. This is really great. It's really great to hear your voice and congratulations on the book. Thank you guys. Thanks, everyone. So you should be in the Zoom app. There should be like a preference. Oh, my God, I'm embarrassed to ask this, but I just realized you might not actually be using a Mac, right?

You're using a PC. No, of course not. I don't know what to do with that. No, here's a trivia question for you. When was Apple's highest market share in PCs? Oh, my gosh. Maybe 1980? I don't know.

You're pretty close, 1981, right before IBM introduced the PC. Wow. Okay, so you were saying... Thank you.