Slack's 2013 preview outgrew its own waiting list

A preview that broke its own wait list

Slack opened a limited preview on 14 August 2013. The next morning, VentureBeat reported that 8,000 companies had signed up within 24 hours, enough that founder Stewart Butterfield joked the wait list to reach everyone would take roughly four years at the pace his team could onboard them. The same report describes the original pitch: a tool consolidating email, instant messaging, text messages and internal wikis into one place, built around full-text search across every conversation. Slack's own 2019 prospectus, filed ahead of its stock market listing, states only that the company's public launch happened in 2014, without naming a month, so the move from a 2013 preview to a fuller 2014 release is documented at different levels of precision across the two sources.

Built for the team that already had the problem

The prospectus records that Slack began as an internal tool, built so its own team could stay aligned without losing decisions and shared files inside individual email threads. That origin matters for who the product suits: it assumes a team already communicating constantly and drowning in the record of that communication, not a team trying to start communicating more. A channel is only useful once there is enough traffic to justify searching it later; a two-person team with one shared inbox has little reason to adopt the model at all.

The always-on cost the launch materials did not mention

Neither the 2013 preview coverage nor the 2019 filing addresses what happens once the searchable channel becomes the default way a team expects a colleague to be reachable. A tool built to make every message findable later also makes every message interruptible now, and the same real-time presence that replaced internal email is what critics of channel-based messaging point to when describing constant partial attention. Slack's own current about page, retrieved 16 September 2026, describes the product's mission in terms of making work life simpler, a framing that says nothing about the attention cost of a tool that is, by design, always open.

Questions to ask before you adopt it

• Does your team have enough shared history to make searchable channels more useful than a shorter email thread?
• Who sets, and enforces, the norms about response time and notification muting?
• Does the pricing plan you are on retain message history long enough for the search feature to matter?

Slack's launch materials describe a communication problem solved. They are quieter about the fact that solving it created a new always-on default a team then has to actively manage.