Key Moments
An inside look at Figma’s unique GTM motion | Claire Butler (first GTM hire)
Lenny's PodcastKey Moments
Figma's unique go-to-market motion focuses on individual contributors, driving adoption through organic spread within organizations, rather than traditional top-down sales.
Key Insights
Figma's co-founder Dylan actively developed a scraper to map the design community on Twitter, identifying influential individuals to engage for product feedback.
Figma intentionally delayed charging for its product, offering a robust free tier to allow teams to build advocacy and confidence before needing to upgrade.
The company hired its first 'Designer Advocate' (DA) on the same day as its first salesperson, integrating deep product understanding into the sales process.
Figma's 'Little Big Updates' launches annually, packaging numerous small, user-requested quality improvements into a single, highly popular event.
A key differentiator historically was charging for 'editors' but not 'viewers,' allowing free collaboration and wider organic spread within organizations.
Internal champions are crucial; Figma actively helps them grow their careers by amplifying their expertise through events and social channels, reinforcing credibility.
From 'Summit' to Figma: Early days of rapid iteration
Claire Butler, Figma's first go-to-market hire and 10th employee, recounts the chaotic early days at Figma, including a significant branding decision made on her second day: switching the product name from 'Summit' to 'Figma'. This rapid iteration, balancing high-level strategic decisions with hands-on tasks like buying ice for the first meetup, characterized the startup's intense pace. The early team was deeply focused on user feedback, even driving to meet their first user, Kota, to resolve a technical issue. This hands-on approach, where every user's problem was critical, set the foundation for Figma's customer-centric growth.
Why Figma was the logical choice to join
When deciding to join Figma before its launch, Claire was drawn to three key factors. First, the product's premise logically clicked: design, unlike many other tools, was not yet online and collaborative, presenting an obvious inefficiency that Figma aimed to solve. Second, trusted connections, including investors from her previous company and prominent figures like John Doerr and John Lily, vouched for the company. Third, co-founder Dylan Finch was not just persuasive but demonstrated a relentless, problem-solving approach to overcoming any concerns, instilling confidence in the venture. These elements, combined with the inherent market opportunity, convinced her to join the early-stage startup.
Defining Figma's unique bottom-up go-to-market motion
Figma's go-to-market strategy is distinctly bottom-up, focusing on individual contributors (ICs), particularly designers, who are the primary practitioners using the tool. The core idea is for these users to love the product so much that they become internal champions, spreading adoption organically within their organizations. This contrasts with traditional top-down SaaS models where sales start with executive buyers. For the first three years, Figma operated without a sales team, relying on self-served revenue through individual credit card purchases. This product-led, IC-centric approach emphasizes building deep credibility and a strong relationship with users before involving sales, making the eventual upsell conversations much smoother and more efficient. The revenue model clicks in as these champions spearhead adoption within their companies.
Building credibility without traditional marketing
Claire highlights that designers are highly discerning and skeptical of traditional marketing. To build credibility, Figma focused on technical content and the product's inherent quality. They leveraged their engineering team to create technically deep content about how Figma's engine worked, which gained traction on platforms like Hacker News. The design team also detailed their meticulous decisions behind features like grids and vector networks, providing users with deep insights into the 'how' and 'why' of the product's construction. This approach eschewed buzzwords and focused on genuine technical merit. Later, hiring a 'Designer Advocate' who was a passionate user and designer, not a marketer, amplified this strategy, creating authentic content and representing the user voice.
Obsession with the product and building with users
A key differentiator for Figma is its deep obsession with the quality and craft of the editor itself, not just its collaborative features. This means making small improvements that significantly impact daily workflows. Building with users was paramount; the team actively listened to feedback and engaged directly. A memorable example is when the first user's engineer couldn't open a file due to a MacBook issue, requiring a Figma engineer to drive across town to fix it. This intense focus on user success, even at the cost of immediate scalability, fostered a profound sense of ownership and loyalty among early adopters. Engineers even participated in direct user support via tools like Intercom, debugging in real-time.
Leveraging community and strategic channel focus
Recognizing that early users wouldn't seek out a new brand, Figma focused on meeting them where they already were: Twitter. Dylan Finch developed a sophisticated scraper to map the design community's influence and conversation clusters. This allowed the team to engage with key influencers, distribute technical content, and foster discussions. Instead of direct selling, the focus was on soliciting feedback. This strategy built passive awareness and confidence over time, crucial for a tool requiring significant workflow shifts. The constant interaction, not just from the brand handle but from individuals on the team, humanized Figma and built a highly engaged community, providing leverage for future product launches.
Making sharing seamless and pricing strategically
Figma's growth engine relies on making it effortless for users to try and share the product. The freemium model is central, initially offering unlimited files with limited collaborators, which was later shifted to unlimited collaborators with limited files. This change was a deliberate move to facilitate organic spread, recognizing that gating collaboration too early would hinder growth. Pricing was structured to allow users to build confidence and advocacy within teams before significant financial commitment. This phased approach, from free to Pro (individual purchase) to Org (enterprise), ensures that users can gradually increase their investment as their reliance and internal championing of Figma grows. Unlimited viewers remain a key part of this strategy.
Designer Advocates and the 'Tom Factor' in sales
Designer Advocates (DAs) are central to Figma's go-to-market success, especially in sales. These individuals, often deeply passionate Figma users themselves, integrate with the sales process without being traditional salespeople. They bring unparalleled credibility and understanding of the designer's workflow, significantly aiding sales conversations. Tom Lowry, an early DA, became so instrumental that his influence was dubbed 'the Tom Factor,' making deals more likely to close. DAs synthesize user feedback, driving product improvements and serving as technical experts who can explain complex features and best practices, bridging the gap between users and the product/sales teams. This role has scaled to advocate teams for various disciplines and regions.
Design systems and operational blockers become advantages
Design systems, initially a significant blocker for enterprise adoption due to their complexity, became a strategic focus for Figma. By investing in features and content that supported creating and scaling design systems, Figma transformed a challenge into a key adoption driver and an upgrade path from Pro to enterprise tiers. They actively engaged with the nascent design systems community through meetups and dedicated resources like designsystems.com and the 'Schema' conference. This deep dive into technical aspects, demonstrating how to manage components and ensure consistency across large organizations, proved invaluable, resonating particularly with the ICs who build and maintain these systems, turning potential obstacles into powerful adoption engines.
Maintaining champion relationships and transparency at scale
Sustaining relationships with internal champions is an ongoing effort. Figma actively seeks to help these champions grow their careers by amplifying their expertise through events, social media, and thought leadership opportunities. This mutual benefit strengthens credibility for both the champion and Figma. Transparency remains a cornerstone, even at scale. Following downtime incidents, Figma opted for public post-mortems, taking accountability and explaining technical reasons and fixes. The day of the acquisition announcement was particularly stressful, but the team opted for an immediate, open Twitter Space with leaders to address user concerns directly rather than hiding behind the brand. This commitment to honesty and direct communication is core to maintaining trust.
Config and FigJam: Scaling community and product value
Figma's annual conference, Config, exemplifies scaling community engagement. It evolved from a platform for technical content and user-generated talks, sourced via calls for proposals, to a major industry event. Config amplifies the voices of practitioners and champions, fostering thought leadership and community connection by focusing on practical, technical content. Similarly, FigJam, while initially unexpected as a personal tool for home renovation planning, has become indispensable for internal strategy sessions and collaboration, demonstrating how user needs can drive new product development and adoption across diverse use cases. These initiatives reinforce Figma's commitment to providing value beyond just the core design tool.
Key prerequisites for a successful bottom-up motion
While not a one-size-fits-all approach, certain factors increase the likelihood of success for a bottom-up GTM strategy. It thrives when the target audience consists of technical individuals who deeply care about their craft and derive significant value from the tool independently. This allows for conversations centered on technical merits and workflow enhancements rather than solely on collaboration. The existence of an established community within the target audience, like the design community on Twitter, provides a pre-built distribution channel. Furthermore, the IC audience must have strong connection points within an organization, making them natural 'super spreaders' due to their collaborative roles across departments. Overcoming ingrained resistance to collaboration, as seen with early designers, is also critical.
Mentioned in This Episode
●Products
●Software & Apps
●Companies
●Books
●Concepts
●People Referenced
Common Questions
Figma's product was originally planned to be named 'Summit.' Claire Butler, on her first day as the 10th employee, argued successfully to drop 'Summit' and name the product 'Figma' instead, believing in the singularity and distinctiveness of one brand.
Topics
Mentioned in this video
Figma's first user company in Palo Alto, whose designer Jeremy became their first full-time user.
A sponsor of the podcast, offering security compliance solutions for fast-growing companies.
A sponsor of the podcast, providing deep insights into user behavior and funnel analysis.
An investor in Claire Butler's previous company and the one that introduced her to Dylan Field.
An early large organization that adopted Figma, starting with small pockets and eventually leading to a need for enterprise-level features and procurement.
A company Dylan Field used to meet someone in a lift who eventually became a Figma user, showcasing scrappy early user acquisition tactics.
A communication platform implemented early at Figma, which allowed engineers and team members to directly debug and get feedback from users.
A sponsor of the podcast, offering an API for transcribing and understanding speech at scale to build AI-powered audio/video features.
The primary social platform Figma leveraged in its early days to connect with the design community, share technical content, and gather feedback.
A platform Claire Butler uses to gather ideas for home renovation before transferring them to FigJam for mood boarding.
A company mentioned as a user of Assembly AI's transcription services.
Mentioned as an early customer of Figma and a company that has adopted a strategy of fewer, bigger product launches, similar to Figma's 'Little Big Updates' concept.
A fast-growing company mentioned as a client of Vanta.
A fast-growing company mentioned as a client of Vanta.
A venture capital firm that provided some assistance to Claire Butler during Figma's stressful launch phase.
A fast-growing company mentioned as a client of Vanta.
A design and prototyping platform that enables real-time collaboration. It was initially code-named 'Summit' before settling on 'Figma'. Claire Butler was the 10th employee and first marketing hire, extensively involved in its go-to-market strategy.
A company mentioned as a user of Assembly AI's transcription services.
Figma's CEO, who personally demoed the product, fixed early user issues, was instrumental in GTM strategy, and created a Twitter scraper for community engagement.
Figma's CTO, who fixed the MacBook issue for Koda and was the key person in building multiplayer.
The first marketing hire at Figma and guest on the podcast, sharing insights into Figma's go-to-market strategy.
An individual from Index Ventures who connected Claire Butler to Dylan Field.
Claire Butler's old boss, who was an executive at Index Ventures and believed in Figma.
An impressive individual who believed in Figma during its early days.
An influential designer whose work on grids was discussed in Figma's technical content, demonstrating a deep dive into design primitives.
The second Designer Advocate hired at Figma, who previously was an internal champion for Figma at his own company and became a foundational part of Figma's sales process due to his product knowledge.
An author of 'Atomic Design,' a foundational concept for Design Systems that Claire Butler studied to understand this area.
A podcast guest who shared advice about not over-extrapolating every moment during parental leave.
Claire Butler's old boss, mentioned as an adviser at Index Ventures who trusted Figma.
The original proposed name for Figma's product suite, which was rejected by Claire Butler on her first day.
A security and privacy framework supported by Vanta for compliance programs.
Video game technology used by Figma to make the design tool work on the internet, which was a significant technical feat.
A security and privacy framework supported by Vanta for compliance programs.
Cited as an example of an online collaborative tool that inspired the fundamental idea behind Figma.
A small team within Microsoft that was among the first to use Figma, acting as a 'patient zero' for its spread within the larger organization.
The video game technology used by Figma to enable design tools to work on the internet, which was a significant technical feat.
A platform where Figma's technical content, explaining how features work, reached number one, helping build credibility.
A cloud provider where a cluster went down, causing Figma downtime and leading to a public postmortem to maintain transparency.
A Figma property focused on content and resources related to Design Systems.
Mentioned as an example of a product that is useless on its own, unlike Figma which provides value to individual users.
Mentioned as a general-purpose tool that a marketer might not feel deep passion for, unlike designers' passion for their tools.
Figma's online whiteboard tool, which Claire Butler uses daily for strategies, explanations, and even home renovation mood boards.
A new feature launched by Figma that influences pricing and packaging, specifically targeting developers.
An early team member from Notion (Ivan Zhao) expressed surprise that Figma launched without multiplayer, highlighting its unique approach.
Figma's very first user, based in Palo Alto, whose initial file opening issue led to an intense effort by Dylan Field and Evan Down to ensure their successful adoption.
A web analytics service offered by Google, mentioned as a tool Mixpanel is designed to be more powerful and easier to use than.
A design tool that many designers used before Figma, making the switch to Figma a challenge due to previous transitions.
Online collaborative tool mentioned by Claire Butler as an analogy for why design tools should also be online and collaborative. (Spoken as 'AA' in transcript)
A popular forum in the early days where Figma would push technical content and where initial skepticism about collaborative design was seen.
A design tool that many designers used before Figma, making the switch to Figma a challenge due to previous transitions.
A management book recommended by Claire Butler for new managers and coaching.
A management book recommended by Claire Butler for new managers and coaching.
A book mentioned by Claire Butler as resonating with her personal motto of 'consistent pressure over time,' emphasizing long-term effort over immediate accomplishments.
More from Lenny's Podcast
View all 30 summaries
100 minWhy we’re at the beginning of the AI hardware boom | Caitlin Kalinowski (ex–OpenAI, Meta, Apple)
100 minHow Anthropic, Costco, and Patagonia all build incorruptible companies | Eric Ries
88 minAI era skills: Why cultivating agency matters more than job titles | Max Schoening (Notion)
71 minSnapchat CEO: Why distribution has become the most important moat | Evan Spiegel
Ask anything from this episode.
Save it, chat with it, and connect it to Claude or ChatGPT. Get cited answers from the actual content — and build your own knowledge base of every podcast and video you care about.
Get Started Free