The short answer
A Conversational CMS (C-CMS) is a way of managing a website where you describe a change in plain language, the system prepares it, and nothing goes live until you approve a preview. The chat replaces the admin dashboard as the interface. The content, the design rules and the decision to publish stay where they were: with you.
In practice that means a message like “Change our opening hours to 9–17 on Fridays and add a note about the holiday break” instead of finding the right page, the right block and the right field in a CMS.
Two things a Conversational CMS is not:
- Not a chatbot for your visitors. Some vendors use “conversational” for websites that answer visitors in a chat window. A C-CMS is about the people who run the site, not the people who visit it.
- Not a component CMS. C-CMS, with a hyphen, stands for Conversational CMS. Component content management systems, used for technical documentation, are a different category.
How a Conversational CMS works
Every change follows the same four steps, whether it is a phone number or a new landing page.
- DescribeYou write what you want in the chat, in your own words. You can attach photos, documents or a link.
- PrepareThe system works out which pages and components are affected and builds the change inside the site’s existing design system: its colours, type, spacing and modules.
- ReviewYou get a preview of the changed pages before anything is public. If it is not right, you say what to adjust and get a new version.
- Approve and publishOnly your approval sends the change live. Until then, your public website stays exactly as it was.
The key difference from a dashboard is where the knowledge sits. In a traditional CMS you need to know where things are and how the editor works. In a Conversational CMS you only need to know what you want to change.
Five stages of website management
Conversational CMS is the fourth of five stages in how websites are run. Each stage changes one thing: who operates the site and through what interface.
| Stage | Interface | Who does the work | Role of AI | What you still maintain |
|---|---|---|---|---|
| 1. Traditional CMS | Admin dashboard with pages, blocks and fields | You, inside the dashboard | None | Software, plugins, themes, database, hosting |
| 2. Headless CMS | Content forms plus a separate, custom-built front end | Editors fill forms, developers build the site | None | Content model, front-end code, integrations |
| 3. AI-assisted CMS | The same dashboard with AI writing and image tools | You, inside the dashboard, with help | Drafts text and images on request | Everything from stage 1 or 2 |
| 4. Conversational CMS | A chat | The system prepares, you approve | Turns a request into a finished, previewed change | Your content and your decisions |
| 5. Agentic CMS | Goals and rules instead of individual requests | AI agents act on their own within limits | Plans and carries out multi-step work | Goals, rules and oversight |
The step from stage 3 to stage 4 is the important one. In an AI-assisted CMS the dashboard stays and AI helps you fill it. In a Conversational CMS the dashboard is no longer something you have to operate.
Conversational CMS vs traditional CMS
A traditional CMS gives you full control and asks you to operate it. A Conversational CMS asks you only to describe and approve, and someone else operates it.
| Traditional CMS (e.g. WordPress) | Conversational CMS | |
|---|---|---|
| How you make a change | Find the page, block and field, edit, publish | Describe the change, review a preview, approve |
| What you need to learn | The editor, the theme, the plugins | Nothing beyond describing what you want |
| Who keeps the system updated | You or your agency | The provider |
| Design consistency | Depends on who edits and how much the theme allows | Changes are built inside the site’s design system |
| Typical delivery | Pages rendered by the server from a database | Often static HTML files, no public admin login |
| Fine control over layout | High | Limited to what the design system allows |
| Best for | Teams that publish daily and want to operate the tool | Businesses that change their site regularly but do not want to run software |
Modern CMS platforms also offer roles, review workflows, version history and static export. The difference is not a single feature. It is who has to operate the system day to day.
Full comparison: WordPress vs. TypeSomething.
Conversational CMS vs AI website builder
An AI website builder is built for day one: it turns a prompt into a first version of a site. A Conversational CMS is built for every day after that: it keeps an existing site up to date.
The line is blurring, because some builders now also accept chat requests. Three questions separate the two:
- What happens after the first version? With most builders you continue in their visual editor. With a Conversational CMS the chat stays the main interface for the life of the site.
- Does a change respect the design or regenerate it? A Conversational CMS changes one thing inside fixed design rules. A prompt to a builder can rework more than you asked for.
- Is there a preview and an approval step? In a Conversational CMS every change waits for your approval. In many builders, edits are live as soon as you save.
If you need a site this afternoon and will rarely touch it again, an AI website builder is a reasonable choice. If your site changes every month, the second and third questions matter more than the first.
Conversational CMS vs Agentic CMS
The difference is who starts the work. In a Conversational CMS a person asks for each change and approves it. In an Agentic CMS, AI agents receive goals and rules and decide on their own which changes to make.
| Conversational CMS | Agentic CMS | |
|---|---|---|
| Who starts a change | A person, with a request | An agent, based on a goal (e.g. “keep the event page current”) |
| Scope of one action | One described change | Several steps: plan, write, check, publish |
| Human role | Approves every change before it goes live | Sets goals and limits, reviews by exception |
| Main risk | A misunderstood request, caught at preview | An agent acting outside what you intended |
| Maturity in 2026 | In use for business websites | Mostly pilots and narrow tasks |
The two terms are often used as synonyms. We find it more useful to keep them apart, because the approval step changes who is accountable for what is published.
TypeSomething is a Conversational CMS by design: every change waits for a human to approve it. Agentic features, such as suggesting updates on its own, can sit on top of that model without removing the approval step.
Conversational CMS vs headless CMS
A headless CMS separates content from presentation. A Conversational CMS separates the person from the software. They solve different problems, and they can work together.
A headless CMS such as Contentful, Sanity or Strapi stores content and delivers it through an API. Developers build the website on top of it. Editors still work in content forms, and every new page type needs a developer.
A Conversational CMS takes the editor out of the forms. Under the chat there can be a static site generator, a headless CMS or plain files in a repository. What the person running the site sees is the same in every case: a request, a preview and an approval.
Choose headless when you publish the same content to many channels (website, app, kiosk) and have developers on the team. Choose a Conversational CMS when the website is the main channel and you do not want to run a development team for it.
Architecture, security and human approval
A Conversational CMS usually has two separate layers. The editing layer is private: the chat, the AI, the build process and the previews. The public layer is what visitors get: on a static architecture, plain HTML, CSS and images served from a host or CDN.
This split changes the security model:
- What disappears from the public site: the admin login page, the database behind every page view, and the plugins that run on each request. These are the most common entry points in traditional CMS attacks.
- What still needs protection: the editing service, the build system and its dependencies, contact forms and the hosting account. A static site has a dramatically reduced attack surface, not zero.
Human approval is the second safeguard. AI can misread a request. In a Conversational CMS a misread request ends as a wrong preview, not as a wrong live page, because nothing is published without approval.
When a Conversational CMS fits, and when it does not
A Conversational CMS fits a business whose website changes regularly but is not its product. It fits less well where the website is an application or where a large team publishes all day.
It shows best on company websites. If yours runs on WordPress, see what moving to a Conversational CMS looks like. If you have nobody on the team who looks after the website, start with a company website from scratch.
| Good fit | Needs a different approach |
|---|---|
| Company and service websites, from a few pages to a few hundred | Large online shops with complex catalogues, stock and checkout logic |
| Simple online shops, for example selling products set up in Stripe | Newsrooms publishing dozens of articles a day |
| Changes a few times a month: offers, team, events, blog posts | Teams that want to design every layout themselves, pixel by pixel |
| No in-house developer, or a developer whose time is better spent elsewhere | Sites with user accounts, logins or member areas |
| A clear brand that should stay consistent across every change | Projects that must be self-hosted on your own infrastructure |
If most of your needs land in the right column, you have two good options. One is a traditional or headless CMS. The other is a custom build by one of our implementation partners, such as hmmh.pl, which can develop shops, integrations and member areas beyond our standard modules.
How TypeSomething does it
TypeSomething is a Conversational CMS delivered as a service: our team builds the site, and from then on you run it through a chat.
- Start from a brief or your current site. You fill in a short brief or send us the URL of your existing website. We build a new static site from custom modules, not a template.
- Pay when you approve. No account or sign-up is needed to start. You pay only once you approve the concept.
- Manage it in chat. Each request is prepared inside your site’s design system and shown as a preview first.
- Approve and publish. One approval publishes plain static pages, with no plugins and no public admin panel.
- On the VIP plan there is a dedicated person behind the chat. They help you publish new content and optimise it.
What you should know before choosing us:
- TypeSomething is Website as a Service. Plans are monthly and each includes a monthly AI allowance. There is no limit if you connect your own API key.
- If you cancel, you keep the rights to your content and photos. The site itself, its code and design, stays with the service.
- Simple online shops are possible, for example with products and payments set up in Stripe.
- Anything beyond our standard modules, such as larger shops, integrations or member areas, can be developed by our implementation partners, such as hmmh.pl.