Why we moved the CMS into ChatGPT
Most internal CMS work is not editing — it is the friction around editing. Opening a dashboard, finding the draft, remembering which fields matter, and switching context away from the writing itself.
What changed
The CMS became a set of tools rather than a set of screens. Employees describe what they want in the same conversation where the writing happens, and the backend keeps ownership of state, scheduling and publishing.
What we deliberately kept out
The interface generates content. The backend decides what is valid, what is published, and what is synchronised. Keeping generation and authority apart is what stops an assistant from quietly becoming the source of truth.