Your client wanted to post an event. Not redesign the page.

Contentive is a CMS for agencies who build in WordPress and end up maintaining it forever. Your design stays yours. Your client gets everything they actually need to change — and nothing they can break.

Get early access See what the client sees

Private build. Self-serve opens shortly. Already have a workspace? Log in.

Nothing to patch. Nothing to update. Nothing to explain to the client at 4pm on a Friday.

001 / The problem

You didn’t build a website. You started a support contract.

The build went well. The design was tight. Then you spent an hour on a handover call showing them how to edit a page, and they nodded, and three weeks later the homepage looks like this: a three-column section with four things in it, every heading wrapped onto three lines, mobile completely gone.

So you fix it. For free, because it’s a ten-minute job and they’re a good client. Then you fix it again next month.

This isn’t a training problem. You gave them a page builder, which is a design tool, and asked them not to design. They were never going to win that. They only ever wanted to post a new event, add a flavour, publish an update — the things they said they’d “hardly ever” need and now need every week.

01 · Content change
CLClient09:41

Just adding Thursday’s quiz night to the events section — I won’t need to bother you!

RBYou09:44

Perfect. That’s exactly what we set it up for.

02 · Design problem

Three columns. Four things in them.

03 · Your problem
CLClient16:02

Sorry to bother you, but the website’s gone weird on my phone.

RBYou16:07

No problem at all. I’ll take a look tonight.

A ten-minute job. Not invoiced. Again next month.

The real loop · a content change becomes a design problem becomes your problem

002 / The shift

Content control. Not design control.

Every page builder makes the same trade: to let clients change the words, it lets them change the layout. Contentive splits those apart.

You define the sections. Three columns is three columns — the client can’t make it four, because “four” isn’t a thing that exists in the model. What they can do is add the eighth event, the ninth blog post, the new location, the seasonal flavour. Endlessly, on their own, at midnight, without calling you.

The design system you upload isn’t a suggestion. It’s the boundary. It holds whether the person editing is your senior designer, the client’s office manager, or an agent.

If it’s in the model, they can change it. If it isn’t, they can’t. That’s the whole idea.

003 / How it works

Three steps, and it’s theirs.

  1. 01

    Model

    Define the content types, fields and sections — in the Studio, or hand your schema to your agent and let it do the typing. The API exists the second you save.

  2. 02

    Generate

    Your agent builds the pages and the front end against your uploaded design system. Real components, your tokens, your spacing rules. Not a theme you’ll spend two days fighting.

  3. 03

    Hand over

    This is the part that used to take an hour and a follow-up call. Now it takes a login. There’s nothing to teach, because there’s nothing they can get wrong — and if they do change their mind, one click puts it back.

004 / 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.

005 / Why there’s no chat box

Bring your own agent. We don’t rent you one.

Plenty of tools now put an AI prompt box on the page. Type what you want, watch it build. It demos beautifully and it’s a cul-de-sac — because that agent only knows what’s inside that box.

It doesn’t know your repo. Your conventions. The client’s brand guide. The Figma file. The ticket that started the job. It can’t reach any of the tools you already have connected, because it lives in someone else’s product and only speaks to that product. And every token it spends is billed to you with a margin on top.

Contentive doesn’t have a prompt box. It exposes its tools over MCP, and you point your own agent at them.

Scoped workspace token · stdio or remote OAuth · tools, not a chatbot

It already knows your business

Your agent has your context and your other connectors already wired up. It’s not meeting you for the first time in a text field.

You keep your workflow

Work where you already work. Nothing new to learn, no second place to go, no habits to rebuild around someone else’s UI.

You’re not paying a markup

You’re already paying for your agent. Use it. There’s no per-token spread on top for the privilege of typing into our box instead of yours.

006 / Build, don’t install

Need a feature? Build it. Don’t go shopping for it.

Client wants a team directory, a menu with seasonal items, a case study library, an events calendar with categories. In WordPress that’s an afternoon of evaluating plugins, picking the least bad one, and then owning that decision forever — its update schedule, its bloat, its settings panel nobody understands, and the day its author stops maintaining it.

Here it’s a content model. Define the type, define the fields, build the section. Twenty minutes, it does exactly what the client asked for and nothing else, and it’s yours — no licence, no upsell, no changelog to watch.

You stop assembling other people’s software and start building the thing you were hired to build.

Every plugin you install is a decision you have to keep making.

The shopping trip
team directory 1,284 results
  • Team Members Showcase Pro ★ 4.2 · 40,000+ installs Untested with your version
  • Simple Staff List ★ 4.6 · 20,000+ installs Last updated 2 years ago
  • Ultimate Team Builder ★ 3.8 · 9,000+ installs Requires PHP 7.4 · 12 add-ons

Pick the least bad one. Own that decision forever.

Your blueprints
  • Team directory teamMember · role · location Used on 6 client sites
  • Events calendar event · category Used on 4 client sites
  • Seasonal menu dish · section Used on 3 client sites

Built once. Yours on every site after that.

Build it once · apply it to the next client in a click

007 / What stops being your problem

The work nobody ever paid you for.

  • 001 /

    Plugin maintenance

    No stack of thirty plugins, each with its own update cadence and its own way of breaking. Nothing to patch on a Friday afternoon.

  • 002 /

    Third-party attack surface

    The overwhelming majority of WordPress compromises arrive through a plugin or theme, not core. Fewer third-party dependencies is fewer ways in — and the ones that remain are ours to patch, not yours.

  • 003 /

    Hosting and updates

    No servers, no PHP versions, no “the host did an update and the site went down.” Publishing is publishing.

  • 004 /

    The 4pm phone call

    The one that starts “sorry to bother you, but the website’s gone weird.”

What’s left is the work you’d actually invoice for: new pages, new templates, new campaigns. And the next build starts from your design system instead of a blank theme — the second site you ship on Contentive is much faster than the first.

008 / 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.

009 / What they can and can’t do

The handover call gets a lot shorter.

They can

  • Publish blog posts, events, updates, products, locations — anything you modelled
  • Swap images, rewrite copy, reorder items in a list
  • Rearrange the page from sections you built
  • Schedule a post for Monday
  • Preview the whole thing before anyone else sees it

They can’t

  • Break the grid
  • Install a plugin
  • Change your type scale, your spacing, or your colours
  • Take the site down
  • Do anything you can’t undo in one click

Nothing to train. There’s no wrong button, because you didn’t ship one.

010 / Migration

Bring the WordPress site with you.

Import posts, pages, media and slugs, with URLs intact so you don’t torch the client’s search rankings on day one. You don’t have to sell a rebuild to move a site — though if that Elementor build you inherited is held together with nine plugins and hope, this is a reasonable moment to mention it.

And this is the last time you migrate that content. Next redesign, it stays put.

011 / What’s in the box

What’s in the box.
012 / Who it’s not for

Probably not for you if:

You’re shipping your own site and nobody’s handing anything over. You need the client to have genuine visual design freedom — some do, and a page builder is the honest answer there. Or you’re running an established WordPress shop with a plugin stack you’re happy with and no handover problem. That’s a real position. This isn’t for you.

013 / Pricing

Free to build. £39/mo to go live.

Agency includes 3 live workspaces, then £10/mo per additional live workspace — unlimited workspaces, unlimited seats. Your price never rises when you invite your client.

  • 3 live sites — £39/mo
  • 10 — £109/mo
  • 25 — £259/mo
  • Every seat free

The full matrix →

Build it once. Hand it over once.

Contentive is in private build. If you run an agency and this describes your Tuesday, we want to talk to you.

Get early access

Already have a workspace? Log in.