Webflow

Lace up. We’re going back 👟 IMA turned the adidas + Offspring House of ZX into a digital time capsule — celebrating the 2026 ZX drops while honoring decades of innovation, design, and street culture. Think: 50+ legendary trainers, archived chronologically, each with the stories that made them icons. #MadeInWebflow, of course 😉 Press play on ZX history: https://lnkd.in/gcUUMfrK

We open-sourced Codeflow, the shell we use for interviewing engineers at Webflow. Candidates work in their own IDE, with their own tools, including AI: Codex, Copilot, Claude Code, ChatGPT, Cursor. It's all on the table. The interview is screen-shared, so we see the full workflow: how they prompt, how they debug, how they ship. Because that's the signal that matters. Many teams are rethinking how to interview engineers when AI is part of the job. We've been running this for a while, and wanted to share what works. Use it, fork it, take what's useful: https://lnkd.in/eDNwDJP5 Built by Kaden Beckstead

We’re going all-in at Adobe Summit 2026 ♠️ April 20–22 | The Venetian, Las Vegas — here's where to find us: 📍Stop by booth #249 for live demos, swag, and to meet the team all week 🍸 Martinis & Martech (April 20, 7–11pm) — co-hosted with Knak, 6sense, Cvent & TransPerfect 🎥 On-demand session: Agentic Web: Design, Automate, Convert with Webflow and Adobe Marketo https://wfl.io/4lZxEVb Book time with our team 👉 https://wfl.io/3Ofkffd

Something different is coming on April 13. Not a webinar. Not a typical product launch. We’ve been working on a new way to talk about what’s happening to the web right now. Because the way people discover products is changing, fast. Fewer clicks. More answers. And a growing gap between what brands say… and what AI says for them. So instead of another announcement, we built something a little unexpected: A full week of programming, with special guests, surprise announcements, and real conversation. Sign up to be the first to know when it drops 👉 https://wfl.io/4v1gHxN

Big news: AI Guy is a finalist for Best B2B Campaign at The Webby Awards 🎉 From “hands, the face of the arms”, to “l’weenis”, to a little “LLM jazz”… it’s been a ride. Now we need your help to win the People’s Voice 👉 https://wbby.co/57251N. Voting is open until April 16th.

I wrote about what we're building at Webflow ... the *marketing harness* and why it's the infrastructure question that matters most for marketing teams right now. The biggest leap for developers in the last few months wasn't a model improvement. It was a harness improvement. Anthropic's Claude Code reads your file system, respects your skills, understands your project structure. The model didn't get smarter. It got context. And, context is what turned impressive demos into software you'd actually ship. But that context is hard to govern. And, I kept thinking about what the equivalent looks like for marketing. Marketers are generating more content than ever and the feedback I hear in every conversation is the same: it's fast, but it's not quite right. Not on brand. Doesn't follow the messaging framework the team spent months building. Sounds like it could be anyone's content, because it is. This isn't a model problem. It's the same problem developers had before Claude Skills was introduced. The context layer is still missing for marketers. A harness for marketing gives AI the stuff that makes your brand yours: your design system, your audience definitions, your compliance rules, your voice and tone, your channel logic. And, it governs that context so you don't have to build systems around answer engine optimization, compliance, publishing governance, and more. When that layer exists, AI stops producing generic output and starts producing your output. The gap between "impressive demo" and "actually publishable" closes dramatically. This is what we've been building at Webflow, honestly, before we had a name for it. Webflow's visual editor, CMS, design system, API-first architecture ... each one was a piece of the harness before anyone called it that. Now we're making all of it agent-readable and composable. I would genuinely love to hear what resonates, especially from anyone building or evaluating this kind of stack ... can't wait to show you what's coming next 🚀 Check out link to my post in the comments ...

100x increase in traffic 🤯 That’s what happened after Vooma launched their new site in Webflow. Vooma is one of the fastest-growing AI companies in logistics, building agents that automate freight operations for brokers and carriers nationwide. They needed a digital presence that reflected that momentum. The new vooma.com does exactly that. From high-impact visuals to custom animations and a seamless build, every detail was crafted to elevate the brand and turn the site into a true growth engine. #MadeInWebflow, start to finish in just 8 weeks. Kudos to the team that brought the site to life: Brand: Primary Web Design: Timothy Boros Creative Direction: Benten Woodring Development: Devin Fountain Animation: Valerio Vazquez

Momentum Tour 2.0, that's a wrap 🌍 8 cities. 1 month. Hundreds of conversations with teams building seriously ambitious things on Webflow. From London to Zurich, we sat down with marketers, designers, and operators who are rethinking what a website can do, not just as a marketing surface, but as a core growth engine. Huge thank you to our incredible partners who made each stop special: MakeBuild, Kvalifik, Klarkode, ZUID., magier, Digidop, Lokalise 🙌 And to everyone who joined us along the way, this is just the beginning.

Every time a new capability makes building easier, the same thing happens. Teams race to use it. They optimize for speed. And then, a few years later, the teams that won turn out to be the ones who built systems around the capability rather than the ones who moved fastest with it. I've watched this play out with e-commerce. With performance marketing. With mobile. With the martech explosion. AI is that moment again. And I'd rather say the uncomfortable part early: Most teams experimenting with vibe coding and agentic development are optimizing for speed to publish. That's the wrong thing to optimize for. Not because speed doesn't matter (it does!) but because speed to publish is now table stakes. Every team has it. The higher order bit is answering the question: "how do we make our website a better growth vehicle every single day?” That's a systems question. And a lot teams don't have a good answer yet. Think of it like Formula 1. Any car can go fast on a drag strip. What separates the winners over 50+ laps is the telemetry, the pit crew, the system learning in real time. The competitive advantage isn't the launch. It's the loop. Your website works the same way. Build fast is phase one. Ship a growth-focused system with confidence is phase two. The moat that too few are talking about is what happens after: a closed loop where the platform has context, sees what's underperforming, generates the hypothesis, ships the change, and feeds it back in. Continuously. Without your team having to orchestrate it. That's the Agentic Web Marketing Platform we're building at Webflow. And it's what I wrote about this week on our blog. Genuinely curious: when you think about your web stack right now, do you have a clear answer to the 'how do we improve it every day' question? Or are you still mostly in phase one? https://lnkd.in/gdtg7mg5