#001 - Alexander Diner, Head of Brand Studio @ Webflow⁩

Epsiode Summary

Built on Webflow - Episode 1: Relaunching Webflow.com in 11 Weeks Ft. Alexander Diner, Head of Brand Studio at Webflow

The week before launch, the team made a decision that Alexander Diner says had never happened in his decade-plus of agency experience. They moved the go-live date forward. Not out of necessity. Because they had the room to do it.

In the first episode of Built on Webflow, host Lydia Smit sits down with Alexander Diner, Director of Brand and Web Design at Webflow, and Jonathan Cook, Founder of N4, for an honest look at one of the most ambitious website relaunches in recent memory. The complete rebuild of webflow.com. 14 separate projects consolidated into one. Hundreds of pages. Three teams spread across multiple time zones. Less than three months from kickoff to launch.

Alexander shares what it was like to join Webflow after a decade in the community, inherit a site held together by years of workarounds, and set out to make webflow.com genuinely worthy of the platform it runs on. Jonathan opens up about what it took to win the project, why N4 showed up to the pitch with a working build instead of a deck, and what made this timeline not just possible but engineered.

Together, they make a case that the enterprise web industry needs to hear. The idea that scale means slow is no longer true. With the right platform, the right team, and the right approach, large-scale migrations and full redesigns can move faster than most people believe at the start.

What you will take away from this episode:

• Technical debt is universal. Even Webflow's own site was held together by 14 separate projects and years of workarounds. If your site feels unmaintainable, you are not alone.
• The timeline you think you need is longer than it has to be. Webflow.com went from kickoff to launch in under 11 weeks, across three teams and multiple time zones, and still shipped a day early.
• Build component-first from day one. Aiming for 80% component-based pages meant developers could build hundreds of pages without design input, and the site stayed completely on brand throughout.
• Clean up your CMS architecture before you build on top of it. Webflow reduced their collections from over 170 down to under 50. That decision changed everything downstream.
• Launch day is day zero. The real value came after go-live: running experiments, personalising for different audiences, and giving internal teams the autonomy to publish without raising a dev ticket.
• Your website is your most important brand surface. Especially now, when most people have their questions answered before they ever land on your site. When they do arrive, it has to count.

Still on AEM, Sitecore, or a platform that's slowing your team down? N4 specialises in large-scale enterprise migrations to Webflow, and the webflow.com rebuild is what that looks like at its most ambitious.

If you are ready to move, or just want to understand what it would take, start the conversation.