For a decade, the Martech "stack" was a collection of destinations. We didn't just use HubSpot, Marketo, or Salesforce; we lived in them. These platforms were the “cockpits”, opinionated interfaces that dictated how we segmented audiences, orchestrated journeys, and measured success. If you wanted to run a campaign, you logged in, followed the vendor’s workflow, and played by their rules.

But something fundamental has shifted. The centre of gravity is moving, and it’s moving downward.

From Software to Scaffolding

We are witnessing a great inversion. People who once spent eight hours a day inside the "Big Four" platforms, Braze, HubSpot, Marketo, and Salesforce, are talking about them in a way that would have seemed sacrilegious five years ago. They are describing them as back-end services.

They are still essential. They are still the "source of truth." But they are no longer where the work happens.

Instead of logging into a Salesforce dashboard or a Braze journey builder, marketing ops teams are now building their own custom AI agents and lightweight apps that sit on top of these platforms. The platform has transitioned from being the "application" (the thing you interact with) to the "infrastructure" (the thing that powers the tools you actually use).

Grounding the Ghost in the Machine

The rise of AI agents is the catalyst for this migration. A year ago, the conversation was about how to add AI into HubSpot or Marketo. Today, the conversation has flipped: how do we use HubSpot and Marketo to ground our AI agents?

In this new model, the value of a platform isn't its UI or its specific "opinion" on how to send an email. Its value is its data, its identity management, and its APIs. It provides the grounded data, the “context-as-a-service”, that allows an AI agent to act intelligently.

When an agent needs to know which customer is at risk of churning, it queries the infrastructure (Salesforce). When it needs to trigger a personalized message, it calls the back-end service (Braze). The human operator interacts with the agent; the agent interacts with the plumbing.

Buying the Butter, Not the Frozen Dinner

As Scott Brinker aptly puts it, we are moving away from the "frozen dinner" era of SaaS. For years, we bought a vendor’s specific opinion on how marketing should work, pre-packaged and rigid.

Now, we’re buying the high-quality ingredients (the infrastructure) and doing the cooking ourselves. We buy the "butter" (the data layer and delivery engines) and use AI to build custom "meals" (bespoke agents and workflows) that are perfectly tuned to our specific business logic.

This isn't "build vs. buy." It’s "build on buy." We buy the infrastructure because building a reliable, compliant, and scalable database or delivery engine is hard and low-leverage. But we build the agentic layer because that is where the competitive advantage now lives.

Conclusion: The Screen is Optional, the API is Everything

This shift marks the "Third Age of Martech." If the first age was about the birth of the suite, and the second was about the explosion of the ecosystem, the third is about headless utility.

For Martech vendors, the stakes are existential. The platforms that will survive are the ones that realize their UI is now optional, but their API is everything. They must become “agentic”, designed to be operated by machines as much as by humans.

For the rest of us, the opportunity is immense. We are no longer limited by the "out-of-the-box" features of our software. By treating our once-mighty platforms as foundational infrastructure, we free ourselves to build a marketing operation that isn't just "powered by AI," but is natively built for it.

The cockpit may be empty, but the engine has never been more powerful.