We switched from Webflow to Claude. Our marketer became our top committer.

In early July one of our founders, Austin, came to the Marketing team with a hunch.

He wondered if the team could retool on Claude and Next.js and reap the same benefits the engineering team had been seeing: shipping more, faster, at higher quality.

We were skeptical that Claude + Next.js could replace our existing site in Webflow, but we decided to give it a try.

The fun part

I volunteered to do the initial site setup with Claude. Fable had just been released so it felt like a fine time to try out the new model. I love starting new projects and doing them with Claude is so much easier.

Two hours later Claude had created 482 React and Next.js files with 29,874 lines of code, and a plausible copy of our 60+ page Webflow site.

The website was genuinely good, but there were still some issues. As we were heading into the weekend I kicked off a couple of long QA sessions asking Claude to compare the website in the browser against the old website and repair any issues it found.

After a little more iteration I was ready to share it with the team.

It’s mind-blowing to be working with the state-of-the-art in 2026. In just 2 days, Claude had accomplished what would have taken a team of developers weeks to do just 2 years ago.

Enabling the team

Now we had a working copy of the website, but there were still some things that needed to be updated. I spent some time with the team walking them through the new stack. We explored Claude Desktop and figured out that it had a really cool site preview tool that could bring the site up and even allowed you to point and click on elements to make changes:

The hardest part was helping the team get used to working with Git. We started with a develop branch where we told the team to push changes. Every other day I made a PR off of develop and merged changes so that they would be available on our Vercel site (where the new site was available for the internal team).

After everyone was comfortable pushing changes we walked them through branching and PRs. Claude made all of this so much easier. Most of the work was teaching the team the right prompts to talk to Claude about Git. Once they understood the conceptual model it clicked.

Vercel really has been a joy to work with. Live previews on every PR make it easy for everyone on the team to review work before it’s merged. The setup process is painless and the Git-based workflow is a dream.

Making it safe

The last part of the system that we built so that non-Engineers would feel comfortable making changes was setting up a QA workflow with Devin. Devin is an AI tool that makes working with AI similar to working with a team mate. It can use a computer just like a human which was perfect for our use case. We have Devin setup to QA all of our PRs. Devin looks at the source code, opens the site in a browser and actually clicks around to ensure that the changes do what they are supposed to do. It then posts exhaustive comments detailing what it did with screenshots showing what works and what doesn’t. Devin has caught countless issues for us and given the entire team confidence to ship code.

Adam Root, our growth marketer also setup tests in Vitest that run on every PR. The test suite started small but now runs 3,005 tests across 157 files and the whole suite finishes in twenty-four seconds.

Marketing is locked-in

It’s been genuinely shocking how well the system has worked for our marketing team.

Our Head of Marketing, Nate Meadows, who had never pushed a line of code before, has now shipped over 150,000+. Seeing his vision come to life across countless pages has been inspiring. He’s shipped countless improvements to the header, navigation and created dozens of new feature pages to highlight Opine with live animations built in HTML.

Coding agents provide software engineers with the joy of pure creation, and now Nate had it too. He always had a lot of ideas for things he wanted to try on the website, but he frequently had to say no to them because they were too costly to justify the experimentation. Now, all those ideas take less time to create than it would take to write up the design brief for a web developer.

I didn’t know just how valuable Austin’s suggestion would be.

With a little support, non-coders can adopt Claude to build and maintain real websites. The value for our team is that everyone is now empowered to ship at a quality level and speed that was unattainable before.

We switched Webflow off for good on August 5. If you’re a marketing team wondering what the future looks like, this is it!