The Longer Game

The episode contains some substantive insights about AI adoption barriers in retail (committees as blockers, failure aversion, leadership challenges) and the need for human creativity alongside AI, but much of the 37 minutes is devoted to tangential philosophical discussion about entrepreneurship, failure, running, and personal development that, while coherent, doesn't directly educate B2B operators on the core topic. Valuable insights are diluted by meandering conversations.

“they don't have like key... they're probably like, there's probably an exception where there's one that's like an accelerant, but most times what I hear from brands are like, I'd love to use this, but the new AI committee has to review all AI things”

“When I first pitched Backstroke, people, like leaders on the team, they're like, don't worry, no one's job's going away... And then about six months ago, I started hearing people say, aren't gonna backfill people because we think we can do things better with AI”

The observation about AI committees functioning as unintentional blockers is useful, but most of the framing relies on familiar tropes: AI replacing jobs, the need for upskilling, failure being essential for growth, and creativity as the human differentiator. The conversation about scarcity vs. abundance mindset and drawing parallels between creative writing iteration and entrepreneurship are recycled concepts. RJ does offer specific CRM metrics tracking example, but the broader narrative lacks fresh angles.

“Everybody goes to like AI is going to ruin us all, kill us all, take all of our jobs”

“You know, it's like iteration. And, you know, that's that's the entrepreneurial journey. That's the AI thing. That's like building new tech”

RJ Talier is a legitimate operator with meaningful credentials: 10 years leading email/marketing at Exact Target/Salesforce, founded and sold Pattern89 to Shutterstock (predictive AI for social media), and currently runs Backstroke. He has boots-on-the-ground experience selling AI solutions to retailers and observing real adoption friction. However, the episode is hosted/co-hosted with Michael Maher (agency owner), making this less of a typical guest interview and more of a peer conversation, which dilutes the single-expert voice advantage.

“I got my start in digital marketing about 20 something years ago when I was an early employee at Exact Target, which got acquired by Salesforce as part of the Salesforce Marketing Cloud. So I led the email and teams for 10 years there”

“I sold that business to Shutterstock in 2021. And then I started working on Backstroke”

The episode includes some concrete details: Backstroke handles 70% of campaigns, email marketing represents 20-40% of e-comm revenue, a one-year deal cycle example, Pattern89 worked with Williams Sonoma and Facebook, and a CRM VP tracking hours saved via AI queries. However, these specifics are sparse and scattered. Most claims about AI adoption barriers, corporate inertia, and employee displacement remain anecdotal without supporting metrics, customer counts, or quantified impact data. The conversation largely operates at the conceptual level.

“email marketing is the bread and butter a lot of digital marketing strategies, making up 20 to 40 % of revenue for e-comm and retail brands”

“we can do 70 % of your campaigns, but 30 % of them are like those tent pole moments, new product introductions, letter from the CEO”

Michael Maher asks reasonable follow-ups (e.g., "Is it a scarcity versus abundance mindset?", "Do you think maybe in some cases these committees... are created an intentional blocker?") and pushes back on soft claims. However, he frequently allows the conversation to drift into personal anecdotes (his degree, running, faith, bourbon birthday gifts) that reduce focus on substance. He doesn't press RJ on specifics (e.g., how many retailers is Backstroke actually working with, what's the adoption rate post-implementation, why exactly are committees blockers vs. what should replace them). The interview becomes a philosophical chat rather than a rigorous exploration.

“So when you say that, that makes me feel like there's not an AI problem. Maybe there's a leadership problem”

“And once you have a use case and you know what you want to do for it, then fine. How do you, how do you integrate this and what's the end goal that you're looking for?”