Top headless CMS development companies (July 2026 Update)

Choosing a headless CMS vendor is harder than choosing a CMS. The platforms are documented. Sanity, Storyblok, Contentful, Payload CMS -- each has public documentation, migration guides, and developer communities. What is not documented is whether the agency you hire has shipped on that platform in a real production environment, whether their content modeling decisions held up over eighteen months of editorial use, or whether they understand the API integration layer that connects the CMS to the rest of your product. Most agency directories list any firm that completed a partner certification. This list uses a different filter: what did you ship, who uses it today, and what would you do differently? The eight companies below passed that test.

The eight headless CMS development companies on this list are FocusReactive, Anything Agency, RaftLabs, Roboto Studio, Bits Orchestra, Cocoon Agency, Culture Foundry, and Webstacks. RaftLabs is on this list. We wrote our own entry with the same directness we applied to everyone else.

How we evaluated this list

No company paid for placement on this list.

The 8 companies

1. FocusReactive

FocusReactive is a headless-first agency based across the Netherlands, UK, and Poland with a team of thirty-plus engineers and architects. Their defining quality on this list is verified breadth: they hold official partnership status across four platforms -- Sanity, Storyblok, Contentful, and Payload CMS. That is not marketing language. It means they have shipped production projects on each of these platforms, understand the failure modes specific to each, and can make an informed recommendation between them based on your content structure, editorial team makeup, and frontend architecture. Most agencies list multiple platforms in their capabilities section. FocusReactive has the partner credentials and the production record to back every one.

Their work lives at the architecture and integration layer. While many headless CMS agencies focus on frontend delivery and basic content type configuration, FocusReactive builds the content infrastructure: content modeling systems, multi-locale pipelines, editorial workflow design, reusable component architecture, and the CDN and caching strategy that keeps a headless frontend fast without constant developer involvement. They have also shipped AI content workflows for clients -- automated classification pipelines, content enrichment tooling, and AI-assisted editorial interfaces integrated directly into the CMS environment. That puts them ahead of agencies still treating AI and CMS as separate concerns that will be connected later.

Their technical depth shows in their production metrics. The Arrive project for EasyPark -- the European parking platform -- delivered over 100 reusable UI components and a 97 Lighthouse performance score in production. That combination is harder to achieve than either number suggests. A 97 Lighthouse score on a content-heavy site requires caching decisions, image pipeline choices, and frontend rendering strategies deeply tied to how the CMS serves data. A 100-component system requires content modeling decisions that map to a component architecture without creating schema sprawl. Getting both right simultaneously is a genuine signal of architectural quality.

Notable work -- FocusReactive built the headless CMS infrastructure for the EasyPark Arrive product (100+ UI components, 97 Lighthouse score in production). Their portfolio includes multi-platform headless builds for European enterprise clients across e-commerce, publishing, and B2B services. They publish technical migration guides and open tooling for the Sanity and Storyblok communities.

Pricing signal -- $50-$99/hr. Minimum engagement $10K+. Most full headless projects run $15K-$60K. Their rate reflects genuine multi-platform expertise and architectural depth rather than a single-platform agency that has added partner logos to a marketing page.

What to watch -- FocusReactive's strongest work is the CMS and content architecture layer. For projects that require deep systems integration outside the CMS -- CRM sync, ERP data pipelines, e-commerce backend architecture, or AI inference pipelines that go beyond content tagging -- you may need to pair them with a specialist in those adjacent systems. If your project is a marketing site or content platform with standard integrations, their depth is more than sufficient.

• Best for: Organizations that need multi-platform headless architecture, content localization infrastructure, or editorial workflow design across Sanity, Storyblok, Contentful, or Payload CMS

• Specialization: Multi-platform headless builds, content architecture, localization pipelines, AI content workflows

• Pricing: $50-$99/hr, minimum $10K+, typical engagement $15K-$60K

• Clutch: 4.9/5 (23 reviews)

2. Anything Agency

Anything Agency is a UK-based digital agency with over ten years of headless CMS delivery. Their defining characteristic is deliberate focus: while many agencies list five or six CMS platforms as capabilities, Anything Agency built their practice around Storyblok and stayed there. They are the named Storyblok UK & Ireland Partner of the Year -- a credential tied to verified delivery volume, not community participation or badge collection.

What sustained focus on one platform delivers is depth that multi-platform generalists rarely match on a per-platform basis. Their team understands Storyblok's visual editor component architecture, the block hierarchy patterns that keep a growing site editorially manageable rather than schema-bloated, and the performance optimization patterns specific to how Storyblok's CDN delivers content across regions. For content teams using Storyblok daily, the difference between a CMS configured by a Storyblok specialist and one configured by a generalist who also ships on three other platforms shows up in every editing session -- in how intuitive the block structure feels, in how predictable publishing is, and in how rarely editors need a developer to fix something that should work out of the box.

Their longest client relationship is over twelve years with Netmums, one of the UK's largest parenting publishing communities. That is not a case study. It is a sustained operational partnership that has covered platform migrations, content architecture changes, editorial tooling updates, and performance rebuilds across more than a decade of digital publishing. For organizations that want a long-term CMS partner rather than a project vendor, that track record matters more than any individual launch metric. Their client roster also includes Amtico, the UK flooring brand, and Quorn, the protein brand -- established consumer organizations with editorial complexity and marketing teams that need to update content without developer involvement every time something changes.

Notable work -- A twelve-year partnership with Netmums, one of the UK's largest parenting publishing platforms. Headless Storyblok builds for Amtico and Quorn. Named Storyblok UK & Ireland Partner of the Year for verified delivery volume in the platform's partner program.

Pricing signal -- Hourly rate and project minimums are not publicly listed. Their partnership status and client profile place them in the mid-to-premium tier for UK headless agencies. Engagements are typically project-scoped rather than hourly. Contact directly for a scoping conversation.

What to watch -- Anything Agency is Storyblok-primary. If your existing infrastructure or future roadmap requires Sanity, Contentful, or Payload CMS, their depth reduces significantly. Their expertise is in Storyblok as a specific platform, not in headless CMS as a broad category. If platform choice is already settled on Storyblok, they are among the strongest options available in the UK market.

• Best for: UK and Ireland organizations building or migrating to Storyblok who want a proven specialist with long-term CMS partnership capability

• Specialization: Storyblok, headless editorial platforms, long-term CMS stewardship, visual editor architecture

• Pricing: Not publicly listed -- contact for project scoping

• Clutch: Not prominently listed -- verify via direct references

3. RaftLabs

RaftLabs builds headless CMS as a component of larger product systems. They are not a CMS-only agency. When headless CMS appears in a RaftLabs project, it is typically part of a broader build: a content layer feeding an AI personalization engine, a structured content backbone for a multi-brand platform, or a CMS integration connected to a loyalty system or proprietary data API. Their Sanity + Next.js + Vercel stack is the same combination that runs raftlabs.com -- a production-tested architecture, not a demo-day recommendation.

Their engagement model is fixed price. Scope, timeline, and deliverables are agreed in writing before any development or CMS configuration work starts. For organizations that have seen a CMS project drift from a defined scope into an open-ended time-and-materials billing arrangement, the difference is material. Scoping takes two to four weeks and produces a fixed-price proposal before any commitment is made on either side.

Their Clutch profile shows 50+ verified reviews at 4.9/5 -- a delivery record built across SaaS platforms, mobile products, AI-powered tools, and enterprise integrations for clients including Vodafone, T-Mobile, Cisco, and Wyndham Hotels. In these engagements, headless CMS appears as the structured content layer that feeds a larger system: a personalization engine, a multi-channel delivery pipeline, a backend API serving a mobile app alongside a web frontend. The integration complexity is where RaftLabs adds value that pure CMS agencies do not have. When a content team's requirements extend beyond a marketing site -- when the CMS feeds an AI recommendation model, syncs to a proprietary data pipeline, or serves content to a mobile app with offline requirements -- that integration work requires a product engineering team, not a CMS configurator.

Their custom software development services treat the CMS layer as one component in a system architecture. The content modeling, editorial tooling, and CMS configuration are designed in the context of the system the CMS connects to -- not as an isolated deliverable that a separate team will later try to integrate.

Notable work -- Sanity + Next.js + Vercel in production on raftlabs.com. Headless CMS integration within larger SaaS and product builds for Vodafone, T-Mobile, Cisco, and Wyndham Hotels. AI-powered platforms with structured content management and editorial workflows designed alongside inference pipelines and custom data systems.

Pricing signal -- $29-$49/hr. Fixed-price engagements. Scoping takes two to four weeks and produces a fixed-price proposal before any development or CMS configuration work starts. All-in project costs for a headless CMS build integrated with a custom product system typically run $40K-$150K depending on scope.

What to watch -- RaftLabs is not a pure headless CMS agency. If your project is a CMS-only marketing site migration with no surrounding system complexity -- a straight Storyblok or Sanity build for an editorial team that will self-manage it -- specialist boutiques deliver faster and with more CMS-layer depth per dollar. RaftLabs adds the most value when the CMS is one layer in a larger product, not the whole product.

• Best for: Mid-market businesses integrating headless CMS into AI pipelines, loyalty engines, multi-channel product systems, or custom API layers where CMS is one component of a larger build

• Specialization: Sanity + Next.js, CMS integration with custom product systems, fixed-price full-stack engagements

• Pricing: $29-$49/hr, fixed-price engagements

• Clutch: 4.9/5 (50+ verified reviews)

4. Roboto Studio

Roboto Studio is a London-based Sanity boutique. They build exclusively on Sanity + Next.js. That is a genuine platform constraint, not a marketing position. If your project requires Storyblok, Contentful, or any other CMS, they will tell you they are not the right fit. If your project requires Sanity, they are among the most capable options available.

Their depth on Sanity goes beyond delivery experience. Roboto Studio contributes to open-source Sanity tooling -- schemas, plugins, and extensions that other developers use in their own projects. Contributing at that level requires a degree of platform understanding that shipping client projects alone does not build. You develop it by working with the platform internals, hitting the edge cases, and building tooling that must work reliably across a variety of content models you did not design yourself. That understanding shows up in how they structure a content schema from day one: with extensibility built in, with editorial workflow implications considered before the first type is committed, and with upgrade paths thought through rather than discovered after launch when changing the schema means migrating thousands of content entries.

Their Clutch rating is 5.0/5 -- the highest on this list. It reflects a boutique that takes on work it can execute well rather than scaling to a size that dilutes quality. The trade-off is capacity. A small team limits the number of concurrent projects and the maximum engagement size they can support internally. For the right project type and scale, that is a worthwhile trade.

Their typical engagement runs £15K-£60K. The lower end covers a focused Sanity migration or a CMS configuration with a lightweight frontend. The upper end covers full content architecture, editorial workflow design, content modeling, Next.js frontend build, preview environment setup, and editorial team training to operate the CMS independently.

Notable work -- Open-source contributions to the Sanity plugin ecosystem, used by developers across the Sanity community. Editorial platforms, marketing sites, and content infrastructure for UK and European clients built exclusively on Sanity + Next.js. Specific client names are not publicly listed -- verify through direct references.

Pricing signal -- £15K-£60K per engagement, project-scoped rather than hourly. Rates reflect London boutique pricing for deep Sanity platform specialists.

What to watch -- Roboto Studio is Sanity-only with zero platform flexibility. Their team size limits concurrent capacity and puts a ceiling on the maximum project scale they can take on internally. For very large engagements requiring multiple workstreams, parallel editorial environments, or a team of ten-plus engineers, their boutique model does not scale to match.

• Best for: UK and European organizations building Sanity-first editorial platforms, content-led products, or marketing sites who want open-source-level platform depth

• Specialization: Sanity CMS, Next.js, open-source contributor, editorial workflow design

• Pricing: £15K-£60K per engagement

• Clutch: 5.0/5

5. Bits Orchestra

Bits Orchestra operates at a specific intersection that most headless CMS agencies on this list do not cover: the .NET ecosystem. Their headless CMS practice is built around organizations that already run .NET infrastructure -- ASP.NET backends, SQL Server databases, Azure deployments -- and need to add a modern CMS layer without replacing the stack their operations depend on. That is a common situation in mid-market and enterprise organizations. The software that runs the business was built on .NET a decade ago. The marketing and content team needs a better editorial interface. A headless CMS that integrates cleanly with that infrastructure, rather than forcing a full-stack migration, is the right answer for many of them. The question is finding an agency that understands both sides of the equation.

Their platform coverage reflects this position. They are a Kentico Xperience Bronze Partner and have delivered production projects across Umbraco, Contentful, Strapi, and Sanity -- each in the context of enterprise .NET modernization rather than greenfield JavaScript-first headless builds. A company running Kentico on an aging .NET Framework codebase that needs to move to a headless architecture is exactly the engagement type Bits Orchestra is designed for. A company starting fresh on a React + Node.js stack with no .NET components is not their best-fit client.

Their delivery record is substantial: 130+ projects over eight-plus years. In the headless CMS category, eight years of delivery history predates the current market's mainstream adoption cycle. Their longevity reflects a stable B2B and enterprise client base rather than a high-velocity startup pool that churns through agencies every eighteen months. That stability is a signal of the client relationships they maintain, not just the projects they launch.

Their B2B portal work -- internal employee platforms, supplier portals, client-facing content platforms with role-based access -- requires structured content modeling with approval workflows, version history, and content governance patterns that consumer-facing CMS builds rarely encounter. For organizations with those governance requirements, their experience is directly applicable.

Notable work -- 130+ projects over eight-plus years, primarily B2B portals and enterprise modernization in the .NET ecosystem. Kentico Xperience Bronze Partner. Headless builds on Umbraco, Contentful, Strapi, and Sanity alongside .NET backend systems.

Pricing signal -- Hourly rate and engagement minimums are not publicly listed. Their .NET specialization places them in the mid-market to enterprise pricing tier for European development agencies. Contact for project-specific scoping.

What to watch -- Bits Orchestra adds the most value when Kentico or Umbraco is already in the stack, or when .NET backend systems require tight integration with the CMS layer. Outside the .NET ecosystem, their differentiation against a multi-platform headless specialist is reduced. For greenfield Sanity or Storyblok builds on a JavaScript-first stack with no .NET components, a JavaScript-native agency operates more naturally on familiar ground.

• Best for: Organizations modernizing a .NET stack that includes Kentico or Umbraco, or building B2B portals with enterprise content governance requirements

• Specialization: .NET ecosystem CMS integration, Kentico, Umbraco, Contentful, Strapi, B2B portals

• Pricing: Not publicly listed -- contact for scoping

• Clutch: Not prominently listed -- verify via direct references

6. Cocoon Agency

Cocoon Agency is a UK-based agency focused on MACH architecture -- Microservices, API-first, Cloud-native, and Headless. In practice, that framing means they build composable digital stacks where the CMS is one component among several: a commerce platform, a personalization engine, a search layer, and a data platform that communicate through APIs rather than being embedded in a single monolithic system. The CMS is not the product -- it is a content service inside a larger composable architecture.

Their primary CMS platform is Sanity, which is well-suited to MACH builds because of its API-first design and flexible content schema. But their vendor-agnostic stance means the CMS selection is driven by requirements, not by preferred partner programs. That distinction matters on complex builds where the CMS must interoperate with services that have their own API contracts and data schemas. An agency that defaults to one platform regardless of the broader stack will create integration friction that a genuinely agnostic agency avoids by designing the content API alongside the other service contracts from day one.

Their focus is on complex B2B and omnichannel builds: organizations with multiple editorial teams, multiple delivery channels (web, mobile, IoT, voice), or multiple brand variants that need to operate from a single structured content source. The MACH approach to these problems is more expensive to build initially but reduces the platform dependencies that make monolithic systems painful to change. A monolithic CMS that manages rendering, routing, and personalization is fast to set up and slow to evolve. A composable stack is slower to set up and faster to evolve. The right choice depends on how stable your requirements are and how frequently you expect your delivery channels to change.

Notable work -- MACH-architecture composable builds for complex B2B and omnichannel clients in the UK market. Sanity as primary CMS within vendor-agnostic stack selection. Specific client case studies are not publicly prominent -- verify through direct references.

Pricing signal -- Boutique UK pricing. Not publicly listed. MACH builds typically run higher than standard CMS projects because each platform integration -- commerce, personalization, search -- adds scoping, connection work, and end-to-end testing on top of the CMS layer.

What to watch -- Cocoon is best when MACH is a deliberate strategic decision, not an aspiration. If your organization is still evaluating whether to go headless at all, a more advisory-oriented firm is a better first engagement. Cocoon excels when the architectural direction is set and the build complexity comes from integrating multiple composable services. Their boutique capacity also limits how many concurrent projects they can staff at high quality.

• Best for: B2B organizations committed to MACH architecture, omnichannel delivery, or composable digital stacks requiring CMS integration with commerce, personalization, or search layers

• Specialization: MACH architecture, Sanity, composable DXP, complex B2B and omnichannel platforms

• Pricing: Not publicly listed

• Clutch: Not prominently listed -- verify via direct references

7. Culture Foundry

Culture Foundry is a US-based digital agency with the widest CMS platform range on this list. Their capabilities span WordPress, Drupal, Craft CMS, Wagtail, MODX, and Django alongside headless implementations. That breadth signals something specific about the type of client they serve: organizations still evaluating whether to go headless, not only organizations that have already decided.

Most headless CMS agencies have a structural incentive to recommend headless. Their expertise, their partner programs, and their margins are built around it. Culture Foundry's multi-platform stance removes that incentive. They will recommend the right architecture for the editorial requirements -- which may mean staying on Drupal, modernizing a WordPress installation, or moving to a headless stack -- rather than defaulting to the architecture they are most specialized in building. For editorial-heavy organizations, universities, media companies, and nonprofits where content governance, accessibility compliance, and long-term content maintainability matter more than frontend performance scores, that platform-agnostic advisory approach delivers genuine value.

Their focus on editorial-heavy organizations reflects a specific kind of content complexity that B2B and e-commerce-focused headless agencies rarely encounter: complex publishing workflows, multi-author content teams with defined editorial hierarchies, structured approval chains, content lifecycle management across hundreds of pages, and accessibility compliance that must hold across a large content catalog managed by non-technical users. Those requirements are often better served by a mature CMS with proven editorial tooling than by an API-first platform optimized primarily for developer experience.

The honest trade-off: if you are already certain you need headless CMS on Sanity or Storyblok, dedicated headless agencies bring more per-platform implementation depth than Culture Foundry can. Their breadth is most valuable when the architecture decision is still open and you need an advisor who does not have a financial stake in recommending headless.

Notable work -- Multi-platform CMS implementations for editorial-heavy organizations, universities, media publishers, and nonprofits across the US. Platform advisory work that includes recommending against headless when traditional CMS better serves editorial and governance requirements. Client references available on request.

Pricing signal -- US agency rates. Not publicly listed. Mid-market tier based on client profile and project scope.

What to watch -- For organizations already committed to a headless architecture on a specific platform, Culture Foundry's multi-platform generalism means less accumulated depth per platform than a dedicated specialist. If you need deep Sanity expertise, a Sanity-first agency is a more direct match. Culture Foundry's value is in advisory breadth, editorial workflow depth, and the willingness to recommend the right architecture rather than the most profitable one.

• Best for: Content-heavy organizations, nonprofits, media companies, and universities evaluating CMS architecture and not yet committed to headless

• Specialization: WordPress, Drupal, Craft CMS, Wagtail, Django, platform-agnostic headless advisory

• Pricing: Not publicly listed

• Clutch: Not prominently listed -- verify via direct references

8. Webstacks

Webstacks is a San Diego-based agency that specializes in B2B SaaS marketing websites. Their client list is shaped entirely by that specialization: high-growth SaaS companies that need a fast, well-designed marketing site where the content team can publish pages, update messaging, and run campaigns without a developer involved in every change. That is a common and real pain point at growth-stage B2B SaaS companies. The marketing team needs to move fast. The engineering team does not want to be the gating resource for routine content updates on the marketing website.

They use Sanity as their CMS of choice for these builds. The combination of Sanity's structured content schema and Next.js's static generation is well-matched to the marketing site use case: pages generate fast at build time, editors update content through a structured interface, and the development team controls the rendering layer without being pulled in for routine content edits. Preview environments allow editors to review changes before they publish -- a capability that matters more than most clients realize until they have operated without it for six months.

Their most visible work is the Calendly marketing site redesign. Calendly is a B2B SaaS product with significant brand recognition and a marketing site that must support a content team operating at scale, SEO requirements across thousands of pages, and rapid campaign deployment without engineering bottlenecks. That is a representative project for what Webstacks does best: a B2B SaaS marketing site that needs to perform like a product, not function like a brochure.

Their typical engagement runs $40K-$120K. That range reflects the scope of a B2B SaaS marketing site done well: brand-aligned design, Sanity CMS configuration, Next.js frontend build, editorial workflow documentation, and launch. The ceiling reflects complexity: multi-language sites, large page counts, or tightly integrated analytics and A/B testing setups that require additional frontend engineering beyond the baseline.

Notable work -- Calendly marketing site redesign. B2B SaaS marketing site builds for high-growth software companies using Sanity and Next.js. Editorial tooling and content operations consulting for marketing teams managing large page catalogs.

Pricing signal -- $40K-$120K per engagement. The range reflects standard to complex B2B SaaS marketing site builds. Not calibrated for projects outside this use case.

What to watch -- Webstacks is purpose-built for B2B SaaS marketing websites. They are not suited for e-commerce platforms, editorial publishing sites with complex content governance, multi-brand consumer content operations, or platforms where the CMS needs to integrate with backend systems beyond a standard marketing analytics stack. If your use case sits outside that lane, you will pay for specialization you will not use.

• Best for: B2B SaaS companies that need a high-quality marketing website on Sanity with fast editorial publishing, strong design, and content team independence from engineering

• Specialization: B2B SaaS marketing sites, Sanity, Next.js, marketing-led content operations

• Pricing: $40K-$120K per engagement

• Clutch: Not prominently listed -- verify via direct references

Side-by-side comparison

The question that separates a CMS specialist from a product studio

The most common procurement mistake in headless CMS projects is treating them as a single category when they are two meaningfully different types of work. A business building a content-led marketing site for an editorial team is buying a different service than a business building a CMS that feeds an AI recommendation engine, a mobile app, and a B2B portal simultaneously. The agencies that do these well are not the same agencies. Choosing one for the other job is expensive.

CMS-first specialists -- FocusReactive, Anything Agency, Roboto Studio, and Webstacks operate best in the CMS-primary lane. The project scope is the CMS itself: platform selection, content type architecture, editorial tooling, frontend delivery, preview environments, and editorial team handoff. System boundaries are relatively clear: the CMS serves content to a frontend, the frontend publishes to a domain. Engagements in this lane run $15K-$120K and take four to sixteen weeks. The agencies here have deep platform knowledge and deliver efficiently within that defined scope. If your project lives here -- a marketing site migration, a content-led product with a standard frontend -- choose from this group.

Product studios with CMS capability -- RaftLabs, Bits Orchestra, and Cocoon Agency operate best when the CMS is one layer in a larger system. The project scope extends well beyond the CMS: the content must feed something else -- an AI inference pipeline, a loyalty platform, an ERP system, a mobile app with offline capabilities, a B2B portal with role-based content access and approval workflows. The integration complexity raises the timeline and the budget, but it is not optional. A CMS-only agency asked to build those integrations will scope them poorly, hand them to a third team, or discover mid-project that the content model decisions they made in week two do not support the integration architecture required in week eight. Product studios handle both, because the content model and the integration architecture are designed together from the start.

Getting the model wrong is more expensive than getting the vendor wrong.

What research says about composable content architecture

"By 2023, organizations adopting an intelligent composable approach will outpace their competition by 80% in the speed of new feature implementation." -- Gartner, Magic Quadrant for Digital Experience Platforms, 2022

According to MarketsandMarkets, the global headless CMS market was valued at $328.5 million in 2022 and is expected to reach $1.6 billion by 2027, growing at a compound annual growth rate of 22.6%. That growth reflects what enterprise content teams are already discovering: when content lives in a structured, API-accessible system, it can be published to any channel -- web, mobile, voice assistant, AI-generated search responses -- without rebuilding the editorial workflow each time a new delivery channel appears. The organizations that model their content correctly now are building infrastructure that survives the next wave of channel changes. The ones that get it wrong rebuild it -- or abandon the headless migration and return to a coupled system after eighteen months of painful integration work. The architecture decision is not primarily a technology decision. It is a decision about how much flexibility the organization is willing to invest in upfront versus how much constraint it is willing to live with as delivery channels and content requirements evolve.

Five questions to ask before signing

1. Which specific CMS platforms have you shipped in production in the last twelve months?

Partner program certifications and platform logos are self-reported and do not expire automatically. Ask for a URL to a live production site the agency built on the specific platform you are considering. Ask when the last code commit was made to that project. A certified partner agency that has not shipped a new project on a given platform in eighteen months may hold the credential but not current platform depth. Sanity updates its APIs and studio components frequently. Storyblok has released major visual editor changes. An agency that is not actively shipping on a platform is learning about those changes from release notes, not from production experience.

2. How do you approach content modeling for a site that will add twenty new content types in year two?

Content modeling is the architectural decision most headless CMS projects underinvest in at the start. An agency that begins from existing page templates and adapts schemas to fit current content fields is building technical debt into the foundation. A well-structured schema starts from editorial workflow requirements -- what does an editor actually do each day, what fields do they fill in, what does a published piece of content relate to -- and models the content types to match that workflow rather than to match a page template. A strong answer includes modular content types, explicit reference relationships between types, consideration of future channel requirements, and documented decisions about what will and will not be hard-coded into the schema. Ask for an example of a content model they designed and then had to change at a client's request twelve months after launch. Ask what made that change easy or hard. The answer tells you more about how they model content than any case study does.

3. What does your preview environment look like for editorial teams?

A headless CMS decouples content storage from frontend rendering. That means editors cannot see a live preview of their changes by default -- they must publish to see the final result, which introduces risk on content-heavy sites with frequent publishing cycles. A production-quality headless build includes a real-time preview environment: a staging frontend that shows the editor exactly how a content change will render before it is published. Ask to see a demo of their preview environment on a recent project. Ask who maintains it when the frontend build is updated. Ask whether it supports draft content previews across multiple content types simultaneously or only on individual entries. Agencies that have built robust preview environments will answer these questions with specifics. Agencies that have not will describe their intention to include preview "as part of the standard build."

4. How do you handle content schema migrations after launch?

Content type requirements change. A marketing team adds a new field. A developer deprecates a content structure that editors have been using for a year. A new delivery channel requires a content format the original schema did not anticipate. The question is not whether these changes will happen -- they will. The question is whether the CMS architecture was designed to accommodate them cleanly or whether each change requires a painful content migration. Ask the agency for a specific example of a schema migration they executed at a client twelve months post-launch: what triggered it, what the migration approach was, how long it took, and whether any editorial content required manual intervention. An agency with a real answer has shipped projects that survived into their second year of editorial use. An agency without a real answer has not.

5. What does your editorial team handoff look like, and who supports it after launch?

An agency that builds a headless CMS and leaves at launch creates a support problem that surfaces within the first month of editorial operation. Ask what happens at the end of the engagement: who receives the documentation, what format it is in, whether there is a recorded walkthrough of the content model for new team members, and who the first call is when an editor has a question that the documentation does not answer. Ask whether the agency offers a retainer for ongoing CMS support and at what rate. A CMS that the editorial team cannot manage independently six months after handoff is a failed engagement regardless of Lighthouse scores or technical elegance. The editorial handoff should be scoped and priced before the build starts, not treated as a documentation task at the end.

The verdict

For multi-platform headless builds with content architecture depth: FocusReactive -- Sanity, Storyblok, Contentful, or Payload, with official partner status across all four and a 97 Lighthouse score as a production reference point.

For UK and Ireland organizations building on Storyblok with long-term partnership goals: Anything Agency -- named Storyblok UK & Ireland Partner of the Year, with a twelve-year client relationship as the reference.

For headless CMS integrated with AI pipelines, custom APIs, or larger product systems: RaftLabs -- fixed price, $29-$49/hr, Sanity + Next.js in production at raftlabs.com.

For London-based Sanity-first builds from an open-source contributor: Roboto Studio -- 5.0/5 on Clutch, £15K-£60K, Sanity-only with genuine platform depth.

For organizations modernizing a .NET stack that includes Kentico or Umbraco: Bits Orchestra -- 130+ projects, Kentico Xperience Bronze Partner, deep .NET integration capability.

For MACH architecture and composable B2B or omnichannel builds: Cocoon Agency -- when MACH is a deliberate architectural decision, not an aspiration.

For editorial-heavy organizations not yet committed to headless: Culture Foundry -- platform-agnostic and willing to recommend traditional CMS when it serves editorial requirements better than headless would.

For B2B SaaS companies that need a high-quality marketing site on Sanity: Webstacks -- $40K-$120K, with the Calendly redesign as the reference build and purpose-built for this use case.

The choice between these agencies comes down to two variables: how complex the systems surrounding the CMS are, and how committed you are to a specific platform. Match those two variables to the agency model before evaluating portfolios.

RaftLabs builds headless CMS as part of larger product systems -- when the content layer needs to integrate with AI pipelines, custom APIs, or multi-channel delivery architectures. No handoff gap between CMS configuration and production deployment. 4.9/5 on Clutch. Talk to a founder about your headless CMS project.