A typical CMO writes most martech postmortems from their own perspective. I’ve sat in those rooms for 30 years, and the story rarely changes.
The platform underdelivered, the ROI never showed, or the vendor oversold the demo. The tools take the blame, but the stack never gets to answer. This time, I’m going to let it respond.
Picture a CMO in a room with her martech stack, facing 18 months of spend, flat results, and a CFO asking what the money bought. She’s done being patient. The stack, for once, talks back.
The CMO explains that she invested in the martech stack to help her team move faster. She needed better segmentation, cleaner data, and the personalization engine her team asked for over two budget cycles.
Yet 18 months later, campaign velocity is flat. Plus, her two reporting tools show different numbers for the same metric. What exactly is she paying for?
The stack responds that she’s paying for three tools that do overlapping work. For example, the customer data platform (CDP) and the marketing automation platform (MAP) both build audiences. They draw from the same slice of customer data and define segments differently.
The world’s most powerful SEO platform, purpose-built for Enterprise.
The cost of ongoing maintenance
The CMO believes the integrations are responsible for handling the overlap between tools. But the stack reveals that API updates broke integrations. That demanded ongoing engineering resources.
That cost hasn’t been on the CMO’s radar. Historically, she’s tracked only tool subscriptions. But she hasn’t considered the cost of keeping the stack running as a connected system because her accounting framework isn’t built to catch it.
The difference between familiarity and capability
Although the CMO believes her team received sufficient training on each component, the stack clarifies what really happened. It explains that her team learned the stack’s buttons, which fostered familiarity. A customer success representative walked her team through building a segment, configuring an identity rule, and exporting to a channel.
But the team still lacks capability. Capability involves knowing which segment to build for the campaign you’re running next quarter and why exports to your MAP and your ad platform need different structures.
The CMO paid for familiarity and assumed capability would follow. But the first 60 days after the stack went live established the ceiling. No one built the work into the team’s rhythm.
The inevitable performance drift
The CMO wants to know why the martech stack’s performance has gotten worse. The stack explains that it was configured for the business that existed at launch, but the business has since evolved. Now the business has new channels, volume, and expectations.
The stack continuously reports on uptime, error rates, and throughput. Yet no one acts on the data. This inaction causes the stack to drift over time, which the CMO only notices once it’s expensive to fix.
The eventual lack of ownership
Finally, the CMO asks about a certain martech tool in the stack. Few team members use it, and finance keeps flagging it. The stack explains that the team that originally needed it was reorganized 18 months ago, yet the subscription automatically renewed.
The organization has an elaborate procurement process involving evaluation committees, scorecards, business cases, and approval chains. But there’s no established process for removing a tool from the stack. Tools stay by default, so the stack continues to grow.
The person who initially selected the stack changed roles a year ago. The stack now has no owner.
It runs and consumes budget, but it’s nobody’s job to decide whether the stack still earns its place. Instead, the CMO governs by default. Whoever buys the tool owns the tool, and when they leave, nobody takes ownership.
The ROI disconnect
The CMO asserts that in 18 months, the stack never provided a single number she can take to her CFO. The stack reports activity but not capability. She’s left to make seven-figure renewal calls based on anecdotes and whoever complains loudest.
The stack explains that someone was supposed to connect its output to business results. But the team never assigned that responsibility.
Translating activity into outcomes takes human judgment. Yet that person doesn’t exist on the org chart. The stack reports what it can measure, and the CMO reads what she can get.
Close the gap between buying and running martech tools
Neither the CMO nor the martech stack is the villain. The CMO bought good tools for real reasons, and the stack did roughly what it was configured to do. The organization still needs a person to manage the stack as a system, evaluate whether each tool still earns its place, maintain the integrations, and connect output to business results.
That role requires headcount, a budget line, and the authority to cut a tool a VP championed. A reasonable benchmark is one operations person per three to four core platforms, with a training investment to match. Many organizations won’t fund it.
Stop auditing the tools and audit the gap between who buys them and who runs them instead. Assign someone the mandate, budget, and authority to manage the stack. Do that, and the next time your CFO asks what the stack is worth, you’ll have an answer that isn’t a shrug and a renewal invoice.
The post If your martech stack could talk, what would it say? appeared first on MarTech.