Acquired - Microsoft Volume I

Episode Date: April 22, 2024

Microsoft. After nearly a decade of Acquired episodes, we are finally ready to tackle the most valuable company ever created. The company that put a computer on every desk and in every home. The company that invented the software business model. The company that so thoroughly and completely dominated every conceivable competitor that the United States government intervened and kneecapped it… yet it’s STILL the most valuable company in the world today.This episode tells the story of Microsoft in its heyday, the PC Era. We cover its rise from a teenage dream to the most powerful business and technology force in history — the 20-year period from 1975 to 1995 that took Bill and Paul from the Lakeside high school computer room to launching Windows 95 alongside Jay Leno and the Rolling Stones. From BASIC to DOS, Windows, Office, Intel, IBM, Xerox PARC, Apple, Steve Jobs, Steve Ballmer… it’s all here, and it’s all amazing. Tune in and enjoy… Microsoft.Sponsors:ServiceNow: https://bit.ly/acqsnaiagentsHuntress: https://bit.ly/acqhuntressVanta: https://bit.ly/acquiredvantaLinks:Congress changing copyright law in 1980 to include “computer programs”Acquired “classic” on Microsoft’s 1987 acquisition of Forethought / PowerPointQuartr's charts on Microsoft's revenues, market cap, IBM comparison, and moreAll episode sourcesCarve Outs:LGRAndré 3000’s new album + GQ InterviewMeta Ray-BansVisual Designer Julia RundbergSummer HealthMore Acquired!:Get email updates with hints on next episode and follow-ups from recent episodesJoin the SlackSubscribe to ACQ2Merch Store!‍Note: Acquired hosts and guests may hold assets discussed in this episode. This podcast is not investment advice, and is intended for informational and entertainment purposes only. You should do your own research and make your own independent decisions when considering any financial transactions.

What were you listening to before we hopped on to your walkout music? New Beyonce. Oh, New Beyonce. I haven't heard it yet. How is it? I really like it. Nice. I think it is reductionist to call it country. I was appropriately enough listening to Start Me Up Through the Ages. Of course you were. But I kind of feel like a David Rosenthal move is that you might have

been listening to Start Me Up whether we were doing Microsoft or not. That's a very squarely in your genre song. The Stones, though, man, like it's crazy. They're in their 70s, 80s. Amazing. Man, I hope we're in our 70s and 80s dancing on stage. Season 126. Yeah.

All right, let's do it. Let's do it. Who got the truth? Is it you? Is it you? Is it you? All right, let's do it. Let's do it. Welcome to Season 14, Episode 4 of Acquired, the podcast about great companies and the stories and playbooks behind them. I'm Ben Gilbert. I'm David Rosenthal. And we are your hosts. We often remark that selling software is the best business model of all time. Well, today, finally, we tell the story of the company that created that business, Microsoft.

Finally, we're like 10 years into acquired here. We're finally doing it. It's been daunting. You know, we wanted to do it for a while, but it takes some chutzpah to tackle Microsoft. I'm so fired up. We're ready. It's time. Yep. Well, listeners, Microsoft today is sprawling and massive. It is the world's most valuable company worth over $3 trillion. They have 49 years of history making software for consumers and enterprises, making hardware, gaming systems, gaming studios, Windows apps, iPad apps, Mac apps, operating systems, mobile operating systems, MP3 players, search engines, cloud computing services on cloud

computing, programming languages, development environments, the list goes on. But it did not start out that way. Today, we will tell the story of the desktop software company. Before the enterprise, before IT, before the internet, before being a trusted partner to governments around the free world. And really, before people even knew what to do with personal computers. This is the story of a bunch of ragtag geniuses in their 20s pushing what was possible. Welcome to Microsoft, the PC era. Well, listeners, if you want to know every time an episode drops, you can get hints at the next topic and follow up. You can sign up at acquired.fm slash email. Come talk about this episode with the community at acquired.fm slash slack. If you want more from David and I, you should check out our second show, ACQ2, where we interview founders, investors, and experts, often as a deeper dive into topics we cover on the main show. So with that, this show

is not investment advice. David and I may have investments in the companies we discuss, and likely all of you if you hold any index funds, and this show is for informational and entertainment purposes only. David, where on earth do we start the Microsoft story? We're right down the middle on this one. We're going to start in 1955 in Seattle, Washington, with the birth of Bill Gates III, or Trey, as he's known growing up. It's so confusing because his dad is the second, but he goes by senior, and Bill is junior slash the third slash Trey. So Bill, in 1955, is born as the second of three children to Bill and Mary Gates. Now, Bill Gates, senior, his father, is from Bremerton, the Navy town just across the sound from Seattle, where

he grows up in a family that owns and runs a furniture store there, a long way from the software king of the world here. Now, Bill Gates Sr. slash the second, after high school, he joins the army during World War II, serves during World War II. And then he goes, I presume on the GI Bill, to the University of Washington, where he's the first member of his family to go to college. And there he gets an undergrad and a law degree in four years, and then decides to stay in Seattle with his new family and become a practicing attorney. Now, I say family because at the UW, he meets and marries one Mary Maxwell. And Mary, I don't know how to put it other than that she is a force.

So Mary's family had founded National City Bank, and her father was a senior executive at First Interstate Bank, which later became a big part of Wells Fargo. Now, Mary, despite being the daughter of a successful business family in that day and age, was not cast aside like so many other daughters we've talked about on the show. New York Times, Hermes, where it was sort of passed to the son-in-law to continue to run the business. That was not the case with Mary Maxwell. No. So after she graduates from the UW, she becomes first the president of the Seattle Junior League, and she starts joining nonprofit boards in Seattle. As a very young woman,

she joins the Seattle Symphony Board, the Chamber of Commerce, the Children's Hospital, the King County United Way. And she's such a force on these boards that she starts getting asked by her fellow board members to join their company's boards too, like the corporate boards. They're so impressed with her. So first she joins the board of First Interstate Bank, the bank that her family's a part of. Then she joins the board of Cairo Television in Seattle. She even ends up joining the Pacific Northwest Bell Telephone Board. That's right. Part of the AT&T breakup.

Yeah. Eventually, she joins the Board of Regents of the University of Washington and the whole entire national United Way board. So she never works full time in a corporate setting. But it is not an overstatement at all to say that Mary Gates became one of the most powerful business people in the Pacific Northwest, period. Absolutely. And Bill Gates Sr. was the prominent attorney in the region. And so it's quite the power couple. Ben, it's like you're reading my script here. Yes. We don't want to give Bill Sr. the short shrift here either. He becomes a superstar

lawyer and he becomes a co-founding partner of the firm Preston, Gates, and Ellis, which today, I didn't even realize this until I dug in the research, that is K&L Gates today, one of the largest law firms in the world. Yep. And another fun fact that you probably know about Bill Gates, Sr., but we got to, that's being acquired, talk about. Do you know what corporate board he joined later in life? I do not. Costco. Of course. Bill Gates Sr., we should say, too, basically galvanized the entrepreneurial community in Seattle. He started the Tech Alliance. He was a huge angel investor.

He really did organize, you know, angel investors, people who want to put high-risk capital to work into startups. And his heart was there, obviously, through his law practice long before Bill Gates III became the prodigy he became. Totally. And that's the point we want to land here is for young Bill, Trey, growing up here, he is growing up in a pretty unique household. He would later talk about being like nine or 10 years old. And most nights at dinner at his house, there would be a CEO or a senator or a governor or somebody who's just over for dinner.

And Bill would sit there and absorb the business conversation. You know, it's like the Hermes family, the Dumas family that we talked about on that episode. You know, this whole thing, it makes me think of Paul, the main character in the Dune movies in the book. Like he's kind of bred from birth to be this incredible business mind. I mean, at age 13 with his best friend, who we will talk about very soon, he brought up the idea, I wonder what company I will be the CEO of when I grow up? What industry will I go after? What problems will I tackle? It wasn't a question of if, but which. Yes. And it just turned out that

he would be the CEO and founder of the biggest company in the biggest industry ever to exist. The other thing that we got to say about Bill growing up, he is insanely competitive. So he did not and does not like to lose at anything. And that is putting it mildly, whether it's sports or swimming or computers or school or the classroom. There's a quote in one of the books we read from a childhood friend of his who says, everything Bill did, he did competitively and never simply to relax. I think this used to be more than today. There's kind of this image of Bill Gates that he was a computer nerd, that he was like this shy little skinny kid. And the way he looks doesn't help this, but that is not the case at all. This guy had a competitive fire in him. I'm sure still does like none other. Well, both things can be true. He was

the number one math student in the state of Washington. He was a nerdy kid and a brilliant kid and also fiercely competitive. His childhood friend and co-founder of Microsoft, Paul Allen, would say about him, you could tell three things about Bill Gates pretty quickly. He was really smart. He was really competitive. He wanted to show you how smart he was. and he was really, really persistent. That sounds about right. So famously, speaking of Paul and where Bill and Paul meet, when Bill is in seventh grade, his parents enroll him at the Lakeside School, which now I think is internationally famous because of Bill, but it is a super rigorous college prep school, middle school and high school. And Bill ends up writing the scheduling software for class scheduling.

And he puts himself in the classes with all the girls. Like, oh, funny. But y'all, like this, Bill, 13 years old, seventh grade, Lakeside. This is when it starts. Obviously, Microsoft doesn't start. But during that year, Bill is 13 years old, the Lakeside Mothers Club raises money to buy the school a teletype and connect it up and rent computer time from a DEC PDP-10 that is located in downtown Seattle and owned by the branch office there of General Electric.

Now, probably a bunch of you are like, I have no idea what any of those words mean. So we got to set some context. This is 1968. 1968, you know, the Beatles, Vietnam, the Summer of Love. This is not the computer age. 2001, a space odyssey had just come out. Nolan Bushnell has not founded Atari yet. Bob Noyce and Gordon Moore are only just leaving Fairchild Semiconductor to start Intel. Silicon Valley is still dominated by Lockheed. There is no such thing as a microprocessor.

The United States would land on the moon one year later. Totally. The way computing worked back then, it was basically still the ENIAC days. A computer meant two things. It either meant a massive room-sized machine that had about the computing power of a calculator, or it meant a human. People talked about computers as humans. Did you ever see the movie Hidden Figures about the Black women who did the calculations? Those women were the computers. They were called the computers, yes. Because they would sit there and compute.

This was a totally different era. So the idea that a 13-year-old kid in this high school, this middle school, would get access to share computer time. I can't imagine there are many other secondary schools in the country that were doing this. Yes. This is a very early place to make the point. Microsoft is the result of tremendous intelligence, brilliant strategy, fierce competition, and an unbelievable amount of luck. Bill Gates was born in 1955, the same year as Steve Jobs, to come into adulthood just as the personal computer wave is starting. And the fact that he was at a middle school and had this much privilege where he could get access to a PDP-10

at this point in his life to help him understand how important computers would become, I mean, there are dozens of people in America who are as well situated as Bill is, and that might be overly generous. He and Paul got a sneak peek into the future there at Lakeside. Now, it's funny, you said the personal computer era. We are so far away from the personal computer here. I mean, we got us at the stage. What is computing? I mentioned ENIAC and these room-sized things. Computers did not have screens. You didn't have cursors. You didn't have lights. You didn't have pixels. Everything was done on a teletype. They kind of looked like typewriters. And they were wired up remotely, either in the same facility or like what Lakeside is doing. You

could be remote. I mean, it's almost like the cloud today. And it called over a phone line. That was the teletype. Yeah, exactly. Got wired over the phone line, hooked up to these mainframes. And so you typed commands into this teletype. And then the response came back over the phone line or over whatever cable from the mainframe. And it got printed out on a spool of tape on the teletype. But this is power that normal 13-year-olds don't come anywhere near accessing. What is the computing market at this time? It is pretty much, we'll come back to the pretty much in a minute, 100% dominated by IBM. Oh, yes. IBM, big blue, big iron is what it was referred to, like the products

that they would produce. They were the industry. Yes. Ben Thompson has a fantastic quote on this. He has an article called, What is a Tech Company? And here's his comment. 50 years ago, what is a tech company was an easy question to answer. IBM was the tech company, and everybody else was IBM's customers. That may be a slight exaggeration, but not by much. IBM built the hardware, at that time the System 360. They wrote the software, including the operating system and the application, and provided services, including training, ongoing maintenance, and custom line of business software. Yeah, System 360 was a line of solutions, I would say, offered by IBM. And it consisted of

the thing, the room-sized thing, the mainframe, and the software, which was System 360, and the consulting, and the implementation. You couldn't just call up UPS and forklift one of these things into a company and expect it to work. No, you got to operate this thing too. Totally. It's like ASML machines. You don't just go ship them off to TSMC and say, good luck making semiconductors. Exactly. It's a full solution, full service thing. But an important thing that was also happening this year, 1968, was that IBM was undergoing some antitrust scrutiny over that huge bundle that I just told you about. I mean, doesn't it smell like antitrust? They do everything from the hardware to the software to the operating system, the service, the support. They are the whole market.

They're starting to get concerned. And so proactively, they unbundled hardware, software, and services, and they started selling those separately for the first time, which was not a problem at first. But what it did was it cracked the door for customers to say, oh, I can buy hardware from IBM and software from someone else. And other people were not exploiting this, but it was possible. Yeah, interesting. It cracks the door for Microsoft like 15 years later, 20 years later. Yeah. Yes. But this is where the seeds are sown of what is the exploitable opportunity when Bill Gates is ready to do something. Interesting. Now, back to the timing thing for Bill and Paul and Microsoft. I mentioned

when we were setting this up that there's something else to talk about here. IBM was facing a disruptive force at this moment. I think probably for the first time in its history, certainly in the computing era of IBM's history, and that was the Digital Equipment Corporation, or DEC. Notice when we said earlier that Lakeside is renting computer time from the General Electric Computer in downtown Seattle, I said it's a DEC PDP-10. It's not an IBM product. So what's DEC? They're the mini computer company. Mini in quotes. Yeah, mini, quote unquote. Mini meaning it was the size of a closet, not the size of like a room. It's all relative. DEC had been started by this guy, Ken Olson from MIT. And what they did, he had this brilliant insight that would play out over and over and over again in technology that I'm not going to go compete with IBM head on. I'm not going to make ENIAC. I'm not going to make mainframes. But computing has advanced enough that there's an opportunity to make something smaller, less powerful, more sort of toy-like.

And there's enough demand out there that I think I can find some new markets for people who will buy those types of computers. And it's smaller businesses, but in particular, it's like branch offices of the big companies. So I am sure General Electric bought lots and lots and lots of IBM mainframes and products at their headquarters. But the GE field office in Seattle, they're not going to truck in a mainframe. And in 1968, Seattle, I mean, this is like a provincial little town. I'm standing here right now. It's a, you know, major city and a huge economy in the United States.

But at the time, kind of a podunk, forgotten, sleepy, faraway place. Totally. And Microsoft would go a long way to changing that over time. And we should say this is the classic low-end disruption playbook. I mean, this is what Clayton Christensen was talking about. Going from mainframe to midi computers, I'm going to make something that's worse for most things, but better for some new things that new customers and new markets are going to care a lot about. And IBM's going to look at it and go, that can't do any of the things that are important to our customers. And that's exactly why it works. And specifically, why are they not going to care about it? I don't know exactly what an IBM mainframe system, system 360, 370, whatever cost,

I'm imagining tens of millions of dollars all in total cost, maybe hundreds of millions of total dollars to run a system like that and buy it. So the first deck machine, when it comes out, the PDP-1 a few years before this time, it was priced at $120,000. So like an order of magnitude, maybe two below a system that you would buy from IBM. Obviously still a long, long, long way from the personal computer. People are not buying these things for their houses. But you know, yeah, GE will buy one for the field office in Seattle, or universities will buy them for research, for their students, for their professors. And so DEC kind of creates a new market for computing. And Bill, he's so studied in business history, the founder, Ken Olson,

Ken is Bill's hero. He totally looks up to DEC and what DEC's done. Now, the DEC and mini-computer UI is still the same as the mainframe. You're still using a teletype. There's no innovation in terms of what the computing is or how you use it. It's just cheaper grade. And Lakeside is a middle school and a high school. The high school is actually in a separate building. The computer room that gets installed with the teletypes, that's over in the high school. But Bill, he doesn't care. He gets exposed to it, I think, in a math class one day. And he's like, oh, I'm hooked. So he goes over. He's hanging out with the high schoolers, teaches himself how to program. And pretty quickly, he becomes known as one of the very best programmers there. And he and three other kids form what they call themselves the Lakeside Programmers Group. And one of his buddies who he forms it with is, of course, the high schooler, I think the 10th grader at the time, Paul Allen.

There is a fantastic photo, listeners, that we will tweet of Bill and Paul sitting in the computer room at Lakeside. And Bill, I think he's like 13, 14. He looks like he's about eight. I think on the wall, there's this almost like printed out magazine thing that says the bug slayer that they've hung up over the wall. It's amazing. So these high school kids, they start the Lakeside Programmers Group. They call it the Programmers Group because they are programmers. This is another super important thing to learn. To use a computer at this time meant to be a programmer.

Right. There was no packaged software that you bought. The software that IBM was selling was the operating system to make the machines actually function. And it was the programming languages to make the machines actually function. And it was the programming languages that you could then program on, but you weren't clicking around and using Excel or like, you know, pulling up apps. Everybody who used a computer wrote their own software. Right. There was not this multi-sided network of you've got developers making applications, and then you've got users of those applications. No, everybody who used a computer was a programmer.

So the goal of the Lakeside Programmers Group, remember Bill is this business prodigy, is to use their very valuable and very rare skills as programmers at this time to, you know, make money, do a business. So turns out, at the same time, I mean, the coincidences here are just crazy. There is a local startup coming out of the University of Washington called the Computer Center Corporation or C-Cubed. And the business plan behind C-Cubed was that they were going to get a bunch of decks, a bunch of PDP 8s, 10s, 11s, whatever. And they were gonna be like AWS. They were gonna just be a computer time-sharing company. So C-Cubed hires the Lakeside programmers group, these kids,

to come in and find and document bugs in the system. And they're gonna pay them directly in computer time. So when they come into C cubed, they learn Fortran, they learn Lisp, they learn machine language for the PDPs. Back at Lakeside, they were just using BASIC, the programming language. Which is reasonably high level in terms of how abstract it is. Like you're not writing machine language. You don't have to know how to address memory and registers and all that. It reads kind of like English. You know how to add numbers together. It's not an elegant language, and it's a very verbose language. But if you sort of look at it with your eyes as a person who speaks English and knows basic math, you're like,

I kind of understand what this program does. So there's a meaningful amount of translation done by a basic interpreter that takes you fromASIC code you have to write to what is actually running on the machine. Yes. But BASIC, we don't want to give the impression that it is just BASIC or just for kids. No, it's widely used. It's going to become hugely, hugely important. It is both the gateway programming language for everybody, but it's a real programming language, and a lot of stuff is done in it. It's sort of the Python of its day. I think the way Python is now, or you sort of joke that Python is so flexible, you know, you can like accidentally write a program by writing English and it can kind of forgive a lot of mistakes and it reads kind of like English.

It's a reasonable parallel to draw it way back when with BASIC, where you say, look, you can understand it as a layman, but also it's used in a broad set of business applications. Totally. When Bill and Paul and their buddies come into C-Cubed, they're now getting access to learn real hardcore systems programming languages, including machine code for the PDP-10. They're becoming pretty prolific engineers here. They're handwriting assembly code. Yes. And they're getting mentored. One of the executives at C cubed is a guy named Steve Russell. Did you find this, Ben? Do you know about this? No. This is amazing. You're going to die. Steve Russell was the guy who wrote Space War when he was at MIT on the first PDP, the PDP-1.

He's like a computer science legend. Nolan Bushnell told us about that. Yes. Space War was the first video game, first computer game ever written. It was written as a fun side project by some MIT engineers in the early days of DEC. And then that became Nolan Bushnell's inspiration for starting Atari and Pong and Space. Like, yeah, Steve Russell, that guy. Wow. He mentored Bill Gates.

And he was here at the University of Washington? He had come out to the University of Washington and then left and was part of one of the execs starting this company. C-cubed, wow. That's like a mile from my house. Right? Crazy.

Wow. So after a little while at C-cubed, all of this real expertise that these kids are getting leads to another opportunity at another timeshare computing company based down in Portland. They ask the kids to write a real piece of software, to write a payroll billing program for all their clients that are using the timeshare system. And Bill, now who's the de facto leader of this group, he negotiates a deal with the help of his dad, Bill Gates Sr., prolific corporate attorney in Seattle, that rather than just being paid hourly for their time, they're going to get a royalty on the revenue that their client makes on the software. I can't believe it. These kids are teenagers. They're figuring out the whole software business model here. They end up making at least $10,000 from these royalties, which the

average household income in the US at the time was below $10,000. These kids are rolling in money. Wow. So the next year, Paul graduates from Lakeside and goes off to college at Washington State. But he and Bill decide to team up on a new venture that they're going to do together called Traf-O-Data. They've identified a market opportunity, and that opportunity is reducing traffic. Yes. So the business plan is that municipalities count cars that go through intersections, use that to make decisions about how they're going to do city planning.

Bill and Paul are like, we can take this new thing that's coming out of Intel, a microprocessor, which is promising to be a full computer on one chip. And we can use that. We can build a machine that is going to be a computer and it'll process and analyze that data. And then we can sell it to governments. Like, great, big market. And listeners, are you kind of sensing what's happening here? Mainframe, mini computer, microprocessor. We kind of have to keep using smaller and smaller words to represent the fact that the computer is getting smaller and smaller here. It wasn't until we started doing research

for this episode that I finally realized, oh, microcomputers, which is the original term for the personal computer for the PC. It was called microcomputers before PC caught on. They're called microcomputers because they're based on the microprocessor. Yes, absolutely. It's not just that micro is smaller than mini. And it is funny that it kind of stopped there. The computers that are sitting on all of our desks are microcomputers. Right. Yes. So while they're waiting for the AD-08, this new first microprocessor from Intel to come out, or at least for them to get access to it, they want to get a head start on programming their traffic data machine and programming this

microprocessor. So Paul's like, I got this. I can find a way to make this happen. He takes the PDP-10 at Washington State, and he writes a whole emulator program to mimic the instruction set for the AD-08 from the manual. And they get a full emulator up and running, and they can code even without the microprocessor actually being there and having access. It's just like NVIDIA. When Jensen was like, no, we got to build an emulator and simulate this, and then we're going to ship it sight unseen. They're doing the same thing. It's funny. In many ways, at this point in history, getting a manual was actually much more valuable than getting the processor itself, because the processor would arrive. And unless there was documentation, you would have no idea

how to interact with it to take advantage of its power. But if you had a manual, well, sure, you couldn't actually test the stuff you wrote for it on the hardware. But if you wrote an emulator on a bigger, more powerful computer that could sort of mimic the computer that you're actually targeting, you could go years before actually ever running the software on the target device and just work off of what the manual says, as long as the manual is correct and matches how it actually works. Yes. And this is going to become very important to Microsoft in just a second. Yep. So traffic data is not a huge success. I think I read a few places they make about $20,000 in revenue from it. So like, again, great money for high school and college kids, but you know, not world changing from it. So again, great money for high school and college kids, but not world-changing stuff here. This is not what Bill aspires to for the company he's

going to start. But Bill and Paul are getting experience with the microprocessor. Bill actually has the idea for Microsoft when they're working with it. He's like, oh, this is a computer. Why don't I go off and write an interpreter for basic here and we can sell the basic interpreter for the microprocessor and build a big business. The AD-08 just wasn't powerful enough yet to do that. But spoiler alert, that totally becomes Microsoft. The seeds of Microsoft are selling language interpreters for new processors, new hardware, new computers that enable you to write familiar programming languages on that new hardware. Yep.

And, you know, Bill and Paul are not the only ones having this insight here, too. Another Seattle guy named Gary Kildall, who they had intersected with, who they knew from C-Cubed and the University of Washington. He kind of had the same idea here. We're going to bring up Gary and his company, Digital Research, a little bit later. Yeah, he cared a little bit less about programming languages and a little bit more about operating systems. So that's how they diverge for the few years here. Yep. But Bill and Paul, they absolutely see the vision for what this can grow into and become. Bill has a great quote. Paul and I had talked about the microprocessor, and it was really his insight that because of semiconductor improvements, things would just keep getting better.

I said to him, oh, exponential phenomena are pretty rare, pretty dramatic. Are you serious about this? Because this means, in effect, that we can think of computing as free. It was a gross exaggeration, but it was probably the easiest way to understand what it means to cut costs like that. And Paul was quite convinced of it. Yes. Is this in the Smithsonian interview? Yes. So good. It's so good. This quote is incredible because basically Paul Allen brings up Moore's law to Bill Gates. They don't use that language there. But in 1971, that is what's happening. And for Paul, this is just an observation of, hey, there's an exponential thing happening here.

Seems like it's going to keep happening. It's been happening. And Bill's shaking. And he's like, what? Exponential phenomena don't just happen. That's incredibly, incredibly rare and immediately gets Bill's wheels turning on, what does this mean for the world? If that's actually true, we need to act and do something profoundly different than anyone's ever done before because this enables new things that no one ever thought could be possible. This moment is the genesis of the vision for Microsoft. Even though Bill doesn't say the words in this quote, the vision of a computer on every desk in every home, that's the famous part and then the part that got left off

later when the DOJ started sniffing around was running Microsoft software. But that is the vision here and it is crazy at the time. A computer on every desk and in every home, Bill sees that this is what this exponential phenomenon, what Moore's Law means, that that is going to happen. You know, we're still in the era of teletypes. Nobody else sees this. Yeah. And it's also the reason why Microsoft is going to form into such a different type of company that's ever come before it. Why they can break all the rules, why they can sell just software, even though that's never been before it, why they can break all the rules, why they can sell just software, even though that's never been a thing before, why their business model can be so much different than everyone else's business model. I mean, in prepping for this episode, we got to talk with

Pete Higgins, who ran Excel and was an executive overseeing office for a long time in the early days. And he had this great quote to us, which was, computer on every desk was wackadoo stuff. People laughed at it. It was absolutely wild. People thought, I don't know, maybe one in 10 people in their finance group or something will have one at some point. This is the profoundness of an exponential decrease in price or increase in power of computing is it's going to become universal. So all that said, even Bill and Paul know the AD-08, it's not there yet. It's not powerful enough to really be a general purpose computer on a chip, but they know it's coming. So in the fall of 1973,

Bill goes off to college at Harvard, famously. It's funny, at Harvard, kind of like Jim Simons that we talked about at MIT on the Rentech episode. Bill thinks he's going to be like a world-class mathematician and set the world on fire. It's literally a quote from Paul Allen. So Bill was the number one math student in the state of Washington. And he gets there and he does this theoretical math class, Math 55, and gets a B. And Paul says, when it came to higher mathematics, he might have been one in 100,000 or better. But there were people who were one in a million or one in 10 million. And some of them wound up at Harvard. Bill would never be the smartest guy in the room. And I think that hurt his motivation. He eventually switched his major to applied math.

Yes. So while Bill's at Harvard, he's also doing a bunch of the typical college kid stuff. He's playing poker, he's cutting classes, he's making friends. And one of the friends he makes there is a kid down the hall from him named Steve. Steve Bomber. And Bomber, everybody knows Bomber. He's kind of everything that Bill is not. He's super social. He's super outgoing. He's in a final club, which is like a big thing in the social scene at Harvard. He's gregarious. Anyone who's ever met Steve or seen a video of Steve, you are well aware that this man has presence. But the thing that people don't know about him is he is so unbelievably analytical. Steve is the guy that outscored Bill Gates on the Putnam exam.

Which is the annual math competition for college students. Yeah. Steve isn't a programmer, but he is every bit the mathematician that Bill Gates is. And that is one of these things where I think when people try to set it up as well, you know, you've got the brilliant programmer genius and the marketing guy. It's just like, those are the roles they took. But I think when you're getting a sense of who the original crew was at Microsoft, they were all brainiacs and they were all wildly analytical. Totally. So then in the spring of 1974, Bill's freshman year, Electronics Magazine publishes big news about a new Intel chip, the next generation, the next turn of the crank on

Moore's law, the 8080. And in Bill's words here, all at once, we were looking at the heart of a real computer and the price was under $200. We attacked the manual. I told Paul, DEC can't sell any more PDP-8s now. It seemed obvious to us that if a tiny chip could get so much more powerful, the end of big unwieldy machines was coming. Yep. And this is really where Bill Gates commits to computers to be his life's work. I think what's often lost in the story is Bill, even though he was good at computers and spent tons of time programming computers, he never fancied himself a computer guy until this moment in history. He went to Harvard because he felt like, hey, if I ever want to be a lawyer or something else, they've got a lot of great programs there.

And this was the moment where I think it really clicked for him that I'm just in the middle of the right place at the right time with the right skill set. And this is my way of having the most impact on the world. So they think, okay, what's clearly going to happen here is all the big computer companies, IBM, DEC, the big Japanese computing companies, they see this, they're going to get into this business. They're going to make machines and they're going to make microcomputers. Surely they will jump on this opportunity, right? If it didn't destroy their existing business model, sure they would. Exactly. So Bill and Paul kind of are sitting around waiting through 1974 and 1975 being like, hey, when are the 8080 computers going to come out?

Where are they? It's just crickets. Yep. Paul is so convinced that the revolution is coming that he actually drops out of Washington State, moves to Boston to be close to Bill so that they can be ready when it happens. And that summer, they both get summer jobs at Honeywell as programmers. Paul stays on into the next school year when Bill goes back to school. He's just like waiting, waiting, waiting. And then in December 1974, Paul is walking across Harvard Square and he sees in a newsstand the January issue of Popular Electronics, on whose cover is the Altair 8800, the world's first real, honest-to-God, commercially available-for-sale microcomputer. And the legend has it that Paul grabs the magazine, runs over to Bill's dorm, throws open the door, throws the magazine on

the desk, and is like, it's here. And Bill just says, oh my God, it's happening without us. We need to get on this right now. Well, it's so funny he thinks they're already behind because clearly they're not. History would show, I think Bill Gates even says, we might have actually started a year or two too early. The market actually hadn't materialized yet. And the funniest thing is the starting gun went off and Bill and Paul ran and everyone else is still standing around. And this is it. This is the moment the revolution is here. Microsoft is about to be founded. Okay, listeners, now is a great time to tell you about longtime friend of the show, ServiceNow.

Yes, as you know, ServiceNow is the AI platform for business transformation, and they have some new news to share. ServiceNow is introducing AI agents, so only the ServiceNow platform puts AI agents to work across every corner of your business. Yep. And as you know from listening to us all year, ServiceNow is pretty remarkable about embracing the latest AI developments and building them into products for their customers. AI agents are the next phase of this. So what are AI agents? AI agents can think, learn, solve problems, and make decisions

autonomously. They work on behalf of your teams, elevating their productivity and potential. And while you get incredible productivity enhancements, you also get to stay in full control. Yep. With ServiceNow, AI agents proactively solve challenges from IT to HR, customer service, software development, you name it. These agents collaborate, they learn from each other, and they continuously improve, handling the busy work across your business so that your teams can actually focus on what truly matters. Ultimately, ServiceNow and Agentech AI is the way to deploy AI across every corner of your enterprise. They boost productivity for employees, enrich customer experiences,

and make work better for everyone. Yep. So learn how you can put AI agents to work for your people by clicking the link in the show notes or going to servicenow.com slash AI dash agents. So David, they're like,

it's happening without us. What do they do? Well, they do the natural thing that two super excited, ambitious, high-octane college kids would do. They call up the main phone number of Altair's manufacturer, a company called MITS, M-I-T-S, and ask for the president, a man named Ed Roberts. And Bill and Paul, they get him on the phone, and they say, we have a basic interpreter ready to go, ready to ship for the 8080 Intel chip, and we want to provide it for you, for your machine. Which... Of course they don't. They don't have a single line of code written. They don't have anything.

But it's a market test. They want to know, like, what's the response if this were true? Exactly. And he's a bit of a character himself. He says, okay, well, guys, a lot of other people are calling me and saying the same thing. What I'm telling them, and I'm going to tell you too, is that anybody who can come here to my office in Albuquerque, New Mexico, and demonstrate a working version of BASIC on my Altair, will get a contract with us to distribute it when they go on sale. And so Bill and Paul,

they say, okay, great. We'll see you soon. And hang up. And by see you soon, they mean, let's go get to work. And this is a big deal for MITS too, if this works. Because right now, they've just announced a machine for which you can't really do anything on it. The hardware is powerful, but they're not going to have a lot of customers unless there's stuff you can do on the machine. And a basic interpreter running on it,

you know, it's quite valuable to then make the claim, you can program BASIC on our computer. So they're very excited about this, even though they're kind of playing coy. I was going to talk about this in a minute, but let's talk about what the Altair is. What did they just announce in the magazine here? This is, the Altair is the first mass market commercially available personal computer. Again, no screen or anything. Yeah, does not have a screen, does not have a keyboard,

doesn't have a display of any kind. What it does have is it has a set of 16 lights on the front of the machine, like Christmas lights, and 16 switches. And you can flip the switches to flip bits, and then the machine will respond by lighting up different patterns of lights. It doesn't come with any software. There's nothing. That's all it is. 16 lights, 16 switches. So in order to use it, you got to hook up your own teletype. You got to get the manual. You got to hope that the manual is right. And you got to code to the machine instructions, like literally the assembly language for the chip inside for the Intel 8080. Now, back to the Trafo data days and Paul writing the emulator for the 8008 at Washington State. Paul's like, we got this. I'll just write an emulator on the

Harvard PDP-10 for the 8080 instruction set. So he does the same thing again. They get the manual and they have an emulator and they write it against an emulator. Yep. Bill writes the basic interpreter. And in a couple weeks, they've got it working. And Ed's like, okay, come on out to Albuquerque. So Bill and Paul, remember, Bill still looks like he's 12 at this point in time. They decide that just Paul should go. And does Paul have like a rockin' beard at this point yet? Oh, Paul is super 70s. He is like into it. And as we'll see, he's going to fit right in

at Albuquerque in myths. So Paul gets on a plane, flies from Boston to Albuquerque, and, you know, in a total like epic legend moment, they didn't have a bootloader written for the basic interpreter. So they had the basic.

It was all written. They'd done it on the emulator. And Paul's flying out with the tape, the computer tape, with the code of the basic interpreter on it. But he's like, oh, shoot. We can't just feed that right into the machine. There's got to be a bootloader to load up this thing. So he writes the bootloader on the plane.

On paper, by hand, he is hand coding octal, not even assembly language instructions, like he's hand coding in pure octal the instructions to load their basic interpreter program into memory. Yep. So he lands in Albuquerque, drives out to MITS. They load the bootloader onto the prototype Altair there that loads up the basic interpreter and it fails. It doesn't work. Paul's like, let's try it again. Let's try it again. So they try it again. You know, this is how early computing is. Like it works the second, like who knows what the bug was the first time. They didn't change anything. It just didn't work the first time and it worked the second time. So it loads up. Paul writes in the instructions, print two plus two. It spits out four. And by

spits out, I mean like the lights light up and say, you know, four. And both he and Ed, their jaws are on the floor. Paul's like, oh my God, the basic works. And Ed's like, oh my God, the Altair works. Neither of them believed this was actually going to work. And Ed actually has more eggs in this basket than he sort of let on because when Bill and Paul call and say, hey, can you give us the teletype instructions? He reveals they're actually the only ones who called about that. So everyone else who said they were writing a BASIC never got far enough to ask, how do we actually interact with your computer? Yes. So now is the time to say a few words about Ed and MITS. What is this company? Bill and Paul originally thought that it was going to be the IBMs, the DEX, the Japanese companies who are going to make the

first microcomputers. MITS is about as far away from IBM as you can possibly imagine. MITS basically was a model rocket company. Which Albuquerque is a great place to do that. Ed Roberts, the founder, he had been in the Air Force and stationed in Albuquerque. And that's how he got involved in model rocketry. And the reason that they're introducing the Altair and they made this big splash in the magazine was this is a last ditch gambit to try and save the company. So you got like a bankrupt model rocketry company. And their little gambit worked and got a couple of college kids to pounce. Totally. And like, why did it work?

They had two things going for them that really Ed, I think, probably personally made happen. One, they got this splashy popular electronics magazine cover. That was through a relationship that Ed had. And two, the sticker price was $397, which is about $2,300 in today, $2024. Yes, that's a lot of money, but the next cheapest computer that anybody could buy at this point in time was like a deck, you know, like $120,000 mini computer. So the idea that somebody could buy a computer for $400, I don't care who's selling that thing. Like I want that. So what did they get some kind of sweet deal from Intel?

Yes. So this is all Ed's doing. The list price from Intel for the 8080 chip was $360. So I think this is part of what was deterring the market of how would anybody sell a kit that was affordably priced when so much of the cost of goods would go to Intel with the processor deal. He managed to negotiate a volume deal with Intel to get 8080 chips at 75 bucks a pop. Whoa. And that was the key unlock. That's like a 5x price reduction. Totally.

Huh. I wasn't able to find how that negotiation went down or why like Ed Roberts in Albuquerque, New Mexico got this sweetheart deal from Intel. I mean, either the list price is like wildly wrong, or they were cutting deals all over the place. Or one thing it could have been is just that, and I'm totally speculating, but chips are the ultimate high fixed cost investment, low marginal costs next to software. You could imagine maybe Intel had already put all the money into the fixed cost of spinning up the

fabs and was expecting a certain amount of market demand. And they weren't seeing it. They were like, crap, we got to recoup our investment. I don't know, lower the price, let them just sell. Maybe we'll make it up in volume. I like that. I have no idea, but that's a totally viable, I think, train of thought here. Either way, he gets the sweetheart deal. And not only does it make computer history and enable and create Microsoft, it saves the company of myths. So they were on the edge of bankruptcy. After the Popular Electronics article comes out, they get 4,000 pre-orders in the first month or two, which is

$1.5 million in revenue, cash paid upfront. That is pure cash hitting the bank account. That'll save a company. And also just proves, hey, 4,000 people just paid cash sight unseen for 16 lights and switches. There's a lot of demand for a home computer here. And at decent margins too. I mean, if they're getting the processor for 72 bucks and they're selling it for, what did you say? $397. Yeah. So I mean, everything else in there is much cheaper 72 bucks and they're selling it for, what did you say? $397. Yeah, so I mean, everything else in there

is much cheaper than the processor. So I don't know, depending on how much they have to give to the sales channel they're selling through, if it's retail or distributors. I think they're selling direct. I think people are just sending money orders. Yeah, so it's decent margin business.

Unlike what the PC business would become over time, they managed to have nice margins. So Paul and Ed, they kind of hit it off. Paul decides to move out to Albuquerque to be close to the action here. And he actually joins MITS as their vice president of software. No, he's vice president of a software department of one. He is the software department here. Yeah, software department of one. But you know software department. Yeah, software department of one. But, you know, he's got his buddy Bill Gates, who is not employed,

but Bill's definitely working on software for the Altair as well. Yes. So Bill stays at Harvard, but keeps cranking on enhancing the BASIC interpreter and adding more functions and functionality to the version of BASIC that they had just written for the Altair.

And then once the school year is over, he comes out to Albuquerque too for the summer. Now the Altair is getting ready to ship with the BASIC, the Microsoft BASIC included in it. Bill and Paul kind of need to set up a company, but Paul is an employee of MITS at this point. So what did they do? They set up a partnership. So the founding of Microsoft at this point, micro-soft, is a two-person partnership between Bill and Paul. And as we record this, that was 49 years and one day ago. So we are sitting here on April 5th recording. That was April 4th, 1975. And it is very funny to look back at some of the original signatures when Bill writes on letters. It's Bill Gates, the general partner of micro-soft, which is great. I think it's actually

a Paul Allen name where he wants to put together microcomputer and software. And Bill's like, that's perfect. We're immediately just going to run with it. As it was a partnership, originally, they were going to call it something like Allen and Gates. And then they ultimately are like, no, Microsoft is perfect. Microsoft has become like Kleenex. But like, no, it's like Microsoft means microprocessor software. I will say like, it's a nice clarifying North Star because it really draws the line in the sand and says, we're in the software business. And Gates makes this really clear to Paul Allen, who is often tempted to do hardware stuff. And Bill is very hardcore about saying, no, what we're uniquely good at in the world is software, and we should stick to that. I also suspect Bill is starting to realize there's an amazing

business model here, if we can pull it it off where we don't have to make the hardware and we can charge for every copy of the software sold. But that insight, I would say, has not yet fully materialized. Yeah. Oh, okay. Well, let's talk about business model here in one sec. First, though, on the partnership, again, we've been saying all along that Bill is clearly the leader here. They set up the partnership. Initially, it's 60-40 ownership. Bill is 60%. Paul is 40%. Later, it gets changed to Bill is 64% and Paul is 36%. So like, yep, Bill is the leader here. Yep. And Bill's case that he makes on that to Paul is, hey, you took a job and you were doing this on the side. I was all in. And Paul's an agreeable

guy and 36 is still a nice percent. And so he says, sure. You know, in the long run here, everybody gets rich. So it's all sort of a rounding error. But to that point, back to the business model. So once the partnership is set up, they sign an exclusive licensing arrangement with MITS. This is super important. This is a big lesson that young Bill and Paul are going to learn here. So MITS gets exclusive license to the basic interpreter, to the basic as they call it, for the 8080. And MITS is the one that can then decide whether to sub-license the BASIC out to other companies or not. Huh. Essentially, this is a distribution deal with MITS where MITS becomes the exclusive seller and distributor of Microsoft's BASIC. Microsoft doesn't have any direct sales control here.

That's going to become a big, big, big issue. And the terms of the deal are Microsoft is to get $30 for each copy of BASIC that MITS sells, plus 50% of the revenue that comes from these sub-licensing deals that MITS may or may not do with other companies who want to use the BASIC. Which, why would they ever do any sub-licensing deals? Like, why would you give it to your competitors? Well, that is a really good question, Ben. So let's just round that part of the revenue to zero. Yeah.

This is a big, big, big diverging of interest between Microsoft and MITS. And the kicker on this contract is that the total amount of lifetime revenue that Microsoft can make from the basic from MITS is capped at $180,000. So Ed and MITS really have the upper hand in this deal. Or phrased another way, it's we will give you $180,000 for you to hand over exclusive rights to all that cool basic stuff you just wrote to us. But if we sell fewer than X machines, we're actually going to pay it out to you on a prorated basis at $30 a pop rather than giving you the full $180,000. Yeah, that is another way to frame it. So definitely a great deal for MITS. On the other hand, what are Bill and Paul going to

do here? Right. Kind of a great deal for them too, given the position they're in. Right. MITS. On the other hand, what are Bill and Paul going to do here? Right. Kind of a great deal for them too, given the position they're in. Right. MITS is the industry. Yeah. Now, there is one very, very important clause in the contract though, protecting Microsoft's interests. And that clause is that MITS must use its best efforts to license, promote, and commercialize the basic broadly in the marketplace. And that any failure to do so by MITS would be grounds for termination of the contract by Microsoft. Thank God Bill's dad is a lawyer.

Indeed. Indeed. thank god bill's dad is a lawyer indeed indeed so the altair comes out for sale later in 1975 microsoft does sixteen thousand dollars in revenue that year from their thirty dollars a pop uh the basics that are getting sold with the altair which is great especially the first year that they're starting and the next year in, everybody's so excited about this new market, the vision that's happening, the demand, the Altair, the sales, that Paul Allen resigns from MITS to join Microsoft full-time. Bill drops out of Harvard officially. He moves to Albuquerque. They're all in on this. But for the year in 1976, Microsoft's revenue is still only $22,000. So it was $16,000 the year before, $22,000 in 1976. Not a high growth company.

This is less than they were making in high school. Like, what is going on here? One is sort of like MITS is the one at the controls of sales, not Microsoft. But two, MITS is selling 1,000 computers a month. not Microsoft. But two, MITS is selling a thousand computers a month. This is taking off. This is creating a new industry. Despite MITS selling thousands of computers a month, only a few hundred copies of BASIC are selling per month. What's going on?

People are pirating the software. This is the discovery of software piracy. And this is a pretty interesting time to pause and say, well, are they pirating software? Because... That's a good question. This is 1975. So piracy implies that you are running afoul of some particular legal protection for the good. And you might say, well, with today's legal frameworks in hindsight, you would say, of

course, if they're copying the software and not paying the money for it, it's piracy. That was actually not established yet. And this is the craziest thing. So Bill basically has an opinion that it's piracy, and he writes letters to the computer community. He writes an open letter to hobbyists. Yes, and tries to basically guilt trip people. He tries to use that as a recruiting method and say, if you're so excited about pirating our software, maybe you should just come work with us. And nothing would make me happier than making the best software in the world, and please join us on this mission. But ultimately, the legal standing that he has and say, what about this is protectable? And if you think about it, it is a little bit weird. So you've got source code that looks kind of like English, you know, basic, it's letters and numbers. It gets translated to machine code. That machine code ends up running and it's basically electrons. It's voltages that are

flipped up and down. And so what about that are we trying to protect? Ultimately, the way it gets litigated through some case law from court cases is that the source code is a copyrightable, creative work that is expressed through some sort of tangible medium. That's the important thing about copyright law. It's a creative work expressed through a tangible medium. So a book, the creative work is the words and the tangible medium is printed on paper. And so with software, it actually took until 1980, Congress changed the law. We'll put a link in the show notes to like the literal congressional change that happened. And it is in Title 17, Copyrights, Chapter 1, Subject Matter and Scope of Copyright

in 1980. They include a defined term, which is a quote-unquote computer program is a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result. And once you have that passed by Congress, codified into law, you now have the standing legal framework that all the whole computer industry used going forward, in particular, the software industry, a computer program is copyrightable work. Wow. I didn't know all that. That's awesome. It's totally crazy how recent that is. But when you think about it,

why would that have any legal, you know, software is such an abstract idea. Before, the whole business model of computers was good luck just replicating an IBM PC and everything that comes with it. You don't need any legal standing. But if you're going to pursue this software-only business model,

what's the protection around your abstract product? That's exactly what I was going to say here. This is the other element of what's going on. This is the first time software has ever been sold. Right. Other than the IBM accounting machinations to protect themselves from antitrust, which was just accounting, nobody had ever sold software before. This is the first time. Right. Certainly to build like a legitimate business around it. The other thing that's useful to know is when you're selling an IBM PC,

you're literally selling a PC to a customer the same way that when I'm selling you this glass from Crate and Barrel, I am selling you the glass and the glass is now yours. I've transferred property to you. Software is not that. So the whole world of software is built on a license agreement. So the source code, that computer program, the actual right of that is retained by the creator, and you license the copyright to your customer to be able to use that on their machine. So there's this dual idea that computer software is copyrightable and you can grant a license under certain conditions for customers to use it. That is the legal framework for which the next 50 years of technology at large would operate under. For the moment, though.

They got a piracy problem. Right. The law isn't going to change until 1980. Microsoft would be dead if they didn't figure out a solution to this before 1980. So this is when Bill ultimately kind of realizes, shoot, we did the wrong business deal with MITS here. MITS has to sell and customers have to make the decision to buy our basic is a key critical part of the value of the computer. It's like the whole thing. It makes that machine useful.

Right. Without it, it is not useful. It's totally setting up the wrong incentives and value equation that customers should be buying this themselves. It should be included by the hardware OEM in the machine that they are selling and in the total purchase price. And then if that happens, we no longer have a piracy problem because we're just getting paid as part of the purchase of the machine. Right. It should be a royalty.

Right. The problem is that is not the deal that they had with MITS. Right. Or framed differently, instead of saying, hey, consumer, do you want to buy something else too and make a new purchase decision? They should be saying, hey, computer manufacturer, we make your thing actually useful, so pay us for it. Yes. So during 75 and 76, MITS pretty much had this new microcomputer market all to themselves.

There were a couple other competitors who sprung up, but nothing made it. The Altair and MITS was the microcomputer company. All that changes, though, in a big way in 1977 when what Byte Magazine calls the 1977 Trinity hits the market. And that is three machines, the RadioShack TRS-80, Tandy slash RadioShack TRS-80, the Commodore Personal Electronic Transactor, or the acronym PET, and the Apple II. All three of which machines were, like the Altair, low cost, mass market. Unlike the Altair, they were not kits. They were fully assembled, fully functional, right out of the box. And they each had their own major distribution advantages.

And in Bill's words, these three machines, the 1977 Trinity, ignite volume in the market. Bill loves these really dramatic verbs, like we attacked the manual. They ignite the volume in the market. Oh, and the press just latches onto him. Whenever Bill has a leaked memo or something where he talks about all this war terminology, those all become headlines. So great. Now, earlier, during 1976, Microsoft had started getting approached by a few of the bigger

computing companies like ncr national cash register ge control data systems i want to license microsoft your basic for the 8080 microprocessor here so that we can experiment with these things and each of these deals would have been revenue to Microsoft of like $100,000-ish. But Ed and MITS, they keep dragging their feet on negotiating these. They've got the exclusive license. Everything's got to go through MITS. And most of them, they're turning down because, Ben, like you said, they don't want anybody to come in and compete with them. Yep. There's the misaligned incentive. There's the misaligned incentive. And there is the clause that Bill and Microsoft, and I presume Bill Sr. put in the original agreement, is MITS using its best efforts

to commercialize the basic and gain adoption in the market. And you can make a pretty strong argument that they're not. So Ed, though, unbeknownst to Bill and Paul, he has another reason that he's dragging his feet on these deals, which is that he's about to sell the company. So in May of 1977, MITS gets acquired by the tape drive manufacturer Pertek for $6.5 million. And Ed kind of rides off into the sunset. And Pertek, they know about this dispute with Microsoft and they sort of come in and they figure like, who is this Bill Gates? He's a 21 year old kid, a college dropout. Like we're a big company. We can deal with this. And Robert says an amazing quote later. He says, Pertek kept telling me they could deal with this kid. It was a little like Roosevelt telling Churchill that he could deal with Stalin. Oh my God. Oh boy. And I also don't think they

realized that this kid's dad is one of the best corporate attorneys in the country. Yeah. Well, Bill Gates was just constantly underestimated, which kind of worked to his advantage in those early days. Yes, totally. This is the thing about Microsoft. People kind of forget how his advantage in those early days. Yes, totally. This is the thing about Microsoft. People kind of forget how insanely young Bill was. He was just 20. And to put that in context, he's only seven years older than Jensen Huang. But they feel an entire generation apart since Microsoft was started almost 20 years before NVIDIA. When you start bending your mind around like, oh, Bill Gates is still pretty young,

considering what an institution Microsoft has become in the world. Right. I mean, Microsoft next year is going to have its 50th anniversary. And I believe that'll also be the same year that Bill turns 70. That's wild. Yeah. So that fall in 1977, the dispute between MIT slash Pertek and Microsoft goes to arbitration in Albuquerque. And the interim months while this arbitration is happening are the only moment in Microsoft's history where like cash gets tight. They're sort of running out of money because they can't really make any sales here. Right. They don't control their destiny. People aren't paying MITS for the basic. They're quote unquote pirating the software.

They can't do deals with all the other computer companies that want to come licensed directly. And so things get a little tight. Microsoft ends up winning the arbitration, I believe in maybe like November 1977, meaning they are now totally free to go license basic to anybody who wants to buy it on any terms that they want. So they turn around, they immediately license it to the Trinity, you know, Apple, Commodore, RadioShack, and Tandy. They license it to all the big companies, the GEs, the NCRs who want to experiment with microcomputers. There's a really funny story with Apple that apparently Woz had more or less written like 95% of their own basic, but it didn't have floating point numbers. It only had integer

numbers. And Jobs is like totally riding Woz and he's like, the basic, it's really important. Like, can you just finish it? Can you do floating point? And Woz just doesn't do it. So Jobs has to go license Microsoft's basic. Amazing. And that's the first deal that happens between the companies. I mean, there's so many deals done both directions, commercial deals, equity deals, legal disputes in both directions. And this is the very first time that they do something together. Yep. So Bill and Paul and Microsoft, they do all these deals and they do them all as cash up

front, fixed cost, all you companies, you're going to pay us and then you include the basic in the machines that you're selling and we're going to get all the money upfront. Super presciently though, Bill does not value maximize on these deals. So like the Apple deal is $31,000 for eight years of access for Apple, for the Apple II to Microsoft's BASIC. They're not price gouging here because Bill sees, he's like, the play here is we want to make it a no-brainer for everybody, everybody who's selling a microcomputer to have Microsoft's BASIC on it because we want to set the standard. If we are the standard programming environment that anybody who's using these computers,

and again, anybody who is using these computers is programming them, they're used to the Microsoft version of BASIC, we're going to have so much power that it'll become a self-fulfilling prophecy. All of our competitors will just wither away. Nobody will want them because it's not going to be compatible

with the language everybody knows. And then once people start trading and then ultimately developing and selling software that they've written, it's only going to run on our basic interpreter, not anybody else's. Fascinating. I actually didn't know that started this early. And one correction there, you don't know for a fact it's only going to run on Microsoft's basic interpreter, but you do know for a fact that it will run on Microsoft's basic interpreter. And

so if it's cheap enough, why would you take the chance on a clone that might have one or two things wrong with it? Yes. Basically, his vision is, I want to remove any oxygen from any argument anyone could have about not using Microsoft's basic on a microcomputer. He thinks about this concept as a positive spiral that he really, in his mind, is the reason for Microsoft's success. He says, success reinforces success. In a growing market, one way of doing something gets a slight advantage over its competitors. This is most likely to happen with high technology products that can be made in great volume for very little increase in cost. And if you get that slight advantage, it'll compound. And this is what he's playing for here. And it's interesting. In the

earliest days, what was stopping someone else from writing a basic interpreter and licensing it to Apple or RadioShack? Nothing. There were other smart people out there. And so it was just a very good business decision to say, we got to close that door. We just got to make this a no-brainer for people to buy from us because if we're value maximizing and it's starting to feel expensive, they're going to turn elsewhere until we get a lead. Right. The Apple story is the perfect example. You know, the Woz thing is cute and it makes for a good story and like, oh, he didn't finish the basic. But when Microsoft sold them the basic, which was already getting established as the standard for $31,000.

Sure. Why not? No brainer. Apple could have gone out and hired another programmer to finish the basic. But they're like, wait, we could do that. Or I could just get the standard one for $31,000. I'm gonna do that. Just because it's important to establish there's trade-offs for everything. If you're running a startup right now, you might think to yourself, oh, great, I'll just run that exact strategy. The important thing here is, A, most of the work was already done for the original basic. B, Bill was doing it himself, Bill and Paul. So the importance of technical co-founders and their overhead was crazy low. And so they could do these deals where

they don't make very much money because they were, I think at the end of 77, they were five employees. So their overhead was just so unbelievably low that they could take a really long lens. So yeah, even though it takes until the very end of 1977 when the MITS dispute gets resolved and Microsoft can actually, you know, make money again. They end 1977 with $381,000 in revenue, despite zero for the first 11 months of the year. They're just rolling in cash. This is when Bill famously goes out and buys a green Porsche 911 and is motoring around Albuquerque getting all sorts of speeding tickets, you know, hilarious stuff. This is when he got his mugshot, right?

Yeah, I think that's right. This is the classic Bill Gates holding up the, yeah. Yes, amazing. Because he got, I think, three speeding tickets in one day, two of which were from the same police officer. Yeah, and there's funny stories of the Albuquerque police thought this, you know, how is a kid driving a Porsche 911? He must be like a drug dealer or something. Because even when he was, what, 20, 21, he looked 17.

Right. It's like, do you even have a driver's license? Wild. But back to what you're saying, this is a really, really important point. To make this dynamic work, you need to be able to afford the investment in the fixed cost for the software, for the technology to make it that little bit superior, like Bill's talking about, the slight advantage over the competitors. And at this moment in time, the industry is completely brand new. The software industry is brand new. So the amount that that fixed cost takes, the cost is quite low. Really, it's just Bill and Paul's time and dedication to this industry

that nobody else is making that investment. You can't run this playbook today because in any market, even a brand new market, even a speculative market, the minimum viable fixed cost is billions of dollars. Right. Yeah, that's interesting. I also think this moment galvanized something important, which is Bill and Paul could sort of look around and see there is going to be so much value created by microcomputers and by software. They really found religion around software as magic. The things that people can create now that we've done this basic interpreter, and these machines are cheap and plentiful, the magic will take care of itself as long as we ensure this industry can just exist and do its thing. And so they flipped from this mode of,

we need to bite and scratch and claw and make sure that we win in deals to, huh, how can we enable software as a thing to thrive? And I'm sure we can position ourselves well to capture some or a lot of that. And I think they became almost stewards of the software industry and evangelists from this point forward. Yes. They also do another really prescient thing the next year in 1978, which is they go global. Yes. Nobody else was going global yet. The way that this happens is so fun. Bill gets a call one day.

Also, how crazy is it? You've got five people. You're operating out of Albuquerque. You just finally expanded from having one customer. And you're like, you know what we should do this year? Let's open in Japan and become an international company. Yes. Now, the way this happens is one day Bill gets a call from a guy named Kazuhiro Nishi or K. Nishi, who's a computer enthusiast in Japan, has gotten a hold of Microsoft Basic, totally shares the same vision as Bill and Paul. He

doesn't have a Paul, nor is he technical himself. He's like, I'm going to bring you guys to Japan. I'm going to bring you to all the big computer companies. They agree that Kay will become Microsoft's exclusive distribution partner in Japan. And by the next year, in 1979, half of Microsoft's revenue is coming from Japan, which is wild. It's unbelievable. And it stayed at that very high run rate of international being a huge chunk, close to half always, basically forever. This is a huge cornerstone of Microsoft's success that they were an international company from year three of their existence. Yes, totally. So revenue in 1977, you know, that like last month of revenue was almost $400,000.

1978 revenue is $1.3 million. And they have 13 employees at this point. 1979 revenue is $2.4 million. And at the end of that year, they're like, all right, we got to get out of Albuquerque. And they've got 25 employees, I believe, at that point. Yeah, something like that. And this is when they moved to Seattle. And it's interesting to hear Bill talk about this. He actually really liked Albuquerque.

And specifically, there weren't any distractions there. No distractions. Weather was great. Yeah. Everybody was happy there. But the big problem was great. Yeah. Everybody was happy there, but the big problem was recruiting. Yeah. He was like, you know, if we're going to build this into the opportunity that I see,

the vision that I see and that Paul shares with me, there's no way we're going to do that in Albuquerque. We got to move to a hub. Right. And so he's got three reasons for why Seattle in particular. And by the way, it worked. Every single person except for his secretary did make the move. So one, he grew up in Seattle. He's like, I just want to go home. And then he justifies it in two other ways, which I found pretty fascinating. This is from an interview in the early 90s that he did. He said it basically came down to Seattle or Silicon Valley. And in Silicon Valley, it's hard to keep secrets because there's a rumor mill. And in Seattle, we can be a little bit more removed and we can announce things when we want to announce

them. And two, in Silicon Valley, people switch around companies. I don't want that. I want people to just work at Microsoft. There was a disadvantage to not being able to recruit from your competitors, but for a while, they were really the only game in town in Seattle. Right. But not really, though, because pretty quickly, I mean, Microsoft is such an important part of the industry. They recruit from Silicon Valley, too. We're going to talk about some of the people who come up. But you're totally right. People stay at Microsoft. They don't leave. This continues right through to this day. And the other thing that I think is really important to say that makes it work for Seattle in a way that I don't know that this could have worked in too many other places in the country

is the University of Washington. Yes. The computer science department there was really good. There were great people. You know, Steve Russell had come out there. There was real talent. And they were churning out graduates out of the UW that would go on to populate Microsoft for decades to come. Oh, and then Bill, of course, reinvested in that flywheel, donating tons of money to the

university. I mean, there's buildings, there's whole new schools. Yes, absolutely. They played right into it. And so today, I mean, it's always a top 10, if not top 5 computer science program in the country. But unlike other top computer science programs, it's a state school. So it just has huge volumes. I think more students come out of the University of Washington and go to big tech than any other program in the country. That has stayed this amazing advantage. Yeah, I think the only thing even close to it is Berkeley in the Bay Area with a lot of the same dynamics. But there's Stanford there too.

So it's kind of like a dual university system in the Bay Area. But yeah, you cannot overstate how important the University of Washington was to this decision and then the ultimate success of coming to Seattle. Yep. in the beginning of the year when they move to Seattle, just in time for, I think you can make a very strong argument, the single most important deal ever done in the history of technology. Absolutely. The Microsoft-IBM. I mean, it's crazy to even say it now, the Microsoft-IBM PC partnership. It's crazy. You have this absolute behemoth partnering with someone that's not really relevant.

And if you're standing here today, it sounds like I'm talking about Microsoft partnering with IBM. But at the time, it was IBM partnering with Microsoft. It was the only computer company that mattered in the entire world, got themselves into a particular situation where they came to Microsoft looking for help. It's the craziest set of events that made this possible, and I can't wait to dive into it. All right, listeners, our next sponsor is a new friend of the show, Huntress.

Huntress is one of the fastest growing and most loved cybersecurity companies today. It's purpose built for small to midsize businesses and provides enterprise grade security with the technology, services and expertise needed to protect you. They offer a revolutionary approach to manage cybersecurity that isn't only about tech. It's about real people providing real defense around the clock. So how does it work? Well, you probably already know this, but it has become pretty trivial for an entry-level hacker to buy access and data about compromised businesses. This means cybercriminal activity towards small and medium businesses is at an all-time high. So Huntress created a full managed security platform

for their customers to guard from these threats. This includes endpoint detection and response, identity threat detection response, security awareness training, and a revolutionary security information and event management product that actually just got launched. Essentially, it is the full suite of great software that you need to secure your business, plus 24-7 monitoring by an elite team of human threat hunters in a security operations center to stop attacks that really software-only solutions could sometimes miss. Huntress is democratizing security, particularly cybersecurity, by taking security techniques that were historically only available to large enterprises

and bringing them to businesses with as few as 10, 100, or 1,000 employees at price points that make sense for them. In fact, it's pretty wild. There are over 125,000 businesses now using Huntress, and they rave about it from the hilltops. They were voted by customers in the G2 rankings as the industry leader in endpoint detection and response for the eighth consecutive season and the industry leader in managed detection and response again this summer. Yep. So if you want cutting edge cybersecurity solutions backed by a 24-7 team of experts who monitor, investigate and respond to threats with unmatched precision, head on over to huntress.com slash acquired or click the link in the show notes. Our huge thanks to Huntress. So the IBM PC. Why is IBM getting into the personal computer here in 1980? A fun quote we heard in our research was that IBM was the sun, the moon, the stars of the computing industry. And that meant the hardcore enterprise mainframe computing

industry. Yes. David, are you going to attribute that quote or are you going to leave listeners just hanging? All right. I think it's time. We talked to probably 10 early Microsoft people in research and preparation. And one of those folks was Steve Bommer himself, and he used those words in describing IBM. Yes. And it's hard to imagine a better person to get their perspective on what IBM meant to the world at this point in time, because 1980 was also the year that Steve joined Microsoft. So literally at the same time in 1980, you've got the management team coming together with Steve and Bill and Paul Allen, and you've got the IBM thing going on, and you've got them moving to Seattle. And we haven't even talked

about Charles Simone yet, but this was the year he joined. This is the year. Yes. I mean, every year for Microsoft until this point is the year, but like 1980 is big. Okay. So why is IBM the sun, the moon, and the stars of computing? Why are they getting into this PC? It's way cheaper than anything else they sell. It seems to be like a totally different business strategy, a different customer set. What's going on? So all the early microcomputers we were just talking about, you know, the Altair, the Apple II, the TRS-80, these are all 8-bit machines. They're running the Intel 8080 processor or competitor making a similar 8-bit processor. The problem with an 8-bit processor is that the maximum data size for a given instruction cycle in the processor, this is called a data word

in computer science terminology, is 256, you know, two to the eighth. You can't represent any number greater than 256 in any given CPU clock cycle in an eight bit machine. Right. It's effectively a bandwidth limitation where if you're in a single clock cycle trying to do some particular instruction, it's a very, very small amount of data that you can move through the arithmetic logic unit or that you can move through the processor in that clock cycle. Totally. You could think of it like an hourglass or something. There's like all the data sitting there in memory at the top of the hourglass. And then there's this small little, you know, funnel that it goes through. That's the processor. And then it comes out.

That's a good analogy. It's going to take forever. Yeah. Into the application of the software that the user sees. You're just not really going to process it that fast. Very primitive machines. Yes. And so for a company like IBM, they eclipsed the 8-bit computing cycle a long, long, long time ago. Mainframes and even many computers with DEC, you know, all these machines are at least 16-bit, if not 32-bit computing machines. So 8-bit just, it's not interesting. Which is why they only cost $375 or whatever for an Altair.

Right. In late 1979, Intel announces that they're coming out with the 8086 processor, which is a 16-bit microprocessor, which is a 16-bit microprocessor. With 16 bits, you can really start to do some damage here in terms of the applications that you could put on this thing to eat into business software use cases. In 16 bits, you can represent numbers up to 65,536. So that's two to the 16th. You can do interesting things passing 16 bits around at once. There's some really, really fun aspects to this. If you look at pictures of these processors, what did the 8080, the 8-bit processor look like? And then you look at what did the 8086,

the 16-bit processor look like? You can see this in the 8008 processor that's only eight bits. You see only nine pins coming off of the little chip. You know, there's the eight pins for the data bits, and then I think there's one more control pin. If you look at the 8086 processor, it's a much longer rectangle with 16, 17, you know, maybe like 20 pins coming off of it. Like you see this physically represented in the chip. The further we get in the computing world, the more abstract stuff becomes. So it's always fun to go back in history when these concepts were so grounded in our physical reality that's sort of easily observable since everything was so much bigger too. Yeah. Back to 1980. The 8086 has been announced. 16-bit microprocessor

is coming. IBM has already lived through missing a computing expansion era once with DEC and the minicomputer. They just let DEC take that market. Of course, that didn't really hurt IBM, but man, it would have been nice to also have that market too. And the, that didn't really hurt IBM, but man, it would have been nice to also have that market too. And the thing that they're observing about the microcomputer market is it's exploding. People in our industry know about DEC. People in the broader world never knew about DEC. But I think it's a very different rate of adoption and rate of demand with microcomputers where IBM started to kind of look at and go, oh, this might be like a real market, like a really big computer market for people. They're finally observing the same thing that Bill and Paul did, you know, all the way back

in the Trafo data days of this is an exponential cycle. Like Moore's law, this is exponential and exponential gets real big very quickly once you get a few years in. of this is an exponential cycle. Like Moore's law, this is exponential. And exponential gets real big very quickly once you get a few years in. And the mini computer cycle never was that. So it's hard to remember today, but just to underscore this again, in 1980, IBM was the most valuable company in the entire world.

The highest market cap company, bigger than all the oil companies, in 1980. The sun, the moon, and the stars. Yes. Do you know what their market capital was? In 1980? $150 billion? You are almost an order of magnitude off. $34 billion. That was the most valuable company. It is wild what a different world we live in today. Yeah, even inflation adjusted. It's interesting that the rate of growth of the most valuable companies in the world in terms of market cap has far outpaced inflation. So that company, the most valuable in the world, they're going to tiny little Microsoft that's

just moved to Seattle for this partnership. What's going on here? So what IBM decided, this is just so amazing. They deserve so much credit here. They got the Clay Christensen, disrupt yourself, disruptive technology thing intuitively decades before Clay writes any of this stuff. The way that they decide to compete is they're like, all the things that Clay wrote about are working against us here. What we need to do is we need to create essentially a skunk works division, just like our Lockheed episode. We need to do something outside the company, completely removed from the politics, sure,

but like the business incentives not to disrupt ourselves, and create a new division they call the entry the Entry-Level Systems Division. Actually, it may have existed before, but they repurpose it. This is in Boca Raton. In Boca Raton, Florida. Very nice place. We were just there a couple of months ago, but not a technology hotbed in the world.

And they create a secret project called Project Chess. Secret from the rest of the company, the whole world. And the goal is to develop the IBM microcomputer or the personal computer as people are starting to refer to microcomputers. Yeah. And this is wild. They're going to do it in secret with a small team with no other IBM resources. And so that means this small team, the only way they can do it is to use all off-the-shelf components from technology providers basically play on the same level playing field as all the

other microcomputer manufacturers out there and oh yeah one more thing ibm leadership tells this team in boca they have to ship the PC to customers within one year. It's a crazy constraint. It is a total crazy constraint. A couple quotes on this. Don Estridge, who was one of the leaders of Project Chess, he would later say that the company realized that if you're going to compete against people who started in a garage, obviously a reference to Apple here, you have to start in a garage yourself. And then Lou Gerstner, who later would take over IBM, would describe this whole Boca project as,

quote, the way you get an elephant to tap dance. And the question is, are they playing from behind and thus have to adopt a flawed strategy? Or is this strategy of assembling with all off-the-shelf components actually a good strategy? Or is this strategy of assembling with all off-the-shelf components actually a good strategy if it works? Well, let's tell the story and then come back to it. Great. Okay. So what do they do? The hardware aspect of this is trivial, basically. Hell, Ed Roberts could put together the hardware to sell a microcomputer and do this deal with Intel. I think IBM can do a deal with Intel. Not necessarily trickier, but the more important part is the software. And thanks to Bill's genius strategy about be the volume player, don't optimize on per unit price, set the standards out there. They were like the world's leading provider of programming language interpreters, right? A hundred percent. There is one game in town and one game in town only,

and that is Microsoft in Bellevue, Washington at this point in time. Now, interpreters are notably different than operating systems, but Microsoft definitely had sort of raised the flag and everyone could see if I want to go buy software for my computers, broadly, they're an interesting group to talk to. Oh, yeah. Obviously, operating systems are going to become really, really big here in just a sec. But again, the 8-bit generation operating systems weren't that important because people were writing their own software. The standardized software, packaged application software doesn't happen until the 16-bit era and doesn't really, really happen until the 16-bit

era and the IBM PC. So that's why the basic, the interpreter, is so important. So what happens? IBM calls up Bill Gates, and by August 1980, the two companies are in serious talks to partner and work together on the IBM PC. And we referenced Steve Ballmer a minute ago. The timing is just crazy. Steve had just joined the company in June of 1980. He's employee number 30. The Microsoft team of 30, which the whole company of Microsoft pivots to work on the IBM PC partnership, is bigger than the Project Chess team in Boca. It's amazing.

Wow. So, okay, Bill has just convinced Steve to drop out of business school at Stanford and come help him and Paul run the company. So Microsoft at this point in time is still a partnership. Steve is the first person besides Bill Paul, to get equity in the company when he joins. And it's 8.5%, and it's a handshake deal at this point. Yes. Bill really, really wanted to bring Steve on. Knew him from the Harvard days. Knew what an asset he could be. He is the yin to Bill's yang.

Yes. And so, I mean, frankly, 8.5%, it's a big grant. You know, who's out there running a 30-person company and you're giving away 8.5% slugs? That just doesn't happen. Those are founder shares. And this is really a sort of reflection that the way that Bill thought about Steve was as a founder. In fact, it created some tension with Paul Allen, where Bill asked Paul if they could go to 5%. Paul said, sure. And then Bill actually offered him 8.5%. And Paul got upset. And Bill said, I'll eat the 3.5%. It can come out of my share because I want him that bad. But he's the perfect person for this point in time.

Bill was like the only salesperson doing these OEM deals. Now they're dealing with IBM. They're entering the enterprise world. This needs to be a real business. Yes. So back to the IBM negotiations. Obviously, Microsoft is very interested. IBM is not just very interested in working with Microsoft. They have to work with Microsoft. They're the only game in town. Yes. And specifically, they ask Microsoft for programming languages. They're like, we're making this great PC. We're going to need a basic. We think you guys are working on a COBOL. We'd like some COBOL. Yep. Fortran, like give us the whole thing. And there's some debate on whether it was the Microsoft side or the IBM side that really saw the vision of, hey,

the 16-bit generation is going to enable real business software use cases on the personal computer. But it doesn't matter. That's the plan here. And that is absolutely what happens. So these initial discussions, right, are for the programming language. Microsoft doesn't matter. That's the plan here, and that is absolutely what happens. So these initial discussions are for the programming language. Microsoft doesn't make an operating system at this point, because in the 8-bit generation, the operating system, I think, was kind of like a glorified bootloader to just get into the programming environment so that you could either write or load up the basic programs that Microsoft was going to interpret

and then run. And in the 8-bit generation, most if not all hardware providers of microcomputers just wrote their own operating systems. It just wasn't a big deal. Now, there was one off-the-shelf operating system out there from a company called Digital Research, which was run by Gary Kildall, who I think as we talked about earlier, Bill and Paul had actually intersected with back in Seattle. Yep. I think they were reasonably friendly. Yeah, I think they were quite friendly because they partnered. You know, you needed the operating system to get into the programming environment. It wasn't that big a

deal. And so, yeah, whenever anybody needed one off the shelf, Bill and Microsoft would just refer people over to digital to get it. Yep. CPM, right? Exactly. CPM, CP slash M, which I think is maybe control program for microprocessors, I think is the abbreviation there. God, they were so bad. Every single thing that's been named to this point, except for the company Microsoft, was a horrible name. Oh, the processor is 8008, and now it's 8080, but the machine is 8800 that the processor is inside. Give me a break, everyone. It's horrible naming.

Bill, and I'm sure Paul too, but Bill is the only person in this industry that has the vision for what this can become. Even Intel, and you know, Bill talks about this. He doesn't think that Intel even realizes what's happening here. They're just like, oh, we're just making more chips, you know, and like people use them for stuff. Yeah, it does seem like very few people are thinking about their products as something they really need to build a brand around with consumers. Yes. Hence the naming schemes. Okay. So the IBM Microsoft discussions are going along and IBM's like, oh, hey, yeah, we need an operating system. So Bill, I think from everything we've read and folks we've talked to, kind of in good faith, just does the standard thing he's always done

in these situations. He's like, oh yeah, go talk to Gary, go talk to digital research. He can probably do that. Right. We don't have an operating system, so this guy does. So what happens next is unclear. But what is clear is, however it goes down, this is one of, if not the biggest business blunder in history. IBM, that team from Project Chess, flies down, I think, directly from Seattle and talking with Bill and Steve to Monterey, California, where Digital Research is based at this point, to meet with Gary and his wife, Dorothy, who run the business together. And Bill's called them. He's like, hey, got a big OEM client coming down, needs an operating system. And he signed hefty, hefty NDAs. So he cannot say who it is, but he's like, hey, got a big OEM client coming down, needs an operating system.

And he signed hefty, hefty NDAs. So he cannot say who it is, but he's like, you really should take this seriously. Right. So the team comes down. Obviously, they show up there from IBM. There's a big snafu where Gary does not attend the meeting. And there's conflicting reports about what happened. Wasn't one of them that he's out flying an airplane? Yeah. So I'm pretty sure he was flying his personal airplane while this happens. Some reports are he was just out joyriding and missed it. Some reports are, no, he was like on a business trip and knew it was happening, but he had another important business meeting and he

didn't know that this was IBM that was coming. Regardless, it doesn't really matter because IBM just wants the operating system. Dorothy does meet with them. She's unwilling to sign their NDA. There's a lawyer from digital research who gets involved and he doesn't really understand what's going on. The punchline is that IBM sort of leaves this interaction with the belief that Gary and Digital Research aren't up for working with them and aren't capable of producing here. And producing is important because it's not like the existing CPM OS that they made would work here. They would have to write a new version, a 16-bit version. And they hadn't done that yet. And in particular, they would have to do some customizing. But part of what IBM wants is a customized version of an operating system for the IBM PC. They don't want this to be fully off the shelf. And just to add one more stir the pot of history here, there is another version of this story

where Gary does actually have a conversation with IBM and it blows up over licensing terms that what Gary really wants is a significant royalty of every IBM PC sold and IBM walks over that. So whether that happened or whether it's just an NDA issue, either way, I think we all know the IBM PC did not end up running the CPM operating system. Oh, that's amazing. I didn't know that. We'll talk about that when we get to the business terms of the Microsoft-IBM deal in a minute. Yes. But for the moment, there's no deal yet because an operating system needs to be provided here. So IBM goes back to Microsoft and they're like,

hey, this guy you referred us to ain't going to work. The way that I read some quotes from the IBM people here were like, we just threw the problem back in Microsoft's lap of you guys deal with this. You source an operating system. Yep. Well, I'd like to say that Bill and Steve and Microsoft, you don't need to give them an opportunity twice. In this case, you kind of did need to give them an opportunity twice because they almost flubbed it and sent IBM down to see Gary. This time they don't flub it. They're like, okay, we'll get you an operating system. And so enter Seattle Computer Products.

Yes. So it just so happens that right down the road from Microsoft in the Seattle area, I think they, despite being named Seattle Computer Products, I think this company was actually based in Tukwila, Washington, a programmer named Tim Patterson had just written a 16-bit operating system for the 8086 that Intel had just announced, and he was calling it the Quick and Dirty 16-Bit Operating System, or QDOS for short, and had it ready to go. Now, why had he written this? What was this company, Seattle Computer Products? Why did they have an operating system? They were a component provider to microcomputer manufacturers. They essentially made motherboards. And so when Intel now has announced this new 16-bit processor generation that they're coming out with, well, Seattle Computer Products, they want to sell motherboards and have them ready for 16-bit. They kind of need to test and play around with these things, and their customers are asking for it. So they had

been going to Kildall and Digital Research too and badgering them to like, hey, write the 16-bit version of CPM. And Gary just didn't. So Tim's like, fine, I'll do a quick and dirty version myself. And thus DOS is born. Incredible.

Which of course later they would drop the Q and call it DOS, the disk operating system. Something about dirty didn't have a ring to it when you're selling it to IBM. No, no, no, no, no, no. So Bill and Paul and Microsoft, they've learned about this. They know Seattle Computer Products. They know Rod Brock, who's the guy who owns the company. They get in touch with him and they say, hey, can we license QDOS from you and Tim?

We've got a big OEM customer that wants a 16-bit operating system. So they work out a deal whereby Microsoft pays Seattle Computer Products $25,000 for the rights to adapt and sell QDOS to the one unnamed original equipment manufacturer who they're working with. Tim actually, he's jazzed about this. He ends up leaving SCP Computer Products and joining Microsoft. And so he, with the rest of the team, he's part of building DOS, taking his initial work and turning it into real DOS. Later on, before this all gets announced and the PC ships, Microsoft would pay Seattle Computer Products another $50,000 for full rights to own 86QDOS, sell and license it to anybody else indefinitely.

So I believe the total amount of dollars that changed hands here is $75,000. Unbelievable. This is DOS. Now, look, one programmer wrote a, quote, quick and dirty operating system, and Microsoft bought the license to that and adapted it into DOS. Tim, when he was at Seattle Computer Products, definitely did not write DOS as DOS becomes. It's not like Microsoft bought all of DOS for $75,000.

They did a lot of work on it. But yeah, this is how it all goes down. So Microsoft would eventually generate billions of dollars on DOS-based products. Now, you're exactly right in the same way that Instagram today is a much different code base than Instagram and much larger code base than Instagram when it was purchased. But my God, $75,000 to buy DOS to get this whole thing started. I mean, until Windows 95, all of the Windows operating systems were DOS-based. It's just crazy. I mean, it really illustrates how fast things were moving, how much all this was getting invented and discovered real time that even to this point, Bill Gates isn't thinking that operating systems are that important. This is just a shortcut to get the deal done with

IBM to make it happen. Yep. Also, David, I got to say, I just looked it up. The address of Seattle Computer Products on the original business card for Seattle Computer Products, where I presume QDOS was written, the space is available. So I know where our next studio needs to be. And it's in Tukwila? And it's in Tukwila. All right. Well, the rent can't be like that expensive then. So like, let's do it. Correct. Correct. Hell yeah. Well, you know, we've been joking for years about making the acquired museum. We might have a location. Okay. So now they've got the operating system, they've got QDOS in place to license to IBM. The only thing that is left to formalize the partnership is the business terms. And Ben, if what you said is right about the Gary Kildall IBM negotiations, this is just a masterstroke from Bill here in the licensing with IBM. Yes. Because there's two really, really big levers that it looks like Bill is giving big time on

one of them, but he is winning big time on the other one. What are they? So the one that it looks like he's giving on is he does another fixed cost OEM deal with IBM. Yes. So this is in Paul Allen's memoir, IBM paid Microsoft $75,000 for testing and consultation, $45,000 for DOS, and $310,000 for an array of 16-bit language interpreters and compilers. So all told, bundled together, that is $430,000 fixed that IBM paid Microsoft with no ongoing obligation. Yes. No per copy royalties. Yes. Every copy of DOS that IBM sells, either included as part of systems that they're selling, or they're free to charge independently for DOS, whatever amount they want, Microsoft gets zero dollars. And if it's true that this is where things fell apart with Gary Kildall,

crazy that Bill is willing to do this. And you might say, what? Didn't Bill learn his lesson? Why would he ever agree to this? On the one hand, this is what he was doing with Apple and others. He was doing these fixed cost deals. You would think like, man, IBM, like this is the time. People aren't going to pirate IBM software.

Now's the time to really grab the money bags. But Bill saw something that no one else did. In exchange, I don't know if it was directly in exchange in the negotiations, but the other lever that he saw that he pulled was Microsoft retained the rights to own DOS and to own their languages and license it and them to anyone else they wanted at any price on any terms. It's so interesting because what ended up happening that Bill Gates masterminded was once we distribute our operating system through IBM's PC, that's going to become the thing everyone buys. And now in the 16-bit generation, when there are people building programs for computers, not just developers, once those application developers who are writing programs are targeting an operating system, then that is the operating system that every other OEM,

every other computer maker is also going to want and really need. And we're going to be the ones that they have to come to to buy it. And I can't figure out, did IBM miss this fact or did they know it? Basically what IBM did was they were the one place where every business needed to go for their computer needs. And what they did in this negotiation was they actually handed that over to Microsoft. And they said,

we are going to become a commodity just like every other hardware manufacturer. And you are going to be the point of integration for the whole ecosystem. You're going to be the linchpin that everyone has to target for their applications. So I think there are two things going on here. One small and one big.

The small thing is actually related all the way back to the beginning of the episode, what you said, Ben, about the antitrust concerns within IBM. To hear them say it, they actually didn't want ownership of the software. They wanted it to be separate because it would sort of look better. Because then they have the sort of plausible deniability of,

how could we possibly have a monopoly? We're buying off the shelf. Part of an ecosystem, blah, blah, blah. Yeah, yeah. Yeah. From a vendor who can sell to anybody else. We have no lock-in. And that may well be true. I think the bigger thing that just wasn't in their consideration or mindset was they, I think, assumed that once they entered the PC market, IBM was going to be the dominant player. So it didn't matter. Once IBM is selling PCs, who's going to buy a PC from anybody else? IBM is going to win this market. Just like they have in every other line of business they've been in. And what Bill saw was he really made a bet that the same dynamics that played out with the Altair were also going to play out with the IBM PC. That there would be a million hardware

manufacturers flowers blooming here. Building to the same spec. And building to the same spec. Using the same processor. Which of course they could because it was all off the shelf components. And IBM either didn't see or didn't believe that that would actually happen. IBM failed to see the value of software. And they certainly failed to understand what a software platform business model would be. Which makes sense. I mean, why would they? Right. It's almost like their experience- They are the computing company. Yes. Their experience in selling mainframes with everything

bundled in was the wrong experience to go off of in understanding the way the future would unfold. And Bill's very modest experience watching the Altair and all these sort of Altair clone type machines, or even if they're not Altair clones, just more microcomputers that need more software, that actually was the useful experience to pattern match off of what does the world of microcomputers look like and how is that fundamentally different than the world of mainframes. Totally. And in a way that, you know,

the minicomputer generation, like we've been saying, it was like a half generation. It wasn't. It wasn't actually fundamentally that different other than DEC gained a foothold. Yeah, the deal that Bill Gates made with IBM for the IBM PC is the greatest deal in at least computer industry history, if not all business

history, full stop. Right. So let's say a little bit about why. I mean, maybe it's obvious, but here now is IBM, most valuable company in the world. They're going to come out with the PC platform. They are going to build the market and Microsoft is going to own the linchpin sort of Hamilton-Hellmer terms, like where the power is in the market. And they're going to be free to license it at whatever terms they want to any other player who wants to enter. So they signed this agreement in November 1980. The IBM PC ships in August 1981. Just incredible.

Almost exactly a year, a little more than a year from the time Project Chess starts to when they actually shipped the PC. I mean, truly incredible they pulled it off. Truly incredible. It changes the world. Like, you know, that's such a trite thing to say, but like everything that everybody's imagining happens. IBM was right that it was by far and away the most successful personal computer on the market as soon as they released it. Totally. They sell 13,500 IBM PCs within the first couple months after they announce

it. Over the next two years, they sell half a million of them, makes them unquestionably the largest personal computer, microcomputer manufacturer, market leader. Everybody at IBM is celebrating. The clones haven't arrived yet, and maybe they won't. It'll play out like they think. Not exactly. Now, before we talk about the clones, this is really just a footnote because, of course, all the incentives are aligned for IBM to push DOS as the operating system for the PC. I mean, they've done this whole deal with Microsoft. They have a royalty-free deal with them. When they launch the PC, customers actually have a choice

of which operating system they want on their IBM PC. They don't have to go with DOS. Consumers can choose between DOS, 16-bit CPM. By this point in time, Gary and Digital Research have gotten their act together. They've written a 16-bit version of the CPM operating system or another 16-bit operating system called Pascal that came out of the University of California at San Diego. And the price sheet for the operating system option is Pascal is an extra $450 with your IBM PC. CPM is an extra $175 with your IBM PC. And DOS, which was developed specifically for the PC is the best way to run it, is only $60. So IBM is making $60 of full 100% margin on top of their hardware for the PC by selling DOS because they don't have to pay Microsoft any of that. And they've set up the incentives that like obviously everybody's going to choose DOS.

It's fascinating. And you know what? To give them a little bit more credit too, they did try to enforce that there's some amount of lock-in to the IBM PC. And they did that in two ways. One is we're simplifying and calling it DOS. It was PC DOS,

which is different than MS DOS, which would get licensed to other computer makers. I don't know exactly what happened, but it basically seems like it just wasn't different enough to be meaningful to application developers. So that's one piece of it. The second is IBM did actually have proprietary BIOS. So that was another part where they kind of thought that that might provide them some protection where they could stay a linchpin in the ecosystem. And it wasn't just all off the shelf. They actually did have something that was theirs that was proprietary. It just turned out that the effort required to reverse engineer the IBM BIOS was trivial,

basically. Oh, do you know the story of the Compaq BIOS? Ooh, well, I know the Compaq story, but I don't know the story of the BIOS specifically in lightness. It is basically why Compaq worked is what it comes down to. So Compaq was formed basically to clone the IBM PC. They saw the market opportunity and they realized they could buy from all the same equipment vendors. So let's go eat their margin is basically the plan. However, the one thing that was not off the shelf is the BIOS, the basic input-output system, which is effectively the thing that decides to load the operating system when you turn the machine on. And so there's some proprietary magic that happens to call upon the operating system to do its thing. So Compaq reverse engineered the BIOS, and the way that they did it was very similar to

Trip Hawkins and the story that he told us about his reverse engineering at Electronic Arts. Of the sake of Genesis. Yes. So Compaq had two engineers, and one engineer went in and fully dissected the code for the IBM PC BIOS and basically saw all the proprietary calls that it made and documented each of those calls without writing the implementation steps. Then he handed, hey, here's what the BIOS needs to interface with over to the other engineer. And the other engineer on their own just went through and thought of an implementation and they have no idea if it's the same implementation. So it's not breaking any sort of infringement. They're basically saying, I'm just seeing the requirements for this product, and I'm coming up with my own implementation of that product. They basically figured out how to exactly clone the IBM PC and buy the very same operating

system. And to go back to quoting Ben Thompson, because this is from his great piece again, the result was a company that came to dominate the market. Compaq was the fastest startup to ever hit $100 million in revenue, then the youngest firm to break into the Fortune 500, then the fastest company to hit a billion in revenue. And by 1994, Compaq was the largest PC maker in the world. The Compaq story is amazing.

So the three people who start Compaq in 1982 are actually Texas Instruments engineers who left and they wanted to start a company. And I believe as the legend goes, they were like trying to decide what to start. They were considering like a restaurant chain and like a bunch of different business ideas. And then the IBM PC comes out at the end of 1981. And they're like, oh, we can clone this and do everything, the story you just told. So yeah, it's wild. They start the company in 1982. And within the first year, they do $111 million of revenue of selling IBM PC clone hardware. Is it just cheaper? Basically,

this is the IBM PC, but for less money? Yes, exactly. Same thing, cheaper. And so begins the race to the bottom of PC hardware. Completely undifferentiated. All the value accrues to the software layer. Totally. Compaq went public the very next year in 1983,

well before Microsoft, which is funny. But yeah, Compaq, all these other clone companies that get started, Microsoft licenses DOS to all of them, importantly, critically, on a per machine sold basis. This is when they grab the money. The operating system is so deeply embedded and needs to get shipped with the computer itself. Yeah, consumers can go buy operating systems to upgrade and whatnot, but no hardware manufacturer is going to ship a 16-bit PC without an operating system. So piracy is not an issue here. Microsoft can now do a per-copy-sold, per-machine-sold

license with all these clones. My God, it's just like a geyser of money. Microsoft used IBM to generate demand for their software, and then they used every other PC manufacturer to capture the value that all that demand created. Yeah. So I think I have these numbers and timeframes right. I believe that for calendar year 1982, Microsoft's revenue was $25 million. And I think this must have been when they switched to fiscal year end and June 30th. So Microsoft's fiscal year end starting then and up through now is June 30th. So their fiscal 1984, so the year ended June 30th, 1984. So 1983 midpoint to 1984 midpoint. Microsoft does $98 million. In an 18-month period from the end of 1982, they go from 25 to 98. It's all on the back of the clones.

And unlike Compaq that, yeah, they did $111 million of revenue their first year, they're selling hardware, which has serious cogs associated with it. Microsoft, 100% essentially gross margin, software revenue, more than doubling year on year. I mean, it's the best business of all time. Yes. And they combined two magical principles together, this infinite replicatability, zero marginal costs of software, and becoming the linchpin of the ecosystem. They are now the software that everyone needs to target, which gives them pricing power. Totally. So that pricing power raises your top line and you have no costs. It's unbelievable.

So meanwhile, in the computing industry background, while all this is going on with the launch of the IBM PC and then the clones. Apple had gone public at the end of 1980 in, I think, the biggest and most successful IPO of all time at that point. Remember, we talked about Genentech on the Novo Nordisk episode. They went public right before Apple, and then Apple was bigger. So they're valued at $1.8 billion at IPO. Steve Jobs is this multi-hundred millionaire, media darling, all this stuff. The next year in 1981, Microsoft reorganizes from the partnership between Bill and Paul with the handshake deal that Steve's going to be cut in on the partnership

into a stock company, a C corporation. And as part of doing that, the venture firm Technology Venture Investors, or TVI, invests $1 million, I believe, for 5% of the company? Yep. This is crazy. That's a $20 million post-money valuation. It's a one-on-20 post when Microsoft is doing how much in revenue? That year, they did $17 million in revenue, and they're about to do the IBM deal. This is absolutely absurd. So it says a lot about this period of time that you could do a 1x revenue deal in a high-margin software company. I mean, I actually don't think this shows a weakness in

Microsoft. Oh, they didn't have leverage or something like that. That wasn't it at all. It was just the deals sucked. Yeah. Venture capital sucked back then. Yes. There's no other way to put it. Now, you know, it's only 5%. So good on Microsoft. Spoiler alert, this is the only dilution that they would ever take. So that's also extremely different than today. But yes, a $20 million valuation at this stage is frankly ludicrous. You know, even among people who should be in the know, the beauty of the software business model still is something people don't understand. That's exactly right.

The hotness is the hardware. It's like Apple just IPO'd. Apple's worth $1.8 billion. Like, that's the industry. It's IBM, etc, cetera. When Microsoft itself would go public a few years later in 1986, they actually go public the same week that they moved to the big campus in Redmond, where they are to this day. Their market cap at IPO is only $750 million, despite having done $200 million of very high margin software revenue in the trailing 12 months up to that, growing 100% year over year. It's insane. Hey, that's Forex multiple expansion off the last time they raised money. Right? But it's just crazy that people don't yet appreciate the power. So Bill Gates and Warren Buffett did a conversation at the University of Washington in 1998. So this is as late as 1998, this thing that we're talking about, the magic of the software business model and how it should be reflected in a company's valuation, especially when it's a high growth company, was still not

understood even by Bill Gates himself. So here's the quote. Bill Gates says, I think the multiples of technology stocks should be quite a bit lower than the multiples of stocks like Coke and Gillette because we are subject to complete changes in the rules. I know very well that in the next 10 years, if Microsoft is still a leader, we will have had to weather at least three crises. So Bill Gates is essentially making an argument. Now, granted, this is in the middle of all the antitrust stuff, so he's very prime for this. And the internet. And the internet. He's basically making the argument that disruptive forces come at you so fast in the technology industry that even though you can grow extremely fast and it's this extremely scalable thing, distributing software at zero distribution costs, and even though the margins are unbelievable

because you have zero marginal costs, they still shouldn't be valued as highly as like a CPG company, which is so different than the way that people think about it today. Well, it's funny. I've thought about this a lot, and I actually watched that interview years ago. It's so good. There are elements of truth to this too. And I think it's that for most technology companies, that is totally true. Yep. And then for a few technology companies that have true power and true scale, the exact opposite is true. Microsoft is still the most valuable company in the world today. Companies that are less susceptible to disruption, more predictable in terms of high growth, high margin revenue,

deserve a premium. But Gates is basically arguing everyone else doesn't. So let's flash all the way back to 1981 and talk about this venture capital investment, this one-on-20 that TVI does. Good work if you can get it, man. How does this come to be? So even a whole year before, in the fall of 1980, Dave Marquardt, one of the partners and the founders at TVI, flies up to Seattle, not to meet Bill Gates, but to meet Steve Ballmer. Because they were classmates at GSB, right? They weren't quite classmates, but because I think they were two years apart, so they didn't overlap, but they had some of the same social circles. And Steve was effectively the screener for anyone who wanted to come and talk to Bill and try and invest in the business.

TA Associates had been up, Sutter Hill had been up, Hambrick and Quist had been up, Xerox Ventures, and all of them only ever got to meet with Steve Ballmer and never got passed on to Bill Gates. Steve would basically just bounce them off. And I know all this because there's a great oral history from the Computer History Museum where this whole thing's in a transcript with an interview with Dave Marquardt kind of recalling the whole thing. So Dave flies up to meet with Steve and Steve says, you're asking really interesting questions. You're thinking about our strategy the right way. You don't just want to do a transactional deal. You really think this is something special. Why don't you meet with Bill? Bill, of course, doesn't have any extra time in his schedule. He says, but I am going to the UW Arizona football game at Husky

Stadium. Why don't you come and talk to me there? So of course they go. Bill doesn't pay attention to the game at all. He's just laying out the strategy and grilling Dave and talking about software the whole time. So this is fall of 1980. So that's a whole year before the deal gets done. And Dave's remarking at this point in 1980, they're doing 5 million in revenue, 2 to 3 million in profit. They don't need VC money. And yet he was able to get in. So here's the quote. I was just sort of helping them out with the business. In the venture business, you're buying and you're selling at the same time. You're trying to figure out, are these guys crazy? Are they ever going to do anything really

interesting? And if so, how do I get myself positioned to be able to help them do it? And so I spent a lot of time up there helping recruit people. I helped to recruit Charles Simone, who was an early key guy. Charles Simone would go on, this is an aside, to write Microsoft Word. And Charles was at Xerox PARC inventing the GUI. Oh, we can talk about Charles in just a sec. Yeah. Yes.

And he says, and I was working with Steve on business strategy. They had these OEM customers, the PC manufacturers, and they had started to engage with IBM on this operating system. And then are we just going to become a low cost contract programming shop for IBM, an outsourced sweatshop? Or is there some way we can build a business out of this, which led to the fixed fee to IBM, the retention of the code, which then we could sell to other people. And that's what created the PC industry, basically. So that is his recollection of the whole thing, that he was sort of very helpful in this transformative time for the company. Now, at the same time, you have to look at everyone else's incentives.

How can I be helpful, Ben? So Dave is only 29 years old, but everyone else is like 23. And so he actually is kind of adult How can I be helpful, Ben? function to actually turn this into a corporation so that we can get some shares granted here. So there's a little bit of incentive to say, hey, if we take on an outside investor, we're going to have to restructure. And that's what I had always read about the TVI investment. Yeah, obviously, Microsoft didn't need the money. They liked Dave. But also a big part of it was this was a catalyzing function to do the conversion into a C Corp. Yes. So this would create a little bit of board and governance. So it's not just Bill all the time. Now, Bill, of course,

I think is still the controlling shareholder just by the amount of stock that he owns. But there's a board. It's Bill and it's Dave and it's K Nishi. It's a three-person board. Yeah. We should say too, vis-a-vis Paul, tragically, and I believe it was 1982, 83,

he's diagnosed with Hodgkin's disease and he ends up taking a leave and then fully leaving the company. I think he did go on and off the board at various points in time. Yeah, that's true. But yeah, he's no longer a full-time member of the company after his diagnosis. Yep. So on this venture investment, it's pretty fascinating. None of these are terribly compelling reasons other than like, I guess it would be nice to have a little bit of capital associated with us formalizing the corporation. But they don't need money at all. They're printing cash. They've been printing cash ever since that one tight period in Albuquerque. Dave charmed them. I think that's kind of the answer. And I've always heard wonderful, wonderful things about Dave. And I think everybody really did love him and see his value. But man, to be a venture capitalist in the 1980s and 1990s, oh man, you couldn't lose. It's pretty crazy. I think part of it too had to do with the fact that Microsoft was up in Seattle.

So the VCs just weren't traveling. Right. And Dave was young and he was single. Oh, Don Valentine famously had the rule, they didn't invest in any company that you couldn't bicycle to from Sand Hill Road. It's crazy. Dave Marquardt, I think most weekends, is flying up to Seattle to hang out with Bill and Steve.

It was a real sell. And he said, I was young and I was single and I had nothing better to do. And it was really fun and intellectually interesting. So I did it. I bet. And that resulted in, depending how long TV I held, one of, if not the best venture capital return in history. Hard to argue with that one. Okay. Back to the story. There's a couple more really, really key things that happen in the pc era and particularly now once we're into the ibm pc era and the clones the 16-bit era and let's start with applications so you know kind of like we've been saying all along the 8-bit era applications package software aren't really a thing in, kind of at the tail end of the

8-bit era, two programs come out for the Apple II, VisiCalc and WordStar. VisiCalc is the first software spreadsheet application, and WordStar is a word processor. These applications by today's standards are super simple, like Stone Age type stuff. But they're the first of their kind, particularly VisiCalc and the spreadsheet. They sort of established the potential for business applications on personal computers. There's a joke at one point in the industry that the Apple II was a quote unquote VisiCalc accessory for small businesses. And I think that is part of what IBM is seeing and why they're deciding to now get into the industry with the personal computer. Around this time, Microsoft starts the quote-unquote

consumer products division to compete and make application software themselves. And it's quite telling. It's called the consumer products division to make applications. Even though they're competing to make these applications that today we would view as business tools, spreadsheets and word processing, that is not how they referred to it. Right. So one of the first people that they hire into this new division to get it going is an engineer, Ben, who you referenced just a minute ago named Charles Simone. And they poached Charles, perhaps with Dave Marquardt's help, away from the legendary Xerox Palo Alto Research Center, or Xerox PARC. And I think this is one of the great misconceptions in technology history. Hopefully we can set the record straight a little bit here. Yes. If you ask anybody in our ecosystem, save for the 1% of people who actually know this,

what happened at Xerox PARC? They will tell you they invented the mouse, they invented the graphical user interface, and then Steve Jobs walked in and he saw it all and he said, oh my God, we have to have it. And then he went off and he made the Lisa, which had a graphical user interface and a mouse. And then that failed. But what succeeded was the Macintosh. And it's a wholesale ripoff of Xerox PARC

that lives on today in Apple. And that is the story that you will hear from basically everyone. I've heard it characterized as something like Xerox hosted a picnic in Silicon Valley and Steve Jobs attended and dined lavishly at the feast. Which all of this is true. Which is true.

That is true. All of that is true. But it's half the story. He was not the only person who dined lavishly at the feast. Microsoft did just as much directly from Xerox and Charles was one of the main vectors by which this happened. So here is the list of things that were invented or basically invented at Xerox PARC. The graphical user interface, the desktop, the mouse, object-oriented programming, Ethernet, laser printing, along with a whole host of other things. Like, this is everything about modern computing invented there.

Who are the people who were at Xerox PARC? Well, there was Alan Kay. There was Bob Metcalf, who would go on to found 3Com. He invented Ethernet, you know, Metcalf's law. Yeah, the value of a network scaling proportionally to the square of the number of inputs. Yeah, Bob Metcalf, Xerox PARC. Larry Tesler, who would join Apple. John Warnock, who started Adobe.

Eric Schmidt worked at Xerox PARC. Everybody was there. It was a lavish picnic. And Charles Simone. And Charles Simone. Now, the thing about PARC and the computer that they built there to instantiate all these concepts, which was named the Alto, is it really was a research center. So the Alto, go look it up on Wikipedia, go look at pictures,

like it's the Mac. The Alto is the Mac. It's the Mac with the monitor turned on its side. Yes, it's a vertical Mac. It's a three by four display, not a four by three display. Now they start making it in 1973. So you might be like, wait a minute, what's going on here? The Mac doesn't come out until 1984. 11 years earlier. How on earth is Xerox making the Mac in the pre-8-bit era, the pre-microprocessor era? Well, it's not a microprocessor. The Alto is not a microprocessor architecture.

It's a mini computer. So what you see when you look at photos of the Alto is you see the Mac. What you don't see is under the table or behind it is a mini computer. Oh, I never realized that. So it is not a personal computer architecture at all. It is a 16-bit essentially mini computer that costs tens of thousands of dollars

to make each one of them. It's a science project. Right. So you should have a little bit more generosity for the East Coast management at Xerox for failing to commercialize this. Totally. The time was not right. It was not possible. It wasn't even conceived of in the microprocessor architecture because the microprocessor basically didn't exist when they made it. Interesting.

So in 1980, again, this year for Microsoft, same year Microsoft joins, same year they signed the IBM partnership, Charles Simone comes up from Xerox PARC. And he's, of course, bringing all this same knowledge, all this same experience that Steve Jobs is bringing into Apple. He's bringing all that right into Microsoft too. And the first thing that he gets tasked with is working with this new consumer products division to build application software to compete with VisiCalc and WordStar to compete with spreadsheets and to compete in word processing. And so he leads the teams that create Word and Multiplan, Microsoft's first spreadsheet.

Now, remember, we're still at the end of the 8-bit era. The graphical user interface doesn't exist yet other than on the Alto in Xerox PARC. No, these are DOS applications. It's all character mode. Yes, it is command line interface. So the vector that they think they're going to compete, at least in spreadsheets with VisiCalc, is that they're going to be on every platform out there. VisiCalc, I believe, was more or less basically only on the Apple II. Well, that doesn't end up working too well. And then the next generation, the IBM PC era, they sort of make the same mistake. The application business stays focused on being on lots of machines, making software that's compatible with everything. A new company pops up called Lotus. And Lotus makes the radical decision that they are going to make a spreadsheet

only for the IBM PC. And this was genius. This is the 1-2-3 spreadsheet. And it goes on to become, at that point in time, the most successful software ever. This is wild. I can't even believe I'm about to say this, and it blew my mind when I found it in research. There are a couple of years in the late 80s where Lotus has more revenue than Microsoft and is valued higher. Yep. In fact, the year that Microsoft went public, Lotus had more revenue than Microsoft at the IPO. Yes. Wild. Yeah, it's crazy. So Lotus 1.2.3 had some graphics, but it was still in character mode. It was a powerful spreadsheet that could start to do some graphics,

even though there wasn't actually a GUI operating system yet, which is interesting. So Lotus 1.2.3 was faster, it had bigger spreadsheets, and it was just more powerful. Microsoft Multiplan was still targeting the older 8-bit. And so Multiplan, despite Microsoft's best efforts, is completely left in the dust. Microsoft's trying to figure out,

what should we learn from this? And in talking with Pete Higgins and Mike Slade, who were both early leaders in the development and the marketing of the applications division, actually, Mike Slade went on to work directly for Steve Jobs at Next and Apple for many years. But in chatting with both of them, what basically became apparent is Microsoft learned with our applications, we should not be targeting the current platforms at all. The lesson to learn is never leave yourself open to the next generation of technology. They're learning the Moore's Law lesson again. Yes. And how it applies to applications. Yes. You always got to target the next platform. Right. Even if that platform is not the one you own. Right. That's

the interesting thing about when they're evaluating multi-plan and they say, how do we not get Lotus 1, 2, 3'd again? Basically, the applications team gets the freedom to look around and say, okay, no matter what our overall company strategy is right now, or no matter what the systems division is doing, what is the most cutting edge platform that is going to be so interesting to people that we can develop the most envelope-pushing technology for it? And that becomes the mandate for applications. This is the dawn of horizontal software. You can have a whole company or a whole division of a company in Microsoft's case that makes this tool, and that tool will be so much

better than anything that even the largest companies could have their own software developers write. General Electric isn't going to write a better spreadsheet than 123. Right. And then so I think that the technology complement to this sort of law is the killer app. You kind of have to counter position.

If 123 is the best spreadsheet out there for the current technology generation, you just can't compete with them. You need to wait for the next big leap forward in order to find a new competitive vector. You need to be the killer app on the next platform. And that's what Lotus 1.2.3 did with the spreadsheet on the IBM PC and IBM compatible PC. And that's what Microsoft decides, hey, we got to do this in the graphical interface. And who's about to decides, hey, we got to do this in the graphical interface. And who's about to come out with the very best instantiation of a graphical user interface? Apple computer. Well, that would be Steve Jobs.

Yes. The next chapter of our Microsoft story is the Macintosh in 1984. So fun. We want to thank our longtime friend of the show, Vanta, the leading trust management platform. Vanta, of course, automates your security reviews and compliance efforts. So frameworks like SOC 2, ISO 27001, GDPR,

and HIPAA compliance and monitoring, Vanta takes care of these otherwise incredibly time and resource draining efforts for your organization and makes them fast and simple. Yeah, Vanta is the perfect example of the quote that we talk about all the time here on Acquired. Jeff Bezos, his idea that a company should only focus on what actually makes your beer taste better, i.e. spend your time and resources only on what's actually going to move the needle for your product and your customers and outsource everything else that doesn't. Every company needs compliance and trust with their vendors and customers. It plays a major

role in enabling revenue because customers and partners demand it, but yet it adds zero flavor to your actual product. Vanta takes care of all of it for you. No more spreadsheets, no fragmented tools, no manual reviews to cobble together your security and compliance requirements. It is one single software pane of glass that connects to all of your services via APIs and eliminates countless hours of work for your organization. There are now AI capabilities to make this even more powerful, and they even integrate with over 300 external tools. Plus, they let customers build private integrations with their internal systems. And perhaps most importantly, your security reviews are now real-time instead of static,

so you can monitor and share with your customers and partners to give them added confidence. So whether you're a startup or a large enterprise and your company is ready to automate compliance and streamline security reviews like Vanta's 7,000 customers around the globe, and go back to making your beer taste better, head on over to vanta.com slash acquired

and just tell them that Ben and David sent you. And thanks to friend of the show, Christina, Vanta's CEO, all acquired listeners get $1,000 of free credit. Vanta.com slash acquired. All right, so David, why are we talking about the Mac? Because I think it's fair to say that the Mac made Microsoft Office and Microsoft Office made the Mac. I don't think that is actually a controversial statement. No. Although it probably sounds crazy to many of you listening. Totally.

Far and away, the first thing to point out is the first version of Microsoft Excel was for the Mac. It's especially crazy for all the finance people today who are like, oh, Mac Excel isn't real Excel. Excel has to happen on Windows. No, Excel was on the Mac. It's especially crazy for all the finance people today who are like, oh, Mac Excel isn't real Excel. Excel has to happen on Windows. No, Excel was on the Mac. That was it. Yes. And the logic basically was Microsoft was really coming around to the idea that the next big thing in computing was the graphical user interface. And the reason they were coming around to this was because they knew from Xerox Park just as well as Apple did, and they were rapidly trying to figure out how to get all of

that Xerox Parkiness into their product line too. That's the other half of this sort of untold Xerox Park story. And one of the first ways that they see to bring the graphical user interface to their products is launching Excel for the Mac, because they basically see the way that we got destroyed with Lotus 1.2.3. We can't compete with Lotus on the IBM PC. So we're going to shelve multi-plan and kind of start over. And Excel is going to come out in the graphical user interface. And we're going to try to be first and best on the GUI.

And one thing just to underscore here, Excel is the world's first graphical spreadsheet program. And that's why it wins. And that's why it's so important. Like imagine trying to use Excel in the command line interface. That's what VisiCalc was. That's what even 123 was. Yeah, useful, better than nothing. But graphical charts, cells, visual was. Yeah, useful, better than nothing, but graphical, charts,

cells, visual relationships, this is so important. And Excel is where it all starts. Yep. And of course, Apple loves this. The Macintosh came out in 1984, and everybody remembers the great intro video and the hello script. And I've watched that Steve Jobs keynote because of course I have. And it've watched that Steve Jobs keynote because of course I have. And it's this magical moment in computing history where finally something that's insanely great comes out. And it's like the beginning of Steve Jobs' unbelievable presentation prowess. It's so fun to watch it. And it's of course a product that eventually people really loved. But at first- It doesn't have the killer app.

No, it's a product that was supposed to ship in 82. It didn't. It shipped in 84. And so at the time, what they were targeting for 82 was like a pretty great set of technologies. By 84, it's kind of an aging set of technologies. So it debuts with 128k of memory, which basically isn't enough to create any interesting applications. And so developers are kind of ignoring it as an interesting platform to develop on. Within 12 months, they kind of figure it out and come out with a better version that's 512k. And that's kind of the version that people now really think about. That gets kind of rechristened as like, that's the original Mac, right? And the original original is the Mac 128 or something like that. Yes, exactly. But in the meantime, Microsoft, the applications group, is working their ass off to make something really great for the Macintosh,

and they come up with Excel. And so what ends up happening is Apple's really trying to promote sales of this machine, and they kind of view Excel and PageMaker as the killer apps, as reasons that people should buy this thing. Because once you run through a lot of the demo apps and the stuff that Apple built, you're like, okay, what else is here? It's kind of crickets. Right. Writing hello in script is, you know, cool, but kind of like a lot of VR stuff. You're like, oh, that's a cool demo. But like, you're going to do that every day? Like, no. And so I'm not sure this has ever been publicly disclosed before, but Apple spent just as much marketing Excel as Microsoft did. They matched Microsoft's marketing spend with their own campaign for it and split the bill. That's amazing.

So you've got a couple of concurrent things going on in applications land. You've got Excel coming out for Mac to take advantage of the GUI. Meanwhile, and this strategy is just all over the place. I think that's an interesting thing to underscore about Microsoft in this era. They're trying a ton of stuff because they're paranoid. They don't want to miss the next wave. Meanwhile, also in the applications group, Charles Simone has written Word. This is about a year before in 1983.

Microsoft Word comes out for DOS. Right. And they ship it with a mouse. Yes. So this is like, okay, we see the Xerox PARC stuff coming out in the Mac. Great. Excel will be for that. We want to develop Word. We're going to do that for DOS. Oh, but I can imagine how useful the mouse is going to be in a word processing environment. So they actually ship a mouse tied to the application that's not a part of DOS. And so this is how early we were in figuring out what the split between applications and platforms were at this point in history. Microsoft thought maybe a mouse makes sense just for this one application, even though it doesn't do anything else for the rest of the command line interface.

Right. Yeah, it was all being figured out. I think it is also really fair to say Microsoft was right there with Apple in the Mac development phase. Obviously, they're working on Excel, working on other, you know, what would become the Office Suite applications, you know, together for Mac. Steve Jobs shows Bill Gates the Mac project in 1981, three years before it ships. And Microsoft and Apple signed an agreement to work together on applications for it in 1982. They were very deeply embedded on this. It's amazing. Which is going to make the lawsuit and what comes up in a minute here all the more sort of funny. Yes. So the decision for the Excel team is to focus on GUI. The whole marketing message is Excel on a Mac is better than Lotus 1, 2, 3 on a PC. you're starting to see truly divergent cultures at Microsoft between

the systems group, which is currently making DOS and will soon make Windows or soon partner with IBM or soon do something else that we're getting into here in the next chapter of the story, and the applications group, which is also currently a bunch of disparate applications and teams targeting disparate platforms, but is also about to become unified in their next chapter. And within the applications group, that next chapter is Microsoft Office. So in 1985, in January, the bundle is released. And it was originally called the Business Pack for Microsoft. And it started on the Mac. It really rolls off the tongue. Totally does. Now, they

haven't acquired PowerPoint yet, or forethought, as we talked about eight years ago on Acquired, way back in history. So there's no PowerPoint. It's not part of the bundle. And so what you've got here on the Mac in the first version of Office is Word, which they've developed in-house, File, Chart, and Multiplan. This is this first notion of a suite so today we're very familiar with sweet creative suite over at adobe software is sold this way this was kind of the first time and so what was actually happening is all of the bundling was happening in pricing in marketing and in manufacturing and so you sort of had a single box that they would ship with the different applications. By 1988 or 89, it was Word, Excel, PowerPoint.

They're very different things, but they're getting sort of bundled together in a way to be sold to customers. But there's no product integration. And so you don't have the ability to do this very nice copy-paste from an Excel table and just paste that into Word. That whole idea is pretty far away. So in this earliest Microsoft Office, it was just how can we bundle something for a cheaper price if you buy all three and make marketing easier for us to kind of have this unified message. Yep. And soon to come, we'll get into Windows here in a second, one of the big, this killer app for productivity in particular, for business productivity, with a graphical user interface like Windows and true multitasking, you can get copy-paste from Excel into PowerPoint.

Lotus and the world back in the command line interface where you've got these programs running on top of DOS, that is like a completely foreign concept. Right. None of those verbs exist. Exactly. So we've now sort of set the stage of Microsoft's doing a lot of stuff. They're hedging a lot of bets. They're not totally sure which strategy is going to win out. They're not sure which platform is going to win out. They're not sure if they're more of a systems company or an application company. But what they are unified on is we make great software for personal computers. And I think anything that fell into that purview, they were willing to explore. They didn't really have hard boundaries between we'll do anything to make our operating systems great, or we'll do anything to advantage our applications, or even we do anything to advantage our applications,

or even we think we're an enterprise company, we think we're a consumer company. They just didn't have well-formed opinions yet. It was just, we make software for personal computers. And at this point in time, the actual boundary between an operating system and an application is very fluid. You've got a mouse that works for one program.

Totally. You know, Lotus would really go down a dead-end evolutionary path with Notes later in its life, in its final chapter, where the application was going to be the operating system. Right. Lotus Notes was crazy. It was a word processor, an email service, and it was a platform on which you could write other applications. Yes. And it itself was an application. It's crazy. Not an operating system. So yeah, it was all kind of dynamic. Speaking of though, Microsoft here is in bed with Apple working on the Mac. Bill and the company are big believers in the future of the graphical user interface. Starting in 1983, they're like, we got to do our own graphical operating system,

or at least user interface. And this is the origins of the Windows product. And they actually announced it in November 1983, before the Mac ends up shipping, which their partner Apple is, of course, not happy about. Now, just like development of the Mac was rocky, development of Windows was super freaking rocky within Microsoft too. This is around that same time when Paul Allen gets Hodgkin's disease and leaves the company.

So his presence as sort of great technical leader is very much missed, but they bring in someone from Xerox to manage the development of Windows. That person ends up not working out. He gets fired. Steve Ballmer gets drafted to come in and be the dev manager for the final push to release Windows 1.0, which is hilarious. You can find amazing YouTube videos from the launch and all joking about how like non-technical Steve coming in to save the day and dev manage Windows to launch.

Which is so funny. I don't think at this point in history, the lines were clearly formed among the executives yet. Like Steve wasn't running the global sales force and Microsoft wasn't an enterprise company. No, no, no. We're going to get to that later. Steve was one of the smart executives and they were a software company and someone had to manage getting the software out and Microsoft wasn't an enterprise company. No, no, no, we're going to get to that later. Steve was one of the smart executives and they were a software company and someone had to manage getting the software out the door. So Windows 1.0 comes out, it's bad.

It's bad. November 1985. Windows 1.0 is a very, very different thing than you imagine a graphical user interface is today or what you know of as Windows. It was tiled it was not overlapping windows that you can drag around and like have one over the other when you opened a program in windows 1.0 the system created a literal window of it on your screen and then it

dynamically resized the windows as you open other applications. And so nothing could ever be on top of each other. So as you open more and more stuff, the windows get smaller and smaller and smaller. It's very bizarre. Yeah, the idea of windows overlapping on top of each other, that was a sort of uniquely Mac thing and a thing that smart engineers at Apple figured out how to do that in a performant way

that offers good user experience. I would classify Windows 1.0 as like a half step between command line and an actual graphical user interface. Yes, 100%. And so I believe Microsoft and Apple actually did like a licensing agreement while they were working together during this time that said, hey, Microsoft can use a lot of the stuff that's being developed for Mac for Windows 1.0. Yes, that's right. Apple does do a deal to license a lot of, quote unquote, their intellectual property, which of course came from Xerox to Microsoft. Apple, I think, was under the impression that it was just for Windows 1.0, but the actual terms of the agreement are this and all future versions of Windows,

which comes back to haunt Apple later. But yes, they totally get the license. Also, by the time that this agreement actually happens, I think Steve Jobs has been ousted. And so it's Scully who does this agreement. And people in Apple would look back on this for years and be like, this was a huge error. The other important thing about Windows during this sort of awkward teenage phase is it's not an operating system. It's just a graphical interface on top of DOS. Yes. The original name for Windows was Interface Manager. Isn't it crazy? In all of their early marketing, they referred to it as Windows, a graphical operating environment

that runs on the Microsoft MS-DOS operating system. Yes. And actually, it was not until Windows 95 that Windows was its own operating system. It was in Windows 1, 2, 3, 3.1, and Windows for Workgroups. It was a graphical operating environment. Yep.

But here's the question. Why is Microsoft doing Windows? Obviously here, Microsoft knows they need to evolve DOS. They need to figure something out for the graphical world. And so, David, are you telling me that Windows is the widely agreed upon future of the company and it's just a straight line? Well, obviously that's a setup there. Here's the other thing that's happening in the company at this time. And it's the bigger thing. It's the next phase of the IBM relationship. Yep.

Windows, the Mac, all of this, these are hedges for the company. Microsoft and Bill in particular were masters of hedging their bets in an uncertain technology future. He was so great. The company was so great at making sure that whichever way the apple fell from the tree, as Jetson Huang put it to us in our interview, Microsoft was going to be positioned to catch it. A lot of people, including Bill and Microsoft themselves, believe that the way that Apple was going to fall from the tree here was IBM and OS too. Well, I mean, the IBM PC was such a big deal last time around. You would think that whatever IBM wants to do next is a pretty good way to ally yourself. Right. So what's going on here? IBM, obviously the PC was a huge success, but losing dominance of the ecosystem to the clones, this was bad. And so IBM wants to find a way to evolve the PC

ecosystem back to being more IBM proprietary. And they're going to make Microsoft come along for the ride here. And the way that they're going to do this is with the next generation of the PC ecosystem, they are going to make a whole new modern operating system. They're going to get rid of DOS. They're going to make this operating system in partnership with Microsoft and it's going to be called, fittingly, OS2. And they are going to lock Microsoft up that they can't license it to anybody else. OS2 is going to be proprietary to IBM hardware, just like the Mac operating system

is proprietary to Apple hardware. Ba-na-na. Ba-na-na. And as powerful as Microsoft's become here, they're still the little brother to IBM. And this is not great news for Microsoft. On the other hand, it's much better for them to be on the inside here with IBM working in bed with them than it would be to be on the outside looking in if IBM's vision comes true and they recapture control of the PC ecosystem. Yep. So Bill and Microsoft and the company and Steve too, as sort of the manager of the account with IBM, commit themselves to Microsoft is all in on this vision

of the future of OS2 and IBM is our horse in the race. This is such a crazy part of the story to me, because we just talked about how Microsoft discovered this amazing business model, and with everyone needing to license DOS from them, they're taking over the world, and they're becoming the standard development platform. Why on earth, if all that is true, are they going to develop some software that's going to be locked to IBM computers? This is a re-centralization attempt. Bomber has this great, great, great quote about it. He says, this, the IBM partnership at this time,

it was what we used to call riding the bear. You just had to try to stay on the bear's back and the bear would twist and turn and try to throw you off. But we were going to stay on the bear because the bear was the biggest, the most important. You just had to be with the bear. Otherwise you would be under the bear. And like that was IBM at this point in time. I mean, really, I think it was IBM essentially putting a gun to Microsoft's head and being like, well, you can be in bed with us on this future that we're going to re-centralize everything. Or you can be like everybody else and

not be, and you'll lose. And so even though Microsoft's doing all these little hedges, you know, Windows, this tiny little team, I think it's 30 people or something. Yes, yes. It's not the most prestigious place at the company. The people in the applications division may as well be on another planet by this point from the systems division. They're trying all kinds of crazy stuff. And the company kind of motto at this point is the next big thing is OS2 and IBM. And we are the software vendor for that. And certainly Bill, and I think Steve too, they needed to tow the party line politically of expressing that, nope, OS2 is the future. And what we're doing with Windows and with the Mac is,

you know, those are small things within the company. It's a super bizarre period in history. But IBM had also kind of made a bit of a power play too with the later generations of the 16-bit era product they called the PC-AT, they used the Intel 286 chip instead of the Intel 386 chip. And the 286 chip, this was an intentional decision on IBM's part. The 286 chip was good, but it wasn't great. Well, you say it was good, but not great. Bill Gates said it was brain dead. Yes, Bill Gates called it a brain dead chip. So I think you might be being charitable. I mean, I think it certainly was more powerful than the 8086, 8088, but it was nowhere near what the 386 could do. You know, there's a bunch of technical aspects to this, but the most important takeaway is that the 286 was not really powerful enough to do a graphical user interface or to power true multitasking

in a way that the 386 and then later the 486 would be. And so a big part of actually the Compaq story about how Compaq and the clones leap ahead of IBM is they're not deterred from coming out with 386 machines, which are way more powerful, can run Windows, can do all this stuff. And so that's how they start to separate from IBM. That's right. That was like a bet the company move where Microsoft was like, hey, Compaq, go make 386 stuff because we're going to make a really great 386 software. And we need someone to be all in on that because IBM's not. This is the thing. Bill and Steve and the company, they're having to toe the party line of expressing commitment to IBM.

But really, they're like, no, no, no, Compact, go do the 386. We're going to do Windows. They're like riling up the rebels. Exactly. They are the rebels versus the empire here. So anyway, IBM, of course, sees all this. They made the decision not to go to 386 and to discourage it in the marketplace because they didn't want PCs to start creeping into the core enterprise, mainframe IBM workloads, their core business. If that was going to happen, they wanted it to be IBM proprietary closed system. So I think that was a big part of the impetus for this OS2 initiative. I see.

This is the empire strikes back here. They're basically trying to co-opt the PC movement back into IBM proprietary land. Yes, exactly. So when OS 2 finally does come out in December 87, predictably, as you can imagine here, it's not very good. The market does not like it. Thank God for Microsoft. And I think, again, this probably was Bill's strategy all along,

that they hedged with Windows, with the Mac. That's clearly the future. The market is not going to accept OS2 and a re-centralization on IBM. Microsoft's just crushing it on the revenue side, even though OS2 is a failure. I mean, DOS and the applications were both great businesses by 87. Yes. So fiscal 87, Microsoft does 350 million in revenue. Fiscal 88, they do 600 million in revenue. Basically, none of this is from OS2 and the IBM world. And then towards the end of 1988 is when the wind starts really blowing away from IBM here. In June of 1988, Microsoft hires Mike Maples, who is IBM's Director of Software Strategy, away from IBM to come head Microsoft's application software.

And what is Microsoft's application software strategy right now? It's the graphical user interface. It's everything that IBM isn't. The writing is starting to be on the wall here that divorce is coming between IBM and Microsoft. And then finally, a year and a half later in 1990, Windows 3.0 comes out and this is when they get it right. This is when there's enough installed base of 386 and 486 machines out there in the open PC ecosystem that you can have a really good, true multitasking, good UI, graphical user interface running on top of DOS.

So Windows 1.0 and Windows 2.0 only ever achieved 5% penetration of the DOS installed base. Windows 3.0 doubles that in the first six months. PC Computing Magazine writes about Windows 3.0, May 22, 1990 will mark the first day of the second era of IBM-compatible PCs. Microsoft released Windows 3.0, and on that day, the IBM-compatible PC, a machine hobbled by an outmoded character-based operating system and 70s-style programs, was transformed into a computer that could soar in a decade of multitasking, graphical operating environments, a.k.a. everything OS 2 is not. Windows 3.0 gets right what its predecessors got wrong. It drives adequate performance.

It accommodates existing DOS applications, and it makes you believe that it belongs on a PC. That's awesome. That's what the press thought. Ben, I know you talked to a really important person in the Windows ecosystem and Microsoft internally at this time. What do you have for us? Yes, we have to thank Brad Silverberg for helping us with this section. Brad led the Windows 3.1 team. He came in right after the 3.0 release and would eventually go on to lead the Windows 95 effort as the VP of the Personal Systems Division. So Brad comes in, Windows 3.0 has just shipped.

And the first thing that is super, super obvious is, as Brad sort of observed everything going on with OS2 land and everything going on with the core Microsoft culture, it was a complete clash. It was impossible for the pace of Microsoft. This is like a super young group, I mean, all in their 20s, some people in their 30s, but mostly 20s, who just want to push the cutting edge ship stuff. It was almost like, think about Google in the early 2000s, just hire all the smartest people you can and set them loose and have creativity and bump up against the edge of what's possible, both in terms of pushing the hardware, but also pushing, I mean, even like laws, as we would later see,

let's just do what users love and see what happens. Let's just do what technology enables us to do and see what happens. That's like the opposite of IBM's culture at this point. So there's this huge cultural rift between what IBM sort of needs and who Microsoft is at this point. And so what ended up happening with 3.0, it was unexpectedly loved. Microsoft was not really prepared for how much people were going to love the GUI. And with 3.1, it got really good. There was a small offsite of the executives and Bill and Steve basically decided that it was time to bet on Windows. That was the new strategy. Windows had always been plan B, and now suddenly it was plan A. And when I say plan B, I don't mean like thought they had a prayer of being plan A. I mean, it was 65 people that shipped Windows 3.1. These were like the misfits. It was not prestigious. I

mean, the prestigious thing to work on at Microsoft was OS 2 and eventually Windows NT, but the Windows team in the Windows 3 era, it's almost like the Mac team over at Apple. They were sort of flying the rebel flag. They valued creativity over bureaucracy, even if it meant they weren't working on the prestigious thing. And so suddenly, there's this huge strategic opportunity to become the standard, independent of IBM, if the platform is good enough. And then boom, the early reception to Windows is so good. It gives this glimmer of that may seem really ambitious, but that opportunity is actually ours if we want to go seize it. So everyone took a big gulp and said,

the GUI is the next big thing. Users love this. Let's take the ragtag group and promote them. This was, I think, the moment when Microsoft started to believe in themselves, like, really. Like, you look at the facts, and as we told the story, it was like, oh, yeah, like, Bill did this great business deal with IBM and anticipated the rise of the clones in the first PC and won. And then, like, Microsoft now was the thing, and IBM was the old thing. But it wasn't until this when, like in this whole OS 2 thing, I think you can see they sort of felt like they were still little brother. They had to go along with what IBM dictated.

And now they're like, whoa. Why do we again? Yeah, we're in control. And the press is making a big deal out of Bill Gates. Boy Wonder, he's the youngest ever billionaire at age 31. And by the way, when Bill Gates became a billionaire, there were not lots of billionaires. There were like 50 billionaires. All this lore around the company, it's like they can do no wrong. But inside the company, I think they're like, we don't know the future of technology. Any wave could break against us at any moment.

And this is all tenuous. I think that chasm kept getting wider and wider and wider of internally feeling like they're screwed. And externally, it's seeming like this is the next great thing. I've got some fun stats on money and revenue around all this. So in fiscal 1990, the year that Windows 3.0 shipped, Microsoft does $1.2 billion in revenue, making them the first software company ever

to pass a billion dollars in revenue. Fiscal 91, they do $1.8 billion. Fiscal 92, they finally win the Apple copyright lawsuit around the GUI. Which, by the way, the way that they won that, a judge basically looked at the paper and said, Apple, you totally said in all the future versions of Windows, they can use your UI paradigms. And so for most of the counts, they're covered. And for these other things that you're trying to ask them about, those are not actually defensible. It's just widely accepted that these are UI paradigms now, and you can't enforce any ownership over those. So it basically got thrown out. Apple tried to appeal all the way up to the Supreme Court, who said no.

That's right. And like we've been saying too, they both stole from Xerox. Yes. Fiscal 92, though, this is when Microsoft just blows the doors off. They do $2.8 billion in revenue in fiscal 92, up from 1.8 the year before. And that year, 1992 in October, is when Gates finally passes John Kluge, acquired OG fans, back to the LVMH episode. Gates passes John Kluge of Metro Media fame, media mogul, to become the wealthiest person in America. And so everything you're talking about,

all the press comes around that. And then January 93, the crowning moment, it happens. Microsoft passes IBM in market cap. And it's like, they have inherited the earth. They have inherited computing. Supposedly, I don't know if this is 100% true. This is written in one of the books I read. I read this. The folks involved will have to confirm or deny. Supposedly, the next month after Microsoft passes IBM in market cap, so we're now in February 1993, the IBM board is in disarray. The empire is going down. They fired the CEO. Tom Murphy of Capital City's fame, who is on the IBM board,

supposedly he comes out to Redmond to sit down with Bill and personally ask him to come and be the next CEO of IBM. No way. Yes. This is what I read. I don't know if this actually happened, but this is what I read.

Is that in hard drive? That's in hard drive, yeah. Wow. Listeners, there's some unauthorized biographies that we tried to corroborate as many of the facts as we can, but the ones where David's saying he doesn't know a source, it's sort of these unauthorized ones. Yes. Gates obviously declines that, but whether or not that actually happened spiritually, you could believe that happened. Bill and Microsoft are the new emperor here. I mean, this carries through to this day. We're going to tell in the next episode here, the antitrust and the fall and all, but

not really. Microsoft's still the most valuable company in the world. They inherited the throne from IBM. Happens right here. It's nuts. And so suddenly, Microsoft feels the full weight of everything that you have to do to build a platform and be a steward of an ecosystem. So suddenly this huge effort began to try and make developers successful. That's how Windows would be successful if it was a great platform for application developers to thrive on. So Cameron Myhrvold led the developer relations group basically to try and figure out what do people want out of a platform and how do we provide the APIs for them and the support and everything in order to do that. All the

documentation, all the help, everything. And at the same time, Microsoft basically knew establishing a platform is brutal and requires bootstrapping a multi-sided network of developers, users, and PC manufacturers. And so 3.1 had users excited, but it was still very early. They could have lost that throne. Developers were not really yet targeting Windows. Microsoft sort of had to show, we make great applications for Windows too. So the applications group really had to start doing Windows 3.1. Right. Because developers were targeting DOS at this point. They were probably preparing for OS2. Some of them were targeting the Mac, like Microsoft itself, but nobody was targeting Windows.

Exactly. So you've got this big developer relations group effort that spins up. Meanwhile, there's a huge push with OEMs to get them to install Windows. At this point, they were still installing DOS, or some people were actually installing nothing and requiring users to put operating systems on. So there's a conceited push to get the OEMs to install 3.1. Well, yeah, and there's some people installing nothing. We should mention here, around this same time, this era, they move a lot of their OEM deals to a per-processor licensing fee arrangement, which gets them in a lot of hot

water with antitrust a few years later. Okay, so this happened from 1988 to 1994. David, explain the per-processor licensing agreement. Well, here's how Microsoft, I think, would position it to their OEM partners. You could pay us, you know, a license fee for every machine you ship with DOS installed on it or DOS and Windows. And you can offer other OSs too. But rather than that arrangement, we'll give you a cheaper per unit deal because you're going to ship DOS on everything. DOS is the standard and we want Windows to be the standard and Windows is going to be the standard. We'll make it more economically attractive to you, give you a lower per unit rate. If we just kind of change the terms and say, instead of every unit you ship with DOS or with Windows, every machine you ship, period,

every microprocessor-based machine that you ship, no matter what operating system is installed on us, just pay us a per processor rate. So if you do that, you'll be paying us for every machine, whether you ship DOS or Windows on it or not, but you're going to ship DOS and Windows anyway. So you may as well take the cheaper rate. May as well take the cheaper option, right? And obviously, what effect does this have on competition? Well, there's now a very, very, very strong incentive never to ship any other operating system. Yeah, basically you're going to pay for two different operating systems even though you're only putting one on if you ever

load a different operating system on. So yes, it very strongly incentivizes you to never ever ever ship any other operating systems on your computers as a company. Now this is of course the way that regulators would look at it in 1994, and that would get Microsoft in some hot water, and they had to agree to stop doing this practice. The way Microsoft would look at it is, we're just helping our customers. Do you really think that these companies want to keep a whole separate ledger of what machines they shipped DOS on or Windows on versus what machines they shipped, period? Wouldn't it just be easier if once a month or once a quarter, they could just report to us their total shipments, like they have

to report to their investors anyway, and then we'll just send them an invoice for all their machines? Totally. And while antitrust and the government would seize onto this as like a smoking gun, like, I think the reality is this was kind of irrelevant in terms of the forces that made DOS and Windows the winners. They were already the winners by the time they started doing this. Right. If this had happened earlier, you could see how this would be more of a compelling way to get market share. But by the time they started doing it, they were already sort of running away with the market. Yes. Now, speaking of this sort of new customer-friendly, buyer-friendly

business practice from microsoft which i think is how they thought about it totally they wanted to make the stuff that people wanted to use the most and that's how they would win their goal was make the very best products the best software we possibly can in the ways that people want to use and buy software and then we'll make a bunch of money yep as. As this changing of the guard is happening from IBM to Microsoft, I think part of this new self-confidence from Microsoft is, wait a minute, why can't we go win the enterprise too and take that from IBM? We don't have to get in bed with them to sell to the enterprise. We should sell to the enterprise.

And the thing they were sort of realizing is, well, we have made software that people like to use, so they're using it in businesses. They always kind of wanted that to be the goal, but now it was happening. People are doing their work in Excel. People are bringing PCs to the office. Maybe businesses are buying their PCs, but people are actually buying them themselves and using them in the office. And so it just made them that much more efficient. And so Microsoft really had to figure out how to sell to businesses, but we actually have no idea how to do that. And it sounds crazy today.

The Microsoft you know today, as late as the mid-90s, really had no idea how to sell or build software for businesses. Totally. And then this is the first half of the original Microsoft vision statement coming true, a PC on every desk and in every home. Desk means work, means enterprise. Yeah. And this era, everybody we talk to gives 100% of the credit to Steve Ballmer. Steve took it on his shoulders at this point in time when Microsoft is passing IBM to say, I am going to build and we are going to learn as a company how to sell to enterprises. And Ben, like you're saying, it's impossible to imagine now Microsoft not like this, but there's so much that they needed to do that they didn't have.

In part because prior to this, personal computers were not used by enterprises. It was just not an enterprise tool. So now that it was happening, Microsoft had to figure out how to be the ones that would benefit from it. Yep. And that meant selling to the C-suite at global Fortune 500 companies, most of whom did not use computers. Correct. And certainly didn't want to buy operating systems one at a time. Right. And to the extent members of the C-suite like CIOs or proto-IT organizations used computers

or were the computing centers in the company, they hated the PC. It made their life hard. This was like when employees would bring a PC to work and plop it down on their desk and start mucking around with stuff. It made things hard. Right. And there really isn't yet a business server that couples nicely with the PC on the desk. And so you have this weird thing where there's a mainframe that is where the company's like real enterprise applications run, but people are bringing PCs and those PCs don't actually communicate well with anything else yet. They just are there for the employee to do their own work on a spreadsheet or something,

print it out, because finally 3.1 had printer drivers, and then deliver that. But it wasn't like a system that operated with other systems in your enterprise. Right. There's no email. So this really was like a business transformation task for the global Fortune 500. Right. It wasn't like, hey, let's sell something to businesses that they want to buy. It's, hey, let's convince businesses that PCs are a good idea for their workforce to adopt. Right. This was partnering with the consulting firms. This was building a direct sales force within Microsoft. This is building an indirect sales force within Microsoft to partner with distribution partners, with channel partners, with independent software vendors. This is building a customer service organization. This is building the executive briefing center on the Microsoft campus and SQL Server and Active Directory, like the classic

mid-2000s Microsoft stuff that they got known for. But that is what this would all evolve into. And it really just started with everyone kind of looking at Steve and saying, can you figure this out? We've all to date basically just been either running dev teams or running marketing or running product groups and been selling through retail or distributors in the application side or mostly through OEMs on the systems and operating system side. But can you go figure out how to sell everything we make in a completely different way to a completely different buyer profile and keep us posted on how that needs to change all the products we make in order to do that? That's a pretty crazy change.

Yeah. And how it actually goes down, and we sort of heard this from Steve and you heard it from other people, is so fitting. So by the end of 1990, the Microsoft-IBM divorce is official. IBM takes full control of OS2 development back from Microsoft. Microsoft ceases involvement. The breakup is official. This now gives Microsoft and Steve hunting license in the enterprise to go compete against IBM. But they have a secret weapon that is going to enable them to come take the enterprise from IBM. And Ben, tell us what it is.

Well, it's painfully obvious. It's Microsoft Office. And it's the fact that the whole workforce is already using Microsoft Office. And everyone loves to talk about product-led growth and how it's this new thing in the late 2010s and how Slack and Atlassian and Trello, everyone figured out PLG in this bottoms up workforce adopted way rather than selling to procurement or IT or the central administrator. And it's just not new. No, this has always been the case. And Microsoft invented it.

All the employees wanted to use Excel and Word, and they just had to figure, they were doing it anyway. And at some point, Microsoft needed to figure out how to take advantage of selling it centrally and how you do business with other businesses, rather than selling a zillion retail copies of people who are using it kind of illegally for their work. There's so many things that are beautiful about this. One, it's the legacy of this bet on the Mac, bet on Excel, and, you know, bet on Windows, you know, shortly thereafter that enables Microsoft to go into the enterprise because, yeah, even though they've just broken up with IBM and OS2

isn't going anywhere, it's not like Steve can just go knock on the door of some banking CEO or C-suite and be like, I'm Microsoft. Come talk to me about how you're going to use Microsoft products in your organization. But rather, it's like, hey, thousands of people in your organization are already using Excel. Let's have a conversation about how we can make that work better for your organization and what else Microsoft can do for you. Yep, absolutely. And next episode is going to be all about the enormous success of becoming an enterprise company and the enterprise agreement and cloud and everything that sort of came after that.

But we have two chapters left in this episode, and they happen concurrently within the systems group by two very, very different teams, and that is Windows 95 and Windows NT. So David, let's start with NT, and then our little cherry on top can be 95 to close us out. How did Windows NT happen? Perfect. And it's intertwined with the beginning of all this enterprise-ification of Microsoft. Okay. So Windows NT. Remember, IBM's whole goal with OS2 was that they saw the trajectory of the PC was going to eat into traditional mainframe-type applications in the enterprise, and they wanted to recentralize and own the pc enterpriseification of workloads nt is after the divorce microsoft being like screw that we're gonna do the same thing and eat your lunch and so the initial work kind of starts out of the work they had been doing on os2 with IBM. But then in October 1988,

as they're heading towards divorce, Microsoft hires Dave Cutler away from DEC. And Dave is an absolute just beast and legend. Like he's still writing code at Microsoft today, which is amazing. Isn't that crazy? It's like in his 80s. Dave at DEC wrote the whole operating

system that DEC ran on, VACS. And so poaching him away to come work at Microsoft, both like, he's the guy that's going to build an enterprise-ready, take share away from the way traditional enterprise computing is done onto the PC. He's got the chops to do this. He's also got the credibility to do this. He's written a widely deployed enterprise operating system. Yes. Him coming to Microsoft, him leading and building this effort gives Steve and the Salesforce so much legitimacy when they're going in and talking to the C-suites and the CIOs and the IT departments at enterprises. Even though they don't yet have an enterprise product to sell.

They've got DOS and early Windows, which is essentially consumer-targeted. But now they've got this guy, Dave. Yes, now they've got Dave. And we should say, Dave, this is really the first time they brought in someone who had real industry experience. I mean, in 88, Microsoft was 13 years old. So Bill Gates would have been 33.

Everyone is in their late 20s and early 30s. And Dave's mid-40s. He's like, I've seen a few things. I think it was Dave and also Mike Maples coming from IBM, too. And Mike obviously wasn't a technical leader, but on the business and strategy side too. So NT, we'll talk a lot more about it on the next episode, but spoiler alert, it is the vision of what IBM wanted OS2 to be,

but it's Microsoft's version of it. Right. It enables all of your desktop computers at the company to join and network together in a compliant way. It enables an internal server that everything communicates with. It enables a directory of all the devices on the network and all the people from your company. The punchline here is that NT becomes the seeds of Windows Server, the business line, which become the seeds of Azure today. So the other important takeaway on NT is it was going to take a long time to build. It was going to take a long time to test. It was going to take a long time to sell and deploy.

And it was going to have really strict requirements for what it could work on because it's a power-hungry operating system built for enterprise IT administrators. And so that is not your short-term product strategy. That is a long-term bet that a team is going to work on concurrently while you're figuring out what to do after Windows 3.1. So in 1991, Bill Gates sums this up in a memo where he says, our strategy is Windows, one evolving architecture, a couple of implementations, and an immense number of great applications from Microsoft and others. And every word in that sentence does a bunch of heavy lifting. So you got one architecture, okay? I think what that basically ends up meaning a few years later is one application programming interface, API,

that developers can target so that when they want to write a Windows app, it works on both NT and whatever the evolution of 3.1 is. Okay, so that's one architecture. But it says one evolving architecture. So that buys Microsoft a little bit more fluidity in the one architecture that's being targeted. Then you hear a couple of implementations.

So this basically says, even though developers are targeting what became the Win32 API, the one way that we write applications, there's two different implementations. And so for many years, they would display very differently on NT systems versus, spoiler alert, Windows 95, the successor to Windows 3.1. Oh, by Windows 95, you mean Windows 4 that was supposed to ship in

1993? Yes, I do. But it's so much sexier to say Windows 95 and name it after the year that it actually ships versus, yes. But yes, an immense number of great applications from Microsoft and others. That sort of sheds light on the DRG, the Developer Relations Group strategy of, we got to go out and be massive evangelists. And everyone in the systems group is looking over at the apps group going, did you see that? Bill Gates just said, our strategy is Windows. We're now the Windows company, and that includes great applications from Microsoft and others. And so what does that mean, applications group? Let's go first and best on Windows, get to it. I just think that sentence kind of says it all for what we're looking at 1991 through call it 2000 or so. Yeah. And, you know, we just spent a bunch of time talking about the enterpriseification and

all the amazing enterprise stuff that the seeds get sown for Microsoft at this point in time. This era is also the heyday of the consumer PC, right? 93, Jensen starts NVIDIA, graphics cards are becoming a thing. PC gaming is becoming an industry. You know, that goes all the way back to, you can even look at Minesweeper as being a seminal moment

in terms of the consumerization, these devices, these personal computers becoming companions to people's lives like the phone is today. I mean, you've got CD-ROM technology, multimedia, and Carta. The heyday of the consumer PC is here in this era. Totally.

I mean, even before Windows 95 shipped, they had 75 million Windows users. This is even before you get plug-and-play or multimedia or networking. Like, this is on Windows 3.1. Yeah. Crazy. Okay. So we've been leading up to it. We've been building hype, Windows 95, or should I say Chicago? So the Chicago name, for those of you out there who are like paying attention, you know, when this was under development and you were all excited about what Windows 95 would become, and I, you know, it's probably 1%

of our audience or something who knows the Chicago codename. They wanted to create an OS for the everyman, one that was easy to get to, a nice quality of life when you're there, it was affordable. Chicago is the perfect name in every way. And it is also kind of a contrast to what was going on in a different part of Microsoft,

where there was the codename of Cairo for a very ambitious next-generation operating system. Now, mind you, NT had already come out in 1993. So Cairo is sort of this general bucket of maybe it's post-NT, maybe it's part of NT, but this is like a really sophisticated, crazy set of technologies that we're going to eventually bake into an operating system. It doesn't really have a release date. No one really believes in any of the release dates that are proposed. But the Windows 95 team, the Windows 4 team, the Chicago team loved contrasting this idea of like a far-flung land that's really ambitious and who knows what it'll actually be like with this. Chicago is something we know quite well.

You get on I-90 from Seattle, you drive for three days and you're there. And that is sort of like the goal. That's the spiritual thing about Windows 95. Pizza, the bears, the cubs. A hundred percent. We should say Cairo never shipped. So there's a lesson in that. Might as well have been called Oz.

Or Longhorn. Okay. All right. You're getting ahead of ourselves. We are getting ahead of ourselves. So, okay. Windows 95, let's start with the launch event itself. It was a huge, ridiculous, insane day in Redmond, Washington. They set up tents all over Microsoft's campus. They flew in journalists, beta testers. There was a movement around Windows 95 in a way that you would not believe. It was an operating system launch, and Jay Leno launched it. It wasn't like Jay Leno did some stand-up. It was like Jay Leno, for 90 minutes, in a tightly scripted environment, co-hosted with Bill Gates, all of the fanfare and festivities.

There is no other word to describe the Windows 95 launch besides glorious. I am so glad that this stuff is preserved on the internet and on YouTube and that we could experience it ourselves over the past month. It might be like the peak moment of pure joy to celebrate technology before a lot of the sort of skepticism came in and the tech haters. The DOJ, you know, and yeah. Totally.

It was unabashed celebration of software is probably the best way to put it. Microsoft licensed Start Me Up famously from the Rolling Stones. It's amazing. A software company licensed Start Me Up by the Rolling Stones as the official theme song of an operating system. Yes. The idea that this would be happening, certainly back in 1975 when they were moving to Albuquerque, but even just a couple of years earlier, this is breaking new ground.

Totally. The other thing that's happening in 1995 is the internet hype is starting to build, but we will table that for next episode. Right at this point in history, only 14% of Americans had internet access. It was still very early. So there was no guarantee that any story posted online

would actually reach the masses. And so Microsoft had really relied on traditional broadcast coverage of this event and brought in all these journalists and all these print magazines and all these newspapers to kind of build the hype. I watched the whole keynote yesterday. And at the end, they ripped down the sort of back of the tent behind the stage. And there's the entire development team in the red, yellow, green, and blue squares of the Windows logo, sort of sitting outside on the big sports

field on Redmond's campus. And there's only 360 people that built Windows 95. So it's still kind of a small team, but they're all there. They're fired up. They're part of the moment. Okay. So that's the launch event in Redmond, at least. Around the world,. They're part of the moment. Okay, so that's the launch event, in Redmond at least. Around the world, people are lined up around the block to buy an operating system. There's a lot of news coverage of that. It was basically the iPhone launch of its day. Yes. They lit up the CN Tower, the Tower of London. This date, August 24th, 1995, they basically treated an operating system launch the way that you would launch like a movie or a new Madonna album. It was a marketing case study, so much so that the folks from Coca-Cola

actually reached out to Microsoft to ask them, how do you do marketing this well in the new age? Coca-Cola! To the Bill Gates quote with the Warren Buffett talk at UW. Yeah. Yes. This is a company that freaking invented Santa Claus to sell us all sugar water. And they're calling Microsoft asking, how do you market in this new era? It was that successful. They launched concurrently worldwide in eight languages. So this thread that Microsoft had of early international continued all the way through to this moment. They invested heavily in doing all of the localization and help stuff so that the whole world really could adopt something all at one time. It really was the perfect product at the right time. The internet, games, all of that. And there's so much about Windows 95 too that I'm sure you're going to get into, but like the start menu.

It was so perfect because this was the peak of the PC going fully mainstream. Nobody had ever treated software like this before. Yes, that's the takeaway. They thought about software in a completely different way. And yes, the start menu,

while it got cluttered and complicated and messed up over time, the idea of a button that you click to start using your computer was very appealing to people. Totally. The Mac obviously shared a lot of these elements, but it was at so much a smaller scale. Oh yeah. I mean, the Mac just never had any real PC penetration. From the IBM PC forward, it never had big market share. Yeah. This was like your grandmother coming into the digital world. And that is how they tried to market it. They marketed it as people on job sites using Windows.

They marketed it as people doing crafts. And there's like someone who's modeling something for an F1 car. It's just fun watching all these old videos and seeing all the different personas. Computer companies love F1 cars for demos. Totally. It's the ultimate aspirational demo. Yep. Now, I must say, this all pains me deeply as someone who never owned a PC,

grew up using a Mac, loved every bit of my Mac, was even an apologist in the sort of OS 9 era of, this isn't very good, but I'm still going to say it's good. And, you know, I was on the OS 10 public beta. I only clicked a start menu when I was like fixing a teacher's computer at school. Even though the takeaway here is everyone thought this was a great operating system and it won the market. I always looked at it like, well, it's not a Mac.

Right. Well, that's how Mac users always looked at Windows. Yes. The way that Apple products became mainstream always felt odd to me as someone who was using them when they weren't. But it's been interesting gaining a new appreciation for Microsoft through studying their history that I absolutely did not have as a user during this era. Having this discussion now makes me think, what Microsoft in this era, Windows 95, like they did what Apple tried to do in bringing Scully in. Scully came from Pepsi.

Obviously, that didn't work. But Microsoft, they're the ones who did it. They're the ones who mass marketified the computing vision. And it was the wrong strategy for Apple, and it was the ones who did it. They're the ones who mass-marketified the computing vision. And it was the wrong strategy for Apple, and it was the right strategy for Microsoft. I mean, Apple has always, at least in my opinion, created a better computing experience by being completely integrated. I mean, it's the Alan Kay quote, anyone who cares about making great software needs to build their own hardware.

And the complete integrated package that Apple offers, I have always found to be the best computing experience. And it doesn't scale. Or it didn't in that era, for sure. In that era, yeah. The way to scale is make the software that is going to get distributed on the most PCs. And then that is the most interesting to software developers. And it is the most interesting to consumers who want the software and IT buyers who want to buy the standard thing. Apple's strategy versus Microsoft's strategy in this era, Apple was always going to be a bit player rather than the sort of scale winner.

And the trade-off is lots of PCs had blue screens of death. Apple never had blue screens of death. Like, where do blue screens come from? It's driver problems. It's that the printer is not speaking the same language as your particular computer and what the operating system knows about your computer. And are the device drivers right for your particular version of whatever's on your motherboard? Apple never had those issues, but they also had very few units shipped and a much more expensive product. Sidebar, that Alan Kay quote about, if you really care about software, you do your own hardware,

makes so much more sense to me now having done this episode because he's coming from having made the Alto and the graphical interface there. The only way that he could have made the GUI on the Alto was basically building a mini computer. Yeah. Isn't that crazy? Makes so much more sense now. Yep. So a little bit more on Windows 95 before we finish the story here.

It is remarkable to reflect that it took, what, five, six years to go from Windows' plan B to Microsoft being extremely right that that was the franchise. Like that was the bet to bet the entire company on. And as Brad Silverberg put it this way to me, he said,

Windows 95 cemented Windows as the franchise product for Microsoft, which interestingly, it was not yet. And David, this is crazy. It would remain the franchise product for the next 20 years, perhaps five or 10 years too long, but we'll save that story. Yeah. And just to put some numbers on this. So August 24th, 1995 is the launch event, the glorious day Windows 95 comes out, sells a million copies in the first week, 7 million copies in the first month.

Fiscal 95, so this is the 12 months ending in June before Windows 95 comes out. Microsoft did $5.9 billion in revenue. Fiscal 96, they did 8.7. Fiscal 97, when Windows 95 is really going, they do $12 billion in revenue. First software company to pass $10 billion in revenue. Already the most valuable company in the world. I mean, they are a monster. There is no other way to put it. Yeah, it's crazy. From a product perspective, there was just so much that really got smoothed here. This was a user experience where they finally had time to think, what actually do users want to do with an operating system? What features should be part of

the OS and what should we delegate to applications? What are modern networking technologies that we should bring in? I don't want to foreshadow too much, but how should the internet be in a modern operating system? That was a huge thing. The multimedia, the video stuff, an operating system really showed up and said, we thought about this experience for you. You're looking for where to start. You're looking for cool stuff to do, and you're looking for it to not break on you. We now finally have a complete story around all of that. Yep. So a couple of interesting technical notes. It was basically all new technology. If you try to look this up, it will tell you Windows 95 was DOS-based. It still used DOS in fallback situations for older DOS applications or

drivers, but for most of the time, it was no longer true that Windows was just an operating environment on top of the DOS operating system. Windows had now become a true 32-bit operating system of its own. Windows did all the heavy lifting. It had its own file system. It accomplished a lot of the sort of user experience magic and speed that it was praised for by rewriting a lot of this from scratch. So this was kind of the beginning of Windows as its own OS. And you can see that actually change in the marketing messages that change from operating environment to operating system. So David, that brings us to the end of our chapter one. We've got plenty of analysis here to do, but my God, what a first 20 years for the company. I mean, we knew this was going to happen, right? This is why we waited 10 years

into Acquired's life to cover Microsoft. It's the most important company in the world still today. Yeah. It was so fun researching, going back and doing all this because, A, there's so many different perspectives and so much has been written. But I don't know if we've gotten it right here, but I feel like every other major attempted storytelling at this has not gotten it right. And so getting to go talk to all the people who were part of this. Well, yeah, living in Seattle is quite helpful. Yeah, like we really got that sense of like, you know, there's still a story to be told here. And

it's never been more relevant again than, you know, today. All that to say, I'm glad we waited 10 years. Right. And there's all this stuff we missed. Like I didn't mention Microsoft Research. Microsoft Research was a lot of people and a lot of money. Right. Microsoft tried to buy Intuit too along the way. That got canned. Actually, the start of research is interesting. I'll say this real quick. In 91, Nathan Mirvold started Microsoft Research and the logic is fascinating. Basically, everything Microsoft had done until that point was taking things from mainframes and mini computers

and adapting those tasks, those jobs to be done for personal computers. And at some point, they kind of looked around and said, all right, well, we did it. All the personal and business applications can now be run on personal computers. So we have to come up with uses for future technologies in order to continue to drive the ecosystem forward. There's no more low-hanging fruit. And I thought that was an interesting thesis of why to spin up a research division at that point in history. Yes. Let's move into analysis. Okay, great. So playbook, the big interesting one that I want to start with, and it actually involves a chapter from the story that we just sort of glossed over, is capital efficiency allows founders to control their own destinies in a way that you just don't get when you're selling off huge chunks of the company in order to accomplish your mission. Oh, yes. I love this. Let's just talk through the cap table over

time and how the company went public. So we talked about the partnership being 64% Gates, 36% Paul Allen. 1980, Steve Ballbar comes in and gets 8.5, 8.75, something like that percent of the company. So dilutes Gates and Allen down. Then in 1981, just a year later, they take the VC investment for 5% of the company from TVI. This also, I'm guessing around 5%, trying to reverse engineer some of the numbers. They also created an option pool where they were then creating opportunity for basically rewarding management, which is how there were 10,000 millionaires created in the Seattle area from Microsoft. Right. That's the amazing thing. The option pool doesn't get created until so late in Microsoft's life. All those Microsoft millionaires

only came from that, you know, whatever size that was 5% of the company or whatever. Right. Yes. At IPO. So even with all this dilution, so you've got the Balmer dilution, the VC dilution, and the option pool dilution, Bill Gates still owned 49% of the company. I mean, that's pretty unprecedented. And he wasn't the only one with a big chunk. Paul Allen owned 28% of the company. Steve had 7.5% of the company. This company was basically owned by the three more or less co-founders, a little tiny option pool, and then a VC who ended up with 6.1%.

I think Dave got some more shares from being on the board. You just don't see companies that look like this anymore. Yeah, this is Bill's company. This is their company. In a way that no other company is these days. No venture-backed company going through the modern era is like that. By the time you get to be public, you may still be the largest shareholder as a founder or CEO, but it's not your company.

Far from it. Yeah, absolutely. I'm trying to figure out why they were able to be so capital efficient. But it's not your company. Far from it. really fast, or it was just an era before much competition. And so they didn't need to out-raise their competitors. Once they got a little bit ahead, there was really no way for anybody else to close the gap, assuming that they executed well. I totally think it's the latter. And I think it's that the minimum fixed cost threshold to be that, you know, in Bill's words, slightly better than your competitors and get the positive spiral going was low enough that it could be paid for just in Bill and Paul's time and effort. And it was that unique moment at the beginning of the software industry

where that was true, you know, and that would never be true again. That's so, so, so insane. And there was no one else really with the knowledge either. Even if someone else came in with a big $1 million check and gave it to a competitor, in 75, how many people could really write these language interpreters? You couldn't buy the experience having written emulation software for microprocessors that Paul had. They had an obsession and an obscure skill that turned out to be one of the most valuable in the world in an area where there was a freak law of nature in play with Moore's law that was so unintuitive that you had to think from real first principles to understand the impacts of it. Yeah.

Well, I think there are two freak laws of natures. One, there was Moore's law that they were benefiting from. But then two, there was the zero marginal cost of software. Yeah, that's true. It's this complete perfect storm that enabled them to build a highly defensible business without really any investment ever. This is the largest company in the world, the most valuable company in the world, that was entirely bootstrapped.

Yes. Even though they raised money, not a single dollar of investment actually happened at this company. No. I mean, in 86, when they actually did go public, they raised $45 million and they never spent that because they generated much more free cash flow than that that year. Right. It was just a means to an end of getting public. And they needed to for the reason that they had been granting so many stock options from that little option pool to employees that they were going to blow the SEC's 500 shareholder cap by, they projected, 1987. So they wanted to go public on their own terms in 86, not when they sort of had to by SEC rules. Also, Microsoft needed to be a public company. If you're going to be an important company in

the world at this scale, if you're going to first ride the bear with IBM, but then inherit the earth from IBM, you got to be a public company. You can't be a private partnership. You're not going to go have conversations with C-suites and CEOs of Fortune 500 companies if you are a private partnership. Maybe. In this era, especially. Maybe. I don't know. I'd agree with you if you had a bunch of short-term capital interests that owned your company. But if it's all founder-owned, there are great, large, private companies in the world. Yeah, fair, true. Koch Industries is a trusted company by a whole bunch of their customers. Cargill is even bigger than that. There's a bunch of European industrial and shipping companies.

Rolex. There are privately held, big, important companies in the world. Oh, yeah, for sure. But none of those companies are Microsoft. That's true. That's very fair. And especially getting to the stage that they eventually got to being the trusted partner to governments around the free world. That requires being a public company.

Yeah. It's funny, this playbook theme. This was a moment in time and a set of factors where this worked. I mean, I guess the lesson is find an industry in its infancy and be capital efficient and run the table. That has like unique economic conditions that have never existed before to create these magical businesses you could never fathom before this new technology thing existed. It's an impossible thing to wish for. Like it may never happen again. We may never get another Google either. That's what I was going to say. It did happen again. It's an impossible thing to wish for. Like it may never happen again. We may never get another Google either.

That's what I was going to say. It did happen again. It happened with Google. But how many things can you collapse to zero? I think that's the question. With Microsoft, they were able to collapse their marginal costs to zero, but they still had distribution costs.

And then Google collapsed distribution costs to zero with the internet. So what's a big cost that a company has now? Maybe AI will collapse. You no longer need 50,000 employees. You can have five employees. Maybe it can collapse that to zero. But you need something of that scale, which is like, where does a company spend most of its money that suddenly it can spend no money on? I suppose, actually, it is on the human capital. You just look at big successful companies and look at what they spend money on and those are the candidates. Good point. Still, unlikely we'll ever find another Microsoft opportunity. Yep. Other fun things on the IPO. Do you know

who IPO'd the day before Microsoft did? Ooh, no. Oracle. Uh-huh. And Oracle had a nice pop, which actually helped Microsoft price a little bit higher in their IPO. That is another episode we have to do. Another thing adds yet another layer to the insanity of everything that we've been talking about, of why they were able to build such a successful company on such little capital. I don't think there has ever been a tailwind in history like the one that Microsoft had with the secular growth of the personal computer wave. And the only thing I can think of that is comparable is Amazon with the growth of the internet, sort of powering their early growth.

But here's the stat. From 1975 to 1986, 11 years prior to their IPO, so founding to IPO, PCs grew at a compound annual growth rate of 98%. It grew from 4,000 units per year to 9 million units per year shipped. You can almost not mess up when you have a Tilwyn like that. Yes, especially when you are like the linchpin player. Right. They managed to make themselves the point of integration for the whole industry. Yes. So oftentimes I find myself when we're looking at these companies that are like among the most successful in the world or like Microsoft, the most successful in the world, it's basically like a multi-dimensional multiplication problem where you're like,

okay, they had this unbelievable one in a zillion thing going for them, which you can sort of multiply by this other one in a zillion thing. And so it's the like zero marginal cost, zero distribution costs, unbelievable secular growth of the PC, Moore's law happening. They're the single choke point for the whole industry. It's just crazy how many things you multiply together. And of course, it should end up in a number over three trillion. Yeah. Which I'll jump in with a playbook theme that we referenced a little bit in the episode, but we really got to highlight here. Bill and Steve and Paul and everybody at Microsoft, they were incredibly talented, incredibly smart. They saw the future in a way nobody else did. But they also were willing

to hedge their bets. It's not like they just got everything right. I mean, they were going to get things wrong with OS2, but they hedged the bets with Windows. I think that is such a key lesson of when you're in a really dynamic market like this, in our ecosystem right now, in tech, venture capital, startups, whatnot, people put so much value on conviction. I have conviction. This is what the future is going to be like. And I think the Microsoft story is the opposite of that. They had conviction that- Software. Software was going to be big.

And personal computers, like creating software for desktop computers was a really good idea, and they wanted to be the best at it. Yeah. But beyond that. But the exact path of how that was going to play out, they had very little conviction and were willing to be very flexible. Yeah, you're right. It's both the hedging, but also then the ability to read the world and quickly, entirely change your strategy if you need to. And having your hedge be far enough along

that you can jump quickly to it and shift your whole organization to get on board with it. That's a hard leadership thing to do. Totally. Oh, I can't wait in the next episode to talk about the internet tidal wave memo. Yes. But that's related to your playbook theme too. You can't really do that if you don't own 49% of the company, you know, if it's not your company. Right. Which I think you're seeing play out with most CEOs today. There's a big difference between a founder CEO

and the stuff that they can do. Zuckerberg with the metaverse or Jensen with betting the whole company and going all in again on AI versus Tim Cook or Sundar Pichai, certainly a very different type of CEO. Satya is interesting. He's almost, despite the fact that he doesn't own half the company, he's got a lot of founder-like control, which I think is pretty interesting. Well, all right, don't get ahead of ourselves. Moving along. Other playbook themes. A big one that jumps out to me is that new generations

of technologies enable market dislocations. And unless you are in a transformational moment in terms of a new technology came out that enables something that wasn't possible before that's going to rearrange the whole value chain and open up new markets, it's pretty hard to go challenge an incumbent. No one was going to challenge IBM really until the microcomputer, even the minicomputer people.

Did DEC really challenge IBM? Not really. It never made a dent. It wasn't a full platform shift in the same way. Yes. And there's these little blips of it, like the GUI, I think meaningfully reshuffled the DECs. But those are the moments where you can have meaningful new entrants. And otherwise, you kind of have to bide your time and just build your hedges and see. Related, even if you are the incumbent being disrupted, it is possible to have a very, very large and durable revenue stream that can go on for a very long time. And what I'm referring to in this particular example is despite all of the dethroning that we just talked about, Microsoft would not eclipse IBM

in revenue. You mentioned market cap, David, but in revenue until the year 2015. Wow. Isn't that nuts? I sort of intentionally didn't look up revenue because it made the story muddier, but wow. Yeah, there you go. But I think that's the point, right? It's like Microsoft's perception by the market. I'm sure they were growing faster. I'm sure they had better gross margins.

I'm sure there was a better story there. And so there's multiple that comes out of story. I'm sure there's lots of good reasons why Microsoft became more valuable than IBM very early. But IBM's revenue did not peak until 2012. Wow. What? It's just like long after public perception moves on, customers still get value from something created by incumbents for a very long time. And I think that's something we often forget about in the sort of buzzy Twitterverse of like, oh,

that thing's over. It's like, it might still grow for another 20 years before it's over. Well, that also just speaks to the nature of the enterprise business too. Yes, that's a good point. You know, IBM was the enterprise business. Right. And today Microsoft is the enterprise business. Right. That's true.

Peloton revenue can dry up a lot faster than contracts for mainframes. Right. What do you got? A playbook theme that I want to highlight that really, really came out in our conversations is Microsoft was not just a talent magnet, the talent magnet during the PC era. If you were an ambitious young person, this is where you wanted to be. And it was on every dimension. If you were an ambitious young technical person, that's where you wanted to be. If you were an ambitious young salesperson,

if you were an ambitious young marketing person, that's where you wanted to be. And they just had this culture there, which is so funny. We'll talk in the next episode of how that culture really fell apart for a while there. But I asked a lot of these early people that we talked to,

what was it like being there? I mean, you guys worked yourselves half to death. Were you mad about that? Did you resent it? Were you like, we're just making Bill rich? They're all like, no. Yeah, we neglected every other part of our life, but that was the good old days. This was the magic. We were making it happen. Yeah, that totally comes through. I asked Brad, why did Windows 95 work? And there's lots of structural reasons, but he said we basically did two things. One, we laid out principles for product and then pushed responsibility down. Developers were often their own PMs. So there's sort of this idea of once you got the principles, we don't need to write a zillion specs and design something

three times and pass it through three functions. Just like, you know, the principles make great software that follows the principles. And two was he said that everyone felt personally responsible for the product, and it really showed. Anybody you talk to from this era of Microsoft, this was their life's work, no doubt about it. Yep. Something we touched on a little bit is the benefit of scaling with OEMs. This was sort of the contrast against Apple, where I said Apple was sort of always going to be a niche player by the way that they designed and built and packaged everything themselves. Apple is in many ways like the Amex, where Microsoft is the Visa.

Yes. Yeah, on our Visa episode, it just became so clear that Visa could sort of quickly take over the world and MasterCard by being an open network where they didn't have to do all the work to scale themselves. They could distribute to a bank, partner with a bank, and then boom, each of the banks that was on their network could independently scale at their own rate, which created obviously compounding effects for how fast

Visa and MasterCard could scale. The same can be said of Windows. Totally. The OEMs, yeah. I think the Microsoft OEM team for Windows was like 20 people or something. Before the enterprise, in this era that we're talking about, the group of people responsible for go-to-market for Windows

was really small. They sold some retail, but the team was just about, hey, make sure HP and... Compaq and Dell and Gateway. Exactly. That was their go-to-market. And it makes your scaling unbelievably efficient.

Dude, you're getting a Dell. Dude, you are getting a Dell. Similarly, I think the fact that they went international early was this very powerful constraint where it meant that every time they shipped software, they had to make it globally ready quickly. And so that meant that if there was any sort of network effects to your software, like anything becoming a standard, Microsoft was just way better positioned to become the standard than anyone else was. And on top of there being network effects, there's also scale economies. A word processor is a word processor.

And so the extent that you have customers in every country who can buy your one piece of software, you can amortize the development costs over a huge user base so much more quickly. A hundred percent. The fact that they forced themselves to be international early meant that every product after that also had to figure out how to do all the localization and training and all of that to get all those effects too. I mean, no matter how much time and money and resources you have to spend to localize Microsoft Word into Kanji, it's a lot less time and resources and money than developing Microsoft Word. Yes, exactly. And they just realized that so early.

They also realized that most people who were doing some sort of localization would do a shoddy job. They would think about it as lesser than the US market. And so they just did a good job at localization. They just cared. They thought of it as like, this is a strategic pillar that in every country, everyone experiences our software

to the same quality because it's our brand everywhere. And I don't know, I just think that is not how the rest of the industry thought about it. Definitely not. On top of all of this, the way that they executed it through subsidiaries was pretty genius. Redmond did not control international. They spun up country managers and subsidiaries in each of these countries in a ton of countries. And so while Redmond did the product development and then did the engineering work to do localization to all the strings files and everything for those countries, the actual marketing messaging and the sales strategy and the sales structure happened in country that was

owned by a person who lived there. So they actually could think through what is the best way for people to receive this software here, which again, that's just going to yield way better results than if you're sitting there armchair quarterbacking at Redmond thinking about how a person in Chile is going to receive your marketing message. And one other that I have is this one that we didn't really talk about, but Microsoft famously was not first to market with basically any of their applications. They aren't even really today in most cases. I mean, you think about the strategy that they had early on, spreadsheets, word processing, all these were copycats at their outset. I mean, sometimes they would do an acquisition, but most of the time they just

look at a product and say, huh, our software should do the same thing. And they would copy it. They had no shame in doing that. They had their eyes everywhere looking for good ideas and they had reverence for the good ones. And then they would just incorporate them. And on top of that, they wanted to make the software very easy to switch to. So a lot of the keyboard shortcuts in Excel to this day are there because they were originally the Lotus 1-2-3 shortcuts, and they wanted people to have the same muscle memory that just worked. So fundamentally, what this does for you as a business is it just leads to better risk adjusted returns.

You already know what's going to work before you ship it. Like, you don't really take market risk. So you're not going to be the first to the market with early adopters, but most of the time you actually don't need to be to win. And I think Microsoft, I don't know, they sort of own that idea. Most of the time people are sheepish about it. Steve Jobs famously said Microsoft has no taste. I think that's another way to put it, that it's copycatting. Well, so I do agree with your premise with all of this. I think doing this episode, though, has made me think there's a little more nuance to it. Yes. And in broad strokes, you can say that's what Microsoft's strategy was with applications over the years.

But the Microsoft versions never actually won until there was a platform shift that they could take advantage of to beat the incumbent. Like, Microsoft't gonna beat lotus one two three until the graphical paradigm came along and then excel being graphical was just obviously so much better they tried with multi-plan they failed multi-plan was fine but one two three was the winner to the nuance to me is yes but it's more like with the resources of Microsoft and the timeframe that Microsoft can afford to have, they can afford to like start building the application, start building the product, get it into market, start learning, be positioned that then when the paradigm shift comes, leap ahead. Right. That's a good point. It's also different. I mean, the

Lotus 1-2-3 multi-plan thing, in that era, Microsoft just didn't have great distribution yet. And so Lotus 1-2-3 just got pretty far ahead of them, and Microsoft had no way to catch up. A few years after that, that would basically never be true again. Yeah, it could be true too. I will say, you touched on something that's an interesting corollary to this, is their first versions of software famously are not good. You look at Windows 1.0 and 2.0, they know that it's part of the strategy and they were world-class at learning from customers and integrating customer feedback into subsequent versions. And so there's always this like saying of Microsoft doesn't have a very good first or second version, but the third version of

something is typically pretty good. And I think that fact pattern definitely follows. Yeah, I'm curious your thoughts on this. I'm so surprised. One thing that you have not brought up yet on this episode is you were a PM at Microsoft for several years. I was, but it was such a different era in that 2012 to 14 era. It's not, I guess, 2011 is when I started as an intern. I'll have a lot of thoughts on it next episode. Okay, great.

I've got one more playbook theme before we move on to power. And that's that, well, Microsoft figured out software before anybody else. And they figured out so many aspects of what it means to be a software business before anybody else. But they figured out that software is never done. Yes. I do think a lot of their competitors, you know, we did obviously didn't study Lotus to the same degree that we studied Microsoft here. We didn't study WordPerfect, you know, et cetera. But I think there was a mindset a lot of other folks that, like, you ship software and then the software was done. And that was not the culture at Microsoft. This is related to what you were just saying.

Shipping software is the beginning. You are always working on that software. Yeah, you're working on next versions and stuff. But even before the next version, the work of software is the beginning. You are always working on that software. Yeah, you're working on next versions and stuff, but even before the next version, the work of software is never done. Which of course, if you own the hardware, you definitely think of it more of like, well, we ship them the big cabinet of things and we install it and we fix it if it's broken, but we've sold them hardware. The software is required to run it, but the thing we sold them is the hardware. And if you're a pure software company, you think about the world differently. You're

like, well, I can always ship you another CD, another floppy disk, you know, over the internet, it's obviously very different. But because there weren't really software companies before them, of course, people didn't come from that mindset. And I think you still see the legacy of this right to this day in Apple versus Microsoft. Apple still is on a yearly software release cadence, which is kind of ridiculous. Whereas Microsoft's on the cloud, it's all constant. It's all constantly shipping and like, look at AI, look at open AI. The software is never done as so deeply in the software business model. Yeah, that's true.

All right, should we move on to power? Yes. So listeners who are new to the show, should we move on to power? Yes. So listeners who are new to the show, we do this section based on Hamilton Helmer's seven powers framework. And the question is, what is it that enables a business to achieve persistent differential returns, or to put it another way, to be more profitable than your closest competitor and do so sustainably? And the seven are counter-positioning, scale economies, switching costs, network economies, process power, branding, cornered resource. And David, I am pretty sure I could make a case somewhere between 1975 and 1995 at Microsoft for all seven

of these. Totally. Yeah. It's one of the most defensible businesses that they built in history. So of course they would have all seven of the powers. All right, let's run through each of them and do a quick 45 seconds on each. Great. Counter-positioning. I think the biggest example of this comes through where Microsoft was basically willing to jump on the microcomputer revolution before the incumbents were. IBM did not want microcomputers to happen. And then when they started to happen, IBM tried to figure out how to slow it down and reintegrate it into their old business model. And Microsoft basically had no baggage. And I mean, this is kind of classic

innovators dilemma stuff. They could say, well, we don't need to make any money on hardware. We don't need to even make hardware. We are free to become the whole point of integration for the entire ecosystem just by shipping bits. And that is crazy. Yep. And, you know, actually related to that, I can't believe we haven't talked about this in the episode until now.

Microsoft could enable other companies to be successful. You talk to Microsoft people, they always talk about themselves as a platform. Like, we're a platform. Other companies grow on the back of Microsoft. That was not true for IBM. Totally not true. Right. But Microsoft could make Compaq successful. Microsoft could make Lotus successful. Microsoft could make Intuit successful. Microsoft could make Netscape successful. We keep talking about Microsoft as the point of integration or choke point or dependency or standard for the whole ecosystem. Given that, it is quite remarkable how much value they created on top of the platform versus just captured for themselves. There's that famous sort of Bill Gates line, you want your ecosystem around you to be

generating more revenue than you are taking for yourself. They did a ton of that. It's the OEMs and it's the application developers. Yep. That's major counter-positioning. Okay. So that's one. Scale economies. That's everything we just talked about in Playbook. It's unbelievable. When Microsoft has an install base of 100 million people using Excel, in this episode, let's just say 10 million people who were using Excel. And suddenly some up and coming spreadsheet comes out with a cool feature like auto sum or like fill down or like draw borders around the cells or whatever. Suddenly,

Microsoft does a tiny bit of dev work and they can reap tons and tons and tons of value for doing that that the tiny company cannot do. Yep, great. So fixed amount of dev work amortized across a large customer base. I don't think we need to say any more on this. The whole episode's about scale economies. Yes, switching costs.

Well, funny thing about Monopoly is there's nothing to switch to. That's a good one. Yeah, this one's pretty related to network economies for me with this one of okay sure you can switch to another operating system like good luck getting other applications that you love know and love to run on that yeah that's the answer yep speaking of network economies developers applications oems yep there's not a classic network, Facebook or AT&T style network here in terms of one user can contact every other user, but more users being on Windows incentivizes more

developers to make great applications for Windows, which enables Microsoft to sell more copies to more users, etc. Although actually, I think once they start getting into the enterprise workplaces in general, organizations in general, there is the user network effect. Like, I want this Microsoft Word document that I just worked on for you to be able to open it and use it too. Oh, you're right. I didn't even think about that. The document formats are a huge network effect thing, even before the internet. Even before organizations were networked and computers were networked outside of an organization. File formats, you're right,

there's huge network economies to file formats. Yeah. And it's inter-organizational too. If I'm a law firm, you know, I want my clients to be able to open my Word docs. Right. Okay, next. Process power. This might be the weakest. As it so often is. It's elusive. This is a little bit later in history, but I did always think it was absolutely incredible when I was at Microsoft and we would ship a version of Office every three years. I worked on Office 15, that the entire 6,000-person organization had a process in place where we could release to manufacturing RTM on a date that we planned three years in advance and actually hit it. Like the process of the ads

cuts meetings and the zero bug bounce and the testing schedule and the triage when you had things that people wanted to introduce late in the schedule, it was a remarkable product, especially with all these teams that needed all their code to interoperate. I worked on a shared experiences team that would check things in that would be a dependency that Word, Excel, PowerPoint, all of them took on the shared code. And we knew our ship date three years in advance and would hit it. It's crazy.

Yeah, totally. This exists, especially by the time you get to the Windows 95 era, the end of this episode. It's like Rentech. The amount of stuff and process within Microsoft, you know, the device drivers, the middleware, the programming languages, the dev tools, the machine there to make all this computing work. It was like a miracle that this stuff worked, You couldn't just recreate that. It's funny. The process power, I would say, is stronger in Office than Windows. Now my colors are showing. Windows always notoriously miss their

ship dates. But I'm actually less sure that process power existed in that early days. I think they were a bunch of smart people, but I'm not sure that they had a unique way of creating software. But I think that got built over time. Yep. Agree. Okay. Branding, for sure. For sure. Don't get fired for buying Microsoft. Well, that's true. Windows 95 built a consumer brand. The idea of a consumer brand of operating

systems was, you know, there was Apple, but they were tiny, and that was more around the hardware. Yeah, it's both fronts. It's their brand in the enterprise that is an amazing story that they built their branding consumer that was the easiest to point to instantiation is like the Rolling Stones and Jay Leno, but they had a software brand that nobody had that. But branding is probably the thing that they rely on the least, interestingly enough. There are other structural reasons that they're entrenched, where even if Microsoft had a crappy brand in this era, they probably still would have won. Yep. The magic of getting the whole deal with the IBM PC and then getting to sell licenses to all the other OEMs.

Yep. Well, that brings us to the last one, which I think is a super strong one, at least in this era, cornered resource, DOS, full stop. Yeah. It didn't start as a cornered resource, but as soon as IBM started shipping it on the IBM PCs,

it was over. I'll say it again. IBM's distribution created demand for DOS, and then Microsoft just got to capture value from everyone else who wanted it. All right. Well, we would do bear and bull listeners, but we kind of know what happened after this. So the bull case is that the party continues, and Microsoft continues shipping amazing operating systems after amazing operating systems, and that stays the important thing in the world. And the bear case is something else becomes an important thing in the world. And just having this super locked-in operating system

is not actually the way to bet your whole company for the future. The dramatic tension for you all to come back for our next episode on Microsoft here is not because you want to find out what happens. Right. That's true. Okay. Takeaway, Splinter. We've spent the last probably six weeks deep in this. We've talked to everybody. What are you thinking about in the middle of the night? The IBM deal. I can't unsee it. Microsoft figured out a way to take someone else's dominance and wholesale transfer that into their dominance for the next generation.

The fact that IBM called the project chess is so deeply ironic because Bill Gates was playing chess and they played checkers. Maybe Bill was playing 3D chess. I mean, this is the thing about it, though. We got to give IBM so much credit for project chess and the PC. That they even did what they did was huge. That a big entrenched corporation like that could ship a Skunk Works project in a year, revolutionize the industry.

They just didn't end up capturing any value out of it. Yep. And if I could make a less cheeky comment on it, I would say it's that a new technology generation, when something becomes possible and opens up a new market, it enables a shift in the point of integration in a value chain. The old value chain of IBM, if you shipped the mainframe, you had all the power. But in this new world of PCs, if you controlled the operating system that all the users were familiar with and all the developers wanted to target, you had all the power. I think that is not necessarily obvious unless you went through it and have the hindsight of history to be able to articulate it.

Yeah. I think you might be right. I think that might be the single best business deal negotiation of all time. It arguably created like $3 trillion of value, so. Right, right, right. No, a lot more than that, because this is the point about Microsoft being a platform. Microsoft is worth $3 trillion, but how much value has been created on top of Microsoft? No matter what you think, good, bad, or ugly of Microsoft,

you can't deny that. Yep, absolutely. At least twice as much. probably much, much more. I mean, you watch every early interview with Bill, and you read a lot of his writing, and he's a great writer. I mean, it's awesome that so many of his memos leaked, whether intentionally or unintentionally, over time. Is that so many of his memos were issued for publication. Yes. He really did view himself as a steward of the software ecosystem and had this steadfast belief that software was magic

and was going to change the world. Over the next 20 years, from 75 to 95, software did change the world and Microsoft enabled it to happen. So again, good, bad, or ugly, whatever you think of the company, they were sincere in... I think the ugly part is a lot of people want to hate on the value capture because, God, did they capture value.

But they were sincere in their desire and ability to create too. Yep, totally. That's super related to my kind of takeaway here. You know, the moment for me in the research and then when we were telling the story along the way is when they start to believe in themselves that they don't need IBM. Just the audacity, and I mean that in a pure good way, of these kids. These kids, they changed the world. That's so trite to say. My book we read, My Daughter at Bedtime, somebody gave us.

It's like the most Silicon Valley trope-y thing ever. It's like, what do you do with an idea? And the punchline at the end of it is, you change the world. And it's become such a trope. But these kids in the 70s, they did it. And they believed in themselves in the beginning and then more and more and more over time. And then there's just this moment that I think where they started to like really truly believe that they were going to change the world. And again, good, bad, and ugly come out of that. Mostly good, I think. But yeah, just the level of ambition and audacity of these people is staggering. Yep. Is that your splinter? The splinter in your mind? That's my splinter. Yeah.

Listeners who are new to the show, we've been iterating on how we end episodes. And we decided on this recently of, you know, how should we land the plane? It's to talk about the thing that we can't stop thinking about. Yeah. I mean, this company is 49 years old and it's still the most valuable company in the world. Crazy. All right, David, I have some trivia for you. Ooh, I love it.

Trivia before carve-outs. Do you know where Dave Marquardt from TVI first encountered Bill Gates? Oh, wow. No, I just assumed it was through Steve. So Dave had watched Bill present many years earlier at none other than the Homebrew Computer Club at Stanford. Yes! none other than the Homebrew Computer Club at Stanford. The very place that is part of the Apple lore with Jobs and Waz showing off the early Apple computer. Apparently, Bill also went and made a presentation there and would hang out there, and that is where Dave first came across him.

Ah, amazing. Well, when we were talking about the letter that Bill writes to the hobbyist community decrying piracy and software. He's basically writing it to the Homebrew Computer Club. He believed that those were the people who were ripping off his software. Amazing. All right, carve-outs. All right, carve-outs for new listeners. At the end of every episode, Ben and I just chat about one or two things that we've been enjoying personally lately that usually have nothing to do with the episode. In my case, I have two. The first one has a lot to do with the episode. I have discovered slash rediscovered the LGR YouTube channel. Are you into this, Ben? No.

Clint and LGR. It stands for Lazy Game Reviews, which I think is how it started, but then it became so much more, and now it's just LGR. Clint is this awesome dude. And I think he lives in North Carolina. He is dedicated to basking in the glory and restoring and reliving and preserving computer history, hardware and software from this era. The YouTube channel is all like unboxing a compact PC from 1992. Like restoring a Windows 3.1 machine. Oh, that's awesome. It's so good. He's got like the best, most soothing voice in the world.

He just seems like such a nice dude. And he's dedicated to preserving the era of computing that we are talking about on this episode. It's so fun. That's cool. It's really hard because all hardware fails eventually. So, you know, at some point there will be zero computers out there that can run Windows 3.1 that will boot. And the only way to experience any of these things is through an emulator. And so it's kind of like, I don't know, to be able to capture, you know, high-res footage and stuff of those machines while they still work. It's cool. Yep. Super cool. My other carve out is Andre 3000 from OutKast.

Do you know what Andre 3000 is up to these days? Not at all. No. Oh my God. Okay. So GQ just did a big interview with Andre 3000 because he just released a new album. This is not what you think.

So Andre, you know, a lot of people say consensus top five rappers of all time and big boy and his counterpart now cast, you know, also great too, but they basically went out on top. So they did Speakerboxx, The Love Below. Yeah, of course. Which was their double album. I think it came out like 2004, maybe I was a freshman in college. Hey, I was on that, right? Yeah. Yeah. Everything was on that. They did it came out like 2004, maybe. I was a freshman in college. Hey Ya was on that, right? Hey Ya, yeah. Everything was on that. They did one more album and then they stopped. And Andre would be featured on some other rappers' tracks over the years, but didn't put out another

album for close to 20 years. He just put out an album and he just did this big interview, video interview with GQ. The album is a flute album. He got really into like woodwind instruments. This has been his life. He reveals in the interview that he has put out other songs and other albums over the years under pseudonyms. And it's like, this interview is so great. It's so unexpected because the interviewer keeps asking like, you're Andre 3000. Why did you stop rapping? He's like, well, I don't have anything to say. What am I going to rap about getting a colonoscopy? This is where my life is right now. And I never wanted to put out any work that wasn't both authentic and great. I just didn't have anything to say anymore.

Yep. I love that. Have you ever heard the phrase, go out when the top row at the back of the auditorium is empty? Yeah. Yeah. And that's kind of what they did. Idlewild, which was the album that came out after Speakerbox, The Love Below. Like, you know, this was great, but it wasn't that. And yeah, that's exactly what he did.

I think it's a Seinfeld quote. I might misattribute it. Drop a note in the Slack if I did. But yeah, I think it's a Seinfeld quote. I might misattribute it, drop a note in the Slack if I did, but yeah, I think it's a Seinfeld quote. You can let one row be empty, but you don't want to wait too long. Yeah. It's same thing as what Seinfeld did. Fascinating. Yeah. Super fun. We'll link to it in the show notes. All right. I have three and they're all sort of different. We've sort of had a tradition on the recent episodes of doing multiple carve outs and all of them sort of different. We've sort of had a tradition on the recent episodes of doing multiple carve outs and all of them sort of are different genres. So my product that I've really been loving, my physical product is the Meta Ray-Bans. Oh, yes. I was talking with the team at Meta

about them. They're doing great. I bet. It's a pretty delightful product. I bought them because I was in Hawaii and with my four-month-old son, we were in the pool and stuff. My iPhone's waterproof, but I kind of want a different angle and I don't necessarily want to be holding my phone. It's very cool to be able to take pictures and record video of what I actually see to be able to relive that moment. And I did a bunch of photos and video and we were on vacation that way. And then I discovered a thing that they're actually just awesome for, I think even better than AirPods, is phone calls. The speakers are great. I wouldn't say like necessarily they're the best for listening to music. The bass

is obviously not as good as headphone bass. They project the sound down toward your ears. So unless you're standing really close to me, you can't really hear, or unless I have the volume all the way up, but the microphones are great too. So I was on a long walk on the beach with the wind whipping by on a call with my mom. And I was like, does this sound really bad and distorted to you? She's like, not at all. And so I was really impressed and will definitely be using them for more calls. I think that style of headphone over the ear, there's many things that it's not good for, like when you're on an airplane or something like you want to plug your ears or if you're's a great call experience. So they're great. The battery's great. They're like four hour battery. So it's like a low key, more subtle augmented reality experience. There's no heads up display. You don't see anything, but when you get a text message, it'll read it to you. Oh, so there's more than just the camera system.

Totally. Yeah. It basically is like you have AirPods in, but you don't actually have AirPods in and you have a pretty good photo video camera on your face. Does it have an indication when you're taking photo or recording video? Yes. It's not super bright. I'm not sure everybody really knows when you are, but if you know what to look for, you know if it's on or off. Cool. So I've been loving it. I think it's a great product. I intend to wear them a lot this summer. My second one is a thank you to a very, very good designer, Julia Rundberg, who worked with David and I on a recent project

for some design work, some of which is actually featured as we speak on Apple Podcasts. And she did a bunch of other stuff with us too, and she's really excellent. So if you're looking for someone who's good at visual identity, slide decks websites i've worked with her on a few projects before and she's just awesome so i wanted to recommend her my third this is kind

of community spotlight to go all the way back to like nine years ago acquired it was a listener who runs a company called summer Health reached out and said, I heard you say that you have a baby. I've got this great company that is for new parents. And here's some info on it. And I am now a paying member. It is a on-demand texting relationship with a pediatrician. Oh, wow.

This is like crack for new parents. It is like crack for parents. It's crazy. And you can hook up multiple phones. So my wife and I both have a direct line to like, something weird is going on. Will you help me through it? Including we had a 2am wake up the other night and some, you know, everything ended up being fine. But as I'm sure any other new parents can relate to, you really want to make sure in the middle of the night, if you're not sure if everything's fine, you would like to figure out the right steps to make sure everything's fine. So having a virtual doctor on demand is totally amazing. So Summer Health, if you are a new parent, we've been loving it. Amazing. Well, I'm going to have to subscribe. We've referred to this before. I think this will probably be the last episode that comes out while I'm still the parent of just one child.

Wow. We have number two coming soon. So if it may take a little longer than usual for the next Microsoft episode to come out, our next six-hour opus on Microsoft, don't get too mad. That is the reason why. Yep. Well, we have a lot of thank yous on this one, as you can imagine. People were really generous with their time, pointing us to different resources, explaining their recollection of history as it happened. And, you know, being in Seattle, active in the venture community here, both through PSL and David, you're in my shared history at Madrona, me working at Microsoft, a lot of good opportunities to learn what really happened from folks. So a huge thank you to Mike Slade, who spent the time with me. Mike spent two different stints at Microsoft and then at Next and Apple in between. Yeah, he worked for Steve at Next,

right? Yep. And one of the few people in the world who both spent a ton of time with Steve and with Bill and worked closely with both of them. So, so great to get his perspective, especially about the early days of Office and the applications group. Very helpful. Similarly, Pete Higgins worked closely with Mike. Pete, I think, ran Excel for a long time and oversaw a lot of the different stuff in the applications group, and I believe also ran Office. It's kind of funny how many different people picked up the mantle over time as these things traded around groups. But frankly kind of funny how many different people picked up the mantle over time as these things traded around groups. But frankly, I think that's a huge part

of the Microsoft story, is the company very quickly adapted and changed its structure depending on the current needs of technology and competitors and et cetera. Huge thanks to Tren Griffin, who is actually a lifelong Seattleite and sort of close friend to the whole Gates family.

Bill Gates Sr. was his mentor. I'm sure you've seen Trenn's prolific tweets online about Microsoft history. So Trenn, and actually Trenn, I think currently works at Microsoft in a strategy role. So thanks Trenn for your help as well. David, I know you've got a bunch. Yes, also speaking of former Microsoft folks

who are very active and prolific on Twitter, we talked to Steven Sanofsky who had lots and lots of great perspective and we can't wait to share more of it on the next episode. I read like 20 of Steven's hardcore software posts. And then when David and I were dividing up what belongs in what episode, I realized like 19 of them belong in next episode. So Stephen, thank you for your early prep work

for part two. Yeah. So much fun internet stuff to talk with that Stephen was right there for. I spoke with other people who ran Windows, Terry Meyerson, who's a great friend and a supporter of the show. Terry ran Windows for quite a long time, right? Yeah. When I was there, Terry was EVP over, I think, Windows and Windows Phone. Yeah. Terry was very generous. And he was actually the first person that clued us into just how key Steve's role was in building the enterprise for Microsoft. Yep. And how different the go-to-market motions were for Windows and Office. I think Terry was the one that sort of gave us

the insight of Windows, especially in the early days, was basically an OEM game, small group doing an OEM thing. Right, there were like 10 people selling that. Right. And it's still, I don't think, a very big team even today. Yep. Speaking of strategy, Charles Fitzgerald,

who's OG, OG Microsoft, and a great platform strategy guy, prolific angel investor in Seattle now. Spun chatting with him about the early days. Yep. Obviously, Brad Silverberg, who we mentioned a bunch. It was very fun seeing, after spending some time talking with Brad and texting a lot with him, to see the end of the Windows 95 announcement after Bill and Jay Leno are done for Brad to sort of come out and finish it off. It's fun. It's like watching a time machine, watching that thing. It's really cool. Soma, Soma Segar

at Madrona is someone that David and I love crossing paths with in the Seattle entrepreneurship ecosystem. Yeah. Soma's just such a legend at Microsoft and in the industry too. There's so many people who Soma made their careers, plucked them out of school, saw something in them that maybe they didn't even see in themselves. And then they went on to be big executives or venture capitalists at Microsoft or elsewhere. Yep. And lastly, huge thank you to Steve Ballmer. To be honest, it was a little bit surreal chatting and hearing about his experience over the whole thing because, I don't know, there's nobody, including Bill Gates, that bleeds Microsoft more than Steve Ballmer. And his just unabashed, pure pride in what they built is infectious. Absolutely. It was so fun talking to Steve. He was so gracious with his time. And

it must have been just super special for you too. He was the CEO when you worked there. Totally. And to be frank, I had a very opposite strategy in mind, but I was a new hire out of college, individual contributor PM. And it was still the Windows company then, and Steve was championing the Windows strategy, and I was a guy working on Office for iPad. If you like this episode, I was thinking of ones to recommend. It would be pretty funny to go listen to the Forethought acquisition, given all of this context. I mean, it's a short episode when David and I were not good at this yet, and we did our very best, but it is from our early days and it covers

overlapping source material. Yeah. Forethought was the company that made PowerPoint, Microsoft acquired. The first major acquisition for the company. Yep. If you are new to the show and looking for great recent episodes that we've done, I highly recommend the Visa one, as discussed earlier in sort of the network of networks idea, if you haven't heard that, or perhaps the Nintendo or NVIDIA episodes, all of which will be right up your alley

if you liked this one. And if you're not at all interested in technology or software, but have somehow managed to get through all these hours with us, go listen to our LVMH and Hermes episodes, even if you do love technology and software, which obviously you do if you're still here. There's so much to learn from that world. Yep. If you want to know every time an episode drops, get hints at the next episode topic, and get episode corrections and follow-up, you can sign up at acquire.fm slash email. Come discuss this episode with everyone else who's chatting about it at acquire.fm slash

Slack. And if you're looking for another episode, go check out our second show, ACQ2, where we will have actually some very awesome tech CEO guests coming out over the next month or so that are absolutely worth listening to, especially if you're interested in semiconductor and tech history. Now, if you want some sweet Acquired merch, go to acquired.fm.store. And with that, listeners, we'll see you next time.

We'll see you next time. Who got the truth? Is it you? Is it you? Is it you? Who got the truth now? We'll see you next time. We'll see you next time.