AAcquired
← All episodes
24 June 2019

The Slack DPO

4Frameworks
12Insights

Listen

Frameworks in this episode

Insights & moments

The myth-busts, hot takes, explainers, and tools worth keeping.

Myth Buster· 1

Myth Buster1:52:30

Correction: The Uber JFK Surge-Pricing Story, Reversed

The hosts issue a correction to a previous Uber episode: Uber actually turned surge pricing OFF (not on) during the JFK taxi strike/immigration ban protest, but still faced backlash over the appearance of strike-breaking.

  • The hosts previously said Uber turned Surge on during the JFK protest; it was actually turned off
  • Uber had a playbook for disabling Surge during crisis situations to avoid appearing exploitative
  • Despite turning it off to help people get to/from the airport, Uber was accused of trying to break the taxi strike
  • Uber's poor public perception at the time meant backlash was likely regardless of the choice made

“So we had said on the episode that they turned Surge on, and that's what people got upset about. It was actually that they turned…”

1:53:30
#correction#Uber#surge pricing

Hot Take· 1

Hot Take1:42:00

Is Slack's Always-On Culture Actually Bad for Us?

The hosts debate the downside of Slack's frictionless, real-time communication: it can turn work into an interrupt-driven, always-on experience, echoing early open-office-space criticisms.

  • Slack enables frictionless, real-time, highly interactive communication at a cultural cost
  • It shifts work from intentional, focus-driven flow to an interrupt-driven always-on state
  • Compared to open office space, we don't yet fully understand its long-term downsides
  • Unlike gig-economy companies, Slack's societal harms are seen as comparatively mild

“It's like the opposite of the four hour work week. It is the always on, always sort of stimulated, always interrupting you.”

1:43:00
#work culture#value creation vs capture#always-on

Explainer· 2

Explainer58:30

Why Slack Beat HipChat: Intra- vs. Cross-Company Network Effects

The hosts explain that Slack's growth relies on an intra-company network effect (inviting colleagues) rather than a cross-company one (like Zoom), meaning word of mouth between companies, not built-in virality, drove its explosive spread.

  • Slack has a network effect within a company (invite colleagues) but not across companies, unlike Zoom
  • Growth therefore depended on genuine word-of-mouth evangelism from happy users to friends at other companies
  • Slack and the team leaned into this by amplifying user tweets and love for the product
  • This distinguishes Slack's organic growth model from a naturally cross-company viral product

“there is a intra company network effect with Slack where you're inviting all your colleagues but there's not a cross company network effect.”

58:30
#network effects#viral growth#Slack vs HipChat
Explainer1:39:30

The Hidden Cost of Free: $8,000 CAC vs. $600 Cost of Sales

A breakdown showing that while Slack's direct sales cost per paying customer is low, its blended customer acquisition cost is high because of the expense of hosting a massive base of free users.

  • Dividing total marketing spend by new paying customers yields roughly $8,000 CAC per company
  • But cost of sales alone is only about $600 per paying company
  • The gap reflects the expense of supporting a huge free user base that never converts
  • This is the tradeoff for choosing a broad free tier as a growth engine

“If you divide their total marketing spend last year by the number of new paying customers that they brought on last year, you end up…”

1:39:30

“However, when they break out their cost of sales, it's only about $600 per company.”

1:40:00
#CAC#unit economics#free tier cost

Story· 6

Story03:30

From a Hippie Commune to Dharma Butterfield's Childhood

Stuart Butterfield's origin story: born Dharma Jeremy Butterfield in a log cabin without electricity on a hippie commune in Lund, British Columbia, to a Vietnam-draft-dodging father and a mother he met in Montreal.

  • David Butterfield dropped out of Harvard, was drafted for Vietnam, and fled to Canada instead of reporting for duty
  • David met Norma in Montreal; they drove west and joined a hippie commune at the end of Highway 101
  • Their son, born in 1973, was named Dharma Jeremy Butterfield and later renamed himself Stuart at age 12
  • The family later moved to Victoria, BC, where Stuart got his first computer at age 7

“if you asked David who he was, he often said, Who I am is I love my wife.”

07:00
#Stuart Butterfield#origin story#biography
Story18:00

A Fever Dream in New York Births Flickr

While trying to fund their ambitious MMO 'Game Never Ending,' Stuart gets food poisoning at a NYC conference and hallucinates the idea to repurpose their photo-upload tech into a standalone product that would become Flickr.

  • Ludicorp (later Tiny Spec) was building a nonviolent multiplayer game called Game Never Ending but couldn't raise enough money
  • Stuart got sick during a trip to New York and had a fever-dream idea to spin off their photo tech into a quick, sellable side project
  • The team initially voted against the idea; Stuart persuaded co-founder Eric to flip his vote
  • The photo-sharing project became Flickr, launched in December 2003

“he starts like getting kind of basically fever dreams and hallucinating.”

18:30
#Flickr#pivot#founding story
Story28:00

Oil and Water: Flickr's Culture Clash Inside Yahoo

Yahoo acquires Flickr for $22–25M with a three-year earnout; the founding team struggles to fit into Yahoo's corporate culture and eventually leaves, with Stuart writing a famously absurdist resignation memo.

  • Yahoo acquired Flickr by the end of 2004 for roughly $22-25 million, requiring the team to relocate to San Francisco with a 3-year earnout
  • The culture fit was poor; the team describes it as 'oil and water'
  • Katarina Fake and others left as soon as the earnout ended in 2008; Stuart stayed a few extra months
  • Stuart wrote a surreal resignation memo comparing Yahoo to a metals-mining company
#Yahoo#Flickr acquisition#corporate culture
Story34:30

Glitch's Rise, Flop, and the Tearful Shutdown

Tiny Spec raises nearly $18M to build the nonviolent MMO Glitch, but after launch flops and re-launches fail to gain traction, Stuart tearfully shuts the company down in an all-hands call, while treating departing employees unusually humanely.

  • Tiny Spec raised ~$1.5M from angels (including a16z) then $5M Series A and later ~$11M more to build Glitch
  • Glitch launched publicly in September 2011 but flopped despite huge industry buzz
  • In October 2012 Stuart wrote a memo to the board calling it off and then broke down in tears announcing the shutdown to the team
  • The team laid off almost everyone but worked hard to help every employee find a new job, and open-sourced all the game's code and art

“in typical Store fashion, I do not feel that we are pouring gas on a fire here. More like pouring good whiskey on a drugstore…”

42:00

“When you go through a trauma together with a group of people, you get bound together and you just want to keep working.”

47:00
#Glitch#startup failure#shutting down a company
Story51:30

The One-Week Pivot from LineFeed to Slack

After Glitch's shutdown, the four co-founders quickly realize their internal IRC-based communication tool, LineFeed, could be the real product — and pivot to building Slack within about a week.

  • LineFeed was an internal tool built on IRC to help onboard remote engineers working on Glitch
  • The pivot decision, which felt like an eternity in memory, actually took about a week according to internal chat history
  • Stuart coined the name Slack as a backronym: 'Searchable Log of All Conversation and Knowledge'
  • The team initially hated the placeholder name, but it stuck

“it felt like an eternity that we were trying to figure out what to do”

51:30
#Slack founding#pivot#naming
Story1:18:30

Excel's 25% Stake and Silicon Valley's Tight-Knit 'Yahoo Mafia'

A look at Slack's cap table at IPO reveals Excel's unusually large ~25% stake and a roster of famous angel investors and CEOs, illustrating how small and interconnected early Silicon Valley/Yahoo alumni networks were.

  • Excel owned close to a quarter of Slack at IPO, atypically high for a VC firm
  • Andreessen Horowitz owned 13%, Social Capital 10%, SoftBank 7%, and Stuart Butterfield himself a similar share
  • Angel investors included Jeff Weiner, the Collison brothers, Biz Stone, David Sacks, and others from the early web era
  • The overlapping networks trace back to the small world of early Yahoo and Web 2.0 alumni

“Excel owned close to a quarter of the company.”

1:18:30

“the Yahoo Mafia is strong”

1:20:30
#cap table#venture capital#Silicon Valley networks

Takeaway· 2

Takeaway1:23:30

The Bull Case for Slack Going Public

The hosts outline why investors are excited about Slack: world-class retention, strong CAC-to-LTV ratio, and a product that sells itself through bottom-up adoption.

  • Only about 10% of newly acquired paying customers churn in their first year, with ~80% still around after five years
  • CAC-to-LTV ratio is roughly 13x despite an ~$8,000 acquisition cost per paying company
  • Slack's sticky app ecosystem and persistent team archive create high switching costs
  • Product-led, self-serve growth mirrors Zoom's playbook of software that sells itself

“one of the biggest things is crazy strong retention.”

1:24:30
#bull case#retention#unit economics
Takeaway1:28:30

The Bear Case: Losses, Declining Retention, and Microsoft Teams

The hosts lay out reasons for caution: Slack is unprofitable with a backloaded payback period, its net dollar retention has been declining, and Microsoft Teams poses a serious competitive threat.

  • Slack has a 2-3 year backloaded payback period on customers, unlike more efficient peers
  • Net dollar retention, while still strong, has been trending down
  • Microsoft Teams bundles chat into Office 365 as direct competition
  • Other competitors like Discord are emerging in unexpected use cases

“Zoom was actually the Slack we thought we had all along.”

1:29:00
#bear case#competition#Microsoft Teams