The martech landscape reached 15,505 tools in 2026. If you have been waiting for consolidation to simplify your technology decisions, that wait is the problem. The market is not consolidating. It is stratifying: winners are emerging within categories, a long tail persists, and a new layer of AI agents is forming on top of existing systems. The mental model most organizations use to make stack decisions is outdated, leading to paralysis, misplaced bets, or both.
Why This Matters Now
Most marketing and technology leaders operate under three incorrect assumptions:
- Consolidation is coming. This leads to decision paralysis. Teams defer investments and tolerate duct-taped integrations, losing ground to more agile competitors.
- AI will replace the stack. This leads to expensive experiments built on tools that cannot function without the deterministic infrastructure underneath them.
- It is too early to act. This is a costly mistake. Agent-optimized customer journeys are not a speculative forecast; they are arriving now.
Research from Scott Brinker and Frans Riemersma in the State of Martech 2026 provides the empirical frame to dissolve these assumptions. The landscape is not shrinking. Specific categories like CMS, iPaaS, eCommerce, and workflow tools are growing, while eight other categories are in quiet decline. The story is not "fewer tools." It is "different tools winning in different layers for different reasons."
The Two-Layer Model for Architecture
Your stack is not one thing. It is two layers doing fundamentally different work:
Layer One: Deterministic SaaS
This includes your CRM, marketing automation platform, CMS, and data pipelines. These systems are rule-based, reliable, and predictable. They are infrastructure, not intelligence. They do exactly what you configure them to do, every time.
Layer Two: Probabilistic AI Agents
These operate on top of the SaaS layer, handling dynamic, context-dependent decisions. They determine which content to surface or how to adapt a journey in real time based on signals the deterministic layer cannot process at speed.
These layers are complementary. You cannot run AI agents without clean, reliable infrastructure underneath them. Conversely, your infrastructure never gets smarter than its last manual configuration without agents. The assessment determines the architecture, and the architecture determines the platform.
Auditing for Stratification
If consolidation were real, a stack audit would simply mean choosing fewer, bigger platforms. Stratification makes the audit more nuanced. The right question is: "Which of our tools sit in growing categories, which sit in declining ones, and which are doing work that an AI agent will do better inside two years?"
One proposed scoping model relies on three intersecting variables:
- Actual company goals.
- Observed customer needs.
- Genuine system capabilities.
If a tool or agent does not sit at the intersection of all three, it is shelfware waiting to happen.
The Role Shift No One Is Staffing For
The people operating the stack are undergoing a fundamental evolution. Campaign managers are becoming multimodal operators, managing cross-channel orchestration across deterministic and probabilistic systems. System administrators are becoming stack wranglers and context engineers who configure both platforms and the AI agents that sit on top of them.
This shift is happening now. The question is not whether to hire for these roles, but where your current team sits on this arc and what they need to move to the next stage.
Strategic Limitations
These frameworks provide better mental models, but they do not eliminate the hard work. It is important to note that these models are built on strategic analysis of external research, not on completed client engagements where these specific arcs were measured at scale.
Stratification means your audit is more complex. A two-layer model provides an architecture to think with, but it does not tell you which specific AI agents are ready for production in your specific context. Furthermore, the research does not dictate what to do about the eight declining categories. The response depends on your migration readiness, contractual commitments, and capacity for change.
Immediate Steps
- Map your stack against the two layers. Identify gaps where deterministic processes could be handled by agents, or where agents lack reliable infrastructure.
- Audit against category trajectory. A best-in-class tool in a declining category is a migration waiting to happen.
- Assess your team against the role arcs. Create a development plan to move people forward one stage in the next six months.
Bring this dispatch into a working session - one page in, scoping memo out.
Brief Foyer