Latest / Startup Stories with Fexingo: Conversations About Founders, Funding, and Building Companies from Zero / How Figma Won Collaborative Design by Targeting Engineers
Transcript
- Lucas: So there's this moment in 2015 where a small startup called Figma launches a browser-based design tool, and the initial reaction from the design community is... tepid at best. Luna: Yeah, I remember people saying it was too slow, too limited compared to Sketch, which was the dominant tool at the time. Lucas: Right. Sketch was native, fast, had all the plugins. Figma ran in a browser. It was heavier, less responsive. But here's the thing: Figma wasn't really trying to win over the Sketch loyalists on day one. Luna: Who were they going after then? Lucas: Engineers. Specifically, frontend developers and technical product managers who were frustrated with the design handoff process. They'd get a static mockup from a designer, try to implement it, and find that the spacing was off, the colors didn't match, and there was no way to inspect the actual CSS. Luna: Ah, so the classic 'over-the-wall' problem. Design throws it over, and engineering catches it — or doesn't. Lucas: Exactly. And Figma realized that if they could make the design file accessible in a browser, with inspect mode that developers could use to get pixel dimensions, font sizes, hex codes — all without installing anything — they'd solve a real pain point. Not for designers, for the people who actually build the product. Luna: That's a pretty counterintuitive move. Most design tools focus on making designers happy, not on making developers' lives easier. Lucas: Right. But here's the key insight: in most tech companies, engineers outnumber designers by a factor of five or ten to one. If you can get even a fraction of those engineers to open a Figma file regularly, you've created a much larger user base than any pure design tool ever had. Luna: And they don't need to be full users — they just need to look at a file, right? That's a low bar. Lucas: Exactly. Figma's free tier allowed anyone to view and comment on files. So a designer could share a link, and the whole product team could see it, give feedback, and eventually start making minor edits. That's how the viral loop started: one designer at a company would adopt Figma, then the engineers would get used to it, then product managers, then other designers at other companies would see it in action. Luna: It's almost like a developer tool disguised as a design tool. I'm thinking of how Stripe or Twilio — they also targeted developers first. But Figma's twist was that their 'developer tool' was actually a collaboration layer. Lucas: That's a great comparison. Stripe made payments easier for developers. Figma made design handoff easier for developers. And by doing that, they fundamentally changed who 'owns' the design process inside a company. Luna: So how did they actually get those first engineers to try it? Did they go to conferences? Cold outreach? Lucas: They did a few things. First, they made the product incredibly easy to try — no sign-up required initially, just open the browser and start designing. But the real hook was the sharing feature. If a designer sent you a Figma link, you could open it and inspect the code. Engineers loved that. So they started requesting that their design teams switch to Figma. Luna: That's a bottom-up adoption pattern, isn't it? Instead of selling to the design department head, they got the engineers to pull it in. Lucas: Right. And Figma also invested heavily in developer-related features. They had an API early on, they let you embed Figma files in tools like Jira and GitHub. They basically made Figma feel like part of the engineering stack, not just the design stack. Luna: I remember reading that one of their early advocates was a frontend engineer at Uber who wrote a blog post about how Figma saved his team hours per week. That kind of organic advocacy is gold. Lucas: Absolutely. And that's the power of targeting engineers as users — they write blog posts, they tweet, they speak at meetups. They have outsize influence in the tech community. So Figma's growth was fueled by technical word of mouth, not by design magazine features. Luna: Let's talk about the product itself. How did Figma's technology enable this? I mean, building a full vector graphics editor in a browser in 2015 was no small feat. Lucas: It was a serious technical challenge. The founding team, led by Dylan Field, spent years on the rendering engine. They used WebGL for performance, and they built a custom data structure called a 'FigNode tree' that allowed real-time collaboration. Multiple people could edit the same file simultaneously and see each other's cursors — like Google Docs for design. Luna: That real-time collaboration was a game changer. Sketch didn't have it; you had to manually export and send files. Figma made it feel like you were in the same room. Lucas: And that collaborative aspect was also a huge selling point for engineers. They could jump into a design file, suggest a tweak, and the designer would see it instantly. It broke down the silo. That's why Figma's adoption wasn't just a tool switch — it was a workflow transformation. Luna: So what can founders learn from Figma's approach? I think there's a lesson about not always targeting the obvious user. Lucas: For sure. If Figma had gone after designers head-on, they would have been compared to Sketch on Sketch's terms and probably lost. By targeting the engineers who were adjacent to design, they created a new beachhead. And once they had that base, they could improve the product and win over designers too. Luna: It's also a lesson in product-led growth. The product itself — the shareable link, the inspect mode — was the sales mechanism. No need for a big enterprise sales team early on. Lucas: Exactly. They let the product speak to a specific pain point. And that pain point was not 'we need better design tools' — it was 'we need better collaboration between design and engineering.' That's a different problem entirely. Luna: You know, this episode reminds me why I love hearing about these startup origin stories. There's always a moment where the founders made a counterintuitive bet that seemed risky at first but paid off massively. Lucas: And we get to share these stories because of listeners like you. We keep the show ad-free — no sponsors, no commercials — because we want the content to speak for itself. If you find value in these conversations and want to support that choice, you can find us at a simple link: buy me a coffee dot com slash fexingo. Luna: That's a great way to keep us going. And it really does help. So if you've ever pulled a useful insight from an episode, consider tossing a few dollars into that virtual coffee jar. Lucas: Alright, back to Figma. So by 2018, Figma had started to win over the designer community too. They added offline mode, improved performance, and built a plugin ecosystem. Suddenly, Sketch's lead was eroding. Luna: And then in 2022, Adobe announced it was acquiring Figma for $20 billion — which later got blocked by regulators. But the valuation alone showed how valuable Figma had become. Lucas: Right. And even though the deal fell through, Figma is still a standalone powerhouse. Last I heard, they're generating over $600 million in annual recurring revenue. And it all started with a decision to make engineers the primary user. Luna: It's a great reminder that sometimes the best customer is not the one you think. You have to look at the ecosystem around your product and find the real pain point. Lucas: Absolutely. And that's the takeaway for today: don't just build a better mousetrap. Find the person who's actually trying to catch a mouse, and make their life easier — even if they're not the one who usually buys mousetraps. Luna: Beautifully said. That's all for this episode. We'll see you next time.