How Vlad Magdalin built Webflow through four failed attempts

Executive overview

Most founders quit after one or two failed attempts. Vlad Magdalin made four attempts over a decade before Webflow found traction — each collapse teaching him something the next version needed.

The core insight came from watching 3D animation software: creatives work directly in sophisticated tools and press a button to see the result. Web design had no equivalent. Webflow was built to close that gap.

Prior failures don't invalidate an idea — they refine the timing and the founder.

Four attempts before launch

1. First attempt wound down when Vlad got married and needed stable income — felt like a pause, not a failure
2. Second attempt: found a co-founder, worked nights and weekends, petered out again
3. Third attempt: got incorporated, secured some funding, two co-founders — then a trademark conflict derailed the rebrand; a competitor (Weebly) raised $20M and seemed to close the door
4. A trademark certificate for "Webflow" arrived unexpectedly in 2012 — Vlad took it as a sign and committed fully

The conviction that held

• Vlad came from a 3D animation background; visual, direct manipulation of complex systems was normal to him
• When he saw web design, the gap was obvious — Dreamweaver and Adobe had tried and quit, which made others assume it was impossible
• He discounted investor scepticism rather than internalising it — useful for conviction, but he later acknowledged it also blocked useful critical input
• The video Inventing on Principle by Bret Victor crystallised both the product vision and the question of purpose; the next morning he called his boss and quit

Building with no money

• Three months of savings as runway; planned a Kickstarter video — then discovered Kickstarter banned hosted software
• Applied to YC without a real product; rejected; kept building
• Extended every credit card, borrowed from friends, converted assets to cash
• Launched on Hacker News in March 2013 — designer forums ignored it, but developers resonated strongly
• Developers valued it because it freed them from tedious Figma-to-code translation work and generated clean, semantic output
• Got into YC on the second application, which provided the lifeline to continue

Why developers became early champions

• Webflow was aimed at designers, but developers did the translation work designers couldn't do alone
• That translation (Photoshop/Figma to HTML/CSS) was low-value, repetitive work pulling engineering time away from product
• Webflow's output was clean, performant, semantic code — not the tag soup that other site builders produced
• Developers saw it as multiplying designer output, not replacing their own meaningful work

Converting a waitlist of 30,000 to 40 paying customers

• The gap between interest and payment was shocking at first
• Recovery came from staying close to early customers and iterating on their specific needs
• No formal framework early on — the practice was customer centricity: listen, solve, repeat

The framework that shaped Webflow's strategy

Vlad describes Simon Sinek's The Infinite Game as providing structure after the fact:

1. Advance a just cause — for every $10 Webflow earns, users likely earn $1,000; the value ratio is built into the mission
2. Prioritise people — inside the company (team empowerment) and outside (users, communities, environment)
3. Generate revenue — third, not first; revenue exists to fund the first two responsibilities indefinitely

Founding with kids

• Vlad had children through multiple attempts and hid it from investors early on, fearing it would signal inability to commit
• In hindsight, having kids shaped Webflow's culture toward sustainability and strong benefits, attracting experienced, family-oriented hires
• His advice: there is never a stable time to start a company or have kids — do both if you want both