← Acquired

The Sonos IPO

Episode 2018-08-202018-08-20EnglishMembers only
The Sonos IPO
Listen to this episode00:00 / 1:32:37
Reading settings
Reading preferences
Text size
Download in-depth read
Read offline

English · In-depth read · Current version

Downloads are not available yet.

Text language

In-depth read · Key ideas, reasoning, and examples, organized by topic.

§01The IPO as a Long-Dated Bet

Sonos went public after a long effort to make music feel native in every room of a home. Its stated mission, as described in the episode, was to fill every home with music. The hosts treated the IPO as an unresolved bet: future results would depend on how home audio changed and how the company responded. The opening does not assume that a clear mission guarantees a successful investment; it asks what would have to happen for the IPO to look exceptional or to fail in retrospect.

The hosts initially cite a striking longevity figure: 93% of speakers sold over the previous 13 years were still active. They then qualify it, saying the statistic they believe appears in the S-1 is that 93% of Sonos products received and installed an over-the-air update in the last 12 months. The latter supports a claim about ongoing software support, but it is not identical to a measure of active use. Their distinction hints at Sonos’s strength and its open question: products can remain useful for years, but durability alone does not show how that value becomes recurring revenue.

§02The Company Before the Speaker

Sonos did not sell a speaker until seven years after founding. The hosts describe the earlier period as two years without a product followed by five years centered on non-speaker products, including bridges and amplifiers intended to bring digital music into the home. This history makes the later product less like a conventional speaker launch and more like the visible endpoint of a longer effort to create a connected audio experience.

The name was chosen after the founders worked with Lexicon Branding, a firm the hosts describe as especially experienced in technology naming. They recall that the founders rejected many candidates before accepting Sonos, and emphasize the name’s palindrome-like quality and legibility when the device or logo is turned. The 2015 visual refresh, with a radial pattern that appeared to move like sound waves on a screen, extended that attention to brand as part of the product experience. These examples show deliberate identity work, though the episode does not treat branding as proof of product-market fit.

§03A Network Founder’s Second Act

Sonos’s four founders had worked together before. John MacFarlane studied electrical engineering at UC Santa Barbara, left his PhD program, and founded software.com with Craig Shelburne, Tom Cullen, and Trung Mai. The company went public during the dot-com boom, merged with phone.com, and became Openwave. The hosts connect this history to early mobile email and phone browsing, giving the founders relevant exposure to networked services before Sonos existed.

After the dot-com crash, the former software.com team left Openwave and considered what to build next. Their stated insight was that wireless networks were becoming an important technology wave: Wi-Fi was beginning to appear in homes even while broadband remained uncommon and many people still used dial-up. MacFarlane’s proposal for the next company grew from that observation. In the opening history, Sonos’s founding thesis is therefore a wager that home connectivity would mature enough to support a new way of listening.

§04A Home Audio Problem Meets Digital Music

The founders did not arrive at Sonos through a product roadmap so much as through a problem they encountered in their own homes. After the dot-com boom, they had bought houses in Santa Barbara and found multi-room music systems painful to set up. At the same time, Napster and MP3s were making digital music familiar, while Wi-Fi was beginning to spread. Their insight was to connect those shifts: build devices that could put any song in any room. The episode frames this as an attempt to make home audio work with the ease of a cloud service, even before that model was commonplace.

The scale of the experience gap helps explain the ambition. The hosts estimate that a wired, multi-room installation could cost $20,000 to $50,000 if built into a home. Their own recollections of 5.1 home-theater equipment underline how much wiring and installation could burden even a single room; multi-room music was harder still. Sonos's opportunity was not merely to sell another audio component, but to make a costly, specialist installation easier to use. The evidence here is retrospective and anecdotal, but it clarifies the customer problem the founders believed they could solve.

§05Engineering for a Network That Was Not Ready

In the absence of streaming services, the first system had to work with music files stored on computers. Sonos planned to put Linux computers inside its devices, connect them to a household's Wi-Fi, find MP3s on existing PCs, and distribute playback across the home without storing those files on each player. That architecture put the consumer experience on top of a difficult networking problem: permissions and file sharing that were cumbersome for ordinary computer users had to become nearly invisible through the Sonos controller.

Keep reading as a member.

You've read the free preview. Become a member to read the rest, with side-by-side reading and downloads where available.