Headless CMS or a traditional CMS: what it costs and what it buys
A website you can edit yourself, with a content management system behind it, is step 03 on our ladder: EUR 1.500-3.500 excluding VAT, four to seven pages, three to six weeks. That price is the same whether the CMS is headless or traditional. The choice between the two changes who can alter what after launch. It does not, by itself, change the invoice.
Headless sounds like the expensive option because it is the one with an API in it. The API is not where the money goes. The money goes into how many pages exist, whether anyone has to log in, how many languages you publish and what has to keep running afterwards. Those move you between steps on the price ladder. The CMS choice moves you between editing experiences.
The difference in plain terms
A traditional CMS keeps your content and your page layout in the same system. The editing screen resembles the page: you change a heading and the heading changes, you drag a block and the block moves. WordPress is the familiar version of this.
A headless CMS keeps only the content. The site is a separate application that asks the CMS for that content over an API and renders it with code we write. The editing screen looks like a form, with a title field, a body field, an image slot and a publish date. Nothing in that form can break the layout, because the layout is not in there.
That is the whole trade. A traditional CMS hands an editor more power and more ways to make the site look wrong. A headless CMS hands an editor fewer decisions and a site that holds its design.
What each one buys
| Question | Traditional CMS | Headless CMS |
|---|---|---|
| Where the design lives | In the CMS, as a theme and a page builder | In the code of the site |
| What an editor can change | Text, images and the arrangement of the page | Text, images and the fields we defined |
| Chance of an accidental mess | Real, and it grows with the number of editors | Low, because layout is not editable |
| Adding another language | A plugin, configured inside the CMS | A language field on each content item |
| Reusing content outside the website | Awkward | Already an API, so direct |
| Adding features from plugins | Many available, quality varies | Fewer, so features get built |
| Where it lands on the ladder | Step 02 or step 03 | Step 02 or step 03, step 04 once accounts or payments appear |
Where the money actually goes
No quote of ours carries a line item called headless. What gets priced is the work: pages designed and built, content modelled into fields, a form that reaches a human, analytics that reports something true. That work barely changes between the two systems at the same size of site, which is why both sit at the same step.
What moves a quote is how much already exists, whether the site needs accounts and payments, how many languages it publishes and what happens after launch. Brand, copy and photography you already own remove work. Missing ones add it. Accounts, a dashboard, an API, a CRM connection, a chatbot or anything that takes a payment is step 04, EUR 3.500-7.500, six to twelve weeks, whichever CMS sits underneath. A checkout is never part of step 03, because that work lives in states rather than pages: a payment that fails, a refund, an order that never completes, a customer record that has to stay correct.
When headless is overkill
If the site is one page and the text rarely changes, skip the CMS. Step 01 is EUR 600-900 and one to two weeks, and the honest version of content management at that size is emailing us the new paragraph.
If it is a small set of pages you want to keep current without asking anyone, step 02 covers it at EUR 900-1.500 in two to three weeks with a basic CMS. A traditional one is the better fit there, because the whole point is that you can move things yourself.
Headless earns its keep in two situations. The design has to stay intact no matter who is editing, or the same content has to appear somewhere besides the website. If neither is true, headless is a preference, and you should not pay more for a preference. How we build the front end is set out on design and engineering.
Process and timeline
Scoping comes first and a fixed quote follows it. We write down the pages, the fields an editor will genuinely need and what has to keep running after launch, then place the project on a step. Build runs to the week ranges: one to two weeks at step 01, two to three at step 02, three to six at step 03, six to twelve at step 04. Step 05, a custom SaaS platform, starts from EUR 7.500 and is only quoted after discovery, because scope, auth, billing, admin and deployment cannot be guessed from a first conversation.
Afterwards, care is EUR 100-300/mo for updates, monitoring, backups and small fixes. It is not a redesign and it is not new features. The two systems differ a little here: a traditional CMS carries a core and plugins that need updating on a schedule, while a headless setup has fewer moving parts facing the public. Neither is maintenance free.
When to spend less
Spend less when you do not yet know what the site has to say. A single-page landing at step 01 that states the offer and captures enquiries will teach you more than a full site built on assumptions, and EUR 600-900 is the cost of finding out. Spend less when the current site works and only the words are stale, because rewriting copy on a site that already functions is not a rebuild.
Spend more when what you are buying sits on the other side of a step boundary, and the boundary is functional rather than aesthetic. Accounts, payments, stored customer data and anything with a logged-in state are boundaries. A nicer editing screen is not.
Questions buyers ask before choosing
Am I locked in if we go headless?
No. You own the code, the repository and the database. The content sits in the CMS and can be exported from it. Hosting can be with us, though that is agreed per customer rather than fixed in advance.
Is a headless site faster for visitors?
It can be, because the page a visitor receives is generated from content rather than assembled by a plugin stack on every request. The larger factors are still image sizes, fonts and how much third-party script gets loaded, and those can be got wrong on either system. Speed is a build decision more than a CMS decision.
Can my team still edit everything?
They can edit everything we turn into a field, which is why scoping time spent listing what will genuinely change after launch pays for itself. Anything nobody will ever touch is cheaper as code. Wanting to rearrange whole pages yourself is a legitimate reason to choose a traditional CMS, and we will say so.
Does the choice affect SEO?
Not on its own. Both can produce clean, indexable pages and both can produce a mess. What decides it is structure, titles, internal linking and whether the pages get found at all. That is a separate purchase. An SEO foundation is a one-off at EUR 450-750 covering Console, analytics, indexation, technical hygiene, titles, internal links and a three to six month plan. Continuing work is SEO growth at EUR 500-800/mo.
We already have WordPress. Is moving worth it?
Only if something is actually hurting, such as editors breaking layouts or plugin updates that keep causing incidents. A migration is priced like a new build at the matching step, because the pages still have to be designed and built and the content still has to be checked.
If you know roughly how many pages you need and what has to work on them, we can name the step and put a fixed price against it. Send us the outline and you will get a quote once scoping is done.
Building something?
JP Studio designs and builds websites, storefronts and product interfaces.