Our own website had become hard to manage, held together with paid plugins, and inconsistent from page to page. Here's how — and why — we rebuilt it using AI-native ways of working.
The problem
For a while, our website did its job well enough. But under the surface, it had quietly become a source of friction rather than something we could rely on.
Every small change — fixing a typo, updating a photo, publishing a new post — meant logging into an old admin panel, hunting through menus, and hoping nothing else on the page broke when you hit save. It wasn’t something you could hand to just anyone on the team; it took someone who already knew where things were.
The site also leaned on a long list of third-party plugins to do fairly basic things — image galleries, contact forms, small styling tweaks. Those plugins needed regular paid upgrades just to keep working and stay secure, which meant real, ongoing cost for features that should have been simple.
And because pages had been built up over the years by different people at different times, the site had drifted: fonts, spacing, and layout weren’t quite consistent from one page to the next. Nothing dramatic on its own, but it added up to a site that felt more patched-together than deliberate.
Digging through a nested admin menu, finding the setting behind a locked plugin tier, hoping the fix doesn't quietly break something three plugins over — a database and plugin maze no AI could work with either.
Describing the change in plain language to an AI that can read and edit the whole site directly, then watching the live preview update in front of you — something a WordPress database behind a plugin maze never let us do.
Click a problem below to see what we actually did about it:
We moved off the old admin panel entirely. Content now lives as plain, readable files anyone on the team can open, edit, and understand — no specialist training required to fix a typo. Before, only a handful of people had admin access, and even they were restricted to an "author" role. Now anyone in the org can propose a change through a pull request, reviewed under rules we set ourselves.
The new site is a small number of simple, self-contained pages with nothing else it depends on to run — no plugin ecosystem, no chain of add-ons that can quietly break each other.
Every page now pulls from one shared design system. Change something once — a colour, a button, a layout rule — and it's consistent everywhere, instead of drifting page by page. Updating the old site's styling meant briefing an external agency and waiting through weeks of back-and-forth. Now we update our own styleguide in-house, AI-assisted, in an afternoon.
There are no plugins left to license or patch. What used to be a recurring cost just to keep the site secure is now zero, permanently.
What we changed
Rather than keep patching the old system, we rebuilt the site from the ground up — as a small set of simple, fast pages, with the actual content (articles, case studies, page text) stored as plain, readable files instead of buried inside a database behind an admin panel. Here’s how that actually went:
WordPress export
Every past article and page pulled out as a starting point.
Branding agent drafts the plan
An in-house styling & branding agent laid out a plan that matched our identity.
AI-assisted migration
Old content carried across and rebuilt onto one consistent design.
First draft ready
Every past page live on the new system, ready to review.
That’s the whole team it took: one skilled person, working with AI and that WordPress export, plus a styling and branding agent we’d already built to keep the plan on-brand. We used AI-assisted development throughout — not to write our words for us, but to move fast through the mechanical, tedious parts of the job: catching mistakes before they ever went live, and rebuilding every page to follow one consistent design instead of several drifting ones.
Every page on the new site is now built from the same small set of shared building blocks. Change something once — a colour, a button, a layout rule — and it applies everywhere automatically, instead of needing to be re-applied by hand across dozens of pages.
What’s different now
- Built as plain files an AI can actually read and edit — not a database locked behind a plugin-and-panel CMS that no AI tool could reason about. That’s what makes everything below possible.
- No plugins to license, patch, or pay to keep working. The site doesn’t depend on any third-party plugin ecosystem at all.
- Publishing something new is just a text file and a couple of images — no database, no admin panel to relearn, no risk of accidentally breaking something else on the page.
- Every page shares one consistent look, because they’re built from the same shared components rather than pieced together one page at a time.
- Changes are checked before they go live. Every update gets a preview version to review first, so nothing reaches the real site by accident.
The page you’re reading right now is a direct product of that same process — a new part of the site that simply didn’t need a dedicated web project to exist. That’s the actual point of AI-native thinking, as we use it: not replacing judgement, but removing the friction between deciding to do something and actually doing it.