Episode 16

full
Published on:

22nd Jan 2024

A Glimpse Into the Future of Martech - Phil Gamache

Martech continues to expand and shift at breakneck speed.

Hot startups from five years ago have become legacy incumbents. Some platforms consolidate into monolithic suites while other categories break apart into specialized point solutions. AI looms over everything, with potential to disrupt virtually every established paradigm.

Who better to guide us through this landscape than Phil Gamache, one of the humans behind the awesome Humans of Martech podcast?

Join us for a deep dive into the future of Martech and a behind-the-scenes glimpse at how Phil and Jon produce their show using the latest AI tools.

Thanks to Our Sponsor

Many thanks to the sponsor of this episode - Knak.

If you don't know them (you should), Knak is an amazing email and landing page builder that integrates directly with your marketing automation platform.

You set the brand guidelines and then give your users a building experience that’s slick, modern and beautiful. When they’re done, everything goes to your MAP at the push of a button.

What's more, it supports global teams, approval workflows, and it’s got your integrations. Click the link below to get a special offer just for my listeners.

Try Knak

About Today's Guest

Phil Gamache is on a mission to future-proof the humans behind the tech and help them have successful and happy careers in marketing. During the day, he runs all things Growth at Pelago and during the weekends you can find him behind the mic on humansofmartech.com.

https://www.linkedin.com/in/gamacp/

Key Topics

  • [00:00] - Introduction
  • [01:40] - Origin of the Humans of Martech Podcast
  • [03:42] - Importance of soft skills in becoming a martech leader
  • [04:33] - Growing an audience for the show
  • [08:00] - Importance of having a specific approach for the show. Enjoying the process of learning through being a host.
  • [11:00] - Use of AI for creating podcast imagery and transcription
  • [17:32] - What do we consider AI-generated imagery to be?
  • [20:30] - Point of view on martech and being platform agnostic
  • [25:21] - Phil’s ideal stack
  • [26:47] - Benefits of a composable CDP architecture
  • [30:17] - Definition of composability in martech
  • [34:27] - Challenges of troubleshooting a composable stack
  • [38:19] - The relative recency of the cloud-first warehouse and the transition to warehouse native tech
  • [40:22] - How much does the tech matter, in the big picture of business?
  • [42:19] - Phil’s take on the role of AI a year from now
  • [44:20] - Propensity modelling
  • [49:03] - Finding balance in life

Resource Links

Learn More

Visit the RevOps FM Substack for our weekly newsletter:

Newsletter

Transcript
Justin Norris:

You're listening to RevOps FM with Justin Norris.

2

:

Welcome to RevOps FM.

3

:

Today, I'm very excited to be speaking

with one of the humans behind the

4

:

Humans of Martek podcast, Phil Gomesh.

5

:

If you're not familiar with

it, Humans of Martek is one of

6

:

the top shows in our industry.

7

:

Phil and his co host John have

been at it for a jaw dropping

8

:

three years and Phil, I'm getting

tired just thinking about that.

9

:

And I noticed you're also just one show

away from your 100th episode milestone.

10

:

Super exciting there, too.

11

:

And one of the things that's super

special about this show, aside from the

12

:

huge diversity of guests and topics that

they have built up over a three year

13

:

span, is the incredible production value.

14

:

So each show that they do has this really

jaw dropping AI generated custom artwork.

15

:

There's a website with very rich and

detailed summaries for each show.

16

:

And you somehow managed to work a

busy full time job as director of

17

:

growth at Palago while doing it all.

18

:

So, Phil, thank you for making me feel

complete podcast inadequacy, and welcome

19

:

Phil Gamache: to the show.

20

:

Thanks so much, man.

21

:

A pleasure to be here.

22

:

Really excited to see what

you're, you're cooking up.

23

:

I know you've had a lot of

Awesome guests already so far

24

:

and some cool conversations.

25

:

So yeah, always happy to share

minds on another podcast.

26

:

Justin Norris: Appreciate that.

27

:

And seriously speaking, having, uh,

I'll be soon to publish my 10th episode.

28

:

So 1 10th of your journey and

just knowing that the effort that

29

:

goes into it, the work that goes

into doing a high quality show.

30

:

I'm amazed that you and John what

you've achieved and what you've

31

:

done over that period of time.

32

:

So serious.

33

:

Kudos to you.

34

:

I'd just love to start out maybe about

the podcast and a little bit of the

35

:

origin story and the why and what

was your journey like building it?

36

:

Yeah.

37

:

Phil Gamache: So John

and I met at Cliffolio.

38

:

He hired me there.

39

:

He was heading up growth

slash marketing at Cliffolio.

40

:

We were a Marketo shop.

41

:

So I came over from Pardot and had

to pick up Marketo and learn it.

42

:

And John and I worked together

there for close to three years.

43

:

He ended up moving to Revenue Pulse

after, but we stayed in touch.

44

:

We became close friends

while at Clipfolio.

45

:

During the pandemic, we were

chatting almost weekly on Zoom.

46

:

And one day we were just

like, why don't we hit record?

47

:

Maybe there's like parts of these

conversations that other folks

48

:

are going to find interesting.

49

:

I think a lot of people were starting

a podcast during the pandemic.

50

:

But I've always had this itch to share the

journey, like share some tips and tricks.

51

:

I've personally learned a ton

from other folks early in my

52

:

career reading and listening.

53

:

So I was just like, if I can help

a handful of people that are five

54

:

years before me in my journey,

it would be really cool to do.

55

:

MarTech at the University of

Ottawa locally here and did

56

:

it for three and a half years.

57

:

And it was awesome.

58

:

Like I still mentor a couple of students

from those classes and initially the idea

59

:

for the podcast was going to be this 101

debunking marketing automation, basically

60

:

repurposing the course after it shut down.

61

:

But it quickly morphed into ramblings and

just getting some cool folks on the show.

62

:

So we eventually settled on the journey

or the mission of how can we future

63

:

proof the folks behind all that MarTech.

64

:

I think a lot of the content

out there is tech focused.

65

:

How do we do X?

66

:

How do we do Y?

67

:

But not enough is about the

humans that are powering all

68

:

of that tech behind the scenes.

69

:

So we spent a bit of time on this

show talking about, I hate the word

70

:

soft skills, but like the people

side of, of MarTech productivity.

71

:

How do you stay sane?

72

:

How do you balance your, your

home life and your work life?

73

:

So yeah, that's kind of the genesis of the

74

:

Justin Norris: show.

75

:

And it's funny that you say, and

I know jokingly about soft skills,

76

:

but I think a recurring theme in the

discussions that I've had is those

77

:

are really the difference between the

practitioner and the leader, like the

78

:

technical skills get you to a certain

degree, but at a certain point, you

79

:

need those communication skills.

80

:

You need the ability to prioritize.

81

:

You need the ability to strategize to

get to that next level in your career.

82

:

Similar experience.

83

:

On your side,

84

:

Phil Gamache: definitely.

85

:

I think that platform skills

will take you a certain way.

86

:

And if you want to be icy for the rest

of your career, even then there's still

87

:

a lot of collaboration road mapping.

88

:

You still need to work with

a bunch of other folks.

89

:

So yeah, there's there's a lot

of people skills involved in.

90

:

I think a lot of roles, uh, but I

think marketing ops, uh, martech

91

:

specifically, you're at the intersection

of a bunch of different teams.

92

:

Uh, so definitely agree

93

:

Justin Norris: in terms of

building up your audience.

94

:

I mean, I'm obviously at a much

earlier phase of that process than

95

:

you, but I saw on your website,

so, you know, 18, 000 listeners.

96

:

Uh, it's a very well known show.

97

:

Does it feel like you get to a certain

place of like self sustaining growth or

98

:

is it always kind of like any business?

99

:

We're always trying to do new

things to get to that next level of

100

:

Listenership and audience building.

101

:

Yeah,

102

:

Phil Gamache: there were

growing pains for sure.

103

:

I mean John joked I like in the early

days even like maybe the first full year

104

:

of doing the show like we it almost felt

Like we were screaming into the void like

105

:

there wasn't A lot of listeners and like I

think the advantage you have is that like

106

:

you've gone the route of publicly sharing

stuff like read a lot of your LinkedIn

107

:

posts and have been a fan before I heard

that you were doing a podcast, right?

108

:

Like John and I didn't

necessarily have that benefit.

109

:

We didn't have an audience already.

110

:

We didn't have following

folks didn't know who we were.

111

:

So we were starting from scratch

and year one was almost like

112

:

just having our friends on the

podcast like friends in Martech.

113

:

And just getting like interesting stories

and stuff and trying to figure out like

114

:

what what was like our unique perspective

on things and I honestly like wanted

115

:

to be attached to John Taylor's name

like he's still a mentor today and like

116

:

I think he his brain works differently

than a lot of folks in Martech like he's

117

:

almost a web dev now like he's picked up

JavaScript and so It's been really fun

118

:

to see how the growth of listenership has

evolved, and it was really rough at the

119

:

start, like I won't joke, and there were

definitely times in like the first year

120

:

where we were just like what are we doing,

like there's a ton of time that gets

121

:

involved in this, like it's really what

we want to be doing with our spare time,

122

:

but it honestly just came down to you.

123

:

We were having fun doing it and we told

ourselves that the day that we weren't

124

:

having fun anymore, we were going to stop

doing it and we never really did it to

125

:

like become like a top podcast and have

like hundreds of thousands of of listeners

126

:

like there was never really the goal like

the goal is really just like sharing stuff

127

:

and helping a couple of folks in in Ottawa

and like our initial little area and when

128

:

it really kind of picked up steam was So I

think there's been like consistent growth,

129

:

like year over year, never like dramatic

growth like we did this summer, actually.

130

:

So this summer I, uh, had a baby,

so I was on pat leave for a full

131

:

month, month and a half or whatever.

132

:

And in between diaper changes and

during naps, it's sometimes like

133

:

her just like sleeping on me.

134

:

I would just like geek out on the podcast.

135

:

And this was right around the time

where like ChatGPT and a lot of AI

136

:

applications were, were picking up steam.

137

:

And I went super deep on the

topic and we did like a four

138

:

part series on AI for marketing.

139

:

And that's when like folks

really started picking it up.

140

:

Like it was, it was such a hot topic

and everyone was talking about it,

141

:

but I feel like the cover art helped

us like carve a unique interest and

142

:

yeah, it kind of picked up from there.

143

:

We started getting a lot of inbound

requests from guests to be on the

144

:

show, be interviewed, talk about AI.

145

:

And, uh, yeah, this year we

had Scott Brinker on the show,

146

:

which definitely helped, uh,

catapult our, our listenership.

147

:

We went really deep on, like, niche

topics, like composable CDP, warehouse

148

:

native tech, uh, email deliverability.

149

:

And so, yeah, it's been a fun

ride, and it's a journey for sure.

150

:

There's growing pains at the

151

:

Justin Norris: start.

152

:

I've noticed that you guys go deep.

153

:

And I think you really need to have a

unique way of doing things, you know,

154

:

for people to start to feel that trust

and that relationship with your show

155

:

and what you do doesn't have to be deep.

156

:

It could be short.

157

:

It could be topical, but.

158

:

I think going deep is a really useful

thing because in people, I was reviewing,

159

:

I'd published a post on the whole

Google Yahoo changes spam complaint

160

:

thing and in my research came across

your episode, you know, it was very

161

:

much the way I also personally think

like you just broke everything down

162

:

very exhaustively, you took it apart,

you put it back together again, and I

163

:

think that's really helpful for people

because not everybody has the time or the

164

:

inclination to do that sort of work when

you feel that someone else has done it.

165

:

And you're like, well, I

can trust these people.

166

:

They're a trusted resource.

167

:

I think it's a great angle and

you're doing it effectively.

168

:

And I also, you know what

you said about having fun.

169

:

I've had a few people ask me since I

started doing this, Hey, do you think I

170

:

should start a podcast or what's involved?

171

:

I was like, do not do that.

172

:

But I think unless you are the type of

person that just actually enjoys the

173

:

process inherently, like if you think

you're going to start it for fame and

174

:

fortune and riches, like not that, but

if you enjoy having conversations and

175

:

learning, like I do think sometimes,

even if nobody else saw them and they

176

:

never saw the light of day, it would

be a very valuable thing for me to be

177

:

doing just for my own personal growth.

178

:

You have to be someone that feels that.

179

:

Phil Gamache: Totally agree.

180

:

Selfishly, a lot of our topics are

things that I'm pondering myself

181

:

at my day job, like the whole

composable CDP deep dive that we did.

182

:

Like we were evaluating

whether to go package CDP or

183

:

composable at my current startup.

184

:

We were debating whether we rethink

our email deliverability strategy.

185

:

So a lot of like the themes

that you see on the podcast are.

186

:

Are self serving like I, I learned from

industry experts and I apply those,

187

:

those learnings to, to my day job.

188

:

So that's like part of the, the joy there,

but I think the, also the other part

189

:

that a lot of folks don't realize until

they get into it is like, this is how

190

:

it's all that happens behind the scenes

on, on the production side of things.

191

:

And I've picked up most of the slack

there from John, but I actually

192

:

think I enjoy most of it because.

193

:

Early in my career before I

wanted to go into MarTech, like I

194

:

was, I was big on graphic design

and just like media production.

195

:

My dad's a photographer and video editor.

196

:

So like I was working on Max and

GarageBand and iMovie when I was

197

:

a kid, like one day I wanted to be

like a cinematographer, you know?

198

:

So the idea of working in editing

audio and figuring out how to like

199

:

create visual imagery for, for the

show, even before we went into AI

200

:

and mid journey, we're Drawing images

and illustrations for each guest.

201

:

So I enjoyed that part of it.

202

:

That part of it like gave me energy

as opposed to a lot of folks are just

203

:

like, I want to chat with people.

204

:

I don't want to like worry

about all that stuff.

205

:

And there's school media

production agencies that that'll

206

:

do that side of it for you.

207

:

I enjoy doing both and that's

part of the joy for sure.

208

:

Justin Norris: There's a real sense

of craft and I think you have to

209

:

almost see yourself as a maker.

210

:

I mean, you are a maker when you

do a show, but it's different than

211

:

just like, we're a business and

we're going to do a podcast and

212

:

what's the ROI and it's what you do.

213

:

So I want to go to the

imagery and the use of AI.

214

:

You've really practiced what you

preach in the sense of incorporating

215

:

technology into the fabric of the

show, which makes a lot of sense.

216

:

I'm vaguely aware of all of

these tools and capabilities was

217

:

certainly not expert in them.

218

:

So I'd love for you to just educate

me and listeners on what your process

219

:

is and how you, how you create all of

220

:

Phil Gamache: this.

221

:

Yeah, we already recorded a pretty deep

episode on, on the whole process and we

222

:

were going to put this live, but we ended

up delaying that one until next 101.

223

:

In favor of like all the Google changes,

too many people are talking about this.

224

:

We're like, ah, wait, let's jump on this.

225

:

Let's let's chat about this.

226

:

But the short version of it

is we started using GPT to

227

:

basically uplevel our transcripts.

228

:

Like, I think a lot of folks for podcasts

will just like copy paste the transcripts

229

:

on, on a landing page and call it done.

230

:

Um, and like, I think

transcription tools have evolved

231

:

a lot and gotten a lot better.

232

:

They're still filled with likes

and ums and half the time,

233

:

like they're hallucinating and

it doesn't really make sense.

234

:

I don't think ChadGBT is really good

at writing and coming up with like, uh,

235

:

authentic content and brand new content,

but ChadGBT is really good at taking

236

:

a raw audio transcript and turning it

into something legible or interesting.

237

:

So I've got a couple of prompts that have

evolved over time, but I'm essentially

238

:

taking the transcript from otter.

239

:

ai, we use that tool for transcripts.

240

:

And I'm basically taking the question

and the answer from the guest and I

241

:

asked ChiGBD to turn it into a blog

post passage and it's actually really

242

:

interesting what it comes up with.

243

:

Sometimes it, it gets a bit confused

when we're talking about CDP or GBT,

244

:

it doesn't always get the acronyms

correctly on the transcription.

245

:

So there's a couple of things in

there that I tweaked the prompt for.

246

:

I always like reread the prompt.

247

:

Sometimes it's not perfect.

248

:

Sometimes the logic is kind of

missed, but oftentimes the output is

249

:

way greater than the raw transcript

that someone would end up reading.

250

:

And so we ended up having this

like long form, like 3, word blog

251

:

post for each of our episodes.

252

:

And we're like, how do we augment this?

253

:

And, uh, around the time I was on pat

leave, I just started playing around

254

:

with mid journey, got a paid account and

was just like playing around with it.

255

:

And I was like, man, it would

be cool to, to make our cover

256

:

art, uh, for mid journey.

257

:

But then I was thinking like, what if

every question that we have, which is

258

:

essentially an H two on our landing page,

what if we have like an accompanying

259

:

image, uh, to, to support that, and

then we can use that for social shares.

260

:

Instead of just sharing the one full

episode, we can share specific pieces of

261

:

questions and takeaways from the show.

262

:

So it's, it's evolved into like

using GPT in mid journey now.

263

:

And we always leverage GPT to come up

with an H2 for that blog post passage

264

:

and summarize a practical key takeaway

for the audience at the end as well.

265

:

But yeah, it's definitely evolved a lot

over time and it's funny, we joke that

266

:

like, we hear a lot of folks on social

that discover us and a lot of the comments

267

:

that we get when we share our episodes are

not like, wow, the content's amazing, and

268

:

I learned so much, most of the comments

are just like, this cover art is badass,

269

:

like, wow, this image is awesome, but

270

:

Justin Norris: we'll take it.

271

:

The imagery is awesome.

272

:

I haven't gone deep into Midjourney,

but I've played around with a few AI

273

:

image generating tools, and some of

them have been pretty underwhelming.

274

:

Some of them are pretty cool.

275

:

Just the other day, actually, I was able

to successfully use one and get an image.

276

:

I'm like, okay, actually, I'll use

this as a feature image on a blog

277

:

post because it's pretty good.

278

:

You have obviously learned the

prompt engineering expertise to be

279

:

able to get exactly what you want.

280

:

How do you get somebody and like very

specific things that are unique to their

281

:

personality and incorporating it in this

futuristic landscape and all that sort

282

:

Phil Gamache: of stuff?

283

:

The secret to making the illustrations

actually look like our guests comes

284

:

from a secondary bot that we connect to

Discord, which we use for mid journey.

285

:

So it's called Insight face swap.ai.

286

:

And uh, I can share you, uh, links

to that, so to put in the show notes.

287

:

But essentially it's saving

features of the face of our guests.

288

:

So I have it in a private server on

Discord, and I'll upload a bunch of images

289

:

of the guests that I'm having on the show.

290

:

And then I use that bot to save one

of those images, like front facing,

291

:

nice, clear, no glasses, good quality.

292

:

And then the bot remembers

features of that face.

293

:

And then I'm using a bunch of different

prompts to come up with an illustration.

294

:

Usually, like, it's the prompt

style is flat illustration.

295

:

This is something I tell a lot of folks

that are getting started in Midjourney,

296

:

is that, like, you can learn a ton about

how to do prompts from their guides.

297

:

There's a bunch of YouTubers and creators

that have been using Midjourney for

298

:

several years now that are like light

years ahead of me and I've learned a

299

:

ton from them as well, but like pick a

style, there's so many different styles

300

:

that you can use in Midjourney and that's

like The difference between Mid Journey

301

:

and some of the other image generators

is that, like, once you pick a style, you

302

:

can actually get pretty consistent type

of colors, type of flat illustration, or

303

:

if you want to go, like, geometric, or

if you want to, like, do cubism, or you

304

:

can do, like, real life photography also.

305

:

So, like, pick a style, like Discover,

you can see a bunch of other people

306

:

publicly using Mid Journey and

get a taste of, like, what the

307

:

prompt was and what the output was.

308

:

But the secret sauce to making the

guest cover art actually look like

309

:

our guest is that we'll basically do

a bunch of prompts to get some flat

310

:

illustrations that look kind of okay.

311

:

Never really look like our guests,

sometimes they're like, we get

312

:

lucky, and it looks pretty similar

to our guests, and they'll be cool

313

:

with us just running with that one.

314

:

But, most of the time, we're just

like, right clicking on the output,

315

:

and then we select the inside face

swap bot, and it applies the guest's

316

:

real face on top of the illustration.

317

:

We're applying like a real photo on top

of an illustration, so the output isn't

318

:

always like, perfect, sometimes it just

breaks the flat illustration style.

319

:

So there's like a bunch of like

test and learn, uh, which is part

320

:

of the fun and the addictive nature

of using these image generators.

321

:

But yeah, ultimately we always

end up on one that looks kind

322

:

of okay and we run with it.

323

:

Justin Norris: What is your

perspective on what this process is?

324

:

Is it a new type of graphic design,

whereas instead of using point

325

:

and click inside of Photoshop?

326

:

You're just interacting with

a different set of tools.

327

:

Is it replacing the work

of the creator to a degree?

328

:

What is your point of view

329

:

Phil Gamache: on that?

330

:

I think for now it's not replacing the

designer, especially not the illustrator.

331

:

It can do concept art way faster than

those illustrators and those designers.

332

:

But it still can't, like, create

something that's specific to a brand.

333

:

Like, a lot of these designers

and illustrators have a set brand

334

:

guidelines that they're following.

335

:

And you can instruct Midjourney

to use specific colors and

336

:

themes, but at the end of the day,

it's never going to be perfect.

337

:

It's never going to be as on brand as an

actual designer and illustrator that's

338

:

creating, like, Retargeting ad banners

like that's always like, at least for

339

:

now, going to be better in the future.

340

:

Maybe there's a way to like upload

your brand guidelines or like a

341

:

specific format within the tool

itself to change those settings.

342

:

That could be game changing if they're

working on that, but I think for now,

343

:

uh, there's still a lot of upside to

using an illustrator and a designer.

344

:

If you've got a big company and you've

got like a media production within it.

345

:

But yeah, the other thing I'll say is

that Midjourney is still not perfect.

346

:

They've gotten better at hands and, uh,

you still can't do words in letters.

347

:

Uh, ChadGBT and Dolly have

started playing around with that,

348

:

but it's still not perfect yet.

349

:

Like if you say like upload

something that says humans of

350

:

Martech on it, it's going to be

misspelled like nine out of 10 times.

351

:

So like the words are still not

really great with image generators.

352

:

That's where like word art artists

and graphic designers are still like

353

:

a level up on top of, of these tools.

354

:

And even if you have like

something super specific to do,

355

:

like I'll give you an example.

356

:

I was trying to come up with an image,

you know, those traditional like

357

:

iceberg images where you see like

the tip of the iceberg, but under the

358

:

water is like the meat of the iceberg.

359

:

And so I was trying to

convey that with a concept.

360

:

I forget what it was, but like.

361

:

Mid journey wasn't able to do it.

362

:

Like I couldn't come up with

a prompt that outputted that

363

:

similar type of iceberg image.

364

:

Sometimes you can even like upload, uh,

an image of something that you want,

365

:

and then you can just like tweak the

prompt on it, reference that image.

366

:

But it, like I couldn't do it,

couldn't do it with mid journey.

367

:

Like the time it took me to

like figure out how to do it.

368

:

The designer would have have

been done already with that.

369

:

So it's still not replacing folks,

but I think at some point you got

370

:

to think that it will interesting.

371

:

Justin Norris: Those strange limitations.

372

:

I saw another one the other day where

it was like it had misspelled linked in.

373

:

It's like you've got, you know, a

quadrillion billion petabytes of data

374

:

and you can't spell linked like It's so

strange that it has such a capability

375

:

and yet limited in those specific ways.

376

:

Maybe we turn to Martech generally.

377

:

You mentioned a number of the different

technologies that you've used.

378

:

Apartheid Shop, then you

moved over to Marketo.

379

:

And you've gone through a

number of other platforms.

380

:

What's been your point

of view on that journey?

381

:

A lot of people tie their career to

one platform and kind of plant their

382

:

flag there and make that their brand.

383

:

And you've taken a different path.

384

:

How do you

385

:

Phil Gamache: feel about that?

386

:

Yeah, I'm definitely biased on

that point just because it is

387

:

the path that I stumbled into.

388

:

So I started off with Pardot in a

Salesforce shop, so I was really

389

:

deep in Pardot for like four

years and became a craft and I

390

:

definitely wanted to stick to it.

391

:

I saw the value of it and I went to like

all the conferences and I saw all these

392

:

like experts that were specific Pardot.

393

:

Specialists, right?

394

:

And I was like, I could do that.

395

:

Like I could become a part hot

specialist and I don't think there's

396

:

anything wrong with going that route.

397

:

I ended up going the route of trying

a different tool just because I

398

:

wanted to join a different company.

399

:

Clipfolio in Ottawa was like one of the

hottest startups and uh, still kicking

400

:

around and doing good stuff today.

401

:

And they just happened to be

using a different tech stack.

402

:

So it wasn't a matter of, I want to find

another cool company that's using Pardot.

403

:

It was, it was time for me to like

leave the company that I was at and try

404

:

something new, like look for something

greater, bigger problems to solve.

405

:

And they happened to be using Marketo.

406

:

And then when I moved over from Clipfolio

to close, they were using customer IO and.

407

:

So on and so forth, like now I'm using

iterable and I've used a bunch of these

408

:

different tools and I like to give this

idea that there is a lot of importance

409

:

being platform agnostic in Martech because

I am a big fan of strategy over platform.

410

:

Maybe like later on in your career

too, like I think initially when

411

:

you're an IC or a specialist.

412

:

And you're at a company, like, I

think there's nothing wrong with being

413

:

an expert in the platform itself.

414

:

But as you like grow up in different

levels in martech or in marketing

415

:

ops, you get involved in a lot

more strategy and budget planning.

416

:

And at the end of the day, like

all these automation tools,

417

:

they're relational databases.

418

:

They all have list building

and segmentation capabilities.

419

:

They're all rule based automation

workflow builders, right?

420

:

If this, then that, yeah, if

this, then that and or statements,

421

:

they're all so similar, right?

422

:

So I give that advice because I would

rather chase cool companies in my career,

423

:

then limit myself to the companies

I could work at because they use a

424

:

specific platform or a specific tool.

425

:

Like, I don't want to limit

myself to a certain stack.

426

:

At the end of the day, there's like

11, 000 martech tools out there, right?

427

:

It's impossible to be

a pro in all of them.

428

:

And the last point I think on that is

like, legacy platforms are slow to change.

429

:

Pardot hadn't changed in like X

years after I stopped using it.

430

:

Like Marketo is still using the same UI.

431

:

It's always used.

432

:

Let's not talk about that.

433

:

It's too painful.

434

:

It's not a dichotomy, right?

435

:

It's not like one or the other.

436

:

I think folks can make a beautiful

career being a Marketo or an

437

:

iterable or a HubSpot consultant.

438

:

I think that folks that go the

strategist way, the platform agnostic

439

:

ways, is also valuable as well.

440

:

Justin Norris: I agree with you.

441

:

I had a almost diametrically

opposed career in that I

442

:

went deep into one platform.

443

:

I spent seven years at a, uh, at a

consulting shop that was deeply embedded

444

:

in the Marketo and then the Adobe

ecosystem, but I think what you see is

445

:

that, yes, the technology is, is big

and it's complicated and they will need

446

:

specialists, but unless you really plan

to just hitch your wagon to that one

447

:

horse and hope That is going to keep

going for 20 years at a certain point.

448

:

You'll probably have to pivot.

449

:

You can see it already.

450

:

I love Marketo.

451

:

I think it's still a marketing

automation platform of choice.

452

:

I'd probably buy it again if I

was building a stack from scratch

453

:

today, but it doesn't have the place

that it once had in the ecosystem.

454

:

Like you said, it's been

acquired its legacy.

455

:

It's slow to change.

456

:

They still can't get the U.

457

:

I.

458

:

Together products.

459

:

They ossify and fossilize once they

get ingested by the maw of one of

460

:

these big companies and then they just

kind of stagnate and younger dynamic

461

:

companies come in and overtake them.

462

:

And so is that something you

really want to worry about?

463

:

Um, and then I also think ultimately,

if you aspire to some sort of in house

464

:

leadership, it's, you're not going to

go to a C level meeting and there'll

465

:

be like, we need your technical skills.

466

:

You know, they want someone who knows

those technical skills and it can be.

467

:

A strategic operations leader and

think about business focus problems.

468

:

So I think the path that you took makes

sense and I think it more and more makes

469

:

sense as the tech skills become not

unimportant, but more commoditized, more

470

:

easy to, to replicate or to offshore or,

you know, to do different things with.

471

:

I'm curious given all that though, let's

say you were starting a new company today.

472

:

What would your stack be?

473

:

Where have you landed as like the

best of breed for the modern era?

474

:

Yeah, it's

475

:

Phil Gamache: interesting that you say

Marquetta would still be your choice if I

476

:

was starting from scratch And it would be

a startup at first like I think you know

477

:

maybe one day when we become a big team

like we look at like the The bigger tools

478

:

in the space, but I think there's too

many less expensive tools and tools with

479

:

a smaller learning curve to get started.

480

:

So like, I think automation for me,

like my two favorite platforms are

481

:

iterable and customer IO slightly biased.

482

:

Cause they are the last two tools

that I've used and, and kind of like

483

:

dove in and really expanded on, on

the capabilities and the beautiful UI

484

:

and building like visual builders and

visual journeys and stuff like that.

485

:

I think that they lean a bit more on the

B2C side of things, specifically iterable.

486

:

My current company is B2B2C.

487

:

It's a super weird business model,

but we're on the B2C side of things.

488

:

We market to consumers and eligible

employees for the Pelago Health Benefit.

489

:

And so iterable is, is well versed

for, for that use case itself, the size

490

:

of database that we have in iterable,

like it would cost us an arm and a leg

491

:

to house that in, in a Marketo or any

of these other bigger ones, but I'm

492

:

a big fan of the modern data stack.

493

:

Like I know we, I said, we went

super deep on the composable CDP

494

:

architecture and I'm a big fan of it now.

495

:

I've completely converted, uh, at

previous companies, I was a big fan

496

:

of segment in, in the packaged CDP.

497

:

I've even used MParticle as well for a

few consulting gigs, but I've, I've opened

498

:

up to the composable CDP now and we can

get into some of the benefits there.

499

:

But like, I, I just think

that like the data warehouse.

500

:

Is the source of truth today.

501

:

And for marketers, it used to

be the CRM and then it used to

502

:

be the automation tool, and then

it used to be the package CDP.

503

:

And in all of those instances, we're

essentially making a copy of our user

504

:

database and we're bothering our data

team or engineering team to cause,

505

:

you know, like none of those CDPs off

the shelf are like, you don't need

506

:

a developer, even though they all

claim that you don't need a developer.

507

:

At the end of the day, like I think

the data warehouse, You always

508

:

Justin Norris: need a developer.

509

:

You

510

:

Phil Gamache: always need it, yeah.

511

:

Especially for data warehousing,

and I think that like most of these

512

:

companies, startups, especially in tech,

like the data warehouse is a central

513

:

piece of the stack today, and they're

making all of this work, building

514

:

all the pipelines to like ingest the

data from all your different tools.

515

:

They're structuring it in the warehouse,

and then we're using reverse CTL

516

:

tools that push that into other tools.

517

:

A CDP, a packaged CDP, is essentially

copying all the work your data team

518

:

did in the warehouse, and you're paying

for a whole other copy of that data,

519

:

just like you are in Marketo already,

or in Iterable, like the, it's not

520

:

warehouse native yet, I think at some

point a lot of these tools will become.

521

:

But so yeah, I think that like, you

know, whether it's snowflake or big

522

:

query or redshift, it's become an

essential part of the stack for Martek.

523

:

Not that Martek folks are really

Engineering the data warehouse, but they

524

:

are architecting a lot of the tools that

they pick based around the idea that the

525

:

warehouse is the central point of truth.

526

:

And then we would use like snowplow

rudder stack to do that event collection,

527

:

replace GA for like, don't have to worry

about all of those limitations there.

528

:

And then you use a reverse detail

tool like census to push the data

529

:

that you have in your warehouse to all

the tools that you use in marketing.

530

:

So your ad platforms, your iterables,

your CRM, so that you don't have

531

:

to worry about, like, is my CDP,

the data in my CDP, is it matching

532

:

with what I have in the warehouse?

533

:

Is it match what I have in the CRM?

534

:

All of these tools have the

warehouse as the central point.

535

:

Of failure were positive there, but

yeah, so those are the core of what I

536

:

think would be part of it from scratch.

537

:

There's a bunch of other ones too.

538

:

Like I'm still a big fan of Zapier.

539

:

I love the world of async and having like

internal wikis for like documentation,

540

:

big fan of notion and using loom.

541

:

All these like white boarding tools

like, uh, we use Figma and, and Fig Jam

542

:

at, at work for just workflow processes,

asynchronous design thinking sessions,

543

:

experimentation, C-M-S-C-R-M, I don't

have too many hot takes on those.

544

:

There's a lot of options in that space.

545

:

Obviously I spend a bit

of time at WordPress.

546

:

I have a, a bit of a bias for that

as, as the CMS, but yeah, there's

547

:

still a ton of options, right?

548

:

Justin Norris: We certainly

have no shortage of options.

549

:

Nobody's ever complained that we

don't have enough MarTech yet.

550

:

As the Scott Brinker landscape

map becomes, like, approaching

551

:

infinity in its size.

552

:

Let's, I want to turn to this concept

of composability and maybe You've

553

:

obviously thought deeply about it.

554

:

For those for whom it might be

a newer concept, can we just

555

:

build it from the ground up?

556

:

Clearly it sounds like what we're

talking about is taking different

557

:

components and putting them together

to create something that maybe you

558

:

would have to buy off the shelf as a

single unit of functionality otherwise.

559

:

Yeah,

560

:

Phil Gamache: I think the easiest way

to think about it is point solutions

561

:

versus an all in one platform.

562

:

Composable for me is like this idea of

best of breed components that some of

563

:

them are purchased, some of them are

created in house, whether you're data

564

:

engineers or building your reverse ETL

pipeline in house, or the ETL pipeline,

565

:

like the best of breed idea, whether

it's purchased or created in house.

566

:

It just means all of these components are

integrated together, and maybe they're

567

:

different pieces, but you're not locked

into one vendor on like a two year, three

568

:

year contract, and you're being billed

by a number of people in the database.

569

:

There's this idea that flexibility is

currency in today's smart tech landscape.

570

:

I think Arun, the founder of Castle.

571

:

io said this on our podcast,

it like it stuck with me.

572

:

Flexibility is currency.

573

:

And so opting for a composable stack

or like a composable CDP or even like

574

:

unbundling pieces of your Martech

over this idea of like an all in one

575

:

tool, it can provide you this like

elbow room to innovate and adapt.

576

:

Faster than if you were

locked into one vendor.

577

:

One of the examples there would be

the advancements of AI right now.

578

:

Like if you're locked into one platform

that doesn't have AI features yet.

579

:

What are you doing?

580

:

Like you want to play

with those AI features?

581

:

Like, are you waiting two

or three years for that?

582

:

Like big legacy platform to

finally come out with AI features?

583

:

Or are you trying some of these new

startups, these new point solutions that.

584

:

Have this capability already that can

actually hook up to your data warehouse.

585

:

That's the idea of the composable stack.

586

:

It's a way more flexible.

587

:

There's options for a bit more.

588

:

Innovation is in some cases it is cheaper.

589

:

In some cases you have to factor in

like the troubleshooting when you

590

:

have like seven tools instead of one.

591

:

And something breaks like the

troubleshooting piece, like it

592

:

comes into becoming a bit trickier.

593

:

Like you have to figure out

which one is breaking there.

594

:

Sometimes it isn't cheaper, but

sometimes folks will pay for it

595

:

just for the added flexibility.

596

:

But this idea of not being locked

in to one platform and you can't

597

:

try any other features until that

one platform comes up with it.

598

:

And maybe they were purchased by a

large enterprise and they're still

599

:

integrating it with the bigger company.

600

:

AI features by the time they

come out, there's going to

601

:

be like way more advancements

already and like point solutions.

602

:

So that's, that's the idea behind it.

603

:

Like best of breed components that

all work together, but it does

604

:

Justin Norris: feel like best of

breed being taken down to another

605

:

higher level of resolution because

time was where best of breed meant.

606

:

I'm going to use Marketo

and Salesforce instead of.

607

:

Pardot and Salesforce, you know,

like kind of like VHS Betamax Wars of

608

:

Best of Breed versus like buying the

Super Stack from one company was, you

609

:

know, I'm not not going to just buy

everything from Salesforce or everything

610

:

from SAP or everything from Adobe or

whatever I'm going to pick and choose.

611

:

And now it's you're even

taking some of those things and

612

:

breaking them down even further.

613

:

It feels like where Yeah, you have a

warehouse instead of just having Marketo.

614

:

Maybe you have one tool

for your workflow building.

615

:

Another tool is, uh, ingesting

activity data like digital clickstream

616

:

data, like you referred to snowplow.

617

:

And I find that inherently appealing

because like for all the reasons that

618

:

you mentioned, the one area where I think

A single vendor sometimes makes sense

619

:

is HubSpot, if you're smaller, helping

a friend with a business project and he

620

:

was on HubSpot and I was just amazed,

they've got kind of everything at 80%.

621

:

And if you're a small company just

getting started, that maybe that's

622

:

kind of like good enough for you.

623

:

I don't need Chili Piper, I have

Calendar Building and I don't

624

:

need Sales Loft because I have my

sequencing and I don't need Marketo.

625

:

It's just all right there.

626

:

But I think once you're past a certain

size, you want Like you said, I don't

627

:

want to wait for features, I want

to have the best of everything, and

628

:

I want them to play well together.

629

:

The flip side to that, then, though,

if I think about it is what you alluded

630

:

to with the troubleshooting point.

631

:

And I've even found we have a

great data team, but it's hard

632

:

working with a data warehouse.

633

:

There's discrepancies.

634

:

There's why is this opportunity in sales?

635

:

As soon as you have more than one of a

thing, then all of a sudden you're Like

636

:

you said, bringing worlds together.

637

:

And is your experience that this

is achievable in a smaller org or

638

:

does it require big teams or is

there inherent overhead and like

639

:

friction and cognitive load that

comes with breaking things up in this

640

:

Phil Gamache: way?

641

:

Definitely I think like on a

troubleshooting perspective on

642

:

like a QA perspective, making sure

that data is matching up in all

643

:

these tools because you're still

loading that data differently.

644

:

You're converting that data in

different format based on like

645

:

the two of the endpoint solutions

that you're sending it to.

646

:

Um, so yeah, maybe, maybe it's

not one of the first things

647

:

you do as a, as a startup.

648

:

And I think even like a couple of years

ago, this idea of like having a data team

649

:

at inception of a startup was, was crazy.

650

:

But I think today it's,

it's almost a necessity.

651

:

And, um, I've worked for startups

where there wasn't a data team, right?

652

:

Like there was maybe an analyst or

two, but like when it came to getting

653

:

data in your automation tool, It was

up to the marketer to figure that out.

654

:

Or if there was too technical stuff,

you had to bother one of the engineers

655

:

who was working on product stuff to

like stop working on customer facing

656

:

product things, help the marketing team

on JavaScript and like cookies and stuff

657

:

like that on on the front end side.

658

:

Today, I think a lot of startups

from day one will have at

659

:

least a person owning data.

660

:

And they're working on source of truth

and maybe some customer facing stuff,

661

:

but at the end of the day, their,

their role is like stitching together

662

:

different teams and making sure that

teams are getting the data they need.

663

:

They're coming up with analysis

like eventually they want to.

664

:

You know, go to funding and,

and, and get extra stuff.

665

:

So like all the fundraisers right now are

asking like, what are you doing with AI?

666

:

And part of the key there

is having a ton of data.

667

:

You can't do anything useful

with AI if you don't have like

668

:

a raw database already started.

669

:

That's, you know, structured

or someone thought about that

670

:

from day one from inception.

671

:

So that's like the need or the,

the exception or the expectation

672

:

of having a data team from day one.

673

:

And so does it make sense to have like

a warehouse, you know, in the first

674

:

couple of days and you're using HubSpot,

like maybe not, but I think at some

675

:

point, if, especially if you have a

data person on the team, like it's a

676

:

matter of figuring out how does the

marketer work with the data person?

677

:

What are the limitations?

678

:

What's going to be the hiring roadmap?

679

:

Are we going to invest

more in that data team?

680

:

And we're going to have

capabilities to figure.

681

:

All those QA issues out and, um, the cost

differences versus like building a package

682

:

CDP, like an MParticle or a segment, like

those discussions and all need to happen

683

:

with like a, the data team and our tech

team, because at the end of the day, like

684

:

when you're just getting started, I don't

think there's anything wrong with like

685

:

doing the HubSpot route, like on top of

all the things you said they do, like they

686

:

also do a CMS, you can have your blog and

HubSpot, they do all the forms for you.

687

:

But at some point you'll

need to make that decision.

688

:

Like, are we still going

to stick to HubSpot?

689

:

Do we want like more best of breed tools?

690

:

And then the whole migration

discussion needs to happen.

691

:

And maybe you kick that down the

road because you don't want to

692

:

take on that migration project.

693

:

And if you've got everything invested in

HubSpot, like you've got like three years

694

:

of SEO data in the HubSpot CMS tool, like

how excited are you about moving that

695

:

over to Ghost or, or, uh, or WordPress?

696

:

Like, That's a big migration

project in and of itself, and I'm

697

:

speaking from experience there.

698

:

Justin Norris: Yeah, those growing

panes are extremely expensive.

699

:

And it's easy to forget, I don't

know, seven, eight years ago, it was

700

:

kind of revolutionary to have a cloud

first warehouse and that wasn't,

701

:

you know, necessarily managed by IT.

702

:

I remember him being consulting,

thinking about like, I want to come

703

:

up with like a totally cloud based

BI solution, cloud based warehouse,

704

:

cloud based ETL, cloud based BI.

705

:

I mean, today that would be

an entirely mundane concept.

706

:

It's like, yeah, like, of course,

but at that time it was a big lift.

707

:

It was different.

708

:

And I think I mean, that's why Snowflake

is a quadrillion dollar company that it

709

:

is because everyone is using it now, but

it's easy to forget, I guess, that that

710

:

was not commonplace, you know, not so long

ago for some of us, at least, even for a

711

:

Phil Gamache: lot of Martech vendors,

like it's not a reality for them yet,

712

:

like a lot of the automation vendors

are not cloud based, like they don't get

713

:

data from your warehouse, some of them

are setting up sinks and like direct

714

:

pipelines into it, but at the end of the

day, they're still copying that data.

715

:

iterable and Marketo and customer

IO, they all charge you based on the

716

:

number of users that you're storing

in the Marketo database, right?

717

:

But you're also paying snowflake for

storing those users in that database.

718

:

So I think in the future, I don't

know how far down the line this is.

719

:

And there's some startups that are

kicking around with this idea already.

720

:

Some bigger platforms on

B2C already doing this.

721

:

But this idea of like warehouse native

martech, like connecting directly to

722

:

the database, like sitting on top of

the database, querying it when you're

723

:

creating a segment versus copying it.

724

:

I go super deep on this on the podcast.

725

:

Like there's a lot of ideas and

opinions about this, like copying data.

726

:

Sometimes there's still

upsides to doing that.

727

:

Like you get that data closer to you.

728

:

So when you want to

act on it, it's faster.

729

:

But then there's like latency issues and

it's not necessarily real time anymore.

730

:

So there's, there's a

lot of debates around it.

731

:

But I think eventually the space is

moving to this idea of warehouse native.

732

:

We'll get a

733

:

Justin Norris: selection from your

back catalog of relevant episodes for

734

:

people that want to go deeper into this.

735

:

Before we turn away from the Martech

talk, this is sort of perhaps an

736

:

existential question in some ways,

but as technologists, as operators,

737

:

we all have our preferences.

738

:

Zooming out a level and taking

like a business lens on it,

739

:

how much does it matter?

740

:

We all need this tech to get jobs done.

741

:

Is it a 5 percent competitive advantage?

742

:

Is it a 10%?

743

:

I know that's impossible to quantify,

but what is the ultimate value to the

744

:

business of all of this technology?

745

:

Phil Gamache: Yeah.

746

:

I think if you're putting on a short

term lens and you're trying to hit

747

:

short term goals, it doesn't really

matter whether it's like X or Y, they're

748

:

probably still going to figure out a

way to do it and, and get to like your

749

:

endpoint for your short term goals.

750

:

I think it's important for companies

and that are thinking more long

751

:

term, like when, when you're building

your Martech roadmap and I know

752

:

you had Daryl on the show and we

just finished recording with him.

753

:

Like, he's really big on

this idea of thinking of your

754

:

Martech stack as a product.

755

:

And there's a lot of

things that come into that.

756

:

But like, one of the cool ideas is

like, Productizing your Martek roadmap

757

:

and looking into the future, like

not just next year, but like two,

758

:

three, four years down the line.

759

:

What does that tech stack look like?

760

:

And what do we need to be able

to do by the time we hit like

761

:

our goals in four or five years?

762

:

The tools that we have today, maybe

they're hitting our short term

763

:

metrics, but we're going to have a

data team that's going to be 20 people.

764

:

Are we making the most use out of

those folks if we're using a tool

765

:

that's copying our customer data and

it's not leveraging our warehouse?

766

:

So like with the long term lens, I

think this becomes super important.

767

:

There's obviously a lot of unknowns,

like there's things you can't predict.

768

:

And like, what does the MarTech

world look like in 5 10 years?

769

:

Like, who the hell knows with AI?

770

:

But I think those discussions

are important to have when, when

771

:

you like think of your MarTech

roadmap as, as a product and

772

:

you're trying to productize it.

773

:

On the

774

:

Justin Norris: AI subject, obviously

that's been the buzzword of the year.

775

:

And so I'm not questioning as

AI, it's a fad, it'll disappear.

776

:

I really don't believe that.

777

:

And I don't think that it's.

778

:

Very defensible to believe that

right now, but I do wonder sometimes.

779

:

What is the reality?

780

:

What is the hype?

781

:

What is overblown?

782

:

Was it coming for our jobs?

783

:

And you clearly a very thoughtful

person and have worked more closely

784

:

with it than I think anyone That I've

had the chance to speak to in depth.

785

:

So I'm curious What's your

take next year this time?

786

:

What will the role of AI be in our

daily work from your point of view?

787

:

Phil Gamache: These discussions have

been happening all year with a lot of

788

:

MarTech vendors on the product side

and trying to figure out Do we just add

789

:

a little copy generator on our tool,

a copy assistant, and call it done?

790

:

Like we have an AI feature?

791

:

Or do we really think mindfully

about the future of the space?

792

:

How do we move away from rule

based automation tools that

793

:

are and, or, ifs, ands, whys?

794

:

to letting AI take the wheel when

it comes to deciding what message

795

:

should a certain segment get.

796

:

And I think some tools in the

space that are less legacy have

797

:

already started moving, uh,

towards some of those features.

798

:

But I think that there's some really

interesting capabilities in the

799

:

enterprise space and I've spent

most of my time in Martech and my

800

:

career in startups, but I did have

a stint at automatic and wordpress.

801

:

com and they're like

a:

802

:

So not like a massive enterprise, but

some really, really smart data scientists

803

:

that I had the pleasure of working with.

804

:

And I think that they're like light

years ahead in terms of Building

805

:

stuff in house that eventually is

going to be part of Martek vendors

806

:

is just going to be table stakes.

807

:

One of those things is propensity models,

or this idea of like, uplift modeling.

808

:

Right now when we're doing like

a discount campaign, we just

809

:

finished Black Friday, right?

810

:

Like, folks are sending out an email

to their entire database with a 15

811

:

percent discount notification, right?

812

:

When you send that discount to all of your

customers and a customer who was going to

813

:

buy at full price anyways gets your offer

and buys at discount, you're technically

814

:

losing revenue from that person.

815

:

So there's a lot of literature around

this like uplift modeling idea.

816

:

I think like the early Facebook

data engineers were some of

817

:

the proponents around this.

818

:

Usually like puts folks into four buckets.

819

:

So there's like the sure things.

820

:

Those are the people that are going

to buy, regardless of whether they

821

:

get your black Friday offer or not.

822

:

There's the lost causes.

823

:

They have moved on from you.

824

:

They maybe started a free trial,

but they're not interested

825

:

in buying your product.

826

:

There's the sleeping dogs.

827

:

Those are the folks that might react

negatively to actually getting your offer.

828

:

Maybe they were going to renew, but they

got your email and it pissed them off.

829

:

And now they're not going to

renew because they remembered how

830

:

much they were spending with you.

831

:

But the Persuadables is kind of

the holy grail of, of marketing

832

:

and, and this idea Uplift Modeling.

833

:

This is the most important group

because these are the folks that are

834

:

on the fence about buying something

and are going to be the most receptive

835

:

to getting your Black Friday offer.

836

:

So how do you let AI take over

when it comes to figuring out?

837

:

Your target users, what

bucket do they fall into?

838

:

And how do you only send that discount

to the persuadables and focus on them?

839

:

So yeah, at automatic, I worked with a

data science team that had built out an

840

:

internal modeling engine called pipe.

841

:

And it was so powerful for marketers

and the growth team because we could

842

:

essentially build a model for any of

the events that we were tracking from

843

:

our users from a predictive standpoint.

844

:

So we could build a list and target

specific users for an email campaign

845

:

based on a question that we had.

846

:

Like.

847

:

Which free users are going to buy a site

by day number 30, or which paying users

848

:

are going to churn by day 90, like we

could target specific messaging to those

849

:

users before they actually do that thing.

850

:

Abandoned cart emails happen

after the fact and sometimes

851

:

people have already moved on.

852

:

But when you are able to predict

someone who's going to have something

853

:

in their cart or isn't going to buy

something at the end of a certain

854

:

day, You can get ahead of that and

try to prevent it from happening.

855

:

So there's a whole, like,

bunch of use cases around that.

856

:

And I think that, like, you know,

a lot of folks are still living

857

:

in this, like, rule based nature.

858

:

And the future is really letting these

models be part of the MarTech vendor

859

:

stack so that humans and MarTech folks

are less prescriptive about the campaigns

860

:

and the touch points that are going out.

861

:

And you're letting models predict

whether someone is going to do something.

862

:

And so you're sending them the best

message at the right time to do that.

863

:

Justin Norris: That's funny.

864

:

What you described reminds me a lot of

something I studied when I was first

865

:

getting into marketing talking about 10

or 15 years ago now, I read a book called

866

:

drilling down by a fellow named Jim Novo.

867

:

He did a lot of database marketing, like

shopping network or shopping catalog

868

:

type of thing where you're, you know,

people that are buying stuff like that.

869

:

But they were looking at like recency,

frequency, monetary value, RFM, maybe

870

:

you or listeners are familiar with.

871

:

But it was a very similar idea.

872

:

You divide people into

quintiles, I think it was.

873

:

And then you adjust your

strategy accordingly.

874

:

You have a discount ladder so that you're

not offering big discounts to people that

875

:

we're going to buy anyways, and you're

offering greater discounts to people.

876

:

That are maybe much less likely to come

so you entice them back with a stronger.

877

:

So it makes me feel like many things

that maybe it's applying a much more

878

:

sophisticated set of rules or taking,

you know, a much bigger set of data

879

:

points aside from just those three.

880

:

To do, to take playbooks that have

existed and apply them, you know,

881

:

perhaps in a more intelligent

way or more automated way.

882

:

Yeah,

883

:

Phil Gamache: letting the machine take

the wheel and you're still kind of, uh,

884

:

running point on stuff and monitoring

things and doing QA, but I think like

885

:

gone are going to be the days and five

ish years where the marketer is creating

886

:

rule based automation based on loose

data as opposed to just like models

887

:

with like a bunch of historical data

and events that are way better than

888

:

us at predicting potential behaviors.

889

:

Will

890

:

Justin Norris: LinkedIn by that time?

891

:

Phil Gamache: Maybe not and like the

hands are still going to be weird.

892

:

Justin Norris: Touching on the

personal side, now you mentioned

893

:

you're a new dad, you have a full

time job, you have this side gig, this

894

:

project, really almost a second job.

895

:

How do you balance

896

:

Phil Gamache: all that?

897

:

Yeah, this is a key theme for us in every

episode that we chat with folks, so.

898

:

I think, for me, we pride ourselves on

this idea that, like, balance is like

899

:

this fixed point in the journey that,

like, it's something that we, we need to

900

:

reach, uh, but I think it's just this,

like, this continuous journey rather

901

:

than a, a, a final destination and it

involves a ton of stuff and every human

902

:

is different and different things.

903

:

Energize people and different things like

reduce the battery on, on a lot of folks.

904

:

So for some folks like passion

and alignment and making sure

905

:

that you're doing meaningful work,

that's like a big part of my job.

906

:

I work at Pelago that

helps conquer addiction.

907

:

And, you know, a lot of companies

like to say that they're saving

908

:

the world and they're saving lives.

909

:

We're not doctors, we're not saving

babies, but we are saving people from

910

:

their addictions, and we have saved

lives, and I think that's a, a super

911

:

powerful, uh, thing to be able to say,

like I, I help run the MarTech stack

912

:

and, and run the growth team that runs

Essentially, like when we convince

913

:

someone to sign up, like they quit

their tobacco addiction, they quit their

914

:

opioid addiction or they reduce their

drinking and it has like meaningful

915

:

impact on, on other people's lives.

916

:

The other thing for me that drives me is

this idea of like personal recharging,

917

:

being able to take time away from work.

918

:

Like I love MarTech obviously, like

I'm able to have a podcast about

919

:

it that I'm doing on my free time.

920

:

But I'm still a big fan of escapism,

healthy escapism, going for walks

921

:

with with my dog, my wife, my newborn,

taking part into TV shows, a big fan

922

:

of like science fiction and reading

books and just like escaping the

923

:

world that is like day to day grind.

924

:

But for me, age old advice that actually

comes out in a lot of the answers on

925

:

the show when we ask this question

is To never underestimate the power

926

:

of a well timed no when you get a new

request or you get a new opportunity.

927

:

That's the key to

maintaining that balance.

928

:

Like we had Lauren on the show

and she put it really nicely.

929

:

I don't know if she came

up with this or not.

930

:

She was like, life is about like

juggling and you have a bunch of balls

931

:

in your hands that you're juggling.

932

:

Some of them are made of glass

and those are the important

933

:

ones that you can't drop.

934

:

So it's about figuring out what are

the most important things that you have

935

:

going on, making sure you're prioritizing

those, and not feeling stressed about

936

:

saying no when other stuff comes up

that won't have the bandwidth for.

937

:

Justin Norris: It's good advice.

938

:

It's good to know you're

a, uh, a sci fi fan.

939

:

We didn't go into Star Trek and Martek,

but I think there's a whole other show

940

:

there we could do, but I really appreciate

you spending the time with me today, Phil.

941

:

You're a super interesting

guy and inspiring what you've

942

:

achieved with the podcast.

943

:

And I also just think how it's informed

your perspective or the interplay between,

944

:

you know, the learning and discussions

you've had through the podcast and your

945

:

thoughtfulness as a Martech leader, as

a growth leader and what you're doing.

946

:

We'll include lots of links in the show

notes again to some choice cuts from the

947

:

back catalog for folks that want to go

deeper Into human smart tech, but really

948

:

appreciate you chatting with me, and

I hope we get a chance to speak again.

949

:

Yeah, it's a

950

:

Phil Gamache: super fun thanks for

having me and really excited to see the

951

:

trajectory of this show and happy to

support you and Excited to keep listening.

952

:

I've listened to all all episodes so far.

953

:

So Keep it up, man.

954

:

Hey

955

:

Justin Norris: everyone.

956

:

I want to invite you over to the

Rev Ops FM substack community

957

:

where you can sign up to get rough

transcripts, show notes, longer form

958

:

articles, and other bonus content.

959

:

Just head over to rev ops fm slash

subscribe to get free access.

960

:

I'd also love to know what you thought

of the episode and to hear suggestions

961

:

for topics you want to learn about.

962

:

Feel free to leave a comment

on substack or send me an

963

:

email at Justin at rev ops fm.

964

:

Thanks for listening.

Show artwork for RevOps FM

About the Podcast

RevOps FM
Thinking out loud about RevOps and go-to-market strategy.
This podcast is your weekly masterclass on becoming a better revenue operator. We challenge conventional wisdom and dig into what actually works for building predictable revenue at scale.

For show notes and extra resources, visit https://revops.fm/show

Key topics include: marketing technology, sales technology, marketing operations, sales operations, process optimization, team structure, planning, reporting, forecasting, workflow automation, and GTM strategy.

About your host

Profile picture for Justin Norris

Justin Norris

Justin has over 15 years as a marketing, operations, and GTM professional.

He's worked almost exclusively at startups, including a successful exit. As an operations consultant, he's been a trusted partner to numerous SaaS "unicorns" and Fortune 500s.