SC

Figma

Figma's founders spent three years making a design editor run in a browser, then let anyone join a file for free and sent designer advocates to the teams that carried it into their companies.

How Figma won

  1. 1 · 2012–16Browser editor: the file lives at a URLA custom browser rendering engine meant anyone with the link opened the working file.Ease of Use
  2. 2 · 2016Everyone works in one live fileEditing and review moved into the same file, shipped against designers' own objections.End-to-End Workflow
  3. 3 · 2015–19Viral adoption with free collaboratorsEditors paid, everyone else joined free; sales followed advocates into existing clusters.Product-Led Sales
  4. 4 · 2018–23Network effects: colleagues and the talent poolDesigners, product managers and engineers shared files, and new designers arrived already trained on Figma.Collaboration & exchange network effects
  5. 5 · 2018–Switching costsLeaving means moving a team's editable work and shared libraries, and retraining everyone.Switching costs

Versus InVision: InVision owned the review layer on top of other tools. Figma owned the file itself, then let everyone into it free.

Arena: Market Conditions Before Figma

Product design teams · 2015 · United States first; anyone could open it in a browser

Disconnected workflows

Interface-design teams moved work between editing tools, shared files and separate channels for feedback. Designers and colleagues could end up discussing different versions or spending time working out which file was current. Good editing tools already existed. The gap was in the work around the design: sharing, reviewing and coordinating changes across a team FG1 FG16.

How each step happened

Step 1 of 5 · 2012–16

Browser editor: the file lives at a URL

Figma's founding bet concerned where the design file lived. Sketch and Photoshop kept it on the designer's own machine, so every reviewer, developer or product manager needed a copy, an export or a separate review tool. A professional editor in the browser would put the working file behind a link that anyone could open FG19 FG1.

The bet only became possible when browsers gained access to the graphics card through WebGL. The founders spent three years in stealth writing their own renderer so the tool would feel as fast as desktop software FG28 FG19 FG24. Speed was the price of entry. Designers first turned Figma down as slow and incomplete and came back as it improved FG4; a link to a sluggish tool would not have spread.

Rivals Sketch was a Mac app and Photoshop desktop software, so a colleague on another machine could not open the working file without an export or a separate review tool FG3 FG19.

Ease of UseTrade-offs & activity fit

Step 2 of 5 · 2016

Everyone works in one live file

With the file at a URL, several people could work in it at once. Figma shipped simultaneous editing in its 2016 public release even though designers disliked the idea and pictured art directors watching over their shoulders FG2 FG21 FG24. The customer Figma had in mind was the team around the designer.

The choice made the design file the place where review, copy changes and developer handoff happened. One designer described a content strategist editing copy in his live file while he kept designing, work his Sketch setup had routed through branching and merging FG3. Comments, presentation mode and links developers could open each gave another role a reason to be in the file FG23 FG17.

Rivals Sketch teams assembled the same workflow from separate tools, with Abstract for versions and InVision for review FG3. Each tool held one part of the work; Figma's file held all of it.

End-to-End Workflow

Step 3 of 5 · 2015–19

Viral adoption with free collaborators

Winning the designers others followed

Designers had only just moved from Adobe to Sketch and were wary of switching again FG18. Figma demonstrated the product to designers one at a time in stealth, waited until one team used it full time, and launched by messaging the designers a script had ranked as most influential on design Twitter FG17 FG18. Starting with the people others copied gave every later invitation more pull.

Pricing that kept the invitation free

Pricing turned the shared file into a growth engine. Figma's first paid plan capped collaborators on free teams, which put the paywall on the feature that made Figma spread. The company reversed it: free teams got unlimited collaborators, editors paid, and viewers and commenters never did FG17 FG18 FG6. Where incumbents charged for viewer seats, each extra reviewer was a purchase FG6. At Figma each reviewer was a free new user, and some of them pulled in more designers FG22. The loop lasted. Figma sells a team plan, Professional, and two company-wide plans, Organization and Enterprise; about 70% of new Organization and Enterprise customers in 2024 and early 2025 already included someone who had been on a Professional plan FG7.

Selling to clusters that already existed

After about three years of self-serve sales, companies such as Microsoft and Google had scattered, unconnected groups of Figma users FG17 FG18. Figma hired its first salesperson and first designer advocate on the same day in 2018 and sold to the champions already inside, using maps of how Figma had spread through each company FG18 FG6. The Organization plan added company-wide shared libraries and admin controls, so a company could approve a tool its designers already used FG5 FG7. Sales converted adoption that pricing had already created.

Rivals Adobe already held enterprise agreements FG8. Figma's route into companies ran through users who were already there.

Product-Led SalesFreemium ModelCustomer Discovery

Step 4 of 5 · 2018–23

Network effects: colleagues and the talent pool

Once every role around a design worked in the same files, each group pulled in the next. Designers invited product managers and developers, and those colleagues pushed other designers toward Figma FG22. The UK Competition and Markets Authority found that customers valued colleagues using the same tool and named Figma's collaboration as a strong example FG8. This collaboration effect works inside a team or company: a designer gains from colleagues on Figma, not from strangers FG22.

A second network ran across companies, through the labor market. Figma was free for students from its 2016 launch, and its Education program gives the paid plan free to universities, bootcamps and workshops FG23 FG7. By 2023 competitors told the CMA that designers leaving university were 'more likely to launch into Figma' than into Adobe, and one described 'a virtuous cycle where people learn the tool, it becomes sort of part of their identity and that flywheel continues because it is a professional space' FG8. Every company that standardized on Figma made the skill worth more on a designer's résumé, and every trained designer made Figma the easier choice for the next employer. The CMA counted the need to retrain or hire new workers among the costs of switching design tools FG8.

Figma widened the network by building for what users already did in the files. Plugins in 2019 let companies build tools for their own workflows, FigJam in 2021 grew out of people brainstorming in design files, and Dev Mode in 2023 served developers already reading them FG9 FG11 FG28 FG13. By early 2025, 76% of customers used two or more Figma products FG7. Each product brought more of a company's people into the same files.

Rivals Sketch had plugins too, hosted on GitHub outside the product FG22. They extended a single designer's tool and brought no new roles into a shared file. Adobe held the older version of the talent advantage: designers grew up with Photoshop and Illustrator, and one customer told the CMA that talent dictates the tools it uses FG8.

Collaboration & exchange network effectsExpertise network effectsMulti-Product

Step 5 of 5 · 2018–

Switching costs

The shared files became the lock-in. Leaving Figma means moving component libraries and editable projects and retraining every role that works in them, and the CMA recorded those burdens as heaviest for large organizations FG3 FG8. Because the whole team works in the same files, one designer cannot leave alone; the group has to move together FG8.

The barrier is local. A new team with no files yet can choose a rival, which is how Figma itself took teams from Sketch through imports and coordinated switches FG3. That makes being the tool a team starts on the real defense, and the free collaborator seat from step 3 is what puts Figma there first.

Rivals Sketch and Adobe XD kept established users, and import tools lower the cost of moving FG8 FG3.

Switching costs

Key dates

  1. 2012-08Founded to build creative tools in the browser
  2. 2015Demos to designers and a first full-time team
  3. 2015-12A browser editor behind a link, launched to design Twitter
  4. 2016-09Open signup and simultaneous editing
  5. 2017Paid plans launch, then the cap on free collaborators is reversed FG24 FG18
  6. 2017-06WebAssembly cuts load time by more than two thirds FG20
  7. 2018The first salesperson and first designer advocate start the same day FG18
  8. 2019-01Organization plan, built with beta customers FG5
  9. 2019-08Plugins with discovery inside the product FG9
  10. 2021-04FigJam, built from observed brainstorming in design files FG11
  11. 2022-09Adobe agrees to buy Figma for about $20B R1
  12. 2023$505M revenue Full year FG7
  13. 2023-11Dev Mode for developers; the UK CMA records collaboration value and migration costs FG13 FG8
  14. 2023-12Independent after Adobe and Figma end the deal FG14
  15. 2024$749M revenue Full year, +48% year over year; net dollar retention 134% FG7
  16. 2025-03$228M revenue First quarter, +46% year over year; about 450,000 paid customers FG7
  17. 2025-07IPO at $33 a share Listed on the NYSE as FIG R3

Sources

Oldest first.

  1. FG16 Design Together. John Lilly / Greylock · 2015-12-02 Investor analysis
  2. FG1 Design: Meet the internet. Dylan Field / Figma · 2015-12-03 Primary source
  3. FG19 Building a professional design tool on the web. Evan Wallace / Figma · 2015-12-03 Engineering post
  4. FG2 Multiplayer Editing in Figma. Evan Wallace / Figma · 2016-09-28 Primary source
  5. FG23 Figma now lets interface designers collaborate on projects. Anna Escher / TechCrunch · 2016-09-28 Contemporaneous trade report
  6. FG20 WebAssembly cut Figma's load time by 3x. Evan Wallace / Figma · 2017-06-08 Engineering post
  7. FG3 My switch to Figma. Sean Rice · 2018-06-11 Primary source
  8. FG5 Introducing Figma Organization: our first enterprise-grade offering. Dylan Field / Figma · 2019-01-29 Primary source
  9. FG4 Figma Partnership: Creativity, Collaboration, and Conviction. Andrew Reed / Sequoia Capital · 2019-02-14 Investor analysis
  10. FG10 Behind the Plugins: Jackie Chui, UX Designer @ Microsoft. Morgan Kennedy interviews Jackie Chui / Figma · 2019-07-31 Primary source
  11. FG9 Automate work. Bring in real data. Extend what’s possible with Figma Plugins.. Sho Kuwamoto / Figma · 2019-08-01 Primary source
  12. FG21 How Figma's multiplayer technology works. Evan Wallace / Figma · 2019-10-16 Engineering post
  13. FG22 Why Figma wins. Kevin Kwok · 2020-06-19 Investor-side analysis
  14. FG25 Figma CEO Dylan Field discusses fundraising, hiring and marketing in stealth mode. TechCrunch · 2020-08-20 Founder interview
  15. FG15 Accessible Design for a Remote World: In Conversation w/Dylan Field of Figma. South Park Commons / Dylan Field · 2021-03-25 Founder interview excerpts
  16. FG11 Introducing FigJam. Yuhki Yamashita / Figma · 2021-04-21 Primary source
  17. FG17 The 5 phases of Figma's community-led growth: from stealth to enterprise. First Round Review (Claire Butler) · 2022-09-01 Operator interview
  18. R1 Adobe to Acquire Figma. Adobe · 2022-09-15 Primary source
  19. FG24 Designers hated Figma at first, but grew to love it. Ron Miller / TechCrunch · 2023-06-25 Trade report with participant interviews
  20. FG18 An inside look at Figma's unique GTM motion: Claire Butler (Lenny's Podcast transcript). Lenny Rachitsky / Lenny's Podcast · 2023-09-07 Podcast transcript
  21. FG13 Dev Mode: Building a design tool that works harder for developers. Alia Fite / Figma · 2023-11-22 Primary source
  22. FG8 Adobe / Figma merger inquiry: provisional findings. UK Competition and Markets Authority · 2023-11-28 Primary source
  23. R2 Adobe / Figma merger inquiry: provisional findings. UK Competition and Markets Authority · 2023-11-30 Regulator customer questionnaire and market investigation
  24. FG14 Adobe and Figma Mutually Agree to Terminate Merger Agreement. Adobe and Figma · 2023-12-18 Primary source
  25. FG28 7 moments that shaped Figma, as told by Dylan Field. Figma (How I Built This excerpts) · 2025-06 Founder interview excerpts
  26. FG7 Form S-1, filed July 1, 2025. Figma / SEC · 2025-07-01 Primary source
  27. R3 Figma Announces Pricing of Initial Public Offering. Figma / Business Wire · 2025-07-30 Primary source
  28. FG26 Figma goes public: thirteen unforgettable years with Dylan Field. Danny Rimer / Index Ventures · 2025-07-31 Board member essay
  29. FG27 Why Index's Danny Rimer bet on Figma and Dylan Field at the seed stage. Allie Garfinkle / Fortune · 2025-08-01 Trade report with investor interview
  30. FG12 Lessons in Product Scaling and Storytelling from Figma’s CPO. First Round Review interviews Yuhki Yamashita · Undated; observed 2026-09-25 Operator interview and editorial analysis
  31. FG6 Inside Figma’s early days: How to build a world-class sales org. Brett Berson interviews Kyle Parrish / First Round · Undated; observed 2026-09-25 Operator interview transcript