Latest / Startup Stories with Fexingo: Conversations About Founders, Funding, and Building Companies from Zero / How Webflow Gave Designers Superpowers Without Code
Transcript
- Lucas: If you're a designer who can write CSS, you're dangerous. If you can't, you're dependent. Webflow built a three-billion-dollar company by letting designers publish directly to the web without a developer's permission. Luna: I remember when Webflow first launched — it felt like magic. But it also felt like a threat to developers. How did they actually get people to trust it? Lucas: That's the core tension. The founder, Vlad Magdalin, had been obsessed with visual development since 2002. He actually built a prototype at Intuit that let non-engineers design interfaces visually — and Intuit killed it. They said 'this is too disruptive.' He quit, went to school, tried again, failed twice, and finally started Webflow in 2013. Luna: So the product was always there, but the market took a while to catch up. Lucas: Exactly. The early version was a visual CSS editor. But designers didn't know what CSS was, and developers thought it was a toy. Webflow had to educate both sides. Their first breakthrough was the Webflow University — free video courses teaching designers how CSS works, and developers how to let designers handle the front end. Luna: That's a classic product-led growth move. Teach your users to use your tool, and they become evangelists. Lucas: Right. But here's what I find interesting — the developer-relations play. Webflow didn't just sell to designers. They actively courted developers by building a clean, semantic code output. If you inspected a Webflow site, the HTML looked hand-coded. No bloat. That was a deliberate engineering decision. Vlad said 'we have to win the respect of the people who might hate us.' Luna: So instead of fighting developers, they made the output good enough that developers would approve it. That's smart positioning. But what about the business model? Webflow is expensive for a simple site — $23 a month for the basic plan. Lucas: That's actually the genius part. Webflow doesn't compete with Squarespace on price. It competes on capability. The median Webflow user is a freelance designer charging $100 an hour. If Webflow saves them four hours of developer handoff per project, the $23 is irrelevant. The real revenue comes from the CMS plan at $29 a month, and the business plan at $39. And then there's the enterprise tier. Luna: So they're not selling to hobbyists. They're selling to professionals who bill by the hour. Lucas: Yes. Webflow's customer acquisition cost is basically zero because designers tell other designers. There's a famous stat: in 2020, 40 percent of new paid accounts came from referrals. No sales team, no paid ads. The product itself is the marketing. Luna: That's the dream for any SaaS company. But how did they get that kind of organic growth? Was it just the university? Lucas: The university was a big part. They also built a community of 'Webflow Experts' — freelance designers who get certified and then recommend Webflow to clients. It's a classic platform play: make your users successful, and they'll sell for you. But they also did something unusual. They made the free tier actually useful. You can build a fully functional site on the free plan, with a webflow.io subdomain. You only pay when you want to connect a custom domain or add a CMS. Luna: So the free tier is a lead generation engine. Build your portfolio for free, then when you land a client, you upgrade. Lucas: Exactly. And that's why Webflow's conversion rate from free to paid is around 10 percent, which is high for freemium. The average SaaS freemium conversion is 2 to 5 percent. Webflow's is double that because the product becomes essential once you have a client site. Luna: Speaking of clients — one thing I've always wondered: does Webflow actually make designers better? Or does it let them avoid learning the fundamentals? Lucas: That's the critique. Some developers argue that Webflow creates a generation of designers who can't actually write code, so they're locked into the platform. Vlad's response is that Webflow teaches CSS concepts visually. You still need to understand the box model, flexbox, grid — you just manipulate them visually. He calls it 'visual development,' not 'no code.' Luna: So it's a pedagogical tool disguised as a product. That's a strong angle for retention. Once you've learned CSS in Webflow, you're less likely to switch to a different tool that doesn't have the visual interface. Lucas: Right. And the numbers back it up. Webflow's net revenue retention is over 120 percent. That means existing customers spend more each year. They upgrade plans, add team members, move to enterprise. The product gets stickier the more deeply you use it. Luna: Let's talk about the funding side. Webflow took a while to raise. They bootstrapped for years, then raised a seed round in 2013, then Series A in 2015, then a big round in 2019 — around $72 million. Then in 2022, they raised $120 million at a $3 billion valuation. How did they stay disciplined through all that? Lucas: Vlad is famously frugal. He lived on ramen for the first few years. The company didn't have a sales team until 2018. They relied entirely on inbound and self-serve. Even now, with over 600 employees, they keep the marketing spend low. The founder's mentality was: 'we will only raise money when we need to scale something specific.' They raised the 2019 round specifically to build out the enterprise sales team. Luna: That's unusual for a Silicon Valley company. Most founders raise as much as they can. Vlad was almost anti vc. Lucas: He was. He's talked about how he hated the idea of answering to investors. But he realized that to win the enterprise, they needed a sales team, and that costs money. So he raised, but only after the product was proven. That's the right sequence: product first, sales second, funding third. Luna: It's interesting — the company is now valued at $3 billion, but they're not yet profitable? I read that they only became cash-flow positive in 2023. Lucas: That's correct. They prioritized growth over profit for a long time. But they were disciplined about it. They didn't burn cash on marketing or sales until they had product-market fit. Now that they're cash-flow positive, they have more options. They could IPO, or stay private. The founder has said he wants to build a 'generational company,' not just a quick exit. Luna: That phrase — 'generational company' — is something I hear from founders who want to control their destiny. It's almost like a cultural signal that they won't sell. Lucas: Exactly. And if you look at their product roadmap, they're building toward a platform that handles more than just websites. They have Webflow Logic for workflows, and they're expanding into no-code app building. The ambition is to become the operating system for visual development. Luna: So where does that leave developers? If designers can build apps visually, what's the role of the engineer? Lucas: That's the big question. Vlad's answer is that developers will focus on the core logic, APIs, and infrastructure — the things that can't be abstracted. The visual layer becomes the designer's domain. It's a division of labor, not a replacement. But you're right, it does shift the power dynamic. And honestly, that's why some developers still resist Webflow. Luna: We've been talking about the business side of Webflow — the strategy, the growth, the discipline. I think a lot of our listeners, especially those trying to build something, can learn from how Vlad approached it. Lucas: That's actually the kind of conversation that keeps this show going. A couple of dollars a month is genuinely what keeps these episodes ad-free and independent. If you've gotten value from hearing how Webflow navigated the designer-developer divide, you can support the show at buy me a coffee dot com slash fexingo. Luna: Totally. It helps us keep digging into these stories without worrying about sponsors. Even a small contribution makes a real difference. Lucas: So back to Webflow's future. The big question is whether they can fend off competition from platforms like Bubble, which is more app-focused, and from traditional CMS providers who are adding visual editing. But Webflow has a moat: the designer community. Luna: And the quality of the output. That's hard to replicate. Lucas: Yes. And the fact that they've built a generation of designers who think in Webflow terms. That's a network effect. The more designers use it, the more agencies and companies require it. It's not just a tool; it's a standard. Luna: So what's the one lesson you'd take from Webflow's story for someone building a product today? Lucas: I'd say: don't try to be everything to everyone. Webflow could have been a simple website builder. Instead, they focused on a specific user — the professional designer — and built a tool that respected their craft. That focus created a cult following and a business that's both large and defensible. Luna: And the second lesson: educate your market. Webflow University isn't just a marketing expense; it's a product feature. It turns users into experts, and experts into advocates. Lucas: Right. The best sales strategy is to make your customers smarter. Webflow did that better than almost any other SaaS company.