Figma converts viewers into paid editors
Matthew Moore, Head of Design at Lime, on Figma vs. Adobe
This is how Figma turns a design seat into an organization workflow. At Lime, the design team uses shared files, libraries, and templates so PMs, engineers, writers, and partner facing teams can make their own edits instead of waiting on designers. That matters because every time a non designer starts changing a live file, Figma stops being design software and starts becoming the place where work gets reviewed, reused, and approved across teams.
-
At Lime, only eight or nine people were active designers, but 35 to 40 people used Figma. The extra seats came from adjacent teams getting editing rights on shared files for practical work like partner materials, product copy changes, and internal decision making.
-
Another Figma interview shows the same expansion path more explicitly. People usually start as viewers or commenters in meetings, then become paid editors once they need to make recurring changes themselves. That is a low friction upgrade path built directly into the collaboration flow.
-
The broader pattern is that Figma wins the specialist designer first, then expands outward by serving jobs Canva, Miro, or Slides also touch. Canva goes wider with simpler creation for non designers, while Figma stays stickier where teams need one live source of truth tied to product design and developer handoff.
The next leg of growth is more light editing products for non designers. As more planning, brainstorming, copy editing, and partner collateral move into the same browser workspace, Figma can keep converting occasional viewers into paid contributors and raise seat count without needing every new user to become a trained designer.