Treat the real constraint in your category as people rather than features, build collaboration into the architecture itself, and enter through the teams who must work together.
Figma
Figma is the browser-first product design tool founded in 2012 by Dylan Field and Evan Wallace, two Brown computer science students who bet that design software belonged in the browser rather than on the desktop. The through-line across its stories: Figma treated the real constraint on design as people, not pixels, and built collaboration into the architecture so it could enter through design teams, spread to everyone who touches a design, and grow from roughly $0 to $400M ARR in under five years.
Beachhead: winning design teams that needed to work together, not alone
The problem. Design in the mid-2010s was a single-player experience. Incumbents Sketch and Adobe Illustrator were desktop programs built for one designer working in isolation, so getting feedback meant exporting files, emailing them, and reconciling versions by hand. Design teams that wanted to iterate together had no tool that let them do so.
The approach. Rather than build a marginally better desktop editor, Figma targeted design teams specifically with a browser-native vector tool whose defining feature was real-time multiplayer editing, multiple people on the same canvas at 60 frames per second. It launched in closed beta in December 2015 and publicly in 2016, positioning squarely against Sketch and Adobe XD on collaboration.
How it solved it. The multiplayer canvas gave design teams something the incumbents structurally could not: live co-editing with no file handoff. This wedge into professional design teams became the foothold Figma expanded from, and it eventually reached use inside 95% of the Fortune 500 and enterprise design orgs at Microsoft, Airbnb, Uber, and Google.
GTM: staging from free self-serve up to enterprise built alongside marquee customers
The problem. A collaboration tool is worth little to a lone user, but enterprises will not buy design software on a cold sales pitch. Figma needed a motion that could seed individual adoption cheaply and then convert that ground-up usage into large, high-value organizational contracts.
The approach. Figma sequenced its go-to-market in stages: a free, self-serve tier for individuals, then paid team seats, then enterprise, landing its largest accounts by co-developing with them. It built alongside its biggest customers, including Microsoft, Airbnb, Uber, and Google, rather than selling to them at arm's length.
How it solved it. The staged motion compounded: Figma crossed $400M ARR in 2022, then roughly $600M by the end of 2023 (up about 50%), and reported net dollar retention of 136% as of December 2025, evidence that landed accounts kept adding seats. By Q4 2025 it counted 67 customers above $1M ARR and 1,405 above $100K ARR.
Network Effect: spreading from designers to PMs and engineers, then across organizations
The problem. A tool adopted only by designers is easy for a company to cut, and its growth caps out at the size of the design team. Figma needed adoption to compound beyond that ceiling and to matter to budget holders.
The approach. Figma engineered both direct and cross-side network effects. Directly, features like team libraries gave designers a reason to pull teammates onto the platform. Cross-side, because work lived in a shareable browser link, designers brought in PMs and engineers to review and inspect, and those non-designers then evangelized Figma to the other design teams they worked with.
How it solved it. As the "Why Figma Wins" analysis put it, Figma recognized that "the constraints on design at companies is often not a problem of pixels, but of people," so adoption metastasized across whole organizations rather than stopping at the design team. That cross-side spread also raised Figma's purchasing priority: once PMs, engineers, and executives depend on it, it becomes business-critical spend rather than a niche designer expense, giving Figma real pricing leverage.
Differentiation: truly browser-first via WebGL, not merely cloud-stored
The problem. "Cloud" design tools of the era were still desktop apps with files synced to a server, so they inherited every friction of native software: downloads, installs, expensive per-seat licenses, and version drift. Anyone outside the design team faced a wall just to view a file.
The approach. Figma built a genuinely browser-native product on a technical breakthrough: Evan Wallace's WebGL work let the team render and manipulate a high-performance vector engine entirely in the browser, something Wallace demonstrated in early experiments (including a WebGL "Water" demo WIRED called one of the most impressive it had seen). The founders spent roughly four years in stealth building this engine before launch.
How it solved it. Because the whole tool ran in a browser, anyone with a URL could open a design with no download and no license, removing the logistical friction that kept non-designers out. That architectural choice, impossible for desktop-bound Sketch and Illustrator to copy quickly, is what let non-designers join the process and turned Figma into the collaboration layer for entire product teams.