Headless CMS: when it pays off and which one fits

A headless CMS stores only content. The website builds its pages from it, separate from the CMS. That gives you freedom in design, speed and channels. It also means more components that someone has to look after. We help you decide and build the system you choose.

When a headless CMS pays off

Many content types
Services, industries, references and contacts are linked to each other. A headless CMS models that as data instead of single pages.
Several languages or countries
Translations and country content sit side by side in a structured way. Missing translations stand out.
Several channels
The same content appears on the website, in an app, a customer portal or in data sheets.
Your own frontend
Design, load time and code should come without a theme's constraints.

What your next website could look like

See all work →

When rather not

A small, quiet website
Five pages that rarely change don't need a CMS of their own. A site builder or content in code is enough.
No technical support
A headless setup has frontend, CMS and hosting as separate parts. Someone has to keep them up to date.
Editors want to design pages freely
Headless systems work with fixed blocks. Anyone who wants to lay out every page freely will feel constrained.

In the intro call we set your goal together.

You learn which first step is worth it for you.

Four systems compared

SystemStrengthTo keep in mind
SanityStudio customizable in code, live preview, collaborative editingDatabase only in Sanity's cloud, cost per person
ContentfulWidespread in large companies, many ready-made integrationsInterface extendable only through apps, cost grows with users and languages
StoryblokVisual editor with page preview, headquartered in AustriaStrongly page-oriented, linked data needs more planning
PayloadOpen source, runs inside your Next.js app with your own databaseHosting, backups and updates are on you

Plans and features change. Before a decision we check the current state with each vendor.

How we choose with you

  1. Observe the editorial teamWe talk to the people who maintain content today. What they do often has to be fast.
  2. Record requirementsLanguages, approvals, roles, interfaces and data location. This produces a short list.
  3. Compare costsLicense, hosting, implementation and maintenance over several years. Not just the entry price.
  4. Trial with real contentYour team maintains a real page in the favored system. Then you decide.

In the intro call we set your goal together.

You learn which first step is worth it for you.

What the costs are made of

Four parts determine the cost: the CMS license, hosting of the frontend, implementation and ongoing maintenance. With cloud systems such as Sanity, Contentful and Storyblok you usually pay per person and by usage. Payload has no license fee, but you pay for server, database and maintenance.

Implementation depends on the number of content types, languages and interfaces. Migrating existing content comes on top. After the selection you get a fixed quote.

Reference websites

All work

Intro call

Let's find out together where your growth gets stuck

  • You talk to the team that also does the work. No sales loop.
  • You learn which first step is worth it for you.
  • If your question fits another specialist better, we'll tell you.
Renata WisniewskaManaging Director, AqteloI read every request myself and reply within one business day.office@aqtelo.com

Start a project

What can we help with?

You can select more than one

What you probably want to know

The CMS has no “head” of its own, meaning no frontend. It delivers content through an interface. The website fetches it and builds the pages.

At the start often yes, because the frontend is built separately. In operation, plugin maintenance and many security updates fall away. We calculate both for your case.

Yes. WordPress then delivers only content and Next.js builds the pages. Plugin maintenance remains. It pays off when your team wants to keep WordPress.

Usually Sanity, because we can adapt the studio precisely to your editorial team. With strict data location requirements we look at Payload on your own servers. The decision comes after the selection, not before.

Yes. Because the frontend is separate, the website stays the same. Only the connection and the content model move.

Keep reading