TRANSCRIPCIÓN 🔗
WEBVTT
1
00:00:00.040 --> 00:00:03.480
I've been in the throes and I
know exactly what they're experiencing and when you
2
00:00:03.520 --> 00:00:07.750
can certainly walk in and have that
level of expertise or subject matter expertise with
3
00:00:07.870 --> 00:00:15.189
the customer, they'll say you get
it now, help me. ECOSYSTEM ACES
4
00:00:15.349 --> 00:00:20.309
is a podcast dedicated to helping business
leaders unleash the full potential of the ecosystem
5
00:00:20.309 --> 00:00:25.339
economy. Whether you're just getting started
with ecosystem partners or you're looking for advanced
6
00:00:25.379 --> 00:00:29.739
strategies and tactics, this podcast is
for you. Let's get into the show.
7
00:00:34.460 --> 00:00:39.210
Welcome back to another episode of ecosystem
ass I'm chip rodgers, CMO at
8
00:00:39.329 --> 00:00:43.090
works fan, excited to be joined
by Chris Cochran. Chris, welcome,
9
00:00:43.369 --> 00:00:46.409
Hey chip, how are you today? Good, good, doing, doing
10
00:00:46.490 --> 00:00:49.130
well, and this is this is
going to be fun. We've got some
11
00:00:49.450 --> 00:00:53.719
interesting things to talk about. I
understand we have you guys have a little
12
00:00:53.719 --> 00:00:57.159
bit of an announcement to is,
you know, going to be exciting,
13
00:00:57.240 --> 00:01:00.359
and so I'm just really thrilled to
have Chris with us. Chris has EP
14
00:01:00.520 --> 00:01:04.750
of Clouds Strategy and alliances at data
dynamics and you guys are doing some really
15
00:01:04.790 --> 00:01:10.349
interesting things. I mean Christ you
have a long history at Gosh net APP
16
00:01:10.430 --> 00:01:14.109
for many years, oracle and q
logic going back, and we have some
17
00:01:14.189 --> 00:01:18.390
mutual friends from some of those organizations. But now you know, data dynamics
18
00:01:18.549 --> 00:01:23.180
just really aggressive and fast growing startup. You're based in Dallas. First of
19
00:01:23.219 --> 00:01:26.579
all, welcome and tell uschool about
what what you and your team are up
20
00:01:26.620 --> 00:01:30.180
to. It did a dynam yeah, you bet, chip, and it's
21
00:01:30.180 --> 00:01:33.569
great to be here. Thanks for
the invitation to join everybody in yourself to
22
00:01:33.650 --> 00:01:36.090
do these podcasts. There are a
lot of fun right. We do have
23
00:01:36.129 --> 00:01:38.969
a significant announcement. I want to
dive into that in just a moment,
24
00:01:38.010 --> 00:01:42.129
but let me tell you about data
dynamics to begin with. So we close
25
00:01:42.209 --> 00:01:47.480
last year with well over fifty percent
growth year over year. So that tells
26
00:01:47.519 --> 00:01:51.079
you the trajectories in the right direction. But what do we do right?
27
00:01:51.480 --> 00:01:57.120
We've built a platform that stems around
customers, unstructured data, that's built on
28
00:01:57.920 --> 00:02:01.590
the auspice of analytics and data rationalization
and that takes on different meanings for every
29
00:02:01.629 --> 00:02:06.469
customer. The most unique part about
this, and we're and we're finding,
30
00:02:06.670 --> 00:02:09.909
is your strategy and my strategies are
completely different and our tool comes right in
31
00:02:09.949 --> 00:02:15.419
the middle and allows you to now
begin to apply your data strategy schemes to
32
00:02:15.699 --> 00:02:20.580
that unstructured data environment. And that's
the uniqueness to it and people can't get
33
00:02:20.580 --> 00:02:23.180
enough of it because most of the
times, you know, we're looking at
34
00:02:23.219 --> 00:02:25.060
Hey, I've got a tool and
it can do it like this. I
35
00:02:25.219 --> 00:02:30.650
have my tagging and Metadata, analytics
and things, but it doesn't necessarily follow
36
00:02:30.650 --> 00:02:32.689
the way I want to do it, and that's been the unique value add
37
00:02:32.729 --> 00:02:38.969
that customers are really enjoying about our
tool built around storage x inside analytics and
38
00:02:38.090 --> 00:02:43.169
control legs, and those are the
platform modules that we at data dynamics have
39
00:02:43.610 --> 00:02:46.960
put into the market. Most recently, chip, I do want to say
40
00:02:46.000 --> 00:02:53.400
that we established a beachhead relationship with
Microsoft and that relationship we we're bringing these
41
00:02:53.560 --> 00:02:58.909
offerings not only in your traditional Var
community supper boarded but also through the Microsoft
42
00:02:59.069 --> 00:03:01.629
market place, which has been really
unique and also, I'd say, it's
43
00:03:01.669 --> 00:03:07.349
been widely well well received. We've
done a whole host of transactions through that
44
00:03:07.509 --> 00:03:12.830
media and the customers love it because
there's very unique nuances when you're a Microsoft
45
00:03:12.979 --> 00:03:17.900
customers inside your enterprise agreement that they
make with Microsoft that allows them to churn
46
00:03:17.979 --> 00:03:23.020
down and we're one of those tools
or products in that category that allows us
47
00:03:23.060 --> 00:03:28.289
to turn down their Microsoft as your
commits to consume. So a lot going
48
00:03:28.370 --> 00:03:32.409
on over here. That's exciting and, Gosh, fifty percent growth is phenomenal.
49
00:03:32.449 --> 00:03:35.930
Yeah, thank you very much.
It was a year that was was
50
00:03:36.490 --> 00:03:40.169
well orchestrated and the execution was the
key to getting to the milestones that we
51
00:03:40.289 --> 00:03:46.479
wanted to achieve as an organization.
So your and your role is really specific.
52
00:03:46.639 --> 00:03:52.479
We were talking about this earlier,
that it's very specific to the hyperscalers.
53
00:03:52.879 --> 00:03:55.150
And tell me about that. How
do you you know? You're a
54
00:03:55.310 --> 00:03:58.469
you're a start up, right.
I mean, first of all, tell
55
00:03:58.469 --> 00:04:01.349
us a little bit about what that
those
Load full transcript
relationships are. Yeah, but then
56
00:04:01.389 --> 00:04:05.189
also love to dive into things like
how do you get it their attention?
57
00:04:05.430 --> 00:04:10.300
And Yeah, those are the hard
questions. Yeah, yeah, the good
58
00:04:10.340 --> 00:04:13.860
ones. Well, let me tell
you about the hyperscale relationships and then let's
59
00:04:13.900 --> 00:04:15.420
dive into you know, how do
you really get their attention? Right?
60
00:04:15.779 --> 00:04:20.459
So what we've done is built out
those relationships with the major hyperscalers. Microsoft
61
00:04:20.579 --> 00:04:25.850
is our paramount or the cornerstone relationship
that we have in place to day and
62
00:04:25.930 --> 00:04:30.089
obviously aws and GCP are quickly on
the heels of that. We had pre
63
00:04:30.209 --> 00:04:34.089
existing relationships and and like any good
relationship, it always starts off somewhere,
64
00:04:34.209 --> 00:04:39.920
somehow there's a bumpy road, and
that's how this started. So so let's
65
00:04:39.920 --> 00:04:43.639
just say when when you kind of
have a low expectation and you come in
66
00:04:43.839 --> 00:04:47.000
well above it, you really gained
some respect and notoriety there. But that's
67
00:04:47.040 --> 00:04:50.839
how this began. Right. We
had a problem situation and we came in,
68
00:04:51.000 --> 00:04:55.029
we solved a big problem and that
problem, number one, had financial
69
00:04:55.110 --> 00:04:59.709
penalties and number two, a large
capacity of data of set inside of a
70
00:04:59.790 --> 00:05:02.550
customers data center here in Texas,
as a matter of fact, that needed
71
00:05:02.589 --> 00:05:08.100
to be evacuated into one of the
hyperscalers. And not only you know the
72
00:05:08.180 --> 00:05:12.180
large capacity, but you know we
had fractional use of pipes and you know
73
00:05:12.540 --> 00:05:15.540
can kind activity into the data center. So you know, any type of
74
00:05:15.379 --> 00:05:18.699
I guess you could say prohibitive factor. We had to kind of gate our
75
00:05:18.740 --> 00:05:24.170
way through those. But we workshop
the process, we work very deliberately with
76
00:05:24.250 --> 00:05:27.610
the customer and, like any good
engagement, right, we were very,
77
00:05:27.689 --> 00:05:30.889
very committed to the success of that
program not only from a timeframe perspective,
78
00:05:30.930 --> 00:05:36.079
but also to alleviate some monetary commitments
that they had that were imposed upon them,
79
00:05:36.199 --> 00:05:39.519
and we stepped up to the plate
and hit it out of the park.
80
00:05:39.800 --> 00:05:42.319
Wow. So that was the beginning
of the company. Well, the
81
00:05:42.439 --> 00:05:46.959
company now is just surpassed its ten
year old mark. This goes back about
82
00:05:46.000 --> 00:05:49.750
two, two and a half years
ago, and we've continually, gradually worked
83
00:05:49.790 --> 00:05:55.230
with this customer and it's an evolving
relationship, right, because they we started
84
00:05:55.589 --> 00:06:00.589
in one beachhead and they've expanded us
out to their data strategy platform across the
85
00:06:00.829 --> 00:06:04.180
entire organization. Let's usually how most
organizations would engage. Say Hey, I've
86
00:06:04.220 --> 00:06:08.579
got a problem to solve and but
I want to do something more right,
87
00:06:08.699 --> 00:06:12.459
and we start exploring those conversations.
You know, the arts of the possible
88
00:06:12.500 --> 00:06:15.500
are always something that you can bring
in those conversations, and that's how that
89
00:06:15.660 --> 00:06:19.529
literally began. Let's solve this one
baseline problem and then let's start looking at
90
00:06:19.610 --> 00:06:24.290
the data strategy. Not only to
that effect, but let me share you
91
00:06:24.449 --> 00:06:28.009
some statistics. That was an outtake
of the process that we had right,
92
00:06:28.329 --> 00:06:31.569
and this is what really gets the
attention of people at the Microsoft's and the
93
00:06:31.610 --> 00:06:35.519
AWS is and the GCP. We
took what was going to be about six
94
00:06:35.720 --> 00:06:41.319
man years to get done and we
did this in less than six months,
95
00:06:41.800 --> 00:06:45.759
and that was unheard of. Number
One. Number two, we took what
96
00:06:46.000 --> 00:06:49.670
was what was. There was a
team of roughly twelve individuals that were inside
97
00:06:49.670 --> 00:06:57.069
the organization. Those twelve individuals,
we literally brought it down to two individuals.
98
00:06:57.149 --> 00:07:00.709
That helped to scope the work and
do the execution, and that was
99
00:07:00.790 --> 00:07:05.500
a byproduct of US having a very
policy based engine inside of our technology,
100
00:07:05.579 --> 00:07:11.139
number one, and secondarily the fact
that we were able to do this in
101
00:07:11.259 --> 00:07:15.180
an automated fashion. So once you
create it, let's just recreate the wheel,
102
00:07:15.420 --> 00:07:18.689
right, and that helped to alleviate
the number of manpower that was going
103
00:07:18.689 --> 00:07:23.129
to be required initially that was scoped
to do the project deck. So that
104
00:07:23.329 --> 00:07:27.250
was some big factors. So that, along with a financial savings, when
105
00:07:27.250 --> 00:07:31.120
we identified the property use of storage
for the customer, we looked at their
106
00:07:31.199 --> 00:07:34.639
data sets and we found that there
were three categorical groups that we put the
107
00:07:34.720 --> 00:07:38.600
data into. We found that there
was redundant data. And let me just
108
00:07:38.639 --> 00:07:43.399
share an example. How many powerpoint
versions do you have of the same powerpoint?
109
00:07:43.560 --> 00:07:46.550
I asked myself that question one time
when I went back and on average
110
00:07:46.550 --> 00:07:49.709
I have twelve versions. Just imagine
that, you know, across thousands of
111
00:07:49.750 -->
00:07:54.750
employees across an organization, you start
to see that that redundant data in the
112
00:07:54.829 --> 00:07:59.540
first category becomes proliferic. Right.
Number two is obsolete data, and I
113
00:07:59.579 --> 00:08:01.459
had the best example I can use
as I worked for net at, what
114
00:08:01.699 --> 00:08:05.420
one of the greatest organizations on the
fatas face of this planet, and they
115
00:08:05.500 --> 00:08:07.540
was. They've been recognized, you
know, as one of the the best
116
00:08:07.579 --> 00:08:11.300
organizations. But when I left there, remember all of that data that I
117
00:08:11.379 --> 00:08:16.089
had created while I was at that
organization is still there and it must be
118
00:08:16.170 --> 00:08:20.810
maintained based on the regulatory compliancies that
they have. So that's obsolete data.
119
00:08:20.050 --> 00:08:24.529
And the third is the trivial data. So the only example I can tell
120
00:08:24.529 --> 00:08:28.199
you, and I don't want to
incriminate any anybody on this one, but
121
00:08:28.759 --> 00:08:33.000
we had a gentleman that was working
in this organization that had about a petabyte
122
00:08:33.080 --> 00:08:35.919
of capacity and we just couldn't make
sense of how much data that was.
123
00:08:37.559 --> 00:08:41.120
But they were dot txt files and
we thought, Gosh, this is very
124
00:08:41.159 --> 00:08:46.669
unusual, until we started analyzing the
data. We found that the naming conventions
125
00:08:46.870 --> 00:08:50.909
often equaled movies, so you could
download these to your IPAD, you know,
126
00:08:52.070 --> 00:08:54.190
put them on there and then change
them to dot mov files and you're
127
00:08:54.269 --> 00:08:58.700
often running watching a movie on a
for our flight across the country. So
128
00:08:58.820 --> 00:09:01.019
we find a lot of that kind
of thing happening inside the organizations. But
129
00:09:01.059 --> 00:09:05.820
a pedopyte a storage is very,
very expensive when you start looking at it.
130
00:09:05.299 --> 00:09:09.820
So that was another example of redundant, obviously, and trivial data that
131
00:09:09.899 --> 00:09:13.929
we found inside the estate. That
helped the customer to rationalize the data set
132
00:09:13.009 --> 00:09:16.409
as they moved it into the hyperscalers
and then they put it into the proper
133
00:09:16.570 --> 00:09:22.490
affordable tier based on their performance requirements. Interesting. So you're you're really helping
134
00:09:22.690 --> 00:09:28.200
to and that's that's the how you're
packaging for your customers with the hyper so
135
00:09:28.399 --> 00:09:35.480
what's the what's the what is the
relationship with the your relationship with the hyperscalers,
136
00:09:35.519 --> 00:09:39.070
and how are you working with customers
in together? What's the what's in
137
00:09:39.269 --> 00:09:45.509
what's the sort of the balanced scorecard
relationship between them and hyperscalers? Yeah,
138
00:09:45.590 --> 00:09:50.350
so, so what we're finding is
we've established a contractual agreement with Microsoft right
139
00:09:50.429 --> 00:09:54.500
to do these types of events for
them and that was just recently announced.
140
00:09:54.700 --> 00:09:58.379
Will have a big press release that
will be issued by Microsoft on February the
141
00:09:58.460 --> 00:10:01.500
seventh, and this is really going
to put us in a position where we're
142
00:10:01.500 --> 00:10:05.940
going to continue to help their customers
and we're moving their customer data right at
143
00:10:07.139 --> 00:10:11.929
no charge for the data dynamics storage
x license. Our engine is now going
144
00:10:13.009 --> 00:10:16.450
to be at no charge to those
customers. So it's a one way straight
145
00:10:16.490 --> 00:10:20.889
end, right. We want to
move data for that customer into the Azure
146
00:10:20.970 --> 00:10:24.799
storage platform, such as as your
files, as your net at files,
147
00:10:24.120 --> 00:10:28.720
and then also into as your blob
storage. So those are some of the
148
00:10:28.840 --> 00:10:33.519
largest portfolios of storage that as your
offers. So that enables the field selling
149
00:10:33.600 --> 00:10:39.309
organization at Microsoft to help grow their
install base with their customer and then also
150
00:10:39.470 --> 00:10:43.029
accelerates that customers adoption of cloud.
Everybody's got the cloud strategy today, as
151
00:10:43.070 --> 00:10:48.350
we all know. Right. It's
just your finding that every time that somebody
152
00:10:48.350 --> 00:10:52.700
starts down the path of doing migration, it's like a science project. So
153
00:10:52.860 --> 00:10:54.700
I often refer back to when I
was a eighth grade kid. I walked
154
00:10:54.740 --> 00:10:58.980
into science class and our professor said
here, here, kid here's your science
155
00:11:00.019 --> 00:11:03.259
kit. Figure it out right.
So these are the same way, because
156
00:11:03.259 --> 00:11:05.970
you've had a customer that's had,
you know, twenty five to thirty years
157
00:11:07.009 --> 00:11:11.330
of experience of building an on premise
state and we're trying to extract that data
158
00:11:11.409 --> 00:11:16.850
in a very contained manner and move
it into the cloud and make it usable
159
00:11:16.129 --> 00:11:20.000
right pose. It's compliance usable,
so they can shift that data into the
160
00:11:20.080 --> 00:11:24.679
cloud. But the file data movements
kind of easy part, but all of
161
00:11:24.759 --> 00:11:28.639
the permission and attributes to the file
or the important ingredient that we need to
162
00:11:28.799 --> 00:11:35.029
move with the file so that way, once you mount it into a hyperscalar
163
00:11:35.110 --> 00:11:39.149
to your vm's or in that environment, you'll notice that that data is accessible.
164
00:11:39.230 --> 00:11:43.669
It has all the permissions and the
things that you know a hip you
165
00:11:43.789 --> 00:11:46.190
you need to access your file data. You know, we want to make
166
00:11:46.230 --> 00:11:50.179
sure that there's there's no gating factor
between you getting to your data and getting
167
00:11:50.179 --> 00:11:52.700
your job done and everyone else inside
the organization. And that's what we do
168
00:11:52.820 --> 00:11:58.139
and we handle that very, very
well. So the advantage obviously for you
169
00:11:58.379 --> 00:12:03.009
as you have customers and and help
them with their with their data. The
170
00:12:03.009 --> 00:12:09.169
value to the customers? What's the
value to the hyperscaler. Then there they
171
00:12:09.649 --> 00:12:11.690
well, you said the behavior is
that you see more adoption. Yeah,
172
00:12:11.690 --> 00:12:16.000
you really do. And chip.
That's a that's probably the paramount question to
173
00:12:16.080 --> 00:12:16.919
it all. You know what?
What do they see? Is that the
174
00:12:18.200 --> 00:12:22.960
return value from from data dynamics to
Microsoft and ATOPS OR GCP? Their goal
175
00:12:24.279 --> 00:12:26.639
is to grow and you know there's
a mass, you know, fierce fight
176
00:12:26.759 --> 00:12:31.870
out here in the street between the
largest hyperscalers, you know, aws and
177
00:12:31.110 --> 00:12:35.350
Microsoft and GCP, and they're all
allowing for that customer data right. And
178
00:12:35.629 --> 00:12:39.309
what we found is the means and
the mechanisms to be that engine right.
179
00:12:39.429 --> 00:12:45.019
We're able to encapsulate the data that's
on the customers a state and move it
180
00:12:45.179 --> 00:12:48.340
in a very expedient manner with a
lot of the restrictions that you know,
181
00:12:48.539 --> 00:12:54.460
complicated environments, networking, firewalling on, all of those those complications that a
182
00:12:54.580 --> 00:12:58.529
state has, and get it moved
into that hyperscaler of choice for the customer.
183
00:12:58.970 --> 00:13:03.169
And that has proven time and time
again to be complicated states. But
184
00:13:03.289 --> 00:13:09.730
our utility are storage x platform allows
the customer to do it because we've got
185
00:13:09.009 --> 00:13:15.879
years and years of experience that have
been built into the technology from the underpinning
186
00:13:16.120 --> 00:13:20.480
respective to recognize, you know,
the different file and unique file types that
187
00:13:20.559 --> 00:13:24.200
you'll have, the different firewalling capabilities
and then the ports and different things like
188
00:13:24.279 --> 00:13:28.629
that. So so we've learned through
the years and built that technology and it's
189
00:13:28.669 --> 00:13:33.070
continue to evolve to the point where
now it's being recognized as one of the
190
00:13:33.149 --> 00:13:37.350
paramount tools in the industry for the
migrations. Yeah, so is this?
191
00:13:37.470 --> 00:13:41.070
Are these the announcement that you have
coming up? I think I'm always interested
192
00:13:41.149 -->
00:13:43.580
in sort of, you know,
partners working together to, you know,
193
00:13:43.740 --> 00:13:48.100
create joint solutions and Gush, you
know. Coming from net APP, you
194
00:13:48.179 --> 00:13:50.820
know flex pod is, I think, one of those sort of industry iconic,
195
00:13:52.059 --> 00:13:54.580
you know, solutions like that,
and I know, I think you,
196
00:13:54.019 --> 00:13:56.850
I remember talking. You were involved
in that, the roll out of
197
00:13:56.889 --> 00:14:01.889
Flex Pot and clash is we have
a huge adoption of flex pot. Boy.
198
00:14:03.009 --> 00:14:05.850
You just can couldn't go back in
touch on such a foundational product in
199
00:14:05.889 --> 00:14:09.320
the industry, right, net APP
service that from a storage perspective with our
200
00:14:09.360 --> 00:14:13.480
Cisco relationship. Yeah, so what
I mean, how do you see that
201
00:14:13.799 --> 00:14:18.279
or what it let's talk a little
bit about about that sort of bringing organizations
202
00:14:18.399 --> 00:14:24.070
together and and now with data dynamics
and this announcement with Microsoft and, of
203
00:14:24.149 --> 00:14:28.669
course, with the Dibs and GCP. How do those come about? How
204
00:14:28.750 --> 00:14:31.509
have you seen come about and how
do you how are you? How do
205
00:14:31.549 --> 00:14:35.750
you bring it to market and a
sort of enable everybody, get everybody aligned
206
00:14:35.789 --> 00:14:39.379
around those new announcements? Yeah,
exactly. So let's go back to the
207
00:14:39.419 --> 00:14:43.659
origination, right. The relationship began
with guys and gals that we've worked with
208
00:14:43.899 --> 00:14:48.220
historically and within the industry, and
you know, there's consistent movement left and
209
00:14:48.299 --> 00:14:52.570
right. Microsoft is by far one
of the one of the largest protigious organizations,
210
00:14:52.649 --> 00:14:56.330
you know, with along with a
WS and and GCP. We had
211
00:14:56.490 --> 00:15:01.330
known and worked with Microsoft, you
know, because we had joint customers.
212
00:15:01.649 --> 00:15:07.679
Where the engagement began was just originally
around some conversations of capabilities, right,
213
00:15:07.120 --> 00:15:11.080
which led to hey, this this
needs to be explored a little bit more
214
00:15:11.559 --> 00:15:16.440
deeply because it's not only one customer, it's an industry sector, right,
215
00:15:16.559 --> 00:15:18.919
and we saw that in the oil
and gas sector, large capacity of data
216
00:15:18.960 --> 00:15:24.309
being moved into into aws and also
into Azure. But we also began to
217
00:15:24.350 --> 00:15:30.070
see the financial services sector, the
healthcare, life sciences, the manufacturing,
218
00:15:30.190 --> 00:15:33.629
retail, consumer goods. They all
began to mimic one another. They have
219
00:15:33.750 --> 00:15:37.179
a cloud strategy, but they,
you know, kind of the last part
220
00:15:37.179 --> 00:15:39.460
of that
was, hey, I'm
going to move all this unstructured data into
221
00:15:39.500 --> 00:15:43.139
the cloud. Right, it was
kind of a last thought. Well,
222
00:15:43.179 --> 00:15:46.419
we brought it to the forefront and
said, hey, let's start talking about
223
00:15:46.460 --> 00:15:50.490
this now. Where are you in
your cloud journey? Who's your hyperscaler of
224
00:15:50.529 --> 00:15:54.129
choice? Right, and then we
can begin to help you analyze and rationalize
225
00:15:54.169 --> 00:15:58.610
the data. So what we did
was we actually reverse the order, literally
226
00:15:58.649 --> 00:16:03.289
reverse the order of the data movement. Most people say, let's just get
227
00:16:03.289 --> 00:16:07.080
it lifted and shifted, as the
term lifted and ship into the cloud.
228
00:16:07.519 --> 00:16:11.000
We said, makes sense and we'll
help you all day long. But what
229
00:16:11.240 --> 00:16:17.159
if we could take a different approach
and let's analyze the data that's on Prim
230
00:16:17.440 --> 00:16:21.230
today and let's build a construct of
what that data is made up of the
231
00:16:21.350 --> 00:16:25.909
redundant, obviously and trivial data sets, and then let's take it one step
232
00:16:25.990 --> 00:16:30.629
further and then let's build the platforms
inside of an Azure or an aws or
233
00:16:30.750 --> 00:16:37.419
GCP and then move that data correctly, because it'll put it in the performance
234
00:16:37.460 --> 00:16:41.179
tire and the price tire that you're
expecting. What we found, and this
235
00:16:41.379 --> 00:16:44.740
is just a byproduct of not not
maybe necessarily knowing, and I think the
236
00:16:44.899 --> 00:16:48.690
industry wide everyone learned when we would
do the lift and shift models. Most
237
00:16:48.730 --> 00:16:52.610
customers would come back and go,
holy count this is expensive. You know
238
00:16:52.730 --> 00:16:56.009
this. This cloud journey is now
become expensive. And what we did was
239
00:16:56.090 --> 00:16:59.970
we took that to heart because we
heard that several instances and said let's make
240
00:17:00.009 --> 00:17:03.279
sense of this, let's rationalize the
data on set and we'll use our analytics
241
00:17:03.359 --> 00:17:08.319
tool to bring those data sets into
the forefront. Then we can make very
242
00:17:08.440 --> 00:17:14.240
intelligent based decisions as the data then
has moved into the proper steer, the
243
00:17:14.400 --> 00:17:18.990
proper tiers of storage inside of the
Azure Platform. So that's worked out really
244
00:17:18.069 --> 00:17:22.670
well. The customers have really loved
that type of process. But, like
245
00:17:22.789 --> 00:17:25.349
I said, we just reversed it
from what we were doing the lift the
246
00:17:25.430 --> 00:17:29.710
shift and then we've now rationalized and
helped customers to move it effectively into the
247
00:17:29.789 --> 00:17:33.339
proper tiers of storage inside of Agure. Sow a little bit of a change
248
00:17:33.380 --> 00:17:37.539
in methodology, but I would say
the results have certainly said Hey, this
249
00:17:37.579 --> 00:17:41.660
is the right way to go.
Do this? Yeah, so for of
250
00:17:41.980 --> 00:17:48.170
hardening standpoint. How how? How
are you working with your counterparts at Microsoft
251
00:17:48.329 --> 00:17:52.609
and each of the hyper scalers?
What's The in your role? What is
252
00:17:52.650 --> 00:17:56.529
your daytoday? Yeah, so,
good question. On the Daytoday, activities.
253
00:17:56.809 --> 00:17:59.319
So number one, right, I
get up early. I got to
254
00:17:59.400 --> 00:18:02.119
get the dog outget and walk then
and, you know, get all those
255
00:18:02.240 --> 00:18:06.160
those family commitments done. Right,
and and that's usually starts around thirty in
256
00:18:06.200 --> 00:18:08.079
the morning. We start with a
team call. I've got a team of
257
00:18:08.200 --> 00:18:12.309
a business development representatives and a customer
success team and other teams, and what
258
00:18:12.470 --> 00:18:15.150
we do is we align, you
know, for our kind of our week.
259
00:18:15.190 --> 00:18:18.269
We're going to work in and things
like that. But the engagement with
260
00:18:18.430 --> 00:18:23.549
Microsoft has been we engage across multiple
business units across that organization. And let
261
00:18:23.589 --> 00:18:26.180
me just share a couple of examples. We have a product team that we're
262
00:18:26.180 --> 00:18:30.180
working very, very closely with.
You know, the product we have today
263
00:18:30.220 --> 00:18:33.099
will not be the product of tomorrow. Right, we are going to continue
264
00:18:33.140 --> 00:18:36.740
to invest and advance that. Our
CEO, pay USHMATA, has said,
265
00:18:36.740 --> 00:18:41.220
Hey, this platform is going to
service the industries, and he means it.
266
00:18:41.690 --> 00:18:44.569
And and I'll tell you what he
has backed it up one hundred percent
267
00:18:44.609 --> 00:18:48.210
and we couldn't be happier to see
that because each time we've had or encountered
268
00:18:48.369 --> 00:18:52.730
feature request, we've put together our
business case and use case examples and we've
269
00:18:52.769 --> 00:18:56.359
brought them forward in the businesses,
looking at them and evaluating. That keeps
270
00:18:56.400 --> 00:19:00.000
the product fresh, right, and
the technology will always continue to change.
271
00:19:00.039 --> 00:19:04.359
The number one we're gladly investing on
that and our product teams were working to
272
00:19:04.440 --> 00:19:08.079
share that information. Now we also
engage with the field selling teams. Right.
273
00:19:08.240 --> 00:19:11.589
So if you looked at the organization
within Microsoft, I'll just give you
274
00:19:11.630 --> 00:19:15.710
some example. There's the regulated industries, which is financial services, healthcare,
275
00:19:15.829 --> 00:19:19.470
retail, consumer goods and manufacturing,
and then the
state and local government entities.
276
00:19:19.869 --> 00:19:23.819
We work in a line into those
regulated industries and we're helping them to
277
00:19:23.900 --> 00:19:30.779
sell the features and capabilities of data
and analysis and that analytics and also for
278
00:19:30.980 --> 00:19:37.660
compliance. And then finally, the
migration our recent announcement benefits the sellers because
279
00:19:37.900 --> 00:19:44.049
we're helping them to grow their internal
term of Azure consumption revenue or annual consumption
280
00:19:44.130 --> 00:19:48.009
revenue, and we're doing that for
a customer. The big benefit here is
281
00:19:48.089 --> 00:19:52.480
the customer has no charge for the
migration licenses and that's a huge benefit for
282
00:19:52.559 --> 00:19:56.880
those customers because oftentimes, like we've
said, we're kind of built the last
283
00:19:57.000 --> 00:20:00.680
thought. Okay, let's move the
data. How we going to move the
284
00:20:00.759 --> 00:20:03.759
data? We're solving that problem saying
well, we're going to move the data
285
00:20:03.759 --> 00:20:04.960
in a very effective manner and,
oh, by the way, there's no
286
00:20:06.160 --> 00:20:10.470
cost to you. So a huge
benefit from the seller's perspective. At Microsoft,
287
00:20:10.509 --> 00:20:11.869
they look at us as kind of
a I think there was a term
288
00:20:11.950 --> 00:20:17.910
shared this morning is deal acceleration and
sweetening the deal because there's no cost,
289
00:20:19.309 --> 00:20:23.660
which is unheard of. Right.
Yeah, that's that's fantastic. So that's
290
00:20:23.740 --> 00:20:27.460
something. I think that's a credit. So we're going with the product teams
291
00:20:27.460 --> 00:20:30.539
to define the product and get it, you know, really lined up with
292
00:20:30.740 --> 00:20:37.049
the needs for as your customers,
right, for hyperscalar customers, and then
293
00:20:37.809 --> 00:20:45.930
getting your pricing and measurements lined up
with the with this the the field sellers.
294
00:20:45.329 --> 00:20:49.960
Yeah, that's exactly what function for
the customers can acquire the technology through
295
00:20:51.160 --> 00:20:55.480
the azure market place and there's no
cost for the storage x license for the
296
00:20:55.799 --> 00:21:00.920
migration engine. But above and beyond
that they can take advantage of the insight
297
00:21:00.039 --> 00:21:04.309
analytics, which reads into the files
and the constructs and gives them data rationalization
298
00:21:04.470 --> 00:21:07.910
information. And then, if they
want to take further steps of compliance,
299
00:21:07.990 --> 00:21:11.390
we have our control x technology,
which is in the platform that can be
300
00:21:11.589 --> 00:21:15.789
procured and bought by the customer in
the Azure market place. So both of
301
00:21:15.829 --> 00:21:21.539
those additional products do have a fee
and the customers enjoy them and they can
302
00:21:21.740 --> 00:21:25.059
purchase them through the azure market place. And then again, the storage x
303
00:21:25.299 --> 00:21:29.660
engine, the migration engines, comes
to them at no cost. So how
304
00:21:29.819 --> 00:21:33.930
where is how are you getting paid? Well, that's the secret sauce.
305
00:21:33.369 --> 00:21:37.410
That's awesome. Yeah, it's an
agreement that we put in place and yeah,
306
00:21:37.450 --> 00:21:41.849
it's well represented it. You know, like I said, there there's
307
00:21:41.849 --> 00:21:45.130
a fist fight in the street right
now with the hyperscalers and you know,
308
00:21:45.369 --> 00:21:52.480
to move one percent in that industry
is a significant capacity compute or capacity of
309
00:21:52.599 --> 00:21:56.559
storage, and you know we're helping
facilitate one of the world's largest hyperscalers out
310
00:21:56.559 --> 00:22:00.519
there to help that. You know, accelerated growth. If you go back
311
00:22:00.559 --> 00:22:03.150
and look at just the earnings,
just just yesterday of Microsoft's earnings, Oh
312
00:22:03.230 --> 00:22:07.789
my word, I mean phenomenal results
and we're glad to be participating in that
313
00:22:07.910 --> 00:22:11.109
and helping them and we see,
you know, that over the next five
314
00:22:11.230 --> 00:22:15.180
years the durations not stopping or slowing
down at all. Chip, I got
315
00:22:15.299 --> 00:22:18.420
to tell you, I think the
hyperscalar, each one of the hyperscalers,
316
00:22:18.460 --> 00:22:25.140
are posting at least high double digit
growth numbers and and then have out quarter
317
00:22:25.259 --> 00:22:29.500
expectations for high double digit corter growths
as well. It's fascinating to watch.
318
00:22:29.900 --> 00:22:33.049
That's amazing. Well, I love
that story because it's and I think that's
319
00:22:33.049 --> 00:22:37.890
one of the challenges in partnering is
is Lining Up. And really you're doing
320
00:22:37.009 --> 00:22:44.250
you've done a great job understanding the
comp structures and the incentives in the motivations
321
00:22:44.359 --> 00:22:51.240
for your partners field teams right and
then building your product. And in a
322
00:22:51.319 --> 00:22:56.240
way, that is that they they're
motivated. Yeah, exactly. And and
323
00:22:56.440 --> 00:22:59.950
what we've seen, the motivation,
the outreach has been incredible. We're expecting
324
00:22:59.990 --> 00:23:02.869
that to double and then, you
know again, you know, continue to
325
00:23:03.309 --> 00:23:06.630
double and grow. Representative of that. You know, we have some big
326
00:23:06.670 --> 00:23:10.670
goals as a company for data dynamics, for our growth, even this year,
327
00:23:11.150 --> 00:23:14.940
and we see this being a very, very large portion to contribute to
328
00:23:15.220 --> 00:23:18.740
that growth this year. So,
you know, hey, it all starts
329
00:23:18.819 --> 00:23:22.740
with really understanding and helping the customers
when we can get
in and help the
330
00:23:22.859 --> 00:23:26.579
customers solve some of the hardest problems. Again, going back to that science
331
00:23:26.660 --> 00:23:27.769
project, every time I say that
I just, you know, I just
332
00:23:27.890 --> 00:23:32.049
go, boy, I've been in
the throes and I know exactly what they're
333
00:23:32.049 --> 00:23:36.450
experiencing and when you can certainly walk
in and have that level expertise or subject
334
00:23:36.450 --> 00:23:40.049
matter expertise with the customer, they'll
say, you get it. Now,
335
00:23:40.250 --> 00:23:41.920
help me, you know, understand
and how we're going to go do this
336
00:23:42.039 --> 00:23:47.400
differently and successfully at the end.
Yeah. Well, Chris, this is
337
00:23:47.480 --> 00:23:51.880
a guess. Has Been Fantastic and
I think you know, I love to
338
00:23:52.000 --> 00:23:55.359
hear your thoughts just because we have
a you know, our audience, our
339
00:23:55.440 --> 00:24:00.750
listeners, are partnering leaders, partnering
professionals just like yourself. What and you've
340
00:24:00.789 --> 00:24:06.950
had, you know, long career
and very successful any any sort of words
341
00:24:06.990 --> 00:24:10.859
of advice that you would either that
you heard early on that that you've,
342
00:24:11.140 --> 00:24:12.779
you know, sort of stuck with
you, or just things you picked up
343
00:24:12.779 --> 00:24:17.259
along the way that you want to
share? Yeah, I'll tell you.
344
00:24:17.380 --> 00:24:19.700
It all began a long, long
time ago, early in my career,
345
00:24:19.779 --> 00:24:25.769
I started IBM and what a wonderful
organization. I just I just can't say
346
00:24:25.769 --> 00:24:29.410
enough about it. The one thing
that I found, and the to the
347
00:24:29.490 --> 00:24:33.250
a testament of that organization's culture,
was just incredible. They put the customer
348
00:24:33.410 --> 00:24:37.650
first, right, and I didn't
really understand that. I thought, Oh
349
00:24:37.730 --> 00:24:41.319
Gosh, you know, just talk
to the customer or or understand the customer.
350
00:24:41.480 --> 00:24:44.920
Really took it a step further.
They help us to really understand the
351
00:24:45.039 --> 00:24:47.839
customer. Right. What are the
pain points the customers going to be facing
352
00:24:47.880 --> 00:24:49.720
in and during, you know,
as they're building out, you know,
353
00:24:49.799 --> 00:24:55.029
these infrastructures and or moving to the
cloud or different things like that. So
354
00:24:55.230 --> 00:25:00.230
early on in my career I really
learned to be more a stute to listening
355
00:25:00.470 --> 00:25:03.309
and understanding, but then, more
informatively, I wanted to share what I
356
00:25:03.630 --> 00:25:07.420
thought I heard and confirm it with
the customers. Right. So I do
357
00:25:07.740 --> 00:25:14.140
of what I hope is a good
job of documenting the discussions and I teach
358
00:25:14.220 --> 00:25:18.259
that to the teams today, because
that then tells the customers we've heard you
359
00:25:18.740 --> 00:25:22.210
and now we're going to put the
proper solution in place in front of you
360
00:25:22.450 --> 00:25:26.769
to make sure that we've heard and
can address all the concerns we have as
361
00:25:26.890 --> 00:25:30.930
well. Looking at the partnership community
today, right, I mean there's no
362
00:25:30.250 --> 00:25:33.849
way that you can't partner with somebody, I mean even friend of these right,
363
00:25:33.930 --> 00:25:37.200
you got to take those into consideration. Right, there's those times that
364
00:25:37.279 --> 00:25:41.519
you're going to have a friend of
me that comes into play. But you
365
00:25:41.599 --> 00:25:45.079
know, we looked at it across
horizontally, across our ecosystem and said,
366
00:25:45.079 --> 00:25:47.240
you know, these are the guys
agalas would want to go focus on.
367
00:25:47.559 --> 00:25:49.509
And when we say focus on them, I mean we took a very myopic
368
00:25:49.589 --> 00:25:55.789
approach. Let's go do this.
We classified our steps and I'm sure everybody
369
00:25:55.829 --> 00:25:59.470
probably follows the same business practice and
I can tell you that, you know,
370
00:25:59.710 --> 00:26:03.940
staying true to your mission is probably
the most critical thing, because there's
371
00:26:03.940 --> 00:26:07.579
going to be a lot of distractions. You've got to turn that noise down,
372
00:26:08.299 --> 00:26:12.259
stay focused on the mission and then
that will oftentimes get you to the
373
00:26:12.339 --> 00:26:15.779
areas that you need to produce the
results you have, and we had them.
374
00:26:17.019 --> 00:26:19.890
We've that ton of noise, you
know, in there and distractions,
375
00:26:21.049 --> 00:26:23.170
just like everyone else, and at
the end of the day we come right
376
00:26:23.289 --> 00:26:26.890
back to our center and what is
it and this is what we want to
377
00:26:26.930 --> 00:26:30.009
accomplish and how we're going to go
accomplish it. So we set our goals.
378
00:26:30.089 --> 00:26:33.319
They're hard goals. We work hard, we play hard and and that's
379
00:26:33.359 --> 00:26:37.119
a theme I hear repeatedly, but
I'll tell you, I really internalize it
380
00:26:37.200 --> 00:26:41.960
and embrace it because I want from
my legacies of understanding in this industry is
381
00:26:41.000 --> 00:26:44.079
to say, you know, Chris, do as you say, say as
382
00:26:44.119 --> 00:26:48.430
you do, right, and that's
just a simple slogan, but it's the
383
00:26:48.549 --> 00:26:52.549
most effective slogan and I think it's
very important for people that are starting their
384
00:26:52.589 --> 00:26:56.470
career and or midway through their career
and so on so forth. But you
385
00:26:56.509 --> 00:27:00.940
will find that that that certainly helps
people to embrace your concepts and your ideas.
386
00:27:02.539 --> 00:27:04.859
From there you can skies
the limit. Yeah, no, I love
387
00:27:04.940 --> 00:27:07.980
it. You know, I think
that customer censor centricity. I'm glad you
388
00:27:08.099 --> 00:27:11.420
started there, because I think that's
and I really like the you know,
389
00:27:11.660 --> 00:27:17.329
seek to understand concept of, you
know, really listening and and having that
390
00:27:17.569 --> 00:27:21.329
customer empathy and then I think feeding
it back, I think, is always
391
00:27:21.650 --> 00:27:25.809
really valuable as well, because then
they understand that they first of all,
392
00:27:26.769 --> 00:27:30.079
in order to say something it's harder. It CANNA. If you're going to
393
00:27:30.119 --> 00:27:34.400
articulate, you got to really understand
it. But then we also know that
394
00:27:34.519 --> 00:27:38.240
you don't understand it as well.
So yeah, if you start with why,
395
00:27:38.480 --> 00:27:41.279
you know, we've all seen the
Ted talks and Simon Senek really kind
396
00:27:41.319 --> 00:27:45.309
of classify. Start with why,
and that really begins to give you the
397
00:27:45.430 --> 00:27:48.710
center point. Your customers will say, you know, why are we doing
398
00:27:48.789 --> 00:27:52.710
this? Why are you doing this? Help us to understand, and it's
399
00:27:52.750 --> 00:27:56.630
not a negative it's really just,
hey, let's expose the problem, let's
400
00:27:56.630 --> 00:28:00.259
expose and talk about these situations.
And why are you trying to why were
401
00:28:00.299 --> 00:28:03.380
people going to the cloud? Right? I heard this, and this is
402
00:28:03.420 --> 00:28:07.819
one of the most keen stories.
I was actually in London and I was
403
00:28:07.900 --> 00:28:11.779
using Linkedin to connect with a guy
that he's based in Houston, Texas,
404
00:28:11.900 --> 00:28:15.529
with a large multinational oil and gas
company. I sent out the linkedin request
405
00:28:15.650 --> 00:28:19.690
and he instantly re accepted it and
hip, you know, that never happens,
406
00:28:19.809 --> 00:28:25.329
and I'm in the cafeteria of this
multinational in London, just outside of
407
00:28:25.369 --> 00:28:29.400
London. I said, Hey,
I'd love to get together for a meeting
408
00:28:29.680 --> 00:28:33.440
and maybe lunch and he says no, can do I'm in London for a
409
00:28:33.519 --> 00:28:38.720
week. My response back is,
oddly enough, I'm in lundle my yeah,
410
00:28:38.920 --> 00:28:45.029
right. So we scheduled lunch that
day and when he came down I
411
00:28:45.190 --> 00:28:49.670
recognized him coming down the escalator.
I recognized and I had asked him as
412
00:28:49.750 --> 00:28:53.069
the CIO of this multinational. I
said, hey, why are you going
413
00:28:53.309 --> 00:28:57.819
to the cloud? And this is
the most astonishing answer I'd had technical people
414
00:28:57.819 --> 00:29:02.059
tell me, because you know,
we're going to cut burocracy and process and
415
00:29:02.140 --> 00:29:04.619
we're going to save money and all
of these different things. He said to
416
00:29:04.700 --> 00:29:08.779
me, at an executive staff level, it takes US ten years to put
417
00:29:08.779 --> 00:29:12.009
a drill bit in the ground and
I want to do it in five.
418
00:29:12.890 --> 00:29:18.289
My shareolder value will double. I
didn't hear him say one word about technology.
419
00:29:18.490 --> 00:29:22.970
I didn't hear him say one word
about anything other than just the business
420
00:29:22.049 --> 00:29:26.359
process that he was reinventing for his
customers, for his customers right, and
421
00:29:26.400 --> 00:29:30.839
I said, I said I just
told him myself that I I've never heard
422
00:29:30.000 --> 00:29:34.279
such a profound answer. And I
said, why are you going to the
423
00:29:34.400 --> 00:29:37.759
cloud? You know, I was
trying to get that why in there.
424
00:29:37.920 --> 00:29:41.670
And there it was and that was
the most miraculous answer that I've ever heard
425
00:29:41.150 --> 00:29:45.470
and it left an indelible impression on
me. Saying wow, if I really
426
00:29:45.509 --> 00:29:49.150
understand, you know, all levels
of the organization, and I can't say
427
00:29:49.190 --> 00:29:52.059
that his message had infiltrated all the
way, you know, into his it
428
00:29:52.380 --> 00:29:57.220
organization, but it was an incredible
answer that really told me I was onto
429
00:29:57.299 --> 00:30:02.339
something just by really taking the time
to understand why they were doing so.
430
00:30:02.500 --> 00:30:03.980
That really closes it up and saying
you know, boy, if you can
431
00:30:04.019 --> 00:30:07.890
get to why you're going to be
you, you will find yourself closer to
432
00:30:07.930 --> 00:30:12.890
a trusted advisor in that true sense. Then bring up yeah, yeah,
433
00:30:14.369 --> 00:30:18.890
love it, Chris, really great
insights and citing what you guys are doing
434
00:30:18.930 --> 00:30:22.599
at data dynamics and wow, I
love the I love the business model and
435
00:30:22.640 --> 00:30:26.720
I love the the alignment with your
with your partners and, Gosh, getting
436
00:30:26.759 --> 00:30:29.279
them motivated to sell your stuff.
That's what it's all about, right,
437
00:30:29.960 --> 00:30:33.119
it really is. It's been a
great ride so far. We've got a
438
00:30:33.200 --> 00:30:36.470
lot to get done, you know, that's the classic statement, but we've
439
00:30:36.470 --> 00:30:41.990
got a very prescriptive plan of getting
their partner community is just they're absolutely invaluable
440
00:30:41.109 --> 00:30:45.990
when you look at the strengths and
areas that they fulfill that we don't have
441
00:30:45.269 --> 00:30:48.589
and areas that we can fulfill that
they don't have. But there's the interlock
442
00:30:48.789 --> 00:30:52.019
and that's where it's truly the partnership
and those make a lot of sense.
443
00:30:52.099 --> 00:30:56.700
So we've got the global systems integrators, we've got a Var community that's just
444
00:30:56.859 --> 00:31:00.500
unheard up in this industry and we're
happy to to work with them. That's
445
00:31:00.619 --> 00:31:03.490
great. Well, Chris, thank
you. Thank you for joining us and
446
00:31:03.690 --> 00:31:08.490
thank you all for joining us as
well for another episode of Ecosystem Asas and
447
00:31:08.890 --> 00:31:14.210
I think you know, with that
will sign off and love to have have
448
00:31:14.369 --> 00:31:18.799
you joined us for another episode coming
up shortly. Chris. Thank you.
449
00:31:18.079 --> 00:31:22.880
Yeah, chip, I've watched some
of the earlier presenters. I've learned a
450
00:31:22.960 --> 00:31:26.799
lot. These are invaluable. Keep
doing what you're doing. The community thanks
451
00:31:26.839 --> 00:31:29.640
you awesome. Good. Thank you, Chris. And Yeah, Gosh,
452
00:31:29.680 --> 00:31:33.670
a hundred, forty some episodes so
far and going strong. So loved having
453
00:31:33.710 --> 00:31:38.190
you on. Chris. Thank you, you bet. Thanks, chip Workspan
454
00:31:38.430 --> 00:31:45.109
is the category leader for ecosystem cloud, where alliance channel and ecosystem leaders connect.
455
00:31:45.430 --> 00:31:52.700
COCREATE CO MARKET CO cell measure and
scale with their ecosystem partners in a
456
00:31:52.859 --> 00:31:57.859
single, secure network to grow business
together. To learn more, visit workspandcom.
457
00:31:59.660 --> 00:32:02.170
You've been listening to ecosystem aces.
To ensure that you never miss an
458
00:32:02.170 --> 00:32:07.329
episode, subscribe to the show in
your favorite podcast player. Thanks so much
459
00:32:07.329 --> 00:32:07.890
for listening. Until next time,