Conquer Local Podcast · 23 min
Key moments - from our scoring
Substance score
49 / 100
Five dimensions, 20 points each
Scott Brinker maps the AI agent landscape across three distinct domains: agents that augment marketer productivity (research, analysis, asset creation), customer-facing agents marketers control (chatbots, AI SDRs), and buyer-controlled agents (deep research functions in ChatGPT and Claude) that vendors must now optimize for. He emphasizes that agents exist on a continuum from deterministic rules-based automation to high-autonomy systems, and most practical 2026 use cases will embed agentic capabilities within structured workflow engines rather than fully autonomous systems. The real differentiation won't come from LLM model choice - OpenAI, Anthropic, and Google APIs are effectively undifferentiated - but from data hygiene, first-mile data quality, and how companies feed clean, contextualized information into these agents. Brinker advocates for API and Model Context Protocol (MCP) based integrations over browser-based agent interactions, positioning the CRM and marketing automation platform as orchestration hubs rather than being replaced. He warns that guardrails, context engineering, and AI observability are non-negotiable before scaling agentic workflows, and frames current adoption as a "horseless carriage stage" where most businesses should focus on fixing data problems while AI remains an add-on, rather than rushing toward full AI-native operations.
Agents that help marketers with their work (research, analysis, asset creation), customer-facing agents that companies control (chatbots, AI SDRs, sales engagement), and buyer-controlled agents that vendors don't control (deep research functions in ChatGPT and Claude).
All major LLM providers (OpenAI, Anthropic, Google) offer functionally equivalent APIs with near-zero differentiation; competitive advantage comes entirely from what clean, contextualized data you feed into agents and how you leverage those agents in processes unique to your business.
APIs and Model Context Protocol (MCP) are more stable and reliable than browser-based agents that simulate human UI interaction, because browser agents break when interfaces change, whereas APIs provide explicit, maintainable integration contracts.
Context engineering (well-defined instructions and controlled data inputs), AI observability systems to audit what agents do, AI governance frameworks, and acceptance that 90-95% accuracy is good for discrete tasks like email personalization or data extraction, not for strategy or high-stakes decisions.
Most businesses should treat AI as a bolt-on while still learning its capabilities and fixing data silos; rushing to full AI-native operations amplifies existing data problems, whereas embedding agentic capabilities within structured, deterministic workflows offers higher ROI with lower risk.
Our reviewer’s read on each dimension, with quotes from the episode.
The episode offers a serviceable three-category agent taxonomy and a useful point about data being the only true AI differentiator, but much of the runtime is spent on broadly known ideas (intern metaphor, deterministic-to-autonomous continuum, 'horseless carriage stage') with little truly novel insight per minute. Too much ground is covered shallowly in 23 minutes.
All of the competitive advantage is entirely a function of like okay, what data do we feed into these things and how do we leverage these things in a process that is unique to our business?
we are starting to see agents that the marketers don't control, that it's the buyers who control these
The buyer-controlled agent category (third type) is the freshest framing offered, but the episode leans heavily on recycled takes - the 'treat AI like a bright intern' line is ubiquitous, the 'AI native' trajectory is a stock prediction, and the 'jagged frontier' is explicitly borrowed from Ethan Mollick. Little here would surprise a moderately well-read martech operator.
treat it like an intern, a very bright but entirely inexperienced intern
eventually we will become AI native to the point that even the phrase AI native probably won't be much. Just like we no longer say digital marketing
Brinker is a legitimate martech practitioner with 14 years of landscape mapping and a VP-level HubSpot role - genuinely credible and relevant. However, in this conversation he operates mostly as a knowledgeable explainer rather than sharing operator-level war stories or hard-won decisions, which caps his impact.
14 years of mapping those thousands of logos taught me that tech is 10%
I am a believer that the best way to do that is through APIs or this model context protocol
Brinker name-drops real tools - ChatGPT deep research, Claude, Google's A2A protocol, Perplexity Comet, OpenAI Operator - which provides some grounding, but there are zero metrics, zero named client examples, no campaign results, no dollar figures, and no timelines beyond vague 'next six to 12 months' hedges.
Google has that uh, a to a agent to agent protocol. That is, we may get there. Right now most of that stuff is still in basically a science fair state
the perplexity one comet, um, uh, what was that, the OpenAI when they did that operator agent thing early in the year
The host provides reasonable topic sequencing and a few structurally sensible questions (guardrails, orchestration layers), but questions are broad and telegraphed, there is no pushback on any claim, no challenged assumption, and no follow-up that extracts deeper specifics. The conversation flows more like a guided tour than an interrogation.
You know, been saying that the agents now are a different type of animal and so just to have a bit of a level set, map out what you mean
Let me ask you about APIs. APIs are going to be super important for the future, uh, of the marketing stack
Computed from the transcript - who did the talking, and the words that came up most.
▶️ Watch this episode on YouTube Your Martech stack isn’t broken - your mental model is. Your Martech stack isn’t broken - your mental model is. In this episode, we sit down with Scott Brinker, Godfather of Martech, editor of Chief Marketing Technologist and VP of Platform Ecosystem at HubSpot, to unpack a reality most marketers miss: The Martech explosion isn’t chaos - it’s the early stage of an AI-orchestrated system that’s about to collapse thousands of tools into workflows. If you’re feeling crushed by: An exploding Martech landscape, AI tools launching daily, integration hell, unused software, and pressure to “simplify”… this episode flips the narrative and shows why the winners won’t have fewer tools, they’ll have better orchestration.
Transcribed and scored by The B2B Podcast Index.
Speaker A: Agency, uh, is at least as big as the Internet. It's moving faster like you know, riding a psychotic horse through a burning barn.
Speaker B: That's Scott Brinker, ex VP of Platform Ecosystem at HubSpot, editor of ChiefMartech.com and the Mind behind marketing technology landscape that's defined the industry for 14 years. Right now he's on the front lines of the next shift agentic AI MCP driven tool use and, and first mile edge enrichment where data becomes decision fuel the moment it's created. In a world where buyers show up with their own agents, Scott's here to tell us what changes, what doesn't and how to win. But what's his play?
Speaker A: 14 years of mapping those thousands of logos taught me that tech is 10%. The advantage now is we have this ability to dramatically expand the scope of things that are being.
Speaker B: In this episode you'll learn more. What are AI agents and the three kinds of agents changing marketing?
Speaker A: Right now we are starting to see agents that the marketers don't control, that it's the buyers who control these.
Speaker B: Why APIs and orchestration, not models will define the future stack.
Speaker A: Can I have like a super agent that acts as the orchestrator organizing these other agents and a network of agents. I can't think of anything in the arc of human history that even comes close to this.
Speaker B: How first mile data turns raw clicks into decision ready signals.
Speaker A: The engines themselves are effectively zero differentiation. All of the competitive advantage is entirely a function of like okay, what data do we feed into these things and how do we leverage these things in a process that is unique to our business?
Speaker B: You know, been saying that the agents now are a different type of animal and so just to have a bit of a level set, map out what you mean like how agents are fundamentally different from um, chatbots and from uh, rules based automations.
Speaker A: You ask 10 different people what they mean by agent or agentic and you might get ten slightly different answers. It's probably easiest to think of it as a continuum where on one end of the continuum you have this like very deterministic rules based automation which is what we've kind of got pretty good at. We're all pretty comfortable with that now. You know, on the other far extreme would be these uh, AI agents that, that operate with a high degree of autonomy. They can take on pretty major large scale tasks like you say, oh uh, go find me five customers and research everything about them and prepare all the campaigns, off it goes all as a single thing. Along that continuum there's a lot of different Steps, we are not at that far end yet where you just turn things over to an AI agent and it does all your marketing for you. Uh, and probably a good thing for all the marketers in the firm. Um, I think we're ways away from that. But you've got these sort of steps along the continuum where we're like, okay, well could I have an AI agent go out and do research on the web for a particular customer? And that research might happen in a very rules based workflow of saying, oh, someone came in, they filled out this form, I saw this signal from the mouseware, very deterministic things. But now I want to put a little bit of very hyper specialized agent in that workflow to say, okay, at that moment you go off and you learn and discover about this customer and that you're actually giving it a certain amount of autonomy to decide, okay, well where is it going to find that out? And when it finds things, what path does it follow to find more things? So I think of these three categories, three domains, so are three areas where we're seeing agents in marketing. The first are these agents that are helping marketers with their work. Uh, you know, the, the production of assets, you know, uh, being able to do analysis on how campaigns happened, uh, what went well, that like customer research, little mini agent we were talking about, you know, so these are all we see a lot of these tools, you know, you know, that are emerging to like help marketers accelerate the things they do. There's a second group of agents that are agents that are customer facing now the marketer, the company still controls them, you know, but they're interacting with our prospects and customers. And the most obvious example of this of course are uh, these, you know, chatbots that we've had on our websites forever to help people answer questions or resolve customer service issues. And these LLMs that they now use, you know, are really good at these conversations, conversational interactions. Uh, we're getting better at hooking these things up to the right sort of data sources behind the scenes for like knowledge bases and ticket histories and things like that. So they're actually getting pretty good. But you have other kinds of AI agents that are interacting with customers too. Um, you know, in B2B, for instance, like these AI, SDR, BDR, things that, you know, either engaging inbound or sometimes outbound emails. Um, well, we'll leave the value judgment aside for that moment. But again, these are a set of agents that marketers are deploying to interact directly with the outside, uh, world. And the third category which to me is the most interesting is we are starting to see agents that the marketers don't control, that it's the buyers who control these. And probably the best example of this would be something like these deep research, uh, functions that are available in ChatGPT or Anthropics. Claude. Uh, where I can say I am interested in evaluating, let's say I'm interested in evaluating customer service chat bar solutions for my website. It can go off and it can track down the information and who are the vendors and where have I seen other comparisons for it and what are people saying in social media or forums and organize this really nice report for me, um, that agent is acting on my behalf as the buyer. Um, but as part of it, it is interacting with the websites, you know, um, uh, other sorts of content, resources. And so this is sort of a really exciting thing for marketers that we've always been used to dealing with a little bit of a computer agent out there as an intermediary. It was Google, right? The googlebot was, you know, the one other agent that we're like, yeah, I guess we're doing this for humans, but kind of want to do it for the googlebot too. I think we're on the cusp here over the next year or so of just seeing easily a dozen of these other different kinds of agents operating on the customers, the buyer's behalf that we're going to have to interact with as
Speaker B: agents sort of proliferate. I think, you know, it feels like there's got to be some sort of center of gravity across the stack. Is that that going to live in the, in the CRM and the website and the messaging apps, or in some other layer that connects everything and makes it talk together?
Speaker A: The traditional Martech stack is not dead.
Speaker B: If you're finding value in this video, make sure to hit that subscribe button. And don't miss out on more tips coming up to help grow your agency.
Speaker A: In fact, if anything, right now in the state of AI, it's more valuable than ever for exactly the reasons you say, you know, which is, hey, it's great that we have these like AI agents or these agentic capabilities that. But they work best in two scenarios. One where we can point them at very clear, authoritative data, uh, data that they can feed into what they're doing, whether it's decision making or content personalization. Um, what you're using is your system of record for that. Um, you might not even just have one. You might have a CRM, you might have a dam, you're using for certain content assets. You see a lot of larger companies have moved to putting a lot of that, uh, both uh, customer data and company wide operational data into a cloud data warehouse and being able to use that as the source of truth that you can feed into agency workflows and things like that. But it's very important. You've got to have your systems of knowledge, your systems of truth, your systems of record that these things can work on. Data is still pretty much a mess. Um, either we still have a lot of data that's just siloed off in different places or even the data we have within particular siloed it might not be very well, uh, like maintained hygiene of it as they would say. Um, and then even in cases where you have companies that are starting to connect data across the org through like using a cloud data warehouse layer or something like that, in theory, okay, this is great. We're now sharing data across product and marketing and sales and operations. And then you realize, wait, the way in which product refers to these things is under a completely different language than how the customer service team does. And so these things, so we've got a lot of work to do. Anyone you know can sign up and get OpenAI's APIs or Anthropics or Google Gemini or whatever. Um, the engines themselves are effectively zero differentiation, uh, for any company that's using them. All of the differentiation, all of the competitive advantage is entirely a function of like okay, what data do we feed into these things and how do we leverage these things in a process that is unique to our business? And there, there's like phenomenal opportunity for differentiation and competitive advantage. But if you don't have your data in a good place where both it's good clean data and you can pipe it to the right place at the right time, you're just not going to be able to tap that power. The second thing is, you know, again we were talking about that continuum between purely rules based, deterministic everything and then wild West, I've turned it all over to the agent, I don't even have a job anymore. Um, you know, and where we're seeing a lot of the practical use cases are saying like, okay, I'm using my marketing automation platform or customer engagement platform or whatever it is that you know, I've been using to set up these structured workflows. Um, you know, maybe it's an IPASS like tool or workflow automation tool, but inside those well structured workflows and repeatable processes, I'm um, now Embedding pieces of more agentic AI to do certain tasks. Um, essentially then that workflow automation engine is becoming your orchestrator. It's keeping the pieces together. Now there's a, um, emerging capability that people talk about of like, well, wait a second, can I have a super agent that acts as the orchestrator organizing these other agents and a network of agents. And Google has that uh, a to a agent to agent protocol. That is, we may get there. Right now most of that stuff is still in basically a science fair state. So, um, not quite prime time.
Speaker B: Let me ask you about APIs. APIs are going to be super important for the future, uh, of the marketing stack.
Speaker A: Integration seems to be, uh, almost a deeply religious thing for me, uh, for all the years of maintaining that marketing technology landscape. I mean the fundamental challenge, people was like, hey, it's great, you have all these pieces of innovation happening all different ways all over the place, but to actually run a business I gotta have this stuff work together. And it doesn't work together very well. I mean AI feels like it just even raises the stakes even more that we have this ability to dramatically expand the scope of things that are being automated or run programmatically. Uh, um, but at the end of the day it's got to be able to integrate with our data sources, it's got to be able to integrate with the services we run to actually execute things like enroll someone in the subscription list or process this transaction. I am a believer that the best way to do that is through APIs or this model context protocol, uh, which is layman's terms would be. It's almost like a standard by which these AI assistants and AI agents can do an integration that is very API like. Um, I think that's, that's best because you know, I mean it's very clear what you do, what you expect. It's easy to sort of maintain. Um, you know, as those things evolve. Now there is another school of thought. Uh, there's a school of thought that, hey, actually these AI agents that run in the browser, they can just go and interact with a company or their website or their web apps through the user interface that a human would have done. And they simply simulate the process of being a human doing that. Um, you see this now with some of these, um, AI browsers, um, that are out there, like the perplexity one comet, um, uh, what was that, the OpenAI when they did that operator agent thing early in the year. These are things that basically like, no, no, no, we don't need to worry about APIs or any of that. We'll just interact with the web like a human would. I think it's really interesting in the sense that the upside of that is it does let these agents interact with things even if they don't have an API, even if they don't have a defined mcp. The downside to that is even as a human user of these things, you know how confusing it can be when you're used to using an app a particular way and then the app developer changes things in the menus. It's just like the AI, uh, agents are going to run the same. It's just not as, in my opinion, it's just not as reliable as having like, hey, listen, we're going to have well defined APIs, well defined MCP servers, uh, explicitly for those AI agents and AI assistants to use. I just think that's a more stable approach.
Speaker B: There's some agents that are really good at doing like 90 to 95% of the things that they're supposed to do. Um, but you know the saying about trust, right? It can take a long time to build trust and just a moment to break it. Sometimes that 5% that it can't do can break trust. So let me ask you what, like what are the guardrails that you think should be in place before some of these agents can do, you know, really
Speaker A: important types of tasks as human beings generally, if we're getting 90 or 95% of things right, it's actually a pretty good hit rate, you know, so, so we have a certain set of expectations and goes back to that thing. We're so used to, uh, computers and software being, you know, this rules based deterministic, it's always going to work this exact same way. You put in X, you get Y. Um, you know, so moving to this world where, okay, actually no, you put an X and you might get y 90% of the time, you might get z 5% of the time. Um, which is not used to even thinking that makes a lot of people very uncomfortable. But that being said, I think it's important to understand like, okay, well what's first of all the range of those outcomes. Like for instance, if we're talking about personalizing a message, you know, writing an email message, what does it mean to be 90% right? Or what's the case where it gets wrong? Is that question of how well the message is written? Did it pull in the right information? Was it making up to decide, hey, actually I'll give you this product for 80% off. Wait wait, wait, you're not allowed. You don't have authority to do that. Um, and so a lot of these things, to be honest, the range in which something might be, it's not that it's necessarily going to go wrong. Um, it's just that, ah, you know, 80% of these were really good. 15% were so, so. Oh, that last 5%, yeah, that wasn't very great at all. But like, you have to ask yourself like in certain contexts, like, you know, I mean, if it's summarizing a ticket history or is it trying to just personalize an email a bit. But that being said, your original question of like, okay, well, how do we put the guardrails in place? Well, I mean again this has a lot to do with uh, what is currently now called context engineering. Making sure like both the instructions that we're giving to a particular uh, AI, um, agent or task, very well defined, we control the exact data that we're feeding into it. Um, we then might have things on the other side that's sort of monitoring, you know, what was done, allowing me to go back to audit it. Um, you know, there's like a series of this whole thing around like AI observability and AI governance. It's maturing. But I think, yeah, companies need to get those systems in place ultimately before they're going to feel really comfortable scaling up, um, more and more of these agencic workflows. Yeah, I mean, uh, Ethan Moloch, uh, you know, who uh, is like probably one of the best writers of like trying to just keep up with uh, you know, what's, uh, what's the state of what's happening here in AI, you know, has referred to this as the jagged frontier. Which is, you know, the puzzling thing about so many of these AI assistants and these AI agents is they can be ridiculously good. It's something that you would think would be like very hard. And you're like, oh my goodness, that's pretty amazing. I was just using this the other night to relearn calculus, uh, to help my daughter on a calculus class and oh my God, I'm asking it to do things and it's just, it's phenomenal. Um, and then there's other things. You're like, well surely if it can do that really hard thing, then this really simple thing should be a piece of cake. And you give it to it and it totally crash the, the bed. Um, I mean this is one of the things that just makes it very difficult um, to be able to say okay, like can we, you know, is it, what is AI going to replace? What should, you know, humans do? I think for now, the more discreet the task is, you know, that. What's the metaphor people say, like, you know, treat it like an intern, a very bright but entirely inexperienced intern. Those sorts of things that you would tend to turn over to it. Yeah, in a lot of cases it is pretty good at those where I think you'd be very careful, uh, is at the level above that, you know that the interns aren't the ones actually setting the strategy. The interns aren't the ones who are actually making sure all the operational pieces fit together the right way. The interns aren't the ones who are actually evaluating to make sure this is working the way it is. You know, I think those are all things that, yeah, you need human leadership, human judgment, human insight on. And actually I think you're going to need that for quite some time.
Speaker B: How do you see orchestration working? Uh, uh, again, when the tools are spinning up their own agents, um, and you're trying to manage workflows across all of these, is it, is that being managed inside of applications like say CRMs, like Vendastas and other CRMs that are out there? Is there another orchestration layer that's, that's needed?
Speaker A: It's early. Probably the most mature right now are the existing, uh, platforms, you know, like uh, CRMs or you know, various marketing automation or engagement platforms. There's even some of these like, again like the workflow automation, uh, products, um, you know, the ipasses that they've sort of evolved to embrace, you know, AI and the agents. These are where most people are doing the orchestration because again, the way they're doing the orchestration is they're still sort of keeping the scaffolding of a very deterministic workflow. And a lot of the pieces tend to be deterministic and reliable and like this is going to work the way I expected it to work and then just inserting like, you know, very discreet oriented AI LED tasks where you could actually turn to the AI to do something that was very hard for us to do before. For instance, like the very common case of this is um, how we leverage unstructured data. You know, it was always very hard for us to like programmatically in these automations, like interpretations, you know, uh, emails or call recordings or things like that. I mean not impossible, but so difficult and expensive is to be unusable by most companies now. Boy, it's like it's a Piece of cake. You just feed that call transcript or that email into the LLM and say, hey, listen, I need to pull out. What are the next three action items you think we need to do to do that comes out with those action items and then the execution of those action items again, once again falls into that very deterministic, uh, you know, workflow process. So it's providing that orchestration. I think the question is, will that change dramatically? Like, would we get to the place where, oh, I spin up a master agent and it's coming up with all these workflows and orchestrating agents. That's right. Maybe, um, that's the sort of like truly disruptive version of what is the Martech stack? What is a company's like, tech operations going to look like? Um, we're just not there today. And uh, I don't think we're going to be there. You know, I can get in so much trouble trying to make these predictions in such a fast changing world, but I don't even think we're going to see that over the next six to 12 months. I, um, think this sort of combination of well structured workflows, but then AI capabilities sort of embedded in constrained ways within them. It's just the safest and most reliant, like the highest roi, like the risk reward ratio. That's what I'm thinking of. M. Like relatively low risk, pretty high reward. Let's get that working before we, uh, you know, leap off into space.
Speaker B: What's going to be the difference between, um, organizations that just add on AI to what they're doing versus ones that are truly native AI companies?
Speaker A: Yeah, I mean, it probably depends a lot on the business. Um, you know, if I am a restaurant, uh, if I'm a chef, um, you know, I might be leveraging AI and various things around, you know, um, whether it's my marketing or, you know, my supply chain or things like that. But you know, the core of my business is probably. I don't know, I might get myself in trouble for saying this one too, but it feels like one of those things, like, oh, you know, it's probably going to look about the same ten years from now. Uh, that looks now if I'm a software company or like a company that provides a digital service. Oh, okay. That's a whole nother thing because. Yeah, I mean, like the whole way in which, you know, the service is created and offered and how people consume it, like if they start consuming it through their own aid, I mean. Yeah, that whole world, you know, feels like it could change very rapidly. So I don't know. I think it is okay for most businesses that right now we're in the AI bolt on stage because we're still learning. You know, we're still learning. Like, how does this stuff work? What is it good at? Uh, what is it not good at? Where are the things that we're missing? Right? Like the data realization. You're like, okay, well, I'm glad I'm figuring out my data problems while this is still just an add on, you know, like, before I turn my entire operations over to it. But these are steps along a path where eventually we will become AI native to the point that even the phrase AI native probably won't be much. Just like we no longer say digital marketing. Yeah, just marketing. But yeah, we're in the horseless carriage stage right now.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.