Indonesia Singapore ไทย Pilipinas Việt Nam Malaysia မြန်မာ ລາວ
← Back to Blog

Why Your MarTech Stack Is Eating Budget and Starving Results

Audit your MarTech stack for activation gaps first — unused tools are a budget liability, not a capability asset.

Editorial illustration of a marketing technology stack as an overfed machine consuming coins and producing nothing
Illustrated by Mikael Venne

Most SEA brands own more MarTech than they activate. Here's how to audit your stack, cut the dead weight, and get tools actually working together.

The average enterprise marketing team is running 12 to 15 tools in its MarTech stack. Fewer than half of those tools are meaningfully integrated. That gap — between what’s licensed and what’s activated — is where marketing budgets quietly disappear.

This isn’t a procurement problem. It’s a strategy problem dressed up as a software problem. And in Southeast Asia, where platform ecosystems fragment across Shopee, Lazada, LINE, and Grab before you’ve even opened your CRM, the dysfunction compounds fast.

The Over-Buying Trap Is a Structural Problem, Not a Vendor One

There’s a useful visual doing the rounds in adtech circles: the digital advertising ecosystem rendered as a game of Hungry Hungry Hippos — every platform snapping up attention, data, and budget with equal aggression and zero coordination. It’s funny because it’s accurate. Vendors sell point solutions to point problems, and over time, marketing teams end up with a stack that resembles a ransom note more than an architecture.

The result is predictable. A CDP that isn’t talking to the email platform. A DSP running on audience segments built from data the DMP stopped refreshing six months ago. An attribution tool that contradicts the numbers in the analytics dashboard. Each tool, in isolation, passed its procurement review. Together, they produce noise.

The fix isn’t always addition. More often it’s subtraction — identifying which tools are genuinely load-bearing and which ones are just occupying a line item on the annual contract list.

What a Useful Stack Audit Actually Looks Like

A proper MarTech audit has three layers, and most teams only do the first one. They inventory what they have. That’s table stakes. The harder work is mapping activation rates — what percentage of each tool’s actual capability is being used — and then tracing data flows to see where handoffs break.

For a mid-sized retailer running cross-border e-commerce across Thailand and Indonesia, this kind of audit typically surfaces two or three integration failures that are silently corrupting campaign performance. Common examples: customer purchase data from Shopee not feeding back into the loyalty platform, so retention campaigns are targeting buyers who already converted. Or mobile push notifications firing through one tool while SMS flows through another, with no suppression logic between them — resulting in the same customer getting the same message twice in three minutes.

The diagnostic question for every tool in the stack is simple: if this went dark tomorrow, would campaign performance measurably change? If the honest answer is no, that’s a tool worth cutting or consolidating.


Integration Architecture Beats Tool Selection, Every Time

The instinct when performance dips is to add a tool. A new personalisation engine. A better attribution model. A fresh creative optimisation layer. Sometimes that’s the right call. More often, the problem isn’t capability — it’s connectivity.

Nest New York’s expansion into the U.K. market, recently reported by Digiday, offers an instructive parallel from the brand side. Rather than flooding every available retail channel simultaneously, the fragrance brand chose specific, deliberate distribution partners — Cult Beauty, Harrods, Selfridges, John Bell & Croyden — and built a coherent retail presence before scaling. The principle translates directly to MarTech: fewer, better-connected nodes outperform a sprawling network of loosely affiliated tools.

For Southeast Asian brands specifically, this means making deliberate choices about which platforms sit at the centre of the stack versus which ones operate at the edges. In markets where LINE dominates CRM in Thailand and WhatsApp Business drives retention in the Philippines, the architecture looks different by country — and that’s fine. The mistake is trying to force a single unified stack across markets with genuinely different platform behaviours. Build for the centre, flex at the edges.

Getting Stakeholder Buy-In for Stack Rationalisation

Here’s the political reality of any stack audit: someone bought every tool on that list. Recommending cuts means implicitly telling a colleague their decision was wrong. Handle that clumsily, and the audit dies in committee.

The more effective frame is activation, not elimination. The question isn’t should we keep this tool? It’s what would it take to actually use this tool at the level we’re paying for? Sometimes the answer is a proper integration project. Sometimes it’s additional training. Sometimes the honest answer is that the use case the tool was bought for no longer exists — and that becomes a straightforward renewal conversation rather than an indictment.

Timelines matter here too. A stack rationalisation that tries to cut five tools simultaneously while rebuilding integrations in parallel is a change management disaster. Sequence it: audit first, prioritise by revenue impact, execute one consolidation at a time. Give each change 60 to 90 days to show up in performance data before moving to the next.

The brands that get this right don’t have the most sophisticated stacks. They have the most activated ones — and that’s a meaningfully different target to aim for.

Key Takeaways

  • Map activation rates, not just tool inventory — a tool nobody uses fully is a liability, not an asset.
  • Build stack architecture around platform ecosystems that are actually dominant in each SEA market, not a one-size-fits-all global template.
  • Frame rationalisation as an activation conversation with stakeholders, not a cost-cutting exercise — the outcome is the same, the resistance is lower.

The real question for marketing technology in 2026 isn’t which new tools to adopt. It’s whether the tools already in the stack are doing the job they were bought to do — and if not, whether the fix is better integration or a clean exit. What would your stack look like if you started from the outcome you actually need and worked backwards?


At grzzly, we spend a lot of time inside exactly this problem — helping Southeast Asian brands figure out which parts of their MarTech stack are carrying weight and which parts are just carrying cost. If your tools aren’t talking to each other the way they should, or you’re not sure what you’re actually getting from what you’re paying for, we’re good at that conversation. Let’s talk

Crispy Grizzly

Written by

Crispy Grizzly

Auditing, assembling, and occasionally dismantling marketing technology stacks for brands that have over-bought and under-activated. Precision over proliferation.

Enjoyed this?
Let's talk.

Start a conversation