Renee Psenka & Ian Faison 27 min

Being Right vs Being a Good Partner


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.

0:07

I'm the in-phase on CEO of Cast Meon Studios.

0:09

And today we are joined by special guest Renee, how are you?

0:12

Great. How are you? Thanks so much for having me in.

0:15

Thanks so much for joining the show.

0:17

Excited to chat revenue operations at

0:20

Rutterstack chat your background and everything in between.

0:24

So let's get to our rev opening here.

0:26

How did you get into RevOps?

0:28

Oh my gosh, I have not heard that pun before,

0:31

but that's a great one. I'm not to use that sometime.

0:34

I got myself too apparently.

0:36

Probably like most people in RevOps,

0:39

I got here sort of by Kinesis,

0:41

but I got into RevOps via partner operations.

0:45

So when I started my career,

0:46

I was in sort of a product management role at

0:48

Cisco where I was responsible for a number of

0:52

applications that the partners in

0:54

Cisco's ecosystem leverage.

0:56

From there, I went from a very large company to

0:59

a very small startup at the time.

1:01

I joined Bolt, the checkout company, Bolt,

1:03

to lead their partner operations from there.

1:07

Based on a number of projects I worked on that role,

1:09

sort of expanded into supporting partnerships and SDR

1:12

and then later sales as well.

1:14

So sort of a standard sort of sales

1:17

off scope of work at Bolt.

1:19

And then from there, I've sort of found the opportunity

1:22

via some folks in my network at Rutterstack

1:24

to lead their RevOps operations function.

1:26

And when I met with the team,

1:28

it ended up being what I thought could be a great fit

1:31

for the next step of my career.

1:33

- Yeah, what's your definition of Rev new operations?

1:35

- So I've been interviewing folks for my team

1:37

for a little while, so I have this spiel down

1:40

in terms of what RevOps means at Rutterstack.

1:42

But I think of RevOps as the team that's responsible

1:45

for providing the go-to-market functions,

1:47

be it sales, SDR, partnerships, marketing

1:50

with the insights, processes and tools

1:54

that they need to be successful at their jobs, right?

1:57

So whether it's a forecast or an impact analysis

2:01

to all of the sales processes and handoffs between teams,

2:05

how do we qualify leads to then all the tools

2:07

that enable those things to happen

2:09

in a systematic, formulaic and measurable way.

2:13

- And then what does your team look like at Rutterstack?

2:15

- A RevOps team is a team of three, so myself

2:18

and then we have someone focused particularly

2:20

on sales operations, so supporting SDR, sales,

2:24

and then sort of all the sort of one level outside of that,

2:27

right?

2:28

How does sales interact with customer success?

2:31

How does SDR interact with marketing?

2:33

So they're responsible sort of for that full stack

2:35

of functions, insights, processes, systems

2:38

for that functional area.

2:40

And then we also have a member of my team

2:41

who's an analytics engineer focused on more detailed

2:46

analytics around marketing attribution

2:48

or product activation insights, anything from our install base

2:52

of a free or paid customers that might indicate some propensity

2:56

to buy or spend more with Rutterstack.

2:58

And then myself, obviously sort of over all

3:00

of those functional areas as well as providing support

3:03

for the marketing team, in addition to obviously

3:05

that sales focus.

3:06

- How does Rutterstack go to market?

3:08

Who are you selling to and what do y'all do?

3:10

- Rutterstack is a customer data platform.

3:12

For those of you not in the space,

3:14

that is Rutterstack provides data pipelines

3:17

that enable you to take data and insights and usage

3:21

from your website or your application

3:24

and send it into your warehouse.

3:25

And then from your warehouse, maybe you can run some DBTs

3:28

or analytics on that data and then send it back

3:31

to either those applications or another source.

3:34

So for a RevOps person, right?

3:37

We do use Rutterstack at Rutterstack.

3:39

We might send someone does a demo request on our website.

3:43

We'll use Rutterstack to send that form submission event

3:46

into Salesforce, use Rutterstack to transform that

3:49

into a lead and create a new lead in Salesforce

3:52

and sort of route that to the SDRs

3:54

through a sort of more traditional SAS tech stack process.

3:58

And then throughout the course of that customer's journey

4:01

with us, as they use our application

4:04

or engage with our website more,

4:06

we'll also retain all that data in our backend.

4:09

And maybe we have a lead scoring model, right?

4:12

We'll use a reverse ETL or we'll send that data

4:16

from our warehouse back in the Salesforce

4:18

to give our go-to-market teams some more insight

4:20

on that person's propensity to talk to us.

4:23

So that's what Rutterstack does in terms of who we target

4:26

and how we go to market.

4:27

We're selling primarily to data teams, product teams,

4:30

heads of marketing rights of folks that want to take the data

4:35

from their customers or potential customers

4:37

and figure out how to use it to drive additional revenue

4:41

or serve better experiences to their customers.

4:43

So we're looking at selling into more technical teams

4:47

a lot of the time.

4:48

And then I think maybe the first part of your question,

4:51

which I'm answering last is sort of how do we go to market?

4:53

So we've recently started doing outbound a lot more.

4:56

So that's one component.

4:57

I think we have a significant amount of inbound traffic

5:01

that we get.

5:01

There's a lot of content that Rutterstack will put out

5:04

in terms of the data space.

5:05

Rutterstack has a top data engineering podcast as well.

5:09

So we'll put out a lot of content.

5:11

Webinars, things like that, that drive inbound interest

5:14

and then leading to demo requests and app signups,

5:17

which is sort of that last go-to-market funnel for us.

5:20

We have a freemium model, right?

5:22

We have a free product.

5:23

You can sign up for Rutterstack today

5:25

and send about 5 million events per month for free.

5:28

So we have a number of users that sign up, try it out

5:31

and either quickly approach that limit

5:34

or are interested to learn more

5:36

and get in a conversation with an expert on our team

5:38

and sort of engage and start the sales process that way.

5:42

- Love to see that.

5:43

You all have a thriving podcast.

5:44

It was great to see and video series, I might add.

5:47

Coming to this role, I'm curious,

5:48

like over your first six months, like,

5:51

how did you approach sort of getting your head around this,

5:54

like where you were at as a company in this RevOps duties?

5:57

- So when I joined, and this was the approach that I shared

5:59

as well when I was interviewing for the role

6:01

and with a whole new set of problems and challenges

6:04

and opportunities, you really need to understand the way

6:07

that everything works today to make it the way

6:10

that it should be, right, or go from point A to point B

6:13

or from zero to one in the case of joining

6:15

sort of an early saved startup.

6:16

So what that meant for me when I came in

6:19

is understanding the way it is, right?

6:21

So who are the key players, people, teams, customers,

6:25

and then what are they doing, right?

6:26

And what are we trying to achieve?

6:28

So you gain that perspective from talking to all

6:31

of those stakeholders and learning what their priorities are,

6:33

what their targets are, and how they're trying to get there.

6:36

So when I joined Rutter Stack, we had, I wanna say,

6:41

with there were three AEs, there was the Head of Sales,

6:43

there were a handful of folks on the marketing team,

6:45

there was one person running customer success

6:47

and managing all of our customers

6:49

and one guy in partnerships and no SDRs.

6:52

So it was pretty easy to get to know all the people

6:55

and understand where they were coming from.

6:57

And then it was a matter of learning all the processes.

7:00

For me, we use Rutter Stack at Rutter Stack,

7:03

and that's not something that I have any experience with

7:05

on the marketing operations side, right?

7:07

For us to get the leads from our website

7:10

enriched and into Salesforce, folks use Marketo

7:13

or Partot or Parto.

7:15

So learning that from a systems perspective

7:18

is definitely something new for me.

7:19

But yeah, I think just getting to know the people

7:22

and the priorities, and then if you have some context

7:24

for how systems work, right?

7:26

It's not rocket science.

7:27

You can sort of quickly build a framework

7:29

and start to deliver some impact pretty quickly.

7:32

All right, let's get to our next segment here.

7:36

Rev obstacles, re-tuck through the tough parts of RevOps.

7:40

What are your Rev obstacles?

7:42

What's the hardest RevOps from you've had to face

7:44

in the last six months?

7:46

- So I think the hardest challenge

7:49

or the biggest challenge that we've had

7:51

from RevOps perspective at Rutter Stack

7:53

has definitely been going true zero to one for our SDR team.

7:57

That's everything and structuring compensation

8:00

to giving them target accounts,

8:02

figuring out how to align eight years with SDRs

8:05

and measure that performance

8:06

and as well as kind of all the systems

8:07

and tools that they need.

8:09

So the challenging part, I think, was doing that all

8:11

within a very condensed timeframe of about two months.

8:15

So if you think about within two months

8:17

going from having no SDRs to having a team of about seven folks,

8:22

all with no tools to start off with, right?

8:24

So didn't have some info.

8:26

Outreach wasn't really optimized for SDRs.

8:28

There was no AESDR alignment concept.

8:33

Up until that point, we had one inbound SDR

8:35

who had since been promoted into a commercial AES role

8:38

and her job day in and day out was just fielding requests, right?

8:42

So when you scale a team thinking about

8:45

making sure everyone is fed

8:47

in terms of having enough leads to work,

8:49

enough accounts to work

8:50

and that you can measure their performance, right?

8:53

Whether it's from a compensation perspective

8:55

or just understanding what's working and what's not working.

8:58

And I think what we found very quickly

9:00

and I think fortunately to have that we had a number

9:03

of those systems set up to be able to measure

9:05

how things were going in terms of conversion,

9:08

in terms of meeting being set or not set

9:10

with particular target stakeholders,

9:13

open rates and reply rates on outreach cadences,

9:16

we were able to find out pretty quickly

9:17

what we needed to change.

9:18

- How do you balance supporting sales marketing

9:21

and customer success together?

9:22

I don't know, you haven't talked to a ton about CS

9:24

as a function, so I don't know how much of that

9:26

you're looking at being in charge of revops

9:29

or yeah, how do you break it down?

9:31

- Yeah, so on the CS side,

9:33

we have someone who's focused on strategy

9:35

and opposite sits within CS,

9:36

but on the system side and I think on the insights piece,

9:40

we do provide a lot of support, right?

9:42

This customer success team recently launched with game site

9:46

that they're familiar with that

9:47

as a sort of like Salesforce for CS, right?

9:50

So we help with that Salesforce integration,

9:52

working with consultants to get that accomplished

9:54

as well as the handoff process between sales and CS

9:58

and then forecasting for CS as well.

10:00

So we do support the teams on the system side

10:02

and then obviously as they work with other teams

10:05

at Brutterstack.

10:06

In terms of how we prioritize,

10:08

I think there's only so many hours in a day

10:10

as I think any revops person can sympathize with

10:13

and understand there's always more stakeholders

10:15

and you have time to help.

10:17

The way that I prioritize it is thinking about

10:20

what is gonna be the most impactful to the business.

10:23

So if we have a really short pipeline month, right?

10:26

And there's a number of projects

10:28

that might help marketing improve conversion.

10:30

That's what's gonna be prioritized, right?

10:31

So if you think about, you know, at the highest level, right?

10:34

The whole company, they're the whole revenue organization

10:37

is aligned to whatever that number is

10:40

for the end of the quarter or the end of the year.

10:42

I think no matter what stage of a startup you are

10:44

or even company, I think everything sort of boils down to that.

10:47

So when you sit in revops,

10:49

you do have a unique perspective on how all of those

10:52

different elements of go-to-market will impact

10:54

that final number at the end.

10:56

And then the second portion of that obviously is,

10:58

is thinking about hiring and scaling your team, right?

11:01

And how you build that leverage

11:02

and how you make a sort of a justification to hire.

11:05

So that's also where, you know,

11:07

we're focused on growing the team

11:08

so that we can get all the teams in love

11:10

in terms of rev-op support.

11:13

- Do you have your biggest revoops moment

11:15

of the past year or something that you messed up

11:17

or you were like, "How geez, we probably should've done that?"

11:21

- Rev-oops, oh my gosh, these puns are killing me.

11:24

As I think anyone who uses Salesforce will know,

11:27

you should always have a dedicated integration user

11:30

for all of your integrations for a number of reasons,

11:32

which basically means that the application

11:34

will communicate with Salesforce

11:35

through a particular account.

11:37

So we had our RutterStack instance connected to Salesforce

11:42

through my personal Salesforce account.

11:44

When it came time for a password reset,

11:47

those credentials were not refreshed

11:48

and RutterStack automatically.

11:50

And it took a few hours, which is, you know,

11:53

a few dozen leads in our case

11:55

and then that went over the weekend actually.

11:59

So, you know, a few business hours,

12:01

but a few days worth of data

12:03

where things were not flowing into Salesforce,

12:05

leads around MQL and because of that sort of

12:07

that credential issue.

12:08

So there was a quick resolution,

12:10

but I think what I learned there is, you know,

12:12

when you're an early stage startup,

12:14

you do a lot of zero to one things where you're like,

12:16

okay, this is fine now, right?

12:17

We're trying to save money.

12:19

So we're not gonna buy additional Salesforce licenses.

12:21

You get to a certain point where you do need to invest more

12:25

in process involving the recommended setups

12:29

for all of your applications

12:30

that you can't just hack everything together.

12:32

So that was a good moment for me to sort of take a step back

12:35

and evaluate how we had set everything up

12:37

to make sure that it would scale.

12:39

And then we went back and updated a decent amount

12:41

of configurations as a result of that

12:43

and have not had a similar issue.

12:45

But I think that was a good learning for me certainly.

12:48

I love it. That's a great one.

12:50

Such a good point that when you're building

12:52

from the very beginning, you know, act like you're big

12:54

'cause otherwise it'll come back to bite you.

12:56

I think about it all the time.

12:57

All right, let's get to our next segment, the Tool Shed.

13:01

We're talking tools, spreadsheets, metrics, stuff like that.

13:04

Just like everyone's favorite tool, qualified.

13:06

The B2B Tool Shed is complete without qualified.

13:08

Go to qualified.com right now and check them out.

13:12

What's in your Tool Shed Renee?

13:14

- Qualified is the most recent addition to our Tool Shed.

13:17

So we do use qualified for our marketing site.

13:20

We're evaluating adding it in the application as well

13:22

on certain pages.

13:23

We'll use that for conversational marketing

13:25

as well as insights and signals for our outbound team

13:28

and our account executives, right?

13:30

And it's been very impactful for us so far.

13:33

If I want you to list out sort of the big players,

13:35

I'll start at the top of the funnel

13:37

where we use Rutter Stack, right?

13:38

So Rutter Stack is what we use to get our leads in

13:42

from our application, from our marketing website

13:45

and sort of track as well all of the interactions

13:47

that those sort of de-anonymized folks have with our website.

13:52

So in the same way that qualified, right?

13:54

When someone puts their email address

13:56

into the qualified bot, you're always able to tell

13:59

that that person coming back in the future,

14:02

we do the same thing on our marketing website, right?

14:04

So if someone gives us their email in a demo request

14:07

or to register for content marketing webinar,

14:10

we'll cookie them, right?

14:11

And we'll track how that prospect is engaging

14:14

with our content going forward.

14:16

We'll actually also use Rutter Stack to instantly enrich those

14:19

or near instantly enrich those with Clearbit.

14:21

So qualified also leverages Clearbit.

14:23

So we do have a good consistency,

14:26

at least in terms of MQL logic

14:28

and how we think about what a qualified versus unqualified

14:31

lead is between qualified and our marketing site.

14:34

Over-arching as well, we leveraged Tableau

14:37

for a lot of the usage insights, analytics,

14:39

just different go-to-market roll-ups.

14:41

So yeah, I think that's like the tool belt

14:44

for us at Rutter Stack.

14:45

- Love it.

14:46

What metrics matter to you?

14:48

- Metrics that matter to me.

14:49

I mean, I think the most important one is our ARR number, right?

14:53

We obviously have that big,

14:54

I don't know if I can say it on the podcast, right?

14:56

But we have the number that we're tracking to

14:58

towards the end of the year

14:59

that's sort of net of everything, right?

15:01

So net of churn, net of self-serve sign-up, upsells, right?

15:04

We have a number we're trying to get to.

15:06

So that's top of mind for me and for everyone.

15:08

I think the most important metric now

15:10

that we have as a growing startup,

15:13

in its earlier stages, it's all about pipeline, right?

15:16

And how are you building pipeline for us

15:18

to hit the even bigger top line number next year?

15:21

So it's not just pipeline ARR.

15:23

In fact, pipeline ARR is probably the least important metric

15:26

to me because no one knows how big a deal

15:28

is gonna be when it comes in.

15:29

But the ones that I care about most now,

15:31

certainly our conversion metric.

15:32

So all the different slices and dices, right?

15:35

Whether it's what was their first touch,

15:37

what were all the touches that that person had,

15:40

how many of, is that the first person from that company

15:44

that we've seen for the second?

15:46

Just looking at how all those things impact conversion

15:48

so that our traffic continues to grow.

15:51

And as we invest in that top of funnel,

15:53

how do we make sure that we're converting

15:55

as much possible into pipeline?

15:57

- If something's not working from a pipeline perspective,

16:01

how do you notice that?

16:03

What's an example of something where you notice

16:05

where you're like, yeah, that doesn't look right?

16:07

- If you think about traffic or a number of meetings

16:09

or anything like that, those finite numbers,

16:13

don't always tell the full picture, right?

16:14

'Cause you can spend a lot more in advertising

16:18

and certainly you could make that a percentage rate, right?

16:21

Of traffic versus your spend.

16:23

But where we are able to identify those issues

16:25

is by looking at the conversion rates

16:27

and what we did, what we actually did notice

16:29

is we had an issue with how our site was showing up

16:33

in organic search that was preventing

16:35

some very high intent traffic from finding our website, right?

16:39

So we did notice that the conversion rates

16:42

from that particular segment of direct traffic

16:46

just nosedove, right, for a few weeks.

16:49

And we're able to diagnose certain partnership

16:51

with different organizations at RutterStack

16:53

and that does show up very quickly, right?

16:56

Because it's a conversion from traffic to inquiry.

16:58

So that's sort of that first indicator

17:01

and we're able to resolve that within a matter of days, right?

17:04

Once that was identified.

17:06

- Are you a spreadsheet person?

17:08

- I would say I'm a spreadsheet person, yes.

17:10

I don't know how many people say no to that question

17:13

when you ask.

17:13

- I think we're probably, I don't know,

17:16

I think we're like 50/50 around there.

17:18

- Oh really, okay.

17:19

- But you had people who like love them

17:20

and then people like, I can't do it at all.

17:22

So what's your top three spreadsheets or favorite ones?

17:26

- Like that I use day to day to run my business or team.

17:31

So I would say-- - Are you gonna

17:32

sign to that?

17:33

- I don't know, you're a fantasy folk artist.

17:35

- Yeah.

17:35

- I don't know.

17:36

- Oh I do, I can talk about that one first.

17:38

That one is that I do have a spreadsheet

17:40

that is how I draft.

17:41

So what I do is, 'cause I don't follow football

17:44

and all that I'm very competitive

17:45

and I do know my spreadsheets.

17:47

So what I'll do is I'll take the top three analyst drafts

17:51

whether it was PPR or standard or half PPR, whatever that is.

17:54

I'll find the top three most recent

17:56

and I will give each player using sort of just

17:59

a simple VLOOKUP, right?

18:01

I'll return all of their draft picks, right?

18:03

So if Jonathan Taylor's picked first in each of these drafts,

18:06

he'll have a three and then I'll sort it

18:08

in ascending order by the position

18:11

and I will pick the top available.

18:13

So that's a good spreadsheet for me.

18:15

I think the other, yeah, so that's my fantasy football hack.

18:20

You do need to know Excel to accomplish that.

18:24

But that's one I think the other sort of big spreadsheet

18:27

that we use which is sort of a master sheet

18:30

is the forecast model.

18:32

So looking at a number of different input metrics

18:35

and sales assumptions,

18:37

there is a relatively robust monthly sales forecast

18:41

that I built at the beginning of the year

18:42

and then we sort of did a read forecast exercise mid-year

18:45

although we were within 5% accuracy

18:48

of the original forecast.

18:49

Certainly second half obviously,

18:51

the world was very different in January than it was in June.

18:54

So it's more of an outlook adjustment, right?

18:56

Going forward, but that's another big one, right?

18:59

So if we think about are we short on pipeline?

19:02

What does that mean for the next five, six months, right?

19:05

If we didn't have a great August,

19:07

how's that gonna impact December?

19:10

So that's a spreadsheet that we referenced a lot

19:13

at RutterStack and we're still at the stage, right?

19:15

Where we'll do this planning in spreadsheets

19:18

at some point, we'll move out of that.

19:20

And then I would say the last one is probably,

19:23

this isn't really a spreadsheet, it's a Tableau dashboard,

19:26

but I think Tableau dashboards are just spreadsheets

19:29

with a nice UI, pivot table with a better UI.

19:32

As a go-to-market scorecard that we have,

19:33

which is essentially, we ETL everything from Salesforce

19:37

into RutterStack on a nightly basis.

19:39

And so it makes it really easy,

19:41

a lot easier than Salesforce reports and dashboards

19:43

to interact with, to build a great visualization

19:46

that sort of shows what our revenue build is to that number,

19:49

what our performance is to the quarterly goal,

19:52

how close are we to 100% renewal,

19:55

who are the top SDRs, where are leads coming from,

19:57

what's the pipeline?

19:58

And it's basically a snapshot, right?

20:01

That the whole company actually looks at.

20:03

- I love it, that's great.

20:05

I think the fantasy football one's probably my favorite,

20:07

but you know, they're all great.

20:09

- Well, you probably need to use it

20:13

within the next two days if you're gonna.

20:15

- No, I wish I had it two days ago,

20:17

but you know, here we are,

20:19

sitting there with terrible running backs.

20:21

What are the blind spots that you have

20:24

or something that you wish you could measure better?

20:27

- Yeah, so I think the biggest one that we have,

20:30

and we're working on sort of filling that gap

20:33

is attribution for leads, right?

20:36

Now that we have so much content going out,

20:38

we're seeing folks before we have a pipeline opportunity

20:42

have three or four touches, right, with us,

20:45

where that becomes pipeline.

20:46

And probably a few more than that, right,

20:48

before that opportunity becomes closed one.

20:50

Not to get too technical, but up until very, very recently,

20:54

we had not been using that campaign member object at all,

20:57

right, which is such a nice way to track all the touches

21:00

for a particular person.

21:01

Using Rutter Stack, we were updating the lead source, right?

21:04

So we had a very robust set of data in Rutter Stack

21:08

in this sort of very, very large sort of beast

21:12

of a user journey table.

21:15

And being able to translate that into something

21:16

that's a little bit more actionable for someone like an SDR.

21:19

So figuring out how we translate that

21:21

into something that's more consumable

21:23

for the go-to-market users, right,

21:25

who aren't gonna query this table and snowflake.

21:28

So the way we're doing that is leveraging campaign members

21:31

and giving that insight to the folks that are using it,

21:33

because of course, on my end,

21:35

and with the help of our analytics engineer and the team,

21:38

we can do very, very complex attribution models

21:42

and all of that stuff.

21:43

That doesn't really help an SDR

21:45

who's gonna talk to that person,

21:46

or an AE who wants to know the three webinars

21:49

that they attended.

21:50

So that was a blind spot for the stakeholders, certainly.

21:53

And it's something that we're actively working on,

21:55

improving and delivering now.

21:57

- Any other tool metric or dashboard related thoughts

22:01

for you to our next segment?

22:03

- You know, there's so many tools that do require,

22:06

that do, where it does help to have all of your sales

22:08

for Stata in your data warehouse, just like full stop.

22:12

If that's all you need, Rutter Stack is something

22:15

that's great that you can use probably for free,

22:17

I would say most people that use it for a B2B use case,

22:22

which I assume is most to the audience.

22:23

You can set up a pipeline from Salesforce to Rutter Stack

22:27

in less than five minutes and get everything that you want

22:29

in terms of the objects just synced over

22:32

and you can have that refresh on a nightly basis.

22:34

That makes it really easy if you want to have

22:37

any sort of complex dashboards or do any sort of joins, right?

22:40

That just aren't possible really to do within Salesforce.

22:44

- Okay, let's get to our next segment.

22:45

Quick hits.

22:46

These are quick questions and quick answers.

22:48

Are you ready for that?

22:49

- Yes.

22:51

- If you could make any animal any size,

22:54

what animal would it be and what size would it be?

22:57

- I'm trying to think about an animal that is in nuisance,

23:00

that is very large, that I could make no longer a nuisance

23:04

by making it smaller.

23:05

Like maybe I would just make bees even smaller,

23:07

just like really, really, really tiny.

23:09

- That's a good one.

23:09

- For like mosquitoes, really, really small,

23:11

so that you don't even feel them biting you.

23:14

- That's a great one.

23:15

'Cause if you made like mosquitoes microscopic,

23:18

then it wouldn't really matter if there's this size.

23:21

- Yeah, exactly.

23:22

Then you'll mosquito bites, you wouldn't even see them.

23:25

- Do you have a biggest rev-ops misconception?

23:29

- I think the biggest rev-ops misconception,

23:32

I would say like is just that rev-ops is Salesforce admins

23:35

and it's deaf.

23:37

I'm not a Salesforce admin, so therefore,

23:39

that is a misconception.

23:41

But I think it's more than just Salesforce management

23:44

and I think that as the space continues to evolve,

23:49

at one point, there was probably just the Salesforce admin

23:51

that worked with the Head of Sales.

23:53

And now as I think we have such a,

23:55

and it's not just the tech stack that's growing complexity,

23:58

but it's the go-to-market analytics layer

24:00

and the focus and sort of what those analytics

24:04

can do to inform strategy where rev-ops

24:06

is a lot more complex than just administering tools.

24:10

So I would say that's what I would think

24:12

that misconception is.

24:13

- What would your superpower be?

24:17

- I would think I would like to pause time

24:20

and just work or get things done.

24:23

I have a wedding coming up in a month.

24:25

So there's, I just wish there was 48 hours in a day.

24:29

I'm sure my stakeholders also wish that I had 48 hours in a day,

24:32

but I think that would be the most

24:34

what I would take, right?

24:35

I would just, just to have more time.

24:37

- If you had a question for the next guest,

24:40

we don't know who that is yet, well, we know,

24:42

but you don't know who the next guest is.

24:45

- A fellow Rev-Opper.

24:46

What's one thing that you would ask them?

24:48

- I would probably ask them, I was on a panel recently

24:52

and this is something that I am curious about

24:55

at any org is how have you set up your PMO, right?

25:00

Your project management and how do you communicate

25:03

to your stakeholders and how do you intake requests?

25:05

Something that is, I think really challenging

25:09

at a remote company as well as one that's gone zero to one

25:13

and now you're going one to five is establishing

25:16

those processes and driving that all being remote.

25:20

So yeah, curious about how they manage work intake

25:23

and prioritization and communication

25:24

with all their stakeholder groups.

25:27

- What's one piece of advice that you have

25:29

for someone who is newly leading a Rev-Opper team?

25:33

- Ask questions, listen, and don't try to come with an answer.

25:37

I think any ops person who is successful

25:41

and has made the transition

25:42

from maybe being an individual contributor to a leader

25:45

has probably as an IC gotten to be successful

25:50

by being right and by delivering value

25:53

and building something cool.

25:54

When you get to the stage of your career,

25:57

if you want to get to this at that point, right,

25:59

where you're leading and your perspective needs to not be

26:04

about being right, it's about being a good partner.

26:07

And sometimes that means being wrong

26:09

or doing something or enabling something

26:11

or building something where you think it might not have

26:13

the desired outcome, but you might need to do it, right,

26:16

to be a strong partner.

26:17

So I would say it's switching from being right

26:20

to being good partner.

26:21

And just always keeping that in mind

26:23

is you have conversations and make decisions.

26:26

Don't have an I told you so type of mindset.

26:28

- Or just shrink a bunch of mosquitoes.

26:31

- Or just have that.

26:31

Everyone will certainly be happy with that

26:35

if you deliver that.

26:37

- Renee, wonderful having you on the show.

26:39

That's it, that's all we got for today for our listeners.

26:42

Go check them out.

26:43

That's obviously you've heard a bunch of cool stuff

26:46

about RutterStack, but go to RutterStack.com

26:48

to learn more.

26:49

Any final thoughts, anything to plug?

26:52

- Nope, I guess the data stack show I could plug

26:55

with the other podcast if anyone here is a data engineer.

26:58

I think it's in the top 10 of data engineering podcasts,

27:01

which I didn't know was a category

27:03

until I found out that we were in it.

27:05

But yeah, that's the only thing that I would plug.

27:07

But yeah, I really appreciate the time today

27:09

and it was great chatting with you.

27:10

- Yeah, awesome.

27:11

Take care.

27:12

(upbeat music)

27:14

(upbeat music)

27:17

(upbeat music)

27:19

(upbeat music)