Adam Tuttle & Ian Faison

Making Good Decisions with Bad Data


On this episode, Renee discusses the importance of knowing the key players in your organization, going from zero to one in a tech start-up, and being right vs being a good partner.



0:00

Welcome to Rise of RevOps. I'm Ian Faizan, CEO of CastMean Studios, and today

0:10

we are

0:10

joined by special guest Adam, how are you?

0:12

I'm doing great. Thank you so much.

0:14

Excited to have you on the show, excited to chat about active campaign, we're a

0:19

customer

0:19

here at CastMean. So it's fun to hear the inner workings of how you all go to

0:23

market.

0:24

And we have a bunch of podcasts that we do that have newsletters and use an

0:29

active

0:29

campaign stuff. So it's fun digging in. And obviously, of course, we're going

0:33

to talk

0:33

about all of your rev-ups. So let's get into it. Tell me about your background.

0:38

How do

0:38

you first get into rev-ups?

0:41

I was dragged in, to be honest with you. So it was fun. I've been with active

0:46

campaign

0:46

for about 10 years. I started in a support role. Did that very early days when

0:52

we were

0:53

like sub 10 employees. So we did a lot of everything and then started a sales

0:58

team in

0:59

2015, opened an international office overseas in Sydney, Australia. And when I

1:04

was coming

1:05

back from that, I realized I didn't want to be a director of sales anymore. So

1:09

I had

1:09

this kind of existential crisis where I was looking at my long-term goals. Like

1:15

, where

1:15

do I want to be in 10 years? And I realized there's a big gap in my skill set.

1:20

And that

1:21

was the operation side of the house. I had been doing ops kind of like under

1:25

the radar

1:26

for a while, but I didn't really know anything about it. And so when I came

1:30

back, I just asked,

1:31

I said, I really don't want to lead a sales team anymore. I want to get into

1:34

operations.

1:35

And so I did that. And then I was doing a lot of side work for our former vice

1:42

president

1:43

of rev-ups at active campaign. And she basically just secured my time. She said

1:48

, 40% of your

1:49

time is mine, no matter what. And then eventually I went full time with her.

1:53

And so that was

1:54

at the start of this last year, actually. So it's been a really fun journey,

1:57

though.

1:57

It's an awesome field to be in right now. It's growing. And I think there's

2:02

just a tremendous

2:03

amount of opportunity. Truly it is on the rise. Hence the podcast name. So what

2:08

's your definition

2:09

of rev-ups? Yeah, I think that rev-ups is going to change depending on the work

2:15

, right?

2:16

And that's something that I've been learning a lot over the last few months is

2:20

I realized

2:20

once I got into rev-ups officially that I didn't know what it actually did. And

2:24

so I was like,

2:24

oh, no, I need to figure this out. And then I realized that everyone does it a

2:28

little

2:28

bit differently. But at the end of it, I think that there's really a core piece

2:34

of that.

2:35

And that is to give a sales org, success marketing, whatever it might be,

2:39

whatever

2:40

orgs that you support, a mechanism to build a foundation upon and have success,

2:46

right?

2:47

And that's the pieces. What you're doing is you're laying a foundation for the

2:52

organization

2:53

or the organizations that you support to be successful in their day-to-day jobs

2:57

. And

2:57

that's it. And tell us a little bit about Active Campaign for our listeners who

3:02

don't

3:02

know. Yeah. So Active Campaign has been around for almost 20 years, which is

3:09

pretty wild.

3:10

And one of the things that we've grown from is we started as just an email

3:14

marketing platform.

3:15

But in the last few years, we've really pivoted to what we call a customer

3:19

experience platform.

3:21

And so what we are is a really simple to use platform that embodies email

3:26

marketing,

3:27

automations, CRM, and kind of takes all of those things that makes them work

3:31

together

3:32

to help you as a small business or large business, whatever it is, to give your

3:36

customer a great

3:37

experience to the entire funnel or journey that they're on with you.

3:43

Tell me about how your RevOps team is organized and what approach do you kind

3:47

of take looking

3:48

at RevOps and how it fits in. Yeah. So RevOps is only a couple years old with

3:54

an Active

3:55

Campaign, as it is within many companies, right? It's a kind of rising star in

4:00

the operations

4:01

community. And what we've decided is that we're going to build our RevOps org,

4:07

especially

4:08

on kind of four main tenants or pillars. And those are really simple. It's

4:13

people, policies,

4:15

processes, and systems. And so what we try to do is look at everything that we

4:21

do to

4:21

drive success within the teams that we support. We want to focus on exactly

4:26

those things,

4:27

the people, the policies, the processes and the systems. And if we can do that,

4:32

or if we

4:32

start to deviate outside of that, we know that we need to pull it back in. So

4:35

it acts

4:36

as a kind of a foundation for us to always make sure that we're pointing in the

4:40

right

4:40

direction as well. How do you think you all differ from like other RevOps teams

4:45

or what's

4:46

maybe unique about your org or active campaign? So historically, Active

4:50

Campaign has had RevOps

4:52

really under the sales org and some under success. A lot of RevOps orgs are a

4:59

little bit broader

5:00

than that. So they might do sales, success, marketing, even support at times

5:06

and sales.

5:08

And so what we have focused on historically was we kind of were birthed out of

5:12

the concept

5:12

of a sales ops org. And then we started expanding that a little bit. And I

5:17

think what we're

5:17

seeing now is the opportunity to say, okay, hold on, how do we centralize ops a

5:21

little

5:21

bit better with an active campaign? Is there opportunity for us to say that Rev

5:27

Ops is maybe

5:27

a bigger part of the puzzle as we try to solve that? I think what makes us

5:32

unique is, you

5:33

know, again, we were a pretty small team to start with and trying to really

5:38

make sure

5:38

that we had our processes nailed down and things like that. Again, a lot of

5:43

businesses

5:44

are in this journey of solving for what is RevOps to them. But that's

5:50

definitely been

5:50

like the piece for us that we focused on is building that out and making it

5:55

successful

5:56

within our business.

5:58

Yeah, it's funny how it usually grows from one area, whether it's marketing or

6:02

sales

6:02

or probably at least common being CS. And then it sort of starts merging into

6:07

that kind

6:08

of combo thing. I'm curious, you know, when it has that initial DNA and you

6:13

were in sales

6:14

and it has like a sales ops DNA, bringing those marketing and success kind of

6:19

pieces.

6:20

How did you go about doing that? Did you kind of like, you know, fold in some

6:23

marketing

6:23

folks into the conversation or how did you do that?

6:26

I think what has been really outstanding is in the last year, the marketing

6:33

teams and

6:34

the RevOps teams have been very, very intentional about saying, hey, there's a

6:39

gap between our

6:40

relationships and we can't operate and continue to be successful together if we

6:45

don't fully

6:46

support each other. And so there has just been iteration after iteration after

6:53

iteration

6:54

of really taking the time to make sure that all the stakeholders are brought

6:59

into the

7:00

conversations that we're having, that we're not planning any changes to how we

7:04

function

7:04

or work without at least notifying like someone in marketing ops at a minimum,

7:10

but more likely

7:11

actually bringing them into our process. And so it's all about that intention

7:16

ality to

7:17

say, hey, yes, we have to do what we have to do. We have our mission, you have

7:21

your

7:21

mission, right? We all have different projects that we work on. But realizing

7:24

how much those

7:25

projects actually probably overlap if we allow them to. And then just again,

7:30

like I said,

7:30

being really intentional is to say, hey, you know, marketing ops director, you

7:35

are a stakeholder

7:36

in my project on RevOps. I'm bringing you into every conversation on it. I'm

7:40

going to allow

7:40

you to have a voice. I will be cognizant of what you need to be successful from

7:45

your

7:45

side to ensure that we work together and create a really unified approach. And

7:50

it's

7:51

been really awesome to see that take place and that relationship build to a

7:55

point where

7:56

I'm like, I feel that our ops teams are more aligned than they've ever been

8:02

before. And

8:03

that really we're just getting started, which has been really exciting.

8:07

Let's get into some of what of those things are in our next segment. Rev

8:12

obstacles. We

8:14

talk about the two parts of RevOps. What's the hardest rev ops problem you

8:19

faced in the

8:19

last six months? I've been chewing on this one, trying to figure out what

8:25

actually is

8:26

the hardest problem. One of the things that is maybe been a unique challenge

8:32

for us, right,

8:33

is that active campaign has a CRM. And so we use that for our inbound teams and

8:39

we have

8:39

used that for our inbound teams for years. But for a small point in history of

8:45

about

8:45

two to three years, our outbound teams use Salesforce. And the reason for that

8:51

was because

8:51

our CRM needed to have some more capability added, some more functionality

8:55

added, to really

8:56

allow us to do outbounding in a cohesive way. And so as the platform's been

9:02

growing and

9:02

changing, it came time to move back. And moving off of a CRM to another CRM is

9:09

often a challenging

9:10

point of view. But also moving off of a CRM into your own CRM when you have

9:17

direct access

9:18

to the engineering teams and things like that. And you have to now manage how

9:23

are we going

9:24

to actually take this move and make it successful. That's been a humongous

9:29

thing that we've been

9:30

working on over the last six to eight months. We're kind of on the tail end of

9:35

it now.

9:36

But there's definitely some big challenges that came along with that. And you

9:41

can imagine

9:42

that it was quite a lengthy process.

9:45

After going through all that, any takeaways of, I mean, obviously that's kind

9:48

of a unique

9:49

scenario with you all because you're, you know, working into your product. But

9:53

we all

9:53

know what it's like to change technologies and kind of bring in those

9:56

stakeholders and

9:57

trying to get kind of that unified data approach. So any takeaways there?

10:01

I think the biggest takeaway for me personally as kind of the person that was

10:06

like leading

10:06

this this project was if I could go back in time and like give myself the

10:13

advice, I would

10:14

have said just spend more time on the planning upfront. Like really, like sure,

10:21

you've got

10:22

a seven month timeline to get this done. Spend four of those months planning

10:27

and spend three

10:27

months implementing. And I think that that we spent a lot of time planning, but

10:31

because

10:32

there was a restricted timeline, our planning was often, you know, we laid the

10:37

foundation

10:38

and then we were building upon that as we were going. And I think that that

10:42

quickly exposed

10:43

some gaps that we didn't realize like in our own product or pieces that we hadn

10:49

't thought

10:50

about just, you know, pain points, right? That are going to be a part of this

10:52

no matter

10:53

what tool you're switching from. So I think this is applicable to anyone in rev

10:57

ops. If

10:58

you're switching from tool A to tool B, it's just ask more questions and really

11:02

get the

11:03

stakeholders involved of, you know, how do you use this function? Is there

11:08

anything that

11:09

we're not doing? Because I think for me, you know, coming out of a sales

11:13

background and

11:14

having working on the system side, you can make assumptions unintentionally

11:20

that, oh,

11:21

I know how dial pad works or I know how X software works. And so I know how we

11:26

use it.

11:27

We dial the numbers and we make calls. But it's like, well, yeah, but how do

11:31

you segment

11:32

those and how do you bucket these and how do you record, you know, the messages

11:36

and

11:36

where do those go? Where's that data stored? And you have to ask those types of

11:41

questions.

11:42

And I think that that was one of the big learning lessons of as we're going

11:45

into more projects,

11:47

it's really getting the stakeholders involved that are like the users very,

11:51

very early and

11:53

taking like deep dive upon deep dive to really understand the ins and outs of

11:59

what makes someone

12:00

successful in their day to day with the current tool. And then how is that

12:05

going to translate

12:06

because there's going to be times where you have to say, this is not important

12:10

to us in

12:11

the future and we're willing to sacrifice that functionality for something else

12:16

. But you need

12:16

to make those decisions intentionally, as opposed to saying like, Oh, shoot, we

12:22

didn't

12:23

think about that and it's too late now. Right. And then you're like kind of

12:27

stuck in a rock

12:28

in a hard place.

12:29

I love that that's really cool. And it's such such great advice. Do you have

12:34

any other

12:35

sort of rev ops problems that little fires, do you even putting out that you

12:39

want to talk

12:39

about at all or? Yeah, I think like one that I would suspect is a very common

12:46

theme amongst

12:48

rev ops leaders. And I've been on a few rev ops training classes and different

12:53

things

12:53

like that. And you kind of start to hear these common themes. And the big one

12:57

is always like

12:57

the data, right? Where is the data? How does it live? What is painting the

13:03

story that you

13:04

need to make a good decision? Right. And I think that what happens sometimes is

13:12

we think

13:12

we're making a good decision, but it's predicated on bad information. And that

13:17

ends up being

13:18

just a bad decision at the end of the day. And so one of those things that you

13:22

're always

13:22

or we're always trying to figure out. And again, I don't think that this is

13:25

like uncommon,

13:27

although it's maybe not talked about is, you know, what is your source of truth

13:33

? What is

13:34

your source of truth? Not only that you align to as rev ops, but maybe

13:38

marketing ops, maybe

13:39

your finance teams, you have to have this this piece where everyone's looking

13:43

at data. But

13:44

if you're you're looking at data and it's just sliced a little bit differently,

13:47

or it's

13:48

maybe the same data, but with just a little bit of a twist that's slightly

13:51

different,

13:52

it's actually different. Right. And that can cause problems. And so those are

13:56

the things

13:57

where we've been actually really going through and being intentional of align

14:01

ing across all

14:02

of the teams and saying, what are the pieces that are feeding our data sets

14:09

across every

14:11

single team that's going to be using it? And then also making sure that as we

14:15

look at

14:16

that, that we're evaluating what is like, what is our source of truth? Because

14:20

other

14:21

thing too is with any company that's growing quickly, somebody built something

14:26

two years

14:26

ago, the data has since changed or the method in getting that data has since

14:31

changed and

14:32

that person's left. So they didn't update the dashboard. Nobody did right. So

14:36

it's just

14:37

making sure like, you know, Hey, if this person leaves, here's all the things

14:41

that they've

14:41

built. And this is what we need to do to make sure that these things are

14:45

accurate at all

14:46

times. So that way we're not making bad decisions unintentionally.

14:49

It was one of the things we thought about for the show of like making a segment

14:52

called

14:53

like data lies. I was like, where's the piece of information that you found

14:57

that actually

14:58

didn't tell the truth? Yeah, I did dig in further or something. But yeah, it's

15:01

a it's

15:02

fun. I mean, we're so data driven now. And that's not a bad thing or so data

15:07

driven.

15:08

But like you said, sometimes you draw the wrong conclusions because of how you

15:13

set up

15:13

the inputs.

15:14

Yeah, and it doesn't take much, right? It can literally just be like one filter

15:21

out of

15:21

10. That's different. And that just changes everything just enough to make a

15:27

huge difference

15:28

for you.

15:30

Any rev oops moments or mistakes that you want to share? I'll go back to what I

15:34

said,

15:35

like, what was one of the biggest problems, right? Again, kind of going back to

15:39

this idea

15:40

of this project of moving changing systems. I think just again, looking back at

15:48

it, had

15:48

I been able to better deep dive and really understand the ins and outs, it

15:53

would have

15:53

made not only the process smoother for me, but it would have made it smoother

15:57

for our

15:58

sales teams. And I think like that's the piece that is like the rev oops is

16:02

sometimes

16:03

you forget that in rev ops, it's not just you or your team that gets affected.

16:09

It's like

16:10

the end sales rep that's like three steps down from you. That is like having a

16:15

really

16:15

tough time because something wasn't communicated to them properly or well. And

16:21

I think these

16:22

things are always going to happen. It's just part of like being in a business

16:25

that's moving

16:26

at an incredible pace. But you have to be honest with yourself and be willing

16:31

at least

16:32

to step back and say, okay, this person's coming to me. And what I used to find

16:36

is I

16:37

would get like kind of offended by it or like put off right where I'd be like,

16:40

you know,

16:40

why are you asking me this? Like I can't control everything. But then I have to

16:44

also

16:45

be willing to step back and say, you know what, you're right, I can't control

16:49

everything.

16:50

But what could I have done differently that would have helped this person not

16:54

have a crap

16:54

day? And so I think like it's it's just being aware that sometimes our actions

16:59

and rev

17:00

ops have ripple effects that can go down pretty deep. And just being willing to

17:05

like, even

17:05

when you have those, be willing to go like talk to someone and say, Hey, I made

17:10

this

17:10

thing, it hurt your team. Let me get on a call with your team, explain why we

17:14

did what

17:15

we did, try to like smooth it over and just be willing to like have those

17:18

relationships

17:19

and those conversations with people. And I found that when I make those

17:23

mistakes or when

17:24

I've had situations that just were like awkward or maybe not handled. Awesome.

17:30

On the first

17:31

try, feeling willing to go have a conversation with a team, an individual, et c

17:36

etera. And

17:37

just be honest, Hey, I totally didn't think about this. Or, you know, we did

17:42

this for

17:43

this reason, but that reason wasn't communicated to you properly. So that was

17:48

the miss. It's

17:48

not that the decision was bad or the implementation was bad. It was just that

17:52

like we we missed

17:53

this final step. And I wanted to own that. And I find that people tend to be

17:57

really receptive

17:57

to that. And you know, very forgiving. Okay, let's get to our next segment, the

18:04

tool shed,

18:04

we're talking tools, spreadsheets, metrics, just like everyone's favorite tool

18:09

qualified,

18:09

no B2B tool shed is complete without qualified go to qualified calm right now

18:15

and check them

18:15

out Adam, what's in your tool shed?

18:19

Well, like I mentioned, we are one of our biggest users in the world, which is

18:25

pretty

18:25

cool. So from the size of our sales team to the amount of automations that we

18:32

use, like

18:33

at any given point, we'll have somewhere between 2500 and 3000 automations

18:39

pumping through our

18:39

account that are live. So we we use our tool on a very high, high level for our

18:45

own purposes.

18:46

So active campaign is the number one tool that we use day in and day, I know

18:51

that obviously,

18:51

of course, like you all use it a ton, but you're also the best at it. So I'm

18:55

curious, like,

18:56

when you say that number of automate, I mean, that's like, that's a huge number

19:00

That's a huge amount. You know, and I know you have like, you know, way over

19:05

100,000

19:05

plus customers and all that sort of stuff. But like, what is in all those autom

19:08

ations?

19:09

You guys are breaking in the bite size chunks. So it's not just rev ops. It's

19:15

our education team

19:16

and our marketing team and our, I mean, we send things to internal people,

19:22

right? It's all of

19:25

those those pieces put together. The thing that I find really fascinating about

19:29

marketing automation

19:31

tools as a whole, right? So let's be agnostic to active campaign for just a

19:35

second is that a lot

19:37

of users, when they hear marketing automation, they think, Oh, that sends email

19:42

. If you were to

19:43

break down, let's just say 2000 automations, and you were to break those down,

19:48

probably only about

19:50

a couple dozen to a couple hundred of them, right? If you so we'll say a higher

19:56

dozen. So one to 200

19:57

send emails, maybe 10%. The rest are actually doing a lot of work behind the

20:03

scenes to manage our data,

20:04

to build funnels for our sales teams, to correct things. When mistakes happen,

20:10

like,

20:11

there's a lot going on behind the scenes. And that is where that number really

20:16

grows,

20:16

because you might have a lot of like micro automations, which is an Adam Tuttle

20:20

original

20:21

coin term, but micro automations that really are there just to do like one very

20:25

simple task,

20:26

like, Oh, this happened at a tag. You know, and so there's a lot of those. And

20:32

when you stack them

20:33

up, then you get thousands. So yeah, what's an example of that that like

20:38

something happened at

20:39

a tag? I'll actually give one. This is like one that I set up in all my

20:43

personal accounts. And I

20:45

always have told customers since back in my sales days to set up right away for

20:49

themselves. So for

20:50

anyone listening, again, doesn't matter the system that you're using, you

20:53

should be doing this.

20:54

One of the big things as you talked about is metrics, right? Data is really

20:59

important.

21:00

Inactive campaign, for instance, what I will do is I set up an automation that

21:04

says any time that

21:05

someone opens an email, update a last open date field to today's date. And I do

21:11

the same thing for

21:12

link clicks. And I usually do the same thing for site visits. So that's a one

21:16

step automation.

21:17

It's literally like someone clicks a link update that link click field to today

21:22

's date.

21:23

What that allows me to do though is say, Oh, hey, I've been sending emails and

21:28

this person,

21:28

I know that on average, I send, let's say, six emails a month. It's been two

21:33

months. This person

21:34

has an open a single one by sending it to the same people over and over and

21:38

over again that

21:39

don't open that's going to hurt my deliverability over time. So I'm going to

21:43

actually push them off

21:44

of the list, or maybe even send them an email that says, Hey, it doesn't seem

21:49

like you're interested

21:49

anymore. I'm going to remove you from my list. But if you want to come back,

21:53

here's a form of how to

21:54

resubscribe. And I can do the same thing for link clicks. Like if you're a

21:58

business that's really

21:59

trying to drive revenue off of link clicks, I can e-commerce store or something

22:03

like that.

22:05

If you have someone that has opened a hundred emails, a hundred out of a

22:08

hundred, but they've

22:10

never clicked on a single link, that's maybe not a high value customer. Maybe

22:14

you need to target

22:15

them through something like Instagram or something else. Like you need to find

22:18

another medium because

22:19

the email piece isn't working for you. And so I think sometimes it's just those

22:22

really simple

22:23

things. It's a trigger and a one action step. It takes about five minutes to

22:27

build,

22:29

less if you know what you're doing. And that can be a pivotal data point for

22:33

your business. So it's

22:35

looking for those things that can really add value off of very simple steps.

22:39

That's awesome.

22:40

Thanks. Yes. So where are the rest of your sales marketing and your CS people

22:46

living and what metrics

22:48

matter to you, what metrics matter to them? We use looker and like snowflake to

22:54

you, you know,

22:55

manage our data and then look at it helps aggregate that and make it pretty.

22:59

That's probably where

23:00

a lot of those teams tend to live. It's taking data out of our tools, whether

23:06

it be, you know,

23:06

we have some homegrown systems that do a lot of our processing for billing and

23:10

different things

23:11

like that and connecting that data to data inside of the CRM. So if I think

23:16

about it from like a

23:18

rev ops perspective, it's looking at things like, okay, how many trials came in

23:24

and how many deals

23:25

did we create out of those trials for our SDR team to try to qualify? If we see

23:30

a huge gap,

23:31

because we know that we only strip out a very few, you know, small amount of

23:36

potential opportunities,

23:37

like, you know, we don't let anything that has an active campaign email address

23:41

go through as like

23:43

an opportunity for a rep to work, right? That doesn't make any sense. So we

23:47

take those out,

23:48

but we should have like a very small margin of, it should be basically the same

23:52

. And so we're always

23:53

looking at things like that, you know, looking at how many, especially on the

23:57

sales side, looking at

23:58

how many people are progressing through the pipeline, like what are our

24:01

qualification rates?

24:02

What are the things that we're doing? And I would say that that actually is

24:05

similar to what marketing

24:07

is doing as well, right? Again, we talked about this relationship with

24:12

marketing ops rev ops,

24:13

at least in the context of active campaign, marketing is the one driving those

24:18

trials.

24:19

But if none of their trials are converting to leads, then that's a problem for

24:24

them as well. It's

24:25

not just something that matters to sales. Where we probably get in the weeds a

24:28

little bit more is

24:29

looking at like the processes that we've built around for our sales teams to do

24:34

, such as,

24:36

hey, we want you to have X amount of touch points before you close loss to deal

24:41

, something like that,

24:42

right? Marketing doesn't so much care about how many touch points we have

24:46

because they've

24:47

trusted us to take care of our processes and manage the sales team. So I think

24:52

that it's very

24:53

relational. It's usually like, you know, it's like just the next step in the

24:57

chain, right? They're

24:58

looking at like, okay, we've generated this many leads. You've got this many

25:02

conversion rates.

25:03

If we're seeing a dip in those conversion rates, they probably will come to

25:07

sales and be like,

25:08

hey, what's going on? Why are you seeing this tip? But they also are looking at

25:12

it from the context

25:12

of, are these leads still relevant? Are we making sure that we're not just

25:16

sending it through garbage,

25:18

right? Like they want to make sure that they're not giving us things that are

25:21

poor leads.

25:22

And so it's that relational communication back and forth of, you know, those

25:25

are the things that

25:26

really matter and how we address them. Gosh, I love it. I mean, that's one of

25:30

those things that

25:31

you could endlessly kind of tinker and fiddle with because, you know, you have,

25:36

hey, this sales rep,

25:37

you know, has sent five straight emails, no response. And marketing is like, I

25:41

don't know,

25:42

they read every one of my marketing emails and they click around a bunch, you

25:44

know, and so you're

25:46

like, right, that person is a very different person from, hey, the sales person

25:51

sent five straight

25:52

emails. And they haven't been reading or clicking on any emails or they haven't

25:56

engaged with the

25:56

website or they haven't done whatever. And like, that's the sort of stuff where

25:59

it's,

25:59

it's so interesting to say like, hey, they still are consuming what we're doing

26:03

, but clearly they

26:04

just ain't ready to buy it. Yeah, I think like when again, you know, when we

26:09

look at like the

26:10

tool shed analogy, right, you kind of often use a lot of the same tools.

26:15

Obviously marketing has

26:17

some that are very special to them, like what they use to drive their SEO or

26:20

different things

26:21

like that. I don't really know anything about that, nor do I get involved in

26:25

that. That's not my

26:26

my field of expertise. Yeah, I don't do anything with the SEO side.

26:31

Oh, yeah, that's just an interesting thing to note that like kind of where you

26:36

set sort of like,

26:37

you know, are you the tool master of all of these sort of things of anything

26:42

revenue related versus

26:43

your specifics and that stuff. So that's that's interesting. Yeah, I think that

26:47

that stems from

26:48

like what I mentioned earlier is how active campaigns rev ops team was kind of

26:54

created out of a sales

26:55

ops probably foundation or that's where it came from. And so we do manage the

27:01

tools for sales.

27:03

So things like LinkedIn navigator licenses or, you know, dial pad, different

27:09

things like that.

27:10

And then we work collaboratively with tools like looker, snowflake, etc, to get

27:15

all the data.

27:16

But we don't manage the tools that are outside of really outside of the sales

27:21

work at this point.

27:22

I think again, we're now looking at, okay, we've kind of gotten to this place

27:26

where things are

27:27

going well. But if we were to make a more centralized ops team or begin to

27:32

centralize our process is

27:33

a bit more, can we enhance what we're doing? Can we, you know, and we have to

27:37

ask those questions,

27:38

like you can't just be complacent with where you're at because the market

27:43

changes so fast.

27:44

The the markets always evolving. And we've seen, especially in the last two and

27:49

a half years,

27:50

that things can shift literally overnight and change almost instantly depending

27:55

on your region

27:56

or globally. Right. And so what we have to do is be always continually

28:01

evaluating ourselves on

28:02

is what we're doing today. The very best thing for us to be doing. And that's

28:07

how you grow.

28:08

Are you a spreadsheet person? I like to look at spreadsheets. I'm not great at

28:14

building spread

28:14

sheets. And I would say like for me, what I try to do is we have several

28:19

analysts on our team

28:20

that are excellent. And I work with them to define what we need, what reports I

28:27

'm looking to get,

28:28

right, how those need to look and feel. And then I work with them to build out

28:32

what we need so that

28:33

we can be up to date and current on things at all times and make sure that we

28:37

do. I have a few

28:38

things that I look at, you know, quite a bit, especially like with, again,

28:42

related to trials

28:43

and conversion rates and different things like that. That's something that we

28:46

were constantly

28:47

paying attention to. But I allow them, the analysts that are really skilled at

28:53

in the

28:54

the spreadsheets to build what they need to build. And then I am lucky enough

28:57

to be able to

28:58

digest that data and try to make decisions off of it. Have you noticed

29:02

something in the pipeline

29:04

that wasn't working and that you had to kind of go about kind of digging in

29:08

doing the research and

29:10

fixing it? There definitely have been at different times, one from a few years

29:15

ago. This was an

29:17

early day. So I was still a director of sales, but at that team, our ops org

29:22

was like two people,

29:24

right? So when there was a problem from my side of the house on the director of

29:28

sales side, like,

29:29

I was involved in it. And having been at AC for so long, I tend to just like

29:34

get my hands into the

29:35

weeds. And basically what was happening is I had a two week span where there

29:40

were no deals coming to

29:41

my team, for whatever reason. And at first, I was thinking that in Australia,

29:48

where I was living at

29:49

the moment, the Christmas holiday, like the country effectively shuts down. So

29:54

I think that it's,

29:56

I was like, Oh, maybe it's just because everyone's going on holiday. And then I

29:59

was like,

29:59

Hmm, this feels off. And so what we had to do is go look through what were the

30:04

reasons for

30:05

that? What was the routing? And then we went through our automations. And I

30:08

think like this is the

30:09

piece of rev ops, right? That can be applied to a lot of things is when you

30:14

have a problem,

30:15

you have to be able to quickly identify what tools could be causing that

30:19

problem. Right? So if data

30:22

is not appearing properly, you can say, well, is my data not refreshing? Maybe

30:26

the data is there,

30:27

but it's just not refreshing. If you can rule that out, then pretty quickly you

30:31

can recognize

30:32

that you actually have a tool problem that you need to address. And in our case

30:36

, because I,

30:37

like I said, we use a lot of automations, we are constantly watching our autom

30:41

ations to make sure

30:42

that they're functioning properly, that they're putting people through them

30:45

properly, that our

30:46

routing is going where we want it to go, and that there's, you know, something

30:49

didn't break. Like,

30:50

again, we use our own tool pretty aggressively. And so we have to constantly be

30:55

watching

30:55

the different things that we have in place within our own system, just to make

31:00

sure that

31:00

everything is going right, or that someone didn't make a change and forget to

31:04

take like, you know,

31:05

we had one similar thing just a while back where luckily it was kind of small

31:12

potatoes. It didn't

31:13

really impact things. But someone said, Hey, man, like, I'm not getting what I

31:17

need. And we realized

31:18

that when someone was changing in automation, they put a wait step in at the

31:23

top will often do that

31:24

just to prevent people from flowing through while we're like working on things.

31:28

And they forgot to

31:29

remove the wait step. So everything went through everything corrected itself.

31:33

But there is this

31:34

like four hour gap where everyone's like, Hey, nothing's coming through to us.

31:38

And so, you know,

31:39

again, we were able to fix it, but we had to know where to look. And that was

31:42

really like the key,

31:43

the key of that piece.

31:45

Any other just like blind spots with data or something that you wish you could

31:50

be measuring

31:51

better, or maybe a tool that you're going to start messing with here coming up

31:56

or anything

31:57

that you'd like to prove? Yeah, I think for us, and this goes back to when I

32:01

talked about like

32:02

building the relationship with operations, especially related to marketing, is

32:07

one of the

32:08

things that we've realized as we've built this relationship, and especially

32:11

over the last 12

32:12

months, is that sometimes marketing says one thing. Revop says the other thing,

32:19

they kind of mean

32:19

the same thing, but they use different terminology or, you know, they might use

32:23

a different tag

32:25

inside of an automation that's just slightly different or a different field to

32:30

be updated,

32:30

right? And again, you're kind of getting to the same result at the end of the

32:33

day.

32:34

But I think one of the things that we're really trying to work on is creating

32:38

this unified like

32:39

language for operational teams within our company. And that can be like from

32:44

again, how the data

32:45

is used, what tables are used, it could be your tagging mechanisms or naming

32:51

conventions.

32:53

It could be even things like how do you build an automation and title it so you

32:58

know which team

32:59

owns it and who is the last person to edit it. And those are the types of

33:03

things that we're like,

33:04

if I look at the next coming 12 months, that's one of those areas that, you

33:09

know, there's been a

33:10

tremendous amount of work done, but there's still a lot to go. And it's worth

33:14

it though, like the

33:16

alignment is only continuing to gain momentum. And that's really exciting. And

33:22

so what we're doing

33:23

is trying to look at ways, okay, how do again, this talks about like bringing

33:27

in your stakeholders,

33:28

right? Yes, I could go through and I could just say, okay, here's all my source

33:33

fields.

33:34

I'm going to like put those in place, easy peasy marketing has their source

33:38

fields. Well,

33:38

if there's not alignment, then we're our data is now skewed, right? So then we

33:42

have bad data.

33:44

And so it's really making sure that, okay, hey, we're going to do an audit

33:47

together.

33:49

We're going to go through this and we're going to agree that nothing changes in

33:53

this,

33:53

unless like we again, mutually exclusively agree together as a team that we're

33:59

going to be

33:59

willing to make that change. And I think that that's really important. Or if I

34:03

add something new,

34:04

where do I record that? And what we would see is again, marketing had their

34:09

documents,

34:10

their Google Docs that they recorded their stuff in, we had ours. And now we've

34:14

had to,

34:14

we've brought those together. And then therefore we have a much more unified

34:19

approach and we don't

34:20

waste time, you know, just talking to each other and trying to figure out like

34:25

where we went wrong.

34:26

All right, let's get to our quick hits. These are quick questions and quick

34:32

answers.

34:33

Adam, are you ready? I'm beyond ready. If you could make any animal any size,

34:38

what would it be?

34:41

I would make a blue whale able to fit in my fish tank. That's a good one.

34:46

You have a bigger rev ops misconception that rev ops means one thing and that

34:53

every company

34:54

does it the same way. Do you have a favorite movie character of all time?

34:59

Ooh, John Wick without a doubt. If you could have a superpower, what would it

35:07

be?

35:08

I'm going to go with the classic of flying. I think that would be just

35:12

unbelievable.

35:12

Do you have a best concert that you've ever been to? Yes, ironically, it was

35:20

Josh Groban back in

35:22

college, but unbelievable musician and an unbelievable concert at the XL Energy

35:28

Center in Minneapolis.

35:31

If you were sitting right here for our next interview with a fellow rev ops

35:37

leader like yourself,

35:38

what would be something that you would ask him? How do you buy in from key

35:44

executive stakeholders?

35:46

So I'm talking like your C-suites and above quickly. How do you get buy in?

35:54

I usually slack our owner and complain to him. If you're being an employee

36:01

number nine,

36:02

I suppose there. No, I don't actually do that. That's not the right way to do

36:07

it. That was a

36:08

bit facetious. I think that it starts with trust. When you go to an executive,

36:12

they have to believe

36:15

in your brand enough to hear what you're saying. And if you say that something

36:20

's urgent,

36:22

because, and you need to be able to back it up, but you can't just go off of

36:25

guts. My gut says that

36:27

things are about to explode. You have to be able to show the why, but they have

36:31

to believe in you

36:32

enough to be able to take it seriously. And I think that building trust is like

36:37

Lynch, Pinn, critical, the most important thing that you can possibly do as a

36:42

rev ops leader

36:43

with both directions. You have to build trust. What advice would you give to

36:50

someone who's

36:50

newly leading a rev ops team? I think it would be to stay humble and get

36:58

involved with groups.

37:00

There's a couple. I go through a group called say with sales assembly. I take

37:05

some of their

37:06

classes. They have monthly meetups for rev ops leaders. I try to participate in

37:10

those from I

37:10

can and just listen, right? I think that I've learned a lot on those calls, not

37:15

because of the

37:16

brilliant things that were being said by maybe a speaker, although some of them

37:19

have been truly

37:20

brilliant. But it's also listening to my peers. And I would say that like, if

37:26

someone's brand new,

37:27

the more that you can get involved with other people and other businesses, one

37:31

is going to

37:32

foster ideas. You're going to hear that one sentence or that one phrase that

37:37

you're like,

37:38

Oh, that totally makes sense. And that's why we've been having this problem. Or

37:44

it might say,

37:44

Hmm, in a future state, we need to get to where we have like a really kick butt

37:49

deals desk. And

37:50

that's something I haven't thought about before. So I think it's just building

37:54

those peer groups

37:55

getting involved with groups on LinkedIn, etc. And that'll take care of a lot

38:00

of your woes.

38:02

Adam, it's been awesome having you on the show. Anything that I missed,

38:06

obviously our listeners

38:07

should check out active campaign and go to active campaign dot com to learn

38:11

more. But yeah,

38:12

anything I missed anything to plug? I don't think so. I think just the last

38:15

thing that I would state

38:16

is really figuring out your tool set and sometimes realizing that the

38:20

complicated answer isn't

38:22

necessarily the best answer, right? And I'll give you a really simple example

38:26

of that as my

38:27

parting words. But one of the things that we've realized right is like we can

38:32

utilize Zapier a

38:33

lot of times to send data back and forth. And so for instance, when we need to

38:39

do big data sets

38:40

and upload data into our CRM, it's often better for us to go through an API.

38:47

And we can do that

38:48

via Zapier without too much coding. I don't have to get a developer involved. I

38:52

've got a guy on my

38:53

team that knows API is enough to like make it work. We grab the data, we put it

38:58

into a spreadsheet,

38:59

it uploads, we can catch all of our failures instantly. We can correct a men

39:04

data, which is

39:05

fantastic. And Zapiers are really simple tool to use, right? And it's really

39:10

powerful. And so for us,

39:12

I could go the route of, man, I need a tool that does this and I need a

39:16

developer to build it to

39:17

me. Well, one that takes away resources from the company from other projects.

39:20

And two, for a couple

39:23

hundred bucks a month or however much Zapier costs, I'm sure we pay more than a

39:27

couple hundred. But

39:28

you get the point for a small fee, certainly cheaper than a developer, I can

39:33

have things built

39:34

for me that I can implement same day most of the time. And that to me is worth

39:38

like speed is of

39:39

the essence. So I try to find a simple solution and make sure that I'm not over

39:43

complicating thing

39:44

because I tend to get shiny objects and drums. So I, that's a fancy new toy.

39:48

And I just did this

39:50

and it will all work perfectly. And sometimes like the answers right under your

39:53

nose and it's

39:54

not shiny, but it's it works. I love it. Great. Great advice and final thoughts

40:01

, Adam.

40:02

You're awesome. Thanks so much for giving your time and we'll talk soon.

40:05

Thank you so much. Take care.

40:14

(upbeat music)