Martech strategy that survives contact with the stack

The Martech contracts dates and rights

87% of Martech contracts renew themselves and 86% say nothing about whether your customer data trains someone else's model. The paper decides.

Last time I argued that the cheapest money in a Martech budget is the capability you're already buying twice, and that the way to find it is to sort your invoices by capability instead of by supplier.

Say you do that. You find one. Now what?

Now the paper decides. And the terms that decide it aren't the ones I went through in the pricing series. Not the meters, not how a vendor counts a profile or an event.

But the dates, and the rights.

I've been handed a lot of Martech contracts over the years, usually

The Martech Stack you bought twice

Unused features cost nothing. A second contract for a capability you already own costs what the invoice says, and no utilization survey will find it.

Just like my previous article, and most because of the fast moving pace of Martech, I revisited some early work.

Back in July I went at whether AI closes the gap in Martec's Law, and part of that piece dealt with the Gartner utilization number. 58% of stack capability in use in 2020, 42% in 2022, 33% in 2023, with the 2025 reading climbing back toward 49% under a slightly different question. Directional rather than gospel, as I put it at the time.

I still think that's right.

What I didn't do is ask why the dead

Discovering Martech is like getting lost in London

Even after 20 years in Martech, I recently felt lost. With 15,000 tools and constant change, the problem isn’t access to information, it’s knowing what actually matters. This piece explores why teams struggle to navigate Martech, and where decisions really break down.

I’ve been doing this work for close to twenty years now.

Helping companies make sense of their data and marketing technology, guiding selections, fixing what doesn’t work, occasionally building something in between. It’s been a fairly consistent thread.

And recently… I found myself staring at it all thinking:

“I’m not entirely sure where I’d start anymore.”

That’s not something I say lightly.

It has been half a year since the State of Martech 2026 edition was published. It included a staggering 15,000+ tools.

Fifteen thousand.

At that point, it stops being a catalogue.

Announcing Piedmont: why I restructured my practice around building, not just advising

Piedmont is French for Niederberger. Foot of the mountain. It's where most organisations find themselves when they reach out. I built a practice around that moment. Here's what it looks like.

If you read my post at the end of last year, you know that my client work changed toward the end of 2025.

It wasn't dramatic. No single conversation triggered it. But looking back at December, roughly 20% of what I was doing had moved from strategy and advisory into actually building things. Custom data apps, operational tools, activation layers that clients needed but couldn't find off the shelf. By April 2026 that number was closer to 50%.

When half your work has subtly become something different from what your practice was named for, it's time to

Negotiating the New Martech Economy

Most Martech vendors talk about “transparency,” yet the real negotiation is about who ends up carrying the complexity. Part 3 explores how ownership, definitions, velocity, and data reality shape what you can truly negotiate in today’s CDP/CEP market.

The reactions to last week's part 2, The inherited costs of the composable stack, revealed something important about Martech today. People disagreed with one another, yet they were all touching the same truth from different angles. Some pointed out that composable savings mostly show up in use-case velocity rather than infrastructure. Others argued that cloud costs are a black box, no matter what you buy. A few reminded us that the data warehouse remains the gravitational center regardless of whether your CDP is composable or packaged.

What everyone circled around, though, was the same underlying question: who

The inherited costs of the composable stack

In Martech, every pricing model hides a workload. Suites sell convenience. Composable platforms sell control. Either way, you pay for someone to hold the complexity, the only question is who.

Last week, in the first part of this series, I shared some experiences on how to read Martech pricing. In this second part, I want to examine the other end of the product spectrum and learn to live with it. Once you understand how vendors define usage, value, and fairness, a new question appears:

What happens when you try to escape those models altogether?

That’s where composability enters the story. It promises freedom from rigid licenses, bundled modules, and predefined ways of working. Build your own stack, plug in best-of-breed tools, let each component scale on its

Posts tagged with Martech strategy