Hey everyone,

I’m Tommy, founder of Release and I’m going to share a bit of my AI journey and a project I’ve been working on. As I started to build out our AI strategy and story at Release, I saw the CEO of Vercel talking about v0.dev on X. I knew I had to get a v0 account and explore its potential. I originally built all of the frontend code at Release in React and thought playing around with something familiar to me would be good for me to start getting acquainted with what was possible. I quickly realized a new way of building was upon us and wanted to see how I could apply this to what we do at Release.

This image shows the before and after of the design, but what it doesn’t show is how fast we can how ship changes to our marketing site, without design, without a frontend engineer… all powered by v0, Cursor and Release.

Playing with v0 was eye-opening. It unlocked my ability, as the CEO, to take the reins of our marketing site and get our ideas out to the world faster. (Which happens to be our mission at Release). For years, our marketing site was built on Webflow—it looked great, but it was slowing us down and I never really loved how we had to work with it. We had to have a designer come up with designs, someone familiar with Webflow had to implement the designs and, in all, it took us about 2-3 weeks to make even the most straightforward changes to it. I wasn’t originally looking to replace our site; I just wanted to see what was happening in the world of AI. But I quickly realized there was an opportunity to move faster and release my ideas to the world faster.

v0 wasn’t perfect—it had limitations when it came to building a real, production-ready site. I decided to marry by prototype components with our deployment capabilities at Release. With the help of Griff, my co-founder, we created our repo (release-next-base) to serve as a base image, so I could bring my designs from v0 into a working app that was easy to deploy to Release.

Even then, it was cumbersome. v0 had no awareness of my repo structure, how my files were laid out, or how my content should live in production. Enter Cursor—it solved that problem by seamlessly bridging the gap between v0’s designs and a fully functioning, deployable site. So with v0, Cursor and Release all in play, our migration off of Webflow began. RIP CMS.

1. Why We Moved Off Webflow

After five years on Webflow, I realized our process was more of a bottleneck than a benefit:

• Slow Iteration Cycles: Every change involved a lengthy back-and-forth with our design firm—sometimes taking weeks or even months.
• Limited A/B Testing: The rigidity of Webflow made it nearly impossible to quickly test new landing page messages.
• Platform Dependency: We were locked into an ecosystem where every update required specialized know-how.
• The AI Advantage: Tools like v0.dev and Cursor and Release showed me that automation and Git-based workflows could not only accelerate our process but also put me in full control. The traditional CMS model just couldn’t keep up. RIP CMS.

2. The Migration Process: From AI-Generated Designs to Production

Step 1: Generating the Initial Design with v0.dev

My journey began with v0.dev. Intrigued by what I had seen online, I fed v0 a simple prompt:

Build a landing page for Release.com out of this description:

Release.com provides a platform called Environments as a Service, designe