Notas del episodio
Every B2B marketer right now is hyped about MCP servers — and Drew's first move in this conversation is to puncture that hype just enough to be useful. His core argument: an MCP server isn't the destination, it's the on-ramp. The real value only shows up once teams get past the novelty and start building something with it. He draws a sharp comparison to the early days of APIs — back then, APIs lived entirely in IT's world. MCP is different because it sits at the intersection of development and marketing, which means the average marketer is going to need to understand what it does and doesn't do, not just consume it secondhand from IT.
That leads into the bigger structural question: what happens to the marketing function itself? Drew pushes back on the idea that marketing and IT simply merge into one job. Brand people, creatives, and social/media specialists aren't going anywhere — they get enhanced by technology, not replaced by it. But marketing ops and rev ops are a different story. Drew's blunt take is that the ops people who win the next few years are the ones building, troubleshooting, and maintaining AI agents themselves — which means working directly with CISOs and CTOs, touching infrastructure like Neon databases and Ingest, and yes, having a GitHub account with a real portfolio of shipped agents. His advice to anyone in ops: start that GitHub now, before you need it.
On hiring, Drew's answer is deliberately role-dependent rather than a blanket rule. Brand hires still get evaluated on portfolio work, not code. But for ops roles, the bar is moving fast — within 6-12 months, hiring managers should expect to see a working portfolio of agents built, plus credentials (Anthropic, OpenAI, and the wave of university programs now teaching agentic AI workflows). The signal Drew's watching for: candidates are no longer coming in with a "marketing degree" as the qualifying credential — they're coming in with agentic AI training regardless of their original field.
The most substantive part of the conversation is the build-vs-buy shift. Drew's thesis: organizations now have the ability to solve micro-problems themselves with agentic workflows built on tools like Claude or ChatGPT, instead of defaulting to "is there software for this?" That's not the same as building your own CRM or trying to replicate Marketo in-house — it's about right-sizing the problem to the solution. Counterintuitively, Drew argues this is currently slowing buying cycles, not speeding them up, because teams are over-indexing on "we can probably build this" before they've felt the real cost, which never shows up in the first two months — it shows up in maintenance, integration, and evolution six months later. He predicts a wave of public "I vibe-coded my own CRM and it wrecked my business" stories on LinkedIn and Reddit before the market recalibrates and organizations find real balance between build and buy. He closes with the Jurassic Park line — teams were so preoccupied with whether they could that they never asked whether they should — as the operating principle B2B leaders need right now.