Latest / Startup Stories with Fexingo: Conversations About Founders, Funding, and Building Companies from Zero / How Figma Became the Design Standard
Transcript
- Lucas: So, a few weeks ago, Adobe's acquisition of Figma finally closed. And I think it's worth stepping back and asking: how did a small startup, which launched when Sketch was basically the default, manage to become the tool that everyone uses now? Luna: It's a good question. I remember when Figma first came out, people were like, why do we need another design tool? And now, it's hard to find a team that isn't using it. Lucas: Right. And the interesting thing isn't just that they won. It's the how. Because they didn't just make a better editor. They made a fundamentally different product. And I think a big part of that was their bet on the browser. Luna: Yeah, the browser was a bold move. At the time, everyone was running native desktop apps. Figma's pitch was, you can just open a link and collaborate with anyone, no install required. Lucas: Exactly. And that was a huge deal for collaboration. But it also solved a distribution problem. And that's something we haven't really talked about much on this show. So today, let's drill into how Figma's browser-based approach, combined with a smart free tier and a plugin ecosystem, turned it into a platform. Luna: Let's do it. I think the browser thing is actually underrated. It meant that onboarding was instant. You could share a link and the other person could comment without even creating an account. That's powerful. Lucas: Absolutely. That's probably the single biggest unlock. If you've ever tried to get a non-designer to open a Sketch file, it's a nightmare. Figma removed all those barriers. And that's what allowed it to spread beyond just the design team. Suddenly, product managers, engineers, even executives could jump in and look at the designs. Luna: And that's where the network effects kick in. The more people in your organization use it, the more valuable it becomes. It's not just a tool for designers anymore; it's a communication tool for the whole company. Lucas: Right. And they leaned into that. They made commenting and feedback super easy. And they made the free tier genuinely useful. You could have unlimited files and unlimited editors, with some limitations on version history and things like that. That was a huge driver of adoption, especially among students and freelancers. Luna: And those students grew up to be professional designers, who then brought Figma into their companies. It's a classic bottom-up adoption play, but executed really well. Lucas: Exactly. And then, on top of that, they built the plugin ecosystem. That was a masterstroke. Because now, not only is Figma the tool, but it's the platform where you extend the tool. And that creates a whole new layer of stickiness. Luna: I think the plugin ecosystem is reminiscent of what happened with other platforms. Like, when I think about it, it's kind of like the App Store model, but for design. And that's a big deal because it creates an ecosystem of developers who are invested in Figma's success. Lucas: And it also solves the problem of one-size-fits-all. You know, the core product is pretty simple, but plugins let you tailor it to your specific workflow. That's how they managed to serve both the indie designer and the enterprise teams with complex compliance needs. Luna: Exactly. And they also did something smart with their API, which allowed for things like design tokens and handoff to engineers. That made it easier for teams to actually ship the designs, which is the ultimate goal. Lucas: Right. So, let's talk about the acquisition. Adobe paid twenty billion dollars for Figma. And at the time, Figma was valued at around ten billion. So it was a huge premium. But Adobe was clearly buying more than just a tool. They were buying the platform, the community, and the mindshare. Luna: And they were also buying the innovation engine. Because Figma was known for shipping really quickly and iterating based on user feedback. Adobe, on the other hand, has a reputation for being slower and more enterprise-focused. So I think it's interesting to see how they're managing the integration. Lucas: Yeah, and the regulatory scrutiny was intense. The deal took over a year to close because of antitrust concerns. And in the end, they had to make some concessions. But it's done now, and the big question is: what happens next? Luna: I'm curious to see if they'll keep Figma independent or if they'll start integrating it with Adobe's Creative Cloud. And also, how will the community react? There's a lot of fear that Adobe will ruin Figma. Lucas: Yeah, I've seen that sentiment online too. But so far, they've kept Figma pretty independent. And I think that's the right move. If they try to force it into the Adobe ecosystem, they risk losing the very thing that made it special. Luna: Well, it'll be interesting to watch. But stepping back, what can founders learn from Figma's journey? I think one big lesson is that you can win even when you're going up against an entrenched incumbent, if you can offer a fundamentally different way of doing things. Lucas: Definitely. And another lesson is the power of a great free tier. Not as a loss leader, but as a real product that brings people in and gets them hooked. Figma did that really well, and then they converted those users into paying customers as those users moved into professional roles. Luna: And also, the importance of building a community. Figma really invested in their community, from their conferences to their ambassador program. That created a sense of belonging that you don't get with just a tool. Lucas: Right. And I think that's why the acquisition might work. Because Adobe, they're good at monetizing, but they're not exactly known for building vibrant communities. Figma has that in spades. So if Adobe can let Figma be Figma, it could be a win-win. Luna: Yeah. And it's a good reminder that in tech, the product is never done. The way you stay ahead is by continuously innovating and listening to your users. Figma did that for years, and that's why they're where they are today. Lucas: Absolutely. So, as we wrap up, I think the takeaway is that winning isn't just about having the best features. It's about having a core insight about how people want to work, and then building everything around that. Figma's insight was that design should be collaborative and accessible, and they never wavered from that. Luna: And that's a great note to end on. But before we go, I just want to mention something quickly. If you find value in these conversations, and you want to support us, you can do that by buying us a coffee at buy me a coffee dot com slash fexingo. It's a small thing, but it really helps us keep doing this ad-free. Lucas: Yeah, and we really appreciate the listeners who already do that. It's what allows us to spend time on these deep dives. So, thank you. And back to Figma - I'm really curious to see how they navigate the next few years under Adobe. Do you think they'll stay true to their roots? Luna: I hope so. I think the design community would be pretty upset if they didn't. But it's a big company now, so we'll see. Lucas: Well, that's all for today. Thanks for listening, and we'll catch you in the next episode.