Interview with Mathilde Collin of Front, which makes tools for sharing inboxes with teammates, on company's vision to build an asynchronous version of Slack
Casey Newton / The Verge :
Context & Ripple Effects
By mid-2018 the asynchronous-workspace idea already had a proven template: Todoist's developer had launched Twist as a threaded, deliberately slow alternative to Slack a year earlier, and Slack itself had spent 2017 engineering its way toward threads with notifications and inline-vs-broken-out conversation design. Collin's interview extends that logic to a different substrate — instead of rebuilding chat around threads, Front starts from shared team inboxes and aims to add the async layer on top.
First-order effects
- Front stakes out a differentiated position against Slack: where Slack owns real-time chat, Front claims the inbox — the channel teams already use for external communication — as the foundation for asynchronous teamwork.
Second-order effects
- Slack's response pattern was absorption rather than concession: within months it bought Astro, whose tools surface important information from email and calendar, pulling email-adjacent workflow into Slack rather than letting an inbox-native rival own that ground.
Third-order effects
- If both paths keep converging — chat products adding threads and email products adding async structure — the chat-versus-inbox boundary dissolves, and competition shifts to whichever surface teams treat as the default place work gets organized.
The trend: Team-collaboration tools are converging on asynchronous, threaded communication from opposite directions — chat platforms bolting on structure, inbox platforms bolting on chat-like coordination.