Claire Butler (first GTM hire)07 September 2023

An inside look at Figma’s unique GTM motion

10Frameworks

15Insights

Episode overview

Claire Butler recounts joining Figma as its tenth employee and first marketing hire, launching the product from stealth, and helping shape its positioning and go-to-market motion. She describes a two-part bottom-up strategy: earn deep love from individual practitioners, then equip those internal champions to spread Figma through their organizations. The discussion grounds that strategy in technical content, direct customer support, designer advocates, a generous sharing model, design systems, community events, and sustained transparency.

Key ideas

Figma's bottom-up growth model began by making individual contributors love the product, then relied on them to champion adoption inside their companies.
Early product-market-fit signal came from intense user behavior and qualitative evidence—such as designers taking the demo laptop—rather than small-sample optimization metrics.
Credibility with designers came from detailed technical content authored with designers and engineers, not conventional marketing language.
Figma built alongside early users through direct support, immediate debugging, and deliberately unscalable actions such as fixing an early customer's MacBook in person.
Twitter provided an existing design-community distribution channel where Figma could request feedback, share technical work, and maintain relationships over time.
Removing collaboration limits from the free tier made sharing easier and protected the product's core growth loop.
Designer advocates supplied the 'Tom Factor': practitioner credibility across marketing, sales, customer feedback, and product development.
Figma turned design systems from an adoption blocker into an enterprise upgrade driver while continuing to protect its bottom-up motion as it scaled.

Transcript available · source text is retained privately and is not published

Frameworks in this episode

Strategy4 steps

Packaging for Spread, Not for Revenue

Never gate the mechanism that grows you: limit files, not collaborators; charge editors, not viewers.

Read →

Strategy5 steps

Signal Over Metrics (Pre-PMF Decision Rule)

You cannot optimize your way to product-market fit — hunt for pull, not conversion lifts.

Read →

Strategy5 steps

The Bottom-Up Fit Checklist

Four market conditions plus one leadership condition that decide whether an IC-led motion will work.

Read →

Influence4 steps

The Champion Amplification Flywheel

Grow your internal champions' careers, and their credibility becomes your credibility.

Read →

Marketing4 steps

The Community Node-Graph Channel Strategy

Map the influence graph of an existing community, then go to its centres — for feedback, not a pitch.

Read →

Marketing4 steps

The Four Keys to IC Love

Credibility, build-with-users, go where they already are, and radical transparency.

Read →

Marketing4 steps

The 'If I Could Have Written It' Content Bar

A one-question filter for whether technical content will earn credibility or be ignored.

Read →

Sales5 steps

The Practitioner Advocate Role (The Tom Factor)

Hire a passionate user from your community into marketing and sales — no quota, no CRM.

Read →

Marketing5 steps

The Two-Step Bottom-Up GTM Motion

Make individual contributors love you, then arm them to spread you inside their company.

Read →

Strategy4 steps

Turn Your Biggest Blocker Into Your Upgrade Wedge

Find the single thing stopping adoption, go deeper on it than anyone, and make it the reason to upgrade.

Read →

People & resources mentioned

Attributed to the moment in the episode. Timestamps are approximate.

People · 11

Lenny RachitskyMentionstoday we've got another very special compilation episode something I've been pulling on more and more with the podcast and the newsletter
“today my guest is Claire Butler”
▶ Watch at ~1:00approx.
Claire ButlerMentionsClaire started at figma while they were still in stealth as their 10th employee and their first ever marketing hire
“today my guest is Claire Butler”
▶ Watch at ~1:00approx.
Danny RimerMentionsI got introduced to Dylan via um index they were an investor at the last company I was at and Danny Rymer specifically
“I got introduced to Dylan via um index they were an investor at the last company I was at and Danny Rymer specifically”
▶ Watch at ~11:00approx.
John LillyMentionsI also met John Lily I didn't know who he was I had to Google him but uh he seemed really smart
“I also met John Lily I didn't know who he was I had to Google him but uh he seemed really smart”
▶ Watch at ~11:30approx.
Brad FrostMentionsmentioned
“and then I went and read a pattern way of thinking and atomic Brad Frost atomic structures Design Systems”
▶ Watch at ~13:00approx.
Evan WallaceMentionswe talked to Evan our CTO and knew it would take about another year for him to build it
“we talked to Evan our CTO and knew it would take about another year for him to build it”
▶ Watch at ~20:30approx.
Sho KuwamotoMentionsthe customer Obsession that we have the the care of especially that editor tool
“I know you had show in your podcast and he talked a lot about this too”
▶ Watch at ~31:00approx.
Josef Müller-BrockmannMentionsmentioned
“we went really deep on Joseph Mueller Brockman um and his influence on grids”
▶ Watch at ~34:00approx.
Dylan FieldMentionsthat's something Dylan's really good out is trusting his intuition and gut
“Dylan really identified immediately that Twitter was the place where that existed”
▶ Watch at ~45:00approx.
Tom LowryMentionsTom he brought he was the internal champion at his company who got his company to adopt figma
“Tom he brought he was the internal champion at his company who got his company to adopt figma”
▶ Watch at ~1:08:00approx.
Noah WeissMentionsNoah is Chief product officer at slack where he spent the last seven years
“right before I went on Pat I had Noah Weiss on the podcast”
▶ Watch at ~1:30:00approx.

Resources · 33

Lenny's PodcastCoinedpodcast · Lenny Rachitsky
“welcome to Lenny's podcast where I interview worldclass product leaders and growth experts”
▶ Watch at ~0:30approx.
SummitMentionsproduct · Figma
“the product design tool right was going to be Summit”
▶ Watch at ~5:00approx.
GreylockUsescompany
“I remember Greylock was helpful at least over there”
▶ Watch at ~9:00approx.
Google DocsUsessoftware · Google
“I use Google Docs I use AA I use all these online tools”
▶ Watch at ~10:30approx.
Index VenturesMentionscompany
“I got introduced to Dylan via um index they were an investor at the last company I was at”
▶ Watch at ~11:00approx.
MicrosoftMentionscompany · Bill Gates and Paul Allen
“our first meeting with Microsoft actually came and this is the scrappiness of working in an early stage startup”
▶ Watch at ~25:00approx.
XamarinUsescompany
“it was zamarin they were the ones who were using figma first”
▶ Watch at ~26:00approx.
AirbnbUsescompany · Brian Chesky, Joe Gebbia, and Nathan Blecharczyk
“I remember spreading at Airbnb early on I think it was when airb be was one of the early customers”
▶ Watch at ~29:00approx.
SketchUsessoftware · Sketch B.V.
“God damn it we just switched to sketch or we going to switch again”
▶ Watch at ~29:00approx.
PhotoshopMentionssoftware · Adobe
“I used sketch I was maybe in Photoshop before that”
▶ Watch at ~30:30approx.
WebGLUsessoftware · Khronos Group
“it was the first time like used video game technology webgl”
▶ Watch at ~33:00approx.
Hacker NewsUseswebsite · Y Combinator
“I got him to like make technical content and that I think went to number one on Hecker news”
▶ Watch at ~33:30approx.
Designer NewsUseswebsite
“we tried to get at designer news at the time Twitter”
▶ Watch at ~37:00approx.
CodaUsessoftware · Coda
“we had Koda they were our first user and they were based in paloalto”
▶ Watch at ~38:00approx.
IntercomUsescompany · Intercom
“I remember we implemented intercom back in the early days”
▶ Watch at ~39:00approx.
TwitterUseswebsite · Twitter
“we really went all in on Twitter that really became a key like our channel that we focused on”
▶ Watch at ~45:30approx.
AWSMentionscompany · Amazon
“an AWS cluster went down and we couldn't we didn't know what was going on”
▶ Watch at ~54:30approx.
ConfigCoinedevent · Figma
“I remember I happily talk about config the way that we do config”
▶ Watch at ~58:30approx.
Dev ModeMentionssoftware · Figma
“we just launched variables in Dev mode back in at confi this year”
▶ Watch at ~1:06:30approx.
designsystems.comCoinedwebsite · Figma
“we have design systems.com it's like a figma property”
▶ Watch at ~1:14:00approx.
SchemaCoinedevent · Figma
“we had a whole conference around it in the fall called schema”
▶ Watch at ~1:14:00approx.
Dare to LeadRecommendsbook · Brené Brown
“radical cander and dare to lead I to be honest are the ones I recommend the most”
▶ Watch at ~1:25:30approx.
Radical CandorRecommendsbook · Kim Scott
“radical cander and dare to lead I to be honest are the ones I recommend the most”
▶ Watch at ~1:25:30approx.
NazaréMentionsplace
“it's Nazar and Portugal and all of the the waves and the surfing culture that's grown there”
▶ Watch at ~1:26:00approx.
PortugalMentionsplace
“I'm going to Portugal next week and that's a place where they have like the biggest waves in the world”
▶ Watch at ~1:26:00approx.
100 Foot WaveRecommendsdocumentary
“so I just watched 100 foot wave on HBO”
▶ Watch at ~1:26:00approx.
HBOUsescompany
“so I just watched 100 foot wave on HBO”
▶ Watch at ~1:26:00approx.
FigJamUsessoftware · Figma, Inc.
“I spend all of my day in fig Jam like literally all of my day”
▶ Watch at ~1:26:30approx.
FigmaUsessoftware · Figma
“I was using figma for a long time”
▶ Watch at ~1:27:00approx.
Atomic HabitsMentionsbook · James Clear
“kind of maybe it's more like Atomic habits or things like that”
▶ Watch at ~1:28:00approx.
PinterestUsescompany · Pinterest
“I start with pinest like get ideas but then I pull them all like a mood board on fig jam”
▶ Watch at ~1:29:00approx.
Apple PodcastsMentionssoftware · Apple Inc.
“you can subscribe to the show on Apple podcast Spotify or your favorite podcast app”
▶ Watch at ~1:31:00approx.
SpotifyMentionssoftware · Spotify
“you can subscribe to the show on Apple podcast Spotify or your favorite podcast app”
▶ Watch at ~1:31:00approx.

Spot an error or want something removed? Request a correction or removal.

Insights & moments

The myth-busts, hot takes, explainers, and tools worth keeping.

Myth Buster· 1

Myth Buster32:00

Designers Don't Want to Hear From Marketers

As Figma's first marketer, Claire learned designers have a high BS meter and reject traditional product-marketing buzzwords like 'efficiency' and 'collaboration'. They want technical features explained deeply. So she deliberately stopped marketing, publishing deep technical content from the engineering and design teams to build authentic credibility.

Designers reject buzzwords and traditional product marketing
They want to understand how technical features work, then infer the benefits
Claire's counterintuitive move was to 'not market' to build authenticity
Technical content (e.g. a WebGL post) hit number one on Hacker News

“designers don't want to hear from marketers they don't want to be marketed to”
Claire Butler · 32:00

“one of the things that I did was really try to like not market and that's so funny as a marketer to say that but…”
Claire Butler · 32:30

#marketing#credibility#technical-audience#figma

Hot Take· 2

Hot Take23:00

You Can't Optimize Your Way to Product-Market Fit

Claire offers a contrarian view on early-stage measurement: numbers are so small that metrics can't tell you if something is working. A 5% email improvement is meaningless; signal (a few people who genuinely love it) matters far more than optimized conversion rates. Founders have to trust intuition and hunt for anecdotal signal instead.

At tiny scale, hard metrics are unreliable and can mislead
Optimizing a landing page or email by a few percent doesn't reveal whether the product works
Signal, a couple of people who'd love it, beats marginal metric improvements
Early stage requires trusting intuition and finding anecdotal evidence

“you can't optimize your way to product Market fit right”
Claire Butler · 23:30

“signal is actually way more important like can you get a couple people who'd love it”
Claire Butler · 23:30

#metrics#product-market-fit#early-stage

Hot Take41:00

Why Users Have to Love You, Not Just Use You

Claire explains why 'love' is the deliberately high bar. Bringing a tool to your organization or community means putting your own social capital and reputation on the line, and people won't do that unless they truly believe in it. Mere usage never converts someone from user to champion; only passion drives the spread.

Championing a tool internally means taking a personal reputational risk
People won't spread something unless they genuinely believe in it
Usage alone doesn't move someone from user to champion
Love is what creates the scalability and spread

“you just don't get the scalability and spread of someone doing this like doing this for you unless they they have that level of of…”
Claire Butler · 42:00

#product-love#internal-champions#bottoms-up

Explainer· 2

Explainer1:07:30

The 'Tom Factor': Why Deals Closed When a Designer Advocate Joined

Figma's first salesperson and a designer advocate (Tom Lowry) started the same day. Tom had been an internal champion who brought Figma to his own company, so he understood designers' problems deeply. He'd join sales calls, without a quota or sitting on the sales team, and deals became far more likely to close, so much so that the team named it 'the Tom Factor'.

The first salesperson and designer advocate started on the same day by design
Tom was a former internal champion and deep technical expert, never a quota-carrying salesperson
He explained the product to other designers with credibility sales reps couldn't match
Deals were far more likely to close when he joined, which the team dubbed 'the Tom Factor'

“they called it the Tom Factor because he was so powerful and their deals so much like more likely to close if he joined um…”
Claire Butler · 1:09:30

#sales#developer-advocacy#credibility#figma

Explainer1:10:30

Turning Design Systems From Biggest Blocker Into Biggest Reason to Upgrade

Design systems (shared libraries of reusable components) were Figma's biggest adoption blocker for large companies, who said they couldn't work without them. Instead of avoiding it, Figma leaned in, running meetups, building features, and creating properties like designsystems.com and the Schema conference. Design systems became a main reason companies upgrade from Pro to Org/Enterprise, and design-systems people became the key internal champions.

Design systems let teams reuse predefined components (buttons, headers) consistently and efficiently
Lacking shareable design systems was Figma's biggest blocker with big companies
Figma leaned in with meetups, features, designsystems.com, and the Schema conference
Design systems became a top reason to upgrade to Org/Enterprise, and their owners became champions or blockers

“Design Systems are one of the main reasons you upgrade from prot org or Enterprise”
Claire Butler · 1:14:00

“they're either the biggest blockers or the biggest Champions depending on if you can win them over”
Claire Butler · 1:14:30

#design-systems#enterprise#adoption#figma

Story· 6

Story04:30

How Claire Killed the 'Summit' Product Name on Day One

On her literal first day at Figma, Claire discovered the design tool was going to be branded 'Summit' while the company was 'Figma'. She argued you can't build brand equity across two names, was told to make a presentation, gave it the next day, and the name was killed. It illustrates how fast decisions moved and how much ownership early employees had.

The product design tool was originally going to be named 'Summit', separate from the company name Figma
Claire argued two brands can't both accrue equity and 'Summit' wasn't ownable
Dylan responded by asking her to present the case to everyone the next day
The name was killed on day two and the product became Figma

“we cannot name this thing Summit that's not going to work we can't have two Brands summit's not ownable like we can't build equity”
Claire Butler · 05:00

“andan said to me he was like oh that's interesting how about you make a presentation and present it to everyone tomorrow”
Claire Butler · 05:30

#branding#figma#naming#early-days

Story38:00

Driving to Palo Alto to Fix a Customer's MacBook

Figma's first user, Koda, said yes to using the tool full-time, a huge milestone. Then the designer texted that his engineer Philip couldn't open the file, so they couldn't use it. Dylan told everyone to drop everything; the servers were fine, the problem was Philip's MacBook, so Dylan drove engineer Evan down to Palo Alto to fix the laptop just to keep the customer.

Koda was Figma's first user; designer Jeremy agreed to adopt the tool full-time
The whole deal nearly collapsed because one engineer's MacBook couldn't open the file
Dylan drove Evan to Palo Alto to physically fix the laptop and retain the user
A textbook example of doing things that don't scale to land the first customer

“D was like everybody drop everything we have to fix this”
Claire Butler · 38:30

“Evan down had a car so Dylan had to drive Evan down the palto to fix the MacBook of phip just to get them to…”
Claire Butler · 39:00

#product-market-fit#customer-obsession#figma#doesnt-scale

Story25:00

Sliding Into DMs to Land the First Microsoft Meeting

Claire got Figma's first Microsoft meeting by sliding into the DMs of her friend's ex-boyfriend after spotting he'd signed up. Adoption then spread organically pocket by pocket inside Microsoft, all on credit cards with no salesperson, until Microsoft itself came asking for security, procurement, and an enterprise product so they could control and pay for it.

The first Microsoft contact came from DMing a friend's ex-boyfriend who had signed up
The Xamarin team was 'patient zero' at Microsoft; usage spread across pockets on credit cards
Figma never went through Microsoft procurement or security to start
Microsoft eventually asked to pay and demanded an enterprise product to regain control

“I uh slid into the DMS of my friend's ex-boyfriend that's how we got our first meeting with Microsoft”
Claire Butler · 25:30

“Microsoft was like wait a minute like we need to organize this know I mean like we need security we need account management we need…”
Claire Butler · 27:00

#bottoms-up#sales#scrappiness#figma

Story45:30

Dylan's Twitter Scraper That Mapped Design Influencers

Dylan built a scraper that took a few design-community influencers, mapped who followed them and the influence they had, and produced a node graph of design sub-communities (iconographers, graphic designers, product managers). Figma DMed the most influential people for feedback, not to sell, and pushed technical content into those feeds. The tool was reused years later for other product launches.

Dylan coded a scraper that built a node graph of design-community influencers and their followers
It revealed clusters by design topic and the key influencers in each
Figma DMed top influencers for product feedback, framed as feedback not sales
The tool was reused when launching later products for other audiences

“he built this tool or this SC this scraper where he identified a couple influencers in the design Community”
Claire Butler · 46:00

“we found the people who were most influential to start and that was another source back to like using whatever you can to get people…”
Claire Butler · 46:30

#twitter#community#distribution#figma

Story49:30

The Pricing Flip: Unlimited Collaborators Instead of Unlimited Files

Figma's original starter tier gave unlimited files but capped collaborators at two or three, hitting a paywall exactly where the product's growth engine lived. Realizing this hurt them, they flipped it to a few files but unlimited collaborators. The change was huge because it stopped choking the spread of the product before teams gained confidence.

The original starter team allowed unlimited files but only 2-3 collaborators
That cap throttled the exact sharing behavior that drove growth
Figma flipped it to ~3 files with unlimited collaborators
The lesson: don't introduce payment friction where your growth engine operates

“now it's like you can have something like three files but unlimited collaborators and that was huge for us”
Claire Butler · 1:02:30

#pricing#packaging#growth#freemium

Story55:30

The Acquisition Announcement: Figma's Most Stressful Day

Claire says the true most stressful day of her Figma career was announcing the acquisition, when as head of social she faced an onslaught. Their first response was just retweeting Dylan, but Rajie pushed to talk to users directly and not hide behind the brand. They held an open Twitter Space the next day where users could ask anything, which is when sentiment began to turn.

Announcing the acquisition was Claire's most stressful day, hitting her social role hardest
The initial response was a bare retweet of Dylan
Rajie insisted they talk to users directly and not hide behind the brand
An open Twitter Space with leadership answering anything helped turn sentiment

“the true most stressful day at figma for me was the day that we announced the acquisition”
Claire Butler · 55:30

“we've got to talk to our users like we just have to talk to them directly we have to show we're the same company we…”
Claire Butler · 55:30

#transparency#crisis-comms#social#figma

Tool· 2

Tool26:30

The Node-Graph Tool That Maps How Figma Spreads Inside a Company

Figma's data science team built an internal tool where you type in any organization's name and see a node graph of everyone using Figma there, including who invited whom across gen-one and gen-two users. The clusters reveal teams and internal champions, showing how one person becomes the center of a spreading cluster.

An internal data tool lets you type any org name and see a node graph of its Figma users
The graph shows invitation chains (gen one, gen two) and clusters that map to teams
It surfaces the internal champions at the center of each spreading cluster
The insight: internal champions are the key to organizational adoption

“you can type in any org any org at figma um and see what that node graph looks like but they're super interesting to see…”
Claire Butler · 28:00

#analytics#bottoms-up#internal-champions#figma

Tool52:30

'Little Big Updates': Packaging Quality Fixes Into a Launch

Figma runs engineering quality weeks where engineers fix the small annoyances users tweet about, and picks which bugs to fix. They package all those quality updates into an annual launch called Little Big Updates, often showing the tweet that prompted each fix. It's one of Figma's most popular launches because it visibly improves users' daily quality of life.

Engineering runs quality weeks to fix small, high-annoyance issues from Twitter and support
Engineers get to pick which bugs and tweets to fix, which is deeply satisfying
The fixes are bundled into an annual launch called Little Big Updates
It's among Figma's most popular launches because it improves daily quality of life

“what if we package all of those quality updates up it's one thing and launch them together”
Claire Butler · 52:30

“people are like yes I care about this this improves my quality of life every single day”
Claire Butler · 53:00

#product#craft#launches#figma

Takeaway· 2

Takeaway34:30

Hiring a Designer, Not a Marketer: Figma's 'Magic Dust'

Claire's first hire wasn't a marketer but a designer advocate pulled from Figma's user base, someone who loved the product and could represent it credibly to other designers. That designer-advocate role scaled across the company and now spans marketing, sales, and regions. Claire calls it the 'magic dust' that makes the go-to-market motion work.

The first marketing hire was a designer advocate, not a traditional marketer
The advocate came from the user base and worked full-time talking to users and creating content
The role scaled into a large team across products and regions (e.g. a Japan designer advocate)
Claire calls advocates the 'magic dust' sprinkled on go-to-market

“the first person I hired was actually a designer advocate so was not a marketer it was someone who was a designer”
Claire Butler · 34:30

“it's kind of the magic dust you call it that we sprinkle on go to market to make a lot of our go to market…”
Claire Butler · 35:30

#hiring#developer-advocacy#credibility#figma

Takeaway44:30

Go Where Your Users Already Are, and Ask for Feedback Not Sales

In the early days users won't come to your space, so Figma went to the existing design community on Twitter rather than building its own channel. The point of engaging influencers was always feedback, never selling, which ends up selling anyway. Twitter also let people passively follow Figma over time until they were confident enough to switch tools.

Early users won't come to you; go to the channel they already inhabit
The design community existed on Twitter long before Figma, so Figma went all-in there
Outreach was always about feedback, not selling, which builds trust and sells indirectly
Twitter let users passively follow along until they were ready to switch

“it allows people to passively follow you over time without having to invest in you”
Claire Butler · 48:00

“we never heard sold the product like it was always about feedback and I think that that's so key to all of this”
Claire Butler · 48:30

#distribution#twitter#community#feedback

Key ideas

Frameworks in this episode

Packaging for Spread, Not for Revenue

Signal Over Metrics (Pre-PMF Decision Rule)

The Bottom-Up Fit Checklist

The Champion Amplification Flywheel

The Community Node-Graph Channel Strategy

The Four Keys to IC Love

The 'If I Could Have Written It' Content Bar

The Practitioner Advocate Role (The Tom Factor)

The Two-Step Bottom-Up GTM Motion

Turn Your Biggest Blocker Into Your Upgrade Wedge

People & resources mentioned

People · 11

Resources · 33

Insights & moments

⚡Myth Buster· 1

Designers Don't Want to Hear From Marketers

◆Hot Take· 2

You Can't Optimize Your Way to Product-Market Fit

Why Users Have to Love You, Not Just Use You

✶Explainer· 2

The 'Tom Factor': Why Deals Closed When a Designer Advocate Joined

Turning Design Systems From Biggest Blocker Into Biggest Reason to Upgrade

❝Story· 6

How Claire Killed the 'Summit' Product Name on Day One

Driving to Palo Alto to Fix a Customer's MacBook

Sliding Into DMs to Land the First Microsoft Meeting

Dylan's Twitter Scraper That Mapped Design Influencers

The Pricing Flip: Unlimited Collaborators Instead of Unlimited Files

The Acquisition Announcement: Figma's Most Stressful Day

✦Tool· 2

The Node-Graph Tool That Maps How Figma Spreads Inside a Company

'Little Big Updates': Packaging Quality Fixes Into a Launch

▲Takeaway· 2

Hiring a Designer, Not a Marketer: Figma's 'Magic Dust'

Go Where Your Users Already Are, and Ask for Feedback Not Sales

Myth Buster· 1

Hot Take· 2

Explainer· 2

Story· 6

Tool· 2

Takeaway· 2