:format(webp)){kind=small}
"Go headless" is common advice for marketing websites, including from agencies like ours. It is good advice for some teams and expensive advice for others. This guide looks at the decision from the marketing team's side: what actually changes in your day-to-day work, what it costs, and the signs that it will pay off.
Headless vs traditional CMS: what changes for marketing
In a traditional CMS, the same system stores your content and produces the pages. A headless CMS only stores and manages the content. The website itself is built separately by developers and pulls the content in.
For marketers, that has practical consequences:
You edit in the CMS, usually with a preview of the real page, rather than in a theme or page builder.
You build pages from approved blocks that developers create. You can combine them freely, but a new kind of block needs a developer.
Design changes go through developers. The upside is consistency: nobody can accidentally break the layout or the brand.
Speed and integrations are in your developers' hands, which means they can be made very good, but someone has to own them.
You have an ongoing relationship with a development team, in-house or external, for new blocks and maintenance.
Signs headless is a good fit
The more of these apply to your team, the more likely headless will pay for itself:
You publish often. Several campaign pages or articles a month, where saving developer time on every page adds up.
You run several markets or languages, and need a clear structure for shared and local content.
Speed matters to your results. You spend on paid campaigns, or organic search is a main source of leads.
Brand consistency is hard to keep across many pages and many editors.
The website connects to other systems, such as your CRM, product data or search.
Several websites or channels share content.
Your current platform holds you back: plugin updates break things, security is a worry, or every change needs a developer anyway.
Signs it probably isn't
Headless isn't always the answer. Consider something simpler if:
Your site is small and rarely changes. The setup cost won't be paid back.
There is no budget for developers after launch. A headless website needs ongoing technical care.
Your team wants to change layouts freely, without guardrails, and has no developer access.
You need everything in one product, such as hosting, forms and email, and a single tool covers it.
You need the site live in days, not weeks.
In those cases, a website builder or a marketing-suite CMS such as HubSpot Content Hub is often the better buy. Our guide on how to choose a CMS for a B2B marketing website compares the options.
What it costs
A headless website has three kinds of cost. Ask for all three before comparing it with an all-in-one platform:
The CMS license, which often depends on the number of users, languages and traffic.
The build: the website itself, the library of blocks, the preview setup and integrations such as forms to your CRM.
Running costs: hosting, updates, security, and developer time for new blocks and features.
The build is front-loaded: you pay for it before launch, while the return comes later, from faster publishing, better speed and fewer rebuilds. That is why the decision depends on how much your team publishes over the following years, not on the launch.
The middle ground
The choice isn't strictly all or nothing:
Some headless CMSs come with visual editing, so marketers see the real page while they edit, which narrows the gap to traditional page builders.
Traditional platforms can be used headlessly. WordPress, for example, offers a REST API that a separately built website can read from, so teams can keep a familiar editor while rebuilding the front end.
You can start with one part of the site, such as landing pages, and move the rest later.
What it looks like when it fits
Perk, a B2B travel and spend platform, uses its website as a main acquisition channel, with hundreds of templated pages in nine languages. Because its content already lived in Storyblok, separate from the website's code, Perk could rebuild its whole front end in Astro and move 205 content components across without restructuring its content. Read the Perk rebuild case study.
If most of the signs above describe your team, a headless CMS website is likely worth the investment. If they don't, a simpler platform will serve you better, and that is a perfectly good outcome.