النص 🔗
WEBVTT
00:00:07.413 --> 00:00:13.289
Welcome back to Partnerships Unraveled, the podcast where we unravel the mysteries about partnerships, and channel on a weekly basis.
00:00:13.289 --> 00:00:19.170
My name is Alex Whitford, I'm the VP of Revenue at Channext and this week I'm very excited to welcome our special guest, brian.
00:00:19.170 --> 00:00:19.771
How are you doing?
00:00:19.771 --> 00:00:20.922
Doing well?
00:00:20.922 --> 00:00:21.685
How are you doing Alex?
00:00:21.685 --> 00:00:33.036
Yeah, I'm really excited about this one because I think you've got a really interesting history in terms of sort of program leadership and you've been an absolute rocket ship.
00:00:33.036 --> 00:00:39.033
So excited to unpick some of the lessons and traumas that have come along that journey.
00:00:39.033 --> 00:00:44.411
Today, maybe for the uninitiated, you could give us a little bit of an introduction around who you are and what you do.
00:00:45.360 --> 00:00:46.845
Sure, sure, happy to do so.
00:00:46.845 --> 00:00:48.731
So my name is Brian Cronman.
00:00:48.731 --> 00:00:55.213
I'm currently the Area Vice President of Global Programs and Strategy for our partner ecosystem here at SentinelOne.
00:00:55.213 --> 00:00:59.508
I've been here for seven years and going on nine months.
00:00:59.508 --> 00:01:01.573
I've been quite a ride with us.
00:01:01.573 --> 00:01:17.281
Prior to that, I was at Proofpoint for five years, and prior to that I was with Symantec through an acquisition that they made with VeriSign, and then before that I was in international development, which is a completely different career from anything in the technology space.
00:01:17.281 --> 00:01:20.427
So a lot of different places and directions we can go.
00:01:21.329 --> 00:01:32.560
So almost eight years at one vendor, which I think that feels like about nine lifetimes in this market because I think people are on this one and a half year to two year rotation.
00:01:32.560 --> 00:01:35.328
It feels like Looking back over.
00:01:35.328 --> 00:01:40.263
Obviously SentinelOne's gone through stupid growth over that eight year period.
00:01:40.263 --> 00:01:46.489
What are some of the sort of key moments that stand out from a channel strategy perspective that's influenced that success?
00:01:47.120 --> 00:01:51.471
Yeah, no, really good question, and I would say, you know, foundationally.
00:01:51.640 --> 00:02:19.522
So before I started and I would say within the first, it was probably three weeks before I started back in 2017, the organization had made the decision right then and there, when we were a tiny, tiny, tiny company, that we were going to be 100% channel oriented, and that meant that, moving forward, all deals had to be transacted with a partner in mind, and if they didn't, then there would be quota ramifications for the sellers on the outset.
00:02:19.943 --> 00:02:22.189
So they were putting their money where their mouth was.
00:02:22.189 --> 00:02:40.362
Even before I
Load full transcript
joined, which very few companies were willing to kind of do that even at that point in time, and then secondarily, kind of along those same lines, one of the core pieces of our business is with our managed service providers, and you know a lot of companies.
00:02:40.362 --> 00:03:00.889
We could see where things were going even at that time, but again, the company had made the decision to re-architect the platform to make it much more usable for managed service providers to essentially own their own tenant and be able to deploy rapidly without any one involvement, and so it was moving towards that direction.
00:03:00.889 --> 00:03:05.980
So we could say, hey, we've got the technology, we've got the ease of doing business Now.
00:03:05.980 --> 00:03:13.907
We just have to come in with both of those things and wrap a program around it so that partners know how they can actually be profitable selling SettleOne.
00:03:15.210 --> 00:03:23.120
Yeah, I know we did the prep call, but it sort of blew my mind because I see so often that businesses start to build a channel.
00:03:23.120 --> 00:03:27.211
Once they've hit you know 100 million in revenue, they're starting to work out.
00:03:27.211 --> 00:03:28.965
Hang on, the unit economics are scaling.
00:03:28.965 --> 00:03:30.490
The sales team doesn't really work.
00:03:30.490 --> 00:03:33.971
We need to start building a channel and that's such a painful transition.
00:03:33.971 --> 00:03:46.604
It's gratifying to hear that, if you sort of build it from the ground up, incorporating that product element which was obviously critical, that actually you've not had to go through any of that difficult transitionary period.
00:03:46.604 --> 00:03:49.361
I'm sure you had a whole load of other challenges that came along with that.
00:03:49.361 --> 00:03:57.283
I imagine the partner ecosystem has changed a lot across that eight year period.
00:03:57.283 --> 00:03:59.129
How do you view that today?
00:03:59.129 --> 00:04:04.646
You've obviously touched on MSPs, but MSPs and resellers aren't the same and that requires two different programs.
00:04:04.646 --> 00:04:05.790
How does all of that come together?
00:04:06.272 --> 00:04:07.556
Yeah, it's a really good question.
00:04:07.556 --> 00:04:25.314
It's actually a super timely question for us too, because we just last week launched our new Partner One partner program, or Partner One program specifically, which actually unifies everything that we've done with all the different parts of the partner ecosystem into one single umbrella, and happy to talk more about that as we move forward.
00:04:25.314 --> 00:04:32.574
But ultimately, you're right, the partner ecosystem has shifted quite a bit, I would say.
00:04:32.574 --> 00:04:37.572
Initially it was very distinct between your resellers and your managed service providers.
00:04:37.572 --> 00:04:58.649
Today those lines are really blurry Because at the end of the day, you know, customers are talking to partners and then make pivoting left or right at the very, very end of the process when they decide, hey, you know, I want to own the title to the license and I want to actually be the ones who are, you know, putting it in our sock or putting it in our IT environments.
00:04:58.649 --> 00:05:00.701
Or they're saying, hey, you know what?
00:05:00.701 --> 00:05:03.565
I've got a better offer for someone to come in and manage on my behalf.
00:05:03.565 --> 00:05:05.490
And so that distinction.
00:05:05.490 --> 00:05:07.973
At the end of the day, the partners are the ones who are doing it.
00:05:07.973 --> 00:05:14.262
They're doing the right thing regardless.
00:05:14.262 --> 00:05:21.185
And so we're with this new program, which essentially trying to put some flexibility into it and say, hey, come to us, we don't want to make it super difficult, we want to meet you where you are, where your customers are.
00:05:22.567 --> 00:05:24.432
But as far as the evolution over time.
00:05:24.451 --> 00:05:35.764
Beyond that, I think one other interesting thing that we've seen is that when we started, endpoint security is a long, long-standing market.
00:05:35.805 --> 00:05:42.283
It's been there probably since I was in elementary or middle school, and that's a long time ago.
00:05:42.283 --> 00:05:51.028
And so you go through this evolution and it ends up being it's a very crowded space, tons of different vendors that are out there.
00:05:51.028 --> 00:05:58.202
You have some sort of innovative new player and they're coming in and you talk to partners and they're like why should we talk to you?
00:05:58.202 --> 00:06:01.552
We have 20 other vendors in this space on our line card.
00:06:01.552 --> 00:06:03.387
What is going to make you different?
00:06:03.387 --> 00:06:12.548
And why should I go back to the customer that I just sold this to, or I've been selling this solution to for 15 years, and tell them it's time to make a replacement?
00:06:12.548 --> 00:06:30.588
And so just an absolute knife fight at the beginning to really prove your tech out, mostly with the SEs that are at the part, the solution engineers that are at the partners to really call out and say, hey, just get your hands on it, play around with it, see what it does, see where there might be a fit for your end users.
00:06:31.740 --> 00:06:45.286
Yeah, what I find interesting there we lovingly describe it as the three Ps at Channex which is, you know, the first thing you build is product, and you've got to make sure that your product is great and valuable and is useful to both the partner and the end user.
00:06:45.286 --> 00:06:46.846
It's easy to deploy and manage.
00:06:46.846 --> 00:06:50.970
From a partner perspective, it drives great outcomes from an end user perspective.
00:06:50.970 --> 00:07:07.884
The problem I see today is that so many businesses are indexed on that first P and there's a lot of great products out there, right, lots of businesses make really great stuff, and so then it sort of
comes down to the next two, which is program and personnel.
00:07:07.884 --> 00:07:13.242
That's what causes the big shift now in the channel, which is hey, why is your program better?
00:07:13.242 --> 00:07:16.029
Because there's a minimum requirement from a product's perspective.
00:07:16.531 --> 00:07:21.112
But once that minimum requirement is hit, we're looking at programming and the people within your channel.
00:07:21.112 --> 00:07:22.523
So, are you a joy to deal with?
00:07:22.523 --> 00:07:25.571
Do you follow up and actually do what you say and say what you do?
00:07:25.571 --> 00:07:39.067
Um, and you know, from a program perspective I think you even touched on it, you, you even mentioned uh in in your job title it's like, hey, we need to educate partners on why it's beneficial to sell sentinel one, that program piece.
00:07:39.067 --> 00:07:50.005
I see that being the the most significant differentiator, uh, in the difference between a great technology that does okay and a great technology that does amazing.
00:07:51.028 --> 00:07:59.822
Yeah, and I'll just let me just echo one thing that you say there, and I think the way that we've kind of orchestrated things throughout the years is just.
00:07:59.822 --> 00:08:20.641
I think programs can sometimes become too complex and you have to have a data dictionary to understand exactly why it's important and then, on top of that, have a program that's complex, that may change every year or every 18 months or so, and I will say that both of those things are things that we try not to do if at all possible.
00:08:20.641 --> 00:08:22.644
Try not to do if at all possible.
00:08:22.644 --> 00:08:36.754
I will tell you, with this program launch that I just mentioned, the last time that we had done anything was probably three or four years ago, which it's actually now overdue to make a change, mostly because business is moving so quickly, our ecosystem is moving so fast.
00:08:36.754 --> 00:08:39.417
We have to adjust and move up and improve with the times.
00:08:49.279 --> 00:09:00.879
However, even when making these changes, we still want to have some core beliefs, which is to say, it's about activity, it's about engagement, it's about enablement, it's about meeting our people where we are and making it simple to understand what's important to us, so that we can tell partners what's important to them Right.
00:09:00.879 --> 00:09:05.893
So we want everyone to be aligned in terms of the incentives in a very clean and easy use fashion.
00:09:05.893 --> 00:09:14.215
Again then using the tools that we have at our disposal and our partners disposal to be able to check our math and say, hey, this is what we're seeing.
00:09:14.215 --> 00:09:14.801
We see that.
00:09:14.801 --> 00:09:19.613
You know, joe Smith, over here, your organization took this enablement course two weeks ago.
00:09:19.613 --> 00:09:20.441
Here you go.
00:09:20.441 --> 00:09:24.091
That means that you're fully compliant with our requirements.
00:09:24.091 --> 00:09:25.013
Here you go.
00:09:25.494 --> 00:09:43.131
That means that you're fully compliant with our requirements, and so trying to keep that transparency and that simplicity in the program again provides that predictability that partners need to know that, hey, you're not going to change the rules on me midstream and I can actually build a profitable business.
00:09:43.131 --> 00:09:44.894
Yeah, interesting to maybe double click on the sort of simplicity of programs.
00:09:44.894 --> 00:09:45.837
I think the bit that I was sort of marveling.
00:09:45.837 --> 00:09:46.719
I think how big is your team?
00:09:49.649 --> 00:09:54.091
Brian, we have uh, so between with me, we have four people on my team.
00:09:54.840 --> 00:10:05.845
So four people total running a program that covers GSIs, msps, resellers, dmrs, sis, regional SIs, all of those pieces.
00:10:05.845 --> 00:10:08.989
I think you sort of touched on it.
00:10:08.989 --> 00:10:15.254
We're starting to see now that programs are becoming simpler rather than more complicated.
00:10:15.254 --> 00:10:25.648
You know, there was a big push, I think from very large companies, to be like right here's our GSI program and it's completely different to here's our reseller program, which is completely different to our MSP program.
00:10:25.648 --> 00:10:39.590
Talk to me about how you cannibalize the workflows between those, while adding simplicity but also making sure that there are enough hard lines in there that you know the GSIs are getting what they need and the resellers are getting what they need.
00:10:40.120 --> 00:10:41.803
Yeah, it's a good question, right?
00:10:41.803 --> 00:10:50.951
So the way that I sort of think about it and the way our team sort of thinks about it is you know what are the barriers to entry to your various pieces of the program.
00:10:50.951 --> 00:10:59.788
And so I think the easiest thing to acknowledge is that for a sell partner or a reseller, that's a fairly simple thing for people to do.
00:10:59.788 --> 00:11:11.370
It means that you know you might have a customer, a couple of customers, they're interested in the solution and you just want to be able to transact the deal, just like you've done every single year with maybe a different vendor.
00:11:11.370 --> 00:11:17.655
And so we make it very simple, relatively speaking, for someone to join and to be maintained in the program.
00:11:17.655 --> 00:11:23.808
You know they would receive the relatively low amount of benefits for being at that level of engagement.
00:11:23.808 --> 00:11:43.210
But then as we start to build up more activity, as we start to work with national partners, the DMRs, like you mentioned, then you start to have much more strategic relationships with those organizations and you can start to pull apart and say, hey, not only are you receiving benefits on the deals, but also predictability in terms of how you can build a business.
00:11:43.210 --> 00:11:48.044
But then when you look at things like managed partners okay.
00:11:48.044 --> 00:11:49.427
Well, those managed partners.
00:11:49.969 --> 00:11:54.767
There's a programmatic requirement to say that you have to be able to provide L1 and L2 support.
00:11:54.767 --> 00:12:01.187
If you can't do that, it's not upon SentinelOne to help you build that framework for yourself.
00:12:01.187 --> 00:12:08.246
We're not out here to train people how to become a support engineer, how to have a ticketing system.
00:12:08.246 --> 00:12:09.772
What's your recommendation?
00:12:09.772 --> 00:12:12.500
How do you orchestrate everything between them?
00:12:12.500 --> 00:12:18.384
We'll provide you the tool, the security tool, to be able to enable your own existing framework to move forward.
00:12:18.384 --> 00:12:27.111
But if you don't have that capacity, we would recommend that you go through one of our other partners who can actually orchestrate that a little bit better.
00:12:27.111 --> 00:12:33.472
You know our managed service provider distributors, like our RMM providers, who do a fairly decent job of that.
00:12:34.679 --> 00:12:43.264
And then, as you move up the stack into your GSIs, your SIs, your service delivery partners, again there's that core competency that has to be there.
00:12:43.264 --> 00:12:45.544
Again, there's that core competency that has to be there.
00:12:45.544 --> 00:12:54.448
I think you can't get away from treating a GSI or an SI somewhat uniquely, just given the frameworks that they have and the investments that have to be made with those organizations.
00:12:54.448 --> 00:12:56.690
No-transcript I.
00:12:56.690 --> 00:13:03.514
What I would say is I don't know that there's necessarily cannibalization in there, but it's really more about understanding.
00:13:03.514 --> 00:13:28.682
Okay, if I require this for someone who's just reselling, then you may have to train 150 people to actually get your product relevant in the headspace of anyone who's out there putting you on a product on a bit.
00:13:30.432 --> 00:13:36.370
So you've built this complicated yet simple recipe for sort of how you build programs.
00:13:36.370 --> 00:13:41.263
I think one of the things that I find interesting is building programs is complicated.
00:13:41.263 --> 00:13:45.279
Prioritizing them, I think, is even more complicated.
00:13:45.279 --> 00:13:50.682
How do you decide which partner segments to start with, middle with, end with?
00:13:52.990 --> 00:14:01.325
You know, I think it depends on your own organization's maturity and where the market is buying your solutions.
00:14:01.325 --> 00:14:14.456
I mean, I will say that, you know, even though we've delivered a program that unifies everything between our sell, our manage tracks, our build tracks and our deliver tracks, our sell track is clearly the most mature.
00:14:14.456 --> 00:14:17.740
I think it's also the easiest one for an organization to start with.
00:14:17.740 --> 00:14:27.913
Secondarily, because of the investments we made on the product side, our managed service provider track that one is fairly mature and we know what we're doing.
00:14:27.913 --> 00:14:40.216
And on top of that, we know what mistakes I wouldn't say mistakes, mistakes, not the right word I would say we've had to evolve based on, now, the size and the scale and the scope of the organization.
00:14:40.216 --> 00:14:56.076
Again, we've matured to the point to say, hey, listen, we need to take a step back, re-prioritize, re-tier who our partners are and what our focus should be in the managed track itself, so that we can actually provide better service and better delivery to those providers.
00:14:57.009 --> 00:15:08.182
But then, as we start to move forward and as you start to move up market a little bit more, you understand that, ok, we need Our customers are asking for product integrations with key vendors.
00:15:08.182 --> 00:15:16.019
You can't just stand alone in a crowded space and say, you know, work with me, and just you can do everything that you want to with us.
00:15:16.019 --> 00:15:17.361
Everything that you want to with us.
00:15:17.361 --> 00:15:28.597
You've got to be able to work with, in our case, the folks like the Optives and the MindCats and the Proof Points and the Zscalers of the world in order for everything to be orchestrated and work really, really well together.
00:15:28.597 --> 00:15:36.177
So then that naturally leads to more of that technology integration path or that alliance path that some vendors have.
00:15:36.177 --> 00:15:56.254
And then when you start to go into other solutions and I would say specifically for us, as we've made more investments into the SIM space, so your event logs everything that's coming in, trying to figure out what's going on in your organization so you can prioritize and actually fix problems when they come up.
00:15:57.976 --> 00:16:02.066
That product, that sphere, is very service heavy.
00:16:02.787 --> 00:16:11.739
Yeah, you know, I think previously, when we were just deploying our endpoint solutions, our core solutions in the past, it's pretty easy for someone to stand it up, deploy an agent and it works.
00:16:12.701 --> 00:16:37.714
When you're dealing with terabytes and terabytes and terabytes of data that you're ingesting into a system that then needs to be normalized and parsed and all of that fun stuff, there are services, opportunities that aren't just nice to have, there needs to have, and you as an organization need to understand, like, okay, am I going to make that investment or am I going to work with partners whose core competency is focused on delivering that type of service?
00:16:37.714 --> 00:16:46.466
And so naturally, your organization, our organization, has kind of gravitated towards building out some of those kind of service offerings.
00:16:46.466 --> 00:17:06.903
I think we probably have a little bit further to go on that side, if I'm being honest, but that's clearly where we're
going, and as we start to open up more and more of those types of opportunities, then the conversation becomes even more interesting for those types of integration partners, your GSIs of the world, and you know kind of taking it from there.
00:17:08.329 --> 00:17:09.071
Awesome.
00:17:09.071 --> 00:17:18.355
You've mentioned that part of your role is sort of measuring or proving the value of the ecosystem and sort of pulling that messaging back internally.
00:17:18.355 --> 00:17:28.377
When a business is 100% channel led, channel revenue is a poor reflection of the value that the channel is providing.
00:17:28.377 --> 00:17:33.459
It means you need a whole other set of data to sort of show and indicate what the channel is providing.
00:17:33.459 --> 00:17:35.553
Talk me through what some of those key metrics are.
00:17:36.213 --> 00:18:02.772
Yeah, I mean I think for us it starts to become a difference, that the core metric of everything at this point is around partner sourced, and that partner sourced activity could be, you know, that traditional deal registration, where someone has identified an opportunity that you're not aware of and they bring it through a portal and it comes into our system and our team says, yeah, I don't know anything about it, let's go to town, I'm going to protect you on the investment that you're putting in place.
00:18:02.772 --> 00:18:19.228
That's just core, and we have our own metrics that are reported all the way up to our CEO that say, hey, this is, this is our benchmark, this is what our goal is for the year from a pipeline generation perspective, from an actual bookings perspective, and we need to, we need to hit that.
00:18:19.228 --> 00:18:29.153
I mean, I can tell you, generally speaking, how close we were last year and how we're, how we're starting off this year, um, and so that's core to everyone on the team.
00:18:29.153 --> 00:18:33.886
Beyond that, then it starts to also come through things.
00:18:33.886 --> 00:18:42.263
We're starting to look more at an influence type play, which is really what the SIs of the world are really interested in.
00:18:42.263 --> 00:18:44.233
They may not transact at all.
00:18:44.996 --> 00:19:02.016
Similar to that are your integration partners where you're meeting either in the channel or you're meeting at the end customer, and they're not really necessarily sourcing deals per se, but they can be heavily influencing how a deal is going to run or any other sort of delivery partner.
00:19:02.130 --> 00:19:11.565
And so what we are trying to do is marry those two things together in a way that shows the true value of what's happening in the ecosystem.
00:19:11.565 --> 00:19:30.334
Because, you know, I think one of the things that's that's kind of complex but simple and complicated about the world is that everyone measures revenue, because revenue is easy, bookings are easy to measure, you can set up systems and you can say, all right, if it comes in this way, then it looks like X, comes in that way, it looks like Y, we're done.
00:19:30.334 --> 00:19:31.417
It's a simple metric.
00:19:31.417 --> 00:19:32.662
We can track this over time.
00:19:32.662 --> 00:19:34.166
Blah, blah, blah.
00:19:34.166 --> 00:19:47.839
That's just not how a customer relationship actually works, where you may have six, seven different partners of different types that are actually influencing a given account.
00:19:47.839 --> 00:20:00.911
Whether they're transacting or not, they're actually still in your deals and need to understand what's the value of this one versus that one, and that's the message that we're starting to turn the organization around right now.
00:20:00.911 --> 00:20:01.854
It's just start to look at.
00:20:02.315 --> 00:20:41.092
We've got to figure out how to measure it, but that's how we, that's how we're thinking about it I spend a obviously a lot of time speaking to um channel leaders, right as a function of the podcast and as a function of of my, my job, um, and it's one of the things that I'm always fascinated by, because the channel is slow moving and slow to measure, and then you have a double problem, which is, if you just measure bookings, that's at the end, and so then you have a slow moving thing that you just measure the last data point, um, and so the real challenge with bookings is what happens when you get month three into the year and bookings are behind.
00:20:41.251 --> 00:20:51.432
If you don't have any of that leading indicator, you might have already missed your entire year and you only realized it in month three, yeah, and and because then you've got to enact change.
00:20:51.432 --> 00:21:15.517
Change takes a while, um, and then arna has to do stuff and the disty has to do stuff, or your aggregator has to do stuff and your teams have, and it's like, and then, hopefully, by month seven, we start to see the uptick and it becomes quite painful, um, given that speed is so critical, I think, to making great decisions and driving continuous performance, how do you think about automation when it comes to program design?
00:21:17.180 --> 00:21:33.393
well, I I'm going to go back in some respects to what I was saying a few minutes ago, in that you have to be able to provide tools that show a partner where they are, and I would also say those tools have to also have an internal facing element so that everyone is on the same page.
00:21:33.393 --> 00:21:41.952
We have dashboards and we have tiering that says all right, at this moment in time, what is it April the 9th?
00:21:41.952 --> 00:21:52.707
I can tell you that here's where we are in terms of bookings, in terms of core programmatic requirements, in terms of pipeline, in terms of deal registrations.
00:21:52.707 --> 00:21:55.214
Incentives earn MDF that's coming through.
00:21:55.214 --> 00:21:57.981
I can tell you what that looks like today.
00:21:57.981 --> 00:22:13.790
And then we can keep taking snapshots and building into business plans, building
into QBRs, building into slides that are shown internally so that people know exactly like hey, this is where we are with partner, A focus partner in this part of the world.
00:22:13.790 --> 00:22:17.096
So that's point one.
00:22:17.497 --> 00:22:22.683
The other piece around automation that's, you know, from a workflow perspective is around.
00:22:22.683 --> 00:22:48.863
You know, whether it's integrating with a disty to ensure that your quotes and your POs and invoices kind of come through, that are clean, that take less of a manual touch, whether your deal registration workflows go to the right people and they are looked at accordingly and you have the right timing associated with it so you can move quickly so that a partner knows early on that they want to partner.
00:22:48.863 --> 00:22:51.351
We want to partner with them, just like they want to partner with us.
00:22:51.351 --> 00:22:57.103
So, again, moving it as quickly as we can to ensure that deals don't slip through the cracks.
00:22:57.103 --> 00:23:09.839
And then I think the other piece that we're starting to put a little bit more emphasis on now is pushing, I would say, more of the opportunity for partners to be able to quote our solutions without us in the door.
00:23:10.410 --> 00:23:16.421
Obviously, you think about things like in the managed environment, where partners have a given buy price with us.
00:23:16.421 --> 00:23:21.713
Then again they don't have to talk to us to turn on a customer in the environment, they just have to turn it on.
00:23:21.713 --> 00:23:22.916
We'll build them in arrears.
00:23:22.916 --> 00:23:24.582
That means it's fast.
00:23:24.582 --> 00:23:34.696
But for a partner or customer who is interested in quoting a deal, that's I would say it's relatively vanilla, let's just use that term.
00:23:34.696 --> 00:23:41.257
There's no reason why we can't give them a predictable price or a predictable set of prices or a predictable discount.
00:23:41.257 --> 00:23:43.642
To say, go out to market with this price.
00:23:43.642 --> 00:23:45.571
If you can sell it at that, great.
00:23:45.571 --> 00:23:49.181
And then, if we need to go a little bit deeper, we can come at that point.
00:23:49.181 --> 00:23:56.913
But at this point we're aligned that this is the right starting point where the market is probably likely to be willing to buy.
00:23:56.913 --> 00:23:59.843
So it's all about trying.
00:23:59.843 --> 00:24:03.272
I mean, the partner ecosystem is great for that scalability.
00:24:03.272 --> 00:24:09.920
You just have to figure out how and where to plug in the various pieces in a way that's going to be efficient for everybody.
00:24:11.049 --> 00:24:23.679
Yeah, I think that understanding a question I sort of really love asking sort of senior executives when I'm talking through uh channel designers, like which metric do you wish you could turn up to 99?
00:24:23.679 --> 00:24:31.859
And I think that that gives me a real clear indication in terms of like oh, okay, it's uh time to value for new partner acquisition.
00:24:31.859 --> 00:24:38.748
It's like okay, I can fully understand exactly what your channel design for the next 12 months looks like.
00:24:38.748 --> 00:24:48.181
Okay, we're going through rapid acquisition of partners and that amount of value is going to perform to a massive difference as opposed to you know, nrr through partner needs to improve.
00:24:48.181 --> 00:24:51.958
Okay, so we're on an upsell strategy and that real understanding.
00:24:51.958 --> 00:25:02.753
But it only works if you've got this great infrastructure of sort of data measurement, because then you can get super precise with your actions to influence a particular data point.
00:25:03.676 --> 00:25:12.019
Yeah, I think that's right and I think that what you're talking about is very much how we've looked at relaunching this particular program.
00:25:12.019 --> 00:25:25.881
You know, obviously there are all different sorts of metrics you could imagine in your mind, but if you can't measure them and you can't measure them predictably and on demand- not only is it useful for a partner, but it's not really useful for your own team.
00:25:26.289 --> 00:25:36.816
You know, if you've got to spend hours and hours trying to calculate something and you can't replicate it the next time you run it or the data changes or something happens, it's not really useful.
00:25:36.950 --> 00:25:47.393
Even if it may be interesting, it's not really useful as a measurement, and so you know, for us, in a subscription world that we live in, you know it does become okay.
00:25:47.393 --> 00:25:49.257
So what's important to the partner?
00:25:49.257 --> 00:25:58.991
Well, we can see that, based on how a partner may be valued in the market, what's important to us is that continuous like you talked about that NRR growth.
00:25:58.991 --> 00:26:09.506
We need to keep seeing not only that we have high retention, low churn, but also upsells, cross-sells, as our platform expands, as our opportunities expand within the market.
00:26:09.506 --> 00:26:12.878
So you know, it does become sort of those things.
00:26:12.878 --> 00:26:23.185
And you know, I think, as we start to review the specific details of the program, as folks come and take a a look at it, you'll see where our head is on a lot of these things.
00:26:23.185 --> 00:26:35.253
Um, but again, like, if you can't measure it consistently, it's interesting but not very useful in terms of how you want to have everyone roll in the same direction I couldn't agree.
00:26:35.334 --> 00:26:43.614
I think it if you, if you understand the data very clearly, it's actually quite quick to change behavior, right?
00:26:43.614 --> 00:26:56.055
If you say, hey guys, as a whole channel organization, we want to improve time to value for newly acquired partners, let's just pick a metric and you just say, off, you go work out how you think we can change that.
00:26:56.055 --> 00:27:03.016
People have great
ideas and they're suddenly extremely well aligned to a very particular and you very quickly see change.
00:27:03.016 --> 00:27:09.259
When you say something loose like, hey guys, we want to grow channel revenue, what does that mean?
00:27:09.259 --> 00:27:12.186
Right, like it's so, it's so ethereal.
00:27:12.186 --> 00:27:16.376
Um, and so, yeah, I think, uh, I think you guys have built it in a really strong way.
00:27:16.376 --> 00:27:21.093
Um, yeah, it's a couple of other like things that we've seen pretty recently.
00:27:21.113 --> 00:27:32.073
and again, I don't want to rabbit hole on this and I know we've got a lot of other topics, but you know we've, we've seen recently that um, even simple visibility of renewals that are coming on.
00:27:32.073 --> 00:27:40.862
So again, going back into the automation, you know very have very few process years of workflows tied around that, but you just make the renewals visible.
00:27:40.862 --> 00:27:44.578
That increases your attention rate by a percent.
00:27:44.578 --> 00:27:46.758
That's what the benchmark seems to be.
00:27:46.758 --> 00:27:49.758
Your distributors want this information.
00:27:49.758 --> 00:27:52.109
Your core focus partners want this information.
00:27:52.109 --> 00:27:56.038
They themselves have workflows, even if you don't know what they are.
00:27:56.941 --> 00:27:59.652
So that's an interesting point, even if you don't know what they are.
00:27:59.652 --> 00:28:00.473
So that's an interesting point.
00:28:00.473 --> 00:28:28.321
But I think the other thing that you kind of touch on is that classic rebate example where, hey, I've got a target that's in place and if you can provide transparency around where a partner is against achieving that target, you're much more likely to get someone to take a few extra minutes and try and pull something in or create something that may not have been there before in order for them to hit that target, which then is actually meaningful, particularly for the principles of the organization.
00:28:28.321 --> 00:28:35.743
But you know it's without that level of transparency and visibility, you lose sight of those opportunities.
00:28:36.690 --> 00:28:44.517
Yeah, and I think the thing that I really like, right, you gave a very specific data and sort of program answer to renewals.
00:28:44.517 --> 00:28:49.615
But marketing will give you a marketing answer and channel sales will give you a channel sales answer.
00:28:49.615 --> 00:28:50.357
And guess what?
00:28:50.357 --> 00:28:51.851
They're all useful, right.
00:28:51.851 --> 00:29:11.923
And so if marketing improves it a percent, and data improves it a percent, and sales improve it a percent, and suddenly you're looking across all renewals across a year, you're talking about huge revenue differences, right, the 3% improvement across all renewals in a 12-month life, that represents tens, hundreds of millions of saved or grown revenue.
00:29:11.923 --> 00:29:21.076
That is why I think having that sort of measurement infrastructure in place and then directing internal and external behavior, that's how you move mountains.
00:29:21.076 --> 00:29:30.920
At this podcast, we like to be a little bit data orientated, because we ask our current guests to recommend our next guest, which keeps everything flowing very nicely.
00:29:30.920 --> 00:29:32.163
Brian, who did you have in mind?
00:29:33.070 --> 00:29:36.621
So he's actually my former boss, Dave Crilley.
00:29:36.621 --> 00:29:51.752
He's had a number of different roles within channel marketing, channel sales, channel programming organizations, large and small, and he's just a wonderful, wonderful person to speak to.
00:29:51.752 --> 00:30:04.397
He's a super high thought leader in a lot of these cases, Worked with security companies for quite a bit, but also outside of the security space, and just has a really varied and interesting background.
00:30:04.397 --> 00:30:07.291
Also just a great conversationalist too.
00:30:07.311 --> 00:30:07.813
There we go.
00:30:07.813 --> 00:30:16.151
Well, my criteria for anyone who's not aware is they have to sort of have some level of channel vision, but, most importantly, not be boring, because it makes my life so much easier.
00:30:16.151 --> 00:30:18.237
It sounds like Dave hits both, which is great.
00:30:18.237 --> 00:30:19.800
Brian, it's been an absolute pleasure.
00:30:19.800 --> 00:30:21.536
Thank you so much for sharing your experiences.
00:30:21.836 --> 00:30:22.538
Yeah, my pleasure.
00:30:22.538 --> 00:30:24.538
It's been quite the conversation.
00:30:24.538 --> 00:30:25.974
I'm super happy to be here.
00:30:25.974 --> 00:30:27.278
Awesome Thanks, Brian.