Features

What’s in the box.

Who actually does the design, why your content isn’t stuck in the website, and the full list — design systems, content types, section composition, preview, agent tools, import and the SDK.

001 / Who actually does the design

You still do the design. You stop doing the assembly.

If you’ve spent years hand-building in Elementor, “the agent builds it” is an alarming sentence. So let’s be exact about what moves and what doesn’t.

The agent does not design. It builds. Every design decision — type scale, spacing, colour, how a card behaves at 480px, what a section is even permitted to be — is yours. You make those once, in the design system, and everything built afterwards obeys them. That’s the actual creative work and it stays exactly where it belongs.

What goes away is the assembly. Dragging the section in. Duplicating it. Setting the same padding for the fortieth time. Nudging the tablet breakpoint. Rebuilding the same card pattern on the next project because last time it lived inside a website instead of inside a system.

You were never being paid to drag boxes. You were being paid for judgement.

01 You decide the design.

02 The agent builds inside it.

03 The client fills it with content.

Nobody can change the layer above them.

002 / The content isn’t stuck in the website

Write it once. Use it everywhere it’s needed.

In WordPress the content lives inside the website. It’s a row in that site’s database, wearing that site’s theme. Want it anywhere else and you’re exporting, copying, or maintaining it twice.

Here the content sits on its own and the website is just one thing reading from it. So when the client opens a second location and wants a second site, the events are already there. When they want the menu on a screen in the shop, it’s the same menu — updated once, right in both places. When they eventually want an app, the content layer already exists and someone just has to build the app.

And when they want a redesign in three years, you rebuild the front end. You don’t migrate anything. The content stays exactly where it is.

Most of your clients don’t need an app. That’s fine — this isn’t a reason to buy today. It’s the reason “can we also…” stops being a rebuild.

Take a loyalty scheme.

The points and balances live in whatever system runs them. But everything a customer actually reads is content: the tiers, the rewards list, the how-it-works page, the terms, the “double points this week” banner.

Maintained the old way, that copy exists twice — once in the website, once in the app. So when marketing moves the offer from spend £50 to spend £40, the website changes that afternoon and the app changes whenever the next release ships. For a fortnight the two promise different things. A customer screenshots it. The client rings you.

Modelled once, there is no second copy to forget. Someone edits the offer in one place and every screen that shows it is already correct.

003 / What’s in the box