Treat product-market fit as a sequence of escalating proof points rather than one launch, narrowing to a customer you already are, then deepening by obsessively following their requests.
Webflow
Webflow is a visual web design tool that lets designers build and ship production websites without writing code. Its stories share one through-line: a sprawling, unfocused idea only found traction once it was narrowed to a customer the founders themselves were, then extended by listening obsessively to what those exact customers asked for. The result was three distinct product-market-fit milestones over three years, not one lucky launch.
PMF: three milestones, not one launch
The problem. Many companies had tried to build websites visually and failed, so a single strong launch would not prove Webflow had durable demand. The founders needed evidence that real customers wanted the product enough to wait for it, pay for it, and stay when the offering deepened. Early enthusiasm could easily have been a spike that faded.
The approach. Webflow treated PMF as a sequence of escalating proof points rather than a one-time event. It launched a deliberately polished beta on Hacker News in March 2013 to gauge raw demand, then shipped a paid full product to convert that interest into revenue, and later expanded the product surface to test whether customers would pay for more.
How it solved it. The beta stayed atop Hacker News for 27 hours and drew nearly 35,000 waitlist signups within two weeks. Two weeks before YC Demo Day the full product launched to 25,000 signups and $5,000 MRR in its first two weeks. When Webflow shipped its visual CMS in October 2015, MRR jumped 25% within a month and the company crossed $1 million in ARR while turning profitable, three separate signals that demand was real and compounding.
Beachhead: narrowing from "reinvent web apps" to freelance designers
The problem. When Vlad Magdalin began the project in July 2012, the idea was to reinvent how anyone builds a web app visually, a scope so broad the product lacked focus. That vagueness cost them: they were rejected from Y Combinator's Winter 2012 batch. A tool that tried to serve everyone had no specific customer to win first.
The approach. They cut the ambition down to one wedge: helping freelance web designers build websites without writing code. As co-founder Bryant Chou put it, they chose to "focus on a specific sliver of the technology and focus on the specific persona that we felt was the most disenfranchised," the designer who could envision a site but had to hand it to a developer to build.
How it solved it. The narrowed target gave the beta a concrete promise, and the audience responded: nearly 35,000 waitlist signups in two weeks, traction strong enough that Webflow reapplied and got into YC's Summer 2013 batch after the earlier rejection. The focused wedge, not the broad vision, is what finally opened the door.
Founder-Market Fit: engineers and a designer building for themselves
The problem. Webflow was trying to merge web design and web development, two disciplines that traditionally did not coexist, into a single tool for a designer-developer persona that the market did not yet serve. Building for a user you do not understand is where most such attempts died, and this product would be dissected by a skeptical technical audience the moment it shipped.
The approach. The founding team was the target customer. Vlad Magdalin and Bryant Chou were engineers, Sergie Magdalin was a designer, and together they had lived the exact pain of a designer mocking up a site in Illustrator and waiting hours for a developer to implement it. They built for the persona they already were, informed by a customer-obsession habit Chou carried from Intuit's "Customer Follow-Me Home" program.
How it solved it. That firsthand understanding produced a demo where Sergie built in five minutes a website that "used to take a proficient developer five hours," the visceral time saving that made the value obvious. The same instinct drove the 2015 turnaround: mining customer support tickets, they saw users asking for a WordPress plugin, correctly read the underlying need as a flexible visual CMS, and built the world's first one in October 2015, reaching $1 million ARR and profitability within a month.