Marketing Is Being Rebuilt Around Machines. Most Architectures Haven't Noticed.

MarTech is having its most interesting moment in a decade. Agents that run campaigns on their own. Creative generated at scale. Entire stacks collapsing into AI native platforms. Personalisation that finally works without a data team babysitting it.

Most of the commentary on this is written from the marketer’s chair. What the tools can do, what the campaigns will look like, what the numbers might be.

I want to look at it from a different seat. I spend my time on enterprise architecture, and from where I sit the interesting question is never what a new capability can do. It is what it does to everything you already built.

Over the past month I worked through four of these shifts one at a time. This is all of it in one place.

1. Your Next Customer Is an Agent

For twenty years, every marketing system we built assumed a human on the other end. A person searching, browsing, comparing, clicking. Our entire MarTech architecture is optimised for human attention.

That assumption is breaking.

A growing share of customer interactions is becoming agent to agent. A shopper’s AI assistant checks stock, compares options, and verifies delivery. The brand’s agent responds. The transaction happens between two pieces of software, and the human sees only the outcome.

Think about what that does to your architecture. Your content needs to be machine readable, not just persuasive. Your product data needs structure an agent can parse in milliseconds. There’s even a new metric emerging for this. Share of model. How often does an AI recommend your brand at all?

Here’s the part that should worry architects. If your systems can’t talk to agents, your brand isn’t losing the conversation. It’s not in the conversation.

Most enterprises are still optimizing the human journey. The buyer is quietly becoming a machine.

2. The Stack Was Built Around Campaigns. The Campaign Is Disappearing.

If the customer is changing, the stack that serves them cannot stay the same.

For twenty years, the MarTech stack had one organising principle. The campaign. Every tool in the chain, CDP, email, ads, analytics, personalisation, exists to help a human plan a campaign, run it across channels, and measure it afterward. Best of breed grew around that assumption. So did all the integration work holding it together.

Agent driven journeys quietly remove that principle. When an agent handles the routine engagements, reorders, notifications, guidance, next best action, there is no discrete campaign to plan. There’s a goal, a policy, and a system executing continuously. This isn’t a fringe prediction either. Gartner expects exactly this shift to collapse traditional martech architectures, with marketers moving from running campaigns to supervising intelligent systems.

Here’s the part I think about as an architect. Enterprises have spent two decades and enormous budgets wiring these stacks together. Point to point integrations, identity resolution, consent flows, data pipelines. That integration layer was built for tools that wait for humans. It was never designed for systems that act continuously and talk to other agents.

So the real question isn’t which platforms survive consolidation. It’s this. When the organizing principle of your stack changes, how much of your integration architecture is an asset, and how much is debt you haven’t recognised yet?

Most enterprises haven’t done that audit. The ones that do it before the shift forces them will choose their architecture. The rest will inherit one.

3. A Thousand Decisions an Hour. Who Owns the Wrong One?

New architecture is one problem. Accountability inside it is a harder one.

The numbers tell an honest story if you read them together. Only about 17 percent of organizations have actually deployed AI agents so far. More than 60 percent expect to within two years. And over 40 percent of agentic AI projects are forecast to be cancelled by the end of 2027, with inadequate governance named among the top reasons.

The majority of the wave hasn’t arrived yet. The failure cause is already known.

Picture the scenario. An agent is live in production. It adjusts spend, picks variants, reallocates budget across channels, makes a thousand decisions an hour. Nine hundred ninety nine are fine. One isn’t. It commits budget somewhere embarrassing, or personalises in a way that crosses a line, or quietly discounts your margin away.

Now the questions that matter. Who owns that decision? Not which tool made it. Which human is accountable for the outcome? Who had authority to override the agent in production, and did they know they had it? And can you reconstruct why the agent did what it did, or do the logs only show that it did?

Most organisations racing toward agentic anything can answer none of these. They designed for what the agent can do. Nobody designed for the day it does something unintended.

There’s a practical catch in the accountability answer too. Override authority has to sit close enough to the decision to actually be exercisable. A senior leader who is accountable on paper but three escalations away from the agent isn’t a control, they’re a formality. By the time the approval chain resolves, the agent has made another few hundred decisions. So the design question becomes uncomfortable. Do you push authority down to someone fast enough to use it, and if so, are they senior enough to carry the accountability?

Capability first, control later. That’s the pattern behind the 40 percent.

4. The Agents Scaled. The Judgment Didn’t.

Everyone is asking how many agents their team should deploy. Almost nobody is asking what the humans are supposed to do differently.

If agents handle execution and humans supervise, the job doesn’t shrink. It changes shape. The work stops being production and starts being judgment. Reviewing what the system produced, catching what it got wrong, deciding what ships and what doesn’t, and knowing which of its outputs you’d stake your name on.

That’s a genuinely different skill from the one most teams hired for.

I saw a small version of this recently. We built a Skills library for our architecture team, automating a lot of the repetitive drafting. The tooling worked. What surprised me was how much the valuable work shifted toward verification, and how few people had ever been trained to verify at speed. Producing was the muscle everyone had built. Judging was not.

Scale that to a marketing organisation running agents across channels and the same problem shows up, just louder. You end up with a team that can generate a hundred times more output and roughly the same capacity to evaluate it.

The teams that win won’t be the ones with the most agents. They’ll be the ones who redesigned the human role around them.

The Thread Running Through All Four

Read these together and the same pattern shows up each time.

The buyer changed and the architecture didn’t. The organising principle changed and the integration layer didn’t. The decision volume changed and the accountability model didn’t. The output changed and the human role didn’t.

Every one of these is a case of capability arriving faster than structure. That is not a new story in enterprise technology, but the gap is wider this time because agents act continuously and at a speed no approval process was designed for.

The organisations that come through this well won’t be the ones with the most agents. They’ll be the ones who did the unglamorous work first. Mapping what they actually have, naming who is accountable, and deciding what their architecture should be before circumstances decide it for them.

Most enterprises have added AI to their tools. Very few have changed what they ask their systems, or their people, to actually do.

So the question I’d leave you with is the same one I asked at the end of each of these. Has your organization redesigned anything yet, or just added capability?

Opinions are my own.