Artwork for podcast RevOps FM
A Quote-to-Cash Masterclass - Nicholas Rose and Tony Tarantino
Episode 463rd September 2024 • RevOps FM • Justin Norris
00:00:00 00:48:16

Share Episode

Shownotes

Quote-to-cash: it's messy, it's technical, and every project takes WAY longer than planned.

It's also absolutely vital. If you can't get quotes out the door, or if you can't collect money from your customers, you don't have a business.

Because of their complexity, these systems tend to change infrequently, and in-house operators may not get the repetitive exposure necessary to master the intricacies of CPQ or billing system projects.

So when I wanted a crash course on quote-to-cash, I turned to Nick and Tony at Hyperscayle—former operators who've built a RevOps agency with a focus on lead-to-cash operations.

We go deep into the process and systems, discuss technical gotchas, and explore the change management issues that must be addressed to make quote-to-cash work smoothly.

Thanks to Our Sponsor

Many thanks to the sponsor of this episode - Knak.

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

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

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

Try Knak

About Today's Guests

Nicholas Rose is Co-Founder of Hyperscayle, a RevOps consulting firm covering lead-to-cash operations. He's previously held senior operations roles at Dell and Mendix (acquired by Siemens AG).

Tony Tarantino is Chief Architect at Hyperscayle. Previously, he was a technology consultant at Accenture and application architect at Mendix.

Key Topics

  • [00:00] - Introduction
  • [00:56] - Making the jump from in-house to agency
  • [05:17] - Quote to cash definitions
  • [10:25] - Design phase and cross-functional alignment
  • [14:06] - When does a company need CPQ
  • [16:41] - Why are CPQ projects so messy
  • [22:34] - Product configuration
  • [28:01] - Ideal tech stack
  • [32:26] - Data quality and deal desk
  • [36:20] - Role of RevOps

Thanks to Our Sponsor

Marketers: it's planning season. Time to live in your office with the world's biggest spreadsheet and hope that finance doesn't slash your budget.

Planning is tough, but at least you can put your best foot forward with a structured framework that covers all the bases. Our friends at Uptempo have just launched the Blueprint for Marketing Planning.

It's a totally free and comprehensive guide for enterprise marketing teams. You'll get a seven-step planning process that integrates top-down strategy with bottom-up execution and gives you a crystal clear picture of how you'll hit your number.

Get your free copy now:

Uptempo Planning Guide

Resource Links

Learn More

Visit the RevOps FM Substack for our weekly newsletter:

Newsletter

Transcripts

Justin Norris:

Welcome to RevOps FM.

Justin Norris:

Today, we're going to tackle a subject that is not for the

Justin Norris:

faint of heart, quote to cash.

Justin Norris:

It's tough.

Justin Norris:

It's technical, it's complicated.

Justin Norris:

so we're going to chat with two guys who are some of the best in the business, Nick

Justin Norris:

Rose and Tony Tarantino from Hyperscayle.

Justin Norris:

I've actually known Nick and Tony for quite a while.

Justin Norris:

They were clients of mine back when I was on the agency side.

Justin Norris:

They worked for a SAS company called Mendix later acquired by Siemens.

Justin Norris:

But now for the past few years, Nick and Tony have been building their own

Justin Norris:

RevOps agency called Hyperscayle where quote to cash is a big area of focus.

Justin Norris:

So I'm super excited to deep dive on this topic today.

Justin Norris:

Fellas, welcome to the show.

Nicholas Rose:

Thanks.

Nicholas Rose:

funny how things have turned.

Justin Norris:

it really is.

Justin Norris:

I mean, before we dive into the theme of the day, I'd love to And the

Justin Norris:

process from your point of view of going from the in house world, setting

Justin Norris:

up your own shop, what drove you there, the challenges, just love to

Justin Norris:

hear a little bit about that journey.

Nicholas Rose:

Yeah.

Nicholas Rose:

So, we got bought by Siemens and, Tony's worked for Accenture.

Nicholas Rose:

I worked for Dell.

Nicholas Rose:

We've been in the large corporation side for a very long time.

Nicholas Rose:

We both went to the startups.

Nicholas Rose:

Side and done successful.

Nicholas Rose:

We got to a buyout, but the question really kind of came up

Nicholas Rose:

for like, what's the next thing.

Nicholas Rose:

And, you we really wanted to be into Rev Ops overall into the Rev Ops space.

Nicholas Rose:

personally, I was looking out and interviewing and I couldn't

Nicholas Rose:

find a place that I wanted to go work for personally, because they

Nicholas Rose:

all had some of the same issues.

Nicholas Rose:

And I just didn't want to go the same rim and order of going through the

Nicholas Rose:

same process and Not really have a lot of control in playing the politics.

Nicholas Rose:

and and I were sitting on the train and Ben's like, why don't

Nicholas Rose:

we just start our own company?

Nicholas Rose:

And I was just like, you are crazy.

Nicholas Rose:

and you know, after more and more, some certain things

Nicholas Rose:

happen at Midnix and Siemens.

Nicholas Rose:

And I was like, you know what, let's go do it.

Nicholas Rose:

Right.

Nicholas Rose:

we started off, on our own, mainly because we want to have more control

Nicholas Rose:

in our own destiny and kind of create a culture of what we wanted a company to be.

Nicholas Rose:

and so we did that and it has been amazing.

Nicholas Rose:

If you ask me, we would be where we are today.

Nicholas Rose:

I would tell you.

Nicholas Rose:

No, but we have been growing like crazy, and having a lot of fun really

Nicholas Rose:

trying to solve more of customers big pain points and problems.

Nicholas Rose:

and you know, it's been great.

Nicholas Rose:

Tony.

Nicholas Rose:

I don't know if you want to add anything to that.

Tony Tarantino:

Yeah, the big thing for me was, as like we scaled Mendix,

Tony Tarantino:

you know, we started at a 50 percent company to, I think it was close to 5,

Tony Tarantino:

000 when we left, did a lot of things right, made a lot of mistakes, learned

Tony Tarantino:

a lot of lessons, I wanted to take those lessons and apply them elsewhere, and

Tony Tarantino:

this was the perfect opportunity to do so, was to learn from all the things

Tony Tarantino:

we did right and all the things we did wrong, and Help other companies,

Tony Tarantino:

but the fact that that foundation to scale from a boss perspective in place.

Tony Tarantino:

And I thought that was a super fun challenge to solve.

Tony Tarantino:

And every company is a little bit different, but it's still the basis

Tony Tarantino:

of getting your data in place, getting your process in place,

Tony Tarantino:

getting your systems in place.

Tony Tarantino:

And I just love that challenge and be able to do it over and over and

Tony Tarantino:

over again is super exciting to

Tony Tarantino:

me.

Justin Norris:

I've been through a bit of that agency experience myself

Justin Norris:

and there's, when you think about like your product and positioning and like

Justin Norris:

you're So you're a new product, right?

Justin Norris:

So I'm curious about what your, your menu of service offerings is going to be.

Justin Norris:

There's a few different ways to play it.

Justin Norris:

In my past life, we were really focused on one platform and

Justin Norris:

going deep into that ecosystem.

Justin Norris:

And you've chosen more of like a, discipline strategy where you're going to,

Justin Norris:

you're focused on RebOps as a discipline.

Justin Norris:

You have a broad menu of products that you partner with.

Justin Norris:

How did you think about what sort of agency you wanted to be

Justin Norris:

in terms of service offering?

Nicholas Rose:

Oh, it's a good question.

Nicholas Rose:

I don't know if we really thought much about it, To be honest, it was like,

Nicholas Rose:

we know we were good at lead to cash.

Nicholas Rose:

I knew marketing ops and sales ops really well.

Nicholas Rose:

And even customer success ops, we had people that can play in all those areas.

Nicholas Rose:

And, I think one of the things that we've centered around was, is it's

Nicholas Rose:

really hard to have marketing ops people.

Nicholas Rose:

Work on systems and not have a downstream impact.

Nicholas Rose:

They don't know what happens like on the Salesforce or CRM

Nicholas Rose:

side and vice versa, right?

Nicholas Rose:

There's been countless of times when even bigger companies are doing

Nicholas Rose:

something on the sales side and they mess up the marketing side, right?

Nicholas Rose:

Because they don't know the downstream or upstream impacts.

Nicholas Rose:

And so I think, where I kind of mean, Tony drew the line the same.

Nicholas Rose:

It was like, we're going to go do this.

Nicholas Rose:

We're going to do lead to cash.

Nicholas Rose:

And this is going to be our competitive advantage.

Nicholas Rose:

and we're going to know what happens from downstream and upstream.

Nicholas Rose:

And so I think it was just more like, this is who we are and what

Nicholas Rose:

we're going to be in particular.

Nicholas Rose:

We want to rev ops.

Tony Tarantino:

My perspective, I'm a huge believer in understanding the end to

Tony Tarantino:

end business process of every client that I work on, like, I want to understand.

Tony Tarantino:

From market to cash, like how data flows, how it's structured,

Tony Tarantino:

the architecture of the systems.

Tony Tarantino:

And if we're going to do that, we're going to spend the time

Tony Tarantino:

and learn all that information.

Tony Tarantino:

It might as well support all those elements of that process as well.

Tony Tarantino:

So that was like a, big driver for me.

Tony Tarantino:

It's like, we're moving the silos and making sure that we're thinking about

Tony Tarantino:

every project, every solution, every functionality that we build as kind of

Tony Tarantino:

a, How it impacts not only the individual piece of the process that we're working

Tony Tarantino:

on, but downstream and upstream.

Justin Norris:

I think there's huge advantage to being able to position

Justin Norris:

yourself as solving a business problem rather than being like, I'm your Mercato

Justin Norris:

shop or I'm your HubSpot shop or whatever.

Justin Norris:

So I want to dive into the big picture of quote to cash.

Justin Norris:

And I'll confess it's not an area that I'm super well versed in.

Justin Norris:

I've touched bits and pieces of it in different ways, but taking on,

Justin Norris:

the standard, big process of rolling out CPQ and rolling out some of these

Justin Norris:

systems, it's not something I've done.

Justin Norris:

So I'd love, for the benefit of myself and perhaps others who haven't gone

Justin Norris:

deep there, maybe just set the stage for what this is, why it's important.

Nicholas Rose:

so kind of let's start with the definitions between Quote

Nicholas Rose:

to cash and cpq right because they're usually insomnious together, but they

Nicholas Rose:

really usually do separate projects, And some of it's kind of obvious,

Nicholas Rose:

But I think when people go into these motions, they kind of gets lost,

Nicholas Rose:

especially within the organizations.

Nicholas Rose:

But quote to cash is really the business process from, you know,

Nicholas Rose:

obviously, when sales creates a quote or configure something like that.

Nicholas Rose:

And then it goes into what we, you know, we say, Cash, which would be

Nicholas Rose:

trained from an opportunity into a quote, into an order or invoice, and

Nicholas Rose:

then the collections process right between the business side, right?

Nicholas Rose:

So capturing that from a net suite or ERP system for the money, Not

Nicholas Rose:

really sexy money means, right?

Nicholas Rose:

But like, those are the pieces, And there's a lot of business

Nicholas Rose:

process that goes underneath that, which makes it complex.

Nicholas Rose:

Because you're usually having to bring in sales, could be marketing,

Nicholas Rose:

depending on where it sits, which some people don't realize, right?

Nicholas Rose:

Especially if you're like a product or product marketing side standpoint,

Nicholas Rose:

operations, but in finance.

Nicholas Rose:

Now, the CPQ section, configure price quote, usually the details around.

Nicholas Rose:

how do you get sales to create a quote, configuring out and getting into the part

Nicholas Rose:

of that, which is a sub piece of that process, but it's also really important,

Nicholas Rose:

Because when you talk about getting things to move harmoniously between the systems,

Nicholas Rose:

you know, very good example, like usually your CPQ and ERP systems have to mirror.

Nicholas Rose:

And if you don't do that process, well, you can create a lot

Nicholas Rose:

more work for your manual work.

Nicholas Rose:

Right.

Nicholas Rose:

But that business process is important because it all ties

Nicholas Rose:

back into the CBQ process.

Nicholas Rose:

that's kind of like setting the stage there.

Nicholas Rose:

and you know, really, it's important is especially when you

Nicholas Rose:

do it from a scaling perspective.

Nicholas Rose:

I feel like 20 salespeople or 50 salespeople, a lot of times they don't

Nicholas Rose:

have a coding process, but that's when they'll kind of like start looking

Nicholas Rose:

into it because the cost savings and the time for them to somehow do

Nicholas Rose:

some of these quotes, especially if they're complex, just becomes way more

Nicholas Rose:

worth it or configuring out costs.

Nicholas Rose:

Like some of the times we've done these CPQ systems because.

Nicholas Rose:

There's a business problem on say, like the warranty or the support

Nicholas Rose:

side, and it's costing them millions of dollars to go fix this as support

Nicholas Rose:

because sales is selling something incorrectly or wrong or missing the item.

Nicholas Rose:

And from a CSI, they have to go support that.

Nicholas Rose:

Right.

Tony Tarantino:

I think the other thing that I would add is how often

Tony Tarantino:

I've seen clients, who have the sales process, well documented, well

Tony Tarantino:

figured out, well implemented in their systems, but we're leaving so much

Tony Tarantino:

money on the table because everything post sales, they weren't focusing on.

Tony Tarantino:

And that's so important because that's how you're getting paid.

Tony Tarantino:

That's how you're generating cash.

Tony Tarantino:

That's how you're invoicing your customers.

Tony Tarantino:

It's such an important part of, your total go to market process.

Tony Tarantino:

That is sometimes especially technically underserved, like there's companies

Tony Tarantino:

that have full Salesforce CRM teams that Have one part time Netsuite consultant

Tony Tarantino:

who's not handling the ERP stuff at all.

Tony Tarantino:

it's a really, really important process that is actually

Tony Tarantino:

doing the revenue generation.

Tony Tarantino:

It is invoicing that you are getting paid for that, always amazed about

Tony Tarantino:

how so many companies don't focus enough and are missing thousands of

Tony Tarantino:

dollars because they don't have their invoice process buttoned up and aren't

Tony Tarantino:

getting the revenue that they need.

Nicholas Rose:

And like, the industry's kind of like monetize it in some ways.

Nicholas Rose:

But it's really complicated because like, no one really owns the CPQ

Nicholas Rose:

process if you think about it.

Nicholas Rose:

But then everyone also owns it because usually the people that have to control

Nicholas Rose:

it only control bits and pieces of it.

Nicholas Rose:

that's what makes it really complicated.

Nicholas Rose:

So like finance would own like the approval process, but usually sales

Nicholas Rose:

wants to own the approval process.

Nicholas Rose:

And a lot of times we'll have troubles with that because everyone

Nicholas Rose:

wants to be in the approval process.

Nicholas Rose:

And usually you have 13 people in the approval process.

Nicholas Rose:

It's like, guys, you can't have 13 people.

Nicholas Rose:

But those are the humans that aspects into that because everyone wants to touch it.

Nicholas Rose:

And then you get to things like product or product market.

Nicholas Rose:

Like someone has to define the playbook that encapsulates what actually

Nicholas Rose:

needs to be configured and priced.

Nicholas Rose:

And a lot of times people don't have that figured out or the

Nicholas Rose:

structure or strategy to go to that.

Nicholas Rose:

someone else owns that.

Nicholas Rose:

And usually you have ops in the middle, like going like, Hey, we need

Nicholas Rose:

to push this together and try to push and pull these organizations, but

Nicholas Rose:

they don't understand the full piece.

Nicholas Rose:

that's makes it, So complicated.

Nicholas Rose:

no one owns it, but everyone does at the same

Tony Tarantino:

CPQ.

Tony Tarantino:

I think it's truly the single hub that is relevant to every single go

Tony Tarantino:

to market group that there is like sales, marketing, finance, CS, all

Tony Tarantino:

have a really, really important.

Tony Tarantino:

Need for a CPQ that fills their needs.

Tony Tarantino:

So it's, a one thing and all of our go to market processes that literally touches

Tony Tarantino:

every single relevant group and with, obviously more people at the table, more

Tony Tarantino:

opinions, that's a lot of the struggles you see with CPQ is everyone's got away,

Tony Tarantino:

everyone's got an opinion on how it should go they have such a huge role.

Tony Tarantino:

It impacts their lives so much.

Tony Tarantino:

That's what makes this work really complicated.

Justin Norris:

you took it just actually where I was going to go, I was

Justin Norris:

just reflecting on all the different players involved product marketing

Justin Norris:

and defining those packages in many cases, sales actually being the ones

Justin Norris:

who have to work with them users of the system finance being stakeholders.

Justin Norris:

Cause everything that has to mirror over into the ERP world.

Justin Norris:

It's hard enough sitting down as like a marketing operations consultant or

Justin Norris:

sales operations consultant with just one or two stakeholders when you've

Justin Norris:

got four or five, six departments, what does that engagement look like for you?

Justin Norris:

Just from a design and discovery phase, that must be fun.

Nicholas Rose:

So one of the things that we always require is an executive leader

Nicholas Rose:

and the executive leader has to sit above everyone because installing or setting

Nicholas Rose:

up the technology for CBQ is not hard.

Nicholas Rose:

I would say in a lot of sense, and Tony will jump in and probably say, there's

Nicholas Rose:

some subtle nuances and things like that.

Nicholas Rose:

But like, we're not doing rocket science, The things that make it harder where

Nicholas Rose:

delays come from are people and it's usually politics, That comes out of it

Nicholas Rose:

most, and I'll give a great example.

Nicholas Rose:

You know, we've had two times.

Nicholas Rose:

It's like who owns what the product book needs to look like.

Nicholas Rose:

And if you haven't had a clear product definitions of how you want to go

Nicholas Rose:

sell something, how is the system supposed to handle it and take it?

Nicholas Rose:

And how is sales are supposed to handle and can vote and

Nicholas Rose:

configure and quote that, right?

Nicholas Rose:

Especially if you're supposed to define what's on the back of

Nicholas Rose:

the truck, so to speak, right?

Nicholas Rose:

For sales.

Nicholas Rose:

Once the back of the truck is defined and that's where they can go sell,

Nicholas Rose:

lot of times we'll use some of this is like cells is selling a deck.

Nicholas Rose:

They don't care what nails are in those skews, whatever else is in the

Nicholas Rose:

deck or how many pieces of lumber they know they're selling a deck.

Nicholas Rose:

You're selling a solution.

Nicholas Rose:

You guys need to tell them what's in that.

Nicholas Rose:

But if they don't have that configured, Sales doesn't if they need to sell a two

Nicholas Rose:

story deck or a three story deck, how much more weight do they need to go have?

Nicholas Rose:

That's not defined easy enough for a person to understand.

Nicholas Rose:

You're never going to have it in place enough for a system to understand,

Nicholas Rose:

especially if there's too many decisions.

Nicholas Rose:

And so like, that's one great example where I would say probably 60 or 70

Nicholas Rose:

percent of CPQ projects like stall is ones like everything else is

Nicholas Rose:

specialized or they don't really have that defined yet for what, like the

Nicholas Rose:

80, 20 rule exists for their company,

Tony Tarantino:

You asked a question about, how the design process goes and

Tony Tarantino:

it made me chuckle but I think the design process always goes really smoothly.

Tony Tarantino:

all the people at the table are very excited about, Oh, we can automate

Tony Tarantino:

approvals and we can, remove all of these clicks I have to make.

Tony Tarantino:

And my email is going to decrease.

Tony Tarantino:

It's going to be great.

Tony Tarantino:

I love letting the system do the work, but it always breaks down when

Tony Tarantino:

it becomes real, like at the point of like, okay, now that we're no longer

Tony Tarantino:

going to remove Approvals from every single group of closed deal and you

Tony Tarantino:

have to trust the system to do its work.

Tony Tarantino:

That's when everyone freaks out and that's what actually slows down the deal.

Tony Tarantino:

So like early on, they love it.

Tony Tarantino:

They love the idea of automating.

Tony Tarantino:

They love the idea of being removed from the process, but as it gets closer and

Tony Tarantino:

they get to a real point where, oh, no, I don't, I'm not gonna have eyes on every

Tony Tarantino:

single deal that goes through our system.

Tony Tarantino:

I have to trust the system and trust the data.

Tony Tarantino:

That's when everyone like, Oh, I got it freaks out and decides

Tony Tarantino:

that we have to slow down and they get scared of that change.

Tony Tarantino:

That's so important.

Nicholas Rose:

Yeah, Tony makes a good point of this and that usually

Nicholas Rose:

times like, oh, well, we thought this work would be a lot quicker.

Nicholas Rose:

yeah, but by the time we get to this point of approvals, or we get to

Nicholas Rose:

this point of we need to go live.

Nicholas Rose:

We're not going to make that because everything that everyone's agreed on.

Nicholas Rose:

They're going to stop at the one yard line and we're gonna have to go

Nicholas Rose:

back and you as an executive leader is going to have to push them to

Nicholas Rose:

make sure that they're okay with it.

Nicholas Rose:

And that's really hard for some people.

Nicholas Rose:

If you don't have like an executive sponsor for a design process

Nicholas Rose:

to help force those decisions saying, this is where we go.

Nicholas Rose:

The design process is easy, but that piece gets really rough.

Justin Norris:

I'm curious if there's a dividing line between where you

Justin Norris:

would recommend a company needs this sort of infrastructure in place.

Justin Norris:

And when you're like, you're good.

Justin Norris:

Like I'm thinking of.

Justin Norris:

new company rolls out a product and maybe they've got like tiers, like,

Justin Norris:

freemium Pro team, just very simple and they don't have that many salespeople.

Justin Norris:

Is there a place for like you're good keep going for a bit more

Justin Norris:

and you don't need this yet

Tony Tarantino:

It very much, and I hate this answer, but it's

Tony Tarantino:

the answer I'm going to give.

Tony Tarantino:

It very much depends.

Tony Tarantino:

and I think CTQ specifically is so dependent on the complexity for

Tony Tarantino:

product offering that if you have a.

Tony Tarantino:

Fairly straightforward product.

Tony Tarantino:

thinking about like us at Mendex, okay.

Tony Tarantino:

It was, we sold a platform and that was it.

Tony Tarantino:

We never needed CPQ because it wasn't relevant regardless of how big we got.

Tony Tarantino:

but if you have a fairly straightforward product that you can get by a lot longer

Tony Tarantino:

without introducing complexity to the CPQ.

Tony Tarantino:

But that being said, like if you have a, a lot of specific bundles and

Tony Tarantino:

packages and product configuration rules and all these different things

Tony Tarantino:

that, you know, are important.

Tony Tarantino:

To success of your customers.

Tony Tarantino:

And then I would even say earlier is probably better, like

Tony Tarantino:

earlier than you would think a CPQ is necessary is important.

Tony Tarantino:

So like, again, a long, non answer, but, the idea is it very much depends on

Tony Tarantino:

how complex your product configuration is and how you're trying to sell it.

Nicholas Rose:

Yeah.

Nicholas Rose:

So my monetary answer back into like, depends on the

Nicholas Rose:

complexity of the product, right?

Nicholas Rose:

So if you have something that has a lot more quote mine items, right.

Nicholas Rose:

And the cost of getting that wrong is higher on the customer

Nicholas Rose:

support or service side.

Nicholas Rose:

And you're talking, you know, 200 and 500 K more cost to the business,

Nicholas Rose:

then there's probably a good reason.

Nicholas Rose:

Like you should go look at a CPQ system, right?

Nicholas Rose:

And that can be five reps, 10 reps.

Nicholas Rose:

It doesn't really matter.

Nicholas Rose:

It'll depend on the ASP, what you have, right?

Nicholas Rose:

But like, if you back into a system cost, you can get a CPQ system for

Nicholas Rose:

1500 K depending what you are for the volume of transactions, So like

Nicholas Rose:

from a customer standpoint, if that is a leakage in the funnel, that's

Nicholas Rose:

a great area to go at it from.

Nicholas Rose:

the sale side, if the cost of them from a time perspective is

Nicholas Rose:

saving them roughly around the same amount of costs in time, right?

Nicholas Rose:

And it's easy way to go figure out if you cut the quoting processed for rep down to

Nicholas Rose:

an hour, hour times the number of costs.

Nicholas Rose:

600 hours that equals close to like, a hundred to 500 K.

Nicholas Rose:

And then, yeah, there's probably a good reason to go do a CPQ

Nicholas Rose:

from that standpoint, right?

Nicholas Rose:

Because your ROI is gonna be anywhere from like five to 10 X at that point, and it'll

Nicholas Rose:

be an easy scaling conversation, right?

Nicholas Rose:

that's the monetary answer backed into the complexity of the coding process.

Justin Norris:

It makes sense.

Justin Norris:

And so thinking about like CPQ as a system and just the process of rolling

Justin Norris:

that out, as I said, I've never done that hands on, but I've been adjacent to

Justin Norris:

many of them, most often in the context of like, we'd like to do this project,

Justin Norris:

but we have to wait till, you know, next fiscal year when the Salesforce

Justin Norris:

team is finished with their CPQ project, It's always this sort of like looming,

Justin Norris:

goblin under the bed or this, menacing thing that is going on in the background

Justin Norris:

somehow that's never going to end.

Justin Norris:

And so I'm just wondering why does this tend to be so bumpy and complicated?

Justin Norris:

We talked about the people side.

Justin Norris:

Are there other technical reasons?

Justin Norris:

Or is it really just, the organization ends up getting bogged down somewhere

Justin Norris:

along one of these milestones?

Nicholas Rose:

The organization usually gets bogged down on

Nicholas Rose:

one of these milestones, right?

Nicholas Rose:

And a lot of times.

Nicholas Rose:

there are technically and I'll go into technical pieces, right?

Nicholas Rose:

But they'll get bogged down and usually it's a lot of

Nicholas Rose:

rework back from the CPQ team.

Nicholas Rose:

But there are technical pieces and like if you're going to like

Nicholas Rose:

integrations between like a CBQ system within the CRM back to an ERP,

Nicholas Rose:

those get really complicated, right?

Nicholas Rose:

And a lot of times too, those systems have to mirror each other, right?

Nicholas Rose:

And there's like integration as tools such as like MuleSoft, and I usually would

Nicholas Rose:

recommend Boomi or something like that, those systems need to talk to each other.

Nicholas Rose:

Now, the problem that what makes it difficult is those systems have to sink.

Nicholas Rose:

What I mean by that is the product book that is in CRM has to match the

Nicholas Rose:

product book in the finance side.

Nicholas Rose:

Oftentimes, when this is a first time install at a company that has not

Nicholas Rose:

done this, they usually don't match, And finance is not taking an easy way

Nicholas Rose:

of looking at it for the contracts or something else for invoicing.

Nicholas Rose:

And the sake of simplifying the process.

Nicholas Rose:

Or sales has done something different from what finance has, but

Nicholas Rose:

like that takes time to match up.

Nicholas Rose:

And so like, we're going through a great example where we're having

Nicholas Rose:

to amend and do all the contracts for our customer back and rewriting

Nicholas Rose:

them back into the ERP system.

Nicholas Rose:

So when we go back into the CPQ, they match back for when

Nicholas Rose:

a item gets sent across as a sales order back into NetSuite.

Nicholas Rose:

And so like, those are some of the technical pieces that happen

Nicholas Rose:

that from a business process are.

Nicholas Rose:

Arrive because they weren't doing it correctly, but that labor or

Nicholas Rose:

work has to happen to get it right.

Nicholas Rose:

And sometimes people don't realize that when they do the CPQ project,

Nicholas Rose:

because not a lot of people in the company, however, go do one, right?

Nicholas Rose:

you're not like installing CPQs every year, right?

Nicholas Rose:

So you don't have a lot of experience of that.

Nicholas Rose:

And that's why you should look at an agency, but those are the things

Nicholas Rose:

that happen that slow it down.

Tony Tarantino:

Yeah.

Tony Tarantino:

I think a couple of things come to mind for me.

Tony Tarantino:

And I think that the big one, I mean, we talked about kind of the product catalog

Tony Tarantino:

and make sure that's well defined that's obviously important, but there's Very

Tony Tarantino:

often I find so much tribal knowledge that lives within sales groups, like

Tony Tarantino:

how they sell things, how they configure their products, how they configure their

Tony Tarantino:

product, it's not documented at all.

Tony Tarantino:

you have a senior salesperson, it's all in their head.

Tony Tarantino:

And like the process of getting that out, making it real, making it systematic

Tony Tarantino:

enough where you can build logic to support that is always very cumbersome.

Tony Tarantino:

that's always a huge problem.

Tony Tarantino:

So many companies have these sales guys that just know how to quote

Tony Tarantino:

and they've been doing it for a long time and they have never written

Tony Tarantino:

it down and that's a process.

Tony Tarantino:

Another thing to Nick's point is that you have these organizations

Tony Tarantino:

that have Salesforce teams because they use Salesforce every day.

Tony Tarantino:

or CRM teams and buy Salesforce versus CPQ and they think they can just.

Tony Tarantino:

Automate Salesforce within their CPQ, not realizing like how different those

Tony Tarantino:

functionalities are, and they don't necessarily play super well together.

Tony Tarantino:

So I've seen a lot of my clients, have these really complex CPQ.

Tony Tarantino:

that's all like automated with flows and apex and just like really complex

Tony Tarantino:

Salesforce specific functionality while under leveraging all of the

Tony Tarantino:

CPQ stuff that's built to be CPQ.

Tony Tarantino:

So again, back to the point of.

Tony Tarantino:

Make sure that you understand and are experts in the system that you're

Tony Tarantino:

using for your CPQ and not forcing your automation that you know how to build

Tony Tarantino:

to work with CPQ because that's going to have dashering that that's big time.

Justin Norris:

Tony I'm just really curious as you described that to dig

Justin Norris:

into like a concrete example, you could make one up if you like, but what's

Justin Norris:

like a configuration process and what would be like the CPQ way of doing it?

Justin Norris:

And then how do people duct tape it with Salesforce automation?

Tony Tarantino:

Not to get too technical and bore our audience,

Justin Norris:

No, we can go, technical.

Justin Norris:

They won't be bored.

Tony Tarantino:

okay.

Tony Tarantino:

I think the big one that you see is when a quote is created, you

Tony Tarantino:

want to automate all of this stuff.

Tony Tarantino:

you want to, when a quote is created, you want to automate that automatically

Tony Tarantino:

add this product and get with this price point and configure this

Tony Tarantino:

together and do all of this stuff.

Tony Tarantino:

And because again, you know, Salesforce, you know, flow, it's a

Tony Tarantino:

very nice tool, very easy to use.

Tony Tarantino:

So go create a flow to go do that.

Tony Tarantino:

When reality.

Tony Tarantino:

CPQ, Salesforce CPQ specifically is a product built on force.

Tony Tarantino:

com, but has all this backend code that's running.

Tony Tarantino:

That's based on actual individual records, price rolls, product rolls.

Tony Tarantino:

So you basically go to the record, the tab in Salesforce, create a price roll.

Tony Tarantino:

Create a product rule and it will allow you to do all of that

Tony Tarantino:

logic, within the interface of CPQ, because that already exists.

Tony Tarantino:

If you automate on top of that, both of those pieces of logic are

Tony Tarantino:

functionality right at the same time,

Tony Tarantino:

and it's going to bog down your system.

Tony Tarantino:

So like once people do that and then their quotes get, Large in

Tony Tarantino:

their system times out all the time.

Tony Tarantino:

They're like, what's going on?

Tony Tarantino:

It's because you're basically automating on top of already existing automation

Tony Tarantino:

because you didn't, properly utilize actual built for CPQ piece of automation.

Nicholas Rose:

And we've seen this multiple times, like that timeout

Nicholas Rose:

happens and you see your whole Salesforce instance timing out.

Nicholas Rose:

And so you're like, oh, Apex timeout issues, your CPU issues.

Nicholas Rose:

You're like, wait, this is a cloud instance.

Nicholas Rose:

Like, why is this happening?

Nicholas Rose:

Right?

Nicholas Rose:

And it's because you basically cut it in half.

Justin Norris:

Yeah, that's weird.

Justin Norris:

Hey, so they kind of get a car and then they hook it up to horses

Justin Norris:

and get the horses to pull the car without turning on the car's engine.

Tony Tarantino:

That's a very, very good analogy.

Tony Tarantino:

Cause there are no horses and I get it.

Tony Tarantino:

Like I had no Salesforce.

Tony Tarantino:

I've been looking at Salesforce for a long

Tony Tarantino:

time.

Tony Tarantino:

I bought a Salesforce product.

Tony Tarantino:

I should be able to use Salesforce, but that's not the reality.

Justin Norris:

That's really interesting.

Justin Norris:

And so like a lot of the things that we're trying to configure when we

Justin Norris:

think of like price books and products.

Justin Norris:

Make these things up.

Justin Norris:

And it was just in a conversation today about, their product marketing

Justin Norris:

team, like how many different ways you can slice and dice this.

Justin Norris:

You can have different plans that include features.

Justin Norris:

You can have core products and then like upsell products.

Justin Norris:

you can, Take the stuff that your system or your, product offering does and

Justin Norris:

arrange it in a lot of different ways.

Justin Norris:

do you technically see that this is under developed or is it over architected,

Justin Norris:

over engineered and should be simplified?

Justin Norris:

How do you see the impact here from a product marketing point of view?

Nicholas Rose:

I wouldn't necessarily say from product marketing, I have seen where

Nicholas Rose:

it gets away from product marketing and it gets overdeveloped, Like when you consider

Nicholas Rose:

like partner skews, Oh, well, we need to give every option to partner because

Nicholas Rose:

we need to give every option partner.

Nicholas Rose:

We create 15, 000 different bundles.

Nicholas Rose:

Nobody asked the question like, Oh, how many are they actually going to sell?

Nicholas Rose:

So then you end up only using like five skews out of a hundred and

Nicholas Rose:

everything else, which creates a more to maintain, um, in a bigger

Nicholas Rose:

playbook and everything else.

Nicholas Rose:

But when it gets out of hands for product marketing, some point, But most of the

Nicholas Rose:

time it'll be overcomplicated, right?

Nicholas Rose:

Oh, we need to have different versions because of this edge case to sell.

Nicholas Rose:

Well, sales doesn't feel really confident that they need to have every option in

Nicholas Rose:

case they go down to, well, no sales.

Nicholas Rose:

It goes back down to the 80, 20 rule.

Nicholas Rose:

Like you guys only sold two of these bundles in the year.

Nicholas Rose:

And so like, think a lot of people will come with like anecdotal evidence, not

Nicholas Rose:

really looking at factual information.

Nicholas Rose:

And so either way you go through the process, you have it for a year

Nicholas Rose:

and you go, all right, guys, this is how many bundles you actually

Nicholas Rose:

sold to this and then cut it.

Nicholas Rose:

But most of the time I see him being overly complicated.

Nicholas Rose:

I haven't really seen any prompts from people's overly simplifying it.

Nicholas Rose:

I mean, have you told me, I can't imagine any

Tony Tarantino:

I could, it's not necessarily overly simplifying, but I

Tony Tarantino:

do have a number, numerous examples in my head of companies that are paying for

Tony Tarantino:

CPQ and their CPQ instance is just a long list of products that their salesperson

Tony Tarantino:

are going in and searching for the right one and adding it, like, there are

Tony Tarantino:

scenarios like that where, because they don't have that process well defined,

Tony Tarantino:

they're just, I've done the bare minimum of CPQ and maybe are just using it for

Tony Tarantino:

the approval side of the house, which again, it may be there's a use case there.

Tony Tarantino:

There are elements of not using the capabilities.

Tony Tarantino:

Of CPQ as they're built meant to be used.

Tony Tarantino:

And I've seen that plenty of times as well.

Tony Tarantino:

there's honestly, I was thinking about it as you're asking that question and

Tony Tarantino:

I've seen both sides of the equation very often where it's like, see a lot

Tony Tarantino:

of like, why is this so complicated?

Tony Tarantino:

Your business process is that it's not that unique.

Tony Tarantino:

And also a lot of other ones that are like.

Tony Tarantino:

paying a lot of money for this application.

Tony Tarantino:

You're not really using it as it's meant to be used.

Tony Tarantino:

So I've definitely seen both sides of the coin for

Justin Norris:

Do you guys have a preferred like Goldilocks zone between

Justin Norris:

the place where every single feature is almost like its own product and.

Justin Norris:

as you're describing that.

Justin Norris:

I'm like, well, you could really just could use native Salesforce quotes

Justin Norris:

and native Salesforce products and just like build it up, you know, like

Justin Norris:

a list of ingredients in a recipe.

Justin Norris:

So there's that extreme.

Justin Norris:

And then there's the other extreme where like every single possible combination

Justin Norris:

is like bundled as a separate SKU and you have the 15, Like you also described,

Justin Norris:

what's the happy path in between there that gives you some efficiency of things

Justin Norris:

already being put together without making it too rigid hard to adapt to.

Tony Tarantino:

It's honestly a really good question.

Tony Tarantino:

It's something that we're still trying to figure out because again, it is complex.

Tony Tarantino:

and I think with CPQ specifically, because it's so dependent on,

Tony Tarantino:

again, the products and the product configuration, it all goes back to

Tony Tarantino:

that kind of monetary quantitative calculation you need to go do of like.

Tony Tarantino:

If I were to bundle this out, how many deals am I making a year with

Tony Tarantino:

this particular configuration?

Tony Tarantino:

How much money is it?

Tony Tarantino:

How much time does it save my salespeople?

Tony Tarantino:

there things that are often left off that is costing us revenue down the line?

Tony Tarantino:

Like, it's really about finding those pain points and understanding,

Tony Tarantino:

quantitatively, like, where can we use our system to minimize time

Tony Tarantino:

that our salespeople are spending?

Tony Tarantino:

Minimize mistakes, and I think that's kind of where you find that answer, and there's

Tony Tarantino:

not really a one size fits all here.

Tony Tarantino:

I don't think it's all about the complexity of the product and in the

Tony Tarantino:

pains that they're currently feeling.

Tony Tarantino:

all about doing that double click.

Tony Tarantino:

And that's why discovery and understand the end to end process is so important

Tony Tarantino:

because I need to understand.

Tony Tarantino:

What is their driver?

Tony Tarantino:

Why are they doing this?

Tony Tarantino:

What are their go to market process?

Tony Tarantino:

Like, what are their salespeople actually selling?

Tony Tarantino:

And when I do CPQ projects, I listen to sales calls.

Tony Tarantino:

I will take time and I will just listen to how are the salespeople talking

Tony Tarantino:

about this product to their clients?

Tony Tarantino:

Like, how are they bundling these conversations?

Tony Tarantino:

I think it's really, really important in, telling me what I need to know about

Tony Tarantino:

how they're thinking about it is how I want to make sure that I build it.

Tony Tarantino:

So their language is.

Tony Tarantino:

Yeah,

Justin Norris:

Right.

Justin Norris:

Cause for SAS, you have to mirror the selling process.

Justin Norris:

It's not like with your deck example, and I have a, brother in law who's a carpenter

Justin Norris:

and builds decks and he's kind of got it in his head where you can say, all right,

Justin Norris:

I'm going to build a deck, it's this big.

Justin Norris:

I know I need this much lumber, this many nails, this many screws.

Justin Norris:

Like you.

Justin Norris:

can kind of figure that out.

Justin Norris:

But with SaaS, it's like you can just do it any which way.

Justin Norris:

It's all just make believe, so to speak.

Nicholas Rose:

Well, and it gets even more complicated when you do

Nicholas Rose:

like software and product, right?

Nicholas Rose:

So there's a company we were worked with and did warehouse

Nicholas Rose:

spots and software along with that.

Nicholas Rose:

That's a really complicated selling process gets really costly too.

Nicholas Rose:

So going back to the Goldilocks answer, it really depends on the product and

Nicholas Rose:

offer anything more than anything else for the complexity of that.

Nicholas Rose:

but like, to your point, like that tribal knowledge, like someone knows it.

Nicholas Rose:

It's just, how do you pull it out and get it written down into a good structure?

Justin Norris:

So getting opinionated about tech for a second.

Justin Norris:

Do you have an ideal stack?

Justin Norris:

No budget, just put in the best of breed for CPQ tech.

Justin Norris:

What would your stack look like?

Nicholas Rose:

I think it depends on what is the CRM and what is the ERP,

Nicholas Rose:

those are the first two questions, because a lot of times we see a

Nicholas Rose:

lot of Salesforce and NetSuite.

Nicholas Rose:

then the next question comes down to is like, how complicated is the quote

Nicholas Rose:

and how many line items for the quote?

Nicholas Rose:

if they're in HubSpot, like, I mean, the HubSpot feature for quoting is can

Nicholas Rose:

get you pretty far, honestly, most of the feature sets in HubSpot, right?

Nicholas Rose:

It goes, it's a mile wide and it goes an inch deep, but like a lot of

Nicholas Rose:

people don't need much more than that.

Nicholas Rose:

So I think those are the questions we ask is like, all right,

Nicholas Rose:

how complicated is the quote?

Nicholas Rose:

What CRM instance in ERP?

Nicholas Rose:

So then, it's not a really complicated, quote process.

Nicholas Rose:

I would stick to like a Salesforce or Steelbrick, Because still, I like it.

Nicholas Rose:

It's nice in that sense, because.

Nicholas Rose:

You don't have to do a lot of customization.

Nicholas Rose:

It's pretty, like, straightforward.

Nicholas Rose:

on the quote guide path.

Nicholas Rose:

for most businesses, it will work really, really well.

Nicholas Rose:

When you get into, like, SaaS or subscription offerings, like,

Nicholas Rose:

Tony, you've got more thoughts about some of those other pieces.

Nicholas Rose:

what would you like?

Nicholas Rose:

It's

Tony Tarantino:

another thing that I think is really unique about CPQ it

Tony Tarantino:

could include so many different things like CPQ can just be quoted, can just

Tony Tarantino:

be guided selling, but it can also include your closed deal approvals that

Tony Tarantino:

can include your contract management, it can include maybe some CPQs that

Tony Tarantino:

can extend beyond also is like a light ERP so like document generation, quote

Tony Tarantino:

generation, it can do all those different things, And when you're evaluating

Tony Tarantino:

the tool that you want to use, like which of those are important to you?

Tony Tarantino:

Subscription management, another one, like Salesforce CPQ is not a

Tony Tarantino:

great subscription management tool.

Tony Tarantino:

So that maybe go to Zora route or you said there's so many different

Tony Tarantino:

variables of different pieces of functionality that you can buy within.

Tony Tarantino:

A CPQ instance.

Tony Tarantino:

It's about, finding what's the most important to you, what you're

Tony Tarantino:

going to use, and then picking the best and breed of those individual.

Tony Tarantino:

And I do like Salesforce CPQ because it's pretty good at all of that.

Tony Tarantino:

it provides an element of, all of those individual pieces pretty

Tony Tarantino:

well, but like, if you really wanted a super advanced approval.

Tony Tarantino:

process as part of your quote approval process, there's probably a better tool

Tony Tarantino:

that does a little bit better than you.

Tony Tarantino:

So it's just all about finding the different pieces of

Tony Tarantino:

functionality that is CPQ driven.

Tony Tarantino:

what do you care the most about?

Tony Tarantino:

What are you going to leverage the most out of that group?

Tony Tarantino:

And then you decide from there.

Nicholas Rose:

Yeah, and I would say most of the time in that sense,

Nicholas Rose:

like if we see, like it'd be like a Salesforce instance, CRM NetSuite.

Nicholas Rose:

You do like a SteelBrick or the Salesforce CPQ, and then you do like a

Nicholas Rose:

NetSuite suite billing if it's a SaaS or subscription management, right?

Nicholas Rose:

Because like there's not really a good subscription management

Nicholas Rose:

feature set out of that.

Nicholas Rose:

So it just depends on what you're going for.

Nicholas Rose:

those are kind of like the main setups.

Nicholas Rose:

I would probably say a large portion of them are out there.

Nicholas Rose:

if you have a really good complex subscription management piece.

Nicholas Rose:

That matters and kind of goes up and down and like Zora would probably be better.

Nicholas Rose:

especially if you want to do a lot of customization, because if

Nicholas Rose:

you're doing a lot of customization, that's where Salesforce, I would

Nicholas Rose:

say doesn't do so well, right?

Nicholas Rose:

Because it's not, set up for that, you're using the wrong tool.

Nicholas Rose:

If you need to build your own adventure, so to speak, right.

Nicholas Rose:

And it's got a lot of the complexities into it.

Nicholas Rose:

You just can't customize it as much.

Justin Norris:

So you've got CRM and I think we all know what that is.

Justin Norris:

You've got ERP, which is your finance playground.

Justin Norris:

And then CPQ, which is more about how do salespeople configure a quote

Justin Norris:

in terms of adding products and SKUs and bundles and all those things.

Justin Norris:

And then there's this, CLM or, contract life cycle management.

Justin Norris:

Like whole document generation piece.

Justin Norris:

Is that an optional thing for some companies or is that

Justin Norris:

always part of the solution?

Nicholas Rose:

again, it goes back to how complicated is the contract, right?

Nicholas Rose:

It's Let's take SAS, right?

Nicholas Rose:

Cause I think a lot of people follow SAS and it's usually the living piece of that.

Nicholas Rose:

Some companies you'll have legal review every contract, And there's going to

Nicholas Rose:

be a lot of pieces that need to be like redline changed and et cetera.

Nicholas Rose:

And that usually needs a full CLM contract life financial for that.

Nicholas Rose:

And, getting a system in like that place, like DocuSign or something's

Nicholas Rose:

going to be really important, or Congo.

Nicholas Rose:

And I example, those are usually the main two, I would say, but those

Nicholas Rose:

are needed because you just have to have the legal reference and

Nicholas Rose:

framework that's in the company, but you'll have some companies that are

Nicholas Rose:

clicked to buy product led growth.

Nicholas Rose:

Doesn't even have to touch a contract.

Nicholas Rose:

And you don't need it.

Nicholas Rose:

It depends on your coding process.

Nicholas Rose:

Which I hate that answer, but it does.

Justin Norris:

I think about, accounting systems and I, funnily enough, a lot

Justin Norris:

of my first jobs, when I was going through college, we're kind of in the

Justin Norris:

accounting world, I was like a bookkeeper.

Justin Norris:

I've worked with ACPAC, QuickBooks.

Justin Norris:

And so I have a decent understanding of accounting systems.

Justin Norris:

They don't tolerate, data quality issues.

Justin Norris:

to the same degree Like we talk about dirty data and CRM.

Justin Norris:

I'm not saying every accounting system is perfect, but you need

Justin Norris:

to balance at the end of the day.

Justin Norris:

in this business process, which is about actually putting data back and

Justin Norris:

forth between those two worlds of like sort of order and then sometimes semi

Justin Norris:

anarchy, how do you bridge the data quality gap between those two places?

Tony Tarantino:

the major difference here, again, every,

Tony Tarantino:

CPQ go to cash project that we do.

Tony Tarantino:

There's always going to be an element of, manual process.

Tony Tarantino:

And I think that very point of when you close a deal, when an account is

Tony Tarantino:

transferring to a customer, like that data integrity is so, so important,

Tony Tarantino:

that's where you really, really need a deal desk, team, a process of someone

Tony Tarantino:

that is confirming that data, making sure that that data is correct before it

Tony Tarantino:

enters the next stage in its life cycle.

Tony Tarantino:

So like that part.

Tony Tarantino:

It totally agreed.

Tony Tarantino:

So important.

Tony Tarantino:

You can not have dirty data in your, in your ERP.

Tony Tarantino:

You can have dirty data in your finance system because revenue impacting mistakes.

Tony Tarantino:

as much as I'm automation and system driven, you need humanize sometimes.

Tony Tarantino:

And that's like the scenario where I always.

Tony Tarantino:

We'll say, Hey, let's, think about who needs to confirm this deal.

Tony Tarantino:

Who needs to get from the data and make sure that the paper

Tony Tarantino:

contract matches your quote.

Tony Tarantino:

And again, CPQ will help with a lot of that, but there's always needs to be

Tony Tarantino:

an element of humanize here because of, to your very point, you can't have data

Tony Tarantino:

mistakes in your accounting system.

Nicholas Rose:

you go back to the original question.

Nicholas Rose:

I was just like, why did we start Hyperscayle?

Nicholas Rose:

Like, this is kind of like the exact reason.

Nicholas Rose:

Cause if you go with like an implementer, like a conga or whatever else out

Nicholas Rose:

there, that's totally around that.

Nicholas Rose:

Like they're going to focus on that part of the data and the technology piece going

Nicholas Rose:

in there, which is like perfectly fine.

Nicholas Rose:

Like that's what they're set for.

Nicholas Rose:

I'm not trying to.

Nicholas Rose:

Dog on them, so to speak, but like, they're not going to come back and ask

Nicholas Rose:

the business process to the business question back to you as the person of

Nicholas Rose:

like, how does my closing process or business, deal that's going to go work.

Nicholas Rose:

And if you don't have one, if you've never done one, like

Nicholas Rose:

it's the blind, lean, the blind.

Nicholas Rose:

And it's important in this case, right?

Nicholas Rose:

Because the finance data piece of data quality should

Nicholas Rose:

never even be in a question.

Nicholas Rose:

If the business process or the deal does process it's closed very well,

Nicholas Rose:

because like that is the Last line of defense, so to speak, to get into the

Nicholas Rose:

finance system and make sure it's right.

Nicholas Rose:

And everything is good and to ensure data quality happens on the finance side.

Justin Norris:

Is it usually only when a deal closes that

Justin Norris:

ERP kind of enters the picture?

Justin Norris:

In terms of passing data over, or is it before that even sometimes.

Nicholas Rose:

deal closes cancellations, renewals in those aspects.

Nicholas Rose:

those will be big things I would say, right?

Nicholas Rose:

Like contract and money generating events.

Nicholas Rose:

but you could also have from the ERP side back into the CRM side of like.

Nicholas Rose:

Bill collections, Dunning process, right?

Nicholas Rose:

Late for that piece.

Nicholas Rose:

you know, something issue and payment that can come up through that, you could also

Nicholas Rose:

have, you know, renewals that come back from a time perspective too, depending

Nicholas Rose:

on how big you want to go through it.

Nicholas Rose:

But then you'll also tie back into like support pieces, right?

Nicholas Rose:

Or credits.

Nicholas Rose:

So, short answer is no, but there's a way longer

Tony Tarantino:

Yeah.

Tony Tarantino:

I think, I think my point to be there ERP as soon as possible.

Tony Tarantino:

But you would need a really, really, really tight data management process.

Tony Tarantino:

You need a really tight integration though.

Tony Tarantino:

Exactly.

Tony Tarantino:

Like when that data is being pushed over, when it's updated, like you need

Tony Tarantino:

to have that process really well defined and feel really good about your data.

Tony Tarantino:

that's why I, most of the clients that we work with don't have that.

Tony Tarantino:

So that's why I always say.

Tony Tarantino:

Wait until the deal closes, wait until human eyes have been on it.

Tony Tarantino:

And then we'll push that data because that's when I feel most

Tony Tarantino:

comfortable with it in a perfect world.

Tony Tarantino:

Like if I had more control over the end of my process, I do agree.

Tony Tarantino:

It would be nice to have it there earlier, but that's not the world that we live in.

Tony Tarantino:

Like most of the time there's data is not ready to be pushed to the

Tony Tarantino:

RP until again, it's been closed.

Tony Tarantino:

And we've gone through that kind of deal desk process.

Justin Norris:

So then when I think about the role of Rev Ops here,

Justin Norris:

obviously, quoting is inherently a sales and a Rev Ops process, but the cash

Justin Norris:

part, like it's much more finance led and, contracts it's very much legal.

Justin Norris:

and yet I do see like.

Justin Norris:

Quote to cash very often listed as one of the responsibilities

Justin Norris:

and Rev Ops job descriptions.

Justin Norris:

So I guess my question is how did Rev Ops kind of end up at the center here?

Justin Norris:

Is this a good thing for the profession of Rev Ops?

Justin Norris:

And what is the role that, that we as a discipline have to play?

Nicholas Rose:

So I think it's a good thing.

Nicholas Rose:

RevOps just entered into this role, right, because, like, back to my

Nicholas Rose:

original statement, like, everyone owns it, but no one owns it.

Nicholas Rose:

And if no one owns it, someone needs to fill in that role.

Nicholas Rose:

And usually RobOps is the best person to go fill in that role because they're

Nicholas Rose:

already interfaced with everyone.

Nicholas Rose:

And they can understand it'd be like the art writers, right.

Nicholas Rose:

Or mediators between the different groups.

Nicholas Rose:

And they can also lead the group down the right path.

Nicholas Rose:

Making sure they can explain why do we need to do X and Y and the

Nicholas Rose:

reason why does you have impact on this person's impact and job?

Nicholas Rose:

Because most of the time, if you have legal, they don't understand

Nicholas Rose:

the sales process necessarily.

Nicholas Rose:

It's very few between, or legal doesn't understand the

Nicholas Rose:

finance process, and vice versa.

Nicholas Rose:

you got people trying to learn about the different roles and

Nicholas Rose:

everything else that slows it down.

Nicholas Rose:

And so I do think this is good, and it's growing more of

Nicholas Rose:

what RevOps and ownership is.

Nicholas Rose:

Now, does that have some negative impacts and other impacts?

Nicholas Rose:

negative is not the right word, right?

Nicholas Rose:

But like, if Rev Ops is filling these roles, I think it does

Nicholas Rose:

have some other impacts.

Nicholas Rose:

Into the organizations around like system ownership and things like that, right.

Nicholas Rose:

Between like the business process, who owns actually

Nicholas Rose:

doing the work of the system.

Nicholas Rose:

Cause I see that shifting and moving up more towards Rev

Nicholas Rose:

Ops of owning the full thing.

Nicholas Rose:

We're like, what is IT's role in that?

Nicholas Rose:

And that's the whole conversation we can get to later on.

Nicholas Rose:

But like, that's where I see like that trade off though, is because

Nicholas Rose:

they have to go fill that role.

Justin Norris:

And yeah, you, kind of anticipated where my

Justin Norris:

next thought was going to be around like IT business systems.

Justin Norris:

There's a lot of companies now where you have a go to market systems

Justin Norris:

role or business systems function.

Justin Norris:

It's kind of IT with another label that are owning a lot of these.

Justin Norris:

how do you see RevOps interfacing with these or what's the ideal ownership

Justin Norris:

state from your point of view?

Nicholas Rose:

Tony and I have this debate and conversation

Nicholas Rose:

every like, I swear three months.

Nicholas Rose:

And I feel like he keeps coming more and more to my side.

Nicholas Rose:

I'm going to make a statement that I think it is phasing

Nicholas Rose:

themselves out of a job, right?

Nicholas Rose:

that might scare a lot of people or some people might argue with that.

Nicholas Rose:

But if you think about it, you go to Scott breakers slides of how much technology

Nicholas Rose:

you've had in the last, what, 10 years, Like we've had like 150, 200, 000,

Nicholas Rose:

different pieces of technology that's been commoditized for the business user.

Nicholas Rose:

The it side doesn't understand the business.

Nicholas Rose:

They've gone deep down the path of code and everywhere else.

Nicholas Rose:

And we come, all land from index of low code development,

Nicholas Rose:

no code, things like that.

Nicholas Rose:

They have lost grass of what the business is, or they need to have requirements to

Nicholas Rose:

a certain key, which is kind of shifted them down the organization overall.

Nicholas Rose:

And so like, no, it's it's still important.

Nicholas Rose:

I think they're still important.

Nicholas Rose:

So I don't say like you diminish, get rid of them.

Nicholas Rose:

They're gone.

Nicholas Rose:

But the roles are diminished very much down to like governance because a lot of

Nicholas Rose:

times we see is like RebOps taking more ownership of the the business operations

Nicholas Rose:

team because like they're closer to the business and the business process.

Nicholas Rose:

It goes off to it.

Nicholas Rose:

And a lot of times the sales organizations, the marketing

Nicholas Rose:

organizations who are paying the budgets for those people don't get the

Nicholas Rose:

answers that they need and ownership.

Nicholas Rose:

it's an interesting question you asked us because I feel like that's more

Nicholas Rose:

and more coming toward the rev ops and more coming towards the business side.

Nicholas Rose:

And that other section is not necessarily with it.

Nicholas Rose:

and it handles more governance and security, which could be

Nicholas Rose:

a whole other topic debate.

Nicholas Rose:

We've been going to for hours on end.

Tony Tarantino:

I spent most of my career in an I.

Tony Tarantino:

T.

Tony Tarantino:

focus role in an I.

Tony Tarantino:

T.

Tony Tarantino:

group.

Tony Tarantino:

I.

Tony Tarantino:

T.

Tony Tarantino:

has been my managers for a good portion of my career, and I do agree that I.

Tony Tarantino:

T.

Tony Tarantino:

Is that close to the business?

Tony Tarantino:

in today's world.

Tony Tarantino:

And we deal with this with our clients all the time.

Tony Tarantino:

They're becoming blockers more than becoming enablers.

Tony Tarantino:

And that's a inherent problem for it.

Tony Tarantino:

that being said, I also scared of a world where kind of rev offs,

Tony Tarantino:

business focused people are owning your data and owning your systems.

Tony Tarantino:

And like, they don't have the understanding of governance data

Tony Tarantino:

integrity and all the different things you need to think about and security

Tony Tarantino:

and all these things that are super relevant from an IT perspective.

Tony Tarantino:

It's going to be lost on a business focused robots person.

Tony Tarantino:

So again, I don't disagree that it needs to potentially reevaluate the role they

Tony Tarantino:

play in a lot of these organizations, but there is a place for them and

Tony Tarantino:

there's a place for find the right balance between the red tape and the

Tony Tarantino:

making sure that we're being as safe as possible and minimizing defects and

Tony Tarantino:

minimize data issues versus just getting in the way of actual value creation.

Tony Tarantino:

From a rev ops group from, with our systems of records.

Tony Tarantino:

it's a tough, and I mostly agree with Nick at this point where he asked me a

Tony Tarantino:

year ago and it was very, very different.

Tony Tarantino:

but do think there's a place for it, especially if we become CPQ, because

Tony Tarantino:

we talked about CPQ as being that true hub of all these different systems

Tony Tarantino:

of record and revenue generating.

Tony Tarantino:

processes.

Tony Tarantino:

And like, if.

Tony Tarantino:

You don't understand the integration.

Tony Tarantino:

If you don't understand how the system architecture of how data moves up and

Tony Tarantino:

down your processes, you can cause some major upstream and downstream impact.

Tony Tarantino:

So I do think there's a role there.

Tony Tarantino:

But again, ownership of the development and solutioning of a CBQ it probably

Tony Tarantino:

should be rev ops with it support from a development standpoint.

Tony Tarantino:

It's providing the governance that isn't necessary.

Tony Tarantino:

Okay.

Justin Norris:

It's funny, like many things, I find this problem, it has like a

Justin Norris:

few, spectrums, and it's hard to maximize both sides of it, but like, you want

Justin Norris:

your people working on these projects to be very close to the business, to have

Justin Norris:

business acumen, so that's like, alright, RevOps, or people embedded in functions,

Justin Norris:

so that they understand requirements, and so that they're thinking more about

Justin Norris:

the business side and not just, you know, the it only looking at things through the

Justin Norris:

lens of technology and governance and this fortress mentality at the same time, you

Justin Norris:

don't want people who lack kind of respect for elegance and architecture and systems.

Justin Norris:

Cause then you end up with technical debt and then you end

Justin Norris:

up with things poorly implemented.

Justin Norris:

So that speaks more to like it skills, specialized domain knowledge,

Justin Norris:

centralization, so that those people can work well together.

Justin Norris:

So like there's this tension all the time.

Justin Norris:

And.

Justin Norris:

I don't know how you end up with the perfect happy medium

Justin Norris:

between the two things.

Justin Norris:

I think we're yet to figure that out.

Nicholas Rose:

in my experience so far, the last 20 years, I

Nicholas Rose:

would actually argue with it.

Nicholas Rose:

You've had more technical debt being created within organizations because

Nicholas Rose:

they don't know the business process.

Nicholas Rose:

They've gotten so far away.

Nicholas Rose:

Like when the CMO has so much technology, I think that has been

Nicholas Rose:

the Genesis of it because they've always said, Oh, we can't support you.

Nicholas Rose:

Go off on your own and run Marketo and everything else that you can go

Nicholas Rose:

do it because we don't understand.

Nicholas Rose:

And it's not the core business.

Nicholas Rose:

I think that's when it has lost the value into the organization because

Nicholas Rose:

you have shadow it on the marketing side, basically already at that point.

Nicholas Rose:

We don't want to call it.

Nicholas Rose:

I mean, that's the genesis of

Nicholas Rose:

marketing operations and it's just, coming back down to the phone.

Nicholas Rose:

Right?

Nicholas Rose:

Like all the marketing technologies have created all the sales

Nicholas Rose:

technologies have been created.

Nicholas Rose:

All the customer success technology has been created.

Nicholas Rose:

I see so many people in customer success of who runs gain site or

Nicholas Rose:

to Tango, not one person in it.

Nicholas Rose:

Who's doing the integrations, not one person in it because they've

Nicholas Rose:

gotten so far away or they gotten so non technical they missed with it.

Nicholas Rose:

And so the technical debt, they have no control over back in the business.

Nicholas Rose:

And they've gotten away with it now for a finance or an ERP or governance was like

Nicholas Rose:

the finance pieces to manage the dollars.

Nicholas Rose:

It's been great there.

Nicholas Rose:

Cybersecurity it's been great there, but they moved so far away

Nicholas Rose:

from it that they've lost control.

Nicholas Rose:

And I think operations has to stand there.

Nicholas Rose:

my big view is you'll see a lot of operations.

Nicholas Rose:

Or business ops systems owning the systems more and more specifically when you get

Nicholas Rose:

into Salesforce, and they'll have it getting sucked into those sides instead

Nicholas Rose:

of being in the finance or other areas.

Nicholas Rose:

And like 10 or 15 years,

Tony Tarantino:

make sure you have the right personnel in those roles.

Tony Tarantino:

you need that technical RevOps.

Tony Tarantino:

And again, I think the idea of, RevOps as truly removing those silos, like being

Tony Tarantino:

marketing ops, sales ops, finance ops, IT ops, CS ops, truly a RevOps organization

Tony Tarantino:

has people that can do it all.

Tony Tarantino:

And I do think that's the route that our group should go, because that's, going to.

Tony Tarantino:

Allow us to add the most value, an organization down the line.

Nicholas Rose:

I can own help desk.

Nicholas Rose:

They can own governance.

Nicholas Rose:

They own security, That's where we go through and you'll see the systems

Nicholas Rose:

pieces go under the rev ops organization

Justin Norris:

it's super interesting.

Justin Norris:

And I've seen a variety of structures, but I think the one, eternal principle

Justin Norris:

that you've alluded to is like, it has to be responsive to the business.

Justin Norris:

As soon as a function gets.

Justin Norris:

Far away from the business.

Justin Norris:

Inevitably, the business just sort of recreates it closer to itself

Justin Norris:

and that's never a good dynamic.

Justin Norris:

So, we'll be interesting to see how it plays out.

Justin Norris:

I want to thank you both.

Justin Norris:

This has been just like super educational for me to flesh

Justin Norris:

out this area of my knowledge.

Justin Norris:

Hope it was equally so for some of the folks listening where CPQ

Justin Norris:

or anything else RevOps related?

Nicholas Rose:

I would go straight to our website at hyperscayle.com.

Nicholas Rose:

Reach out to us, connect to us

Justin Norris:

And that's,

Nicholas Rose:

hyper scale with Y S C A Y L E.

Nicholas Rose:

the person who owns Hyperscayle.

Nicholas Rose:

com has been selling airplanes for 40 or 50 years, so we can't touch that one.

Justin Norris:

All right.

Justin Norris:

Thanks guys.

Justin Norris:

It was really great catching up and let's hope to speak to you again.

Nicholas Rose:

Thanks.

Nicholas Rose:

It was awesome.

Tony Tarantino:

Appreciate you,

Tony Tarantino:

tony-tarantino_1_07-11-2024_160501: Jason.

Links

Chapters

Video

More from YouTube