Code means git, branches, and pull requests. That is the objection. Here is the answer.
Every platform company is making the same argument against code-first websites, and it is a good one. AI coding tools work in git. Git means branches, commits, pull requests, failing checks, and a review process built by engineers for engineers. Handing that to a marketing team is not empowerment. It is a new job description nobody asked for. That is the objection, and it is the right objection.
Grant it fully
A content manager who wanted to change a headline used to open a page, type, and press publish. On a code-first site the same change is a file edit on a branch, a commit with a message, a pull request, a check that passes or fails, a review, a merge, and a deploy. Every step exists for a reason, and every step is invisible to a person who has never used a terminal. The platform companies are right that this is not a workflow a marketer will adopt.
They are right about what happens next, too. If the workflow is unusable, the team routes around it. Requests go back into chat, a developer becomes the bottleneck again, and the capacity the agent was supposed to add never arrives. The objection is about whether the site can be operated at all.
Where the objection goes wrong
The objection assumes two choices: keep the abstraction layer, or make marketers learn git. The platform companies assume that because the abstraction layer is their product. But the gap the objection describes is exactly the job of a management layer, which is a different product from the one they sell.
Look at what git actually provides. A branch is isolated work in progress. A pull request is a proposal with the change attached. A review is a person looking before it lands. A merge is a permission being exercised. A commit history is a record you can return to. Those are governance concepts with engineering names. The CMS had weaker versions of all five and hid them behind a form.
What the management layer does with them
A management layer takes the same five things and puts them in front of the team in the form the team already understands. A request in plain language becomes a branch the agent works on. A preview becomes the review surface, so nobody reads a diff. Approval by a named role becomes the merge, with a second approver for high-risk work. The record sits on top of the commits: who asked, what context governed the work, who approved, what shipped. Restore is a commit too, landing a prior version with history intact.
| What the CMS gave you | What the code side has | What the management layer does |
|---|---|---|
| Ask: a form field or a ticket to a developer | A branch and a chat window | A plain-language request that opens the branch and briefs the agent |
| Review: a draft preview inside the editor | A diff in a pull request | A preview link as the review surface |
| Permissions: editor and publisher roles | Repository write access | Named roles, risk tiers, second approver for high-risk work |
| Publish: a button | Merge and deploy | Approve by role; the layer merges and tracks the deploy |
| Undo: version history, if the page kept one | git revert, if you know which commit | One-click restore that lands as a normal commit |
The marketer never sees git. Git is still there underneath, and that is the point. The engineering workflow is not removed; it is operated on the team's behalf. Every guarantee that made engineers trust git, isolation, review, permission, and history, is preserved precisely because the layer never bypasses it.
A chat window is not a workflow
Bolting a chat interface onto a repository and calling it a workflow skips every step above. The agent commits straight to the branch, nobody with a role approved it, and the request disappears when the window closes. That is git with the governance removed, which is worse than either the CMS or the pull request.
Why this is not the abstraction layer again
This is not a new CMS in different clothes. The abstraction layer replaced the code with a model of the code, so anything the model did not express could not be changed. The management layer leaves the code as the source of truth and governs the work done to it. The agent can change a layout, a redirect, and a schema block in one pass because nothing stands between it and the repository, and the team still gets review, approval, and restore.
That is also why the layer does not need to own the agent. Bring your own agent (BYOA): branch, preview, approval, and record are the same whether the work is done by Claude Code today or something else next year. Dispatch governs the work; other systems execute the work.
So, code means git
Yes. Git, branches, and pull requests are what make a code-first site trustworthy, and they are not something a marketing team should ever have to touch. The answer to the objection is not to keep the abstraction layer. It is to put a management layer above the repository so that asking, reviewing, approving, publishing, and undoing look the way they did in the CMS while running on guarantees the CMS never had. If your site is already on code, connect it to Dispatch and the first governed request can ship this afternoon, free for one website.
Do marketers need to learn git to run a code-first website?
No. Git stays underneath, operated on the team's behalf by a management layer. A plain-language request becomes a branch, a preview becomes the review, an approval by a named role becomes the merge, and restore lands as a normal commit. Nobody opens a terminal.
Is a management layer just a CMS with a different name?
No. A CMS replaced the code with a model of the code and could only change what the model expressed. A management layer leaves the code as the source of truth and governs the work done to it: who asked, who approved, what shipped, and how to undo it.
Do pull requests still happen when a management layer is in place?
Yes. Every governed change is still a branch, a pull request, and a merge in your repository. The layer creates and completes them, so the team sees a request, a preview, and an approve button rather than a diff.
Can we use our own AI coding agent?
Yes. Dispatch is bring-your-own-agent. The workflow is the same whether the work is done by Claude Code today or another agent next year.
Dispatch Team
Writing about AI-powered websites, AI governance, and collaboration, helping teams turn AI from scattered experiments into shared organizational capability.