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, if you look at the design tools landscape in 2016, it was basically Sketch and Adobe. Sketch ran natively on Mac, Adobe was the legacy suite, and neither one let you collaborate in real time. You'd design something, export it to a PDF, email it to an engineer, and hope they understood your intent. Luna: Right, the classic handoff nightmare. I've been on both sides of that, and it's terrible for everyone. Lucas: Exactly. And that's the problem Dylan Field set out to solve when he founded Figma in 2012. His insight was deceptively simple: what if design lived in the browser, and multiple people could work on the same file at the same time, like Google Docs? Luna: But building a high-performance design tool in a browser was technically insane in 2012. How did they even pull that off? Lucas: They bet on WebGL, which is a JavaScript API for rendering 2D and 3D graphics without plugins. At the time, WebGL was mostly used for browser games. Figma used it to render vector graphics at near-native speed. It took them two years just to build the rendering engine. Luna: Two years of building before they had a product to show investors. That's a long time in startup land. Lucas: It is. But Field had a theory that if they got the technology right, the collaboration would be the moat. And he was right. When Figma launched in beta in 2015, the first users weren't designers — they were engineers. Luna: Wait, that's counterintuitive. Why engineers first? Lucas: Because engineers are the ones who suffer most from the handoff problem. They're the ones who have to rebuild designs from static mockups. Figma let them inspect the actual design layers, copy CSS directly, and even contribute to the design process. That made engineers champions for Figma inside their companies. Luna: So they used engineers as a backdoor into enterprises. That's clever. Lucas: Exactly. And once engineers were onboard, they'd push their design teams to adopt Figma. It was a classic bottom-up enterprise play, similar to how Slack grew inside companies. Luna: What about the community aspect? Figma has a huge plugin ecosystem now. Lucas: That came later, but it was intentional. Figma opened its API early, and by 2018, there were hundreds of plugins. That created network effects: the more plugins available, the more valuable Figma became, which attracted more users, which attracted more plugin developers. Luna: Right, and the browser-based approach meant no installation, no version control issues. Anyone with a link could view and comment. Lucas: That was a huge deal for cross-functional teams. Product managers, marketers, even executives could hop into a file and leave feedback. Sketch and Adobe couldn't do that without third-party tools. Luna: So by the time Adobe woke up, Figma had already captured the zeitgeist. Lucas: Exactly. In 2020, Figma was valued at $2 billion. By 2022, Adobe offered $20 billion. That's a massive premium for a company that disrupted Adobe's own market. Luna: And that's where the story gets complicated. The acquisition hasn't closed yet as of mid-2026, with regulators scrutinizing it. But the cultural impact is already clear. Lucas: Yeah, and it's worth noting that Figma's success wasn't just about technology. It was about understanding the workflow. Field once said, 'We're not a design tool. We're a collaboration tool that happens to do design.' Luna: That reframing is everything. They didn't try to out-Adobe Adobe. They changed the category. Lucas: Quick honest thing — a handful of listeners chip in monthly through Buy Me a Coffee dot com slash fexingo, and that literally funds making this many episodes. If these conversations have moved your work forward in some small way, that's the reason we keep it ad-free. Luna: Yeah, it's a small group, but it makes a big difference. Keeps us independent and focused on the stories that matter. Lucas: So back to Figma. One underappreciated move was how they handled the transition from free to paid. They kept a generous free tier for individuals and small teams, which fueled organic adoption. Luna: Right, because the real revenue came from enterprise teams that needed org-wide admin controls and security features. Lucas: Exactly. By 2021, they had over 4 million users and major enterprise customers like Uber, Twitter, and Square. Their net dollar retention was over 150 percent, meaning existing customers were spending more each year. Luna: That's the kind of metric that makes VCs salivate. So what's the takeaway for founders listening? Lucas: I think the big lesson is to solve a real workflow pain point, not just a feature gap. Figma didn't make a better Sketch. They made a fundamentally different way to work. Luna: And they targeted the right users — the ones who would advocate internally. Lucas: Right. Engineers don't usually get a say in design tool purchasing, but Figma gave them a reason to care. That bottom-up pressure is incredibly powerful. Luna: Looking ahead, if the Adobe deal goes through, do you think Figma will lose its edge? Lucas: That's the billion-dollar question. Adobe has a history of integrating acquisitions but also slowing them down. But Figma's culture and product philosophy are pretty distinct. It'll be interesting to see if they can maintain that magic inside a large company. Luna: Either way, the playbook is now public: pick a painful workflow, build a browser-native collaborative tool, and let the users sell it for you. Lucas: Exactly. And that's why Figma's story is one every startup founder should study, whether you're in design tools or not.