What the choice of CMS really decides
A content management system, or CMS, is the tool your team uses to change the website without a developer. The choice shapes daily work for years: how quickly a new page goes live, whether marketing can build a campaign page alone, how safely the site is updated and what it costs to keep running.
It decides less about how the site looks than most buyers expect. Nearly any design can be built on nearly any modern system. What differs is the editing experience, the flexibility of the content, the hosting and the amount of maintenance. Those are the things to compare.
Start with the people who will edit
- 01
Who will edit, and how technical are they?
Why it mattersA system that suits a developer can defeat an office manager. Match the tool to the least technical regular user.
- 02
How often does content change?
Why it mattersA site updated daily needs fast, safe editing. A site updated twice a year can accept a simpler arrangement.
- 03
Do editors need to build new page layouts?
Why it mattersIf yes, you need a visual page builder or a flexible set of blocks. If no, structured forms are quicker and harder to break.
- 04
Is approval needed before publishing?
Why it mattersDrafts, review steps, scheduled publishing and a history of changes matter in regulated or larger organizations.
- 05
How many languages?
Why it mattersMultilingual content, and right-to-left languages in particular, are handled very differently from one system to another.
Describe your content before you look at products
List the kinds of thing you publish: services, case studies, team members, articles, locations, products, events. For each, note the fields it needs and how it relates to the others. A case study belongs to an industry and mentions services. A team member writes articles.
This list is called a content model, and it is the best test of any system. A simple brochure site with a handful of pages can live anywhere. A site with many related content types, reused across pages and languages, needs a system built for structured content. Trying to force the second kind into a tool designed for the first is the most common cause of an unhappy migration later.
Also list where content must go besides the website: a mobile app, email, screens in a showroom, a partner portal. If the same content feeds several places, that points toward a headless system.
The four kinds of system
| Kind | How it works | Strong when | Watch for |
|---|---|---|---|
| Hosted website builder | Design, content and hosting in one subscription | Small teams, marketing sites, speed of launch | Limits on custom features and on moving away |
| Traditional open-source CMS | You host the software, extended with themes and plugins | Content-heavy sites, wide choice of developers | Updates and security are your responsibility |
| Headless CMS | Content is stored separately and delivered to any front end | Structured content, several channels, custom design | Needs developers for the front end and its hosting |
| Custom-built | An editing system made for your content and workflow | Unusual workflows, deep integration with internal systems | You carry the full cost of building and maintaining it |
Our comparison of a headless CMS and a traditional CMS goes deeper into the second and third rows, and Webflow against a custom build covers the first.
Compare the cost of ownership, not the licence
A free system can be the expensive choice, and a paid one can be the cheap one. Add up what the site will cost to run, not only to launch.
- Licence or subscription. Often priced by users, content volume or traffic. Check what happens to the price as you grow.
- Hosting. Included with hosted builders. Separate, and your responsibility, for self-hosted and headless setups.
- Updates and security. Self-hosted systems and their plugins need regular updates. Someone must be named and paid to do them.
- Development for changes. How much can editors do alone, and what needs a developer? The answer drives the yearly cost more than any licence.
- Leaving. Can you export all content in a usable format? A system that is easy to enter and hard to leave has a hidden price.
A worked example
A professional services firm chooses a system
This example is invented to show the reasoning. A consultancy with offices in two countries is replacing a website that only its former agency could edit.
- EditorsTwo marketing staff publish articles weekly and update team and service pages. Neither writes code. Partners must approve articles before they go live.
- ContentServices, industries, case studies, people, articles and offices, all related to each other, in English and Arabic.
- ShortlistA hosted builder is ruled out because its handling of related content in two languages is weak. A traditional CMS and a headless CMS remain.
- TestBoth candidates are given the same task: publish a case study in two languages, link it to a service and two people, and send it for approval. The marketing staff do the test themselves.
- DecisionThe headless system wins on structure and languages. The firm accepts that layout changes will need a developer, and budgets a small monthly retainer for it.
The decision took one afternoon of testing, and it was made by the people who will use the system. The retainer is written into the plan, so the cost of ownership is known before the build starts.
Test the shortlist with a real task
Demonstrations show a system at its best. A short trial shows it with your content. Ask each candidate, or the company proposing it, to set up one of your real content types and let your editors try three things.
- 01
Create and publish
Add a new item with text, images and links to related items. Time it, and note every moment of confusion.
- 02
Change something structural
Add a field, reorder a page or create a new landing page. See how much an editor can do without help.
- 03
Recover from a mistake
Publish an error, then roll it back. Check that history, drafts and permissions behave as promised.
If a company refuses a trial of this kind, treat the refusal as information.
CMS selection checklist
CMS selection checklist
0 of 10 checkedWhat to do next
Write the content model first. It takes an hour with the people who run the site, and it makes every later conversation shorter. If you are also planning the site itself, our website project brief builder collects the rest.
When no existing system fits the workflow, a custom CMS may be justified, and we will say plainly when it is not. Send us your content list and we will suggest which kind of system to test.
Common questions
Is a headless CMS better than a traditional one?
Neither is better in general. A headless system suits structured content, several channels and a custom front end, and it needs developers for layout changes. A traditional system gives editors more control over pages and has a larger pool of ready-made extensions, with more maintenance to manage. The right choice follows from your content model and your team.
Can we change CMS later without rebuilding the website?
Sometimes. With a headless setup, the front end and the content store are separate, so one can be replaced without the other, though the work is still significant. With traditional systems and hosted builders, design and content are bound together, and changing system usually means rebuilding. Either way, clean structured content makes any future move easier.
Do we need a CMS at all for a small website?
If the content changes a few times a year and a developer is on call, a site without a CMS can be faster, safer and cheaper to run. The moment non-technical staff need to publish regularly, a CMS pays for itself. Decide by counting how often content really changes and who makes the changes.
Who should own the CMS account and the content?
Your organization should hold the main account, the billing relationship and administrator access, with the company that builds the site added as a user. Ownership and licensing terms are defined in the project agreement, so check there how themes, custom code and content are treated before the work starts.
How do we judge whether a CMS is secure?
Ask who applies updates and how quickly, how access and permissions are controlled, whether two-step sign-in is supported and how backups are taken and restored. For self-hosted systems, the answer depends largely on your own maintenance. For hosted ones, read the provider's published security information and confirm it meets your organization's policies.
