Skip to main content

The Rise of Google, Part 10: The IPO

The IPO

🎬 Prefer to watch? Here's the 60-second version:

Watch on YouTube ▶

📚 The Rise of Google — a 20-part series. See all parts »  |  « Part 9: Adult Supervision

By the spring of 2004, Google had a problem that most companies would kill for: it was making too much money to stay private. Search advertising had turned Larry Page and Sergey Brin's dorm-room project into a cash machine, and once employee stock options pushed its shareholder count past the threshold that triggers mandatory financial disclosure under U.S. securities law, the choice was made for them. Google would have to open its books either way. If the numbers were going public, the founders reasoned, the stock might as well go with them.

They were not happy about it. Page and Brin had watched the dot-com boom mint paper billionaires and then vaporize them, and they distrusted the quarterly-earnings treadmill that public markets impose. So when Google finally filed to go public, it did so on its own terms — and picked a fight with Wall Street on the way out the door.

Breaking the underwriters' game

The traditional IPO is a clubby affair. A company hires investment banks, the banks set a price, and then they parcel out shares to favored institutional clients. Those insiders often watch the stock "pop" on the first day of trading — a tidy profit for them, and a sign that the company sold itself too cheaply, leaving money on the table. Google's founders looked at that arrangement and saw a rigged game that rewarded the middlemen.

Their answer was a modified Dutch auction. Instead of letting bankers hand-pick who got shares, Google opened the bidding to anyone with a brokerage account. Investors large and small submitted the number of shares they wanted and the price they were willing to pay. The system then found the highest price at which all the offered shares would sell — the "clearing price" — and everyone who bid at or above it paid that same amount. It was the OpenIPO model pioneered by banker Bill Hambrecht, and Google was the biggest company ever to attempt it. Morgan Stanley and Credit Suisse First Boston led a syndicate of some two dozen underwriters, but the auction, in theory, took the pricing power out of their hands.

It did not go smoothly. The initial filing floated a price range of $108 to $135 a share — numbers that struck many analysts as greedy for an unproven business model. Demand in the auction came in softer than hoped, the broader tech market was sagging, and the mechanics confused ordinary investors. In the final days before launch, Google slashed the range to $85 to $95 and cut the number of shares on offer. The stock ultimately priced at $85.

An owner's manual and a Playboy problem

Tucked inside the sober legalese of Google's prospectus was something no bank would have written: a letter from Larry Page titled "An Owner's Manual for Google's Shareholders." It opened with a line that has been quoted ever since — "Google is not a conventional company. We do not intend to become one" — and it warned prospective investors, in plain English, that the founders would not manage the company for smooth quarterly numbers, would make large and unusual bets, and expected some of them to fail. To make sure they could keep steering, Page and Brin built in a dual-class share structure: the shares sold to the public carried one vote each, while the founders' Class B shares carried ten. Wall Street bristled at the loss of control. Google shrugged.

The company even turned its filing into a joke. Its original registration announced it would raise up to $2,718,281,828 — the mathematical constant e, spelled out to the dollar. A later financial target came in at a figure matching the digits of a golden-ratio calculation. The message was unmistakable: the nerds were running this one.

Then came the near-disaster. During the SEC-mandated "quiet period," when a company going public is supposed to say nothing that could hype its stock, an interview with Page and Brin appeared in Playboy. Regulators were not amused. Rather than scrap the whole offering, Google's lawyers scrambled to file the entire interview as an amendment to the prospectus, defusing the violation. The IPO survived by a technicality.

The number that wouldn't behave

On August 19, 2004, Google began trading on the Nasdaq under the ticker GOOG. It sold 19,605,052 shares, raised about $1.67 billion, and opened the day valued at roughly $23 billion. By the closing bell the stock stood at $100.34, up about 18 percent.

Critics called the auction a flop, pointing to the slashed price and shrunken size. Defenders countered that a modest 18 percent bump was exactly the point — the auction had left far less money on the table than the typical first-day moonshot, meaning Google, not a handful of insider clients, captured most of its own value. Both sides were, in a way, right. The Dutch auction never became Wall Street's default; the old system had too many powerful people invested in keeping it. But Google had proven a public company could go public without kissing the ring, and had walked away with a war chest and a founder-controlled voting structure that would shape every decision to come.

The money was now in the bank. Next in the series: Part 11 — The Product Explosion, when a flood of cash and a policy called "20% time" gave the world Gmail, Google Maps, and the sense that Google could build anything.


🔗 Explore more from Syncster

Comments

Popular posts from this blog

Cursor AI Review: Is the AI Code Editor Worth It?

I've been using Cursor as my main code editor for a while now, and enough people have asked whether it's worth switching to that a proper review felt overdue. Short version: for me, yes — but with caveats. What is Cursor? Cursor is an AI-first code editor built as a fork of VS Code. That means every extension, theme, and keybinding you already use in VS Code works here, but with AI woven directly into the editing experience instead of bolted on as a plugin. It's made by Anysphere and can run models from OpenAI and Anthropic under the hood. What I like Tab completion is uncanny. Cursor predicts your next edit — not just the rest of the line, but the next change across the file. Once you get used to hitting Tab, going back to a plain editor feels slow. The Composer / Agent mode. You describe a change in plain language and it edits multiple files at once, showing you a diff to accept or reject. For refactors and boilerplate, this saves real time. It unde...

MacBook Pro M5 vs M5 Pro: Which One Should You Actually Buy?

Apple's latest 14-inch MacBook Pro comes in two very different flavors: the base M5 and the step-up M5 Pro . On paper they look similar — same gorgeous Liquid Retina XDR display, same design — but under the hood the gap is bigger than the names suggest. Here's a clear, no-hype breakdown, with concrete use cases so you can match the chip to your work. Quick spec comparison Spec M5 M5 Pro CPU 10-core (4 performance + 6 efficiency) Up to 18-core (6 performance + 12 efficiency) GPU 10-core Up to 20-core Neural Engine 16-core 16-core Memory bandwidth 153 GB/s 307 GB/s (roughly double) Unified memory 16 / 24 / 32 GB 24 / 48 / 64 GB Max storage Up to 4 TB SSD Up to 8 TB SSD Battery (video playback) Up to 24 hours Up to 22 hours Media engines Single encode/ProRes engine More encode/ProRes engines (higher configs) What actually changes between them More cores — the M5 Pro nearly doubles CPU cores and adds GPU cores, so sustained, multi-threaded work finishe...

How I used Google Sheets and Apps Script

Google Sheet is one of the most powerful spreadsheet application that exists online, rivaling with Microsoft's Excel. One of the main strengths is its strong support for collaboration with other users, much easier and popular than collaboration tools with Microsoft Office. Aside from plain spreadsheet, it also supports extensions such as macro. If you are familiar with macros on other office tools, they work almost the same. However, the most extension I use and tinker with is the Apps Scipt . Apps Script Extension One of the challenges I faced recently is how do I track or monitor reports in our department if they are submitted on time or worst, forgotten due to lack of better monitoring tools. So I thought if there can be simple applications that can be deployed or use by a more general user to allow reminding periodically what reports are approaching due dates or those that are past dues. Then I looked for a way, instead of creating a full blown app from scratc...