How Nomio migrated from Webflow to CloudCannon in 2.5 days with Claude and Astro
Ed Stennett
Head of Growth
Nomio
36x faster
to publish content
99-100
scores across all Lighthouse metrics
4+ branches, 4+ agents
working concurrently with zero disruption to the live site
When Ed Stennett told his CEO that a new Nomio website might take months with his existing stack, the reply was a question: could he do it sooner? He said he’d try. A site of 200 to 300 pages, completely redesigned, rebuilt and reconfigured, went live about two and a half days later.
Ed is Head of Growth at Nomio. He’s also the company’s only marketer. So this wasn’t a dev team grinding through a sprint. It was one person, armed with Astro, CloudCannon, and a handful of AI agents pointed in the right direction.
Contracts, made searchable
Nomio sells contract-management software to in-house legal teams. Their contracts usually sit in a shared drive as Word files and PDFs, so a simple question means digging for the right document. Nomio pulls out the dates and terms that matter and makes them searchable, so answers come fast. Its buyers are heads of legal and general counsel, along with procurement and finance leaders, all of whom want clear communication and value up front. That puts a lot of weight on the website: it’s Nomio’s shopfront, and its job is to turn those visitors into demos.
The Webflow wall
Nomio’s old site ran on Webflow, and for a long time that was fine. The site sat mostly untouched, and it did its job. Then Nomio decided to ramp up its marketing and build something that explained the product properly. That’s when Webflow started to bite.
The trouble is, everything in Webflow happens with a mouse. A new solutions section with pages for legal, procurement and finance meant building a collection, defining every variable in the interface, dragging and dropping the layout, then fixing it once for mobile and again for desktop. “It’s a visual editor, so what you see is what you get, and it’s really slow,” Ed says. Updating the site to the standard he wanted looked like months of work.
So he asked a different question. What if it didn’t have to be Webflow?
Ed had history here. At a previous company he’d moved a WordPress site onto CloudCannon and kept it there for years, and he’d built with Jekyll, so he knew his way around the bones of a site. Coming back to CloudCannon was easy. What had changed since then was the rest of the toolkit.
Why CloudCannon, and why now
The thing that made such a short turnaround possible was cheap, capable language models. Anyone can now build large chunks of a site without writing all the code by hand, and Ed wanted to get on top of that fast.
But speed on its own can be a trap, and he's blunt about it. Your LinkedIn feed is probably full of people vibe coding a website over a weekend and walking off Webflow and other CMSs, and the build is the part everyone shows off. "There's an over-indexation on how you build something over what you're actually building," Ed says. The part that people tend not to post about is what comes next: maintaining the thing, and getting a team to work on it without it falling over.
This is where CloudCannon earned its place. It lets Ed build fast, but speed isn’t the whole point. He’s a one-person marketing team, and he didn’t want to stay the only person who could touch the website. A CMS means colleagues across the company, none of them developers, can go in and update the parts they look after when they need to, all under clearly defined guardrails. Those guardrails come down to a few concrete things. CloudCannon’s configuration sets what inputs are allowed and gives each person a clearly defined role, so someone editing a blog post can’t wander into parts of the site they shouldn’t touch. And nothing goes live by being published straight to the main site. Changes happen on a branch, a full copy of the site, and only reach production once they’ve been signed off.
It’s almost the perfect time for something like CloudCannon. It’s got the legs and the authority. A lot of the new companies are exciting, but they’re young and haven’t been through it.
There’s a neat second-order effect to a product that’s been documented for years, as CloudCannon has. A team can hand all that documentation to a language model, point Cursor or Claude Code at it, and let the model read the docs and build the configuration that used to need a human to study them first. The guardrails and the AI workflow reinforce each other.
For the static site generator, Ed asked a Claude project loaded with his background what it would recommend. It suggested Astro over his old static site generator, Jekyll, especially with CloudCannon as the CMS. The structure was familiar enough that he knew his way around it, and getting to a genuinely fast site was straightforward.
Everything runs on branches
Of those guardrails, branching is the one Ed keeps coming back to. For him CloudCannon’s Git workflows are the hero of the whole setup, and they’re the thread running through both the rebuild and everything since. Every agent that worked on the migration did so on a branch, and every fix that’s shipped since has done the same. He calls Git “the most underrated and under-thought-about part of web development, particularly in marketing,” and he has a point.
On Webflow, a change went live the moment Ed pushed it, with no safety net. CloudCannon works the way engineers have for years. Main is locked, so nobody edits it directly. Changes happen on a staging branch, get checked on a staging link (Ed sometimes hands that link to a language model for a once-over), and only when he hits ‘Publish’ does staging merge into main and go out to production.
Every branch Ed and his agents are working on is its own live site, with its own URL. So he can build a landing page as a throwaway experiment, send the link round, and ask what people think, and none of it ever shows up in production. Even better, several pieces of work can run at once without tripping over each other.
You can have lots of concurrent pieces of work: a solutions page, a new case study layout, new terms and conditions, a legal section, all on different branches with different agents working on them in isolation, without corrupting your main site.
The vibe-coding horror stories are familiar by now: someone ships to production, breaks it, and spends the night firefighting. In Nomio's case their production site is live but locked to direct edits. Ed can test anything he wants on branches all day, and the live site stays exactly where it was. That’s what made a two-and-a-half-day rebuild feel safe rather than reckless, and it’s the same model that keeps the site changing every day now.
From three hours to five minutes
Adding a single case study in Webflow used to take Ed two or three hours once he’d done all the required configuration. Nomio is case-study-driven, with more than 30 of them already on the site, plus a couple of new posts and edits a week. That’s a lot of hours.
On the new setup it takes about five minutes. Ed points an agent at the CloudCannon docs, tells it he’s using Astro and how the front matter should look, and it builds the collection so anyone can add content afterwards. “Instead of three hours it takes about five minutes, because you just go into CloudCannon and add the content.”
The fact that anyone can do it matters more than the time saved. On a lean team, having one person own the website is a single point of failure.
It’s no longer just ‘Ed’s the guy who updates the website.’ Other people in the business can go into CloudCannon and quickly figure out where content goes.
And because the editable layer stays simple, the engineering underneath can change as much as it needs to. Nomio can push big refactors, restructures and improvements into the site without disturbing the place people go to edit it. That separation was never available in the old workflow, where the content and the build were the same tangled thing.
5 minutes
to add a case study, down from 3 hours
10-15 minutes
from Slack feedback to shipped fix
~300 pages
migrated in 2.5 days
Four agents, four perfect scores
Ed treats Lighthouse as the benchmark, which already puts him ahead of plenty of marketers who never look at it. On Webflow, the scores moved around depending on the page, and there wasn’t much he could do about it. Accessibility and SEO he could push close to 100. Performance was the stubborn one, full of unused CSS and heavy JavaScript he had no real control over. The old site’s Ahrefs SEO score floated in the low 90s and was a pain to lift.
The Astro and CloudCannon setup flipped that. The homepage hits 99-100 across performance, accessibility, best practices and SEO without much of a fight, and the same treatment rolled out across the rest of the site.
This is the branching model doing the heavy lifting again. Rather than tinker on the live site and hope, Ed branched off staging once per Lighthouse parameter and put a different agent on each one.
I had four separate areas within CloudCannon with different agents working on different things. The end result was the site still works, it’s still responsive, the content’s still there, and the score’s 100. I couldn’t imagine trying to do that any other way.
Each branch is a playground. Ed can refactor, change how he delivers CSS and JavaScript, test the result, and if something breaks badly the only thing he has to do is close the branch. The live site never knows it happened. Compare that to the old fear, where he’d try a change, wonder whether it would help or bloat the page, and have to unpick it by hand when it didn’t.
From a Slack emoji to a shipped fix
The same branching model that carried the rebuild now handles the day-to-day. Nomio runs an open feedback culture in a shared Slack channel, so there’s a constant trickle of “there’s a typo here” and “why is the case studies page so slow?” messages. Rather than let those pile up on his to-do list, Ed reacts to the message with a ticket emoji. A Notion agent spots the reaction, writes a ticket from a set schema, and asks whether Claude should take a first pass. It opens a branch, reads the project’s agent reference file, works out the likely cause, makes the change, and drops a staging link back into the channel. From there, Ed can approve it and merge to staging, and then to main.
In practice, it’s exactly how Ed solved the issue of slow-loading case study pages. The pages had little autoplay videos that weren’t lazy-loading, so every one of them fired on load. The agent wrote the ticket, Claude came back inside ten or fifteen minutes with four changes and a recorded video to prove the fix worked, and it went out, all while Ed was working on something else.
The website stops being a bottleneck and becomes a place where you ship every day.
CloudCannon is what keeps all of these parallel workflows safe. The guardrails hold, there’s a proper CMS for new blog posts and everything else, and the agents get on with their work without anyone lying awake over production.
Where Nomio is now
It’s early days, and Ed is honest about it. Traffic is up, though — he puts a lot of that down to more marketing activity, though the two are hard to pull apart: the new site is what gave him the confidence to drive traffic to it in the first place, and to trust it to do its job once people land. There’s plenty of positive feedback, though, and the wins that count are easier to point at. A 200-to-300 page site rebuilt in two and a half days, against an estimate of four to twelve weeks on Webflow. Lighthouse scores at 99–100. New case studies down from hours to minutes. A site the whole company can edit, instead of one that lives on a single person’s to-do list.
For a team with one marketer, that’s a huge lift. Their website used to be the bottleneck. Now Nomio ships to it every day, quickly and safely.
Want to find out more?
Book a friendly demo call with us, and find out how CloudCannon can help you deploy and manage websites more efficiently.
Tom Richardson
Solutions Architect
