A headless CMS is a content management system that stores and serves content through an API, without a built in front end for displaying it. Developers build the website or app separately and pull content in, so the same content can feed a site, an app and other channels. Sanity, Contentful and Strapi are common examples.
Why It Matters for Your Website
A headless setup gives engineering teams a lot of control. It suits companies with complex content models, several products or apps sharing the same content, or strict technical requirements. The tradeoff is that the front end is custom code. New page layouts, design changes and many fixes need a developer, which can leave a small marketing team waiting in a queue.
So the real question is not whether headless is modern. It is who needs to change the site, how often, and with what help. If your marketing team wants to launch pages and run experiments on its own, a visual builder with a CMS, such as Framer, is often a better fit. Your product docs or app content can stay headless while the marketing site moves. If your content has to feed a product, an app and the site at once, headless can be worth the overhead.
A common pattern at funded companies: engineering chose a headless stack early because it matched the product codebase. Two years later the marketing team has grown, launches are more frequent, and every landing page is a sprint ticket. Nobody made a bad call. The needs changed. That is often the moment to revisit the setup, either by improving the editing experience on the headless build or by moving the marketing site to a visual builder.
What Good Looks Like
The content model matches how your team thinks: products, case studies, team members, posts, not generic blocks.
Editors can preview changes before they go live.
Marketing can publish routine updates without filing a ticket.
There is a clear owner for the front end code, and a plan if that person or agency leaves.
Page speed, metadata and redirects are handled in the front end, since the CMS does not do it for you.
Costs are clear across CMS seats, hosting and ongoing development time.
Questions to Ask an Agency
Why headless for us, rather than a visual builder with a built in CMS?
What will our marketing team be able to change without a developer?
Who maintains the front end after launch, and what does that cost each month?
How will preview, SEO metadata and redirects work?
If we part ways, how easily can another team pick this up?
How Goodspeed Handles It
We build on both sides of this choice, and we will tell you which one fits your team. Our Sanity CMS development guide explains when a headless build is worth it and what it takes to run well. For many marketing led sites, we recommend Framer instead, because it puts publishing back in the hands of the people who own the site.
Related Terms
Website Migration
Website Redesign
Website Maintenance
Landing Page