❝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”
“andan said to me he was like oh that's interesting how about you make a presentation and present it to everyone tomorrow”
#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”
“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…”
#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”
“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…”
#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”
“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…”
#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”
#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”
“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…”
#transparency#crisis-comms#social#figma