Latest / Startup Stories with Fexingo: Conversations About Founders, Funding, and Building Companies from Zero / How Webflow Gave Designers Superpowers Without Engineers
Transcript
- Lucas: So there's this statistic that's haunted the web design industry for years: roughly 80 percent of the visual designs handed from designers to developers never get built exactly as designed. Luna: Eighty percent — that's staggering. And it's not because developers are slacking off, right? It's just that translating a pixel-perfect mockup into HTML and CSS is genuinely hard. Lucas: Exactly. And that friction is the entire reason Webflow exists. Today we're looking at how a company that let designers build production websites visually — no coding required — turned a $3,000 side project into a business valued at over $4 billion. Luna: And the founder, Vlad Magdalin, wasn't even a designer by training. He studied computer science. Luna: So it was a dogfood project. He was solving his own frustration. Lucas: Exactly. And he showed it to his brother, who was also a designer-developer hybrid, and they started building it out. The original prototype was called 'Webflow' — just a single page app that let you drag and drop elements onto a canvas and export the code. They launched a beta in 2013, and the initial reaction was... muted. Luna: Muted how? Were designers skeptical? Lucas: Yeah, there was real pushback. A lot of designers said, 'I don't want to touch code. I hand off to developers — that's the workflow.' And on the flip side, developers dismissed it as 'just another WYSIWYG editor' — remember how terrible Dreamweaver was for producing spaghetti code? So Webflow had this identity problem: it was too technical for pure designers, and too simple for hardcore developers. Luna: That's a classic startup chasm. How did they cross it? Lucas: They pivoted the positioning. Instead of saying 'this replaces developers,' they said 'this gives designers superpowers.' They targeted what they called the 'designer-developer hybrid' — the person who knows enough HTML and CSS to be dangerous, but who's not a full-time engineer. That person was underserved. There were tools for pure designers — Sketch, Figma — and tools for developers — code editors — but nothing in between. Luna: And that niche turned out to be much bigger than anyone expected. I remember reading that by 2015, Webflow had over 50,000 users just from that hybrid segment. Lucas: Yeah, and they grew that community without spending a dollar on traditional advertising. Their playbook was content marketing — they wrote incredibly detailed tutorials about CSS Grid, responsive design, animation. And they built a show and tell culture where users could share their Webflow-built sites in a gallery. That gallery became a portfolio showcase, and it created a viral loop: designers would build a site, show it off, and other designers would ask 'how'd you do that?' and then sign up. Luna: So it was product-led growth, but with a community twist. The product itself was the marketing. Lucas: Precisely. And they made a crucial strategic decision early on: they didn't take venture capital for the first three years. Magdalin bootstrapped the company with consulting work and a small angel round from friends and family. That forced them to be disciplined about monetization from day one. They launched a paid pro plan in 2014 — $16 per month — which gave you the ability to export your code. That was the hook: if you wanted to actually publish the site you built, you paid. Luna: That's smart because it aligns with the value. Designers saw the tool as a time-saver, and $16 a month was trivial compared to the hours it saved them. Lucas: Exactly. And the export feature was key — it meant designers weren't locked in. They could take their code and host it anywhere. That built trust. But over time, Webflow added hosting, a CMS, e-commerce — and each of those became additional revenue streams. Today, the average revenue per paying user is much higher because they've moved upmarket to agencies and enterprises. Luna: Let's talk about that move upmarket. How did they go from freelancers to agencies? Lucas: They launched a 'Workspaces' product around 2018 that let multiple designers collaborate on a single project. That was the bridge. An agency could have ten designers all working in one account, with shared style guides and assets. And then they added a 'Client Billing' feature — so the agency could bill the client directly through Webflow. That removed a huge pain point: agencies hated invoicing separately. Suddenly, Webflow became the operational backbone of a design agency, not just a tool. Luna: That's a classic platform play. You start with a single-user tool, then layer on collaboration, then billing, and soon you're indispensable. Lucas: Right. And the numbers bear that out. Webflow's revenue grew from about $10 million in 2018 to over $200 million by 2025. Their enterprise product, which includes advanced security and SSO, now accounts for a big chunk of that. But they've been careful not to alienate the freelancers who made them. The free tier still exists, and the gallery still drives new signups. Luna: There's another angle I find fascinating — the no-code movement more broadly. Webflow is often cited alongside Bubble, Airtable, Zapier as part of that wave. But Webflow is unique because it's visual AND produces real code. Lucas: That's the key technical distinction. Most no-code tools generate proprietary data formats or abstract syntax trees that can only be edited inside the tool. Webflow exports semantic HTML, CSS, and JavaScript. If you wanted to, you could download your site and never touch Webflow again. That's a radical transparency that built trust with the developer community — because even if they didn't use it themselves, they couldn't argue it was 'fake code.' Luna: And that trust paid off when Webflow launched their CMS. Developers who had dismissed the tool suddenly realized they could hand a site over to a client and let the client manage content without breaking the design. That's a huge value prop. Lucas: Yeah, the CMS is probably their most underrated innovation. It's a visual content management system where designers define the structure — fields, collections, relationships — and then content editors fill in the blanks through a clean interface. No templates, no PHP, no WordPress-style dashboard chaos. It made Webflow a legitimate alternative to WordPress for marketing sites and blogs. Luna: And it's not just for marketing sites. We're seeing Webflow used for everything from SaaS landing pages to full e-commerce stores. Webflow's e-commerce platform, launched in 2021, now powers thousands of online stores. Lucas: Right, and that's a more crowded space — Shopify, BigCommerce, WooCommerce. But Webflow's differentiator is design flexibility. If you want a truly custom storefront, Webflow gives you that control without needing a developer. It's a premium play, not a volume play. Luna: Let's talk about the funding story. They took a seed round in 2015, a Series A in 2017, and then a massive Series B in 2019 — $72 million at a $400 million valuation. Then in 2021, they raised $140 million at a $4 billion valuation. That's a huge jump in two years. Lucas: Yeah, and the interesting thing is that Magdalin was famously reluctant to raise. He said in interviews that he wanted to stay bootstrapped longer, but the market opportunity demanded scale. Once they decided to raise, they were very deliberate about picking investors who understood design tools — like Accel and 8VC, who had backed Figma and Unity. Luna: And they've been profitable or near-profitable for most of their history, which is rare in the SaaS world. That discipline comes from those early bootstrapping years. Lucas: Absolutely. They didn't burn cash to grow — they grew because the product was good and people paid for it. That's a healthy signal. As of mid-2026, Webflow is still private, but there's constant speculation about an IPO. They've got the revenue, the unit economics, and a strong brand. It feels like a matter of when, not if. Luna: Before we wrap, I want to touch on something you mentioned earlier — the community. Webflow's community is unusually passionate. There are Webflow meetups in dozens of cities, a vibrant forum, and even a certification program. How did they cultivate that? Lucas: Part of it is that they gave designers a new identity. Before Webflow, a designer who could code was called a 'unicorn' — rare and mythical. Webflow democratized that. Suddenly, any designer could learn enough CSS to build a real website. That's empowering. And the company nurtured that by featuring community work prominently, hiring community managers early, and building a 'made in Webflow' badge that people put on their portfolios. It became a status symbol. Luna: It's almost like a guild badge. 'I built this with Webflow' signals that you're a modern, tech-savvy designer. Lucas: Exactly. And that tribal identity is hard to replicate. It's one reason Webflow has been able to fend off competitors like Wix and Squarespace — those are seen as 'template tools' for amateurs, while Webflow is for professionals. The branding matters. Luna: So what's the lesson for founders listening? The thing that stands out to me is the importance of serving an underserved niche first, before expanding. Lucas: Absolutely. Webflow didn't try to be everything to everyone. They found the designer-developer hybrid, made them incredibly happy, and then expanded from there. Also, the bootstrapping-first approach gave them the luxury of time to get product-market fit right before taking outside money. And the transparent code output was a brilliant trust-building move that paid off for years. Luna: And you know, this show is all about digging into those startup stories. We've covered over a hundred now, and each one has its own unique twist. If these conversations have moved your work forward in some small way — maybe helped you think differently about your own product or gave you a new idea — we want to say that we keep this podcast ad-free deliberately. No sponsors, no mid-roll interruptions. And that's possible because of listeners who choose to support us. Lucas: Yeah, it's a simple choice. If you value the show and want to keep it independent, the link is buy me a coffee dot com slash fexingo. No pressure, no perks — just knowing you're helping us stay ad-free. And we really appreciate it. Luna: Okay, back to Webflow. One thing we haven't touched on is the competitive landscape. Figma recently added some design to code features. How does Webflow stay ahead? Lucas: Figma's approach is about improving the handoff — making it easier for developers to inspect designs and generate code snippets. But Webflow's approach is about eliminating the handoff entirely. That's a fundamentally different philosophy. As long as there are designers who want to own the entire pipeline from design to deployment, Webflow has a moat. And the community is the moat's reinforcement. Luna: It's a good reminder that in software, the hard part isn't just building the product — it's building the ecosystem around it. Webflow did that masterfully. Lucas: They really did. And the story's not over. With ai assisted design tools emerging, it'll be interesting to see how Webflow integrates those capabilities. But if their track record is any guide, they'll find a way to give designers even more superpowers.