What is a headless CMS, and does a small business need one?

The term usually turns up in a quote. Somewhere between the line items it says “headless CMS”, nobody explains why it is there, and because it sounds technical nobody asks.

The question underneath it is rarely technical, though. It is this: do I need to understand this, or is it something developers settle between themselves?

Partly. Some of it genuinely is just tooling and none of your business. The rest decides how much work you will do a second time in three years.

What is a headless CMS?

A headless CMS is a system your content lives in that has no say in how it looks. Text, prices and images are managed there and fetched from the outside. Whatever displays them is a separate, replaceable thing: a website, a second website, an app, a screen in a shop.

“Headless” means without a head. The head is the presentation, and it is missing on purpose.

In a traditional system the two are one piece of software. Your content sits inside the same application that draws the page, and the template has a say in how the content is structured at all. As long as nothing substantial changes, you never notice. You notice at the first rebuild.

What it changes day to day

A new design does not cost you your content. When the site is rebuilt, everything written stays. What gets built again is the presentation. In a conventional move that is the part that eats the most time and gets underestimated most often, because someone carries the pages across by hand.

You write things once rather than several times. The same description of a service can sit on the website, appear in an app and run on a screen. You maintain one version instead of three that drift apart.

The structure holds. You get fields rather than a blank page: a service has a name, a description, a price. That sounds like less freedom and turns out to be a relief, because you can no longer dismantle a layout by pasting text in from a document.

Pages arrive finished. Because the content is fetched in advance and the pages are prepared ahead of time, nothing has to be assembled while somebody waits. Visitors feel that, and search engines measure it.

Where the difference becomes obvious

margeoma.ch is a cleaning company. Their site exists twice: a classic version, calm and direct, and a 3D scroll story you move through. Visitors choose which one they want and can switch at any point.

These are two different websites, not two variants of one. They share nothing in the way they look. What they share is the content: services, process, packages, questions. It is written once in the CMS and appears on both.

In a traditional system that would not be one project but two. And within a few months one of them would be out of date, because somebody forgot to make a change twice. That is the actual point. Not that it looks better, but that the second version does not create ongoing work.

When you do not need one

If your site has five pages, changes twice a year and will still have five pages in three years, the difference is small for you. What does not pay off in that case is the setup you do at the start.

If your current system works and is not slowing you down, “headless” is not a reason to rebuild. The word on its own is not a mark of quality. It describes a way of building, and that way is only better when it matches what you intend to do with the site.

It also takes nothing off anyone’s plate. A system where the content sits cleanly separated still will not keep your opening hours current by itself.

What to ask before you agree to it

Four questions, and none of them need a technical background.

What does editing look like? Ask to see the screen you will be sitting in front of, not the architecture behind it. If nobody wants to show you that screen, that is your answer.

What happens when I want a new design in two years? You want to hear that the content stays where it is. If the answer is “then we migrate everything”, it is not a headless setup, whatever it is being called.

How does my content come back out? Any serious system can export. Ask while you are deciding, not when you want to leave.

And: what can I change myself, and what can I not? That line should be clear before the build starts, rather than discovered the first time you cannot make a change on your own.

If we get to the end of a conversation and the honest answer is that your current setup is fine, that is what we will tell you. It happens, usually with sites that rarely change, and it is the right answer when it does.