In September 2022, Adobe announced it would acquire Figma for $20 billion. Figma's annual recurring revenue at the time was approximately $400M, putting the deal at roughly 50x ARR. The acquisition fell apart in December 2023 after regulatory pushback, but the price tag told the story: Figma had won the design tool market so decisively that Adobe, with Photoshop, Illustrator, and XD in its portfolio, decided buying was easier than competing.
By 2024, Figma had over 4 million paying users, was generating north of $600M in ARR, and held an estimated 80%+ market share in collaborative UI design. The company that was dismissed as "Google Docs for design" had become the default tool for product teams worldwide.
Here is how they did it.
Company Context
Figma was founded in 2012 by Dylan Field and Evan Wallace. Field was 20 years old at the time, having dropped out of Brown University after receiving a Thiel Fellowship. Wallace brought deep technical expertise in browser-based graphics rendering, having built a WebGL-powered image editor as his thesis project.
The company spent four years in development before launching its first public version in September 2016. During that time, Sketch had established itself as the dominant UI design tool by displacing Adobe's tools with a lighter, Mac-native alternative. Figma entered the market as an underdog challenging an incumbent that had already beaten a larger incumbent.
Figma raised a $14M Series A in 2015, a $25M Series B in 2018, a $50M Series C in 2020 (at a $2B valuation), and a $200M Series D in 2021 (at $10B). The valuation doubled to $20B in the Adobe acquisition offer just one year later.
The Growth Strategy
The Browser-First Bet
Figma's foundational strategic decision was to build entirely in the browser using WebGL and WebAssembly. In 2012, this was considered risky. Native desktop applications were faster, more capable, and what professional designers expected. Sketch was Mac-native and that was seen as an advantage.
Field and Wallace bet that browser technology would improve fast enough to close the performance gap, and that the benefits of browser-based delivery would outweigh the initial limitations. Those benefits turned out to be substantial:
- Zero installation friction. Anyone with a link could open a Figma file. Designers, developers, product managers, executives. No download. No license check. No OS requirement.
- Real-time collaboration. Because everything was in the browser, Figma could build Google Docs-style multiplayer editing from day one. Multiple people could work on the same file simultaneously, with live cursors showing who was doing what.
- Cross-platform by default. Sketch only ran on macOS. Figma ran on any device with a browser. This was critical for teams where developers used Linux or Windows machines.
- Always up to date. No version conflicts. No "which version of the file is the latest?" The file was always live, always current.
The collaboration angle was the wedge. Designers did not switch to Figma because it had better drawing tools (early Figma was arguably worse than Sketch at raw design capabilities). They switched because sharing designs with non-designers went from a painful export-and-email process to "here is a link." That shift in workflow was more valuable than any feature.
Multiplayer as a Moat
Real-time collaboration sounds like a feature. In practice, it was a structural advantage that reshaped how design teams worked. Before Figma, design was a solitary activity. One designer worked on a file, exported it, uploaded it to InVision or Zeplin, and waited for feedback. Figma made design a team sport.
The multiplayer model created several growth dynamics:
More stakeholders in the tool meant more seats sold. When design was a solo activity, one Sketch license per designer was sufficient. In Figma, product managers opened files to leave comments. Engineers opened files to inspect specs. Executives opened files to review progress. Each of those users became a potential paid seat.
Network effects within organizations. Once one team used Figma, adjacent teams adopted it because shared files were easier to work with than cross-tool handoffs. This is the classic product-led growth pattern: usage spreads laterally through an organization without top-down mandates.
Switching costs increased with adoption. A company with 5 designers using Figma could switch tools. A company with 50 designers, 100 engineers, and 30 PMs all working in shared Figma files could not switch without massive workflow disruption.
By 2023, the average Figma customer had roughly 3x more seats than a comparable Sketch customer, according to industry estimates. More users per account means higher ACV and stronger retention.
Freemium for Individuals, Paid for Teams
Figma's free tier was generous and strategic. Individual users could create up to three projects with unlimited files. Students and educators got free access. This meant every design student was learning on Figma, creating a generational lock-in that Sketch and Adobe never matched.
The free tier served two purposes. First, it removed all barriers to trial. A designer curious about Figma could start using it immediately without a purchase order, a manager's approval, or a credit card. Second, it created a massive base of individual users who would later bring Figma into their workplaces.
The conversion path was predictable: a designer uses Figma for personal projects, brings it to work for a team project, the team sees the collaboration benefits, someone upgrades to the Professional plan at $15/editor/month. Enterprise features (SSO, org-wide libraries, analytics) drove further expansion at $45/editor/month.
This bottoms-up motion is what made Figma's growth so capital-efficient. By the time a sales conversation happened, the product was already in use. Sales did not have to convince anyone that Figma was good. They just had to help procurement standardize what was already happening organically. For a deeper look at how this freemium model drives growth, the conversion mechanics are worth studying.
The Developer and Plugin Ecosystem
Figma launched its plugin API in August 2019. Within six months, the community had built over 1,000 plugins. By 2024, the plugin directory had over 5,000 plugins covering everything from accessibility checks to data population to animation export.
The plugin ecosystem accomplished three things:
Extended Figma's capabilities without engineering cost. Instead of building every niche feature internally, Figma let the community fill gaps. Need to import icons from a specific library? There is a plugin. Need to generate realistic dummy data? Plugin. Need to check color contrast ratios? Plugin.
Created switching costs. Teams that built custom plugins for their design systems, or relied on specific third-party plugins in their workflow, had another reason not to switch tools.
Attracted developers to the platform. Designers were Figma's primary users, but developers who built plugins became invested in the ecosystem. Some built businesses around Figma plugins. That investment deepened the platform moat.
Figma also invested in developer-facing features like Dev Mode (launched 2023), which gave engineers a dedicated interface for inspecting designs, extracting CSS, and understanding component properties. This expanded the addressable market from designers to the entire product development team.
Config as a Growth Channel
Figma launched Config, its annual user conference, in 2020. The first edition was virtual (pandemic timing). By Config 2023, the event drew over 10,000 in-person attendees in San Francisco plus hundreds of thousands of virtual viewers.
Config served as both a product launch platform and a community celebration. Major feature announcements (Variables, Dev Mode, AI features) happened at Config, generating press coverage and social media activity that no ad campaign could match. The event also reinforced Figma's identity as a community-driven company, not just a tool vendor.
The conference playbook is well-established in enterprise software (Salesforce's Dreamforce, Atlassian's Team, Apple's WWDC), but Figma executed it at a scale unusual for a company its size. Config became a cultural moment for the design community, which reinforced Figma's position as the default tool of the profession.
Metrics That Mattered
Figma's publicly available metrics tell the story of a company that found product-market fit and then expanded aggressively:
- ARR: Approximately $400M at the time of the Adobe deal (September 2022), growing to an estimated $600M+ by late 2024.
- Paying users: Over 4 million by 2024, up from roughly 1 million in 2020.
- Market share: Estimated 80%+ of the collaborative UI design tool market by 2024, based on surveys by UXTools.co and other industry sources.
- Net revenue retention: Reported to be above 150% at the time of the Adobe acquisition, driven by seat expansion within existing accounts.
- Free users: Tens of millions of free users, including students and individual designers, forming the top of the conversion funnel.
These numbers illustrate a business where the core PLG flywheel was working. Free users converted to paid. Paid teams expanded. Enterprise deals locked in large accounts. For more on how PLG compares to sales-led models, the structural differences in growth mechanics are significant.
What Product Teams Can Learn
Make a technology bet that changes the competitive frame. Figma did not try to build a better Sketch. They bet on browser-based delivery, which changed the comparison from "design features" to "collaboration workflow." The lesson is not "build in the browser." It is "find the technology shift that makes your competitor's advantage irrelevant." When planning your product strategy, ask what technology bet would reframe your market.
Expand the user base beyond the primary buyer. Sketch sold to designers. Figma sold to everyone who touches design: designers, developers, PMs, executives. Each additional user type increased the value of the product (more collaboration) and the size of the contract (more seats). If your product is used by one role, ask whether adjacent roles would benefit from access.
Free tiers should create advocates, not just trials. Figma's free tier was not a 14-day trial with a countdown timer. It was a genuinely useful product for individuals. Those individuals became advocates who brought Figma into their organizations. The best free tiers create users who actively sell the product to their teams.
Ecosystems compound value. Figma's plugin directory and community files made the product more valuable in ways Figma did not have to build itself. Every plugin deepened switching costs. Every shared design system file made the community stickier. If you are not thinking about how external contributors can extend your product, you are missing a growth lever. The RICE framework can help you prioritize which ecosystem investments to make first.
Conferences are worth the investment. Config is expensive to produce. But the combination of product launches, community energy, and press coverage generates awareness that compounds over the full year. If you have a passionate user base, a well-run conference is one of the highest-ROI marketing investments you can make.
Win the next generation. Figma's free access for students meant that an entire generation of designers learned their craft in Figma. When those students entered the workforce, they brought Figma with them. If your product has an education or training angle, making it free for students is an investment in future market share that pays off over years, not quarters.