Composable martech gains ground as marketers weigh flexibility against governance
Composable marketing technology is attracting interest as organizations look for ways to add capabilities, incorporate AI and modernize technology stacks without replacing everything at once. But modularity does not eliminate complexity: it makes integration, ownership and cost management more visible responsibilities for marketing and technology teams.
That trade-off framed the panel “Built to adapt: Why composable martech is becoming the new standard” at the November 2026 MarTech Conference. Speakers Craig Schinn, COO of Actable; Gene De Libero, founder of Digital Mindshare LLC; Kristina Kalpokaite, head of martech at Loop Horizon; and Yefim Natis, principal analyst at Natis Labs, discussed how companies can pursue architectural change at a pace their teams can govern.
A hybrid stack can be a deliberate destination
The panel’s approach challenged the idea that composable architecture demands a wholesale shift away from existing platforms. Kalpokaite described a model in which customer data and core business logic are anchored in a central data warehouse, while specialized tools connect to that foundation to carry out particular marketing tasks.
In this structure, the central environment supports data hygiene and audience segmentation, while tools at the edges can be replaced as requirements change. The approach offers a route to flexibility without requiring companies to discard systems that continue to serve a useful purpose. It also makes the warehouse and the quality of its connections important parts of the operating model.
Natis emphasized the practical limits of major technology overhauls: business operations must continue while systems change. He also noted that technology considered cutting-edge today can eventually become legacy infrastructure. Taken together, those points argue for treating architecture as an ongoing set of choices rather than a one-time migration to a supposedly final state.
De Libero said retaining a hybrid stack need not mean a company has failed to complete its roadmap. For lean teams with constrained resources, or organizations facing strict compliance requirements, fewer integrations and dependable core tools may be more manageable than a broad redesign. The appropriate balance depends on what a team can maintain and scale, rather than on an idealized version of composability.
Integration requires ownership, not just APIs
APIs can move information between systems, but the panelists stressed that technical connectivity alone does not ensure a useful integration. Kalpokaite said engineering and analytics partners need to understand how campaigns work in practice. Without that context, a technically sound connection can still send unsuitable fields to the tools that marketers rely on.
De Libero recommended treating a composable stack like an internal product, with a designated owner. As organizations move away from an all-in-one suite, they take on more direct responsibility for understanding data flows, mapping dependencies and governing costs. A named owner can help keep those concerns in view across teams, rather than leaving them as disconnected technical tasks.
Costs are part of that oversight. De Libero pointed to a consequence of moving workloads to a central warehouse: compute usage moves with them. Queries that are not monitored can increase infrastructure bills. That makes the financial effects of integration decisions part of the governance discussion, not an issue to consider only after deployment.
Schinn’s advice was to scope integrations around the customer signals that actually support engagement. Connecting every available data point is not necessarily valuable. The more useful objective, as the panel framed it, is to deliver reliable, high-impact signals into marketing workflows.
Modernize at a maintainable pace
The discussion presented composability as a way to adapt a martech stack incrementally, not as a guarantee of simpler operations. Each additional connection creates work to oversee, and a more modular design makes clear ownership and cross-functional understanding essential. Teams also have to weigh integration effort and ongoing costs against the capabilities they expect to gain.
For marketing leaders, the practical question is therefore not simply whether to adopt a composable architecture. It is which components should remain central, which specialized tools merit a connection, and whether the organization has the capacity to manage those relationships. A hybrid stack can be a durable outcome when it reflects real operating needs and keeps essential data and workflows under control.
The panel’s central message was measured: change the stack without assuming that everything must change at once. A realistic modernization plan can preserve dependable systems while creating room to replace selected tools. Its success depends on governance, an accountable owner and integrations designed around useful signals—not on modularity for its own sake.
