A prospective client told us last month that a previous agency had pitched them a "headless architecture" for their new company website. When we asked why, they said, "We're not sure, but it sounded modern." That's not a great reason to choose any technology, so let's unpack it.
Traditional CMS in one paragraph
A traditional CMS like WordPress, Joomla or a custom admin panel handles everything in one place. You write content in the admin area, and the same system turns it into web pages using a theme or templates. Content and presentation are tightly connected.
Headless CMS in one paragraph
A headless CMS only stores and manages content. It has no front end of its own. Instead, it offers the content through an API, and a separate application (a website, mobile app, kiosk screen, smartwatch, whatever) fetches and displays it. Popular examples include Strapi, Sanity, Contentful, Directus and Payload. WordPress can also be used in headless mode.
When headless makes sense
- Multiple channels. The same content needs to appear on your website, mobile app and maybe in-store screens. Write once, publish everywhere.
- A modern front end is required. Your product team wants the site built in Next.js, Nuxt or Astro for performance or developer reasons.
- Large content teams. Structured content models, editorial workflows and multiple languages are often easier to manage in a dedicated headless CMS.
- Security and scale. The public website can be static files on a CDN, with the CMS hidden away. There's less surface to attack and very little that can fall over under traffic.
When it's overkill
- A small business site with a few pages. You'd be paying for two systems where one would do.
- Non-technical teams who want visual editing. Headless editors are getting better at previews, but many still feel like filling in a database form compared to WordPress's block editor.
- Tight budgets. Headless projects usually take longer to build and need developers for changes that would be a simple theme setting in a traditional CMS.
- Hosting simplicity. You'll often run two services (the CMS and the front end), sometimes on different platforms.
The cost difference
As a rough guide, a headless build often costs 30 to 60 percent more than an equivalent traditional build, because you're effectively building two applications and connecting them. Running costs can also be higher if you pay for a hosted CMS plan.
A middle path
For many clients, we build a traditional server-rendered site with a lean custom admin panel, like this one. Content editing is simple, pages are fast, and there's one system to maintain. If they later need a mobile app, we add a small API on top of the same database. That gets most of the benefits of headless without paying for it on day one.
Questions to ask
- Will this content appear anywhere other than the website within the next two years?
- Who will edit content, and how comfortable are they with structured forms?
- Do we have developers available for ongoing changes?
- Is there a specific performance or security requirement that a traditional setup can't meet?
If you answer "no" to most of these, a traditional CMS is probably the right call. Headless is a great tool. It's just not the default answer it's sometimes sold as.
