
Figma
The multiplayer canvas that made design a team sport.
Every shared artifact is a recruiting surface. Optimize the experience of the recipient who hasn't signed up yet.
Designer shares link → Stakeholder opens (no install) → Comments inline → Becomes regular viewer → Team upgrades to paid plan → More designers onboard.
Every shared artifact is a recruiting surface. Optimize the experience of the recipient who hasn't signed up yet.
Multiplayer Viral Loop
Why this company matters
Figma's wedge wasn't better design tools. It was the browser URL. A design file that anyone could open without an install, on any OS, with cursors of teammates visible in real time — that single property turned design from a craft into a meeting.
The business
Free for editors with limits, paid per seat for teams. Viewer-only seats are free forever — a deliberate choice that turned every designer into a distribution agent for the team plan.
The growth engine
Bottom-up adoption inside design teams via viewer links. Once non-designers (PMs, engineers, marketers) started receiving links, the case for company-wide accounts became impossible to refuse.
Product mechanic
Browser-native rendering meant zero install friction. Multiplayer cursors made async work feel synchronous. Components/variants encoded design systems as code, which made teams dependent on the file format.
Visual system diagram
Designer shares link → Stakeholder opens (no install) → Comments inline → Becomes regular viewer → Team upgrades to paid plan → More designers onboard.
- 01LoopDesigner shares link
- 02Stakeholder opens
- 03Inline feedback
- 04Becomes viewer
- 05Team upgrades
- 06More editors onboard.
- 01LoopDesigner shares link
- 02Stakeholder opens
- 03Inline feedback
- 04Becomes viewer
- 05Team upgrades
- 06More editors onboard.
Strategic lesson
The product surface that wins isn't the one with the most features. It's the one with the lowest activation friction for the next user in the workflow.
What builders can steal
Make sharing free, frictionless, and identity-rich (cursors, names, presence)
Build for the recipient as much as the creator
Pick a delivery surface (browser, link, embed) that bypasses IT
Encode workflows in your file format to deepen lock-in
Risks / limits
Browser-native multiplayer was a once-per-decade platform shift; replicating the wedge requires a similar surface change, not just a better tool.
Viewer-link virality assumes the artifact has cross-functional value — most B2B tools produce artifacts only one role cares about.
Adobe's failed acquisition signaled that incumbents will respond; sustaining advantage now depends on AI-era surface bets, not the original wedge.
Want more company operating manuals?
Get one new product intelligence brief in your inbox every week.
