
Intuitive tools have pushed more of the marketing workflow out to distributed teams, though the pull runs both ways: Forrester found that 14% of field marketing teams were fully centralized in 2025, up from 9% in 2023. When everyone is a marketer, then all tools must enable marketers. This is the central challenge facing enterprise marketers looking to move to a decentralized marketing model.
In our work with the top enterprises on the planet, we've observed a new model emerge: a hub-and-spoke model with tech at the center enabling distributed teams. To decentralize, we may need to centralize our tech stack.
Should enterprise marketing be centralized or decentralized?
Most enterprise teams do best with neither extreme: centralize the technology, templates, and approvals, then let regional teams execute on that shared platform. Pure centralization builds a queue at HQ, and unchecked decentralization produces brand drift. Knak's 2026 research found 56% of organizations already run this hybrid structure for campaign production.
Model | Who builds | Who governs | Strength | Risk |
|---|---|---|---|---|
Centralized | A central team at HQ builds every asset | HQ | Tight brand control and one standard | A queue at HQ, slower launches, and campaigns that miss local markets |
Decentralized | Each region, on its own tools and templates | Each region | Speed and local relevance | Brand drift, duplicated effort, and tool sprawl across business units |
Hub-and-spoke | Regional teams, from central templates and modules | Marketing ops sets templates, permissions, and approval workflows | Local speed with a consistent brand | Depends on marketing ops keeping the shared system current |
Why centralized vs. decentralized is the wrong question
For enterprise teams with a centralized marketing operations function, the opportunity is to use technology to enable everyone on your team. An interesting observation from our own customers is that SMB teams lean on centers of excellence, while enterprises face continued demand for decentralization.
That split makes sense, because enterprises operating on a global scale have distributed teams in many locations. Field marketers responsible for a region may be supported by a small, capable team, but not the full support or attention of the centralized ops function. For enterprises, picking the right model is essential.
Pure centralization may not be the answer, because it can build a queue at HQ, slow your time-to-market, and leave campaigns out of step with local markets. The same Forrester research found 57% of field marketers do little or no adaptation of global content. Requiring everyone to funnel requests and approvals through a central command post can be a challenging proposition.
The hub-and-spoke model
The hub-and-spoke model centralizes systems and decentralizes execution, which provides the best of both worlds:
- Center of excellence accessible to everyone in the org
- Clear brand controls and approval workflows
- Collaboration without delay
- Distributed teams execute quickly
- Creative freedom within the bounds of brand guardrails
The role of marketing operations in this model is strategic enabler. They orchestrate the systems that everyone uses (ensuring consistent data collection, workflow execution, and requisite templates) while enabling distributed teams to execute marketing campaigns without being bogged down by process.
Decentralization with marketing operations as the focus
Technology is the great enabler in modern marketing. The continuous and rapid development of martech has propelled marketing operations teams to the forefront, and MOps roles and team structure have grown with it. Undoubtedly one of the most important teams, they ensure that the lights stay on and all processes run smoothly. They are the engineers behind the marketing machinery.
As such, marketing operations plays an important role in decentralization, including choosing the self-serve marketing tools distributed teams rely on. Technology infrastructure is the key to linking all the distributed marketing nodes around the world. Regardless of where you work, technology connects you back to headquarters. MOps teams must consider dozens of variables when deploying new technology:
- Does it integrate with our tech stack?
- If it doesn't integrate with all our tools, which tools do we need to evaluate?
- How do the workflows of a new system improve or fit into existing processes?
- How do we govern the application while still enabling autonomy?
- Does it give regional teams autonomy without each business unit buying its own tools?
- Who owns the templates and permissions once it's live?
Keep permissions, privacy settings, and integrations central, and let regions control the content they build inside them.
Custom builds and vendor lock-in are persistent challenges in enterprise marketing. Oftentimes, enterprises require unique tools and features, potentially even integrating custom vendor work or homegrown systems. Replacing these is a hurdle of technology and habit.
In the hub-and-spoke model, we also have the opportunity to utilize composability: point tools that do a few things extremely well versus monolithic, all-encompassing suites. The end of the journey is a well-oiled decentralized team, but the side-quests along the way can create roadblocks and difficult challenges.
What are the essential components of a centralized marketing platform?
Let's consider how we approach evaluating software for our hub-and-spoke strategy. True decentralization is tech-enabled, but that puts a lot of onus on MOps to make informed choices.
Here's how you might review deploying an email template system to enable a distributed team with email campaigns.
Component category | Core functionality | Hub benefit | Spoke enablement |
|---|---|---|---|
Template and asset libraries | Pre-approved, modular design components that ensure brand consistency at scale | Centralized brand control and shared updates | Creative freedom within established guardrails |
Integration stack | Native connections to marketing automation platforms (Marketo, Salesforce, Eloqua) | Assets sync directly to each platform | Execution without platform switching |
Collaboration and approval workflows | Real-time commenting, review cycles, and multi-level approvals | Process governance and compliance oversight | Faster approvals without email ping-pong |
Governance and permissions | Role-based access controls and brand guardrail enforcement | Maintain brand integrity | Autonomous creation within defined boundaries |
Dynamic content engine | Built-in personalization and dynamic content, with AMPscript for SFMC and Velocity-based dynamic content for Marketo | Strategic personalization standards | Tactical execution without technical barriers |
Multi-language support | AI translation and localization workflows | Global brand consistency across markets | Local market relevance and cultural adaptation |
Cross-platform optimization | Testing across email clients and devices | Rendering and quality standards | Fewer surprises at deployment |
Project management integration | Integrations with Asana, Monday.com, and team communication tools | Request tracking in the tools the team already uses | Less switching between tools |
AI assistance | Subject line generation, alt text creation, and content optimization | Brand voice consistency at scale | Enhanced creativity and accessibility |
Analytics and performance tracking | Campaign performance data and optimization insights | Strategic decision-making from engagement data | Data-driven local optimization |
Self-service as the default
Centralized technology must be self-service. In my opinion, it's non-negotiable in modern digital marketing. Self-service means having the ability to do your job within the application without help from internal or external resources, and to push the finished asset to your MAP when it's ready.
Self-service tools open adoption to the whole organization, and they take off when they are married to organizational processes, eliminating redundancies in your workflows and speeding up time-to-market.
Take sending an email campaign. In the enterprise world, the lifecycle of that campaign can span days or weeks from the time you submit the initial request to getting that email developed, and Knak's 2026 research found 36% of teams need at least one full business day to produce a single email. With centralized technology, you can enable team members throughout your organization with automation, notifications, and tools to get the job done quicker.
To get to this state, you need to map out your current processes, find where requests stall, and discover opportunities to boost efficiency. What if all requests were submitted via a project management tool that integrates with your email builder? As the template is developed, reviewers are notified when they are needed to review materials. Once approved, the template is synced directly to your MAP ready for your next campaign.
Traditional ways of doing things, cobbling together requests through a hodgepodge of Google sheets and email attachments, give way to smoother processes, because self-service isn't just ease of use, it's also about governance and process improvement. The role of martech in decentralization is to enshrine process in the technology, to ensure that workflows are clearly understood, and that the system is accessible and available to the right people. MOps' mandate is to map this out and conduct all the players in the orchestra.
The competitive advantage of getting it right
Enterprises are already using the hub-and-spoke model to enable their distributed teams to do more with… more. The best way to scale creativity, the fuel of successful marketing campaigns, is to centralize the tools that make creativity possible.
In the old model, launching a locally relevant campaign meant rounds of back-and-forth with headquarters. In the new model, they grab pre-approved assets, customize them for local needs, and launch routine assets without waiting on HQ. The brand stays consistent, but the execution becomes faster.
This shift requires marketing operations teams to think differently. Instead of being the gatekeepers who slow things down, they become the engineers who speed things up. They build the systems that make "yes" the default answer.
Are enterprise teams moving faster on a unified platform?
Two Knak customers show two different gains on a shared platform. Citrix measured participation, with far more people able to build emails, and SAP measured sign-off, with time to approval down 60%. Neither is a full speed-to-market figure, but together they show where one central platform helps: more people building, and faster sign-off.
"In a matter of weeks, we went from having just five people creating emails to over 80 people with the ability to create emails," said Cory Riley, Marketing Operations Solution Lead at Citrix.
Knak is the agentic production layer for enterprise marketing: marketing ops sets the templates, permissions, and approvals once, and distributed teams produce on-brand emails and landing pages from them. Your MAP still sends, and Knak produces what feeds it.







