A former founding engineer reflects on the challenges of building collaborative browser startups Sail and Muddy, detailing the lessons learned from failed product-market fit and complex positioning.

Key Points

• The team raised $5.5 million from investors including General Catalyst and YC to build a "multiplayer browser" based on Chromium.
• Products Sail and Muddy attempted to integrate infinite canvases, chat, and real-time collaboration into a unified work environment.
• Development relied on a sophisticated sync engine using GraphQL, WebSockets, and React to stream DOM mutations between users.
• The company struggled to differentiate from established tools like Slack and Notion, ultimately failing to gain broad user adoption.
• The author emphasizes the importance of "reps"—the iterative process of building, testing, and failing—to sharpen product intuition.

Why it Matters

This retrospective highlights the "novelty tax" and the difficulty of disrupting mature productivity categories where existing tools are already considered "good enough." It serves as a cautionary tale for founders about the dangers of prioritizing grand technical visions over clear, legible user workflows.