How it works

Three steps, and it’s theirs.

Model the content, let your agent build the front end, then hand it over. This is what that actually looks like, end to end.

001 / The three steps

Model. Generate. Hand over.

  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.

    schema.json page 
    {
  "page": {
    "label": "Page",
    "fields": [
      { "name": "title",  "type": "string" },
      { "name": "route",  "type": "slug" },
      { "name": "blocks", "type": "array",
        "of": ["hero", "menu", "cta"] },
      { "name": "author", "type": "reference",
        "to": "staffMember" }
    ]
  }
}

    ✓ API regenerated · 0 migrations

  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.

    Joe’s Cafe · Studio Theme
    The theme card in the Studio's Deployments settings, showing the deployed theme version on staging and production and the commands for pulling it into a repository.
  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.

    Joe’s Cafe · Studio Owner
    An entry open in the Studio with its history underneath, listing every save and publish and who made it.

    Nothing here needed you.

002 / Why there’s no chat box

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

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.

003 / What the client gets

An editor with exactly their content in it.

Editable

  • Entries
  • Pages
  • Media
  • Forms
  • Publishing

Not exposed

  • Layout
  • Type scale
  • Spacing
  • Theme code
Joe’s Cafe · Studio The Menu items list in the Studio, with a dish the client has just added sitting at the top of it alongside its price and section.
They can add the eighth dish, and the ninth, and price them.
Joe’s Cafe · Studio The page composer in the Studio: a page built from an ordered list of sections, with one section open and its fields showing.
They can rearrange the page from the sections you built — and there is no control anywhere for anything you didn’t.