Integrating Product-Led and Sales-Led Strategies at Zapier - Lindsay Rothlisberger
Is the future of SaaS growth product-led or sales-led? What if it's both? Zapier uses PLG to create an ecosystem of users and product signals which then drives their sales-led outreach.
Coordinating these motions in parallel takes technical sophistication, great communication, and tight process. Fortunately, they have a unified RevOps team that keeps everyone on the same page.
This week we chat with Lindsay Rothlisberger, Director of RevOps at Zapier, about how her team helps the magic happen.
Thanks to Our Sponsor
Many thanks to the sponsor of this episode - Knak.
If you don't know them (you should), Knak is an amazing email and landing page builder that integrates directly with your marketing automation platform.
You set the brand guidelines and then give your users a building experience that’s slick, modern and beautiful. When they’re done, everything goes to your MAP at the push of a button.
What's more, it supports global teams, approval workflows, and it’s got your integrations. Click the link below to get a special offer just for my listeners.
About Today's Guest
Lindsay Rothlisberger is a dedicated Revenue Operations Leader with a background enriched in marketing. She thrives on transforming ideas into strategies that improve the customer experience and business metrics. She currently serves as Director of Revenue Operations at Zapier, and has previously held marketing positions at UNiDAYS, Oracle, and Blackboard.
https://www.linkedin.com/in/lindsay-rothlisberger/
Key Topics
- [00:00] - Introduction
- [00:59] - The RevOps scope at Zapier
- [02:52] - Blending PLG and Sales-Led Funnels
- [15:11] - How RevOps helps coordinate different GTM motions
- [22:19] - Org and reporting structure
- [28:49] - Planning and prioritization
- [34:05] - Tech stack and governance
- [41:07] - Tracking signals and CRM architecture
Thanks to Our Sponsor
This November, MOps-Apalooza is back in sunny, Anaheim, California, and it's going to be the marketing ops event of the year, packed with hands-on learning from real practitioners.
This is the only truly community-led tech-agnostic MOPS conference out there. It's got the best speakers, the best networking, the best social events, and maybe even a trip to Disneyland. This isn't your 50,000 person tech company conference. It's an intimate gathering of folks who are in the trenches every day.
Registration is capped at 700 attendees, and tickets are going fast.
Resource Links
Learn More
Visit the RevOps FM Substack for our weekly newsletter:
Transcript
Welcome to RevOps FM.
2
:Today, we chat with Lindsay Rothlisberger,
Director of Revenue Operations at Zapier,
3
:where she leads a unified team supporting
sales, marketing, and customer success.
4
:And Lindsay's experience is super
interesting to me because she's
5
:evolved into a RevOps role from
the marketing side of the house.
6
:Whereas the norm that I see is still
really for RevOps leaders to come
7
:from more of a sales ops background.
8
:So.
9
:As someone with a marketing
background myself, I'm really
10
:interested to drill into that.
11
:And she's also working in a super fast
paced, high volume PLG environment.
12
:And that brings a ton of interesting
challenges and opportunities for
13
:things like leveraging automation.
14
:So we just have a lot of cool
things to dig into today.
15
:Lindsay, welcome to the show.
16
:Lindsay Rothlisberger: Awesome.
17
:Thanks for having me.
18
:I'm really excited to be
19
:here.
20
:Justin Norris: why don't we just
start out with, how you think about.
21
:The scope and the mandate of your team.
22
:And this is something I think
about a lot as an operator.
23
:Like, how do you know when
your team is doing a good job?
24
:How do you know what success looks like?
25
:What's the sort of North star that
you try to keep focused on day to day?
26
:Lindsay Rothlisberger: Yeah.
27
:So maybe I'll start with the scope
of my RevOps team here at Zapier.
28
:We, are responsible on the marketing
side for personalization, segmentation,
29
:and marketing tooling, as well as
things like campaign operations, to
30
:really make sure our customers are
having the best experience possible,
31
:or leveraging all of our data.
32
:in the right ways.
33
:and then we are also responsible for go
to market efficiency and productivity.
34
:So like, are we as
profitable as we can be?
35
:And are we like making the best use
of resources across go to market?
36
:and then our core like North star
metrics are, around qualified
37
:opportunities in particular.
38
:So what can we do from an
operations perspective?
39
:Whether it be better qualification,
better analytics, Really optimizing
40
:the funnel to increase the number
of qualified ops that we're driving.
41
:And then on the other side of
the house as well, it's around
42
:revenue and sales efficiency.
43
:So how can we actually make sales
as efficient as possible so that
44
:we're, opening up sales capacity.
45
:To, be able to handle and sell more deals.
46
:and so within that realm, we're
looking at things like automation
47
:and AI, strategic insights.
48
:So we have a function focused
on that, tech and tooling.
49
:So like the underlying infrastructure
to do all of that, and then like.
50
:Lead and deal management and process, to
make all of that flywheel run day to day.
51
:so that's kind of like a general
overview of our team and the metrics
52
:in particular that we're focused
53
:on And measured
54
:by.
55
:Justin Norris: And you mentioned
opportunities, which usually, you know,
56
:means like a sales led motion, but
you also have, and maybe I don't know
57
:what , your percentage is, but like
I'm as after customer where I work,
58
:but we just pay with a credit card.
59
:We've never talked to a
salesperson that I know of.
60
:Is that also within your purview or
do you view that as like a completely
61
:separate side of the business?
62
:Lindsay Rothlisberger:
it's super interesting.
63
:So when I joined Zapier four years ago,
we did not have a sales team and I was the
64
:first marketing ops person to join Zapier.
65
:So it was really, really interesting
because, I was more focused on that,
66
:like customer experience and campaign
operations and like, how do we,
67
:communicate with our customers in
a way that like really makes sense
68
:for what they need and who they are.
69
:and then we really only started
transitioning into a, more of the
70
:sales led motions about two years ago.
71
:So, There's a whole slew of
learnings from that experience.
72
:But really then there are two challenges.
73
:Like you're building a new sales
funnel, figuring out how to
74
:leverage your vast user base.
75
:And like, who of those people are the
right sales opportunities and figuring
76
:out how that all fits together in terms
of process and operations, et cetera.
77
:And that.
78
:makeup or scope is the reason
why a centralized rev ops team
79
:works so well for us at Zapier.
80
:Just because there's so much movement,
like customers on a subscription
81
:model can, have a certain planting
type and upgrade on their own.
82
:And at what point are they
ready to talk to sales?
83
:And like, we don't want
to cross wires there.
84
:So the centralized rev ops
function helps us like stay really
85
:aligned and making sure that our.
86
:Processes in our customer
journey are like.
87
:acting in a complimentary fashion.
88
:it's a really good
89
:question.
90
:Justin Norris: So let's, dive
deeper into the PLG side just cause
91
:it's such an interesting topic.
92
:I'm used to thinking of like a funnel
from a sales led point of view, you
93
:have a lead and then they're an MQL
but it's all driving towards sales
94
:and then sales owns a piece of it.
95
:Now you've got this thing where
people can choose their own adventure
96
:and take all sorts of weird and
wonderful paths to purchase.
97
:How do you think about that
customer journey, from a top
98
:level, like in the big picture?
99
:Lindsay Rothlisberger: Yeah.
100
:So it's always a work in progress.
101
:I think with PLG, there are
two main motions that we ran.
102
:We have sort of our like requested
demo inbound flow on our website.
103
:So, we actually organically we
have good brand recognition.
104
:We have a pretty high volume of
folks who come through that funnel
105
:and raise their hand to talk to us.
106
:And I think that's a testament to like the
marketing and the initiatives that we do
107
:among our user base on an ongoing basis.
108
:But then when it comes to like
our existing user base and we have
109
:so many different, use cases that
Zapier serves, we have a really large
110
:breadth of personas that we serve.
111
:So figuring out how to like.
112
:Get those folks to the right place
in terms of whether they should be
113
:talking to sales or whether they
should be fully self sufficient
114
:has been, a lot of experimentation.
115
:So we have hypotheses around like,
what types of product signals warrants
116
:like, higher sales effort or might be a
signal that this is our ideal customer
117
:for expansion with our sales team.
118
:So we sort of like canvas our, our user
base and like, for more of those one
119
:to one high touch efforts via like an
experimentation framework of like, is this
120
:our ICP for our higher price point plans?
121
:is this a customer who's sort of bought
in to our product and is using it in a
122
:ways that warrant, more enterprise level,
product features like admin and security.
123
:and so we really.
124
:Don't want to talk to everyone in our use.
125
:Like not everyone in our user base is the
right fit for a high touch sales motion.
126
:so it's been a lot of experimentation
to figure out not only like who
127
:are the right people who are like.
128
:Most likely to expand their usage
of Zapier across their organization.
129
:So who are those people?
130
:And then, what type of touch or
outreach is going to work best for them?
131
:is it a very high touch one to one sales?
132
:Is it an automated sales outreach where
rev ops and marketing sort of like.
133
:personalizes that one to one
outreach because we're reaching
134
:a pretty vast user base.
135
:What is their motivation to upgrade
to one of our higher tier plans?
136
:we've had to learn a lot of that through
trial and error and it's very ongoing.
137
:so we're always iterating
and improving on, that.
138
:Justin Norris: And do you
think about, the product as the
139
:ideal entryway for everyone?
140
:In other sense, in other words, everyone
should come in, they'll create an
141
:account, and then we have like a lead
pool that we can observe and see like
142
:this fish looks like it's going to be a
big fish so we can, try to scoop it out.
143
:Or are there some people where you really
do just want to drive them directly to the
144
:request a demo flow right from the outset?
145
:Lindsay Rothlisberger: We do both.
146
:we're not doing like pure outbound,
traditional like b2b demand gen per
147
:se, where we're like acquiring lists
of potential customers and like doing
148
:outreach, we really have to balance like
our price point with the level of effort.
149
:So that's another, pretty large role
that Rev Ops has played is like, what
150
:should be a very, like, low touch.
151
:high velocity sales motion, where
we're closing deals in one or two
152
:days, because the price point is
just not where it needs to be to do
153
:that level of hands on, nurturing.
154
:so we do a little bit of More
so trying to drive inbound.
155
:So we have our blog, we have, advertising
programs and, and we really try and use
156
:those to bring folks to us in more of
like an inbound fashion, but then our user
157
:base is really, Really, really interesting
because we've got a lot of users who come
158
:in who maybe are using Zapier for one or
two use cases and don't know like all of
159
:the different opportunities by which and
so for them marketing becomes like how can
160
:we get them to find their next use case
and when we have enough like penetration
161
:or usage within an organization.
162
:Then it, warrants more of like a,
almost like an outbounding, our
163
:user base, if that makes sense.
164
:So yes, I would say in terms of
like what you would think of a more
165
:traditional, like B2B sales motion
with PLG, it's really using our
166
:product and marketing levers combined.
167
:To like drive that adoption.
168
:and then when the customer is ready,
we engage with them with more of
169
:a one to one human touch effort.
170
:Justin Norris: Just thinking about it
feels like a great way to run a business.
171
:is it as rosy as it sounds like if
you had to start a business today,
172
:would you, do you like this model?
173
:obviously every motion has its benefits,
but, is it all that it seems like it's
174
:cracked up to be to do business this way,
175
:Lindsay Rothlisberger: I do think so.
176
:come from a more
enterprise B2B background.
177
:I've been at large organizations And
I do think having a product where
178
:people can come in and try it and get
up and running it rather quickly and
179
:solve a pain point that they have,
like it's so much more powerful, I
180
:think, than what you can do with like
marketing webinars and email nurtures.
181
:I think the tricky part there are
definitely some gotchas, like as you start
182
:to expand, market and bring on sales and,
start experimenting with those efforts.
183
:You have to figure out how
you're like single user project.
184
:drives intercompany adoption.
185
:So like where you have multiple
users and you have more people
186
:engaged with the project.
187
:it's a really, really interesting
challenge because you almost have to
188
:look at how can your product drive
more virality within an org to really
189
:warrant more extensive use of it.
190
:at least for us, I think for similar
PLG companies who can solve very
191
:like one to one needs as, as well
as like larger business needs.
192
:you have to figure that out.
193
:As you go.
194
:Otherwise, the sales motion falls flat.
195
:Justin Norris: maybe to
make it more concrete.
196
:If we could walk through like
a semi hypothetical example,
197
:like hypothetical, but grounded
perhaps in real world experience.
198
:you have a company even of a few thousand
people or even less, you might have
199
:multiple like people with different
accounts within that same company.
200
:And so what signals do you look through?
201
:And then What does the seller do to
like, try to bring that together and
202
:create a sales led project out of that?
203
:Lindsay Rothlisberger: Yeah,
that's actually a great question.
204
:and I can walk you through exactly
what that looks like for us.
205
:So, at Zapier, if we have, if we see that
we have multiple accounts within the same
206
:organization, and when you think of this
on the RevOps side, there was a lot of
207
:work that we had to do in RevOps to get
our data in a place to be able to do this.
208
:So like think custom
209
:objects in the CRM to like sort
of group accounts by company.
210
:It's giving me chills just thinking
211
:Yeah, it took a long time to get
where we are today, but at this point
212
:a sales rep can look in HubSpot.
213
:We use HubSpot as our CRM Can
see multiple accounts across a
214
:single domain or a single company.
215
:And at that point they will be
able to see okay, what context
216
:do I have at this account?
217
:Is it someone with enough buying authority
or who may be interested in like having
218
:a conversation about how we might
consolidate that account into a larger.
219
:And then also bring more people in
the organization onto the account.
220
:So then the sales motion becomes okay.
221
:I've identified these companies
where we have several users.
222
:, do we have like maybe a
director or an it person?
223
:In the product.
224
:And oftentimes that's not the case.
225
:And then you think of
like multi threading.
226
:And so your sales motion becomes very
much like, okay, how do I then find
227
:the it person or the director and
bridge that, So that's one example.
228
:We also use product signals in other
ways where, for example, if, Rev
229
:Ops is one of our like key personas.
230
:If we have someone in Rev Ops, who's.
231
:Using Zapier for a pretty like
critical CRM integration, but they're
232
:not really maybe getting the value
out of Zapier that they could be.
233
:we might engage them one to one and
offer, input into like other automation
234
:opportunities and, expand the account.
235
:Yes,
236
:we've
237
:Justin Norris: have like a framework
that you give your sellers?
238
:Like sometimes.
239
:either when I've been on the rev up side
or I've had some past experiences, a
240
:pre sale solution consultant, you kind
of know, like, this is what my path
241
:looks like, like first I engage with
persona one and then I got to get persona
242
:two on board and then persona three.
243
:And maybe there's a few different
routes, but you sort of have this
244
:knowledge of one, two, three.
245
:Is there something like that?
246
:Or is every account like a unique
snowflake that you need to figure out?
247
:Lindsay Rothlisberger: Exact framework and
trying to map it out in a way that is like
248
:clear and repeatable for our sales team.
249
:So what's cool is, I have a
sales enablement person sitting
250
:within the rev ops team.
251
:So, our sales enablement person is able to
bridge, not only the process and how to.
252
:Gaps associated with that, but also
the strategy, around stakeholder
253
:engagement and engaging the right.
254
:Users within an account
around what they care about.
255
:So, yeah, we sort of have a very
like basic framework for like, this
256
:is what the IT person cares about.
257
:And you go to them if this is The
playbook, or, this is what the end
258
:user, what we call, like, the automator
really cares about, the person
259
:building in Zapier and here's how you
sort of elevate them to engage the
260
:director or lead of their department.
261
:So, I would say this is.
262
:Still very much a work in progress.
263
:So our framework isn't completely solid.
264
:but we're starting to make progress
on how that looks like to really
265
:penetrate within an account.
266
:Justin Norris: It's a
fascinating challenge a way.
267
:especially because.
268
:you could have a sales led part of the
process, maybe with some automation
269
:involved, and then maybe like a
marketing led part of the process.
270
:Is your team having total visibility over
all that to like, keep them coordinated?
271
:Or how do you think about that problem?
272
:Lindsay Rothlisberger: that is
what has become so interesting.
273
:I think in this world is like the lines
become very blurred between marketing
274
:and sales because of like our user
base and because it's quite large.
275
:Sales cannot possibly, engage
everyone who meets our, ideal customer
276
:profile for a enterprise level plan.
277
:So marketing really helps to,
like, drive those, meetings or
278
:opportunities for the sales team.
279
:but I think RevOps plays this really
interesting role where We can see it all.
280
:Right.
281
:So, sales leads their own motions
as well, and they have ideas for how
282
:they're going to engage customers.
283
:And marketing has experiments
that they're running.
284
:And so without unified rev ops, I,
I don't know how this would work
285
:because, our marketing ops folks, or
we have, I can go back to our team
286
:structure a little bit, but we have,
three folks dedicated specifically to
287
:sort of like the umbrella of marketing
ops, and like lead management.
288
:And they basically own the
process up until, a lead
289
:becomes a qualified opportunity.
290
:So they book a meeting and then they
are deemed, qualified as a deal.
291
:and then our sales ops folks, we have.
292
:Two people dedicated to like the sales
process and like deal management.
293
:And those two groups are just like this,
it's actually more crucial for them
294
:to be aligned in my opinion, then like
for us to be aligned to marketing just
295
:because, of how quickly that transition
can happen and also like how many
296
:different motions and experiments were
running, there's just too much risk.
297
:to the customer for RevOps
not to play a pretty like deep
298
:role in overseeing all of it.
299
:Justin Norris: To make that a little
bit more real, what is an example
300
:or like a mechanism through which.
301
:, like a day to day basis does RebOps
actually protect the customer from those
302
:sorts of like inconsistent or weird
experiences that could easily happen.
303
:Lindsay Rothlisberger: unfortunately it's
probably more manual than I would prefer
304
:it to be, but I think that's because
we're just moving really quickly and
305
:trying a lot of new motions and things.
306
:so we have actually like a, a.
307
:a small working group, which includes like
a sales person, a sales manager, a sales
308
:ops person, a marketing ops person and
309
:a marketing person.
310
:And they form this little tiger
team that, when it comes to.
311
:Finding opportunities among our
user base there, they've got like
312
:a campaign plan and schedule.
313
:And so they try to create a lot of
transparency and like collaboration,
314
:but revolves plays a pretty large
role in helping to facilitate that.
315
:and helping to stay somewhat neutral in
terms of What's working and what's not
316
:so, if we launch a campaign to our user
base, for example, and we drive a ton
317
:of meetings, but deals are stalling and
they're just not closing as like quickly
318
:as we would like them to, we have this.
319
:Little working group that
can say let's diagnose this.
320
:Why is it because of who we
targeted in the campaign or is it
321
:because, maybe the message sent.
322
:a message that wasn't really helpful
when it didn't really translate well
323
:into the sales motion and what we were
actually, trying to sell the customer.
324
:So, right now we're sort of
doing it in a more manual, like
325
:smaller working group style.
326
:Style way.
327
:but I've noticed like when Rev Ops
is not involved, you see a lot more
328
:friction there, like among sales and
marketing of like, Oh, well, we need
329
:better sales enablement because the deals
aren't closing or, and then marketing.
330
:So, they sort of tend to
like talk past each other.
331
:and I just find that Rev Ops can play
like such a strong role in not only
332
:unifying go to market, but also like,
Offering a perspective that like, take
333
:it, takes into account the like challenges
across both marketing and sales.
334
:Justin Norris: Kind of
couples therapist almost.
335
:Lindsay Rothlisberger: Totally.
336
:It can be stressful, but it is rewarding.
337
:I've just found that like communication.
338
:Is literally the most important skill
that I've needed to have, a RevOps
339
:leader, at least, it's really RevOps as
a function can be really, really powerful
340
:at aligning, go to market and driving
just an amazing customer experience,
341
:it takes a lot of strong communication
and like navigating conflict and all of
342
:those things, it's definitely something
I've learned in the last couple of years.
343
:Justin Norris: That is so true.
344
:Hmm.
345
:and people think of it in many
ways as like a technical function
346
:or like a, process function, but,
the ability to get people on board
347
:and call out those problems and be
like Switzerland, like you mentioned,
348
:be neutral and be seen as like this
trusted person that can kind of
349
:arbitrate these conflicting demands.
350
:Do you find having a unified structure
helps with that because you're not,
351
:embedded in any one of the functions,
you can be that, neutral force.
352
:Lindsay Rothlisberger: absolutely.
353
:I think that was a game changer for us.
354
:So we only moved to a unified rev ops
function two years ago when our sales
355
:motion really started to pick up.
356
:I reported directly into
the CMO prior to that.
357
:So I was in the marketing ops function.
358
:so I think it has been really.
359
:instrumental, in
360
:growing our go to market and maturing
our go to market really, just having
361
:the autonomy, I think, to really focus
on like this intersection between
362
:customer experience and profitability.
363
:There's no one focused on that
otherwise, teams sort of have.
364
:Specific goals that they're trying
to meet that don't take into the
365
:account, like drawbacks, like, Oh,
well, , this is a great motion, but
366
:our, it's taking our sales team a
hundred days to close these deals.
367
:And it, that's just not
going to work for us.
368
:It's not something that we can scale.
369
:The role RevOps plays for
us is like, how do we find
370
:repeatability that we can scale?
371
:And having someone overseeing that
I think has really been successful
372
:and it's elevated us as a function.
373
:Like we get a seat at the table because
we bring that perspective, in a way
374
:that I didn't necessarily get in other
marketing ops roles, at least in my
375
:experience.
376
:Justin Norris: Who do you report into now
377
:Lindsay Rothlisberger: So I reported
into the CRO for the length of our
378
:rev ops time, since we existed in
the org, but our CRO just left.
379
:So for now I'm reporting
into our VP of sales.
380
:And normally at first, I
was concerned about that.
381
:Our VP of sales is very, very
understanding of the importance
382
:of the rev ops function.
383
:And so through this transition, and this
was just like in the last couple of weeks,
384
:it's actually been interesting cause
I've been more intentional then about.
385
:Marketing and being more involved there.
386
:So I'm also like a part of
the marketing leadership team.
387
:So while I report into sales now,
I am embedded within the marketing
388
:leadership function to help bridge that.
389
:And I think that can work long term.
390
:I'm not sure if that will be
what it is for us long term.
391
:but I would say reporting to the
CRO did work very well and was
392
:probably
393
:ideal.
394
:Justin Norris: was your CRO overseeing
all the go to market functions
395
:or was he just a sales leader?
396
:Lindsay Rothlisberger: Yes,
he oversaw marketing, sales
397
:and support and partnerships.
398
:So a pretty big, scope.
399
:Justin Norris: we've touched a
little bit on the structure of your
400
:team, but just digging into it.
401
:you Wrote a great blog post, which
I'll link in the show notes about
402
:your transition to rev ops and you
sketched out and work structure there.
403
:I don't know if it's evolved
since then, but maybe just walk us
404
:through the branches of the tree.
405
:Lindsay Rothlisberger:
Yeah, so it's interesting.
406
:It has evolved a little bit organically.
407
:but I'll explain that
a bit more in a second.
408
:I think what we really wanted to do is we
wanted to have a level of specialization.
409
:Where, someone could really be
deeply embedded with marketing
410
:sales and customer success.
411
:We didn't want to lose that,
like that deep connection with
412
:what those teams strategies are.
413
:let me back up.
414
:We have an operations function
and those are like the day to
415
:day automators, process builders,
campaign ops, deal lead management.
416
:but as you've heard at Zapier,
we are pretty experimental, in
417
:finding out like what motions to
scale from a sales perspective.
418
:So they're very like agile, I
would say like, lead assignments
419
:change, prioritization of
leads change quite often.
420
:So, our operations
function is sort of like.
421
:Core builders.
422
:They're the ones who are in the CRM day
to day building workflows automating.
423
:and then we have the planning
and analytics function.
424
:And so this is the
smallest part of our group.
425
:And this is another interesting, nuance
in being at, in a PLG, company where
426
:we have a really large data org and
we have a really large finance org.
427
:So we've had to carve out like where
RevOps plays within that, org structure.
428
:So we actually only have One person
dedicated to analytics across the funnel.
429
:and they're sort of responsible
for like obsessing over the funnel,
430
:like where are the breaking points,
where are leads dropping off?
431
:and again, that's across everything.
432
:And then we have a
sales enablement person.
433
:and then we have.
434
:Somebody who oversees our tech stack,
and this is actually just one person
435
:probably because she's absolutely amazing.
436
:but she makes sure that, the data
that we need is sinking in and
437
:out of our, tools and our systems.
438
:And our systems are integrated
in a way that facilitates this.
439
:Great customer experience and motions
that we've been talking about today.
440
:but within the operations
function, that's our largest group.
441
:And those are the automators.
442
:we have folks, we have three folks
dedicated to marketing ops, two
443
:dedicated to sales ops, and one
dedicated to CS ops, and those 5 are
444
:very, in sync and have, just a lot of
overlap, coordination and crossover.
445
:Justin Norris: of the things that occurs
to me is, there's this expression, that
446
:a friend of mine uses that I really like.
447
:he talks about, Run the business
versus change the business, whereas
448
:with like run the business, you're
really executing existing process
449
:or making adjustments, but it's
primarily about keeping the business
450
:running forward in its current state.
451
:Then you have other folks that are
focused on what can we improve?
452
:Let's figure that out.
453
:Let's initiate new projects.
454
:Does that sort of split out that
paradigm neatly between the operations
455
:team and let's say the person that's
in planning and analytics, or.
456
:Are, is the operations team divided
between, let's say like day to
457
:day recurring stuff and then
strategic projects that might change
458
:the state of business as usual.
459
:Lindsay Rothlisberger: I love
that way of looking at it.
460
:our operations team is, um.
461
:A mix of both, so they're doing the day to
day running the business, but then they're
462
:also working on larger strategic projects.
463
:I will say that if we did all of
the projects that our stakeholders
464
:requested of us, we would never.
465
:Work on those larger strategic projects.
466
:So we say no a lot.
467
:We forced trade offs a lot.
468
:and, so yes, they're running the business.
469
:And when I say running the
business, it's more of like.
470
:deal hygiene and, and making sure
that campaigns are being launched and,
471
:making tweaks to lead management when
we see a bug come through, et cetera.
472
:they're doing those things.
473
:but I would say they're more because
of the stage of growth that Zapier
474
:is at, they are probably more.
475
:Aligned with the strategic projects and
more so, prioritizing, sort of bigger
476
:bets, Ooh, could we figure out how to
solve this drop off point where we have
477
:people coming inbound and they're not
actually engaging with our chat, we have
478
:a chat team, a sales team that just does
chat and it's a high velocity motion.
479
:And.
480
:And so they might have a project in
marketing ops to figure out how to reduce
481
:that friction and drive, make sure that
like those leads are not dropping off.
482
:So they will have like other
strategic projects like that.
483
:We also have a lot of AI projects that
we sort of like position as strategic
484
:because we view those as helping us
learn and grow and figure out the
485
:next phase of what rev ops could be.
486
:But we.
487
:Definitely have to make
room for that stuff.
488
:and that is just like lots of transparency
with our stakeholders, lots of trust
489
:building, lots of communication about
like why these things are important.
490
:Justin Norris: So thinking about
that prioritization and kind of
491
:planning process, is that, like
yearly, quarterly, monthly sprints,
492
:do the teams have autonomy or do you
centralize it with you guiding it?
493
:How do you think about where the
team should focus their time?
494
:Lindsay Rothlisberger:
luckily for us, we are pretty.
495
:deeply embedded in the
teams that we support.
496
:So like, for example, we go, I go to
the leadership marketing leadership
497
:meetings, myself and a member of my team
go to the sales leadership meetings.
498
:And so I feel like we have a pretty
strong pulse on what the biggest
499
:challenges are, at a strategic level.
500
:however, what we tend to do is
operate on more of like a monthly
501
:commit framework where we have this
overarching roadmap that we create
502
:on a half yearly basis where we say
okay, these are the big things that
503
:we need to figure out this half.
504
:but because of how.
505
:Agile and new.
506
:A lot of our motions are, we find that
we, that operating on a monthly commit
507
:framework and those monthly commits,
they're not exhaustive of everything
508
:we're doing, but we go to the sales
and marketing and CS leadership and
509
:we say, these are the two things
we're going to get done this month.
510
:this is what we're committing to
delivering, and this is the business
511
:impact that it's going to drive.
512
:And so that might just be like.
513
:One or two things across marketing,
sales, and CS that we, we commit to.
514
:And, we can shift, if something changes,
we don't mind pulling that out or
515
:getting feedback and swapping things
around just to make sure we're aligned.
516
:But we've found that planning too
far out, like it just, the roadmap
517
:gets pulled and changed so much.
518
:The team loses morale.
519
:So we found that just being
more agile upfront works for
520
:us.
521
:Justin Norris: In a high velocity,
high growth organization, it can kind
522
:of be a waste of time to plan too far.
523
:That's what I've observed
524
:Lindsay Rothlisberger: Yeah,
525
:Justin Norris: It's not worth the
paper that it's written on anymore.
526
:you mentioned impact and that can
be something that is difficult
527
:for some revenue operators.
528
:To like, like aside from saying we closed
so many tickets or we launched so many
529
:campaigns or we did so many projects
really tying your work to impact.
530
:How do you think about that?
531
:Lindsay Rothlisberger: we use two I
guess, frameworks for how we do this.
532
:One is did we add new
functionality or capabilities?
533
:it's a little bit trickier sometimes
to tie to revenue, but if we can
534
:unlock a huge motion and literally
do something that we couldn't
535
:do before, like outbounding, for
example, if you don't have the
536
:tools to do that, you can't do it.
537
:So we will sometimes latch on to like
features or capabilities as like.
538
:Business value or business
impact that we're delivering.
539
:and then we do also try to speak about
our wins under the lens of, additional
540
:sales capacity or selling time or
like, ROI on marketing dollars spent,
541
:like we will, Even if it doesn't
have to be scientific in most cases.
542
:Like I think you can really
get the point across about
543
:your value as an organization.
544
:If you're just making sure that you
include that, why was this worth it?
545
:Because we saved you from hiring another
salesperson basically, because now you're
546
:working deals that are going to close.
547
:You're spending, less amount
of time closing those deals.
548
:we really try and focus on like, what's
the profitability that we drove, like
549
:whether it be additional sales capacity,
or like, Just time saved, which is pretty
550
:easy to like, put some math behind and
say like, that equals this in revenue.
551
:And that doesn't even, include
additional deals when it's literally
552
:just like time we've saved per employee,
553
:Justin Norris: And it sounds like
you're also thinking a lot about
554
:things like, deal cycle length deal
value, I mean, that's one of the
555
:really nice things I like about PLG
and I've had some past experience
556
:working for a PLG company myself that
the automations that you can drive
557
:actually can like directly impact revenue
from a direct response point of view.
558
:Like you roll out a new
automation and then more people
559
:put their credit card down.
560
:And that's a really cool feeling
that, a lot of folks in an
561
:enterprise context don't always get.
562
:Lindsay Rothlisberger: 100 percent it's
really rewarding to be able to see, a
563
:small automation or optimization lead
directly to revenue rather quickly,
564
:especially for some of the, higher
velocity, low touch motions that We
565
:just had one very recently where a
marketing ops person was like, Hey, I
566
:think if we add another, like automated
sales touch for this lead type, I think
567
:we could drive like a lot of revenue.
568
:And it was like insane.
569
:She launched, it was very
small, very easy to do.
570
:And it like closed a gap and it
equated to pretty significant,
571
:like additional revenue number.
572
:So there's just so much opportunity,
I think, like when you have the
573
:volume and like the funnel to like,
we say obsess over, cause there,
574
:there's so many like potential drop
off points, which also makes the job
575
:harder too, because, you really have
to prioritize and make the right bets.
576
:Justin Norris: So I want to
geek out a little bit on, on
577
:like technology and data topics.
578
:cause you're in an automation space.
579
:Let's maybe start with, you mentioned
you're using HubSpot for your CRM.
580
:Is that also your marketing
automation platform?
581
:Lindsay Rothlisberger: Yes, it is.
582
:our tool stack is interesting.
583
:So we have had to, this was
like such a tough decision.
584
:Uh, when I we have.
585
:iterable, which is our email
tool, like our, it's a mass
586
:personalization email tool.
587
:It's really good at making hyper
personalized email experiences.
588
:so we had Arable when I joined,
we're starting to like experiment
589
:with human touch and sales brought
on the CRM and HubSpot, but we also
590
:didn't really have a true marketing
automation platform because we weren't
591
:really doing like B2B marketing.
592
:We were doing like More
of a like B to C, right?
593
:Like a more of a one to one.
594
:so yes, brought on, HubSpot
marketing automation and CRM and
595
:it's continued to scale for us,
which is pretty, pretty cool.
596
:and then we use intercom for chat.
597
:And then, Gong, LinkedIn sales, Nav,
Looker for analytics and Chili Piper
598
:to help with like our, lead management
and like instant booking capabilities.
599
:Justin Norris: It's interesting
that you mentioned that HubSpot
600
:has continued to scale for you.
601
:Cause I think there is this perception in
the marketplace like, yeah, it's HubSpot.
602
:It's good.
603
:But at a certain point
you'll have to migrate.
604
:And I had a chat with, a fellow named Rich
Archbold, who actually is of engineering
605
:for HubSpot's own internal GTM systems.
606
:And of course they use HubSpot too.
607
:And I asked the same question, like,
does it, was it scaled for them?
608
:So it means it was scaled for them.
609
:So maybe there is this,
misperception in the marketplace.
610
:what have you found in terms of like
scaling your business on HubSpot,
611
:any challenges, or is it actually
maybe the grass is sort of greener
612
:over here for some Salesforce folks?
613
:Lindsay Rothlisberger: Yeah.
614
:I mean, it's tough.
615
:Like we constantly go back and forth
and debate, has a great user experience.
616
:Like we, Yeah.
617
:And customer experience.
618
:We really just love the team over
there and just have had a great
619
:account manager for a long time.
620
:Technical support.
621
:and so we've really stretched the limits.
622
:I would say of HubSpot CRM where.
623
:We've got custom objects and we've got,
we're using like, all of the new features
624
:as soon as they release them to like,
be able to customize our sales process.
625
:But I would say we're, it's hard
for us to predict the future.
626
:But for now we have fairly simple
and straightforward sales motions
627
:that we're and proving out.
628
:And so for our use case, it
works really well for that.
629
:Some of the gaps that we've had are just
probably mostly around Some integrations,
630
:just are made, tailor made for Salesforce.
631
:but for us who use Zapier in our
back pocket for everything, like
632
:we've been able to use Zapier to like
sort of enhance our integrations.
633
:For example, with intercom,
like intercom to Hubsan.
634
:spot is fine, but like we, we have a
pretty customized workflow of how our
635
:sales team uses intercom and then how
those leads get pushed through to like
636
:other reps and customer success managers.
637
:So we, we use Zapier for that integration
or to like augment that integration.
638
:and again, I think We use
Zapier for a lot of different
639
:things across our go to market.
640
:so the combination of, and I
of course didn't even mention
641
:Zapier as part of our tool stack.
642
:but it combined with HubSpot
is very, it allows for a very
643
:customized experience and it's
644
:working for us.
645
:Justin Norris: So let's,
talk a little bit about that.
646
:Cause that's cool.
647
:And I think, the basics of creating
a zap are probably pretty familiar
648
:to most people who understand like if
this, then that type of functionality.
649
:One of the things I'm curious about is
when you start to roll out automations
650
:at a, a larger company, approaching
enterprise scale, It seems to me that
651
:it could get hairy in the sense of like,
the left hand not knowing what the right
652
:hand is doing and zaps contradicting
each other, overriding each other.
653
:What's the kind of governance or like
building framework, the architecture
654
:that you put in place to keep that
series of automations coherent.
655
:Lindsay Rothlisberger: so Zapier now does
at least have like admin capabilities.
656
:And so we have in our account,
like we have oversight over what
657
:apps are like connected to what and
what workflows are doing at a high
658
:level and, reporting around that.
659
:and so we have a member of our team
owns integrations at a whole and can
660
:see across all of our integrations, like
what's being updated by Zapier versus
661
:what is like a native integration or
what might be being updated by our ETL.
662
:So that's really through like
documentation and having a single, body
663
:like overseeing that full ecosystem.
664
:but I would say like the ways that we use
Zapier, in addition to like integrations,
665
:tied to our CRM are more of like little
mini applications to enhance our CRM
666
:that wouldn't have competing workflows.
667
:So for example, we have a series
of zaps that is a little like
668
:sales enablement, application.
669
:And what it does is it looks at
all of our like gong transcripts.
670
:So all of our call transcripts.
671
:It takes that data.
672
:It has an AI step that, our sales
enablement person set up that says
673
:like, okay, look at these calls and give
some constructive feedback for the rep.
674
:did they nail their negotiation or like
objection handling or like, did they
675
:talk about the Zapier value proposition?
676
:and that all goes into a Zapier table.
677
:That then each sales manager has access
to and can like quickly glance okay,
678
:what are the learnings I need to like
really like nail down with each member
679
:of my team and one on ones this week.
680
:And so that's an example of something
that we built with Zapier that
681
:customizes our CRM and connect
some of our different tools.
682
:But I'm not so worried about That
zap conflicting with something else.
683
:So I think the integration layer is like
one, but then there's also this Sales
684
:efficiency enablement layer of things
that we use Zapier for that is a little
685
:bit more the wild west to be honest.
686
:Like I let the team do what you
need to do, try and figure out,
687
:let's find some cool use cases here.
688
:and we haven't had an issue yet,
but, the oversight is important
689
:definitely for those like system of
690
:record
691
:updates.
692
:Justin Norris: I'd love to see a
screenshot of that SAP you described.
693
:Cause I was trying to build
something, uh, very similar.
694
:So you'll save me some time though, like
gong transcript to AI to table, workflow.
695
:that would be very handy
696
:Lindsay Rothlisberger: Awesome.
697
:I'll follow up.
698
:Justin Norris: I'm really curious
about like CRM data model and product
699
:signals and data, you mentioned having
a custom object for like accounts.
700
:Maybe let's just talk through like
how that's linked together and then
701
:how you're providing visibility on
product signals to, users of the
702
:Lindsay Rothlisberger: So this was tough.
703
:when we initially brought on a sales
motion because not only do they need
704
:access to data to like have the Good
conversations with their customers.
705
:Like they need to know how their customers
are using Zapier today to be able to have
706
:an effective like sales conversation.
707
:So that's one, but then when it
comes to like finding those moments
708
:in time, when a customer is ripe for
expansion or where like human touch
709
:could be really valuable, we're super
reliant on product signals for that.
710
:A challenging thing is we have a
lot of product signals and we need
711
:them in real time or near real time.
712
:And that wasn't a capability for us,
in terms of like our data architecture
713
:until more recently, until we
brought on sales and really had to
714
:like, be intentional about that.
715
:but it can be very expensive.
716
:You can't send all of
that data in real time.
717
:so you have to be really smart about
like what data matters, what data
718
:you need in real time versus when.
719
:Yeah.
720
:Just 24 hours is fine.
721
:And then we can use our normal sink.
722
:what we do, it kind of varies
depending on the product signal.
723
:but we do sometimes use Zapier to send a
product signal into HubSpot, in particular
724
:to like validate and see is this signal
leading to the outcomes that we want?
725
:Like, are those sales
conversations, successful?
726
:so with the product signal side of it,
that has been looped into that motion
727
:that I mentioned earlier, where we have
the tiger team who figures out what
728
:products signals matter, and that's why
it's so important for RevOps to be in the
729
:room so that we can help orchestrate the
data to do that, because in most cases.
730
:We don't have all the data
in our CRM necessarily.
731
:Like at this point we've got the
things that we know matter, like
732
:someone activated his app or
somebody connected a system of
733
:record or a CRM, things like that.
734
:We've had to orchestrate and build over
time once we validated that worked.
735
:Justin Norris: do you have a separate
table of product signals or do you
736
:have just fields on the HubSpot
contact record or account record?
737
:Where does that sort of data live?
738
:Lindsay Rothlisberger: it varies.
739
:typically does live in our
CRM at the contact level.
740
:So at the contact level, a
user takes a specific action.
741
:it's synced over into HubSpot.
742
:It might run a workflow that activates a
campaign like a automated sales outreach.
743
:in a lot of cases too, there's a
whole process that needs to run
744
:where say it's the signal is a
zap was activated or specific type
745
:of zap, zap activated by user.
746
:Send signal to, HubSpot CRM attached
to user, assign a user as a lead to a
747
:particular sales rep, send an automated
sales outreach email, if that's what
748
:we want to do in some cases, we might
actually send sales a notification
749
:and then they will reach out.
750
:So it depends on the campaign.
751
:but then we also.
752
:aggregate those product signals at the
company level or at the organization
753
:level so that when a rep is looking
at an account it can see like oh well
754
:this account has five zaps activated
around this particular use case so
755
:that they can also have like a Good.
756
:And like productive
conversation with that company.
757
:but it's taken us a lot of time and
really like focused effort, not only
758
:to figure out like what signals,
but like how quickly we need them,
759
:how we're going to orchestrate them.
760
:Do we want to use Zapier?
761
:Do we want to use high touch
our ETL or, some other way.
762
:So, it's been a, definitely
a work in progress.
763
:Justin Norris: The roles and
responsibilities of different systems gets
764
:really complex, when you have multiple
options and paths and that sort of thing.
765
:Lindsay Rothlisberger: Yeah, absolutely.
766
:And this is another area where we
have a sort of a working group.
767
:So we have, a data warehouse
engineer and, someone on our team
768
:and RevOps and, a product manager
who actually like oversees our.
769
:platforms like internal infrastructure.
770
:and so they form a little working
group where Revops plays this role
771
:where we're translating business needs.
772
:into technical requirements.
773
:So like in the past, I think without
Rev Ops in this situation, I think it
774
:would be really challenging for the
data warehouse engineer to understand,
775
:do we need this in real time?
776
:Sales is always going to
say, yeah, we need it in
777
:real time.
778
:but Rev Ops plays this really like
complimentary role in that scenario where
779
:we can like really look at like, what
does the business need in this scenario?
780
:What is the path of least
resistance to get there?
781
:and how do I coordinate with
data and engineering on that?
782
:And if you think about to like product
signals and new products, sometimes we
783
:won't even have the event that measures
that signal available, in which case
784
:we need an engineer to go build that.
785
:And so I could probably do a whole session
or someone on my team who focuses on
786
:this could do a whole session on like
the evolution of that relationship.
787
:But we do have some standardization
now where we know if it's this type
788
:of product signal for this type of
campaign, it's going to be seen,
789
:it's going to be set up in this way.
790
:So
791
:Justin Norris: that is so interesting.
792
:And, we could probably go a lot deeper
down that path, but I know we are out
793
:of time and I just want to say thank
you for popping the hood and taking
794
:us inside the engine that you built.
795
:It's super cool.
796
:And it honestly sounds like a lot of fun.
797
:So, I hope it's as enjoyable
as it sounds like day to day.
798
:Lindsay Rothlisberger: absolutely.
799
:I have an amazing team, so it's
all them, but it's been a really,
800
:really fun intellectually challenging
experience to like transition from.
801
:B2B marketing to something like this.
802
:But, we're going to see a lot of
companies start to go this route.
803
:So I'm honored and grateful that I've had
the opportunity to learn in this, case.
804
:So thank you.
805
:Thanks for having
806
:me.
807
:Justin Norris: so much
for being on the show.