ABOUT THIS EPISODE
Text us your thoughts on the episode or the show!
In today's episode, we talk with Irwin Hipsman, founder of Repititos, to explore the often-overlooked world of customer marketing and the critical role of customer contact data. Irwin shares findings from his recent research report on the state of customer contact databases, revealing why so many organizations struggle with poor data quality and how it impacts customer communications, renewals, and crisis response.
Together, they dive into:
- The definition of customer contact databases and why focusing on individuals—not accounts—is crucial.
- Key findings from Irwin's research, including an industry-average database health score of just 47%.
- The importance of cross-functional teams in maintaining healthy customer data.
- Actionable steps ops professionals can take to assess, clean, and maintain customer data health.
- Why better customer data translates directly into stronger customer relationships, higher retention, and better crisis management.
Whether you're in marketing ops, customer marketing, or revenue operations, this conversation offers practical insights that can help transform your organization's approach to customer data management.
Access the customer health score assessment here.
Access Irwin's report here.
Episode Brought to You By MO Pros
The #1 Community for Marketing Operations Professionals
SHOW NOTES 🔗
TRANSCRIPT 🔗
00:00:25.013 --> 00:00:30.574
Hello and welcome to another episode of OpsCast brought to you by MarketingOpscom, powered by all the MoPros out there.
00:00:30.574 --> 00:00:33.481
I am your host, michael Hartman, flying solo once again.
00:00:33.481 --> 00:00:41.823
Mike, I'm sure, is recovering from Spring Fling 2025 and is working, I'm sure.
00:00:41.823 --> 00:00:47.911
Anyway, joining me today to talk about the importance of customer marketing and customer data is Erwin Hipsman.
00:00:47.911 --> 00:00:56.237
Erwin is the founder of Repetitos, a consultancy which helps clients turn their customer data into a revenue-generating advantage.
00:00:56.237 --> 00:01:01.557
Prior to that, Erwin started and led Forrester's customer lifecycle marketing practice.
00:01:01.557 --> 00:01:06.713
Before Forrester, he held several leadership roles in customer marketing, engagement and advocacy.
00:01:06.713 --> 00:01:09.058
He started his career in sales and account management.
00:01:09.058 --> 00:01:10.640
So, erwin, thanks for joining me today?
00:01:11.042 --> 00:01:11.944
Yeah, looking forward to it.
00:01:11.944 --> 00:01:15.799
I'm a big fan of OpsCast and just give a little bit of quick background.
00:01:15.799 --> 00:01:31.558
I've been listening to it all the time and then in the February issue with Kobe Stock, it was you actually who gave this great quote about customer marketing and customer databases and why it's not a priority, and you know there are always campaigns to happen for it.
00:01:31.558 --> 00:01:37.179
It's in the report itself, that quote, and I just reached out and I said hey, you're talking about customer contact databases.
00:01:37.179 --> 00:01:38.302
Would you have me on?
00:01:38.302 --> 00:01:44.918
I'm just a regular solopreneur, not a fancy guy, not on the in crowd, and I really appreciate the opportunity to chat with you.
00:01:45.078 --> 00:01:46.995
Yeah, absolutely Well, I think it's one of those.
00:01:46.995 --> 00:01:52.832
We opportunity to chat with you.
00:01:52.832 --> 00:01:54.036
Yeah, absolutely Well, I think it's one of those.
00:01:54.036 --> 00:02:01.079
We'll get into this a little bit, but I think the idea that customer marketing was one of the ones where I think a lot of organizations, you know there's a missing opportunity there, right, and I think we'll talk about some of the background and reason why.
00:02:01.180 --> 00:02:13.618
But, yeah, so after you reached out, you know, you and I talked a little bit and you were working on you kind of alluded to it a paper that you I think is now published right On the state of customer contact database.
00:02:13.618 --> 00:02:22.632
So maybe just very top level because we may drill into some more what are some of the key takeaways from this customer contact database paper?
00:02:22.632 --> 00:02:46.212
And maybe just I think it would be good also because I think when I first heard this from you, I'd like for you to distinguish, when you say customer contact database, what you mean, because I think some people might, like me, have a broader idea of what that means it includes more than what I think you are focused on.
00:02:46.233 --> 00:02:56.305
Yeah, so by customer contact database I mean the individuals who, not the accounts at the account level, the individual level, who are those contacts?
00:02:56.305 --> 00:02:58.292
And there'll be two different types of contacts.
00:02:58.292 --> 00:02:59.914
Imagine a company like Salesforce.
00:02:59.914 --> 00:03:10.503
They might have 10 or 15 business relationships that they have within a particular account and then they'll have hundreds, if not thousands, of users.
00:03:10.503 --> 00:03:23.877
I'm less concerned with the individual users because customer marketing won't communicate with individual users, like I've never received an email from Salesforce about a new product update, even though I've been a user at every company I've been at.
00:03:23.877 --> 00:03:27.319
Those emails go to their 10, 15, 20 people.
00:03:27.319 --> 00:03:33.852
They have a relationship with the account, whatever segmentation, and then, if it's important, they'll let us know that there's a change that needs to happen.
00:03:33.852 --> 00:03:36.578
So it's really those anywhere.
00:03:36.578 --> 00:03:41.896
You know a small company might be three to four people, a larger company seven or eight people.
00:03:41.896 --> 00:03:43.039
Enterprise company.
00:03:43.039 --> 00:03:50.431
You know 15 to 20 people at the account that you need to communicate with and know who they are and keep track of.
00:03:50.431 --> 00:03:52.697
You know did they leave the company?
00:03:52.697 --> 00:03:54.701
Do they move to a different location?
00:03:54.701 --> 00:03:55.693
Do they have a new title?
00:03:55.693 --> 00:03:57.925
Who are the people you really need to keep track of.
00:03:57.966 --> 00:04:08.902
From an account management perspective, and as I've been talking to more and more sort of companies who are interested in thinking about what do I do with my customer contact database challenge, I realized there was no data out there.
00:04:08.902 --> 00:04:11.948
There's data on everything MQLs and all sorts of things.
00:04:11.948 --> 00:04:12.590
There was no data.
00:04:12.590 --> 00:04:15.961
It's like, okay, what is the state of customer contact databases?
00:04:15.961 --> 00:04:20.475
And everyone will say, yeah, it's not that good, but what does that really mean?
00:04:20.475 --> 00:04:37.557
And so I endeavored to do a research report that I published last week, and the four key takeaways are, first of all, the average score of customer contact database, and by that I don't just mean how accurate is the locations, it's more everything around it, like do you have an inventory?
00:04:37.557 --> 00:04:39.425
Can you send out a crisis communication?
00:04:39.425 --> 00:04:40.750
What are the open rates?
00:04:40.750 --> 00:04:42.053
What's the health of the database?
00:04:42.053 --> 00:04:54.620
The average score was not good, it was 47% and, like I said in the report, if we were in high school, it might be parent-teacher conference time, like who's our kid and you know why is he or she getting 47% on this test?
00:04:54.620 --> 00:05:08.985
And so that was key result number one, not a shock, and everyone I talked to said, yeah, that's about right, but looking at the underperformers versus the overperformers.
00:05:08.985 --> 00:05:17.710
We were able to say that by doing some of the things that we talked about in the report and I'll talk about the two key ones in a second you can get that score from 47 to 62%.
00:05:17.710 --> 00:05:19.356
Now we're talking about passing grade.
00:05:19.356 --> 00:05:20.956
It's never going to be above 80.
00:05:20.956 --> 00:05:24.399
So you know you're doing pretty well if you're in the 60s and 70s.
00:05:24.399 --> 00:05:33.878
We had some people who scored, you know, in the low 80s, the 60s and 70s, with some people who scored, you know, in the low 80s.
00:05:33.898 --> 00:05:36.306
And the two key factors that would impact the score the highest one's obvious, one's not obvious.
00:05:36.306 --> 00:05:49.523
So the non-obvious one is you know, do you have a group that meets on a formal, not an emergency, ad hoc basis could be weekly, monthly, quarterly that thinks about and coordinates customer communications as a whole?
00:05:49.523 --> 00:05:56.094
So here's this group of people in marketing, ops, customer marketing, customer success, product marketing, whoever it would be.
00:05:56.094 --> 00:05:59.302
They get together and say, okay, how are we communicating with customers?
00:05:59.302 --> 00:06:02.340
So if you have that, then you know.
00:06:02.340 --> 00:06:06.474
If you don't have that, that's a great way to impact that score, because they're going to ask all the tough questions.
00:06:07.174 --> 00:06:11.763
And then the second one is, which is very obvious, is the maturity of the segmentation.
00:06:11.763 --> 00:06:22.563
The more mature the segmentation you have, the better your overall customer contact data score will be, because it means you're thinking about well, how do we segment our audience?
00:06:22.563 --> 00:06:24.057
Is it by title?
00:06:24.057 --> 00:06:28.422
Well, that's, you know, a lot of people tend to segment by title, because that's easy, because you get their titles.
00:06:28.422 --> 00:06:32.019
What about their role vis-a-vis the product?
00:06:32.019 --> 00:06:35.320
You know, there are companies where CEOs will log in and be a user.
00:06:35.320 --> 00:06:38.677
There are companies where the CEO never logs in and they're just.
00:06:38.677 --> 00:06:41.062
You know, somebody gives them reports.
00:06:41.062 --> 00:06:45.837
So what are those different personas within the account that you want to be able to track?
00:06:46.018 --> 00:06:57.822
So just real quick, something that you hit on that just is this sort of analogous to the concept of buying groups on the pre-customer standpoint.
00:06:57.822 --> 00:07:03.461
So I don't know if you were in the Forrester part that was serious decisions.
00:07:03.461 --> 00:07:20.634
But that concept of buying groups that they originated, maybe they popularized, I don't know if they originated it, but that idea of identifying who are the people you need to be involved with to get a win on a deal with a customer, to carry that forward.
00:07:20.634 --> 00:07:24.556
It sounds like having something similar to that on the customer side is useful as well.
00:07:25.197 --> 00:07:26.081
Yeah, no, absolutely.
00:07:26.081 --> 00:07:32.817
I mean the number one reason when I was managing customer success teams, the number one reason why we lost the deal was we were single-threaded.
00:07:32.817 --> 00:07:45.317
So you know earlier I talked about you know, small companies needed three to six people in their customer contact database and some of them might not even be users, they might not be involved in the deal.
00:07:45.317 --> 00:07:46.895
But who are those extra people?
00:07:46.895 --> 00:07:52.498
And you probably need a new sort of role for them, so who might be called buying center?
00:07:52.498 --> 00:07:56.360
So I've got you know, let's say, 15 people in my customer contact database.
00:07:56.870 --> 00:08:02.840
These three are users, these two are influencers and these five are just people we want to keep an eye on.
00:08:02.840 --> 00:08:04.917
Like are they moving within their company?
00:08:04.917 --> 00:08:06.152
Did they leave the company?
00:08:06.152 --> 00:08:10.837
They don't use the product but they may.
00:08:10.837 --> 00:08:22.297
In six months they may have a new role that all of a sudden uses it and now they've got to learn about your product and you would communicate with them very differently because they're not a user.
00:08:22.297 --> 00:08:25.907
But absolutely it's that expansion beyond just those five people who the CSMs talk to.
00:08:25.907 --> 00:08:28.857
Who else do you need to know within the account?
00:08:28.857 --> 00:08:29.440
Got it?
00:08:29.600 --> 00:08:29.841
Okay.
00:08:29.841 --> 00:08:43.716
So I know you said that you might not be like users of whatever product service you have might not be the primary people you want to focus on communicating with as customers.
00:08:43.716 --> 00:08:46.571
Do you think that's my?
00:08:46.571 --> 00:09:11.327
I initially went to the idea of like PLG type SaaS companies right, where it's probably maybe a little bit different because you especially in the phase before, maybe if you have a freemium kind of model where you could have users who are not paying yet their customers, so you're going to be communicating to them, but it's maybe still considered not.
00:09:11.327 --> 00:09:17.598
Maybe it's a differentiation between a freemium customer versus a paying customer and maybe that's a distinction.
00:09:17.598 --> 00:09:31.082
But do you think there's a difference there where you do want to do communications to customers, especially paying customers in a PLG-type organization, or do you still think it's most important to have a limited set?
00:09:31.082 --> 00:09:32.535
Who are your core people?
00:09:34.757 --> 00:09:51.361
Well, it depends on the company, obviously, but anybody who you would need to, you'd want to communicate with and, depending on that segmentation, so, like when I was a forester, when I started, the average email there were like 15,000, were that we really focused on.
00:09:52.250 --> 00:09:54.236
The average email went out to about 1200 people.
00:09:54.236 --> 00:09:55.961
I time I left it went out to 800 people.
00:09:55.961 --> 00:10:10.690
So you know who is that, who's the audience for that particular communication and how do you know, how do you really do that, that deep segmentation, so you're not sending information to think to people that they don't really care about, so you're not sending information to people that they don't really care about.
00:10:10.690 --> 00:10:21.136
And so in a PLG world, yeah, you know they might be that user, might be a segment that gets a very different type of communication than somebody else than, like, the admins would get.
00:10:21.136 --> 00:10:24.978
You know who get a very different, you know, obviously, very different type of communication from each other.
00:10:24.978 --> 00:10:29.800
And that's, you know that gets, you know that's, a much more mature organization than most.
00:10:29.800 --> 00:10:38.685
And you can't do that without a healthy customer contact database, because if you don't have the titles right, particularly the titles, then it gets to be a real challenge.
00:10:39.045 --> 00:10:39.726
Well, and titles?
00:10:39.726 --> 00:10:43.107
I mean you said titles are easy to segment by.
00:10:43.107 --> 00:10:59.119
I would say that, yeah, on the surface it seems like it's easy, but as soon as you start to get any level of detail it can be misleading, because just take the example like we only want to communicate to vice presidents, right, that sounds great, until you start talking about financial services firms.
00:10:59.179 --> 00:10:59.500
Of course.
00:10:59.581 --> 00:11:06.134
Right, where, like, virtually everybody's a vice president of something, even though that's not really the.
00:11:06.134 --> 00:11:12.937
It doesn't correspond to the level of responsibility as a vice president in many other organizations, or the size of the organization matters.
00:11:12.937 --> 00:11:22.404
Right, a vice president at a small organization might be equivalent to a director or even a senior manager at a really large organization in terms of scope of responsibility.
00:11:23.290 --> 00:11:24.555
Yeah, a lot of companies have title inflation.
00:11:24.555 --> 00:11:27.597
We're not going to give you a raise, but we're going to give you a nice title.
00:11:27.932 --> 00:11:29.687
It's like oh, but I'm still doing the same thing.
00:11:29.687 --> 00:11:31.475
Yeah, I haven't used that term.
00:11:31.475 --> 00:11:37.800
That is a term I have used a lot and I think it's particularly common in marketing and marketing ops too.
00:11:37.800 --> 00:11:38.582
Yeah, exactly.
00:11:38.582 --> 00:11:41.077
So that's a whole.
00:11:41.971 --> 00:11:43.492
And AI can only do so much, I mean.
00:11:43.492 --> 00:11:51.703
Ai can drop a list of 10,000 people in a spreadsheet and tell what to do, but there are going to be a lot of subtleties around the edge that's just not going to pick up.
00:11:52.605 --> 00:11:59.353
Yeah, so I just want to make sure I understand.
00:11:59.353 --> 00:12:05.105
So when you talk about customers, you're talking about people who have actually paid for whatever product or service.
00:12:05.105 --> 00:12:06.509
You Absolutely actually paid for whatever product service.
00:12:06.509 --> 00:12:16.762
You Absolutely People from companies or organizations or individual people who have paid for your product or service, as opposed to prospects or leads Absolutely yeah.
00:12:17.030 --> 00:12:18.477
Prospects in a whole different world.
00:12:18.477 --> 00:12:31.563
Accuracy I mean I would argue that if I had a customer contact database and let's say I did some basic segmentation my most important people, my medium important people, my least important people you would never segment by that.
00:12:31.563 --> 00:12:32.533
Let's just keep it simple.
00:12:32.533 --> 00:12:41.779
I would argue that you probably need 98% accuracy on your most important people and the medium important people may be 90%.
00:12:41.779 --> 00:12:44.973
The least important people may be 80% and you don't worry about them.
00:12:44.973 --> 00:12:46.819
You focus on those first two tiers.
00:12:48.170 --> 00:12:57.765
But it seems like to me I don't know what like that seems like they would all be higher in terms of the level of quality and trust you have in that data compared to people who are pre-customer stage.
00:12:58.528 --> 00:13:00.595
Yeah, exactly like no, you want to know.
00:13:00.595 --> 00:13:02.780
Location is really important because you start doing events.
00:13:02.780 --> 00:13:06.476
You know I've worked for swiss companies and they think I'm in switzerland.
00:13:06.476 --> 00:13:09.624
They invite me to events in London and I'm living in Boston.
00:13:09.624 --> 00:13:13.180
They never invite me to an event in Boston because they assume I live where the headquarters is.
00:13:13.180 --> 00:13:16.238
You know that's where it starts hurting people across the organization.
00:13:16.238 --> 00:13:19.499
Other people not just marketing ops and not just customer marketing.
00:13:19.759 --> 00:13:41.221
Yeah, you know, it's funny you bring that up, that idea of location, and I can remember a specific example at a company I worked for where a lead had come in, got routed because there was some data app request from one country to another country, which meant a whole different region for lead, like where the SDR would be.
00:13:55.750 --> 00:14:03.983
Sdr picks it up, turns out what happened is and I think of the countries were Australia and India and it'll make more sense.
00:14:03.983 --> 00:14:19.111
So when it got routed to the wrong place and people were like what happened and it's not a great thing Digging through what happened the data got appended, changed it from Australia to New Zealand or Australia to India.
00:14:19.111 --> 00:14:24.399
That's because the person actually based on LinkedIn profile or whatever, was in India.
00:14:24.399 --> 00:14:33.211
But it also was pretty evident by looking at the profile the person worked for the kind of company that was a service provider to other companies, right outsourced type work.
00:14:33.211 --> 00:14:41.356
My suspicion I don't know that ever got validated was that person was because he put in another company name in australia, like.
00:14:41.356 --> 00:15:05.230
So my guess is he's working on, being working on as a consultant contractor for third-party company based in Australia, was doing some research for them, and it got rerouted to somebody because company name got changed, location got changed, but that's not really what the intent was right, and so that's the kind of stuff that can go wrong if you're not careful.
00:15:05.250 --> 00:15:08.615
And if you have translations, then I'm getting everything in Swiss German, and I happen to, even if I was in Switzerland.
00:15:08.615 --> 00:15:08.924
I have translations.
00:15:08.924 --> 00:15:10.813
Then I'm getting everything in Swiss German and I happen to, even if I wasn't Swiss, I do Swiss French.
00:15:10.813 --> 00:15:12.240
I'm getting everything in German.
00:15:13.610 --> 00:15:14.815
Yeah, so I think, yeah.
00:15:14.815 --> 00:15:20.553
So it's interesting because it makes sense that you really want that customer data.
00:15:20.553 --> 00:15:32.814
But if a big part of that score you talked about on your report that it was 47%, I'm going to guess that a part of that score you talked about on your report that it was 47%, I'm going to guess that a part of that is because it just wasn't accurate enough to be able to action on.
00:15:33.035 --> 00:15:37.057
Okay, now, one of the questions we ask people is you know, how would you rate the accuracy of your database?
00:15:37.057 --> 00:15:40.019
You know accuracy and usability of it.
00:15:40.019 --> 00:15:43.996
People may not know the accuracy of it, but they do know the usability of it.
00:15:43.996 --> 00:15:45.115
They have a gut sense of that.
00:15:46.289 --> 00:16:02.539
Yeah, yeah, knowing that our audience is primarily ops type people, something you and I talked about is that it would be good for people in these roles to better understand how to support customer marketing.
00:16:02.539 --> 00:16:09.518
That's even if a company even has a customer marketing focus at all, which I'm finding less and less common.
00:16:09.518 --> 00:16:20.374
So one of the suggestions you shared with me was that really you might like, if you're a marketing ops, like, yes, you should be coordinating with sales.
00:16:20.374 --> 00:16:24.616
You know sales ops if there's a sales ops function in your marketing ops.
00:16:24.616 --> 00:16:29.283
But your suggestion is like also reach out to customer success or customer support, depending on what you have in your marketing ops.
00:16:29.283 --> 00:16:33.939
But your suggestion is like also reach out to customer success or customer support, depending on what you have at your organization, and learn how to collaborate with them as well.
00:16:33.939 --> 00:16:36.937
And then, obviously, a customer marketing team if there is one.
00:16:36.937 --> 00:16:43.730
So talk about maybe talk a little more about that and why that would be beneficial for our folks in our office.
00:16:43.750 --> 00:16:46.754
Yeah, I've thought with a story when I was at a company called Crimson Hexagon.
00:16:46.754 --> 00:16:50.010
It's not there anymore social media analytics.
00:16:50.010 --> 00:16:53.471
You know we would go to marketing ops and we need to send this customer communication out.
00:16:53.471 --> 00:16:56.014
And they go, well, we'll do it at the end of the month.
00:16:56.014 --> 00:16:58.434
And it's like, well, no, we need it sooner than that.
00:16:58.434 --> 00:17:00.375
And the end of the month would come.
00:17:00.375 --> 00:17:08.799
It's like no, we didn't get any emails out the door to the customers.
00:17:08.799 --> 00:17:11.882
Can I just buy my own email marketing package?
00:17:11.882 --> 00:17:13.202
And she said, yeah, just do it.
00:17:13.202 --> 00:17:15.504
So we bought our own email marketing package.
00:17:15.504 --> 00:17:21.467
It took a year for the marketing office people to realize we had done that because we left them alone.
00:17:21.507 --> 00:17:26.511
We stopped asking and then they got really mad at us, like what do you mean you're doing this?
00:17:26.511 --> 00:17:30.160
We said you know we can't get any emails out to her because we always get pushed to the end of the line.
00:17:30.160 --> 00:17:33.291
And then they said okay, cancel the contract.
00:17:33.291 --> 00:17:35.758
We will put you in the line like everyone else.
00:17:35.758 --> 00:17:46.300
And so in every company I've worked at, I've never had a marketing ops person come to me and say hey, you communicate with customers all the time.
00:17:47.363 --> 00:17:48.764
What can we do to help you?
00:17:48.764 --> 00:17:49.405
What do you need?
00:17:49.405 --> 00:18:10.541
Well, you know, what would be really helpful is a field in the CRM that lets us know what the person's Gmail address is, because when we first meet them, they put their non-company address in, but once they become a customer, then you replace it with their company address.
00:18:10.541 --> 00:18:17.815
We want to know what their Gmail address is because when that person leaves, we want to be able to reach out to them because they're a potential lead.
00:18:17.815 --> 00:18:23.994
But we don't have their email anymore, and now we've got to send in mails through LinkedIn and they don't open them up.
00:18:23.994 --> 00:18:25.200
Wouldn't it be nice?
00:18:28.549 --> 00:18:30.023
And it's like oh yeah, we never thought about that.
00:18:30.023 --> 00:18:30.649
That's actually a good idea.
00:18:30.649 --> 00:18:35.721
What's funny is there are now platforms that try to mimic that.
00:18:35.721 --> 00:18:39.118
You've spent a lot of money, like track people moving.
00:18:39.118 --> 00:18:45.578
What you just described would be a pretty simple I'm assuming, as long as there's some discipline, like anything else.
00:18:45.578 --> 00:18:50.100
Right, maintaining that personal email address along with their work email address?
00:18:50.100 --> 00:18:51.976
Yeah, I mean, I would encourage people to.
00:18:52.811 --> 00:18:56.557
I would encourage companies, when they have those landing pages, to ask people for their Gmail address.
00:18:56.557 --> 00:19:05.855
And then you know, as they move through that, through the pipeline, and they hit a certain stage now let's get their company address, but now you've got both.
00:19:05.855 --> 00:19:09.396
And it's counterintuitive that you need both email addresses, but now you've got both.
00:19:09.396 --> 00:19:10.820
And it's counterintuitive that you need both email addresses.
00:19:10.820 --> 00:19:17.942
But if you think about customers, not prospects, then having their Gmail address is really helpful, because 20% of all people leave their employers every year.
00:19:17.942 --> 00:19:19.330
Yeah, Crazy.
00:19:20.132 --> 00:19:24.097
Yeah, I never even would have thought of that.
00:19:24.097 --> 00:19:27.462
Like's like, right there, I think is worth worth the time here.
00:19:27.462 --> 00:19:44.118
Yeah, um, so you, you mentioned the idea of of of being able to do a crisis communication to customers right as a challenge, and I probably said it before, like one of the hardest things to do to fulfill in marketing ops is, hey, we need to send a letter.
00:19:44.118 --> 00:19:53.743
You send an email to our customers, right, and, as your research is evidence right, most that is a really way harder thing than it should be to do.
00:19:53.743 --> 00:20:00.793
So take crisis communications in particular Like what can?
00:20:00.793 --> 00:20:07.048
Why do you think it's so hard for companies to be able to identify those key people?
00:20:07.048 --> 00:20:18.431
And then what can we do to try to, what can our listeners do to try to help their organizations be better prepared to do that kind of thing?
00:20:19.095 --> 00:20:19.375
Yeah, I mean.
00:20:19.375 --> 00:20:20.521
Think about a B2C company.
00:20:20.521 --> 00:20:23.324
Think about United Airlines with Newark and what's going on.
00:20:23.324 --> 00:20:31.655
They have a playbook that says if we have a massive outage in one of our airports, this is how we communicate with the media.
00:20:31.655 --> 00:20:33.701
This is how we communicate with our customers.
00:20:33.701 --> 00:20:36.503
This is how we communicate to customers who aren't impacted.
00:20:36.503 --> 00:20:38.634
These are how we communicate with customers who are impacted.
00:20:38.634 --> 00:20:48.049
They're literally on their way to the airport, so they've got playbooks because they know that the cost of not doing that is just huge.
00:20:48.934 --> 00:20:53.826
B2b companies maybe don't think of their product as being that essential.
00:20:53.826 --> 00:21:01.644
I would argue that if somebody spent $40,000, $50,000, $100,000 on a product, they want to go in and see the dashboard, go in and use it.
00:21:01.644 --> 00:21:10.502
And if there's a crisis communication or just a major communication we're announcing a merger we want to let you know because it's going to be in the newspaper tomorrow.
00:21:10.502 --> 00:21:12.801
That gets to segmentation.
00:21:12.801 --> 00:21:14.359
Like, who are those people?
00:21:14.359 --> 00:21:21.445
Because you don't want to send to every Salesforce user that we just purchased a company and here's the impact to you.
00:21:21.445 --> 00:21:25.826
You want to be able to do some pretty quick and heavy segmentation.
00:21:25.826 --> 00:21:33.565
Well, these are the people we need to communicate with, and we only need to communicate with companies in North America and we only need to communicate with companies that have this sort of profile.
00:21:34.055 --> 00:21:37.665
Okay, that 100,000-person list is now down to $10,000.
00:21:37.665 --> 00:21:44.258
Now, assuming that there's another part to it, which is the email needs to get written, so that's on corporate comms.
00:21:44.258 --> 00:21:45.240
So I don't worry about that.
00:21:45.240 --> 00:21:48.445
Somebody needs to get written, so that's on corporate comms.
00:21:48.445 --> 00:21:49.387
I don't worry about that.
00:21:49.387 --> 00:21:51.432
Somebody needs to hit the send button.
00:21:51.432 --> 00:21:52.153
I begin to worry about that.
00:21:52.153 --> 00:21:56.254
And then you know, we in customer marketing need to be able to do the segmentation because you know, we know the subtleties.
00:21:56.254 --> 00:22:09.189
So you know, if the CEO calls the head of corporate comms 9 pm on Friday, on Tuesday and we need an email out by Wednesday, you know, are all those pieces in place or no?
00:22:13.514 --> 00:22:13.796
it's a draw.
00:22:13.816 --> 00:22:15.343
Everybody has to drop everything because nobody has the playbook.
00:22:15.343 --> 00:22:20.401
So you know, when I was in customer marketing, I would go to the CMO and say, hey, if we need to send an emergency communications out, do we have a playbook?
00:22:20.401 --> 00:22:22.615
It's like no, why would we ever need that?
00:22:22.615 --> 00:22:23.978
Well, what if?
00:22:23.978 --> 00:22:34.779
Why don't we develop something so that if there is an emergency, everyone sort of knows what we do and once a year we sort of remind everybody what that is?
00:22:34.779 --> 00:22:49.703
To me, it's an insurance policy for everyone's jobs, because if I was CEO and we couldn't get that out the door and the open rates were only 5% because we didn't know who to send it to, or send it to people who didn't care, that would be, oh my God, why do I have a marketing team?
00:22:49.703 --> 00:22:50.859
Why do I have a customer marketing team?
00:22:50.859 --> 00:22:54.546
Why have a marketing ops team if you can't do an emergency communication?
00:22:54.546 --> 00:23:03.506
So I think it's that awareness and it's the playbook, and marketing ops plays a key role because in some ways, they're the ones who hit the send button.
00:23:04.027 --> 00:23:04.206
Yeah.
00:23:04.206 --> 00:23:24.627
So I'm going to tie this back to one of the things you said is I think what you said is that the companies in your research that were higher rated in terms of their customer database tended to have a cross-functional team that had a regular focus on that.
00:23:24.627 --> 00:23:49.545
So if I'm kind of putting some things together like one step is just saying we need to have that dedicated team that at least part of their job is to be thinking about customer database, it sounds like having a plan for how we're going to execute on different types of key customer communications, whether it's crisis or whether it's an announcement, whether it's a more general one, whatever.
00:23:49.634 --> 00:23:50.881
A product release would be a classic.
00:23:51.035 --> 00:23:53.704
Yeah, changing our terms of service or whatever.
00:23:53.704 --> 00:24:02.905
And then it feels like also a part of that might be what are the gaps in our current infrastructure?
00:24:02.905 --> 00:24:14.065
Both people process technology probably heavy on technology where if we had to do something tomorrow like this would be prioritized, like these are the things we should go try to.
00:24:14.065 --> 00:24:21.951
I'll say fix Fix may not be the right word, but fix so that we are going to be able to do those things.
00:24:21.951 --> 00:24:22.811
So then have that play.
00:24:22.811 --> 00:24:25.783
It feels like all those things would be really valuable.
00:24:27.337 --> 00:24:29.325
And to some degree, not actually that complicated to do.
00:24:30.135 --> 00:24:32.259
And that's why that group has such a big impact.
00:24:32.259 --> 00:24:35.627
If you have that group, your customer contact database health school will be higher.
00:24:35.627 --> 00:24:36.956
The three things you know.
00:24:36.956 --> 00:24:37.819
Let's say you don't have one.
00:24:37.819 --> 00:24:40.527
It's like, oh my God, michael and Erwin, that was a great suggestion.
00:24:40.527 --> 00:24:41.495
Let's, you know, let me pull.
00:24:41.495 --> 00:24:44.697
Let's start pulling that together within you know, within my company.
00:24:44.697 --> 00:24:45.959
Let's start pulling that together within my company.
00:24:45.979 --> 00:24:51.701
And the number one task I would ask them to do is create an inventory of all the one-to-many communications that are sent out from the company.
00:24:51.701 --> 00:24:53.543
What's product sending, customer success?
00:24:53.543 --> 00:24:58.047
What are those automated emails that no one's ever looked at in the past three years?
00:24:58.047 --> 00:24:59.146
What do they look like?
00:24:59.146 --> 00:25:02.349
Yes, I think you'd be shocked what they look like.
00:25:02.349 --> 00:25:05.751
So let's get that inventory of the things that we combine.
00:25:05.751 --> 00:25:11.415
What are the open rates you know?
00:25:11.415 --> 00:25:12.118
How do we improve the open rates?
00:25:12.118 --> 00:25:12.681
You know who actually said.
00:25:12.681 --> 00:25:14.869
You know who hits the send button, who you know who writes the content you know.
00:25:14.869 --> 00:25:17.581
So there are probably seven or eight things you want to know in the inventory.
00:25:17.581 --> 00:25:19.430
What platform you know?
00:25:19.430 --> 00:25:23.539
Because at Forrester we have three different platforms for emails to go out the door.
00:25:23.539 --> 00:25:24.801
So which platform is on?
00:25:24.801 --> 00:25:26.104
Who owns that platform?
00:25:26.545 --> 00:25:37.625
The second thing I would do is I would do a quick take 400 names at random of your customer contact database and divvy it up amongst a group.
00:25:37.625 --> 00:25:39.060
Each of us has 50 names.
00:25:39.060 --> 00:25:42.244
Let's go into LinkedIn and see what does it look like?
00:25:42.244 --> 00:25:44.000
What's their title?
00:25:44.000 --> 00:25:46.027
Are they still employed by the company and location?
00:25:46.027 --> 00:25:51.446
You probably won't be that far off to say, okay, this is the state of our customer contact database.
00:25:51.446 --> 00:25:56.576
20% of our people this is what I've learned working with customers aren't employed at the company anymore.
00:25:56.576 --> 00:25:59.944
30% we have the wrong title and 40% we have the wrong location.
00:25:59.944 --> 00:26:03.017
Not worry about fixing it yet, but just assessing it.
00:26:03.257 --> 00:26:05.898
Right, kevin, it's almost like a scorecard.
00:26:06.379 --> 00:26:11.223
Yeah, and the third would be if we have a crisis, can we get an email out the door?
00:26:11.223 --> 00:26:13.046
Let's look at that and figure that out.
00:26:13.046 --> 00:26:16.608
Those three things alone would keep that group busy for probably 90 days.
00:26:16.608 --> 00:26:26.178
That's a great 30, 60, 90 for that group, and then you report back to people.
00:26:26.178 --> 00:26:27.023
Well, you know, our database isn't good.
00:26:27.023 --> 00:26:30.401
Okay, now let's figure out who do we need to bring in, what resources, what allocation to fix it.
00:26:30.401 --> 00:26:38.221
Again, it's a journey that could take three or four more months to do, but you at least know what you're doing and we can't do a crisis communication.
00:26:38.221 --> 00:26:40.606
So let's get corporate comms involved in this.
00:26:40.606 --> 00:26:44.405
Let them head it up and say, hey, let's figure out what the playbook is going to be.
00:26:48.514 --> 00:26:49.299
Those three things alone would be huge.
00:26:49.299 --> 00:26:51.773
Yeah, and it feels like maybe I'm a step beyond here.
00:26:51.773 --> 00:26:55.555
I'm going to kind of go back to different points in my career.
00:26:55.555 --> 00:27:09.778
I was involved with helping customer support teams, kind of not really on the marketing focus, but I'd always felt like there was a great opportunity with customer support teams, like they're interacting with customers on a regular basis.
00:27:09.778 --> 00:27:19.772
As part of their role should be, or could be, to help improve the health and the quality and the completeness of customer data.
00:27:20.575 --> 00:27:24.163
Yeah, so in the process of solving customer problems.
00:27:24.163 --> 00:27:24.723
They could do that.
00:27:24.865 --> 00:27:25.968
Yeah, I mean two things.
00:27:25.968 --> 00:27:37.988
One, the problem with that is more and more companies are outsourcing their support to AI, so customer support teams are one of the teams that's really getting hurt by bots and AI.
00:27:37.988 --> 00:27:46.348
Second is that you know when, like you call Blue Cross, blue Shield, they always will confirm is this the right email?
00:27:46.348 --> 00:27:47.681
Is this the right phone number for you?
00:27:47.681 --> 00:27:53.782
Do you still live wherever you live Now, because they're updating their database all the time?
00:27:53.782 --> 00:27:57.223
Yeah, now, who was it?
00:27:57.694 --> 00:27:59.402
Venmo did this amazing thing.
00:27:59.402 --> 00:28:02.600
All of a sudden, just out of the blue, they said hey, we just want to double check.
00:28:02.600 --> 00:28:05.178
Is this still your best phone number, still your email address?
00:28:05.178 --> 00:28:17.296
Because they had built it into their system to update, because people do change email addresses to update it.
00:28:17.296 --> 00:28:20.329
So it'd be a big ask for a B2B company, when somebody logs in, for a little box to come up and says, hey, this is where we have you as located.
00:28:20.329 --> 00:28:20.952
Is this all correct?
00:28:20.952 --> 00:28:32.925
I think it's a lot to ask, but I think there are points in various interactions that support would be a good one, even if it's AI and bot At the end of that interaction say hey, we have you as this address.
00:28:32.925 --> 00:28:36.100
You know, here's your contact information.
00:28:36.100 --> 00:28:37.394
Can you please update it Now?
00:28:37.394 --> 00:28:42.402
A lot of people won't, but some people will, and it'll at least help you.
00:28:42.402 --> 00:28:43.645
You know, get along the way.
00:28:49.979 --> 00:28:53.687
You're never going to have a 100% accurate database, but it should be a lot better than it is today.
00:28:53.687 --> 00:28:54.569
Okay, that all makes sense.
00:28:54.569 --> 00:28:56.093
Okay, I love this idea of again.
00:28:56.093 --> 00:29:00.790
I'm just sort of absorbing all this and going like, actually, this doesn't seem like it'd be that hard.
00:29:00.810 --> 00:29:01.454
I know that's a funny thing.
00:29:01.836 --> 00:29:02.518
It's not that hard.
00:29:02.518 --> 00:29:23.019
Which brings me to one of the things I learned early on when I kind of transitioned to marketing is this whole concept of that it's much less expensive to retain a customer than to acquire a new customer, right?
00:29:23.019 --> 00:29:34.825
It continues to baffle me why more companies are not really it feels like similar to the four Ps right that really only one of the Ps matters anymore promotion.
00:29:34.825 --> 00:29:46.335
But it feels like over the last 15, 20 years, this idea, this very classic understanding that it costs less to retain customers, has kind of been lost a little bit.
00:29:46.335 --> 00:29:48.321
So what do you attribute that to?
00:29:48.321 --> 00:30:01.035
Right, like, why aren't more companies and maybe it's more true in smaller early stage companies than it is on growth as a priority than it is at larger enterprise companies?
00:30:01.035 --> 00:30:06.187
But it still feels like there's this general trend that customer marketing is not really a focus area.
00:30:07.075 --> 00:30:12.427
Yeah, there are two types of customer marketers out there and this is an important distinction.
00:30:12.427 --> 00:30:27.104
If you think about the past 30 years, customer experience is a discipline that's been around a long time More B2C, but certainly in the B2B world, customer success has been around 15 years more in the B2B world, less in the B2C world.
00:30:27.104 --> 00:30:36.674
Customer marketing is the newbie on the block and when customer marketers first came on board, they were really customer advocate practitioners.
00:30:36.674 --> 00:30:49.701
Their job was references and reviews, referrals, things like that case studies, stories, videos, and I think that and this is a self-criticism we all sort of boxed ourselves into.
00:30:49.701 --> 00:30:51.385
Well, we're the case study people.
00:30:51.385 --> 00:30:55.806
We're the people that if you need a reference, call us up, but you know.
00:30:57.317 --> 00:30:59.523
It all feeds back into our acquisition.
00:31:00.626 --> 00:31:01.028
Right right.
00:31:01.797 --> 00:31:02.902
And it's all about new logo.
00:31:03.295 --> 00:31:04.883
Because case studies don't go to existing customers, they go for new logos.
00:31:04.883 --> 00:31:07.074
Yeah, because case studies don't go to existing customers, they go for new logos.
00:31:07.074 --> 00:31:07.335
Yeah.
00:31:07.335 --> 00:31:13.625
Over the past few years we're starting to see and I made that pivot I've directed four, started up four customer marketing practices.
00:31:13.625 --> 00:31:24.170
The first two were customer advocacy, the last two I started pivoting and that's why I'm so passionate about customer contact databases into what's called lifecycle marketing.
00:31:24.555 --> 00:31:29.000
Now some companies think of life cycle as from prospecting to renewal.
00:31:29.000 --> 00:31:31.982
I'm talking about post sales life cycle marketing.
00:31:31.982 --> 00:31:39.702
So everything from onboarding to nurturing, and that's where, obviously, customer contact databases become really critical things like that.
00:31:39.702 --> 00:31:47.341
And probably early on, 100% of the people were advocacy practitioners.
00:31:47.341 --> 00:31:49.978
Three, four years ago it's like 90, 10.
00:31:49.978 --> 00:31:51.415
Now it's more like 70, 30.
00:31:51.415 --> 00:32:10.616
And beginning to see more and more customer advocacy people realizing that pure customer advocacy is probably, unless you're at a large company, is probably not a long-term strategy because that's where a lot of the layoffs have been is in that we have a customer marketing team of three we're going to you know they just do stories.
00:32:11.110 --> 00:32:14.836
I don't mean to be flip, but not that they just do stories, but the way the executives think about it.
00:32:14.836 --> 00:32:18.881
Yeah, that is a perception and it's unfortunate, but it's true.
00:32:18.901 --> 00:32:21.417
Yeah, so we only need one person to, we still have it.
00:32:21.417 --> 00:32:32.392
But if one of those people was a customer lifecycle market, it Lifecycle market is like oh, that person is, they're helping us identify people to cross-sell.
00:32:32.392 --> 00:32:34.933
They're the ones sending out crisis communications or paying attention to it.
00:32:34.933 --> 00:32:38.537
They're the ones that are doing the one-to-many communication.
00:32:38.537 --> 00:32:42.460
The product team loves them because product team doesn't have to think about who needs to.
00:32:42.460 --> 00:32:46.962
They'll write the message, but they're the ones who figure out who needs to get that message.
00:32:46.962 --> 00:33:07.664
So, as customer advocates transition to lifecycle marketers and I would argue that it'd probably be better for a customer advocate's person to transition to lifecycle because they understand customers as opposed to a marketing ops prospecting person transition over to customer lifecycle.
00:33:07.664 --> 00:33:13.999
Yes, they'll understand how Marketo and Eloquent all these systems work, but they're not going to understand what motivates customers.
00:33:13.999 --> 00:33:28.576
So their lens is the operational lens and the customer advocate lens is they're thinking from the customer experience, customer relationship lens, and you could teach the other one.
00:33:28.576 --> 00:33:33.341
It's really hard to learn the way customers tick within an organization.
00:33:33.950 --> 00:34:02.298
Yeah, at the same time I probably have said this dozens of times on the podcast and certainly outside of it that marketing and marketing ops people need to spend more time understanding customers, whether that's through sitting in or listening to sales calls, or sitting in or listening to customer success or whatever their organization has that is focused on retaining customers and helping them.
00:34:02.298 --> 00:34:04.752
I think it's an important one.
00:34:04.752 --> 00:34:08.430
I'm a big believer that context matters Exactly Otherwise exactly.
00:34:08.791 --> 00:34:19.959
Otherwise, if you don't really understand the context of why you're being asked to do something, you may fulfill the exact thing that you're being asked to do, but it may not actually be what's needed, or there might be a better way to do it.
00:34:20.820 --> 00:34:26.003
With customers, context is harder to assess and even more important than with prospects.
00:34:26.003 --> 00:34:31.768
Because prospects, yes, there is a context, but they're a little bit easier to think about than customers.
00:34:31.768 --> 00:34:37.342
Because customers will change also what their relationship with you is and what their needs are vis-a-vis your product.
00:34:37.730 --> 00:34:39.016
If they get promoted or moved to.
00:34:39.016 --> 00:34:42.897
You know they're on a special project for three months, so they're not going to use your software.
00:34:42.897 --> 00:34:44.556
All of a sudden alarm bells ring.
00:34:44.556 --> 00:34:45.775
They haven't logged in in three months.
00:34:45.775 --> 00:34:45.836
No.
00:34:45.836 --> 00:34:46.358
A sudden alarm bells ring.
00:34:46.358 --> 00:34:47.122
They haven't logged in three months.
00:34:47.122 --> 00:34:48.689
No, they're perfectly happy, they're just on another project for three months.
00:34:48.689 --> 00:34:48.890
Yeah, yeah.
00:34:49.550 --> 00:34:49.730
I mean?
00:34:49.730 --> 00:35:04.950
I think I mean one another kind of, maybe, thought experiment that people in marketing ops could do is to think about you know what it's like for them with their vendors, right?
00:35:04.950 --> 00:35:14.780
So how does my view of that vendor change over time from when I'm in their mind, right, a prospect or a potential buyer become a buyer.
00:35:14.780 --> 00:35:16.555
We purchase something.
00:35:16.555 --> 00:35:23.502
We now are onboarded and you know, because I think by nature of it is, I think about my own times going through that.
00:35:23.502 --> 00:35:28.240
Right, the things I care about change over that time.
00:35:28.382 --> 00:35:36.090
Right, and I think it's a really important, like what I care about as I'm going through the evaluation to purchase stage.
00:35:36.090 --> 00:35:39.936
It's going to be like I very much want to make sure, like, will this actually work?
00:35:39.936 --> 00:35:46.853
Do I believe that the solution will be worth the cost over time and the change effort or whatever that goes into it?
00:35:46.853 --> 00:35:58.470
Once that I go over that, then I want them to be depending on what it is right I think it's software in particular I want them to be a partner with me and I want them to be responsive.
00:35:58.470 --> 00:36:11.056
I want them to try to understand me and our business in a level of detail deeper than what it was before, and I think maybe that's the flip.
00:36:11.056 --> 00:36:24.140
There is like the level of understanding and this is back to your point right, we should have a really high level of clarity about our customers that we don't necessarily need when they're prospects.
00:36:25.211 --> 00:36:31.539
And traditionally that's been laid onto customer success managers, as has the health of the customer contact database and most companies.
00:36:31.539 --> 00:36:32.161
If you were to ask.
00:36:32.161 --> 00:36:33.833
Well, who's responsible for it?
00:36:33.833 --> 00:36:35.176
Oh, csms, they do that.
00:36:35.176 --> 00:36:40.757
Well, first of all, with the advent of digital customer success, companies have less CSMs.
00:36:40.757 --> 00:36:43.343
They focus on the top 10% of accounts.
00:36:43.430 --> 00:36:52.965
Everyone else is in a digital customer success mode and and you know the CSM yeah, they'll update the two people they talk to at an account on a regular basis.
00:36:52.965 --> 00:36:55.017
Oh, you have a new title, oh, you moved.
00:36:55.017 --> 00:36:56.060
I'll go in there and update.
00:36:56.060 --> 00:37:08.301
But those people in the buying groups that have been added, those seven or eight other people in the list who don't come to QBRs, they're not going in there and going to LinkedIn and say has something changed for that person?
00:37:08.301 --> 00:37:09.952
So they're only.
00:37:09.952 --> 00:37:19.179
You know, if you were to do a database health assessment of your main primary contact, that's probably in pretty good shape because the CSMs probably are updating them.
00:37:19.179 --> 00:37:26.817
But when you get to that, you know anybody outside the CSMs have that one-to-one relationship nobody's updating it because you know everybody thinks the CSMs do it.
00:37:26.836 --> 00:37:27.682
CSMs say we nobody's updating it.
00:37:27.682 --> 00:37:28.769
Because you know everybody thinks CSMs do it.
00:37:28.769 --> 00:37:30.176
Csms say we're not doing it.
00:37:30.176 --> 00:37:34.000
And then everyone says well, everyone's responsible for it.
00:37:34.000 --> 00:37:35.897
Well, whenever you hear everyone, it means nobody.
00:37:36.358 --> 00:37:38.894
Yeah, no, I totally.
00:37:38.894 --> 00:37:41.843
It's one of my pet peeves whenever I've been.
00:37:41.843 --> 00:37:42.893
It's like I want.
00:37:42.893 --> 00:37:47.591
I say this over and over Clarity about decision-making is a game-changer.
00:37:47.591 --> 00:38:00.379
If you don't have that and you think it's by committee, then there's no one's taking responsibility for the decision, and so it makes it easier for people to abdicate that responsibility.
00:38:00.379 --> 00:38:07.022
But even worse is decisions that get made, and even at the executive level who really?
00:38:07.383 --> 00:38:07.823
who really?
00:38:07.823 --> 00:38:08.864
Oh, is it the CMO?
00:38:08.864 --> 00:38:11.045
Who sort of is it under their purview?
00:38:11.045 --> 00:38:12.626
Is it the, you know?
00:38:12.626 --> 00:38:15.347
If they have a head of customer success, is it on their purview?
00:38:15.347 --> 00:38:16.928
Is it VP of sales?
00:38:16.928 --> 00:38:25.655
I mean, who actually, you know, sort of thinks about the health of their database?
00:38:25.655 --> 00:38:29.884
I was talking to a CFO friend of mine and I asked him, like you know, who's responsible for the update of the database?
00:38:29.884 --> 00:38:32.479
He goes well, at every handoff I expect to be updated.
00:38:32.479 --> 00:38:36.181
So when the salesperson first meets, you know gets updated.
00:38:36.181 --> 00:38:42.097
When the BDR gets updated, when they become a client, you know the onboarding person updates it.
00:38:42.097 --> 00:38:44.550
When it gets handed off to CSM, the CSM checks.
00:38:44.550 --> 00:38:49.160
It's like none of these people are doing that, you know, at each handoff is the problem.
00:38:50.323 --> 00:38:55.800
Yes, I mean we hadn't really hit on this, but so I'm going to throw this at you a little bit, because I don't think we talked about it before.
00:38:55.800 --> 00:39:12.546
It's like how do you, how would your like, how would you recommend to that CFO how to measure that database, health and quality, and then use that to then drive the way?
00:39:12.546 --> 00:39:15.980
I would think that's like here's how we're going to measure the quality of our customer database.
00:39:15.980 --> 00:39:34.848
And then all the people that we expect, whether it's tacit or not, to be a part of making sure that score or whatever metrics are going in the right direction, how are they then measured on their part of that Does?
00:39:34.868 --> 00:39:35.230
that make sense.
00:39:35.230 --> 00:39:49.324
Yeah, well, I think it was an open prize report that said that 71% of all companies do not have a data quality understanding, a definition of data quality.
00:39:49.324 --> 00:39:58.314
So I think, again, that might be something that group, that cross communications group, would do is, let's define what we mean by data quality and what are minimal acceptables, like we talked earlier.
00:39:58.314 --> 00:40:01.510
You know our key people that's got to be 95%.
00:40:01.510 --> 00:40:03.157
Our not so key 90.
00:40:03.157 --> 00:40:04.516
Our less key 80%.
00:40:04.516 --> 00:40:06.518
And what do we mean by that?
00:40:06.518 --> 00:40:07.893
You know, do we just mean the?
00:40:07.893 --> 00:40:14.358
We just mean the location, title, employer, or do we mean utilization?
00:40:14.358 --> 00:40:15.914
Well, we don't integrate.
00:40:15.914 --> 00:40:17.239
That isn't integrated.
00:40:17.310 --> 00:40:19.959
Well, okay, that should be on our roadmap for a year from now.
00:40:19.959 --> 00:40:24.382
We should be able to at least tie into the database health.
00:40:24.382 --> 00:40:32.983
When did they first become a user, when did they first get their username and password and when was the last time they logged in?
00:40:32.983 --> 00:40:43.160
From a segmentation perspective, that's really important, because if somebody became a user three years ago and they've never logged in, why do we keep on sending them emails like this one they're going to open up.
00:40:43.160 --> 00:40:56.304
That's how you get from the average email going out from 1,200 people to 800 people and, lo and behold, you clean up your database, your open rate is going to go up five to 10 percentage points immediately.
00:40:56.690 --> 00:40:59.940
Quicker than any AP testing quicker than any time of day.
00:40:59.940 --> 00:41:06.939
Cleaning up the database will improve someone's open rates and give you a much more honest appraisal of your open rates than anything else you could do.
00:41:07.159 --> 00:41:14.236
Yeah, I mean yeah, I think the fear that a lot of people aren't familiar with that is like, oh, we're going to miss someone.
00:41:14.236 --> 00:41:16.263
Or they're like do not hit it again.
00:41:16.263 --> 00:41:27.782
And I'm like but to your point, right, if that person's never opened something like, why do we hit our head against the wall and go well, this is a much better email, right?
00:41:27.782 --> 00:41:28.603
It's really not.
00:41:28.944 --> 00:41:29.565
They don't give a shit.
00:41:29.565 --> 00:41:35.839
Let's go back to your question we talked about earlier about doing a little, just a quick assessment.
00:41:35.839 --> 00:41:38.283
Have people go into LinkedIn, take 50 names each.
00:41:38.283 --> 00:41:41.277
In a week from now let's go back and report.
00:41:41.277 --> 00:41:44.538
I mean, there are data processors out there.
00:41:44.538 --> 00:41:48.620
Most of the data processors want one-year commitments and they'll do a little sample data processors out there.
00:41:48.620 --> 00:41:51.025
Most of the data processors want one-year commitments and they'll do a little sample.
00:41:51.025 --> 00:41:52.167
Yeah, we'll do 200 people sample for you.
00:41:52.187 --> 00:41:55.213
But I would argue, take whatever cross-section makes sense.
00:41:55.213 --> 00:42:00.292
You know you're 20% of your biggest accounts, all of the contacts in those accounts.
00:42:00.292 --> 00:42:02.784
Some will be that first level, second and third level.
00:42:02.784 --> 00:42:06.015
Let's go to a data processor who will do a one-off for me.
00:42:06.015 --> 00:42:07.378
Some of them will, most of them won't.
00:42:07.378 --> 00:42:09.963
I'm happy to coordinate that.
00:42:09.963 --> 00:42:15.817
And you know, let's give them 2,000 or 3,000 names and now we have some real data.
00:42:15.817 --> 00:42:18.598
So we have a sense from manually looking at that.
00:42:19.019 --> 00:42:21.857
Okay, it's not good, but what does that not good really mean?
00:42:21.857 --> 00:42:24.894
Now let's take a few thousand names spend.
00:42:24.894 --> 00:42:25.997
You know it's not a lot of money.
00:42:25.997 --> 00:42:28.843
I mean we're talking pennies per name, not dollars per name.
00:42:28.843 --> 00:42:30.374
To do a quick assessment.
00:42:30.374 --> 00:42:34.316
You know what's the person's first name, last name, company title.
00:42:34.316 --> 00:42:39.293
You'll get back a report and you'll be able to see drop into Excel and you know, you'll be able to see.
00:42:39.293 --> 00:42:40.937
Okay, you know.
00:42:40.937 --> 00:42:42.140
What patterns do we see?
00:42:42.140 --> 00:42:44.451
What are we doing poorly, what are we doing well?
00:42:44.451 --> 00:42:52.143
And now you can start defining data quality and also what are those minimum expectations that you know we should never fall below this.
00:42:52.583 --> 00:42:58.675
Yeah, yeah, there's a floor, so it's interesting, as you were describing that process.
00:42:58.675 --> 00:43:19.104
My initial thought, like defining the patterns would be seems like a good use case for an AI kind of tool, and we've talked a little bit about AI and some of the implications of some of this, but what do you see as some of the impacts of AI on this good, bad or indifferent on this kind of discipline?
00:43:20.045 --> 00:43:20.865
Well, I have a great quote.
00:43:20.865 --> 00:43:26.623
It's in the report State of B2B Customer Contact Databases from Ed King, the CEO of OpenPrize.
00:43:26.623 --> 00:43:41.842
The title of his article blog post was AI will expose your data quality issues and he says AI is likely the one technology that will expose data quality issues the most, which may help raise the awareness and urgency of dealing with your go-to-market data quality issues.
00:43:41.842 --> 00:43:45.921
Maybe this will finally make the executives care about and invest in data quality.
00:43:45.921 --> 00:43:49.857
So AI on its own isn't going to.
00:43:49.857 --> 00:43:54.438
I can't go into chat GPT and say, okay, here's my 10,000 customers.
00:43:54.438 --> 00:43:58.818
Tell me where do they live, what's their current title and where do they work.
00:43:58.818 --> 00:44:08.382
Linkedin isn't going to let that happen, so you need to go in there and once you have it, then you can start using AI to help with the segmentation.
00:44:08.382 --> 00:44:10.173
That's a huge use case, I think, for it.
00:44:10.173 --> 00:44:15.064
But that basic foundational do we have the data right?
00:44:15.064 --> 00:44:17.013
Ai is not going to help you.
00:44:17.013 --> 00:44:18.859
Interesting, okay, what?
00:44:18.899 --> 00:44:19.180
about-.
00:44:19.631 --> 00:44:42.318
It'll magnify the issues, because you're and AI will give you all sorts of Even when you scrape LinkedIn, you get all sorts of crazy false positives, like somebody just got you know they work for IBM and they just, you know, join the board directors of their local YMCA, and that's at the top of LinkedIn, and a new job is board directors YMCA.
00:44:42.318 --> 00:44:43.693
So you know.
00:44:43.693 --> 00:44:48.680
So AI has got to be smart enough to say okay, and some of the data processors are and some of them aren't.
00:44:48.680 --> 00:44:52.341
I mean, the data processors use AI and say no, no, no, that's a false, negative.
00:44:52.341 --> 00:44:59.944
Board directors of YMCA this is where they really are at, even though that's their second job on that title.
00:44:59.944 --> 00:45:06.343
So if you work with data processors, are they smart enough to use AI to be able to figure some of those things out?
00:45:06.590 --> 00:45:06.971
Gotcha.
00:45:06.971 --> 00:45:23.961
Yeah, it feels like there's a lot of opportunity to help around some of this stuff, but also it sounds like some of the impacts of AI have actually put pressure on the roles and jobs that would be focused on this too.
00:45:23.961 --> 00:45:28.186
Absolutely, yeah, okay, awesome.
00:45:28.186 --> 00:45:30.656
So, erwin, I think we're going to have to wrap it up here.
00:45:30.656 --> 00:45:35.341
This has been a fun and very educational conversation for me.
00:45:35.341 --> 00:45:52.744
I always enjoy these, even though what our listeners may not realize like I usually talk to these folks before we record and I'm always surprised that, like, oh, there's this thing that came up in this conversation that we actually recorded, which I'm always surprised that, like, oh, there's this thing that came up in this conversation that we actually recorded, which I'm grateful for, that didn't come up before.
00:45:52.744 --> 00:45:58.835
So I definitely had a few of those and this idea of having a cross-functional team that's focused on this area.
00:45:59.430 --> 00:46:03.156
Yeah, not so obvious, but a huge impact because it touches a lot of things.
00:46:03.216 --> 00:46:09.172
Yeah, yeah, if our listeners make it this far, to it.
00:46:09.172 --> 00:46:27.104
Right, just that alone, like taking that idea back to your organization, I think, and articulating why it would be beneficial for the enterprise in terms of the relative level of quality of our database is probably correlated to retention.
00:46:27.104 --> 00:46:30.786
Of quality of our database is probably correlated to retention.
00:46:30.806 --> 00:46:33.248
And you know Well, expansion, yeah, a lot of it impacts a lot of people, even legal.
00:46:33.248 --> 00:46:38.093
I mean compliance with email privacy regulations.
00:46:38.093 --> 00:46:40.919
If legal knew what was going on with locations, they would not be happy.
00:46:42.303 --> 00:46:43.451
Absolutely Well.
00:46:43.451 --> 00:46:44.696
Hey, Erwin, thank you so much.
00:46:44.696 --> 00:46:51.724
So we can certainly put a link to the report, if there's one, in the show notes when we publish that.
00:46:51.724 --> 00:46:55.878
But if folks want to learn more, maybe talk with you.
00:46:55.878 --> 00:46:57.461
What's the best way for them to do that?
00:46:57.501 --> 00:46:58.504
Yeah, connect with me on LinkedIn.
00:46:58.504 --> 00:47:02.021
I am the only Erwin Hipsman on the planet, so I'm easy to find.
00:47:02.021 --> 00:47:07.657
And if you want to, my parents knew about branding way before anyone else.
00:47:07.657 --> 00:47:20.659
And if you want to get your own customer health score, if you download the report there are links to do it yourself, so go in there and you can generate your own score by answering the same questions that everyone else asks Fantastic, it's anonymous, so it's not a lead generation tool.
00:47:20.659 --> 00:47:23.698
You can just go in there and do your own health score.
00:47:24.039 --> 00:47:24.340
Love it.
00:47:24.340 --> 00:47:25.411
Love it, erwin.
00:47:25.411 --> 00:47:25.994
Thank you again.
00:47:25.994 --> 00:47:34.331
So much, great conversation.
00:47:34.331 --> 00:47:36.153
I'm sure our audience is going to be the beneficiaries of that.
00:47:36.153 --> 00:47:37.537
Thanks to our audience for their ongoing support and ideas.
00:47:37.537 --> 00:47:47.003
As always, if you want to be a guest, have an idea for a guest or a topic, feel free to reach out to Naomi, mike or me and we'd be happy to get the ball rolling on that Until next time.
00:47:47.003 --> 00:47:47.484
Bye, everybody.