Front Built Habits Not Features
Front: Inside the $1.3B Startup Slackifying Email
The hard part is not adding collaborative features to email, it is training users to live in a new workflow every day. Front got people to discuss, assign, and resolve work inside the inbox itself, which shows up in 72% DAU to MAU, 148 minutes of daily use, and 137% net dollar retention. That kind of habit loop is what big incumbents usually fail to reproduce, even when they own the underlying account, identity, and distribution layer.
-
Email clients are unusually hard to replace because users bring years of habits with them. Shortwave describes the core migration problem as mapping stars, labels, inbox sorting, and notification patterns into a new system, which means a clone has to rebuild not just features, but a full daily routine.
-
Front works because it turns one person email into team workflow. Instead of forwarding a thread or switching to Slack, a user tags a teammate inside the message, assigns ownership, pulls in CRM or project data, and keeps the customer conversation in one place. That is a behavior change, not a UI skin.
-
Large companies often ship capable productivity software but still miss on usage intensity. The broader productivity market shows that moving from feature completeness to real daily engagement is difficult, and former Front and Outlook operator Alice Default describes rebuilding Outlook inside Microsoft as still leaving users with too much busy work. Product depth and product pull are not the same thing.
Going forward, the winners in team email will be the products that make inbox work feel native, fast, and shared, not just bundled. If Front keeps deepening the workflow around shared inboxes, assignments, and connected apps, it can stay ahead of copycats by owning the habit, which is the part of the stack that is slowest to replicate.