An inside look at Figma’s unique GTM motion | Claire Butler (first GTM hire)

Sep 7, 2023 Episode Page ↗
Overview

Claire Butler, Figma's 10th employee and first marketing hire, shares Figma's unique two-part bottom-up go-to-market strategy. She details how to get individual contributors to love your product and then enable them to spread it within their organizations.

At a Glance
33 Insights
1h 31m Duration
24 Topics
6 Concepts

Deep Dive Analysis

Early Days at Figma: High-Level Decisions vs. Grunt Work

Figma's Branding Decision: Killing the "Summit" Name

Stressful Early Days: Launching Out of Stealth

Why Claire Joined Figma: Logic, Social Proof, and Founder Conviction

Defining Figma's Bottom-Up Go-To-Market Motion

Figma's Unique Approach: Obsession with Tool Quality

Decision to Launch Out of Stealth: Prioritizing User Excitement

Early Stage Metrics: Prioritizing Signal Over Hard Numbers

Figma's Organic Spread: Winning Over Microsoft

Four Pillars to Make ICs Love Your Product

Building Credibility with Technical Content and Designer Advocates

Customer Obsession: Building Product Directly with Early Users

Why User Love is Crucial for Product Spread

Leveraging Twitter for Community Engagement and Feedback

Maintaining Transparency and Authenticity at Scale (Downtime, Acquisition)

Scaling GTM: Little Big Updates and Designer Advocates

Scaling Community Engagement with Config Conference

Four Pillars to Spread Product Within Organizations

Figma's Freemium Strategy and Pricing Tiers

Designer Advocates: The "Tom Factor" in Sales

Design Systems: Turning a Blocker into an Adoption Driver

Nurturing Internal Champions for Continued Growth

Prerequisites for Successful Bottom-Up GTM

Summary of Figma's Bottom-Up GTM Model

Bottom-Up Go-To-Market Motion

This strategy focuses on individual contributors (ICs) loving a product, then enabling them to spread it within their organizations, which eventually leads to revenue. It contrasts with top-down approaches that target executive buyers directly.

Designer Advocate

A role at Figma, often filled by former product designers, dedicated to meeting with users, creating content, and bringing feedback back to the product team. These advocates bridge the technical product and user community, building credibility and driving adoption.

The Tom Factor

An internal term at Figma referring to the significant positive impact a designer advocate (Tom Lowry) had on sales deals. His deep product understanding and ability to explain technical aspects to other designers made deals more likely to close.

Little Big Updates

An annual launch at Figma where engineering teams fix numerous small, user-reported bugs and make quality-of-life improvements. These updates are packaged and launched together, highly valued by users for improving their daily workflow.

Design Systems

A library of reusable components, guidelines, and standards that help designers and engineers build consistent products efficiently. For Figma, enabling robust design systems became a key feature for large organizations to adopt the product and upgrade to enterprise tiers.

Consistent Pressure Over Time

A personal motto adopted by Claire, emphasizing that sustained effort and grit are more important for long-term success than immediate accomplishments or intense short-term pressure. It's about continuous work rather than expecting instant results.

?
What is a bottom-up go-to-market motion?

It's a strategy focused on individual contributors (ICs) loving a product and then enabling them to spread it throughout their organizations, eventually leading to revenue, rather than starting with executive buyers.

?
Why is user "love" so important for product growth?

Users won't put their social capital on the line to spread a product within their organization unless they deeply believe in and love it, making "just using it" insufficient for scalable adoption.

?
How did Figma build credibility with its early technical audience?

Figma focused on producing deep technical content explaining product decisions and features, hiring designer advocates (designers themselves), and having engineers directly engage with users for feedback and support.

?
How did Figma leverage Twitter in its early growth?

Figma identified Twitter as the existing home for the design community and used a custom scraper to map influencers, engaging directly with them for feedback and pushing technical content to spur conversation.

?
How did Figma handle its pricing tiers to encourage growth?

Figma initially allowed unlimited files with limited collaborators, but switched to three files with unlimited collaborators in its free starter team, making it easier for teams to try and spread the product before hitting a paywall.

?
How did Figma turn design systems from a blocker into an advantage?

Figma engaged directly with the design systems community, built features to support advanced design systems, and created content and events around them, making it a key reason for large organizations to upgrade to enterprise tiers.

?
What types of companies are a good fit for a bottom-up GTM motion?

Companies whose products cater to a technical individual contributor audience that deeply cares about their tools, can derive value from the tool independently, and whose users have many collaboration points within their organization.

?
How does Figma maintain authenticity and transparency at scale?

Figma continues to engage directly with users through channels like Twitter, conducts public postmortems for downtime, and held open forums (like Twitter Spaces during the acquisition) to address user concerns directly and honestly.

?
How did Figma scale its "building with users" approach?

Figma implemented "Little Big Updates," an annual launch derived from "quality weeks" where engineers fix small, user-reported bugs and annoyances, often directly citing user tweets or forum requests.

1. Implement Bottom-Up GTM

Focus your go-to-market strategy on individual contributors (ICs) by building a deep relationship with them, aiming for them to “love” your product so much they become internal champions willing to spread it throughout their organizations.

2. Obsess Over Tool Quality

For technical tools, prioritize the quality and craft of the core editor/tool itself, as individual contributors who spend hours daily in the product highly value even small improvements.

3. Aim for User “Love”

Strive for users to deeply “love” your product, not just use it, because this profound passion is essential for them to become champions willing to risk their social capital to spread it within their organizations.

4. Integrate Technical Advocates

Hire “advocates” (e.g., designer advocates, developer advocates) who are technical experts and passionate users from your target audience to build credibility, gather feedback, create authentic content, and significantly boost sales deal close rates.

5. Structure Free Tier for Collaboration

Design your product’s free tier to prioritize unlimited collaboration (e.g., unlimited viewers, many collaborators on limited files) over unlimited individual features, removing friction for team adoption and enabling product spread.

6. Turn Blockers into Advantages

Identify significant blockers to product adoption (e.g., missing key features for large organizations) and strategically invest in transforming them into core features or advantages that drive upgrades and widespread organizational use.

7. Go Where Users Are

Instead of trying to attract users to your own channels, actively engage with them on platforms where your target community already congregates (e.g., Twitter for designers) to build connections and gather feedback.

8. Build Credibility with Technical Content

For technical audiences, avoid traditional marketing fluff; instead, build credibility and authenticity by focusing on deep technical content, feature explanations, and detailed insights into how the product works.

9. Building with Users: Everyone Does Support

In the early days, have everyone, including engineers and founders, directly engage with user support to quickly debug issues, gather feedback, and foster strong user relationships, making users feel invested.

10. Building with Users: Foster Ownership

Actively communicate to users when their feedback has led to product improvements, fostering a sense of ownership and strengthening their relationship with your product.

11. Building with Users: Scale with “Little Big Updates”

Implement “quality weeks” where engineers fix small, user-reported annoyances, then package and launch these “little big updates” together to demonstrate ongoing commitment to user experience and quality of life.

12. Building with Users: Empower Engineers to Pick Fixes

During quality sprints, empower engineers to choose which small bugs or annoyances to fix, allowing them to feel ownership and directly address user feedback from sources like Twitter or support.

13. Maintain Champion Relationships

Continuously nurture relationships with internal champions, addressing their concerns and supporting their success, as they remain critical for ongoing product spread and advocacy within organizations.

14. Amplify Champion Careers

Support and amplify your internal champions’ professional growth by offering opportunities like speaking at events, social media amplification, and thought leadership platforms, creating a mutually beneficial relationship.

15. Transparency: Public Postmortems

When critical issues like downtime occur, issue public postmortems that explain what happened, the technical reasons, and how it was fixed, taking full accountability to maintain user trust.

16. Transparency: Direct User Forums

In high-stakes or controversial situations, host open, direct forums (e.g., Twitter Spaces) where users can ask questions and leadership can be honest and transparent, fostering trust and turning the tide of sentiment.

17. Protect Core GTM as You Scale

As a company scales and introduces traditional top-down motions, actively advocate for and protect the core bottom-up strategies that drove initial success, ensuring they continue to thrive alongside new approaches.

18. Prioritize Signal Over Metrics (Early Stage)

In early stages, prioritize qualitative “signal” (e.g., a few users loving the product, emotional reactions) over quantitative metrics, as small numbers make metrics less reliable for determining product-market fit.

19. Launch for Momentum & Feedback

Don’t stay in stealth too long; launch to gain momentum, provide a team milestone, and gather crucial user feedback, even if a key feature is still a year away, by observing strong emotional user reactions.

20. Embrace “Do Things That Don’t Scale”

Focus intensely on acquiring and retaining the very first users, even if it requires highly manual, unscalable efforts like fixing a single user’s technical issues, to ensure their success.

21. Ensure Executive Belief in GTM

To successfully implement a bottom-up GTM, secure executive leadership who deeply believes in the approach and trusts intuition over immediate, clear metrics, especially when scaling challenges arise.

22. Prerequisites: Technical IC Audience

This bottom-up GTM model is most effective for products with a technical individual contributor (IC) audience who deeply care about their craft and can derive significant value from the tool independently.

23. Prerequisites: Leverage Existing Communities

A pre-existing, active community for your target audience (e.g., on social media) can significantly accelerate bottom-up adoption by providing a ready-made distribution channel.

24. Prerequisites: Seek Collaborative IC Roles

The bottom-up model thrives when the target individual contributor role is inherently collaborative, naturally leading them to share and spread the product within their organization.

25. Choose Startup: Logical Idea

When deciding which startup to join, ensure the basic premise of the product or company immediately and logically clicks for you.

26. Choose Startup: Trusted Social Proof

When evaluating a startup, look for social proof from people you trust, such as respected investors or former colleagues, who believe in the company.

27. Choose Startup: Impressive Founder

Consider joining a startup where you are deeply impressed by the founder’s persuasiveness, drive, and ability to overcome obstacles.

28. Unify Product & Company Branding

Consolidate branding to a single, ownable name for your product and company to build strong equity and avoid confusion, especially in early stages.

29. Make Fast Decisions with Ownership

In early startups, empower individuals with ownership to make decisions quickly and run with them, driving rapid progress and adapting to new information.

30. Trust Your Intuition as Sole Role

When you’re the sole person in a role at a startup, build confidence by trusting your intuition and just “going for it,” as external gut checks may be limited.

31. Scrappy User Acquisition

Employ highly scrappy and unconventional networking methods, like leveraging personal connections or chance encounters, to get early users and gather feedback.

32. Life Motto: Consistent Pressure

Adopt a mindset of “consistent pressure over time,” focusing on sustained effort and grit rather than immediate accomplishments, to achieve long-term goals and manage pressure.

33. Parenting Tip: Don’t Overextrapolate

As a new parent, avoid overextrapolating individual challenging moments or problems, and instead, practice letting go, recognizing that not every issue will necessarily persist.

You can't optimize your way to product market fit.

Claire Butler

Designers don't want to hear from marketers. They don't want to be marketed to. And they have an extremely high bullshit meter.

Claire Butler

You're not going to do that unless you really believe in something. And so just using it isn't enough to get someone over that stage of going from just like a user to a champion.

Claire Butler

It's all about feedback. And I think that that's so key to all of this is all about feedback.

Claire Butler

The double-edged sword of Twitter is like, you build a strong communication channel, their users, and they communicate right back to you. They're not happy.

Claire Butler

How do you not just walk away from this thing that got you to where you are as well?

Claire Butler

Figma's Two-Part Bottom-Up Go-To-Market Strategy

Claire Butler
  1. Get individual contributors (ICs) at a company to love your product.
  2. Enable them to spread the product throughout their organization.

Four Pillars to Make ICs Love Your Product

Claire Butler
  1. Build credibility, especially with technical audiences, by providing deep technical content and having technical experts (like designer advocates) engage directly.
  2. Build the product with your users by actively listening to feedback, even for single users, and having engineers directly address bugs and requests.
  3. Find a channel where your target audience already exists (e.g., Twitter for designers) to build relationships over time without requiring immediate product investment.
  4. Be extremely transparent and honest with users to build trust and authenticity, especially during difficult times like downtime or major company announcements.

Four Pillars to Spread Product Within Organizations

Claire Butler
  1. Make it easy to try and share the tool without significant gates, such as offering a robust free tier with unlimited collaborators for a limited number of files.
  2. Integrate designer advocates (DAs) into the sales process to leverage their deep product understanding and credibility with technical users, significantly increasing deal close rates.
  3. Identify and address operational blockers to adoption, such as the need for robust design systems, and turn them into key reasons for upgrading and spreading the product.
  4. Maintain and grow connections with internal champions over time, helping them grow their careers and profiles (e.g., speaking at events, social amplification) beyond just tool usage.
10th employee
Figma's employee count when Claire Butler joined Claire Butler was the first marketing hire.
3-4 years
Figma's time in stealth mode Started in 2012, launched end of 2015.
About 1 year
Time it took to build multiplayer after Figma's initial launch Multiplayer was a core differentiator but not available at launch.
3 files
Figma's free tier file limit (after change) Allows unlimited collaborators, changed from unlimited files with limited collaborators.
$12 a month
Figma's Pro tier monthly cost Allows users to avoid moving files in and out of drafts.