The publicly reported system is a five-node growth loop in which each step is publicly described and structurally load-bearing:
1. Designer creates file in Figma. The file is created in a browser-based product with no local install required. The likely operating principle is that the absence of an install step is not just a UX improvement — it is the precondition for stage 2 to work. A design file that requires local software to open cannot be shared with non-installed collaborators.
2. Designer shares file URL with non-designer collaborators. Per Figma's publicly reported product behavior, files are shared via link, the same way a Google Docs URL is shared. The collaborator does not need to be a Figma customer to receive the link; they need a browser. The structural property of the URL — that it is the artifact, not a copy of the artifact — is what makes the loop possible.
3. Collaborator opens the URL and accesses the file in-browser with zero setup. Per the publicly reported coverage of Figma's browser-based architecture, the collaborator opens the URL and the file renders immediately — no install, no account required for read access, multiplayer cursors visible if multiple people are present. The likely operating principle is that the cost-to-collaborate is essentially zero, which is what produces the volume that feeds stage 4.
4. Collaborator becomes Figma user (Free or paid). Once the collaborator has opened the file once, the likely behavioral pattern is to open it again — for review, for comment, for the next iteration. The repeated access converts the collaborator into an actual Figma user. Per Figma's publicly reported metrics, two-thirds of MAU are non-designers — the collaborators became the users.
5. New user brings Figma into their own team workflow. Once a PM, engineer, or marketer has been using Figma as a collaborator on a designer's files, they have the structural incentive to start using Figma for their own work — wireframes, presentations, flowcharts, internal docs. The non-designer use cases became publicly described expansion vectors that feed stage 1 from a different team, closing the loop.
The structural insight: the loop only works because each step has near-zero cost. The URL is shared at zero marginal cost; the file opens at zero install cost; the collaborator's access produces zero friction; the conversion to user is implicit in the repeated access; the expansion into the collaborator's own team happens without sales involvement. The compound is in the friction-removal at every step.