Make Individual Contributors Love You First: Inside Figma's Bottom-Up Growth Playbook

Claire Butler joined Figma as its 10th employee and first marketing hire while the company was still in stealth. She recalls her first day: the product was slated to be called Summit under a Figma company brand, and she immediately argued that two brands could not build equity and that Figma was the ownable name. Dylan asked her to present the case the next day, and the name was killed on her second day.

She pairs that story with a very different memory from the first meetup, when she forgot the ice and walked three blocks back carrying heavy bags of it. For Butler the contrast sums up early-stage life: you oscillate between high-level strategic decisions and doing whatever small job needs doing. Lenny jokes that it is almost a metaphor, because someone always has to carry the ice.

The most stressful period, she says, was launching out of stealth. She had never run the full chain from messaging and positioning to PR, and as the only go-to-market person she had nobody to sanity-check decisions with. Venture investors helped, but ultimately she learned to trust her own judgment, a skill she says Dylan models well and that has stayed with her.

Butler had already decided she wanted an early-stage company, and three things made Figma stand out. First, the premise clicked immediately: she used online tools like Google Docs and Asana every day, so it seemed strange that design was not online, and she had felt the inefficiency of sending designers feedback by email.

Second, people she trusted believed in it, including investors from Index and an old boss, plus John Lilly, whom she had to Google but found impressive. Third, Dylan would not take no for an answer: every concern she raised he picked apart one by one. She stresses that she had no idea Figma would get this big and that luck played a part.

Lenny summarizes the lesson as believing in the idea, seeking social proof from people you trust, and being impressed by the founder. Butler agrees and adds that she simply believed in Dylan.

Butler defines Figma's go-to-market as bottom-up and focused on individual contributors: practitioners who use the tool all day. They come to love the product and the brand, and love it enough to risk their social capital by spreading it. The link to revenue is companies, where those individuals become internal champions who spearhead adoption and eventually generate large revenue. This differs from the top-down SaaS model of selling to a VP who then pushes a tool down.

The efficiency is striking. Figma had no sales team for the first three years, with revenue all self-serve on credit cards, and the team could focus on technical features rather than procurement requirements. Even later, most marketing qualified leads came from the free tier or Pro users who wanted help getting past security. Butler says Figma spent essentially nothing on programmatic paid marketing, since leads arrived through a form from people who already had a champion inside.

What sets Figma apart from other bottom-up companies, she argues, is obsession with the editor itself. Saving a designer one click matters when they spend eight hours a day in the tool, and nobody wants to talk about collaboration; they just want it to work. People stay for the collaboration, but the craft of the tool is what they love.

Figma was built quietly for about three years, and Butler says the decision to leave stealth was partly about morale: the team needed momentum and a milestone. The surprising part was that multiplayer, the core differentiator in the positioning doc, would take roughly another year, so they launched without it. Butler recalls an early visitor telling them they could not launch without multiplayer.

What gave her confidence was watching designers react in demos. She and Dylan drove around showing the tool to companies, and once features like vector networks were in, people took the laptop out of Dylan's hands to play with it. A few teams were using it full time, and that signal was enough. Lenny calls the laptop story a good metaphor for product market fit.

On metrics she holds a possibly controversial view: at early stages the numbers are too small to mean anything. She often repeats that you can't optimize your way to product market fit, and she would rather find a couple of people who love the product, through anecdotes and conversations, than chase small conversion gains. Lenny's own mental model is get one company to use it, keep them, get a second, then get someone to pay.

The Microsoft story illustrates the bottom-up motion. Butler got the first Microsoft meeting by messaging a friend's ex-boyfriend after noticing someone from there had signed up. The first pocket of users was the Xamarin team, and Figma then slowly appeared in more pockets, all on credit cards, with no procurement or security review.

Eventually Microsoft came to Figma wanting to pay: they needed security, account management and procurement for a tool that had been popping up in the organization without their control. Figma's data science team built node graphs showing how a product spreads from one user to the next across teams and organizations, and the graphs revealed how important single internal champions were. Butler calls this the unlock for understanding how champions drive the rest.

She also describes Dylan's hustle, such as talking about Figma with someone he met in a shared Lyft who then became a user. Early on, she says, you do whatever you can to get people to try the product and give feedback.

For step one, getting ICs to love you, Butler lists four principles: credibility, building the product with users, a channel where you can build a relationship over time, and transparency. On credibility, she learned right away that designers do not want to hear from marketers and have an extremely high bullshit meter. Words like efficiency and collaboration turn them off, and they want to understand how technical features work.

So Figma leaned on what it had. The tool ran on WebGL, and Evan's engineering feat drew technical interest, with a technical post reaching the top of Hacker News. The designers wrote about decisions behind grids and vector networks, going deep enough that Butler used a simple bar: if she could have written it herself, it was too basic. She had to Google the grid pioneer Josef Müller-Brockmann the first time he came up.

Six months after launch, her first hire was a designer advocate drawn from the user base, not a marketer. He talked to users, wrote content and fed feedback back to the product, and the role scaled with Figma to what she calls the magic dust of its go-to-market. Butler says they published maybe ten pieces in the first six months, favoring quality over quantity, and pushed them on Hacker News and Designer News.

The second principle is building with your customers, and Butler tells the story of Coda, the first company to say yes to Figma. Their designer wanted to take it on full time, but then a teammate's file would not open. Dylan told everyone to drop everything, and it turned out the problem was one engineer's MacBook, so Dylan drove down to Palo Alto to fix it in person.

Early on everyone at Figma did support through Intercom, and engineers debugged problems live with users and fixed bugs right away. When the designer advocate joined, scaling that listening became part of his job, and telling users their request had shipped made them feel ownership. Lenny notes that this is a classic example of things that don't scale, and Butler agrees that in the early days nothing does.

Asked why love matters rather than mere use, she says becoming a champion means taking a personal risk by bringing other people in, especially at work. People won't do that unless they really believe in the product, and that passion is what produces spread without you pushing.

The third principle is choosing a channel where people can follow you without investing. Early users will not come to your Slack or your space, so Figma went to them. Dylan identified Twitter, where the design community already lived and shared best practices, and the company went all in on that single channel.

Dylan built a scraper that started from a handful of design influencers and mapped who followed them, producing a node graph with clusters such as icon designers, graphic designers and product managers. Figma used it to decide who to ask for feedback, never to sell the product, and also followed those people and pushed technical content to them. Engineers and Dylan engaged personally, so the account was people and not just a brand handle. Butler says they have reused the graph when entering other audiences.

The fourth principle is transparency and authenticity. It is easy with a few users, and harder at scale, where Butler says the better examples sit. The aim is to be human and not hide behind the brand.

Butler says the playbook stays the same as Figma grows. The advocate function became a large team: developer advocates, FigJam advocates and regional ones, such as in Japan. Advocates often find Figma before Figma finds them, because they emerge from the community, and the designer advocates were all previously product designers.

To keep building with users, engineering runs quality weeks in which engineers pick small annoyances from Twitter and support and fix them. The team bundles them into an annual launch called little big updates, one of Figma's most popular. The transparency side was tested during multiple downtimes in a week caused by an AWS cluster issue, when Figma published a public postmortem with the technical reason and took full accountability.

Her most stressful day was announcing the acquisition, when the team had only retweeted Dylan. A colleague, Raji, argued they should talk to users directly, so the next day they held an open Twitter Space with Dylan, Sho, Raji and Tom taking any question. Butler says that is when the tide began to turn. Config, the conference, applies the same ideas: content comes from a call for proposals, advocates help speakers shape talks, and the aim is to make it fun, more like a rock concert than a conference.

For step two, helping the product spread inside an organization, Butler lists four items: make it easy to try and share, bring designer advocates into the sales process, find the operational lever that lets you scale, and maintain relationships with champions. On the first, anyone can sign up for a free account and create a free team. After pricing arrived about two years after launch, the starter plan originally allowed unlimited files but only two or three collaborators.

The team realized that hurt them and flipped it to a limited number of files with unlimited collaborators, which showed clearly in the metrics. Teams get confidence using it for free before anyone involves procurement. Butler says the change was intuitive, and the hard part was change management, since people had been working around the old limits with drafts and links.

Free leads to Pro on a credit card, and Pro to Org through sales, and most upsells to Org come from Pro. Viewers and commenters are free, so Figma reaches product managers and others, and only editors are charged. Lenny admits he recently upgraded after hitting the three-file limit, and Butler says the core foundations of packaging rarely change, though new features like variables and Dev Mode force tier decisions.

Figma's first salesperson started the same day as a new designer advocate, Tom Lowry, himself a former champion who had brought Figma to his own company. He joined sales calls without ever carrying a quota, explaining the product the way only a designer could. The sales team started calling it the Tom Factor, because deals were more likely to close when he joined. Butler says the role reports to her and that it also synthesizes feedback from hundreds of customers back to product.

The operational lever was design systems: shared libraries of components such as buttons that update everywhere and tie to code. Early Figma lacked shareable design systems, and big companies said they could not adopt it without them. The company started informal meetups with design systems practitioners, learned from them, built features and then leaned into content, designsystems.com and a conference called Schema.

Design systems are also a main reason to upgrade from Pro to Org or Enterprise, and the design systems people are now the key internal champions, either the biggest blockers or biggest allies. Lenny's takeaway is to see whether the thing blocking adoption can be turned into an advantage. Butler adds that this works best when the IC gets value alone and the product is technical, because practitioners want to learn the craft.

The last step is to keep the relationship with champions going indefinitely. They do not go away, and sometimes they get mad and tweet about it, which means you must go talk to them right away. Butler also thinks about what they get beyond the tool, such as speaking at events, amplification on social and becoming thought leaders, which in turn builds more credibility for Figma. Lenny calls it flywheels within flywheels.

As Figma grows and adds more top-down motion and ROI proof, her job is increasingly to protect the bottom-up engine, including Config, Schema and the advocate team. She says it is easy to break the thing that worked while layering on new methods. As prerequisites, she names a technical audience that cares deeply about its tools, an existing community to distribute through, and an IC role with many collaborators who can act as super-spreaders.

She also reminds listeners that Figma faced real disadvantages: the first reaction on Designer News was that if this is the future of design, the commenter was changing careers, because designers did not want to be collaborative. The team that works best has an executive who believes in the approach, as Dylan does, and who can trust intuition when metrics are unclear. In the lightning round she recommends Radical Candor and Dare to Lead, shares her motto of consistent pressure over time, and says she uses FigJam for home renovation planning.