EO StudioFrom $0 Ad Spend to $12.5B: The Figma StoryㅣClaire Butler & Corey Lee
At a glance
WHAT IT’S REALLY ABOUT
How Figma scaled through product-led community, not ad-driven marketing growth
- Figma’s earliest marketing work was hands-on: in-person pitches, user interviews, and rapid iteration based on direct feedback rather than dashboards.
- A key Day-One brand move was consolidating the product name to “Figma” (instead of “Summit”) to create a single, ownable identity.
- The team navigated early skepticism about collaborative, web-based design tools by holding a clear vision while building trust with respected designers and influencers.
- Community emerged organically from “all hands” support and relationship-building that turned individual users into internal champions who brought Figma into their companies and cities.
- Figma’s brand strategy is framed as product-led growth: build a loved product with users first, then scale community programs and flagship moments like Config.
IDEAS WORTH REMEMBERING
5 ideasEarly-stage GTM relies on intuition and anecdotes, not metrics dashboards.
When adoption is “zero or one team,” quantitative metrics won’t guide you; Figma used qualitative signals like whether a team fully switched and whether people were compelled to grab the laptop and try the product.
A single, ownable name can be a decisive early growth lever.
Claire’s first task was arguing against a split brand (company “Figma,” tool “Summit”) because a generic product name is hard to own and dilutes recognition—especially pre-launch.
You can launch before the ‘signature’ feature is complete—if momentum and learning are worth it.
Figma launched even though multiplayer (arguably the core differentiator) wasn’t ready for another year, choosing beta learning and user feedback over waiting for a perfect release.
Skepticism is normal; trust is earned through conversation and credibility over time.
Rather than trying to win everyone immediately, Figma kept confidence in the collaboration vision and built relationships with influential designers, using dialogue and iteration to change minds.
Doing “unscalable” support work can scale through compounding champions.
Engineers answering tickets sounds inefficient, but fast fixes (like Japanese input) create loyalty; those users then convert teams, start local communities, and spread adoption more effectively than paid campaigns.
WORDS WORTH SAVING
5 quotesAnd I remember I thought to myself, like, "This just isn't gonna work."
— Claire Butler
Metrics are so important, but I feel like sometimes when you're doing something really early and you're like, "I have to 10X this, I have to 100X this, I have to 1000X this-" ... you kinda have to go more on intuition and more on feeling, I think, and really believe that, because metrics just aren't gonna get you the answers that you're looking for.
— Claire Butler
It wasn't like we thought to ourselves, like, "Let's have a community-driven strategy." It was just, we need to listen to our users, and we need to build a product that's gonna be really useful for them, and they know what their problems are more than we do, and we need to spend time with them and, and fix their problems.
— Claire Butler
And so it sounds, like, pretty un- unscalable, right? Oh, you have your engineers sitting there answering support tickets, fixing bugs. Like, you can't do that forever. That doesn't scale. But actually, it does scale.
— Claire Butler
The story of Figma is not about ending at Figma. The story about Figma is where does Figma get that person to?
— Cory Lee
High quality AI-generated summary created from speaker-labeled transcript.
