Headless CMS for marketing teams

Every few months a founder tells us their marketing team is "blocked on the dev team" and asks if a headless CMS will fix it. Sometimes yes. Often the real problem is that nobody decided who owns the homepage, and no tool solves an org chart. Here is the honest version of what a headless CMS does, what it costs, and when it is the wrong call.

What "headless" actually means

A traditional CMS like WordPress bundles two jobs: a place to edit content and a place to render the website. Headless splits those apart. The CMS becomes a content database with a friendly editor on top, and it hands content to your site through an API. Your developers build the front end separately, usually in something like Next.js.

The practical upshot for a marketing team: your editors get a clean interface to write pages, blog posts, and landing pages, and the live site is a fast, modern front end that your engineers fully control. Nobody is fighting a theme or a pile of plugins.

The tradeoff is that "render the website" is now your team's problem. With WordPress, you install a theme and you have a website. With headless, the website does not exist until someone builds it. That is the whole deal in one sentence: more control, more upfront work.

When a headless CMS is the right call

A few situations where we'd push you toward headless without much hesitation:

• You publish to more than one place. A website, a mobile app, in-store screens, a newsletter. Headless lets the same content feed all of them from one source. This is the original reason the approach exists.
• Performance and SEO matter to the business. A well-built headless front end on Next.js gives you fast page loads and clean control over metadata, structured data, and Core Web Vitals. This is exactly the kind of performance and SEO engineering that moves the needle. Google notices, and so do your conversion rates.
• Your brand or interactions are custom. If your landing pages need real design, animation, or interactive components, you want engineers building in real code, not wrestling a page builder into submission.
• You have, or are hiring, developers. Headless assumes someone maintains the front end. If that is already true, the model fits.

When it is the wrong call

Equally honest: plenty of teams should not go headless.

• A five-page brochure site that rarely changes. WordPress, Webflow, or Squarespace will serve you fine and cost less to run.
• Marketing wants full drag-and-drop control with no developer in the loop. Headless can give editors a lot, but it does not turn them into page designers. If "I want to rearrange the whole layout myself at 11pm" is a hard requirement, look at Webflow first.
• There is no budget for ongoing maintenance. A custom front end needs occasional care. If you want to build it and never touch it again, this is not your model.

The options worth shortlisting

There are dozens of headless CMS products. For a marketing team we'd usually look at four:

• Sanity. Very flexible, great for custom content models and structured data. Editors get a polished editing experience. Our default pick when the content is non-trivial.
• Contentful. Mature, enterprise-friendly, predictable. Good if you value stability and have the budget. Pricing climbs fast as you add users and content types.
• Storyblok. Has a genuine visual editor where marketers see the page as they edit, which is the thing most non-technical teams actually want. A strong middle ground.
• Payload. Open source, runs on your own infrastructure, no per-seat pricing. Worth a look if you want to avoid vendor lock-in and you already host your own database.

If the single biggest pain is "marketing cannot see what the page looks like while editing," weight Storyblok and Sanity's visual editing heavily. That preview experience is often what makes or breaks adoption.

Rough costs and timelines

Treat these as ballpark figures, not quotes. Real numbers depend on how many page types you have, how custom the design is, and whether you are migrating existing content.

CMS subscription. Free tiers exist and are real for small projects. Once you have a marketing team with several editors and a meaningful number of content types, plan for somewhere in the range of a few hundred dollars a month. Contentful's higher tiers go into the low thousands per month. Payload self-hosted shifts that cost to your hosting bill instead, which is usually modest.

Initial build. A focused marketing site (homepage, a flexible landing-page builder, blog, a few content types) built on Next.js plus a headless CMS is typically a few weeks to a couple of months of engineering. A small, clean site might land in the lower half of that. A site with lots of bespoke sections, animation, and a content migration from an old system runs longer.

Migration. If you are moving content off WordPress or a legacy system, budget real time for it. Mapping old content into new structured models is the part everyone underestimates. It is rarely a copy-paste job.

Ongoing. Expect a steady but small line item: dependency updates, occasional new content types as marketing's needs grow, hosting. The good news is that hosting a Next.js front end is cheap and a CMS handles its own infrastructure.

What to watch out for

A few things that bite teams after launch:

• The "blank page" trap. Headless gives developers freedom, which means without discipline you can end up rebuilding every page from scratch. Insist on a reusable set of content blocks (hero, feature grid, testimonial, call to action) that marketing can assemble themselves. That block library is what makes the system feel self-serve instead of "open another ticket."
• Preview that does not work. Editors need to see drafts before publishing. This requires real setup on the front end and is sometimes skipped under deadline pressure. Make it a requirement, not a nice-to-have.
• Over-modeling. It is tempting to build a content model for every hypothetical future need. Start with what you publish today. You can add fields later far more easily than you can untangle a baroque schema.
• Forgetting redirects and SEO on migration. If you change URLs when you move, set up redirects from the old ones. Skipping this quietly tanks your search rankings, and it is painful to recover.
• Vendor lock-in. Your content lives in someone else's system. Check that your chosen CMS lets you export everything cleanly. Most do, but confirm before you commit years of content to it.

A simple way to decide

Ask three questions. Do you publish content to more than one channel, or expect to? Do performance and search rankings move real money for you? Do you have or want developers maintaining the site? If you answered yes to two of those, headless is probably right. If you answered no to most of them, a hosted builder will get you live faster and cheaper, and there is zero shame in that. The good kind of lazy is picking the tool that solves your actual problem, not the one with the best conference talks.

If you want a second opinion on which side of that line you fall on, we are happy to take a look before you commit to anything.