Skip to main content

The Rise of Facebook, Part 10: Buying Instagram

Buying Instagram

📱 The Rise of Facebook — a 20-part series. See all parts »  |  « Part 9: Move Fast and Break Things

By the spring of 2012, Mark Zuckerberg had spent almost a decade learning a hard lesson about the internet: the thing that kills you is rarely the competitor you can see. It is the small, fast product your users quietly fall in love with while you are busy running a giant. On the evening of April 5, 2012, Zuckerberg found himself staring at exactly such a product — a photo-sharing app called Instagram, barely eighteen months old, with thirteen employees and not a cent of revenue. Four days later, he agreed to buy it for a billion dollars.

A tiny company with a terrifying growth curve

Instagram had launched on October 6, 2010, the work of two Stanford graduates. Kevin Systrom — a former Google engineer who had once turned down a job offer from Zuckerberg and interned at Odeo, the startup that became Twitter — had built a clunky check-in app called Burbn. Together with Mike Krieger, he stripped it down to the one feature people actually used: posting a square photo, running it through a nostalgic filter, and sharing it. The pared-back app hit the App Store and gained 25,000 users on its first day.

The numbers only got scarier from there. Instagram was, for its first eighteen months, an iPhone-only app — and it still crossed roughly 30 million users. Then, on April 3, 2012, the company finally shipped its Android version. It was downloaded more than a million times in a single day. A week before that, Instagram had closed a fresh round of about $50 million from investors including Sequoia Capital, at a valuation of around $500 million. A company with no business model had just been priced at half a billion dollars, and its growth was accelerating. For Zuckerberg, that curve was the whole story: mobile photos were becoming the core social behavior on earth, and Facebook did not own it.

A weekend deal, negotiated at the kitchen table

What happened next has become Silicon Valley legend precisely because of how it was done. Zuckerberg negotiated most of the deal himself, largely from his home in Palo Alto, over the course of about three days. Facebook's board was reportedly briefed only after the terms were essentially settled — a level of unilateral control few CEOs could get away with, but Zuckerberg's dual-class shares gave him exactly that. He wanted Instagram closed before Facebook's own IPO, then just weeks away, when a public company's every acquisition would be dissected by analysts.

The announced price was $1 billion in cash and stock, making it the most expensive acquisition in Facebook's history to that point. Split across thirteen employees, that worked out to something like $77 million per head — a figure so absurd it became shorthand for the entire mobile land grab. Systrom, who owned a large slice of the company, stood to make several hundred million dollars before his thirtieth birthday. Crucially, Zuckerberg promised Instagram something Facebook rarely offered: independence. Systrom and Krieger would keep running their app as a separate brand rather than being folded into the blue machine.

The bargain the numbers hid

There is a wrinkle to the billion-dollar headline. Because a chunk of the price was paid in Facebook stock, and because Facebook's shares slumped badly after its rocky May 2012 IPO, the deal's value had actually shrunk by the time it formally closed that September — to roughly $715 million. The most famous billion-dollar acquisition in tech history did not, in the end, quite cost a billion dollars.

And yet, within a few years, the reaction flipped completely. The commentators who had mocked Zuckerberg for overpaying for a toy fell silent as Instagram grew past a billion users and, eventually, into a business contributing well over $20 billion a year to its parent company. What looked in 2012 like the pinnacle of bubble-era excess turned out to be one of the shrewdest purchases ever made — a defensive move against mobile disruption that quietly became one of Facebook's greatest offensive weapons.

But buying the future does not make you immune to it. Instagram had beaten Facebook to the camera; someone else was about to beat Facebook to something else entirely — and this time, the founder would say no. Next: the messaging war, and the acquisition that cost nineteen billion dollars.


🔗 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...

Running a Server on a Mac Mini: Apple Silicon vs the Home-Server Field

The Mac Mini has quietly become one of the most interesting home-server boxes you can buy. It’s tiny, nearly silent, sips power, and Apple Silicon punches far above its weight. But is it actually the right machine to run your services on — or are you paying an Apple tax for a job a $400 mini PC does better? Let’s put it head-to-head. Why a Mac Mini makes a surprisingly good server Three things make Apple Silicon compelling as an always-on machine: Performance per watt. This is the headline. An M4 Mini idles at just a few watts and rarely pushes past ~35W under load, while delivering multicore performance that embarrasses machines drawing twice the power. Silence. Under typical server loads the fan is inaudible. If your “server” lives in a living room or bedroom, this matters more than any benchmark. Footprint. It’s the size of a coaster and runs cool, so it tucks anywhere. The honest catch It’s not all upside: macOS isn’t...