Best headless CMS for agencies: Top platforms and selection framework for 2026

Headless CMS (Content Management System)  platforms help agencies deliver faster, more scalable multi-channel experiences and sidestep development bottlenecks. The most credible options, like Storyblok, Kontent.ai, Contentful, Strapi, and Sanity, combine API-first delivery with strong collaboration tools and flexible integrations. This guide breaks down which platforms work best for different agency needs heading into 2026, from enterprise-scale operations to marketing-led teams.

What is a headless CMS for agencies?

A headless CMS for an agency is a content platform that separates the front-end development from the back-end, supporting faster builds and multi-channel delivery.

In traditional CMS setups, content and presentation are married together. You create content, it gets locked into templates, and pushing that content anywhere beyond your website requires custom development work. A headless CMS flips this model. The “head” (the presentation layer) gets severed from the “body” (the content repository), and everything flows through APIs instead.

For agencies managing multiple client sites, this architecture shift matters. You’re no longer building the same functionality over and over. Content becomes portable, reusable, and deliverable to websites, mobile apps, digital signage, voice interfaces, or whatever channel your clients require next.

How a headless CMS works

Content lives in a central repository accessed through RESTful or GraphQL APIs. Developers build front-ends using any framework, such as React, Vue, Next.js, or whatever framework best fits the project. Content teams work in the CMS interface, creating and organizing material without touching code. When content is published, APIs deliver it to any connected channel. The architecture enables true parallel workflows: developers ship features while marketers craft campaigns, neither group waiting on the other.

Headless CMS vs. traditional and decoupled CMS

Well-established platforms like WordPress bundle everything together. You get convenience, but flexibility suffers. Need to power a mobile app? You’re fighting against the system’s assumptions. 

Decoupled CMS options split some differences: they maintain a default presentation layer but allow API access for teams who are not ready for a full rebuild. 

Headless platforms go full separation, giving maximum flexibility at the cost of requiring you to build and maintain your own front-ends.  

Why agencies go for headless CMS solutions in 2026

Top headless CMS platforms for agencies improve speed, collaboration, scalability, and omnichannel consistency.

The shift comes from rising client standards and developer reality. In 2026, agencies face three emerging demands: AI-assisted content workflows, composable architecture integration, and real-time personalization at scale. Nobody launches just a website anymore. The market wants apps, responsive web, digital kiosks, and more. Traditional CMS platforms often buckle under these demands, while headless platforms can handle the complexity.

The data points to a lasting focus on headless CMSs, with agencies and enterprises voting with their budgets. The global headless CMS software market reached $973.8 million in 2025  and is projected to grow to $7.11 billion by 2035 (CAGR 22.6%).

Faster front-end development and parallel workflows

Decoupled front-end and back-end means your developers ship features while content teams update copy, skipping waiting and blocking. Text changes happen without developer tickets, and marketing swaps images without triggering deployments.

Storyblok reports teams adopting headless CMS see 58% better site performance and 69% faster time-to-market, proving velocity for client work.

Wpromote applied a headless WordPress architecture on WP Engine to rebuild CentralSquare’s (a public sector software provider) web presence, enabling faster front-end performance and parallel content and development workflows. The decoupled setup supported fast marketing iteration without back-end bottlenecks, contributing to a 56% increase in demo requests and 30% pipeline growth.

Multi-channel content delivery at scale

Headless platforms are designed to “write once, publish everywhere” across websites, mobile apps, IoT devices, and voice assistants.

For agencies juggling multiple clients, this flexibility means you don’t rebuild content workflows for each project. A unified headless platform handles complexity, so you take on more clients without hiring more people.

thunder::tech used Kentico Kontent, a cloud-based headless CMS, to build a Tokyo Olympics media room for USA Track & Field. The platform gave journalists and teams a single login to access live athlete Zoom sessions and up-to-date content in real time, while reducing strain on existing systems. The experience was well received by both USATF staff and media covering the Games. 

Better SEO foundations and technical control

Headless platforms give you more control over technical SEO implementation, but you’ll need custom work for metadata, server-side rendering, and structured data.

Done right, this control gives you real performance gains. A 2024 study of 34 CMS platforms shows headless systems outperform traditional ones in speed, throughput, and efficiency — key factors that boost SEO via better Core Web Vitals. For content teams managing agency clients, faster sites mean better ranking, conversion, and keeping clients happy.

Reduced maintenance through API-first architecture

APIs separate your content system from how it’s displayed. When a new device or channel launches, you build a new front-end that consumes existing APIs, without a CMS revamp. Decoupled systems update independently, reducing regression risk during upgrades.

Platform-level security and performance updates mean fewer maintenance tasks and surprises. In practice, it means your team spends less time on legacy support and more time delivering for clients.

Kanopi Studios leveraged a mobile-optimized, API-driven headless WordPress architecture on WP Engine to rebuild the site for Alameda County Community Food Bank (ACCFB). By decoupling content management from presentation, the new setup delivered faster performance and improved accessibility, resulting in +100% users, +89% sessions, and +54% pageviews, and strengthening community outreach.

Practical overview of the headless CMS for agencies  

The best headless CMS platforms for agencies balance flexibility for developers with usability for marketers.

No single platform owns the space, and none checks every box for every team. Some are great for fast builds, others for content control, but pricing, support, growth potential, and how well it fits your team’s workflow and your clients’ needs all play a role. Here’s what to weigh:

Storyblok

Storyblok makes headless CMS accessible to non-technical users without limiting developers. Its visual editor shows components inline for real-time previews, while the component-based architecture mirrors modern front-end patterns. Coming in 2026, Storyblok’s Strata layer adds AI-powered search and personalization at scale.

Pricing: Storyblok uses per-user pricing with a SaaS model, with a free Starter plan for one user. Growth plans begin at $99/month, with Premium and Elite tiers using custom pricing for enterprise requirements.

Agency fit: 

• Small-to-midsize agencies where non-technical clients will self-serve content updates daily
• Projects requiring real-time visual preview during editing 
• Teams building component-driven sites where marketers assemble pages from pre-built blocks without developer involvement.

Watch for: Performance can suffer at enterprise scale. The platform is younger than competitors, meaning some edge cases lack battle-tested solutions.

Kontent.ai

Kontent.ai delivers enterprise-grade governance without the complexity overhead. The platform centers on structured content modeling, workflow orchestration, and team collaboration tools. AI features streamline operations by offering content recommendations and insights throughout the lifecycle.

Agency fit: 

• Enterprise agencies managing multi-stage approval workflows with legal, compliance, or regional sign-offs
• Global brands requiring sophisticated translation management with in-context localization tools
• Projects where content governance and audit trails are contractual requirements.

Watch for: Pricing isn’t transparent. Budget discussions require vendor contact.

Contentful

The established player, Contentful, is an enterprise-grade headless CMS built for performance at scale. Its massive ecosystem, mature APIs, and extensive documentation make it a safe choice for demanding projects. Contentful’s recently launched AI Actions generate content suggestions and variants across the entire content lifecycle.

Pricing: Contentful’s pricing ranges from a free tier to $300/month for the Lite plan, with Premium plans for enterprise clients able to request custom thresholds.

Agency fit: 

• Large-scale implementations serving thousands of pages or supporting millions of API calls monthly
• Projects requiring deep integration with enterprise systems (ERPs, PIMs, DAMs) through a mature marketplace
• Agencies betting on long-term platform stability and guaranteed enterprise SLAs with established vendor accountability.

Watch for: Developer-heavy workflows can create bottlenecks. Non-technical users often struggle with the abstract editing interface. Costs scale quickly with additional users and usage. 

Strapi

Open-source and self-hosted, Strapi puts developers in control while giving editors a smooth publishing experience. Built on Node.js, it provides both REST and GraphQL APIs by default. Strapi also offers AI features that build content types from plain language or Figma designs and generate media metadata automatically.

Pricing: Strapi’s pricing ranges from a free plan for basic use, through paid cloud plans starting at $45/month for small teams, up to higher-tier professional and enterprise options that scale depending on team size and deployments. 

Agency fit: 

• Agencies requiring full codebase ownership for IP reasons, white-labeling, or client-specific regulatory constraints
• Projects with highly custom data models that commercial platforms cannot accommodate without expensive workarounds
• Teams comfortable managing server infrastructure, security patching, and database optimization in-house

Watch for: Self-hosting shifts infrastructure management, updates, and security responsibilities to your team. Strapi eliminates licensing fees as open-source but adds hosting overhead ($18–$5,000+/month scaling with traffic, plus 45–48% more ops time).

Sanity

Sanity is a developer-first headless CMS built for flexible content and real-time collaboration. Teams define content models in code through its customizable Sanity Studio, and the Portable Text format gives precise control over how content appears across different channels. For 2026, Sanity adds AI-assisted writing and AI tool integration, making it ready for where content operations are heading.

Pricing: Sanity uses tiered SaaS pricing with a free plan for small projects and public datasets. The Growth plan starts at $15/user/month with usage-based scaling, while Enterprise pricing is custom and includes advanced security, SSO, and dedicated support.

Agency fit: 

• Developer-led agencies building content tools as product features
• Projects requiring real-time collaborative editing
• Teams that define content schemas in code and version-control them alongside application logic.

Watch for: The developer-centric setup can be challenging for non-technical editors. Marketing teams often face a steeper learning curve compared to more UI-driven platforms, which may increase onboarding and support effort.

Hygraph

A GraphQL-native headless CMS, Hygraph centers on API performance and structured content relationships. Its unified GraphQL API simplifies querying and content federation, ideal for projects that pull from multiple sources smoothly. Hygraph AI adds tools like Developer Copilot and Workflow Copilot for autonomous operations.

Pricing: Hygraph’s prices range from a free Hobby plan for personal projects (conditions apply) to the Growth plan starting at $199/month for small businesses, with the Enterprise offering custom options.

Agency fit:

• Projects with complex relational data, where GraphQL query efficiency matters
• Teams already invested in GraphQL across their stack, who want unified query patterns
• Agencies building content federation architectures that pull from multiple sources into a single API layer.

Watch for: The ecosystem is smaller than more established platforms, which means fewer third-party integrations, plugins, and community resources. Teams may need to build more custom solutions.

WP Engine Atlas (Headless WordPress)

WP Engine combines WordPress’s familiar editing experience with headless delivery and managed infrastructure. This lets agencies modernize WordPress projects without forcing content teams to change their workflows, and still benefit from enterprise-level hosting and support.

Agency fit:

• WordPress-specialist agencies transitioning existing client portfolios to modern architecture without retraining content teams
• Clients who demand WordPress familiarity but need performance and security beyond traditional hosting
• Projects where managed infrastructure, automatic updates, and enterprise support justify premium pricing over DIY WordPress headless.

Watch for: WordPress remains the underlying system.  Atlas removes many traditional limitations, but some architectural constraints and legacy assumptions still apply compared to fully native headless platforms. For production use WP Engine’s  pricing remains custom or quote-based  

Prismic

Prismic is a developer-friendly headless CMS with a strong focus on modular content and visual editing. Its Slice-based approach supports reusable components, while the interface remains approachable for content teams managing SEO-driven or marketing-led sites.

Pricing: Prismic offers a free plan for one user. Paid plans start at $10/month (Starter), scale through $25/month (Small) and $150/month (Medium), and reach $675/month (Platinum). Enterprise pricing is custom and includes advanced security and dedicated support.

Agency fit:

• Marketing-driven agencies building campaign microsites, landing pages, or content-heavy blogs where speed-to-publish trumps governance
• Small teams looking for modern architecture without enterprise complexity or pricing
• Projects where the CMS is secondary to the front-end framework and only needs to feed content reliably.

Watch for: Prismic offers less depth in governance, workflow complexity, and advanced localization features, which may limit its suitability for large or regulated organizations.

Magnolia

Magnolia pairs enterprise content management with hybrid headless flexibility, letting editors work in an intuitive interface while developers make use of robust APIs. Its light module system allows fast customization without heavy Java overhead, fitting composable architectures for multi-channel delivery. The AI Accelerator speeds up content creation and handles automatic image recognition.

Pricing: Magnolia offers two deployment models: DX Cloud (fully managed PaaS) starts at $6,000/month, and DX Core (self-hosted) begins at $3,500/month. Pricing scales with users, traffic, instances, and support levels.

Agency fit: 

• Regulated industries (financial services, healthcare) requiring on-premise deployment options and full-scale audit capabilities
• Legacy Java-based organizations transitioning to headless while preserving existing technical investments
• Projects needing hybrid CMS (traditional templating AND headless APIs) during multi-year migration phases.

Watch for: DX Core calls for Java expertise for scaling and infrastructure management. Custom pricing means mandatory sales conversations. The platform targets mid-to-large enterprises; smaller teams may find alternatives more accessible for quick starts.

Headless CMS comparison: Which is best for your agency?

The best choice depends on project complexity, client CMS maturity, budgets, and required integrations. When looking for headless CMS options, you need to stop thinking about “best” in absolute terms. Think about “best for what?”

Headless CMS comparison for agency needs

Best fit category	Platforms	Why this fit (agency lens)	Watch for
Enterprise agencies	Kontent.ai  Contentful MagnoliaWP Engine Atlas (Headless WordPress)	Enterprise readiness: strongest security controls, compliance support, SLAs, structured workflows, auditability, SSO (platform-dependent) Platform maturity for large-scale delivery: proven multi-brand, multi-locale, multi-environment use	Higher cost and setup effort. Governance features require upfront content and workflow design to avoid extra complexity
Open-source / code-first options	Strapi  Sanity	Control and customization: self-hosting or hybrid hosting, flexible content schemas Integration freedom: REST and/or GraphQL APIs for custom services and internal systems Licensing flexibility: suitable when SaaS pricing or constraints don’t fit	Operational responsibility shifts to the agency (hosting, updates, security, monitoring)
Marketing teams	Storyblok  Kontent.ai Contentful  Prismic	Editor-first experience: visual or modular editing designed for non-technical users Reduced developer dependency: routine publishing and updates without code changes Fast content workflows: previews, scheduling, and approvals (platform-dependent)	Visual tools rely on well-designed components. Limited governance depth can become a risk at enterprise scale
All-rounder (balanced teams)	Kontent.ai  Storyblok Prismic	Balanced ownership: editors and developers can work independently without blocking each other Structured content with flexibility: strong modeling without dictating front-end choices Scales with team maturity: suitable as projects grow from simple to moderately complex	May miss advanced governance/compliance features needed by heavily regulated enterprises

Key features agencies should evaluate in a headless CMS

Validated by real success stories and our own experience at GetDevDone, the right headless CMS helps your agency ship faster, reduce friction between teams, and spend less time maintaining platforms that push back.

Feature checklists tend to create selection paralysis. What actually matters for client success is how well a platform supports real delivery, real clients, and real growth.

Developer experience (DX)

Everything starts with the API. If it’s slow, limited, or poorly documented, delivery suffers. Look for clear, well-documented APIs, solid SDKs for your preferred frameworks, predictable rate limits, and reliable webhooks. These details directly shape how quickly your team can build, extend, and scale client applications.

Editorial experience and workflows

Content tools should match clients’ actual workflows. Visual editing, previews, approvals, and localization minimize errors and cut down on back-and-forth with developers. If editors can’t confidently manage content on their own, your team becomes a bottleneck, and costs rise.

SEO and delivery control

Headless doesn’t remove SEO concerns; it shifts responsibility. Make sure the platform supports your rendering strategy (SSR, SSG, ISR), handles metadata cleanly, and manages localization correctly. The CMS should give you control, not force workarounds.

Content migration

Migration often determines whether a project stays on schedule. Strong import tools, clear documentation, and optional professional support reduce risk. Agencies regularly underestimate this phase until legacy content models collide with new structures.

Integrations and extensibility

Every client stack is different. Your CMS needs to integrate cleanly with analytics, marketing automation, commerce, DAMs, and custom systems. API-first design is essential, but pre-built integrations can save weeks of development time.

Cost and total resource load

Consider the complete financial picture for 2026. Commercial headless CMS licensing is only part of the cost. Factor in developer time, onboarding, hosting, maintenance, and support overhead. Headless platforms can look expensive upfront, but they often reduce long-term complexity, rework, and maintenance compared to heavily customized traditional CMS setups.

Common challenges agencies face with headless CMS  

With headless CMSs, agencies get more freedom in how they build and scale, but they also step closer to the engine room. That shift from configuration to responsibility demands clear ownership and discipline.

Technical complexity and learning curve

Traditional CMSs hide complexity behind defaults. Headless platforms surface it. Teams now have to make choices about hosting, rendering, deployments, and API orchestration. For agencies used to WordPress-style setups, the ramp-up is real.

How agencies handle it:
Start with managed platforms and opinionated starter kits. Invest early in developer enablement. Reuse architecture patterns across projects so the learning curve pays off over time.

SEO doesn’t come “out of the box”

With headless, SEO isn’t prepackaged. Metadata, structured data, sitemaps, redirects, and canonical URLs are part of the build, instead of a settings page. That extra work is the price of control.

How agencies handle it:
Standardize SEO components, lean on framework capabilities, and make SEO checks part of the delivery pipeline. Done right, this moves SEO from guesswork to something predictable and repeatable.

Content preview is harder than it looks

Editors expect to see changes before they publish. In headless setups, previews often require extra configuration or custom environments. They don’t always match production perfectly.

How agencies handle it:
Choose platforms with solid preview tooling and plan preview work upfront. Start with “good enough” previews, then refine them as the project matures.

Front-end ownership becomes real

With headless, on top of managing content, the team owns the front-end application. Every update, security patch, performance optimization, and feature addition becomes your responsibility, no longer abstracted away by the CMS.  

How agencies handle it:
Set clear ownership boundaries with clients, use well-supported frameworks, and rely on managed front-end hosting to reduce operational load.

When hybrid headless CMS makes sense for your agency{h

Not every agency needs to throw out familiar tools to go headless. Many traditional CMS platforms now support headless architectures, allowing teams to modernize delivery while keeping content workflows that clients already understand. 

This hybrid approach improves performance and front-end flexibility without forcing a full reset. It reduces onboarding friction, preserves institutional knowledge, and provides a practical upgrade path to more advanced architectures when needed.

The trade-off is depth. Hybrid setups can limit customization compared to purpose-built headless CMSs, so the right choice depends on the client, timeline, and how much control the project demands.

WordPress, Drupal, and Joomla: evolving with headless

Platforms like WordPress, Drupal, and Joomla can now act as content hubs while modern front-ends handle presentation. Content is delivered via APIs, and teams are free to build with frameworks like React or Next.js.

For agencies, the appeal is straightforward:

• Clients keep familiar editing workflows
• Developers gain flexibility in how experiences are built
• Performance and security improve through decoupled front-ends
  

This approach works well for agencies modernizing existing accounts or scaling premium projects without retraining content teams from scratch.

That said, hybrid setups come with trade-offs. Preview workflows often need custom work, and not all plugins or extensions are designed for headless use. These are manageable challenges, but they need to be planned for upfront.

Marketing platforms taking a headless role

Platforms like Wix and HubSpot aren’t headless CMSs by design, but their APIs allow agencies to use them in headless-like ways.

This works best when:

• The client is already deeply invested in the platform
• Marketing automation, CRM, or commerce are as important as content
• Speed and integration matter more than deep content modeling
  

For agencies serving SMBs or marketing-led organizations, these platforms can accelerate delivery. For complex content systems or large-scale publishing, they’re usually a stepping stone rather than a long-term CMS foundation.

How to choose the best headless CMS for your agency in 2026

1. Start with what you’re actually building

Twenty product pages need a different infrastructure than a content ecosystem with thousands of interconnected pieces. When evaluating headless CMS platforms for your agency, feature sets matter less than workflow reality: do your clients need elaborate approval chains with regional sign-offs, or should editors just publish? This clarity determines if you need enterprise governance or something less complex.

2. Channel strategy reveals your technical reality

Most platforms deliver to websites. But delivery to web, mobile apps, kiosks, and voice interfaces across multiple markets is a totally different challenge. The right agency CMS selection depends on how much content gets reused versus rebuilt for each channel. A blog post that appears everywhere unchanged needs less infrastructure than content that adapts substantially per platform.

3. Migration makes or breaks timelines

Content volume creates work, but structure creates risk. Clean taxonomies that map directly to new models enable smooth transfers. Inconsistent legacy data with manual cleanup ahead? Expect the unexpected. Phased rollouts reduce risk but extend complexity. Complete transitions compress schedules but intensify coordination. Match the approach to your project’s tolerance for running parallel systems.

4. Budget beyond the price tag

Platform fees are just the entry point. Schema design, API integration, custom tooling, and team training frequently cost more than annual subscriptions. Watch pricing models closely: per API call, per user, or per content entry. What looks affordable at launch can become expensive at scale. Factor in hosting, bandwidth, maintenance, and support, as it often happens that the true cost picture emerges over time.

5. Stack alignment drives velocity

React teams build Next.js front-ends deftly. Forcing them into Vue slows everything. GraphQL advocates struggle with REST-only platforms. Match platforms to existing team strengths unless you’re building new capabilities on purpose. Misalignment creates friction that builds up across every sprint.

6. Localization separates regional from global

Three languages with shared structure? Straightforward. Thirty languages with country-specific compliance, currency handling, and cultural nuances? You need sophisticated tooling. Consider where translation happens: inside the CMS or through external systems. Workflow architecture matters as much as language count.

7. Team capability determines platform fit

Technical writers comfortable with structured data thrive in developer-focused systems. Marketing teams expecting visual editing and instant previews need different tools. When routine content changes require developer intervention and several approval stages, you’ve chosen wrong, no matter the platform’s technical sophistication.

On a final note

Through our digital solutions and development services, we at GetDevDone have seen headless CMS consistently reduce dev bottlenecks and speed up multi-channel delivery.

The platforms that work best are API-first, support real collaboration, and integrate cleanly. There’s no single winner, though. Some tools optimize for speed, others for content control. The right choice depends on cost, support, scalability, and whether it fits your team’s workflow and client expectations.

You don’t have to go fully headless. Many traditional CMSs now support headless delivery, giving you modern performance without breaking familiar workflows. Hybrid setups favor practicality; purpose-built headless offers deeper control. Choose based on the project, timeline, and level of control you actually need.

If you’re evaluating headless CMS options, contact our team to help you separate signal from noise and identify what fits your delivery model.

FAQs

What is the best headless CMS for agencies in 2026?

There is no universal best headless CMS for agencies. The right choice depends on governance depth, stack alignment, and delivery complexity. Enterprise teams often select Contentful, Kontent.ai, Magnolia, or WP Engine Atlas for SLA, compliance, and auditability. Developer-led agencies prefer Strapi or Sanity for schema control and code ownership. Marketing-driven teams choose Storyblok or Prismic for visual editing and faster publishing.

At GetDevDone, selecting the best headless CMS for agencies always starts with business context and operational reality: scope, processes, and team collaboration.

How do headless CMS solutions for agencies improve delivery efficiency?

Modern headless CMS solutions for agencies separate content from presentation through APIs. Developers build front-ends independently, while marketing teams manage content without developer tickets.

This parallel workflow reduces dependencies, shortens time-to-market, and limits unnecessary QA cycles. For C-level leaders, the benefit is operational clarity: predictable releases, controlled maintenance, and scalable multi-channel delivery without proportional headcount growth.

GetDevDone supports agencies in structuring CMS architecture around real delivery constraints: clear ownership, controlled releases, and minimized operational friction.

Are top headless CMS platforms for agencies better for SEO?

The top headless CMS platforms for agencies do not automatically improve SEO. They provide control. Technical SEO elements, like metadata, structured data, rendering strategy (SSR, SSG, ISR), localization logic must be implemented intentionally.

Headless architecture often improves Core Web Vitals and performance when engineered correctly. The advantage is architectural flexibility, not default plugins. Agencies that standardize SEO components in their delivery pipeline see more consistent ranking and performance gains.

When should an agency choose hybrid over a fully headless CMS?

A hybrid approach (for example, headless WordPress via WP Engine Atlas) makes sense when modernizing existing client portfolios without disrupting editorial workflows. This path works well for agencies upgrading performance and security while keeping familiar CMS environments. It reduces onboarding friction and protects institutional knowledge.

Fully headless platforms are better suited for multi-channel ecosystems, composable architectures, and high-scale environments. The decision should match project complexity and governance needs.

How should agencies evaluate the best headless CMS for agencies beyond pricing?

Selecting the best headless CMS for agencies requires a delivery-first assessment. Subscription cost is visible. Operational impact is not.

Evaluate how the platform handles structured content, approval workflows, localization, and API limits under real production load. Review integration depth with analytics, DAM, commerce, and internal systems. Assess migration complexity early, as legacy taxonomy often creates more risk than licensing.

From GetDevDone’s experience supporting agency delivery models, the deciding factor is rarely features. It is whether the chosen headless CMS for agency operations reduces deployment drag, limits rework, and keeps front-end ownership predictable over time.

A platform that fits the team’s technical strengths and client governance needs will protect margin. One that does not will increase coordination overhead, regardless of price tier.