Which CMS Should You Choose – and Do You Even Need One?

The CMS choice is often made on the wrong basis: a comparison of feature lists where the one with the most checkmarks wins. But most CMSs handle most things – the difference that shows up in daily work is about how editors actually work and what the solution costs to own over several years. Here’s the choice from a buyer’s perspective, including the often-forgotten option of having no CMS at all.

Traditional vs. headless – seen from daily life

The difference is clearest if you look at two people’s workday.

The editor’s day. In a traditional CMS, the editor sees the page while editing it: text, image, and layout in one place, with the result right in front of them. It’s reassuring and asks little of the technology. In a headless CMS, the editor instead fills in structured content – headline, body text, image as separate fields – without seeing the finished page at the same moment. Many find it an adjustment at first, and a relief later, provided a preview is in place from the start.

The developer’s day. A traditional CMS ties the developer to the platform’s template system and conventions; a lot moves quickly within the boundaries, but anything outside them becomes cumbersome. A headless CMS leaves the frontend completely free – any framework, any design – at the cost of more having to be built from scratch.

So the core question isn’t which is “most modern”, but where your emphasis lies: one website with editors who want everything in one place, or content that needs reuse across multiple channels by an organization with developer capacity. A common mistake is choosing headless because it sounds future-proof, then discovering the editorial team misses the simplicity they were used to – without actually using the multi-channel strength that justified the choice.

The cost that separates the options – and the one that doesn’t

A common misconception is that the license cost is decisive. In practice, the options differ more in hosting and maintenance than in purchase price.

• License. Some platforms are free at the core, others cost anywhere from a few thousand kronor a year to six figures for enterprise platforms with personalization and support.
• Hosting. A traditional CMS with a database requires more ongoing operations than a statically generated site; headless often means both a CMS subscription and separate hosting for the frontend.
• Maintenance hours. This is where the real cost hides. A “free” CMS with many plugins and constant updates can, over time, cost more than a paid platform with fewer moving parts.

The point: calculate the three-to-five-year total cost, not what it costs to get started. A cheap build that requires a developer for every change can end up more expensive than a pricier platform where the editorial team is self-sufficient.

When you don’t need a CMS at all

The third option is almost always forgotten: skipping the CMS entirely. If content changes rarely and the people changing it are developers anyway, pages can be built directly in code and version-controlled like the rest of the system. The result is a fast, secure, and cheap site with a minimal attack surface – no admin to protect, no database to attack.

A concrete example: a tech company’s twenty-page marketing site, updated once a month or so by the same team that builds the product. A CMS there would mostly be a cost and a security surface to maintain. Without a CMS, they get a faster site and a lower hosting bill – but the day a non-technical editor needs to publish daily, the lack of editing tools becomes an obstacle. It’s exactly that trade-off that decides.

A requirements checklist based on how you work

Make the decision based on how you work, not on what’s popular. Ask the questions: How often does content change, and who changes it? Does content need to reach more channels than the web? How much developer capacity do you have on an ongoing basis? And what can the budget bear over five years, everything included?

The answers usually point clearly toward one path. Want help setting the requirements and calculating the total cost? Our services look at editors’ daily work, your integration needs, and hosting together. Feel free to get in touch with how your content work looks today and we’ll give you a recommendation.