How Figma's First GTM Hire Built a Bottom-Up Empire Without a Sales Team

Claire Butler — "An inside look at Figma's unique GTM motion" — Lenny's Podcast, UmirRfy-gzA

Claire Butler joined Figma as the tenth employee and the company's first marketing hire before the product had even launched. Eight years later, she still leads the go-to-market motion that turned a stealth-mode design tool into a multi-billion-dollar category-defining company. The defining feature of that motion? Figma operated for its first three years without a single salesperson. All revenue was self-serve. All enterprise leads came inbound from free and Pro users who loved the product enough to drag it through procurement themselves.

Butler's framework is deceptively simple: Step one, make individual contributors love your product. Step two, give them the tools and social proof to spread it inside their organization. What sits beneath that simplicity is a set of specific, often counterintuitive tactics that most B2B startups ignore.

The Two-Step Motion: IC Love First, Revenue Second

Most B2B SaaS companies default to top-down sales. They build a deck, target a VP, and hope a mandate rolls downhill. Figma did the opposite. Butler defines their motion as a true bottom-up strategy focused on practitioners — the designers who live inside the tool for eight hours a day.

"You have this core audience... they're largely individual contributors... they love you so much that they're willing to put their social capital and themselves on the line and spread the product throughout their communities."

The revenue model only clicks in when those ICs become internal champions. They spearhead adoption inside their companies, eventually hitting procurement walls and calling Figma for help. At that point, the sales conversation is not cold outreach. It is unblocking an already-committed user who is doing the selling internally.

For the first three years, Figma had no sales team. No account executives. No SDRs. Revenue came from designers and small teams putting the product on a credit card. The sales team was only introduced once the inbound volume from free-to-paid champions became impossible to ignore.

Four Rules for Making ICs Fall in Love

Butler breaks down the "get them to love you" phase into four concrete pillars. They sound like buzzwords until you hear the specifics.

1. Build Credibility Through Technical Depth, Not Marketing

Butler's first realization was that designers do not want to hear from marketers. They have an extremely high "BS meter" for words like "efficiency" and "collaboration." So Figma's early content strategy was engineered to pass the "Claire test": if she could have written it herself, it was too basic.

Instead of product marketing, Figma published deep technical essays — on vector networks, on grid systems rooted in Josef Müller-Brockmann's design philosophy, on the engineering feat of running a graphics editor in WebGL. The content was written by Figma's own designers and engineers, not marketers. The goal was not conversion optimization. It was giving practitioners a reason to keep coming back to the tool before they were ready to switch.

The first marketing-adjacent hire was not a demand-gen specialist. It was a designer advocate — a former user who represented the community, wrote technical content, and fed product insights back to the team. Butler still calls this function "magic dust."

2. Build the Product With Your Users — Literally

Figma's early customer obsession was not a Slack channel or a feedback form. It was live, human, and often absurdly scrappy. When their first full-time user, a designer at Kota, reported that an engineer could not open a file, Dylan Field declared: "Everybody drop everything." After ruling out server issues, they realized the problem was the engineer's MacBook. Evan Wallace did not have a car, so Field drove him to Palo Alto to fix the laptop in person.

The team implemented Intercom when user counts were tiny. Engineers, designers, and Butler herself would jump into live chats and debug issues in real time. Users felt ownership because they watched their feedback turn into fixes within hours.

3. Go to Where Your Users Already Are

Early-stage startups often try to pull users into their own communities. Figma went the other way. The design community already lived on Twitter, so Figma went all-in there — and only there. Dylan Field built a scraper to map the design Twitter graph, identifying influencers and cluster leaders in iconography, product design, and graphic design. The team DM'd them for feedback, not sales pitches. They pushed technical content into existing feeds. They interacted as humans, not as a brand handle.

The strategy was deliberate passivity. Users could follow Figma's journey without committing to the product, building confidence over time until they were ready to switch.

4. Be Transparent Even When It Hurts

When Figma announced its acquisition by Adobe, the social backlash was immediate and intense. Butler, who runs social, described it as the most stressful moment of her career. Rather than hiding behind corporate communications, the team held a public Twitter Space the next day with Dylan Field, Sho Kuwamoto, and others. They let users ask anything.

That same instinct showed up during outages. Figma published public postmortems, took full accountability, and promoted the technical explanations on Twitter. The transparency was not a tactic. It was a value that became harder to maintain at scale — and therefore more important to protect.

Signal Over Metrics: You Cannot Optimize Your Way to Product-Market Fit

Butler is skeptical of early-stage metrics. When user counts are in the single digits or low hundreds, a 5% lift in email conversion means nothing. Her north star was qualitative signal: Do people pull the laptop out of Dylan's hands during a demo because they want to play with it?

"You can't optimize your way to product-market fit... signal is actually way more important. Can you get a couple people who'd love it? Not like a slight improvement of a conversion of a landing page."

Figma launched without multiplayer — the feature everyone assumed was its core differentiator — because the team saw enough excitement in early demos to justify getting out of stealth. The bet was that emotion and engagement were truer signals than any funnel metric.

The "Tom Factor": Why Your First "Sales" Hire Should Not Be a Salesperson

When Figma finally built a sales team, it started on the exact same day as its next designer advocate hire: Tom Lowry, a former Figma user who had championed the product inside his own company. Tom had no sales quota, no CRM, and no script. He simply joined sales calls to explain the product to other designers from a practitioner's perspective.

The sales team started calling it "The Tom Factor." Deals were dramatically more likely to close if Tom was on the call. Not because he closed them, but because he had credibility that no salesperson could manufacture. This is why Butler argues that for technical IC audiences, advocate-led selling is not a nice-to-have. It is structural.

Today, Figma has scaled this into a full advocate team spanning designers, developers, and regional specialists. They report into GTM, but they are not measured on pipeline. They are measured on authenticity and product expertise.

The Operational Unlock: Design Systems as Enterprise Trojan Horse

The single biggest blocker to enterprise adoption was not security or procurement. It was design systems. Large companies could not adopt Figma at scale without shared component libraries that connected design to engineering. Rather than treating this as a product gap, Figma turned it into a go-to-market wedge.

They hosted meetups, built designsystems.com, launched a conference called Schema, and produced advanced technical content showing how sophisticated organizations managed components in Figma. This content targeted the exact practitioners who would later become the internal champions pushing for Org and Enterprise upgrades. Design systems became the "reason to upgrade from Pro to Org."

Pricing as a Growth Loop, Not a Paywall

Figma's freemium structure evolved specifically to avoid choking the viral loop. Initially, the free tier limited collaborators. The team realized this was backwards: it penalized sharing, which was the whole growth engine. They flipped the model to unlimited collaborators but limited files. Now a designer could invite their entire cross-functional team for free, and only hit a paywall once the workflow was deeply embedded.

The team also made viewers free. Product managers, engineers, and executives could comment and inspect without a license. This dramatically expanded surface area inside organizations and made Figma useful to more people than just the design department.

Why This Matters for Diffie

Diffie is building AI-powered browser testing for frontend engineers — a technical tool used by the same kind of craft-obsessed ICs that Figma targeted. The lesson is not to copy Figma's Twitter strategy. It is to recognize that your ICP is an individual contributor who cares deeply about their tooling, and that winning them requires credibility, not marketing.

For Diffie's GTM specifically: do not lead with ROI decks for VP Engineering. Lead with technical depth that frontend engineers respect. Publish the testing primitives, the edge cases, the craft decisions behind how Diffie handles flakiness or visual regression. Hire an advocate from your user base before you hire an SDR. Make the free tier expansive enough that an engineer can run Diffie in CI, share results with their team, and build internal momentum before procurement ever gets involved.

The outbound challenge is real, but Figma's story reframes it. Outbound does not have to mean cold emails to executives. It can mean scraping the frontend engineering graph on Twitter, DMing practitioners for feedback (not demos), and building relationships in the channels where they already hang out. Your first enterprise deal will likely come from an engineer who loved the product, put it on a credit card, and eventually needed help unblocking security — not from a top-down mandate.

Most importantly: do not hire sales until the founder can sell. Figma waited three years. If your IC users are not pulling the laptop out of your hands during demos, a salesperson will not fix that. Signal first. Scale second.