HomeVideos

Skip Zapier, Go Straight to Code: Inside the Future of Sales & Marketing Ops

Now Playing

Skip Zapier, Go Straight to Code: Inside the Future of Sales & Marketing Ops

Transcript

1602 segments

0:00

So, what is a GTM engineer, and why is

0:02

it one of the fastest growing roles

0:05

right now that's coming into the market?

0:06

Why are so many companies hiring [music]

0:08

for it? A GTM engineer is a go-to-market

0:10

engineer, and they basically use

0:12

software to build pipeline for

0:14

companies. They use tools like Cloud

0:16

Code and all of these different APIs to

0:18

basically wire together automations and

0:21

workflows and even agents that can do

0:23

tasks or run autonomously. Now, on this

0:25

episode today, I'm hosting my friend

0:26

Ben. Ben is a GTM engineer who's worked

0:28

at multiple startups, and he's going to

0:30

be talking about what the actual job

0:32

role and function looks like and how

0:34

companies can be successful by

0:36

implementing these people at their

0:37

organizations. Specifically, some of the

0:39

things that I found really interesting

0:40

about this conversation is we're going

0:42

to talk about how API [music]

0:43

completeness is now the buying criteria

0:45

for software. An example of this is how

0:47

Salesforce is actually better now than

0:48

HubSpot because you can do more through

0:50

the API. [music] We're going to also

0:51

talk about how you can build UIs just in

0:54

time for your team for internal tools.

0:56

And this interface can be anything that

0:57

you need it to be because you can just

0:59

vibe code it. We're going to talk how

1:00

you should just leap over entirely from

1:03

Zapier or n8n. Don't even touch him. Go

1:06

immediately to code. The benefits of

1:07

that and why it's the better way to

1:09

start building these solutions. And then

1:11

we're going to talk actual workflows.

1:12

What does Ben's day-to-day GTM

1:15

engineering work actually look [music]

1:16

like? Where are the opportunities right

1:18

now on cold outbound and how you can

1:20

actually build pipeline for your sales

1:22

team. And this episode is brought to you

1:23

by graft.com. Graft.com is the platform

1:26

to deploy marketing agents with. It's a

1:28

data pipeline, a data warehouse, and

1:30

then also a cloud server that you can

1:32

push code to or agents to.

1:34

>> [music]

1:34

>> With that stack, you can build basically

1:36

anything that you need for marketing

1:38

engineering. And the best part about

1:39

Graft is that four deployed software

1:41

engineers can do these implementations

1:43

for you on top of the platform. They're

1:44

basically like Palantir, but how you do

1:47

if you're trying to implement marketing

1:48

agents for your business like a Facebook

1:51

Ads agent, a Google Ads agent, an SEO

1:53

agent, a cold email agent, go to

1:55

graft.com to learn more. All right,

1:57

let's get started with today's show.

1:59

>> [music]

2:08

>> Dan, what's up? Man, we've been chatting

2:10

online for like months, but I'm I'm so

2:12

stoked to actually have you on and be

2:14

able to share You have so much knowledge

2:15

on the GTM engineering side. I feel like

2:17

you're one of the few people that's

2:19

really actually doing this in

2:20

organizations. Like a lot of these guys

2:22

are just like you know, lone wolves.

2:25

Maybe they run it like a

2:27

you know, an ex-clay agency. They've now

2:29

moved everything to a super base and

2:31

like a railway server, right? But I feel

2:33

like you're one of the few people I see

2:35

that's actually doing these GTM systems

2:37

within companies. So, man, you you I

2:39

read you said this the other day online

2:40

and I

2:41

I just always resonates with me. You're

2:43

like salesforce is now the best CRM for

2:47

go-to-market.

2:49

Why do you believe that? Like why did

2:50

you say that?

2:52

I'd love to go deep on that for me.

2:54

>> Yeah, so

2:55

>> Um

2:56

>> So, first of all, it is

2:58

I don't care what anybody says. Like

2:59

listen, Adia is cool. We use HubSpot at

3:02

AirOps, which I wasn't a super huge fan

3:04

of and I don't think it's like a big

3:05

deal to say that, but

3:07

all these other CRMs like they they have

3:10

cool features. Like don't get me wrong.

3:13

But actually what's happened now that

3:15

you can just plug the salesforce CLI

3:17

into cloud code, all of that like legacy

3:20

complexity and all of those like crazy

3:22

endpoints and everything

3:24

that used to be like a huge pain in the

3:25

ass are actually like an asset in the AI

3:28

era and because I say

3:30

I'll give you an example of something

3:31

that's really stupid probably to most

3:33

people, but is a

3:35

symptom of how good salesforce actually

3:37

is now, which I know it's crazy that we

3:39

are having this conversation. Like we're

3:40

out here selling salesforce. Like we

3:42

should be getting kickbacks on

3:43

salesforce for this hopefully, but

3:45

um

3:47

when my

3:48

my previous company Sift

3:51

we you could literally provision user

3:54

security settings from the terminal.

3:58

Um

3:59

and some people might say, "Well, who

4:00

who cares?" Well, first of all, if

4:01

you're Salesforce admin or like an IT

4:03

person, you definitely care. Um

4:06

but

4:07

it's that sort of like attention to

4:08

detail that

4:10

makes something actually usable by

4:12

agents. Um that's so important now

4:15

because think about like you could have

4:16

you could build your own onboarding

4:18

flow. Like if you wanted to set

4:19

something up in cursor with all the end

4:21

points, it's like, "Okay, well, the rip

4:22

laying API is like this person's

4:24

onboarded. What what's their uh user

4:26

group?" Oh, they're an SDR. Well, we

4:28

already have all that provisioned. Um

4:30

and just go do the [ __ ] like

4:32

automatically. And I'm sure there's

4:33

services out there that do this, but

4:35

for enterprising teams who want to run

4:38

lean, who don't want to buy a widget for

4:39

like every [ __ ] business process,

4:42

like this stuff is a huge asset. Not

4:43

even not even getting into any of like

4:45

the actual sales and revenue generating

4:47

like potential of that. So, all those

4:50

features, right? So, that's that's my

4:51

like 10-second bit on why Salesforce

4:54

rocks and everything else sucks.

4:57

>> I I I think this is a larger like theme,

4:59

too, right? I mean, this is basically

5:01

how honestly, I got to tell you this

5:02

like my how I think about software and

5:05

choosing purchasing software now is

5:07

based off of what you you saying this

5:09

like 6 months ago. Like I I am now all I

5:11

think about is like how robust is the

5:13

API and do I have to like if I can't do

5:17

everything

5:18

through the API that I can do within the

5:20

UI of the website, like I am not buying

5:23

that software at this point.

5:25

Cuz it's like, "Why would I ever try to

5:27

touch a UI?" And and and really what it

5:29

comes down to even more so is like if I

5:31

need a UI, I'll just build a custom one.

5:34

Like we're doing this more and more now

5:35

where it's like if I need some type of

5:37

visual way to interact with like

5:39

whatever it is that I'm doing, I will

5:41

just use my like I will build the custom

5:43

solution that I need like just in time,

5:45

right? Cost of code has gone to zero and

5:47

I can basically build the exact solution

5:49

that I need. Um like if I need to click

5:51

a button or like view you know, have it

5:54

build a flowchart to understand what's

5:56

going on. This I think it relates It's

5:58

funny I've been having a lot of

5:59

conversations with companies and all

6:00

that they're like, "Why wouldn't we use

6:02

Zapier or like N8N to do this? Like why

6:05

would we Why should we go straight to

6:06

code? Like it's hard to visualize." And

6:08

I'm like, "Just ask it to visualize it.

6:10

Just ask it to make a work like It's

6:12

just a It's a flowchart. That's that

6:14

That's not complicated. It can do It can

6:15

show you that logic." So

6:17

>> Yeah, that's so funny the portfolio

6:19

Well, you guys can't see in the chat,

6:20

but I was sending my portfolio earlier

6:22

and like it's literally all these

6:23

mermaid charts. I'm like, "Hey, I have

6:25

all these like old repos. Make mermaid

6:28

charts out of these." Like there's

6:30

nothing uh sophisticated about this

6:32

stuff. This is like an amalgamation of

6:33

like all the systems that I was running

6:35

and um this is like some some of the

6:37

smaller subsets, but like all this stuff

6:40

is like generated by Cursor.

6:42

Like um

6:44

and there's a ton of different like

6:45

pieces of code out there that it can

6:47

like then string together for like that

6:49

big mermaid chart. But yeah, um yeah,

6:51

it's funny that when you talk about like

6:53

N8N or something, somebody was um

6:56

telling me that Make was hiring for a

6:57

job in Raleigh or whatever, which is

6:59

kind of near me, and I was like, "Dude,

7:00

like how are these companies still in

7:02

business? Like if you're at Zapier or

7:03

Make, like I'm not trying to be a dick,

7:05

but like how are you How are these

7:06

companies still in business?" Um because

7:09

when I used to use those things, dude,

7:11

it was such a headache. And like I like

7:13

to think I'm pretty smart. I just I

7:15

think I have like, you know, ADD or

7:16

something and I'm like, "I can't I can't

7:18

get this [ __ ] workflow to work." Um

7:21

and when you're in Cursor or something,

7:23

it's like, "Hey, fix my workflow." And

7:25

you know what's crazier about this, too,

7:26

is like N8N had an opportunity to

7:29

actually really get people more embedded

7:31

into their tools when AI started like

7:33

coming out because

7:34

think about it, like the stuff that we

7:36

were talking about with Salesforce, like

7:37

N8N already has all that. They already

7:39

have all their endpoints and they have

7:41

metadata about what these endpoints are

7:43

supposed to do. And like, why did it

7:45

take them so long? I don't even know

7:46

what they're doing now, but like I

7:47

assume by now they've solved this

7:48

problem. Like, why did it take them so

7:50

long to like act upon the market forces

7:53

and like actually take advantage of

7:54

that? Like, I don't know.

7:56

>> Totally. I mean, I think and this was

7:58

the major learning like in the epiphany

8:00

I kept So, I was using N8N for a lot of

8:02

the stuff that I was doing on like the

8:05

marketing engineering, whatever you want

8:06

to call it. Like this this category that

8:08

we're in. Um but I found myself I was

8:11

using Claude code to create

8:14

uh or I was basically using a

8:16

state-of-the-art model to create JSON

8:18

files that I would drop into N8N. And I

8:20

was like

8:20

>> exact same thing.

8:21

>> Exactly. And you're like I'm like I was

8:23

like I'm vibe coding here. Why am I

8:24

doing this? Why am I not just going

8:26

straight to a server, right? Like, why

8:27

am I not just pushing code? And I think

8:29

that it leads into the next thing I want

8:31

to talk about with you. You you you you

8:33

say this all the time um about really

8:35

like code is the truth now of like what

8:38

you're doing as it go to market like for

8:40

go to market. Like it's almost a log of

8:42

your actions and your activities and you

8:44

know, everything that you're doing at a

8:46

company. I I think you advocate for this

8:48

a lot. Like if you don't have a GitHub

8:49

repo showing the stuff that you've done,

8:52

right? For the work that you've done at

8:53

companies, like

8:55

like that that is what the future of

8:57

this looks like, you know, for

8:58

everybody. They you need to learn how to

9:00

build these systems. Uh what's your

9:02

thoughts on that? Like do you do you are

9:04

you seeing I mean,

9:06

more I I I think we're both kind of on

9:08

the forefront of this. This is how we

9:09

think about everything now is like I'm

9:10

not trying to hire a marketer

9:12

traditionally. I'm trying to hire like

9:14

somebody that uh can actually build

9:17

systems and use all these AI tooling to

9:19

like build out processes, not just like

9:21

do individual, you know, campaigns that

9:23

are one-offs. But I love to think about

9:25

I love to hear about your systems design

9:26

and just like how you're approaching

9:28

like I am writing code that build, you

9:30

know, and trying to create this log of

9:32

all my actions. If you would want to go

9:34

down that that rabbit hole with me.

9:36

>> Yeah, yeah. So, um so first uh I think

9:39

when we talk about like hiring people,

9:41

um

9:44

like revenue operations people,

9:47

go to market people, engineers,

9:50

I don't know where this is going to end.

9:51

Like I guess like you don't want an

9:52

enterprise account executive to have a

9:53

GitHub repo. I mean, it'd be cool if

9:55

they did, but like I don't know if

9:56

that's super relevant for them, but like

9:58

even like the SDRs at AirOps were like

10:00

five coding stuff. And like those are

10:03

one of the things that I enabled some of

10:04

them to do is like, "Hey, we have the

10:05

growth team GitHub. If you have

10:07

automations, put them here, and like we

10:09

can like build upon this stuff like over

10:11

time." And we even had some of like the

10:14

less technical marketers. I was like

10:16

red-pilling them on this stuff. I'm

10:18

like, "Use the GitHub so that like I can

10:20

help you with this stuff. Other people

10:21

can help you with this stuff."

10:23

Um [snorts]

10:24

I am seeing like the top tier of like

10:26

GTM engineers like have GitHub repos,

10:28

and I think that a lot of the I don't

10:30

want to say like whatever middle tier I

10:32

don't know cuz I don't know like how

10:33

talented these people actually are. Um

10:35

but

10:37

I'm seeing more people adopt it. And to

10:39

me like not having a portfolio,

10:43

like there's so many other jobs where

10:45

you'd have a portfolio.

10:46

And like that's your

10:48

I don't know, stamp of approval or or

10:50

calling card or whatever. And

10:52

when like [snorts] people are trying to

10:53

get into GTM engineering, they're like,

10:55

"You know, I'm interviewing for GTM

10:56

engineering roles, but I'm not having

10:57

much success. Like what should I do?"

10:59

I'm like, "Well, you need a portfolio,

11:01

and you need to like be

11:02

working on these problems over time

11:04

because it's not the same as just being

11:06

like a random like campaign manager

11:09

where you're like, "Okay, we sent out an

11:10

email campaign. We'll see if it works."

11:13

It's like, "No, like

11:15

I had

11:17

a folder

11:18

where it it had all of my email

11:20

campaigns that had ever been sent, all

11:22

of the copy, the background, the context

11:24

on each one." And this was not something

11:26

that I finished, but it's something that

11:28

I need to do is like build Like gotten

11:31

into loops yet. Maybe maybe you can

11:32

educate me on those later, but like

11:35

Uh and Eric Nittolosso talks about this,

11:37

too, I think. There's probably some

11:38

other people who are a little bit

11:38

smarter than me about this particular

11:40

point. Where like every time [snorts]

11:41

you send an email campaign, you should

11:43

recursively use AI to like improve it

11:45

over time based on like response rates,

11:47

like how uh improve segmentation, like

11:49

things like this. And so that's like

11:50

something that would sit in a in a

11:52

GitHub repo. But yeah,

11:54

I mean, the bottom line is if you're not

11:56

like keeping a record of your work

11:58

either

11:59

uh for yourself or for your company to

12:01

like that's the that's the real value in

12:03

it is I think like when a GTM engineer

12:06

is like building something and leaving

12:08

it there for the company when they

12:09

leave. Like AirOps has all the stuff

12:10

that I built, you know, in in the group

12:12

GitHub repo. So, yeah.

12:15

>> No, absolutely. I I It's funny you say

12:16

the loops thing. I feel like it's people

12:18

overcomplicate it so much and it's like

12:21

it's just what a human was doing

12:22

previously, but now we're just like

12:24

using agents within that process. Like

12:25

for example, say you're doing a cold

12:26

email campaign. Like how would you find

12:28

success? I would be like, "Cool. Like if

12:30

you're starting out from zero, we cold

12:31

email a bunch of people. We create

12:33

pipeline. We like have calls. We look at

12:35

who closed. And then we're like, 'Okay,

12:37

companies that have this shape

12:39

like they're the best companies.

12:41

Let's go find more companies that have

12:43

this shape.' But I think the granularity

12:44

that you can get to now is really

12:46

interesting cuz it's like, 'Oh, I can go

12:48

and I can scrape their similar web

12:50

traffic to be like, okay, what is their

12:52

What is the similar web traffic of a

12:53

good client look like for us?' Okay, I

12:56

can go and scrape their um for example,

12:59

um

13:00

uh like job post listing history. Like I

13:03

can scrape like there's all there's all

13:04

these different things that I can use to

13:06

enrich like who What does our target

13:09

customer look like? Both from like a

13:11

firmographic standpoint, but then also

13:13

like you can start to uh

13:15

like mine the sales transcripts,

13:17

understand like where were they at at a

13:19

given moment in time. Can we find other

13:21

businesses that have like that

13:22

psychographic that are, you know,

13:24

they're that look like for example, like

13:27

uh you know, we can go into signals

13:29

probably all day and there's people that

13:30

are way more advanced on this than I am,

13:32

but you know, one of the easiest signals

13:33

is literally like or two of them that we

13:35

see the most success with is like, did

13:37

they interact with content on LinkedIn

13:39

that's related to the product that we're

13:41

trying to sell? Um

13:43

and the second one is like, are they

13:45

hiring like for specific job roles that

13:47

we basically like augment or totally

13:49

replace that job role, right? Um and

13:52

then from that it's like, okay, is it

13:53

the company size that's appropriate for

13:55

it, but I think on the loop piece,

13:56

that's the thing like it's just it's

13:57

exactly what a human was doing

13:58

previously, but just didn't have time

14:00

for it, but now we can just do it at a

14:01

scale and with at a granularity with

14:03

also like more metrics than we

14:05

previously could, so.

14:07

>> Yeah, well,

14:08

that's what I was going to say about the

14:09

loops, too, is like you actually have to

14:11

know what information to enrich, which

14:12

is kind of like a crap shoot, so it's

14:14

kind of like you could you have to go

14:16

get everything like 100, you know,

14:18

different data points and

14:20

you know, at that point I feel like

14:22

sometimes like the

14:23

>> [gasps]

14:24

>> granularity and detailed like nature of

14:26

all that information can actually be

14:28

like distracting.

14:29

Also, the funny thing about like people

14:31

say this about like sales conversations

14:33

and stuff, too, but dude, listen, I I

14:35

mined thousands of conversations from

14:39

Gong at AirOps and there was a lot less

14:42

information there than than you would

14:44

hope and this is nothing against the

14:46

sellers at AirOps. I love you guys, but

14:48

it it's not always like people don't ask

14:52

the best questions for for me, you know,

14:55

which is not the point of them having a

14:56

sales conversation to be fair.

14:57

>> No, yeah, they're doing a talk track.

14:58

It's like how different can it be if

15:00

they know like if you know a talk track

15:02

works and it actually closes, like

15:03

you're going to do that same talk track

15:05

>> [laughter]

15:05

>> Yeah, you're not going to ask them like,

15:07

how are you feeling today? Like,

15:09

how many people did you hire last month?

15:11

Like, nobody's going to [ __ ] ask any

15:12

of that stuff.

15:13

>> No, totally. Totally. Yeah, I mean, we

15:15

just like all that information we're

15:17

just collecting anymore from like Reddit

15:19

or from like social chat channels like

15:22

we're using the uh

15:24

more and more just like scraping like

15:25

Tik Tok and Instagram to find like what

15:28

are the people talking about that are in

15:29

this category and like can we figure out

15:32

different or unique ways to talk about

15:34

the product? Um cuz I I feel you you you

15:37

said this before we jumped on the call.

15:38

It's like everything is becoming red

15:40

ocean right now. Like whether it's paid

15:42

ads, whether it's SEO, whether it's cold

15:45

email, like any cat like any any

15:47

everything is becoming just absolutely

15:50

cooked. Um

15:51

the

15:53

I I think the only way that we're seeing

15:55

that you can find like edge is you have

15:57

to basically map out what is everybody

15:59

doing in the market and a lot of the

16:01

times that your competitors are all

16:03

positioning themselves in the exact same

16:04

ways that you are.

16:07

Or like you know, they're all like

16:08

they're basically like you know, if you

16:10

think about it as a

16:11

a matrix, right? Where it's like here's

16:13

you know, five different ways I can

16:14

position and here's like 10 different

16:16

situations I could be in. They're all

16:18

kind of they'll they're going to be

16:19

bunched together.

16:20

Um and what you'll find is that like

16:23

rather than competing in that red ocean

16:24

space, if [clears throat] you go over to

16:25

this blue ocean space for like nobody

16:27

else is positioning themselves or like

16:28

talking about the product in that way,

16:30

it's so much easier to compete there.

16:32

And we see this within the ads all the

16:33

time where it's like, okay,

16:34

can we find some type of alpha within

16:36

the way that we're describing the

16:38

product or the pain that we're talking

16:39

to or the outcomes that we're talking

16:40

to, etc. Um but anyway, I I think it's

16:44

it's also

16:45

like something what we're seeing and

16:47

that's really top of mind for me is like

16:48

certain categories are extremely

16:50

competitive. Like I I

16:51

I imagine with Air Hops like you guys

16:54

there's so many companies that are doing

16:56

like AI search observability. Like how

16:59

do you differentiate in a category like

17:01

that? It gets really challenging, but in

17:03

contrast like we're working with a

17:04

company right now. They're like a motion

17:06

graphics company.

17:08

Um and for them uh like there's just not

17:12

a lot of players in the category yet.

17:14

And so it's just so much more blue

17:16

ocean. And I think this is just, you

17:17

know,

17:18

Anyway, I'm curious your thoughts there

17:20

like how you're thinking about it or how

17:21

how are you like trying to extract or

17:23

find that arbitrage or find that edge

17:25

within the current market? Also, just

17:26

what are you seeing on the front lines

17:28

from a competitiveness?

17:30

>> Well, okay. So, yeah, this is a great

17:32

conversation to have because Owen Clancy

17:34

who is my the VP of growth he left but

17:37

he was the VP of growth who hired me at

17:38

AirOps. Amazing guy if anybody's on

17:41

LinkedIn you should go he doesn't really

17:42

post anything but you should go ahead

17:43

him up. He's he's doing recruiting now.

17:45

So, anyway,

17:47

um

17:48

he would send me emails that like he

17:50

would get because people are, you know,

17:52

VP of growth they're going to send them

17:53

emails even though we literally sell

17:55

what they're they're trying to sell him.

17:57

And it was very interesting like some

17:59

people did a really good job with their

18:01

emails

18:03

and some of them did really bad job but

18:06

I don't think I think from a like a to

18:08

zoom out a little bit I don't think that

18:09

most people

18:11

understand the market that they operate

18:13

in and I think about this all the time,

18:14

right? Like people are like, "Oh, yeah,

18:15

I work at this venture-backed company.

18:17

We just raised a series B." I'm like,

18:19

"Okay, well, you just raised a $20

18:21

million series B or whatever it is.

18:23

Let's remember that the GPs in all those

18:25

funds

18:26

are LPs in other funds and they're

18:29

de-risking their investment by investing

18:31

in five other companies just like yours

18:33

who have the exact same positioning or

18:35

selling exact same product. We're all

18:37

just a bunch of monkeys in a knife fight

18:39

for the venture capital firms which is

18:41

fine. I'm not complaining. That's that's

18:42

what we all signed up for or I don't

18:44

know if you signed up for that. I don't

18:45

know if you're bootstrapped or whatever

18:46

but

18:46

>> Yeah, yeah, we we raised a pre-seed in

18:47

October.

18:49

We we just had to like make this like

18:51

infrastructurally we couldn't do it

18:53

bootstrapping so

18:54

>> Yeah. Well,

18:55

you have to

18:56

>> sign a sign a Fivetran contract. We love

18:58

you Fivetran. Thank you for all

18:59

everything you do for us but like yeah,

19:01

there was no way we were going to be

19:02

able to handle that so

19:03

>> Yeah, well, so you know this raising

19:06

money is an obligation not an

19:07

accomplishment. It's the the beginning

19:09

of the work and not the end but um

19:12

but yeah, uh there's a couple things I

19:13

can't really talk about that we were

19:14

doing at Ahrefs, but uh that they

19:16

wouldn't want me to talk about, but

19:18

um positive things like uh we were

19:21

trying to get a differentiation on our

19:23

positioning and go uh deep into one

19:26

vertical that we really believed uh we

19:28

could conquer. Um and especially like in

19:31

AI search, the thing about like Ahrefs

19:33

is like that we weren't just doing

19:35

visibility, but that's what you know,

19:36

right? Like and that's the problem.

19:38

That's that's that was our problem that

19:39

we were dealing with, right? Because

19:41

Profound was our biggest competitor.

19:42

They sort of I think we can say that

19:45

they won the visibility round for like

19:47

the last year. Um so, you know, hats off

19:50

to them

19:51

uh

19:51

>> [snorts]

19:51

>> for sure, but they also raised an insane

19:53

amount of money and I don't think that

19:55

their revenue is

19:58

like I just think that they have a a

19:59

very long road ahead of them. Um so,

20:02

best of luck to to them and they're

20:04

dealing with the same stuff, but

20:06

um yeah, finding differentiation is

20:09

really tough. I will say like one of the

20:10

things that I worked on right before we

20:12

left was um this lead magnet, which I

20:14

think I can talk about this. I don't

20:15

think it really matters. Um

20:18

where basically we went really deep on

20:19

analyzing

20:21

um everything about the company's uh

20:22

company's website, all of their AI

20:24

search performance, and we got like this

20:26

snapshot in time about like what how

20:27

they were actually performing against

20:29

competitors and things like this, right?

20:30

>> [snorts]

20:31

>> So, the lead magnet was great. Um it

20:33

generated a lot of pipeline for us

20:35

in a very short amount of time, and it

20:36

was really what what I thought of it as

20:38

like a V1 of a sales enablement product

20:40

and like marketing product that you

20:42

could actually spin off into a bunch of

20:43

different directions, um which is going

20:45

to be like phase two, and that's what I

20:46

would tell people. I'm like, "Okay,

20:47

guys, like I know the lead magnet was a

20:49

huge pain in the ass for us to build and

20:50

maintain and all this stuff, but it's V1

20:53

of a platform that we're developing for

20:56

our sales and marketing team." And um I

20:59

don't think that every industry has like

21:00

a tool that they could build like that

21:02

that would generate alpha.

21:04

Uh if anybody wants to know about it, I

21:05

can talk in more detail about it after,

21:07

but like um message me. But um

21:10

trying to find alpha and like leveraging

21:12

it in interesting ways and presenting it

21:13

in interesting ways

21:15

um

21:16

is something that like I think about a

21:18

lot. The problem with this lead magnet

21:20

though is like okay, think about this,

21:21

right? Like you get an email where like

21:23

hey, we did some analysis on your search

21:25

AI search performance.

21:27

SEO offers are so commoditized like that

21:30

you like VPs of growth, webmasters, I

21:33

don't know if that's a term that SaaS

21:35

bros use, but like the directors of

21:37

digital marketing, I don't know,

21:38

whatever.

21:39

They get so many emails where they're

21:40

like hey, your your traffic is down, you

21:43

know, all those like [ __ ] like

21:45

commodity sort of offers. And so how do

21:47

you actually present that in a different

21:49

way was a much different question and

21:50

like a much harder question to answer.

21:51

And I think we did a pretty good job of

21:53

it by like naming specifics from the

21:54

research that we actually did. Said hey,

21:56

you're not doing so well against this

21:58

competitor. We actually have a bunch

22:00

more we actually have an amazing data

22:01

set on this.

22:03

We would love to walk you through it and

22:05

you know, see if it could be useful. And

22:07

so that

22:08

Anyway, I'll I'll just like pause there.

22:10

Um but that's sort of like how we were

22:11

thinking about it.

22:13

>> No, man. I think it that's such a like

22:16

the insight there is like you have to

22:17

have some type of proprietary

22:19

information. Like everybody can go find

22:20

anything that's public, right? So like

22:22

that historically that was just like can

22:24

you systematize the process of getting

22:27

unique insights and sending them at

22:28

scale, right?

22:30

Um

22:30

but now it's you really have to have

22:32

some like secret sauce and that's the

22:34

only way that you can actually compete.

22:36

I also think that there's this something

22:38

to be said about like like the cost of

22:40

software has gone to zero. You can use

22:42

that as like a lead magnet now. So I I

22:44

have a friend who's running this company

22:45

is in the mental health space. Um

22:47

they have this mobile application and

22:49

like their data looks like super good

22:51

from a retention standpoint, all this.

22:53

Extremely cheap. And I'm like why is it

22:55

why are you charging so little? Like

22:56

this is crazy. And he said Cody, this is

22:58

marketing for me cuz like if I get all

23:00

these people into this app and like have

23:02

them, you know, basically using this

23:03

constantly, then I can go and it creates

23:06

pipeline for me to like, you know,

23:08

sell mental health like counseling,

23:10

right? Like to like whatever BetterHelp,

23:12

etc. And I it kind of was this epiphany

23:14

to me of like, okay, you can make these

23:16

like micro, whatever you want to call

23:17

them, like like features

23:20

and they become almost the lead magnet

23:22

itself. Like it's like the software

23:24

>> [laughter]

23:25

>> or this like custom thing that you build

23:26

is is what you use to get people in the

23:29

door. And I think that gets like pretty

23:30

exciting when you think about that at

23:31

scale and

23:33

it's It's really fascinating, man. I I

23:34

think that um

23:36

like this is also like a part of like

23:38

this new like go-to-market, you know,

23:40

your GTM engineer, marketing engineer

23:43

role is like what what free things can

23:46

you like what what can you give the

23:47

market that's relatively zero cost um

23:50

but historically would be impossible to

23:52

actually ship because like you you

23:54

couldn't actually get, you know, product

23:55

used to be the hardest thing to get out

23:56

the door cuz engineers were the most

23:58

expensive, you know, asset that we had

24:00

in an organization. I mean, that's kind

24:01

of flipped. It's like I can build

24:02

anything now. Now do you Now how do you

24:04

build this thing that is actually useful

24:06

and like have that filter for that? Um I

24:08

think everybody's calling this uh like

24:10

right now. It's it's basically taste,

24:12

which I think is like such a dumb way to

24:14

think about it. It's more just like what

24:15

does the market have appetite for?

24:17

That's actually the better way to think

24:19

about it. Um so

24:20

>> I think it's almost like expertise

24:22

though because think about like

24:23

companies like Clay and AirOps was

24:26

somewhat moving like in this direction.

24:28

Um and I'll I'll hear this I'll explain

24:31

it. Uh Jesse over at Lead Magic has this

24:33

like bit

24:34

that he does.

24:36

He's like, there's no such thing as

24:37

SaaS. Uh

24:39

there's software and then there's

24:40

services and they're not the same and

24:42

you have to sell both of them. And I

24:43

think that's kind of like where we're

24:44

moving like with something like the lead

24:45

magnet because like like to be fair,

24:48

like a lot of the stuff that AirOps

24:50

does, like

24:52

you could do on your own, but if you

24:54

don't have like alpha and expertise to

24:56

execute on these projects, like you may

25:00

put yourself in a bad hole. Like a lot

25:02

of the stuff that you do, this is why we

25:03

wanted to have you on one of our

25:04

webinars,

25:05

>> [snorts]

25:05

>> but um I think the the decision was like

25:08

um

25:08

if Cody comes on the webinar, he's going

25:10

to show up people how to do air ops for

25:11

free or whatever. But [laughter] like

25:14

>> That was the problem. I was like, all

25:16

right, maybe I can figure out how to

25:17

like fit this together where I like the

25:19

tooling is a part of the process, but

25:21

anyway, yeah, go ahead.

25:23

>> But

25:23

>> [laughter]

25:24

>> no, I mean, I I still think we should

25:25

have had you on because I don't think

25:26

that stuff matters. Because what happens

25:28

is

25:29

what like

25:30

uh okay, let me try not to go off on

25:32

another tangent, but like HubSpot just

25:33

implemented their like AIO

25:36

uh tool. It it's not good. It's actually

25:38

really bad and it's going to lead a lot

25:40

of people astray and they're going to

25:41

end up wanting to

25:43

buy something more mature and

25:45

purpose-built. And so like if somebody

25:46

tries to run the Cody Schneider

25:48

playbook, they're probably going to

25:49

shoot themselves in the foot. Like just

25:51

being real. Uh most people do not have

25:53

the expertise to do. It's the same thing

25:54

with cold email. People are like, "I

25:55

sent a million emails and like nothing

25:57

happened." I'm like, "Okay, well, let's

25:58

like

25:59

let's examine what you actually did and

26:01

maybe we can talk about like why it

26:02

didn't work and maybe why you need some

26:04

level of better expertise because doing

26:07

the actions at volume is like we said,

26:09

it's not the problem. Um so

26:12

anyway, I

26:13

>> No, man, I think everything you're

26:15

saying is exactly what we're

26:16

experiencing and feeling like on our

26:18

side of like the aisle. Um so like you

26:22

know, I I can't tell you how many

26:23

conversations I had where it's like I

26:25

had Claude code running our SEO and it

26:27

looked great and now it's absolutely

26:29

nuked. And it's like, yeah, it's cuz you

26:31

weren't, you know, you you it's still

26:34

like the tool is only useful by a person

26:37

that knows how to wield it, right?

26:38

>> Yeah. Um like I I and I think it's that

26:40

same principle. Like all this is is just

26:42

a tool for for execution. And and

26:44

there's ways to create those guardrails,

26:46

um but I mean, we're

26:48

you know, we're we're still figuring out

26:49

like how do we do this like in a

26:51

self-service motion, right? Like with

26:52

graphs. And what we're finding is that

26:55

there is a subset of people that are

26:56

like incredibly confident with and know

26:59

how to do this already. And maybe

27:00

they're running it locally and like

27:01

that's actually where we're finding this

27:03

opportunity right now. I'm curious your

27:05

thoughts here. It's basically the

27:06

infrastructure to deploy marketing

27:08

agents. Cuz it's like everybody's

27:10

monkey-patching this together right now

27:11

with like, "Okay, I I've got some data

27:13

stream. Maybe I got access to like, you

27:16

know, I I I I

27:17

Yeah. I begged my CTO to get access to

27:20

the data warehouse.

27:21

Um and uh I'm now like deploying random

27:24

agents to railway, but I have no

27:26

observability and my consistency.

27:28

Um and so basically what we realized is

27:30

like, "Okay, can we just unify that

27:32

where we're just going to give you

27:33

literally a CLI you can give your agent

27:35

and you're like, 'Go and spin up this

27:38

workflow I just made locally, put it

27:40

into a cloud with a live data stream,

27:42

and it can go do that, right?'" Um but

27:45

anyways, um first off, curious to get

27:47

your thoughts there in a second, but I I

27:49

think just to come back to that that

27:51

core idea, like the expertise is still

27:53

the most valuable part. Especially now

27:55

with like everybody like trying uh

27:57

competing, right? This is I think this

27:59

idea is related to what we just talked

28:00

about where all all of the marketing

28:02

channels are becoming more hard to

28:04

compete on because everybody can just do

28:06

the average route, right? Like so how do

28:08

you have differentiation? How do you

28:10

stand out? Um that you you it's becoming

28:13

more and more valuable. Like if you

28:15

really are good, you know, top 1% direct

28:18

response copywriter and you know how to

28:20

get um you know, uh an AI to write in

28:24

this in your style for for example email

28:27

or cold email or, you know, even scripts

28:29

for for ads, right? The the likelihood

28:32

that you're going to be able to

28:33

outcompete with the exact same tools is

28:35

way higher, right? So I think that that

28:37

expertise like there was this moment

28:38

where it's like, "Oh, you could just

28:39

throw anything up because

28:42

you know, it was the zero to one, but

28:44

we're past that now. It's now moving

28:46

into, "Okay, um it's the one to one to

28:49

100, which is way way harder because

28:51

it's just it's no longer blue ocean.

28:52

Like there's way more competition there.

28:54

So, but anyways, I'm curious to hear

28:56

your thoughts on like, you know, where

28:57

we see this is where the market's all

28:58

going and

29:00

that like everybody is trying to deploy

29:02

marketing agents. I swear to God, a new

29:04

one pops up every day and it's like

29:06

whack-a-mole at this point and it's

29:07

hilarious to me and it's like you look

29:09

under the hood and you're like, holy

29:10

[ __ ] you're just spamming Reddit

29:12

threads.

29:13

>> [laughter]

29:13

>> That is the software.

29:15

Um in my, you know, in my view, like

29:18

what what is an actual agent? It's like,

29:20

okay, some type of like job to be done

29:23

and you have like a thinking loop that's

29:25

within it with like an LLM making

29:26

decisions. Um and then you have a data

29:28

stream,

29:29

you know, that's basically coming back

29:31

to the agent so that it can understand

29:32

the outcomes based off of the actions.

29:34

And that's just like it's very it's very

29:36

simple, right? Like

29:37

I'm not trying to create God and put him

29:39

in a box and like have him have total

29:41

like control like I don't really want an

29:43

agent to make decisions and say, I want

29:45

it to run a process and I think that the

29:48

thing that we're realizing is like the

29:49

infrastructure for that is kind of hard

29:51

to like get built quickly. You can do

29:54

it. Like for example, like you can build

29:56

a data pipeline or warehouse and you

29:58

know, have a server that you deploy

30:00

agents to. It's like you can do it with

30:01

Airbyte with ClickHouse and then

30:05

you could have, you know, your agents

30:06

running a railway, but that's still like

30:08

engineer it's just hard. It's just like

30:10

we've tried to do it.

30:11

>> [laughter]

30:11

>> And maybe this gets easier as like

30:13

frontier models go along and and you

30:15

know, we're totally wrong, but our

30:16

thesis is that that like everybody's

30:18

going to want to go to code immediately.

30:20

Like anybody that is building some UI to

30:23

like connect together sequences. Like

30:25

I've seen this with all of these

30:27

marketing

30:28

like engineering startups. It's like

30:30

it's like this is just a Zapier clone.

30:32

Like you're you're ending up in the same

30:33

space. That's not how this is going to

30:35

work. Like how the the best are

30:36

performing right now that are like, you

30:38

know, I I talk to heads of growth at

30:40

companies like every week. Like they're

30:42

all running their systems out of cloud

30:43

code and the challenge that they're

30:45

facing is they're like they're trying to

30:46

deploy that into like something that can

30:48

either run on an hourly or a daily

30:49

cadence, but I'm curious just to get

30:51

your thoughts on like what you you saw,

30:53

you know, or what you're seeing on the

30:54

front lines, if that feels like it's in

30:56

the right direction or if you're like

30:57

no, this is like, you know, this

30:59

something entirely different. Is it Is

31:01

it going in a two different place?

31:02

>> Um yeah, so a couple things. So first of

31:05

all, like the marketing agents that spam

31:08

Reddit for you, that [ __ ] is not going

31:11

to last. Like that that

31:13

door is going to be closing very

31:15

quickly.

31:16

And there was some news about Reddit

31:18

possibly not renewing their contract

31:20

with Google that allows Google to scrape

31:22

them for AI overviews, which is going to

31:25

screw up a lot of people.

31:27

And I don't know, I don't care if they

31:28

do or not, but

31:30

if that's what your product is built on,

31:32

you need a you need to find God pretty

31:34

much.

31:35

>> [laughter]

31:37

>> Um

31:38

as far as like

31:39

what the best heads of growth are doing

31:41

and stuff like this, um I don't know if

31:43

this answers your question, but

31:44

basically like the way that I was I was

31:46

running a lot of my processes was out of

31:49

Vercel with just the code that we we

31:52

deployed. And so like

31:55

you can almost imagine a future where

31:57

like instead of,

31:59

you know, where your directory of vibe

32:01

coded slop revenue agents are is like in

32:04

Vercel and instead of logging into like

32:06

Salesforce every morning, you're like

32:07

logging into Vercel to like make sure

32:09

that none of them errored out overnight.

32:11

And you know, you click on the little

32:13

Vercel tab and it opens the app and you

32:15

go to the the dashboard and you know,

32:17

you see what's going on. Um

32:20

I I don't see people like

32:24

buying more apps. Like it just Think

32:27

about like some of the most successful

32:29

things that I did

32:31

AirOps was around like job changes.

32:33

Um and it was 100% vibe coded. Like

32:35

could I have gone and bought User Gems

32:37

or something? Like, probably, yeah. But,

32:39

there's like so many little nuances

32:40

around like account ownership and, you

32:42

know, all these First of all,

32:44

vibe coding a job changing bot, like

32:47

that automatically sequence people and

32:48

enrich stuff, like was like way harder

32:50

than I felt like it should have been.

32:51

Like, maybe I'm an idiot or something,

32:53

but it seemed so simple. And, um I

32:55

remember one time I got into like a uh

32:57

fight on LinkedIn with the CTO of

32:59

UserGems because I was like joking

33:00

around about how anybody could vibe code

33:02

UserGems.

33:03

I don't regret it. I wasn't wrong, but I

33:06

will say if you are listening to this,

33:08

you are right. It was not easy.

33:10

Okay, I admit it.

33:12

>> [laughter]

33:13

>> You can see.

33:14

Tell me how you did that, just so the

33:15

audience gets some nugget there. So,

33:17

what just for context for everybody

33:19

who's listening as well, like what what

33:22

uh Ben is talking about is basically uh

33:24

like com- person switches to a new role

33:26

and you're trying to as quickly as you

33:28

can

33:30

get to them basically with your offer

33:31

cuz like a job change is typically a

33:33

high signal that they're going to try to

33:35

implement some type of new solution at

33:36

the company that they're at. Uh tell me

33:38

about uh like what was it what was the

33:40

actual tactical like what did you use in

33:41

the stack to do this?

33:43

>> Yeah, so uh we used Common Room for the

33:45

actual signal. Um and

33:49

the Common Room folks, I've had

33:50

discussions with their product team, so

33:51

this is they're not going to be mad at

33:53

me if I say this, but like Common Room

33:54

is great is a great tool, but there's a

33:56

lot of shortfalls for it. I I probably

33:58

would have used something else to be

33:59

totally honest if uh if we didn't

34:01

already have Common Room. Um but,

34:04

they're trying to do great things over

34:05

there, so

34:07

hopefully they do it. But, um

34:09

uh all the all you need is a webhook

34:11

that uh you need something hook up to

34:13

your CRM, so obviously it has

34:14

everybody's LinkedIn URLs. Um then you

34:17

need a database uh or a

34:19

you know, enrichment provider that's

34:21

going to tell you that they changed

34:22

jobs. Um I mean, that it sounds really

34:25

simple, but the the problem was like all

34:28

of the stuff downstream from that, like

34:29

all of the the rules, like did were did

34:31

they have an open up? Are they a

34:33

customer? Because I had two different

34:34

sequences. I had former customers and

34:36

then former prospects. Former prospects

34:38

is really kind of overstating the matter

34:39

because they may not know anything about

34:40

us.

34:41

Um, and

34:43

all I wanted to do was like in enroll

34:45

them in a one-month sequence. The the

34:47

hard part like like the part where like

34:48

complexity started getting in was like

34:50

account ownership. Um, you know, if an

34:53

SDR I felt like if an SDR had helped

34:56

book the meeting that the original

34:57

customer came from, like they should get

35:00

the downstream of that, but that's not

35:01

really how we wanted to do it. Um, just

35:03

making sure that if the account wasn't

35:05

because this was the other problem,

35:06

right? We have an account scoring model.

35:08

If an account's not tiered, we're not

35:10

going to work the account. And so like

35:11

if it was a new account that wasn't in

35:13

HubSpot, I had to send it to a clay

35:14

table to get scored and then I had to

35:16

like make a webhook that would like wait

35:18

for 5 minutes for it to like either show

35:20

up in HubSpot or not and then I if you

35:22

know, then I had to like route it to a

35:23

different person based on the tearing

35:25

and like all this [ __ ] Um, and so

35:28

that's why people buy UserGems, I guess.

35:30

But uh, I think that it's probably

35:32

explains the the whole thing.

35:34

>> Totally.

35:35

>> it would go into a one-month sequence.

35:36

That's that that was the end of it. Like

35:37

it goes into a sequence. That's pretty

35:39

That's pretty simple.

35:40

>> Totally. Uh, I got some money that is

35:43

like the very midwit version of this,

35:45

but it's basically just like their

35:47

LinkedIn profile.

35:49

Um, you just all of the you know,

35:52

getting your ICP, you have them in a

35:53

database. Um,

35:55

and daily you just use an Appify to

35:57

scrape it

35:58

>> [laughter]

36:01

>> or weekly you can do this like go to

36:03

each profile and pull out the job

36:05

listings and then just have an LLM

36:06

that's like a super cheap LLM be like is

36:09

there a new job role on here from last

36:12

time? And that is a way to get signal.

36:14

>> What kind of What kind of scale does

36:16

that work on though? Like how expensive

36:17

is that?

36:18

>> You can get profiles for like like

36:21

fractions of a penny. So imagine if

36:23

you're doing 10,000 like it would be

36:25

cheaper than what you would pay one of

36:27

these signal companies for, for sure.

36:29

>> Yeah, I mean we had like few hundred K

36:31

contacts in HubSpot at least, probably

36:34

more than that. Like the week before I

36:35

left I had like 50,000 more contacts. So

36:38

we were well on our way to

36:39

having a lot, but

36:42

I don't know. I mean I think it would

36:43

even be at that cost. I mean depends on

36:45

how the frequency you want, but like I I

36:47

mean you could do this weekly, you could

36:48

do this

36:50

uh

36:50

you could do this daily depending on

36:51

your list size. It just depends on like

36:53

I mean I don't know what a contract for

36:55

a common room looks like um on a yearly

36:57

cadence, but like I I again

36:59

it's just that's that's all they're

37:00

doing, right? It's just

37:03

Well, we're seeing like is the LinkedIn

37:04

did they change, right? So anyway. There

37:07

was a bunch of other stuff we were doing

37:08

with Common Room. That's the ours used

37:10

to do.

37:10

>> for sure, for sure, for sure. It was

37:12

just what I had at my disposal. But

37:13

yeah, there's probably a mid-web version

37:14

of that that would have saved me time.

37:16

But like now I did it and I'm like next

37:17

time I'm doing this I'm [ __ ] doing

37:18

the mid-web version. Like this [ __ ] was

37:20

too complicated.

37:21

>> For sure, for sure. So

37:23

Um okay, man. What What am I not asking

37:26

you about that I should be? Um like

37:28

we've we've been here for a minute. Like

37:30

there's so much I feel like changing in

37:32

this category. Also like for the

37:34

uninitiated like GTM engineering, what

37:36

is How do you think about it? What is

37:37

your definition of that? I feel like

37:39

it's just like this thrown around term

37:41

and it started out as like you know,

37:43

people doing waterfall enrichments.

37:45

>> [laughter]

37:45

>> That was like the origin and now it's

37:47

evolved into like nah, man. I'm writing

37:49

like custom software and you when you

37:51

hire me I literally have agents I bring

37:53

with me to the team. What do you

37:55

actually view it as and then what am I

37:57

not asking you that I should be?

37:59

>> Um well well you're not asking me what

38:01

kind of job I'm looking for cuz I'm

38:03

looking for a job.

38:04

>> [laughter]

38:04

>> We can deal with that later, but um

38:06

uh

38:07

yeah, for to me GTM engineering is a set

38:10

of principles around

38:13

applying software solutions to sales

38:15

problems and

38:17

a lot of people are going to be like,

38:18

well, you know sales isn't a product

38:20

problem. And of course I agree sales is

38:22

not a product problem. It's not that

38:23

it's why I like you see like engineering

38:25

founders really struggle and why they

38:27

make bad first sales hires and why they

38:29

want to hire a VP of sales for 350k a

38:32

year who like does nothing for them and

38:33

things like this.

38:35

Um to me it's about like finding

38:38

uh friction points in like sales

38:40

processes. And this could be anything

38:42

from like revenue operations, marketing,

38:44

sales development is kind of like where

38:45

my like specialty lies, like finding

38:48

friction in those processes and like

38:49

working with like SDR teams, uh

38:51

marketing teams to like build lead

38:53

magnets, things like that. Um and then

38:55

like utilizing and measuring all that

38:57

stuff. But um

38:59

it it is fundamentally different. I

39:01

think the best way to explain it is why

39:03

it would be fundamentally different from

39:04

like revenue operations cuz first of

39:06

all, nobody's asking me about finance

39:07

stuff. Like nobody's asking me to

39:09

reconcile billing. Like you don't want

39:11

to ask me to do that. Like cuz I

39:13

probably wouldn't do a good job. But um

39:15

but it is interesting because I actually

39:17

saw a job listing for a post-sales GTM

39:20

engineer and I was like, I've never

39:22

heard this. What does this mean? And

39:23

when I went onto the listing, somebody

39:25

had, you know, sent it to me.

39:27

Um it was around like onboarding, CPQ,

39:30

finance, billing. And so really it felt

39:32

more like a bizops person with like a

39:33

cursor subscription. But I was like,

39:35

that's actually really cool. That would

39:37

be really cool application of these

39:39

principles

39:40

um and like ways of working that uh are

39:43

GTM engineering adjacent. Um

39:46

I don't think GTM engineering is just

39:47

about spamming people at this point,

39:49

like whenever I would run an email, um I

39:52

mean, we would use email bison, but like

39:54

all of the inboxes and stuff, you know,

39:56

I have a provider for that, like and um

39:59

there's a lot of things within email

40:00

deliverability that require like custom

40:02

coding, like inbox rotation and like

40:05

automatically retagging an inbox that's

40:07

like burnt to re be warmed up for, you

40:10

know, the next 3 weeks and things like

40:11

this. But um I know that's kind of like

40:14

a a long-winded to It's it's not

40:16

marketing exactly because like typically

40:19

I'm not doing like creative or campaigns

40:21

or or ads for the most part. Like

40:23

I did uh

40:25

add people to add audiences based on

40:27

like certain things, but that's um just

40:30

like one little thing. I don't do too

40:32

much of in ads. Um what I think uh

40:36

if you're looking for a GTM engineer,

40:37

you should hire me. No, I'm just

40:38

kidding. Um but uh if you're looking for

40:40

a GTM engineer, like I think you should

40:42

find somebody who has a real sales

40:44

background and not just a uh computer

40:46

science background because to me it's

40:47

more about the jobs to be done and

40:49

understanding what actually closes deals

40:51

and drives the revenue and like building

40:54

things in service of that as opposed to

40:56

like, you know,

40:58

a bunch of dopamine hit like workflows

41:00

that like sound cool and like I talked

41:01

to one guy who had hired a GTM engineer,

41:04

quote-unquote GTM engineer, and I was

41:06

like, "Okay, [snorts] well, what

41:07

happened?" Cuz they're like, "We let him

41:08

go." Or something. And he's like, "Well,

41:09

they just made like a bunch of

41:10

dashboards. Like they vibe coded some

41:12

dashboards." And I'm like, "Okay, well,

41:15

that's not really driving the business

41:17

forward, but um

41:19

okay." So, yeah, there's a lot There's a

41:21

lot of things to look out for. I know

41:22

there's some recruiters out there who

41:23

help people find GTM engineers and like

41:26

maybe can help you vet them better. So,

41:28

that's

41:29

that's what I'd probably recommend if

41:30

you're looking for somebody like that.

41:32

>> No, totally. I think that it's it's it's

41:35

your point. It's like this person is

41:38

They're I like what you described. It's

41:40

like it's better for them to come from

41:41

the sales rep side of the spectrum and

41:43

then move into this um rather than the

41:45

engineering side and move into it, you

41:47

know, from that that side. Um

41:49

it can be possible and like depending on

41:51

like the complicate, you know, what

41:52

you're doing. Like I

41:54

met a

41:55

>> [laughter]

41:56

[snorts]

41:57

>> Absolutely. Absolutely. But I think for

41:59

the general public when they think about

42:00

like what is the actual like

42:01

implementation of this hire look like in

42:03

the company, it's to your point. It's

42:05

like it's in service of the sales team,

42:07

right? Like it is not uh

42:09

you know, you're this person drives

42:11

revenue for the company and has like

42:12

directly and has a lever to pull that.

42:14

Like I think what you said is really

42:16

interesting to you on the dashboard

42:17

side. Like this isn't like a person that

42:20

is

42:21

you know, you're not reporting on the

42:22

activities. You are initiating the

42:24

activities and then reporting on them,

42:26

right?

42:27

That's like you're not an analyst. This

42:28

isn't an analyst role. This is like

42:30

somebody that goes and actually does

42:31

things. So

42:32

>> Yeah, absolutely. And they should hold a

42:34

bag. I think GTM engineers should be

42:36

responsible for a quota of some kind.

42:38

Whatever that is. SQLs pipe blind.

42:41

Whatever.

42:42

>> I think that's great and be measured to

42:43

that and maybe have bonus structures

42:44

that's associated that I get it. This is

42:46

a sales hire, right? And it is a part of

42:48

the sales organization as a function. Um

42:51

I'm curious your thoughts on this. I

42:52

talked to it I had it another person on

42:54

the podcast yesterday.

42:56

They'll be like right before your

42:57

episode comes out.

42:59

He called the email guy talking about

43:02

he's like I'm starting to think about

43:03

cold email now was it like one-to-one

43:05

marketing at scale.

43:07

>> [laughter]

43:08

>> Um and I I really found this like a very

43:10

interesting and unique idea of like oh,

43:13

you can now research people so deeply

43:15

and like have like an understanding of

43:16

the individual like at a such a granular

43:18

level that like Wait, and for example,

43:21

the example he used was were they're

43:23

cold emailing these different agency

43:25

businesses and maybe they have different

43:26

specialties like cold calling or cold

43:29

emailing or

43:30

you know, LinkedIn DMs etc. And so from

43:33

that they can basically like craft this

43:35

like pitch, you know, because their

43:36

product you know, it serves all of those

43:38

individuals. But rather than a generic

43:40

it can be specific to them. You know,

43:41

based off of their website, based off of

43:43

their LinkedIn post history, you know,

43:45

them talking about the business etc. And

43:47

then from that it's like an email he's

43:49

like I don't even care if they respond.

43:50

I just want them to see this.

43:52

>> [laughter]

43:53

>> And like we know that that impression

43:55

like is going to be a high value

43:57

impression because it's like a

43:58

one-to-one like you know,

44:01

basically it's a one-to-one ad is like

44:02

how he was thinking about it. I thought

44:03

that was really interesting. I'm curious

44:05

your thoughts there and like have you

44:06

seen at you know, any experimentation

44:08

with that or any, you know, any data

44:10

that you're sitting on, you know,

44:12

anecdotally that that feels related to

44:14

that idea?

44:15

>> Yeah, um so first thing, um I do also

44:18

view cold email as a one-to-one ads

44:20

channel. Um I think that's the best way

44:22

to think about it. Obviously, we want

44:24

people to respond. We want people to

44:25

say, "Send me the booking link." That's

44:27

not But here's the thing about email,

44:29

and I think this probably is obvious

44:31

when you really think about it, but I

44:32

don't think

44:33

I think um

44:34

the way that like cold email has been

44:36

treated is like we used to think of it

44:38

as a marketing channel, and then to some

44:40

people, maybe it's just me, I don't

44:42

know, we then started to think of it as

44:43

like a sales channel where we're like,

44:44

"Oh, if they don't respond to the email

44:46

and book a meeting, then it's not

44:47

working." And now after working at

44:49

AirOps and being exposed to like a more

44:51

traditional marketing organization, I've

44:52

sort of like shifted back to thinking

44:54

about it as a traditional marketing

44:55

channel,

44:56

um

44:57

because like I do have data, hard data,

45:00

that showed like uh heavy influence on

45:02

some of the larger deals that we booked.

45:04

Um where I had this like a it's in my uh

45:08

portfolio if anybody goes to see it, but

45:09

like um

45:11

this dashboard that showed like all of

45:13

the deals that we'd booked, and like it

45:14

would manually allow me to attribute it

45:16

to outbound or not based on like do I

45:18

think that we actually had some effect?

45:20

Did they reply to an email?

45:22

Uh did we email the person who came

45:24

inbound? Things like that. [snorts] Um

45:26

and so there was an influence whether or

45:27

not they responded to it. And the other

45:29

thing is like think about like this,

45:30

like what hap- like this happens to me

45:32

all the time, and I do this, right? Like

45:33

somebody will send me an email, it's not

45:35

really relevant for me, but I'm like,

45:36

"Oh, you know what? The other guy like

45:37

in RevOps or the SDR leader might be

45:39

interested in this." I forwarded it to

45:40

them. Like there were Gong transcripts,

45:43

speaking of Gong transcripts, this was

45:45

actually useful for me, um

45:46

in this deal attribution like uh app

45:49

that I built.

45:50

I would have it analyze the Gong call to

45:51

see if they said how they heard about

45:53

us, and I would use that to like

45:54

attribute it to the case. It's amazing.

45:56

I would use it to attribute deals to

45:57

outbound because like there was a couple

45:59

of examples where somebody was like,

46:00

"Oh, well, my boss forwarded me this

46:01

email and told me to like check you guys

46:03

out." So, nobody responded to anything.

46:05

They [ __ ] came in through a branded

46:07

search, but like they told us on the

46:10

call and they probably didn't even in

46:11

the like we have a how did you hear

46:12

about us form on our like our demo

46:13

booking. They would never [ __ ] say

46:15

email.

46:16

>> [laughter]

46:16

>> I so I don't know why people are so

46:18

reticent to just tell us how they heard

46:20

about them. Um but then they'd get on a

46:22

call and they'd be like, "My boss

46:23

forwarded me your cold email." So,

46:26

I can't figure it out. You know,

46:28

attribution is not a solved problem. So,

46:31

it's something everybody else deals

46:32

with. So, yeah, that's that's my spiel

46:34

on that.

46:35

>> No, man. I I I stand so firmly behind

46:38

this. I did this test forever ago. I I

46:40

said this in the last pod, so sorry if

46:42

you're hearing this again, but we

46:44

basically like cold emailed a bunch of

46:46

people with no intention of responses

46:48

and then we just looked at the emails to

46:49

see if they went and signed up for the

46:50

product and we saw

46:52

we saw a conversion rate that was

46:54

comparable to like what we saw with like

46:55

ad traffic.

46:57

>> [laughter]

46:58

>> From like, you know, ad traffic to sign

47:00

up and I was just over there and I was

47:01

thinking to myself, I'm like,

47:03

"This is just literally a marketing

47:04

channel if you think about it like

47:05

this." And so it's like, "How cheaply

47:07

can I send it scale?" It's like and

47:09

actually get it to land, actually get it

47:10

to be open. So,

47:11

>> Dude, think about the cost per click

47:13

versus the cost of somebody reading your

47:15

email.

47:16

>> Totally.

47:17

>> Like

47:17

it's cold email is basically [ __ ]

47:20

free like when you think about it like

47:21

that.

47:22

>> Yep. And so then it's like, "How do I

47:24

stand out?" And that comes to the

47:25

copywriting piece, but

47:27

All right, brother. We're coming up on

47:29

time. Thank you so much for coming on

47:31

today. I cosign that you should go sign

47:33

go hire Ben if you need a GTM engineer.

47:35

He's exceptional at what he does. I

47:37

respect your work deeply. Also include

47:39

link to the portfolio below and anything

47:41

else that you want, but man, if they if

47:43

you want to reach out to you, where

47:44

where should they where should they find

47:46

you?

47:47

>> Awesome. So, I have a website. It's a

47:48

benyamin.ai b e n y a m i n.ai. You can

47:53

check me out there. It's got links to my

47:54

LinkedIn, my uh account, my YouTube, um

47:58

all my other podcast appearances and

47:59

stuff. So, a bunch of like long-form

48:02

articles if you guys want to go

48:04

pick my brain. I wrote all these

48:05

articles cuz people would always ask me

48:06

things and I got [ __ ] sick of like

48:08

answering their questions. So, I'm just

48:09

going to write an article about this.

48:10

[laughter]

48:11

So, anyway, that's where you should go

48:12

check me out.

48:13

>> Amazing. Awesome. We'll include that all

48:15

in the show notes. Thanks for coming on,

48:17

man. We'll have you back in like 6

48:18

months and tell us the state of the

48:19

union, what's going on at GTM

48:21

Engineering, and what you're seeing on

48:22

the front lines. So,

48:23

>> Dude, we're all going to be unemployed

48:24

by then.

48:25

>> But,

48:25

>> [laughter]

48:27

>> Yeah, we're going to have the Chinese

48:28

model ship and it's just going to it's

48:30

going to replace every person. So,

48:32

>> We can talk about our woodworking

48:33

projects that we're doing now that we've

48:35

been replaced by the robots.

48:37

>> Exactly. Exactly. I've just gotten into

48:39

gardening. I'm happy to just like

48:40

continue only doing that if this my job

48:43

basically disappears. So,

48:45

>> [laughter]

48:46

>> All right, brother. Yeah, thanks for

48:47

coming on. We'll talk to you soon.

48:49

>> Yep, talk soon.

Interactive Summary

This episode explores the emerging field of GTM (Go-To-Market) engineering, where professionals use software, APIs, and custom code to build automated systems, workflows, and pipelines that drive company growth. The host and his guest, Ben, discuss why robust API access is now a primary buying criterion for software, why they advocate for writing custom code over using low-code tools like Zapier, and why maintaining a 'GitHub portfolio' of one's work is essential for career success in this role. The conversation also covers strategies for effective cold outreach, the importance of proprietary data, and the role of GTM engineers as revenue-driving assets within a sales organization.

Suggested questions

4 ready-made prompts