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 it's 2012, Dylan Field is a twenty-year-old college student at Brown, and he gets a Thiel Fellowship — a hundred thousand dollars to drop out and build a company. His initial idea? A tool for creating and sharing GIFs. Luna: GIFs. That is a long way from a twenty-billion-dollar design platform. Lucas: Right. But that first idea didn't work. He and his co-founder Evan Wallace pivoted hard and landed on building design software that runs in a browser. Not a native app. That choice — browser-first — was the foundational bet. At the time, every serious design tool was a desktop app. Adobe Photoshop, Sketch, Illustrator — all installed locally, files on your hard drive. Luna: And the conventional wisdom was that browsers just weren't powerful enough for that kind of graphics work. WebGL was still young. Lucas: Exactly. But Evan Wallace was a gifted graphics programmer. He and Field believed they could push the browser to do what only native apps had done before. And they were right. By 2013 they had a prototype that could render vector graphics in real time. The key insight wasn't just technical though — it was behavioral. If the tool lives in the browser, there's no install friction. You send someone a link and they can see your work instantly. Luna: That's the seed of the collaboration feature that eventually became Figma's killer advantage. Lucas: Precisely. In 2015 they launched a private beta with multiplayer editing — multiple people working on the same file at the same time, seeing each other's cursors, changes appearing in real time. This was unheard of in design tools. Sketch, the incumbent at the time, had a plugin for collaboration but it was clunky. Figma baked it into the core product from day one. Luna: But here's the interesting part — who did they target first? Not designers. Engineers. Lucas: That's the strategic twist. Figma's early go to market focused on engineering teams. Why? Because engineers were the ones frustrated with the handoff process. Designers would create a mockup in Sketch, export PNGs, attach them to a ticket, and engineers had to guess the spacing, font sizes, colors. It was a constant source of friction. Figma gave engineers a live view of the design file — they could inspect pixel values, copy CSS, see the actual specs. Luna: So engineers became Figma's internal champions inside companies. They'd push for the team to adopt it. Lucas: Exactly. And once the engineers were on board, the designers followed. By 2018, Figma had about four million users. Not huge by Adobe's scale, but the growth rate was accelerating. The network effect was kicking in — the more people in your organization using Figma, the more valuable it becomes, because all your design files are in one place, shareable with a link. Luna: They also had a clever pricing model. Free for up to three projects and unlimited viewers. That made it trivial to try and adopt. No credit card required. Lucas: Freemium with zero friction. Adobe, by contrast, had expensive Creative Cloud subscriptions and a sales team. Figma's self-serve model meant a single engineer could start using it and then invite the whole team without ever talking to a salesperson. By 2020, they hit a two-billion-dollar valuation in a Series D led by Andreessen Horowitz. And by 2021, with remote work exploding, Figma became the default design tool for startups and even large enterprises. Luna: There's another cultural detail I love — Figma instituted 'no meetings Wednesdays' to protect deep work. That's a sign of a company that really understands its users are builders. Lucas: Absolutely. That policy started early and stuck. Engineers and designers got one day a week with zero scheduled meetings. It's a small thing but it signals that the leadership values focus over constant communication. And for a company building a collaboration tool, that might sound paradoxical, but it actually made sense — they needed to build a great product before they could sell it. Deep work was how they innovated. Luna: So the lesson for founders here: don't just build for your core user. Think about who else in the buying process has pain. For Figma, engineers were the wedge. Lucas: Right. And the second lesson: choose a technical bet that compounds. Browser-first was harder in the short term but it unlocked collaboration and zero-install distribution. That's a moat that gets deeper every year the web improves. By the time Adobe launched its browser-based competitor, Figma had years of head start and a community of millions. Luna: It's also a reminder that timing matters. Figma launched multiplayer editing in 2015, but the real wave came in 2020 when everyone went remote. They were years early. Lucas: Yeah. They built for a future that hadn't fully arrived yet. But when it did, they were the only game in town. And that's why they're now valued at twenty billion and arguably the most important design tool of the decade. Luna: Speaking of building for the future — if you're a founder listening and these kinds of strategic decisions are helping you think about your own product, we'd love your support. This show stays ad-free because listeners chip in at buy me a coffee dot com slash fexingo. It's a small gesture that keeps these stories coming. Lucas: Yeah, we hear from a lot of you that these episodes actually help you reframe your own challenges. That means a lot. So if you find value here, consider tossing a coffee our way. It really does make a difference. Luna: Alright, back to Figma's trajectory. After 2020, they started expanding beyond design — they launched FigJam, a whiteboard tool, in 2021. That was a direct play to own the entire product development conversation, not just the design phase. Lucas: That was a smart move. FigJam competes with Miro and Mural, but because it's integrated with Figma, teams can move seamlessly from brainstorming to wireframing to high-fidelity design in the same ecosystem. It increases switching costs and deepens the moat. Luna: And it's all still in the browser. No downloads. That's the thread that runs through everything. Lucas: It's the original bet that keeps paying off. For any founder listening, the lesson is clear: find a constraint that seems like a weakness and turn it into your strongest differentiator.