You didn’t build a website. You started a support contract.
Every page builder makes the same trade, and every agency running one ends up maintaining it forever. Here’s the actual argument for splitting content from design.
Page builders trade content control for design control. We don’t.
Every page builder makes the same trade: to let a client change the words, it lets them change the layout too. That single decision is where most of an agency’s ongoing support load comes from.
-
001 /
Plugins vs apps
A plugin is code you install and then own forever — its update cadence, its conflicts, the day its author stops maintaining it. An app is a scoped capability you enable per workspace, maintained by us, removable in one click.
-
002 /
Page builder vs content model
A page builder edits layout, so a content change can also become a layout change. A content model separates the two: the client edits fields, and the layout stays exactly as built.
-
003 /
Maintenance vs hand-over
A page-builder site needs an agency on retainer for updates, security patches and layout fixes. A content-model site is handed over once, and the client’s edits can’t touch the parts that would break it.
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. A menu card is a menu card — the client can’t turn it into a price list, because “a price list” isn’t a thing that exists in the model. What they can do is add the new dish, update the price, swap the header photo, open a second location. On their own, without waiting on 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.
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.
- Team Members Showcase Pro Untested with your version
- Simple Staff List Last updated 2 years ago
- Ultimate Team Builder Requires PHP 7.4 · 12 add-ons
Pick the least bad one. Own that decision forever.
- 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
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, ever.
-
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 /
Support calls
No call that starts with an apology because a content edit reshaped the layout — a content edit can’t reach the layout, because it isn’t part of the model.
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.
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.