Figma Prioritizes Company Accounts
Matthew Moore, Head of Design at Lime, on Figma vs. Adobe
This reveals that Figma’s center of gravity is still the company account, not the designer’s personal identity. The product spread because individual designers loved it, but the paid seat, file permissions, admin controls, and security upgrades are built to serve a design leader buying for a team. That makes Figma easier to expand inside an organization, but weaker as a lifelong home for a designer’s work across jobs, side projects, and portfolio building.
-
Inside companies, Figma wins by becoming shared infrastructure. Teams move brand libraries, prototypes, comments, version history, and developer handoff into one browser workspace, then add SSO, access controls, and bulk pricing as usage grows. The buyer is usually design leadership, not IT, which reinforces an organization first model.
-
That is the opposite of Discord’s economic model. Discord makes servers free and charges end users for premium identity and participation features, which helps people carry one account across many communities. Figma’s monetization is tied to company seats and governed workspaces, so cross company identity matters less than internal control.
-
The tradeoff is strategic. Organization centric design helped Figma beat Adobe XD and drive wall to wall adoption, because companies will pay for both Creative Cloud and Figma when design teams insist on Figma. But the same structure creates friction when a designer wants to take old work into a personal archive or reuse it outside the employer’s workspace.
Going forward, the biggest product question is how far Figma can push beyond company controlled workspaces without weakening enterprise trust. The likely path is more layers, with strict company governance for core files and lighter identity, community, and portfolio features around the edges, so Figma can keep expanding seat count while giving individuals more persistent presence.