WEBVTT

NOTE
This file was generated by Descript 

00:00:00.000 --> 00:00:03.161
Todd Kane: Most MSPs are still
treating automation as a nice-to-have.

00:00:03.340 --> 00:00:06.020
Aaron Bailey has been treating
it like a core operational

00:00:06.100 --> 00:00:07.440
strategy for over a decade.

00:00:07.940 --> 00:00:10.341
Aaron is the COO at Webit Services.

00:00:10.460 --> 00:00:14.940
Before that, he was COO at
MSP Bots and an RPA wizard.

00:00:15.319 --> 00:00:18.781
He's seen automation from both the
product side and the ops side, and

00:00:18.820 --> 00:00:22.300
that's a perspective most people
don't always have in the MSP industry.

00:00:23.120 --> 00:00:29.040
get into all things AI, RPA,
automation, and general operations.

00:00:30.020 --> 00:00:31.400
welcome to the Evolved Radio podcast

00:00:32.338 --> 00:00:33.218
Aarin: Thanks for having me, Todd

00:00:34.355 --> 00:00:40.156
Todd Kane: So you are, uh, very close
to my heart as a, an operator, uh,

00:00:40.337 --> 00:00:46.397
obsessed with improvement and efficiency
and, looking for all the things that

00:00:46.436 --> 00:00:49.397
you can squeeze out of the tools and
the systems that you're building.

00:00:50.236 --> 00:00:53.996
so you wanna tell us a, a bit about kind
of your experience and your journey on, on

00:00:54.036 --> 00:00:55.976
that moving, I guess, from sort of theâ¦

00:00:56.276 --> 00:00:59.677
You were a tech, obviously, then went
into the management and operations

00:00:59.736 --> 00:01:04.596
side, and then went really heavy
into, uh, automation opportunities.

00:01:04.635 --> 00:01:05.476
How did that come about?

00:01:05.515 --> 00:01:09.056
Like, what was sort of the, the
aha moment where you're like, "I

00:01:09.136 --> 00:01:10.097
think we could do this better"?

00:01:10.097 --> 00:01:11.877
Aarin: Yeah, I think it
was right around COVID.

00:01:11.957 --> 00:01:15.727
We had just hit COVID, and I was
working, uh, at a similar sized

00:01:15.977 --> 00:01:21.257
or about a $4 million MSP north
of, uh, where I'm at now in Elgin.

00:01:22.057 --> 00:01:25.237
Um, and, and it was before
all these tools had come out.

00:01:25.277 --> 00:01:25.997
Anything hadâ¦

00:01:26.057 --> 00:01:28.487
Nobody had even heard of,
of RPA in the industry.

00:01:28.757 --> 00:01:31.317
And I was sitting there looking at
a ton of PowerShell scripts, and I'm

00:01:31.357 --> 00:01:33.677
like, "How do I string these together?"

00:01:34.497 --> 00:01:38.757
And it became one kind of principle
of, I feel like if I could do multiple

00:01:38.837 --> 00:01:44.817
things at once or in a string, then I
could potentially repair a machine or

00:01:44.917 --> 00:01:48.997
execute more complex tasks than I'm
currently getting from, like, my RMM.

00:01:49.717 --> 00:01:53.197
Um, and, and you get limited to, like,
the RMM of just being a quick job or,

00:01:53.357 --> 00:01:56.317
or maybe it's just running the component
and, and there goes the job, and it's

00:01:56.357 --> 00:01:58.317
done, and you get what you get at the end.

00:01:59.037 --> 00:02:02.457
So I got really fascinated about
stringing some of these events

00:02:02.497 --> 00:02:07.217
together, and it really was just
tinkering with the PowerShell scripts.

00:02:07.277 --> 00:02:12.737
And as I kinda got really more into it,
it d- it kind of evolved into Python

00:02:12.797 --> 00:02:16.737
taking over more of the scripting
components of it and then, and then a GUI.

00:02:17.637 --> 00:02:22.377
And so I was a few years in, and
that's when I met Daniel, and I was,

00:02:22.417 --> 00:02:24.037
like, completely enamored with him.

00:02:24.077 --> 00:02:26.237
He just had all these great
ideas, and I'm like, "Daniel,

00:02:26.337 --> 00:02:27.577
let me show you what I'm doing.

00:02:27.657 --> 00:02:32.137
Like, I, I might be crazy, but I feel like
there's something to what you're saying."

00:02:32.257 --> 00:02:34.887
Um, and so I ran it through the whole
thing, and he's like, "Wow, that's

00:02:34.917 --> 00:02:38.177
exactly, you know, that's exactly
where my head's at too operationally."

00:02:38.197 --> 00:02:39.737
And he's like, "Let me
show you this platform."

00:02:39.757 --> 00:02:42.057
And so I was like, "Oh, I'd
love to be a part of that."

00:02:42.067 --> 00:02:44.567
And it kinda just took over from
there and, and just, you know,

00:02:45.017 --> 00:02:48.057
bunch of super nerds just nerding
out even more about automation.

00:02:48.067 --> 00:02:51.897
It just, uh, it became a problem where
it's like we're carrying a stopwatch

00:02:51.957 --> 00:02:55.417
'cause if you get Daniel and I in a
room, we'll just talk forever and ever

00:02:55.457 --> 00:02:57.977
and ever, and then we look back, and
we're like, "Okay, what did we get done?"

00:02:57.977 --> 00:03:00.957
So it's just kinda been
this evolving fascination.

00:03:01.057 --> 00:03:04.057
Um, and then of course when ChatGPT
came out and everything and it kinda

00:03:04.157 --> 00:03:08.997
changed the landscape, it really
changed how much I could get done.

00:03:09.017 --> 00:03:13.017
And I started looking at it of just,
okay, well, how can I augment myself to

00:03:13.037 --> 00:03:15.297
get more of what I wanna get done, done?

00:03:15.937 --> 00:03:19.637
Um, and then just one thing after
another and, you know, four endless

00:03:19.697 --> 00:03:22.877
sleepless nights after another, and I'm
realizing all the cool stuff I can do.

00:03:23.277 --> 00:03:26.797
And I've just burnt, you know,
84 hours into an AI project,

00:03:26.897 --> 00:03:29.837
and, uh, I'm explaining to my
wife, "It's gonna be okay."

00:03:31.501 --> 00:03:31.801
Todd Kane: This feels

00:03:31.877 --> 00:03:33.337
Aarin: It's all in the name of work.

00:03:33.682 --> 00:03:33.922
Todd Kane: Yeah.

00:03:35.021 --> 00:03:36.241
Like, do you have any hobbies anymore?

00:03:36.442 --> 00:03:39.982
Yeah, yeah, lots of vibe coding,
lots of, uh, figuring stuff

00:03:40.048 --> 00:03:40.428
Aarin: Yeah.

00:03:40.461 --> 00:03:40.801
Todd Kane: AI.

00:03:40.961 --> 00:03:41.101
Yeah.

00:03:42.108 --> 00:03:42.428
Aarin: Yeah

00:03:43.282 --> 00:03:46.281
Todd Kane: Well, so let's, uh, let's
go deep and nerdy then, 'cause,

00:03:46.341 --> 00:03:47.442
like, a bunch of things that you

00:03:47.532 --> 00:03:47.772
Aarin: Sure

00:03:48.041 --> 00:03:49.141
Todd Kane: I wanna understand better.

00:03:49.201 --> 00:03:52.621
Um, so I, I guess from my
perspective, like, uh, like I'll,

00:03:52.621 --> 00:03:53.742
I'll give the background on this.

00:03:53.841 --> 00:03:58.081
I was always very cautious and a bit
skeptical about the way that vendors

00:03:58.181 --> 00:04:02.822
positioned automation and, you know,
the original, uh, what they called AI,

00:04:02.881 --> 00:04:04.461
which was, like, barely machine learning.

00:04:04.522 --> 00:04:06.741
It was a bunch of strung
together if-then statements.

00:04:07.761 --> 00:04:12.101
a-a-and I think my skepticism
was somewhat justified.

00:04:12.781 --> 00:04:15.261
Uh, my tune has changed a
lot, which we'll get to.

00:04:15.701 --> 00:04:21.221
But, uh, w-w-w- the RMM
kind of relying onâ¦

00:04:21.322 --> 00:04:25.101
Like, the original RMMs were scripts
inside the RMM, and then what I, I

00:04:25.141 --> 00:04:28.041
kind of told people based on what
I sort of understood was, like,

00:04:28.101 --> 00:04:29.401
"Don't rely on internal scripts.

00:04:29.421 --> 00:04:30.961
Don't build your scripts in your RMM.

00:04:31.322 --> 00:04:33.641
Just have your RMM call
PowerShell scripts."

00:04:34.801 --> 00:04:37.581
I still sort of understand that
that's probably the default

00:04:37.621 --> 00:04:40.961
way to go about things as, uh,
maybe for general purpose stuff.

00:04:41.641 --> 00:04:43.341
Is that correct, or would you sayâ¦

00:04:43.621 --> 00:04:46.982
Like you said, you kind of drifted
more into, into, like, Python for,

00:04:47.141 --> 00:04:50.781
for more programmatic controls
of this beyond PowerShell.

00:04:51.281 --> 00:04:52.721
What was the difference between those?

00:04:52.761 --> 00:04:56.221
Would you say, like, typical automations
from R- from an RMM are still

00:04:56.281 --> 00:05:00.481
probably better done in PowerShell,
or is there, uh, would Python be the

00:05:00.522 --> 00:05:02.261
new hotness, and if w- if so, why?

00:05:04.017 --> 00:05:05.317
Aarin: They're sort of
different languages.

00:05:05.497 --> 00:05:09.997
I think I've always still had PowerShell
that runs because in some way.

00:05:10.037 --> 00:05:11.497
I mean, it depends on
what I'm interacting with.

00:05:11.597 --> 00:05:14.277
If I'm interacting with like the
Windows system or something like

00:05:14.337 --> 00:05:17.897
that, yeah, I'm, I'm definitely diving
into my, my, my PowerShell because

00:05:17.957 --> 00:05:21.497
it's readily available on the system,
don't have to do anything special.

00:05:22.157 --> 00:05:26.897
I think what ended up changing for
us is what we wanted to get out of

00:05:26.937 --> 00:05:30.017
the system was a little bit more
than what a lot of people can offer.

00:05:30.617 --> 00:05:32.877
You get SaaS products and
a lot of them are great.

00:05:32.937 --> 00:05:36.256
You can do a bunch of great stuff with
them, but there's always something

00:05:36.317 --> 00:05:41.017
more that we wanna do as engineers that
just doesn't fit into that white glove.

00:05:41.597 --> 00:05:45.187
Um, and so that kind of evolved
into-- It started off as actually a,

00:05:45.277 --> 00:05:47.777
uh, a bot, um, when I came to Webit.

00:05:47.877 --> 00:05:51.757
Uh, it started off as just a,
a bot on the Azura framework.

00:05:51.897 --> 00:05:56.277
Um, and so it was, uh, setting all
that stuff up and then hooking that

00:05:56.337 --> 00:06:02.137
into the automations with Roost and
then breaking free of the RMM entirely.

00:06:02.217 --> 00:06:07.197
The only reason we use RMMs is, um,
we'll write scripts for monitoring

00:06:07.417 --> 00:06:10.237
if we're trying to monitor like a
service or, or something like that.

00:06:10.817 --> 00:06:13.837
Um, and then we'll use it to push
our quick jobs coming off of like

00:06:13.897 --> 00:06:15.157
Roost or something like that.

00:06:15.937 --> 00:06:20.537
And so, um, most of our actual computation
doesn't even happen in the RMM.

00:06:20.837 --> 00:06:22.097
Um, I go crazier.

00:06:22.237 --> 00:06:23.357
I have SQL servers.

00:06:23.477 --> 00:06:24.957
I've got Python servers.

00:06:24.997 --> 00:06:28.437
I've got just server upon
server of just stuff.

00:06:28.497 --> 00:06:34.237
It's, it's kind of looking at it more
like a beehive of taking individualized

00:06:34.277 --> 00:06:38.437
components and, and essentially what
is that component really good at and

00:06:38.577 --> 00:06:43.217
snapping it into a larger system, um,
that all works in conjunction together.

00:06:43.347 --> 00:06:44.937
And so I'll have a little bit in Roost.

00:06:45.337 --> 00:06:48.257
I've got a little bit in, in like our
thread system that we currently run.

00:06:48.297 --> 00:06:51.757
We've got, uh, uh, some that's in a
Python server just sitting in Azura.

00:06:52.437 --> 00:06:56.527
Um, but that's pretty much our primary
instance of stuff running is that

00:06:56.557 --> 00:07:00.147
Python server which runs all our
PowerShell scripts, uh, all our Python,

00:07:00.197 --> 00:07:01.577
everything comes from that server.

00:07:02.137 --> 00:07:05.697
But it, it's where it starts out
is either on the RMM or within

00:07:05.757 --> 00:07:09.727
Roost, um, coming into that, and
then it takes a direction based on

00:07:09.757 --> 00:07:11.277
whatever the code's telling it to do.

00:07:11.849 --> 00:07:15.349
Todd Kane: Okay, so it's more like
extensibility than it was sort of like,

00:07:15.709 --> 00:07:17.629
like the actual call actions, right?

00:07:17.710 --> 00:07:18.270
Like PowerShell's

00:07:18.372 --> 00:07:18.812
Aarin: Correct

00:07:18.869 --> 00:07:21.829
Todd Kane: kind of controlling a
Windows server or a Windows desktop,

00:07:21.924 --> 00:07:22.585
Aarin: Absolutely

00:07:23.129 --> 00:07:26.749
Todd Kane: more sort of global
control and like functions that

00:07:26.789 --> 00:07:28.269
would call other stuff to do.

00:07:28.629 --> 00:07:31.529
I guess like, yeah, like you said,
like it's almost in a way, like

00:07:31.649 --> 00:07:35.809
would you consider it sort of an
alternate or a replacement of the

00:07:35.849 --> 00:07:37.669
larger functions of the RMM in a way?

00:07:37.669 --> 00:07:39.969
Aarin: No, I think they
still have their own purpose.

00:07:40.270 --> 00:07:44.449
Um, I mean, you could probably dice
and I'm sure there's crazier people

00:07:44.510 --> 00:07:48.490
out there than me that have probably
tried, but I try to limit the amount

00:07:48.530 --> 00:07:51.609
of agents that, that are on my
clients' computers in the first place.

00:07:52.089 --> 00:07:55.249
I mean, we've already got three
or four different agents between

00:07:55.389 --> 00:07:56.949
systems that run on these things.

00:07:56.990 --> 00:07:59.729
So that's always been a big concern.

00:07:59.830 --> 00:08:05.289
Being able to leverage the RMM in
that capacity doesn't really change

00:08:05.349 --> 00:08:08.330
what we're doing with it as far as
the monitoring and everything else.

00:08:08.809 --> 00:08:12.489
It just, it's, it's kind of just, okay,
I don't want that to be my entry point.

00:08:12.549 --> 00:08:14.729
I don't want my stuff to start in the RMM.

00:08:15.189 --> 00:08:19.029
It just needs to be a piece or a layer
of this bigger system that we're building

00:08:19.070 --> 00:08:23.649
because inevitably, um, back to that
beehive, as we start to snap stuff

00:08:23.729 --> 00:08:27.789
in and, and snap them together, um,
we get better, we get faster, we get

00:08:27.829 --> 00:08:30.229
smarter with every piece that happens.

00:08:30.269 --> 00:08:34.630
And so it's just another layer, um, in
that, in that onion that we're building

00:08:35.510 --> 00:08:39.051
Todd Kane: Yeah, 'cause this sort of
goes to like, um, who is it told me this?

00:08:39.091 --> 00:08:43.151
I think it was Dave Sobel described
RMM as a zombie product to me.

00:08:43.631 --> 00:08:46.312
I don't know if he got this from somebody
else or if, uh, he coined that, but

00:08:46.371 --> 00:08:50.892
like I, I got immediately attached to
that idea, and I still feel like it's

00:08:50.951 --> 00:08:55.852
somewhat true, but maybe I'm losing a
bit of faith that like the, the, that

00:08:55.872 --> 00:09:00.371
it becoming a true zombie product is as
near term as maybe I imagined it was.

00:09:00.651 --> 00:09:05.011
I think it's still got some legs, but
like the longer term view of this I think

00:09:05.091 --> 00:09:10.472
becomes more like what you're describing
of like global infrastructure, uh, and

00:09:10.551 --> 00:09:14.251
how these things are knitted together
in some fashion rather than it being

00:09:14.391 --> 00:09:16.391
kind of built actually in the RMM.

00:09:16.411 --> 00:09:20.991
I think the RMM may be still as an
attach point or maybe it migrates to

00:09:21.051 --> 00:09:25.371
like, uh, kind of Intune as backplane
management, those sorts of things, right?

00:09:25.651 --> 00:09:30.812
But then, you know, um, you know, how
are we managing SaaS platforms and, you

00:09:30.812 --> 00:09:32.371
know, third-party integrations, right?

00:09:32.891 --> 00:09:36.831
Um, uh, so, you know, it gets, it get-
gets kind of complicated, but maybe as

00:09:36.871 --> 00:09:41.612
a quick aside, how do you feel about,
uh, that, that description of RMM as a

00:09:41.671 --> 00:09:45.571
zombie product and like it will continue
to live on, but like doesn't sort of

00:09:45.612 --> 00:09:50.012
carry the same gravity or importance in
the MSP ecosystem in five years, say?

00:09:51.890 --> 00:09:53.750
Aarin: I mean, I don't, I don'tâ¦

00:09:53.760 --> 00:09:55.770
The world's getting
really, really complicated.

00:09:55.830 --> 00:10:00.450
I mean, when I look at could I
cut my RMM today and be just fine?

00:10:00.510 --> 00:10:01.780
Probably.

00:10:01.830 --> 00:10:02.650
I probably could.

00:10:02.690 --> 00:10:05.190
Would I have to do some extra
work to get that to happen?

00:10:05.270 --> 00:10:05.670
Yes.

00:10:06.390 --> 00:10:09.250
Uh, but most of our clients
have E3, so we can tap into the

00:10:09.290 --> 00:10:10.810
Microsoft system for patching.

00:10:11.050 --> 00:10:15.210
Monitoring, okay, yeah, that's a
loss, but we also have Imibot, so that

00:10:15.310 --> 00:10:18.730
helps us with like RMM and, and, and
patching and some other stuff as well.

00:10:18.790 --> 00:10:20.580
So we've got so manyâ¦

00:10:20.710 --> 00:10:24.310
I think we counted last time, we had
something like 70 tools in our arsenal.

00:10:25.010 --> 00:10:28.570
Um, and I was just thinking, "My
God, uh, we have a lot of stuff."

00:10:28.810 --> 00:10:30.270
Um, and it becomes why?

00:10:30.470 --> 00:10:31.650
And, and I, I agree.

00:10:31.750 --> 00:10:36.990
I don't see five years, maybe a little
bit longer, um, but you just get one

00:10:37.030 --> 00:10:41.250
good idea that just shakes up everything
and, and the cards start falling.

00:10:41.310 --> 00:10:44.150
I mean, we've already
saw- seen threats come in.

00:10:44.350 --> 00:10:48.030
Or not really threats, I think fantastic
products, but like Halo coming into

00:10:48.050 --> 00:10:52.970
the marketplace and really just taking
on, um, that Autotask Connectwise

00:10:53.010 --> 00:10:54.750
relationship of them being the dominant.

00:10:54.870 --> 00:10:59.050
Now here they come, and you have NinjaOne
making a play for it with their PSA

00:10:59.070 --> 00:11:03.050
and their RMM, and, and they're trying
to pair them together of the best

00:11:03.090 --> 00:11:05.550
functionality that could possibly happen.

00:11:06.040 --> 00:11:08.410
And that's true when you're
in their platform, absolutely.

00:11:08.470 --> 00:11:11.130
Like I'm not gonna be able to
replicate the same experience in

00:11:11.170 --> 00:11:14.330
my Autotask platform as I would if
I started to say, "Hey, I'm gonna

00:11:14.350 --> 00:11:18.730
throw in, um, you know, Automate or
whatever, uh, as my RMM platform."

00:11:19.110 --> 00:11:20.950
It'd be a completely different experience.

00:11:21.570 --> 00:11:24.310
So I, I don't know that it's
really the RMM is going away.

00:11:24.330 --> 00:11:28.410
It's reshaping into a different
experience, um, into what it's being

00:11:28.490 --> 00:11:30.450
used for and how it's being used.

00:11:30.670 --> 00:11:33.270
Uh, the, the one thing that's
really doesn't seem to be changing

00:11:33.290 --> 00:11:37.190
at that, that layer is the PSA
as far as being a ticketing

00:11:37.200 --> 00:11:38.800
tool, but I think that's natural.

00:11:38.850 --> 00:11:40.360
I mean, what are you gonna
do with a ticketing tool?

00:11:41.250 --> 00:11:43.770
Inject some AI into a
50-year-old framework?

00:11:44.598 --> 00:11:47.279
Todd Kane: Well, e- even like Thread,
you know, like I, I love this, the

00:11:47.299 --> 00:11:49.819
work that they're doing over there
and, and they have this, this call

00:11:49.859 --> 00:11:51.218
to action of death to the ticket.

00:11:51.379 --> 00:11:54.759
But, you know, realistically, there
still needs to be some type of database

00:11:54.819 --> 00:11:57.039
of record of work activity and action.

00:11:57.218 --> 00:11:58.459
So is it a PSA?

00:11:58.759 --> 00:11:59.980
Like, where does the ticket live?

00:12:00.020 --> 00:12:02.439
Like, we still k- uh, we need
the plumbing still, right?

00:12:02.565 --> 00:12:03.325
Aarin: You need the plumbing.

00:12:03.365 --> 00:12:04.885
If there's not a ticket,
it never happened.

00:12:05.547 --> 00:12:06.146
Todd Kane: Yeah, that's

00:12:06.325 --> 00:12:08.125
Aarin: Even if it did happen
and you don't know it,

00:12:09.087 --> 00:12:09.307
Todd Kane: Yeah

00:12:09.525 --> 00:12:09.785
Aarin: prove it.

00:12:09.805 --> 00:12:12.045
It's like if a tree falls in
the wood and nobody's around to

00:12:12.065 --> 00:12:13.285
hear it, it doesn't make a sound

00:12:13.655 --> 00:12:13.856
Todd Kane: Yeah.

00:12:14.555 --> 00:12:17.534
So this also lends to, you
know, delicate infrastructure.

00:12:17.754 --> 00:12:21.775
Like, as you kind of like gobble these
things together and like pack modules

00:12:21.834 --> 00:12:26.874
onto modules and, and build upon sort
of this, this, uh, this towering code

00:12:26.954 --> 00:12:31.675
structure, um, how do you think about
sort of the risk of that being, you

00:12:31.675 --> 00:12:37.774
know, unstable or a lot of, uh, support
effort or, uh, or it just being quite

00:12:37.834 --> 00:12:40.974
complicated and troubleshooting things
that go sideways for some reason?

00:12:40.994 --> 00:12:44.374
If you add a module, then all of a
sudden three other things break, right?

00:12:44.435 --> 00:12:48.074
Like how, uh, how do you think about
scaling the complexity of the things

00:12:48.114 --> 00:12:49.094
that you're building internally?

00:12:50.813 --> 00:12:54.313
Aarin: I think that's part of what
I've tried to do is keep everything

00:12:54.393 --> 00:12:57.453
into those separate modules and
then, you know, we use a lot of

00:12:57.493 --> 00:12:59.353
RESTful API and other stuff to, toâ¦

00:12:59.433 --> 00:13:02.553
That way if something does break, it's
not really affecting the whole platform.

00:13:02.633 --> 00:13:04.713
We see it just in that
individualized module.

00:13:05.614 --> 00:13:09.433
Um, but one of the things that I've,
I've really tried to really focus

00:13:09.473 --> 00:13:13.493
the whole team on preparing for is,
like, if you're not ready to start

00:13:13.533 --> 00:13:16.693
learning Python, at least in a, in
a readability, you don't need to go

00:13:16.793 --> 00:13:18.213
sit there and code out the next app.

00:13:18.253 --> 00:13:19.753
But you need to be able to read Python.

00:13:19.793 --> 00:13:22.873
You need to understand what RPA
and automation is, and be able

00:13:22.914 --> 00:13:26.393
to have a conversation in, in,
in what's going on in reality.

00:13:27.053 --> 00:13:32.713
Um, it, it helps as we start to go through
this to have more people involved in that

00:13:32.793 --> 00:13:38.234
sort of, that sort of mentality of, okay,
five, six years ago, everybody was jumping

00:13:38.293 --> 00:13:42.053
on the security train and everybody needed
to be a security trained professional.

00:13:42.074 --> 00:13:44.013
Well, now it's like, okay,
well, why wouldn't we do the

00:13:44.074 --> 00:13:45.413
same thing with automation?

00:13:46.133 --> 00:13:49.853
Um, and it makes more sense
because, or it makes just as much

00:13:49.914 --> 00:13:52.933
sense as it did with security
because the world ends up shifting.

00:13:53.414 --> 00:13:55.933
If you're not preparing your
staff for that, then in five

00:13:55.994 --> 00:13:58.213
years I won't even be in business.

00:13:58.293 --> 00:14:01.593
So it's kinda just adopting
and taking, like, I understand

00:14:01.634 --> 00:14:02.573
that AI is gonna happen.

00:14:02.653 --> 00:14:04.613
I understand that the
world is gonna change.

00:14:04.653 --> 00:14:08.373
How can we better prepare
ourselves, um, to be ready for that?

00:14:08.414 --> 00:14:11.673
And it's, it's kinda brings me back
to that Ray Dalio quote of just,

00:14:11.713 --> 00:14:14.553
"You're going down a river and
there's always objects in the river.

00:14:15.053 --> 00:14:16.313
Um, you can't remove the objects.

00:14:16.373 --> 00:14:18.774
All you can do is, is learn
to go around the objects."

00:14:19.613 --> 00:14:22.473
And that's just kind of how the,
uh, the AI and the MSP's gone

00:14:23.042 --> 00:14:25.602
Todd Kane: Or flow like l- flow
like water, Bruce Lee, right?

00:14:25.645 --> 00:14:25.986
Aarin: Yes.

00:14:28.102 --> 00:14:30.542
Todd Kane: Uh, okay, so I'll, I'll
maybe circle back to that 'cause

00:14:30.562 --> 00:14:31.883
that's another thing I wanted to,

00:14:32.561 --> 00:14:32.741
Aarin: Yeah

00:14:32.803 --> 00:14:33.303
Todd Kane: on here.

00:14:33.442 --> 00:14:38.582
Um, but the other, the other aspect
that I find really interesting, um, I,

00:14:38.702 --> 00:14:41.723
I know a lot of the stuff that you're
building, you build internally rather

00:14:41.803 --> 00:14:43.202
than using something off the shelf.

00:14:43.282 --> 00:14:46.902
Now, part of this is because you can,
I suppose, and you have a bit more

00:14:46.963 --> 00:14:52.062
control over it, But, like, uh, what's,
what's sort of your calculus on I

00:14:52.122 --> 00:14:55.963
could buy an off-the-shelf project, uh,
product, but, you know, for example,

00:14:56.222 --> 00:15:00.082
one of the things I know you did was,
uh, built like your own AI for triage.

00:15:00.422 --> 00:15:03.362
Like, that's generally beyond the
capability of a lot of people.

00:15:03.463 --> 00:15:08.882
Maybe less so now with some of the,
like the AI, uh, assisted coding tools.

00:15:09.303 --> 00:15:12.702
But, um, uh, that, that's, uh,
that's something you chose to build

00:15:12.742 --> 00:15:16.582
internally rather than using a, like
a, a software package that you could

00:15:16.622 --> 00:15:18.362
buy that do, does the same thing.

00:15:18.842 --> 00:15:19.402
So whatâ¦

00:15:19.442 --> 00:15:22.922
Like, what's your, what's your thought
process or analysis of this feature

00:15:23.042 --> 00:15:25.963
exists in some of the platforms
I could potentially purchase,

00:15:26.342 --> 00:15:29.382
but I could also just go build
this myself because I know I can?

00:15:29.382 --> 00:15:33.222
Aarin: I think it comes down to, uh,
looking at it from building at scale.

00:15:33.542 --> 00:15:37.212
Uh, you know, we've, we've done a
considerable amount of just growth as,

00:15:37.242 --> 00:15:41.102
as far as a company, and, and we're about
twice the size, but we've only added

00:15:41.142 --> 00:15:43.882
two bodies, um, across the whole stack.

00:15:44.002 --> 00:15:46.642
Um, everything has gone
up and, and, and weâ¦

00:15:46.802 --> 00:15:50.052
As we start having to deal with
that, it becomes what delivers the

00:15:50.102 --> 00:15:51.982
most ROI coming back off of that.

00:15:52.742 --> 00:15:56.102
And that's an important factor because
I think early on as I was doing

00:15:56.162 --> 00:16:00.722
automation, uh, I think I mentioned,
I would go spend dozens of hours

00:16:00.822 --> 00:16:02.282
just trying to play around with it.

00:16:02.462 --> 00:16:06.462
And, and it really became important
that if I was gonna sit down and do an

00:16:06.502 --> 00:16:10.582
automation, it was gonna have some sort
of ROI or some impact on the company.

00:16:10.632 --> 00:16:12.522
It wasn't just for the sake of automating.

00:16:13.242 --> 00:16:18.022
And so as we start to build this stuff
up, we start looking at what is the cost

00:16:18.082 --> 00:16:21.482
to do it versus the benefit that we're
actually getting off of this stuff.

00:16:21.542 --> 00:16:23.642
How complex is this gonna be?

00:16:23.742 --> 00:16:27.762
Um, and then the second half of that is
looking at does it fit what we wanna do?

00:16:27.882 --> 00:16:31.322
Because we're not building
like every other MSP.

00:16:31.382 --> 00:16:34.902
I mean, I've come across a lot, as
I'm sure you've come across a lot

00:16:34.942 --> 00:16:38.332
of MSPs, and n-not one single one
have I ever looked at and said,

00:16:38.402 --> 00:16:40.582
"Wow, you operate just like I do."

00:16:40.602 --> 00:16:42.942
In fact, it's almost
always the exact opposite.

00:16:43.462 --> 00:16:47.042
And so, um, and even when I was talking
to Daniel yesterday, uh, we were talking

00:16:47.122 --> 00:16:49.562
about scale, and he's like, "Well, yeah,
you go build it for the one company

00:16:49.582 --> 00:16:50.862
and that's great, it works perfect."

00:16:50.902 --> 00:16:52.442
And then the second, okay.

00:16:52.722 --> 00:16:56.002
And then the third, and then it's like,
oh crap, we've gotta go figure out we

00:16:56.062 --> 00:16:57.481
missed this, this, this, this, this.

00:16:58.182 --> 00:17:01.062
Um, and so that kind of became
just this whole, I don't wanna

00:17:01.122 --> 00:17:04.482
have to deal with other problems
of other things that are going on.

00:17:04.542 --> 00:17:08.982
I don't wanna have to deal with, uh,
um, being put into a box where I'm sure

00:17:09.022 --> 00:17:14.662
it might work for this group of MSPs,
um, but we operate entirely different.

00:17:14.703 --> 00:17:18.433
You know, our entire triage and dispatch
is automated, uh, with ninety-eight

00:17:18.522 --> 00:17:21.542
percent accuracy, and we haven't
touched it in, in about a year now.

00:17:22.142 --> 00:17:27.922
Um, the triage we did move, uh, naturally
over to Thread because, um, token costs

00:17:28.723 --> 00:17:31.703
and which became a completely different
factor in all of this, of just how

00:17:31.723 --> 00:17:33.223
much token costs are coming in this.

00:17:33.243 --> 00:17:36.842
And it became cheaper to run this off
of Thread at the time than it did to

00:17:36.942 --> 00:17:40.803
actually run this off of a large language
model, where inherently it's actually

00:17:40.862 --> 00:17:45.203
cheaper, it's cheap enough to keep our
dispatching on that system using the AI

00:17:45.263 --> 00:17:48.982
as kind of like a, um, this ticket got
missed in the process, so it, it runs

00:17:49.002 --> 00:17:51.783
through a fail-safe check to say, "Did
everything get done on the ticket?"

00:17:51.842 --> 00:17:54.362
before I actually punch it through
and send it out to somebody.

00:17:54.922 --> 00:17:57.642
Which, and, and funny
enough, that uses no AI.

00:17:57.902 --> 00:18:01.183
It's, it's actually all a roost
workflow and a stored SQL, uh,

00:18:01.303 --> 00:18:03.421
process off an AI as our tenant.

00:18:03.462 --> 00:18:09.002
So, um, it's really is a true hodgepodge,
but I haven't really gotten to like, this

00:18:09.062 --> 00:18:11.183
is what is the best thing for ROI orâ¦

00:18:11.433 --> 00:18:14.522
I think the best thing that I've
found is have a plan, know what

00:18:14.562 --> 00:18:18.902
you're gonna build, and know that it's
gonna return some sort of ROI on it.

00:18:19.142 --> 00:18:21.092
Um, and that's kind of
just been my guiding map

00:18:22.731 --> 00:18:24.311
Todd Kane: Yeah, so that's
really fascinating, right?

00:18:24.411 --> 00:18:30.551
Like, um, I, I, I quote this all the time
of, um, uh, especially being a person

00:18:30.592 --> 00:18:35.011
that consults with of different MSPs
and gets a bit of a peek behind the door

00:18:35.251 --> 00:18:39.271
for a lot of them, and I always joke
that everyone has the same predominant

00:18:39.332 --> 00:18:40.551
business model for the most part.

00:18:40.631 --> 00:18:43.191
Like, maybe you're a bit more of a
VAR, maybe you're a bit more of an

00:18:43.311 --> 00:18:46.671
MSP, but generally, like, we're all
trying to achieve the same thing with

00:18:46.711 --> 00:18:48.451
the same, same general business model.

00:18:49.251 --> 00:18:51.091
of them operate the same way, right?

00:18:51.191 --> 00:18:51.751
Like, which is

00:18:51.938 --> 00:18:52.197
Aarin: Yeah.

00:18:52.871 --> 00:18:52.992
Todd Kane: right?

00:18:53.072 --> 00:18:56.672
Like, the number of ways to actually do
this and the differences that always sort

00:18:56.692 --> 00:19:01.631
of stem from sort of the, the, the, the,
the lessons or the experiences of the

00:19:01.731 --> 00:19:05.411
owner, the psychology of the owner, the
makeup of the team, the experiences of

00:19:05.431 --> 00:19:09.591
the team, all of those things influence
how the operation actually sort of

00:19:09.611 --> 00:19:11.311
spins out and what it looks like.

00:19:11.371 --> 00:19:13.691
So there's, there's
definite truth to that.

00:19:13.731 --> 00:19:18.824
But also your, your point about, um
We build it for ourselves because

00:19:18.884 --> 00:19:21.884
we want it the way that we want it,
not the way that the vendor chose

00:19:21.944 --> 00:19:25.074
to build it based on inputs from all
of these other companies that don't

00:19:25.144 --> 00:19:26.404
operate the same way that we do.

00:19:26.744 --> 00:19:29.724
I think that's really, really
interesting, quite insightful also

00:19:29.764 --> 00:19:34.024
that, uh, um, you know, you, you--
again, because you have the capability

00:19:34.284 --> 00:19:38.004
to take that on yourself, I think is
a bit of a unique advantage as well.

00:19:39.584 --> 00:19:42.924
the token cost, I, I think this is
a really interesting aspect, right?

00:19:42.984 --> 00:19:45.924
Like we're seeing this all over
the place in the enterprise, right?

00:19:45.964 --> 00:19:49.304
So I'm glad you brought this up because
I'm curious how this will eventually start

00:19:49.384 --> 00:19:55.664
to, uh, impact more of the MSP and the
SMB space, we're seeing at the enterprise

00:19:55.744 --> 00:20:00.284
level, there, you know, I'm sure you've
heard the term token maxing, right?

00:20:00.364 --> 00:20:01.844
There's a few, a few companies.

00:20:02.004 --> 00:20:05.584
I know a guy who works at a very,
very recognizable, uh, uh, uh,

00:20:06.084 --> 00:20:10.684
enterprise SA- uh, SaaS company,
they have a token leaderboard.

00:20:10.964 --> 00:20:14.914
And the CFO was in a meeting with the
leadership team and suggested like,

00:20:14.934 --> 00:20:19.254
"Hey, do you think we're creating, uh,
an incentive that doesn't align with

00:20:19.284 --> 00:20:21.004
what we're trying to achieve here?"

00:20:21.024 --> 00:20:24.924
And everyone kind of understood what
they were, they were suggesting, but

00:20:24.944 --> 00:20:29.144
they got completely shut down and the,
the, the ethos from the leadership team

00:20:29.184 --> 00:20:31.164
was essentially let them cook, right?

00:20:31.664 --> 00:20:36.224
But at the same time, we're also seeing
a lot of enterprise companies that are

00:20:36.284 --> 00:20:41.594
now drastically slashing the AI coding
budgets because they have, they have

00:20:41.724 --> 00:20:47.504
dwarfed the actual, uh, human labor
costs that they were supposed to replace,

00:20:48.057 --> 00:20:48.317
Aarin: Yeah

00:20:48.364 --> 00:20:51.674
Todd Kane: So there's some interesting
efficiency economics that are not

00:20:51.724 --> 00:20:56.224
necessarily working out the way that
people anticipated with utilizing AI

00:20:56.284 --> 00:21:00.844
coding, and I'm curious sort of how
this will eventually impact some of

00:21:00.884 --> 00:21:04.824
the SMBs that are trying to, uh, you
know, do some of the stuff on your own.

00:21:04.924 --> 00:21:07.894
Um, I think like you have a more
traditional coding background

00:21:07.924 --> 00:21:09.034
and can do some of this.

00:21:09.124 --> 00:21:12.834
You're, uh, kind of by yourself
and string these things together.

00:21:13.144 --> 00:21:17.544
Uh, how much has that shifted
in using like, uh, um, you know,

00:21:17.644 --> 00:21:19.764
vibe coding or AI pair coding?

00:21:19.804 --> 00:21:22.714
How much of that is your, is
your workflow now versus before?

00:21:24.466 --> 00:21:28.706
Aarin: Well, I think it's, I think
the industry has got it wrong.

00:21:28.946 --> 00:21:33.246
AI was never, in my mind,
never meant to replace humans.

00:21:33.317 --> 00:21:37.826
And the more that we try to go force
that down humanity's throat, the

00:21:37.886 --> 00:21:39.706
more lost the companies are gonna be.

00:21:39.766 --> 00:21:42.797
I mean, Salesforce went and laid off,
what, 4,000 jobs, and then next thing

00:21:42.846 --> 00:21:44.526
you know they're hiring them all back.

00:21:44.706 --> 00:21:47.726
Um, AI's always been an augmentation.

00:21:47.986 --> 00:21:51.627
It's, it's, it's like taking
something that can only handleâ¦

00:21:51.667 --> 00:21:52.946
It's, it's the world of data.

00:21:52.986 --> 00:21:54.926
Our data in the world is so complex.

00:21:54.966 --> 00:21:55.746
There's so much data.

00:21:55.786 --> 00:21:57.906
We can't physically,
as humans, handle that.

00:21:58.627 --> 00:22:02.107
So we need AI to be able to keep
up with the amount of complexity

00:22:02.127 --> 00:22:04.377
that life is, is, like, produced.

00:22:04.456 --> 00:22:07.226
But it's not like, oh, let's go
replace humans and, and we're just

00:22:07.246 --> 00:22:08.946
gonna have robots walking around.

00:22:09.006 --> 00:22:11.187
Like, that's, it's not gonna happen.

00:22:11.306 --> 00:22:14.506
Um, but companies think that
that is a good way to get ROI.

00:22:14.587 --> 00:22:17.817
Oh, let me just go replace it with
this magical robot in the sky that's

00:22:17.826 --> 00:22:20.246
gonna make all my problems go away.

00:22:20.306 --> 00:22:25.397
They end up making them worse because,
yes, the AI will kiss your butt, it'll

00:22:25.426 --> 00:22:28.607
tell you you're right, it'll tell you
you have a great idea, even if you're

00:22:28.645 --> 00:22:34.466
like, "Hey, I think I'm gonna go take
over the world with, uh, a slingshot."

00:22:34.777 --> 00:22:35.687
"Yeah, you should do that.

00:22:35.746 --> 00:22:36.627
That's a great idea.

00:22:36.746 --> 00:22:37.706
I think you should do that."

00:22:37.806 --> 00:22:38.147
I'm likeâ¦

00:22:38.986 --> 00:22:44.047
So it's, it's fascinating to see
all these companies dive so heavy

00:22:44.107 --> 00:22:47.006
into this, thinking that it was
gonna fix all the problems, but

00:22:47.067 --> 00:22:48.766
it was not ever meant to do that.

00:22:48.806 --> 00:22:49.906
It was meant to augment.

00:22:50.647 --> 00:22:56.437
And so I augment my workflow, I would
say about 40% of the time, because I

00:22:56.446 --> 00:22:59.206
can do more than I could without it.

00:22:59.226 --> 00:23:01.236
And when we're talking like, oh,
let me go through and structure

00:23:01.306 --> 00:23:04.587
out everything and all that, like,
I'll, I'll just make the AI do that.

00:23:05.107 --> 00:23:08.766
But I still have to go back and check
it because what library did it use?

00:23:08.826 --> 00:23:09.547
What did it do here?

00:23:09.607 --> 00:23:10.966
What did it do there?

00:23:11.107 --> 00:23:13.607
Um, which is always the biggest
thing working at MSP Bots.

00:23:13.667 --> 00:23:16.167
It was one of the biggest things that
everybody looks at of, like, what

00:23:16.226 --> 00:23:19.107
third-party libraries are you using
when you're coding in your system?

00:23:19.547 --> 00:23:23.087
Because if one of those gets attacked,
it's, it's just an entryway into your app.

00:23:23.587 --> 00:23:25.906
And so data security
became just so prevalent.

00:23:25.926 --> 00:23:30.607
And so I get really paranoid in some
of the vibe coding in just using any

00:23:30.647 --> 00:23:34.226
of the AI stuff for specific functions.

00:23:34.266 --> 00:23:37.067
Like, I won't use it for anything
authe- authentication based.

00:23:37.147 --> 00:23:39.806
I won't use it for anything, like,
security based and that nature.

00:23:39.866 --> 00:23:44.766
But I will use it to check the security,
which is, is, it sounds weird, but it's

00:23:44.806 --> 00:23:47.946
like checks and balances of yourself.

00:23:48.971 --> 00:23:49.191
Todd Kane: Yep.

00:23:49.547 --> 00:23:49.846
Aarin: Um-

00:23:50.392 --> 00:23:52.591
Todd Kane: to that point,
like Mythos was like thatâ¦

00:23:52.892 --> 00:23:53.571
There was a lot ofâ¦

00:23:53.611 --> 00:23:56.872
I, I was talking about how like,
like Mythos is legit and like maybe

00:23:56.931 --> 00:24:01.192
it's AGI and it, uh, its impact on
security w- it was pretty dramatic.

00:24:01.312 --> 00:24:03.572
And I initially got a bunch of
pushback from people saying,

00:24:03.651 --> 00:24:07.431
"Oh, you know, like, GPT 3.5,

00:24:07.551 --> 00:24:09.591
they said they couldn't release
it because it was too dangerous.

00:24:09.691 --> 00:24:10.971
Like, this is a marketing tactic."

00:24:11.011 --> 00:24:12.171
I'm like, "No."

00:24:12.312 --> 00:24:15.951
Like I, I agree with what you're saying,
but if you look at the data, like

00:24:16.111 --> 00:24:18.851
it, it was able to find thousands and

00:24:19.118 --> 00:24:19.357
Aarin: Yeah

00:24:19.851 --> 00:24:22.251
Todd Kane: of vulnerabilities
in, in open source software.

00:24:22.291 --> 00:24:23.871
Like it was legit, right?

00:24:24.031 --> 00:24:25.131
So I, I, I

00:24:25.145 --> 00:24:25.886
Aarin: It's scary.

00:24:25.892 --> 00:24:27.011
Todd Kane: It's really scary.

00:24:27.051 --> 00:24:27.572
It's a totally

00:24:27.806 --> 00:24:28.426
Aarin: It's scary.

00:24:28.665 --> 00:24:30.246
And I read today that the, umâ¦

00:24:30.487 --> 00:24:33.346
Yeah, that's the other thing about,
like, the AI is just, like, how do

00:24:33.386 --> 00:24:37.185
we view the AI in the US is different
from how they would view it in China or

00:24:37.246 --> 00:24:40.726
different from how they would view it
in Russia from, you know, just business

00:24:40.806 --> 00:24:43.125
use cases, even down to environmentals.

00:24:43.165 --> 00:24:48.005
Like, we're more like, "Oh, let's not
go kill a bunch of water and power

00:24:48.065 --> 00:24:49.326
plants and build all this stuff."

00:24:49.366 --> 00:24:51.366
Like, we're protesting out there.

00:24:52.206 --> 00:24:54.926
They'll just keep building and building
and building, and some of that has been

00:24:54.985 --> 00:24:59.286
seen in the, in the manifest of the number
of attacks that have come across recently.

00:24:59.306 --> 00:25:02.587
And we just see more and more of
those AI attacks coming across and

00:25:02.665 --> 00:25:05.447
across and across, and they're just,
they're just Rolodexing, looking for

00:25:05.485 --> 00:25:08.886
those vulnerabilities, anyone they
can find, and then right in, and then

00:25:08.926 --> 00:25:10.585
somebody's gonna have a real bad day.

00:25:11.551 --> 00:25:11.671
Todd Kane: Yep.

00:25:12.711 --> 00:25:14.391
I mean, we won't, we won't sidetrack.

00:25:14.491 --> 00:25:17.191
This is something I, I probably
wanna have someone on to talk about,

00:25:17.452 --> 00:25:18.811
uh, to go a little deep on this.

00:25:18.952 --> 00:25:23.872
But like the, the, the whole idea that
like, uh, a data centers are gonna steal

00:25:23.952 --> 00:25:25.731
all the water and, and things like that.

00:25:25.771 --> 00:25:30.171
Like, we had this conversation on a, on
a group chat, um, that like, has anyone

00:25:30.571 --> 00:25:32.191
attacked the almond industry, right?

00:25:32.292 --> 00:25:34.471
Like see how much water they take, right?

00:25:34.531 --> 00:25:38.011
Like a lot of these fears I think
are misplaced in application.

00:25:38.051 --> 00:25:41.232
Like I get why people are fearful
of it, but I, and you, you see all

00:25:41.251 --> 00:25:42.812
these layoffs and stuff like that, and

00:25:42.969 --> 00:25:43.169
Aarin: Yeah

00:25:43.231 --> 00:25:45.952
Todd Kane: people that are coming
out of college are somewhat Right.

00:25:45.992 --> 00:25:47.771
in kind of having some hate on for AI.

00:25:48.152 --> 00:25:52.091
But I think sort of the, the why
is a maybe mi- misapplied and the

00:25:52.191 --> 00:25:55.171
actual impact that it will carry,
I think is misapplied as well.

00:25:55.381 --> 00:25:56.881
Aarin: I think the impact is huge.

00:25:57.001 --> 00:26:01.381
I was, I was talking to my wife's
cousins and, and they're 20 years

00:26:01.421 --> 00:26:04.921
old respectively in, in variances,
and their biggest concern is, "I

00:26:04.961 --> 00:26:06.023
don't feel like I need to save.

00:26:06.081 --> 00:26:09.102
I don't need to do anything because
AI is just gonna come get my job."

00:26:09.181 --> 00:26:12.002
And I'm like, "That's not how you
should be feeling at 20 years old."

00:26:12.631 --> 00:26:12.751
Todd Kane: Yeah.

00:26:13.192 --> 00:26:13.391
Yeah

00:26:13.762 --> 00:26:15.562
Aarin: And first off, it's
not coming to get your job.

00:26:15.602 --> 00:26:18.362
I mean, I think that's just another
far-fetch in the industry of just

00:26:18.401 --> 00:26:19.822
it's gonna replace all humans.

00:26:20.341 --> 00:26:22.042
Okay, well, what would humans do then?

00:26:22.241 --> 00:26:25.901
Like, that sounds like a very
dark dystopian future that

00:26:26.002 --> 00:26:27.002
I don't wanna be a part of.

00:26:27.721 --> 00:26:28.881
Can we get to Mars already?

00:26:29.675 --> 00:26:29.855
Todd Kane: Yep.

00:26:30.275 --> 00:26:32.835
Yeah, universal, uh,
universal, what is it?

00:26:32.895 --> 00:26:37.156
Not universal bacon, um, uh,
universal base income, universal,

00:26:38.181 --> 00:26:40.201
Aarin: Basic, yeah, universal basic income

00:26:40.616 --> 00:26:43.515
Todd Kane: Yeah, but there was a second
one that, uh, I'm blanking on the term,

00:26:43.735 --> 00:26:45.675
um, where it's, it's like a full version.

00:26:45.895 --> 00:26:46.515
Like, it's not like

00:26:46.618 --> 00:26:47.079
Aarin: Okay.

00:26:47.095 --> 00:26:48.235
Todd Kane: like 60K a year,

00:26:48.538 --> 00:26:49.578
Aarin: You just get a full paycheck

00:26:49.795 --> 00:26:51.595
Todd Kane: everyone gets like 160K a year.

00:26:51.975 --> 00:26:53.735
Uh, yeah, anyway, whatever that term is.

00:26:54.076 --> 00:26:58.735
All right, so, uh, yeah, we won't solve
the, the AI debate necessarily right now,

00:26:58.873 --> 00:26:59.573
Aarin: Not today.

00:27:00.243 --> 00:27:02.303
Speaker: Tired of fighting
the MSP fires alone?

00:27:02.513 --> 00:27:05.403
The Opsleader Pro group connects
service delivery professionals who

00:27:05.443 --> 00:27:07.033
understand your daily challenges.

00:27:07.303 --> 00:27:11.093
From KPIs and workflows to career
planning and team management, Opsleader

00:27:11.113 --> 00:27:12.803
Pro has systems for you to use.

00:27:13.303 --> 00:27:17.443
Join operations leaders from successful
MSPs who are sharing real solutions for

00:27:17.443 --> 00:27:21.653
managing client expectations, optimizing
service delivery, and making your service

00:27:21.653 --> 00:27:23.853
delivery team as effective as possible.

00:27:24.343 --> 00:27:27.923
Opsleader Pro, 'cause your service desk
deserves more than just survival mode.

00:27:28.363 --> 00:27:28.713
Visit opsleader.co.

00:27:28.713 --> 00:27:35.803
That's O-P-S leader dot C-O to
apply to join the public community.

00:27:35.879 --> 00:27:38.818
Todd Kane: so scaling, I, I think it's
interesting, like you noted, like you guys

00:27:39.519 --> 00:27:44.118
essentially doubled in volume with only,
uh, adding two additional headcounts, so

00:27:44.178 --> 00:27:51.258
like a, like a pretty, uh, asymmetric,
r- ratio for labor to, to work.

00:27:51.318 --> 00:27:54.359
Um, I mean, you would, y- I think
you would credit that to a lot of

00:27:54.418 --> 00:27:58.358
the work and the, the automation
work that you guys have done.

00:27:59.359 --> 00:28:01.598
where would you say is sort
of some of the highest impact?

00:28:01.618 --> 00:28:04.138
And, and maybe this is sort of a
twofold question of what did you

00:28:04.199 --> 00:28:08.718
find, and therefore what would you
reme- recommend people investigating

00:28:08.779 --> 00:28:11.438
within their business saying like,
"Well, shit, this sounds great.

00:28:11.538 --> 00:28:16.638
Aaron, you know, uh, was able to have
this huge impact on, on the business

00:28:16.699 --> 00:28:18.498
and how they manage the, the workflow."

00:28:18.938 --> 00:28:21.298
What are the areas that you
found the most value in?

00:28:21.379 --> 00:28:25.318
Um, you know, triage probably, um,
being a, a big component of that.

00:28:25.338 --> 00:28:29.358
What are the other areas that,
that were a really good, uh, source

00:28:29.419 --> 00:28:30.798
for you guys to automate work?

00:28:32.617 --> 00:28:32.858
Aarin: Yeah.

00:28:32.877 --> 00:28:36.317
The biggest thing came down
to having a really detailed,

00:28:36.537 --> 00:28:38.994
um System across the board.

00:28:39.134 --> 00:28:42.154
I mean, between, you know, the
vCIOs, the projects team, we

00:28:42.214 --> 00:28:45.494
have a field team, we have a help
desk, we have a central services.

00:28:45.574 --> 00:28:49.594
Not every single one of those teams even
existed when I started a few years ago.

00:28:49.734 --> 00:28:53.234
Um, when I started, there
really wasn't much of a coherent

00:28:53.294 --> 00:28:54.833
system that was kind of there.

00:28:54.894 --> 00:28:57.654
Like, they had systems in place,
but there wasn't anything that

00:28:57.674 --> 00:28:59.614
really tied stuff together.

00:28:59.654 --> 00:29:03.624
And, and so I looked at it and saying,
"How do we tie all these things together?

00:29:04.504 --> 00:29:08.794
Let's make it simple for the, simple for
the employee, uh, easy for me to, to kind

00:29:08.814 --> 00:29:13.094
of have visibility into, and that it turns
over really good results for the client."

00:29:13.874 --> 00:29:17.564
And so as we went through our, our entire
system, we started really just gutting

00:29:17.634 --> 00:29:21.494
everything and rebuilding it because
I'm really kind of OCD about that.

00:29:21.534 --> 00:29:24.794
Like, everything needs to
function in a specific way.

00:29:25.454 --> 00:29:29.854
And that's not uncommon, but I think
the layer that I took it to, the

00:29:29.914 --> 00:29:33.694
granularity that I stepped into is a
lot different than what most people do.

00:29:34.234 --> 00:29:36.114
They kind of scratch that
surface level and then they're

00:29:36.154 --> 00:29:37.014
like, "Okay, that's good enough.

00:29:37.074 --> 00:29:37.834
Let's move on."

00:29:37.874 --> 00:29:40.574
And it's like, okay, well, that
may be good enough for one to three

00:29:40.634 --> 00:29:43.814
million dollars, but that's not gonna
carry you past three million dollars.

00:29:44.214 --> 00:29:47.654
Once you get past that stage, you start
talking about a different maturity model

00:29:47.714 --> 00:29:49.194
for your businesses that is needed.

00:29:49.874 --> 00:29:52.574
Um, and therefore, your policies
have to evolve in some of that.

00:29:52.624 --> 00:29:56.974
And so having some of those granular
policies and playbooks that say, "This

00:29:57.034 --> 00:30:00.834
is what happens, when it happens,
and how it happens," has been the

00:30:00.874 --> 00:30:02.464
biggest lifesaver of anything.

00:30:02.554 --> 00:30:04.764
Because at the end of the day,
we're still a people business.

00:30:04.834 --> 00:30:06.194
We still have people to support.

00:30:06.654 --> 00:30:08.474
I still have people that call
up and say, "Hey, I wanna

00:30:08.514 --> 00:30:09.894
talk to a tier two right now."

00:30:10.514 --> 00:30:13.413
No automation in the world
is gonna fix or solve that.

00:30:13.454 --> 00:30:14.794
They want a human.

00:30:14.854 --> 00:30:20.034
By having really good finite documentation
and playbooks, it, it really helps figure

00:30:20.134 --> 00:30:22.094
out, okay, where is everything running?

00:30:22.794 --> 00:30:23.034
Good.

00:30:23.214 --> 00:30:24.174
Everything runs great there.

00:30:24.334 --> 00:30:26.714
Now let's take it in reverse and
look at what doesn't run great.

00:30:26.754 --> 00:30:27.834
Let's look for the anomalies.

00:30:27.894 --> 00:30:28.454
What sucks?

00:30:28.554 --> 00:30:29.054
What's bad?

00:30:29.134 --> 00:30:29.794
What's terrible?

00:30:30.194 --> 00:30:31.294
Let's focus on that.

00:30:31.694 --> 00:30:34.634
And so we shifted focus in
just saying, "Good is good.

00:30:34.734 --> 00:30:35.674
We know good is good.

00:30:36.134 --> 00:30:37.034
Let's look at bad."

00:30:37.054 --> 00:30:40.524
And so our whole life for the last year
has just been living in what is the bad?

00:30:40.554 --> 00:30:41.214
Where is the bad?

00:30:41.254 --> 00:30:41.934
Where's the problem?

00:30:41.974 --> 00:30:42.644
Where's the problem?

00:30:42.654 --> 00:30:46.254
And it may not be something huge
like, oh, the house is on fire.

00:30:46.294 --> 00:30:51.174
Sometimes it's like something stupid like,
oh yeah, our dispatching automation wasn't

00:30:51.294 --> 00:30:54.354
kicking off, or something happened like
it wasn't tagging a ticket correctly.

00:30:54.894 --> 00:30:56.574
Okay, let's go do this and this and this.

00:30:56.694 --> 00:31:01.074
So as we start to build more stuff
on top of that, it kind of grew.

00:31:01.134 --> 00:31:04.374
But without that base foundation, we
never would have gotten off the ground.

00:31:04.864 --> 00:31:07.974
And that's pretty much the biggest
key component to everything.

00:31:08.034 --> 00:31:08.594
It's evenâ¦

00:31:08.674 --> 00:31:10.734
You can't dispatch
anything without a roadmap.

00:31:11.234 --> 00:31:13.514
You gotta have a blueprint of
some-- or sorry, not dispatch.

00:31:13.614 --> 00:31:17.274
Automate without some sort of
blueprint, some sort of document

00:31:17.284 --> 00:31:19.674
that says, "This is what I'm building
and this is how I'm building it."

00:31:19.683 --> 00:31:24.004
And if that doesn't exist in your
operations today, putting that automation

00:31:24.054 --> 00:31:26.854
in and saying, "This is how it's gonna
work," isn't gonna fix that problem.

00:31:27.354 --> 00:31:29.974
You're still gonna-- You're probably
gonna have more problems after you get

00:31:30.014 --> 00:31:33.594
done with that that you don't know how
to fix because you implemented something

00:31:33.614 --> 00:31:37.810
without knowing what the outcome is gonna
be Which is a huge part of anything, of

00:31:37.889 --> 00:31:41.889
just what is the outcome of what we're
doing, what we're trying to accomplish.

00:31:42.570 --> 00:31:45.870
And so we've kinda tried to keep that
mentality as we go through and build

00:31:45.909 --> 00:31:49.668
all this stuff, but that foundation has
been always near and dear to my heart.

00:31:50.109 --> 00:31:53.229
Uh, which is why, you know, when we
were talking a few years ago, I sent

00:31:53.289 --> 00:31:56.708
you so many documents, and I'm like,
"Here, here, here's 1,000 documents."

00:31:56.750 --> 00:32:00.609
I'm And you're probably like,
"Whoa, this guy's nuts."

00:32:01.135 --> 00:32:03.974
Todd Kane: friends, Aaron, because
the I, I think this, this is an

00:32:04.055 --> 00:32:05.994
unexpected answer, I would think.

00:32:06.034 --> 00:32:08.194
Like, uh, like if anyone would
have guessed, like, what you

00:32:08.234 --> 00:32:11.655
would say if I asked you that,
it wasn't good documentation and

00:32:11.734 --> 00:32:13.294
procedural understanding, right?

00:32:13.334 --> 00:32:15.735
Like, that's not the automatic
answer when people are like,

00:32:16.114 --> 00:32:17.094
"How do you automate something?"

00:32:17.174 --> 00:32:19.475
It's like, "Good documentation
to understand the process."

00:32:19.594 --> 00:32:22.374
Like, wait, wait, where's
the cool techy stuff?

00:32:22.555 --> 00:32:25.874
Also, I, I think that's an incredibly
important base layer, is what

00:32:25.961 --> 00:32:26.141
Aarin: Yeah

00:32:26.234 --> 00:32:27.475
Todd Kane: actually trying to achieve?

00:32:27.555 --> 00:32:30.815
What's the end goal, and how do
we actually achieve that and then

00:32:30.894 --> 00:32:32.475
iterate the process internally?

00:32:32.774 --> 00:32:35.675
Once you have a good process, then
you can automate it, and I think

00:32:35.714 --> 00:32:38.074
that's where people kind of go
sideways on this, is they're trying

00:32:38.094 --> 00:32:41.675
to automate a procedure that doesn't
really exist in the first place,

00:32:41.812 --> 00:32:42.493
Aarin: Absolutely.

00:32:42.594 --> 00:32:44.135
Todd Kane: it's good and
it produces a good result?

00:32:44.174 --> 00:32:46.475
Like, uh, let's just keep
stabbing at it, basically, right?

00:32:46.953 --> 00:32:47.273
Aarin: Yeah.

00:32:48.013 --> 00:32:48.133
Yeah.

00:32:48.313 --> 00:32:51.393
And I've been fortunate enough to
where because we have gottenâ¦

00:32:51.433 --> 00:32:53.893
I mean, when I came in, we were
taking in, I don't know, somewhere

00:32:53.913 --> 00:32:55.553
around 100, 120 tickets a day.

00:32:56.213 --> 00:32:58.973
Um, we've since now, we
take in maybe 20 a day.

00:32:59.053 --> 00:33:01.373
Um, so the, the volume of
everything has gone down.

00:33:01.573 --> 00:33:05.513
Some of it's also, like, just fixing
the business and getting everything into

00:33:05.593 --> 00:33:09.133
where we want it to go and how we want
it to go, lining that up with what is our

00:33:09.213 --> 00:33:12.533
vision and our EOS say that we wanna do,
where do we wanna go with all this stuff?

00:33:13.013 --> 00:33:16.313
And then taking, you know, what Eric is,
is, you know, him being the visionary of

00:33:16.354 --> 00:33:17.653
saying, "Hey, here's where I wanna go."

00:33:17.713 --> 00:33:21.153
And then it's my job to kinda
say, "Okay, you know, I likeâ¦

00:33:21.173 --> 00:33:22.493
You know, you gave me 1,000 ideas.

00:33:22.813 --> 00:33:23.693
900 of them are great.

00:33:23.734 --> 00:33:26.273
I'm gonna ignore this other 100 and
hope you don't kill me for them.

00:33:26.333 --> 00:33:28.513
But let's go focus on these 900."

00:33:29.034 --> 00:33:31.053
Um, and so you take all this
stuff and put it together.

00:33:31.899 --> 00:33:32.438
Todd Kane: so yeah.

00:33:32.673 --> 00:33:33.093
Aarin: It is.

00:33:33.194 --> 00:33:34.034
It is.

00:33:34.133 --> 00:33:35.714
Uh, it's also learning when to say no.

00:33:36.438 --> 00:33:37.158
Todd Kane: Yes, yeah.

00:33:37.513 --> 00:33:39.033
" Aarin: No, we can't do that today."

00:33:39.698 --> 00:33:41.538
Todd Kane: but that, that's a
really important aspect as well.

00:33:41.618 --> 00:33:45.118
Like, uh, the vision- the visionary
and integrator relationship is,

00:33:45.299 --> 00:33:49.158
I think, too often integrators
are afraid to say no, right?

00:33:49.398 --> 00:33:50.039
Uh, because they're like,

00:33:50.153 --> 00:33:50.353
Aarin: Yeah

00:33:50.498 --> 00:33:51.938
Todd Kane: you know, that's
what the owner told me.

00:33:51.978 --> 00:33:55.018
Like, I, I, I don't, I don't
necessarily own this place," right?

00:33:55.158 --> 00:33:58.878
A lot of, uh, integrators and
operators are not necessarily owners.

00:33:58.919 --> 00:34:02.819
They can be, but in a lar- large
majority, I don't think they are, and

00:34:02.858 --> 00:34:06.238
that, that's a difficult dynamic of
being able to sort of politely and

00:34:06.279 --> 00:34:09.438
professionally put back and push back
and say, "I hear what you're saying.

00:34:10.119 --> 00:34:13.558
I, like, are you okay if I pick these
three and I'm gonna drop the rest?"

00:34:13.619 --> 00:34:13.798
Right?

00:34:13.908 --> 00:34:14.269
Aarin: All

00:34:14.498 --> 00:34:16.338
Todd Kane: that feels like a
dangerous conversation when

00:34:16.358 --> 00:34:18.318
it's entirely practical, right

00:34:19.060 --> 00:34:19.681
Aarin: Well, it should be.

00:34:19.781 --> 00:34:22.781
I think that's majority of
the problem across, acrossâ¦

00:34:22.880 --> 00:34:27.600
You know, if we look at why can't an
MSP grow, it's, it's likely something to

00:34:27.661 --> 00:34:31.982
do with something, somebody at the top
has hit a lid some way, shape, or form.

00:34:32.041 --> 00:34:34.841
Like, they can't get out of their
own way to allow the company to grow.

00:34:34.902 --> 00:34:36.940
That's why they say getting
off of owner-led sales is

00:34:37.002 --> 00:34:38.020
the hardest thing to do.

00:34:38.621 --> 00:34:41.180
It's, it's, it's a hard thing
to do, and I don't blame them.

00:34:41.201 --> 00:34:43.301
I mean, from the visionary end,
it's like, this is their baby.

00:34:43.360 --> 00:34:44.541
They built this bad boy.

00:34:44.581 --> 00:34:46.281
This is everything to them.

00:34:46.841 --> 00:34:47.982
Companies have to grow.

00:34:48.060 --> 00:34:50.440
Companies have to be healthy, and
we always have to consider what

00:34:50.482 --> 00:34:53.600
that, uh, that outcome is gonna be,
whether it's good or it's bad, no

00:34:53.640 --> 00:34:55.220
matter what layer it comes from.

00:34:55.241 --> 00:34:58.201
And, and I've been really lucky
that Eric's been a great, great

00:34:58.261 --> 00:34:59.581
mentor, and he's been a great friend.

00:34:59.600 --> 00:35:02.081
And, and it's kind of just we hear
each other when we're talking,

00:35:02.121 --> 00:35:04.662
and we're going through all these
processes, and it's like, "Hey, what

00:35:04.682 --> 00:35:06.140
do we actually wanna get through?

00:35:06.261 --> 00:35:07.201
Like, get out of this."

00:35:07.261 --> 00:35:11.361
And, and when we sit down and line
it out, we're pretty much identical.

00:35:11.381 --> 00:35:14.381
And it got really scary because
we used to think so much alike

00:35:14.461 --> 00:35:15.881
I wouldn't have to talk to him.

00:35:16.520 --> 00:35:19.982
Um, and I feel like that's a really
great VI dynamic to be able to have

00:35:20.020 --> 00:35:22.961
that sort of sync, but it doesn't
mean that we're always in sync.

00:35:23.001 --> 00:35:25.781
There were definitely periods
where it was like, "Okay, hold on.

00:35:25.821 --> 00:35:27.541
This or this or this."

00:35:27.600 --> 00:35:30.742
Um, but as you get through those, some
of those, those things and start to work

00:35:30.781 --> 00:35:34.421
through it, you get stronger as a, as a
dynamic, and you build something that's

00:35:34.482 --> 00:35:38.081
really impenetrable when you look at
it from can something bring this down?

00:35:38.162 --> 00:35:41.001
No, not if our dynamic
is actually working.

00:35:41.100 --> 00:35:44.220
Because if it's working up
top, it'll work down below

00:35:45.263 --> 00:35:45.383
Todd Kane: Yeah

00:35:45.603 --> 00:35:49.963
I think this is a, an important aspect,
I agree, of like the professional dynamic

00:35:50.043 --> 00:35:54.983
of being able to disagree professionally
and still align on we're trying to

00:35:55.043 --> 00:35:56.563
achieve the same, the same thing.

00:35:56.603 --> 00:35:57.913
We disagree on approach.

00:35:58.343 --> 00:36:02.013
Let's kinda talk about that, and at
some point I may go, "You know what?

00:36:02.063 --> 00:36:05.083
I don't necessarily disagree, but
I understand sort of why we're

00:36:05.103 --> 00:36:07.623
making this decision, and we're
gonna run forward with this."

00:36:07.763 --> 00:36:09.563
And I'm not gonna say,
"Hey, I told you so.

00:36:09.643 --> 00:36:10.623
I told you this wasn't gonna work."

00:36:10.683 --> 00:36:12.143
It's like, "Ugh, okay, we tried this.

00:36:12.303 --> 00:36:12.683
Didn't work.

00:36:12.723 --> 00:36:14.043
Like, let's go in a different direction.

00:36:14.083 --> 00:36:14.423
That cool?

00:36:14.543 --> 00:36:14.703
Cool."

00:36:15.183 --> 00:36:15.373
Right?

00:36:15.423 --> 00:36:20.173
Like, like I think people make massive
mountains out of molehills in all

00:36:20.183 --> 00:36:24.292
of these subtle sort of disagreement
dynamics between, uh, a visionary and

00:36:24.323 --> 00:36:28.823
an inter-integrator, when as far as I'm
concerned, like that's necessary, right?

00:36:28.903 --> 00:36:31.883
Like I often joke, you've heard
me say this in meetings, is a

00:36:31.943 --> 00:36:34.963
meeting without a little drama is
not a meeting worth having, right?

00:36:35.003 --> 00:36:39.523
Like there has to be enough disagreement
for you to align on and push back and

00:36:39.583 --> 00:36:45.252
have sort of the, the, uh, that subtle
disagreement, uh, on approach that there's

00:36:45.303 --> 00:36:48.923
other people are heard, and there's other
dynamics and other voices in the room.

00:36:48.983 --> 00:36:51.693
That's the point of, of those
discussions and having that

00:36:51.797 --> 00:36:52.037
Aarin: Yeah

00:36:52.103 --> 00:36:52.903
Todd Kane: different perspective.

00:36:53.283 --> 00:36:56.483
Because to your point, like if we
align on everything, we're, like

00:36:56.523 --> 00:36:57.743
there's no point in having a meeting

00:36:57.769 --> 00:36:58.729
Aarin: Nothing's gonna get done.

00:36:59.083 --> 00:37:00.043
Todd Kane: yeah, like we all agree.

00:37:00.123 --> 00:37:02.083
It's like, like, okay, we're
gonna talk about this thing.

00:37:02.143 --> 00:37:02.823
Yeah, yeah, sounds good.

00:37:02.843 --> 00:37:04.133
Okay, well, why are we here, right?

00:37:04.163 --> 00:37:05.873
Like this absolutely could've
been an email, right?

00:37:06.685 --> 00:37:07.085
Aarin: Yep.

00:37:07.643 --> 00:37:08.403
Todd Kane: Yeah.

00:37:08.443 --> 00:37:08.643
All right.

00:37:08.743 --> 00:37:08.883
So

00:37:09.325 --> 00:37:09.546
Aarin: Yeah

00:37:09.763 --> 00:37:12.683
Todd Kane: what, another piece I
wanted to, to hit on here is, uh,

00:37:12.843 --> 00:37:18.003
sort of user-facing versus, um,
versus backend automations, right?

00:37:18.103 --> 00:37:23.653
So, um, I'm curious to you, uh, how
you think about what the, the, the

00:37:23.803 --> 00:37:27.903
backend automation, how, like how
much of what you do is just purely

00:37:27.963 --> 00:37:31.723
underground plumbing mechanics,
uh, is, is invisible to everyone.

00:37:31.753 --> 00:37:36.063
It does some fancy stuff and produces
something eventually for either an

00:37:36.103 --> 00:37:41.133
end user or an internal, um, um,
uh, sort of member of the company.

00:37:41.133 --> 00:37:46.523
And what I'm thinking about here
is like how does AI and automation

00:37:46.563 --> 00:37:51.123
continue to show up for both the
end users as well as the internal

00:37:51.263 --> 00:37:52.963
users within the company, right?

00:37:53.083 --> 00:37:57.403
Like you mentioned the VCIOs, and
we're starting to see a lot more, uh,

00:37:57.583 --> 00:38:02.563
automation, data collection, and AI
enablement for, for the VCIO group.

00:38:03.803 --> 00:38:07.763
um, I'm struggling to wrap this
into a consolidated question, but I

00:38:07.783 --> 00:38:08.903
think you know where I'm going here.

00:38:09.321 --> 00:38:10.661
Aarin: Yeah, no, absolutely.

00:38:11.663 --> 00:38:14.683
Todd Kane: th- the, yeah, the, uh,
the underground backend mechanics

00:38:14.930 --> 00:38:15.369
Aarin: Yeah

00:38:15.403 --> 00:38:18.923
Todd Kane: user-facing interactions
with the automations and the AI.

00:38:18.963 --> 00:38:21.003
What, what's, what's sort of
your take on that dynamic?

00:38:22.165 --> 00:38:24.365
Aarin: No, this has been
actually pretty funny.

00:38:24.705 --> 00:38:28.645
Funnily enough, been pretty, uh, hot
recently on the topic as we kinda go

00:38:28.665 --> 00:38:32.886
through stuff of just client-facing
versus the plumbing, and I think it, it

00:38:32.926 --> 00:38:37.665
kinda sparked off of, um, funny enough,
watching the Super Bowl and, and seeing

00:38:37.705 --> 00:38:41.465
that almost every single ad was AI, and
by the end of it I just wanted to throw

00:38:41.506 --> 00:38:42.845
up 'cause I'm just like, "I'm done.

00:38:43.145 --> 00:38:43.785
I'm done with this.

00:38:43.846 --> 00:38:44.245
I don't wannaâ¦

00:38:44.365 --> 00:38:46.426
I-- Where's the funny
Budweiser commercials?"

00:38:46.665 --> 00:38:47.885
Like, what happened to us?

00:38:48.002 --> 00:38:49.642
Todd Kane: ads were pretty
funny though, like poking

00:38:49.805 --> 00:38:50.086
Aarin: The,

00:38:50.323 --> 00:38:50.682
Todd Kane: GPD

00:38:50.926 --> 00:38:51.225
Aarin: it'sâ¦

00:38:51.926 --> 00:38:52.965
That's about it, though.

00:38:53.006 --> 00:38:55.345
Like, it's, it's everything
else was so fake.

00:38:55.385 --> 00:38:59.606
And so as we started to go through, I
started to notice that, you know, what

00:38:59.645 --> 00:39:02.064
is people's reception to AI gonna be?

00:39:02.145 --> 00:39:05.885
Because, you know, my dad
is, is very, we'll say, uh,

00:39:06.045 --> 00:39:07.865
stuck in 1950, we'll call it.

00:39:08.545 --> 00:39:10.545
So he just got his first iPhone last year.

00:39:10.564 --> 00:39:12.064
He's had a flip phone up until then.

00:39:12.524 --> 00:39:15.385
Um, I mean, it's, it's
crazy how much he livesâ¦

00:39:15.465 --> 00:39:18.086
Yeah, never- doesn't email,
doesn't computer, doesn't

00:39:18.106 --> 00:39:19.024
believe any of that stuff.

00:39:19.106 --> 00:39:22.805
I, I'm surprised he has a debit
card instead of just a checkbook.

00:39:22.885 --> 00:39:23.185
So

00:39:23.291 --> 00:39:25.490
Todd Kane: up to be such a nerd
coming from that lineage then?

00:39:26.290 --> 00:39:27.908
Aarin: It's, uh, it's, it's, umâ¦

00:39:28.269 --> 00:39:31.269
I was a wild child and,
um, yeah, I don't know.

00:39:31.349 --> 00:39:35.874
I got really into it Well, I
started off in film, surprisingly

00:39:35.913 --> 00:39:38.514
enough, and then when I got bored of
that, I was like, you know, I'mâ¦

00:39:38.714 --> 00:39:41.744
My grandfather was really into
computers, so I think it kinda just was,

00:39:42.138 --> 00:39:42.378
Todd Kane: Same

00:39:42.474 --> 00:39:44.834
Aarin: just took over and just ended
up being one of those things to where

00:39:44.894 --> 00:39:46.314
I realized I'm really good at it.

00:39:46.434 --> 00:39:47.413
So, like, what am I doing?

00:39:47.494 --> 00:39:51.094
Like, am I really gonna go make a
blockbuster hit in the middle of Oklahoma?

00:39:51.434 --> 00:39:52.754
Probably not.

00:39:52.874 --> 00:39:55.654
Um, so that just kinda
died on the vine there.

00:39:55.694 --> 00:39:57.394
But, um,

00:39:58.062 --> 00:39:58.643
Todd Kane: Or I derailed

00:39:58.674 --> 00:39:58.894
Aarin: no.

00:39:59.913 --> 00:40:00.654
Yeah, you derailed me.

00:40:00.774 --> 00:40:02.394
Now I forgot where we
were going with all this.

00:40:02.582 --> 00:40:03.863
Todd Kane: internal versus us-

00:40:04.154 --> 00:40:04.574
Aarin: Yes.

00:40:04.682 --> 00:40:05.382
Todd Kane: backend versus,

00:40:05.453 --> 00:40:05.754
Aarin: So

00:40:06.282 --> 00:40:06.423
Todd Kane: yeah

00:40:06.754 --> 00:40:09.473
Aarin: yeah, it became like
this, this, this kind ofâ¦

00:40:10.214 --> 00:40:12.784
When we were talking with our clients,
they started to get frustrated, and

00:40:12.794 --> 00:40:14.154
they're like, "I don't like this AI."

00:40:14.214 --> 00:40:15.913
And I'm like, "Well, what
about it don't you like?"

00:40:16.484 --> 00:40:17.994
They're like, "I don't like
that it's talking to me."

00:40:18.034 --> 00:40:19.453
And I'm like, "Iâ¦

00:40:20.014 --> 00:40:20.354
Wait."

00:40:21.323 --> 00:40:21.834
They're like, "Am Iâ¦

00:40:22.034 --> 00:40:24.744
Is it talking to you, or is
it saying something wrong?

00:40:24.754 --> 00:40:27.774
Like, explain this a little bit more
to me about what you're saying."

00:40:27.814 --> 00:40:30.094
And they're like, "Well, it
just says some weird stuff."

00:40:30.154 --> 00:40:34.014
And as we started to go through some of
the systems, we realized the AI had been

00:40:34.034 --> 00:40:39.794
hallucinating and sending out random
public-facing notes just at random to

00:40:39.854 --> 00:40:41.794
just random people about random things.

00:40:41.894 --> 00:40:43.834
Uh, it didn't even have
to do with the ticket.

00:40:44.184 --> 00:40:46.734
And I'm just like, "Okay,
that's concerning."

00:40:47.394 --> 00:40:51.524
Um, so we kinda reshaped our strategy
and, and really the only time that AI hits

00:40:51.594 --> 00:40:55.104
a client-facing ticket is that initial
triage bot and then a reminder bot.

00:40:55.604 --> 00:40:58.474
All the other AI is, is
completely on the back end.

00:40:58.534 --> 00:41:03.014
It faces either the techs or it just
functions on the back end autonomously.

00:41:03.054 --> 00:41:06.044
We've tried to break away from just
shoving so much down our clients'

00:41:06.114 --> 00:41:09.714
throats because we've learned
from past events like security.

00:41:10.304 --> 00:41:13.274
And having gone through security
becoming a thing and a big push in

00:41:13.314 --> 00:41:16.574
the industry, the more we shoved it
down people's throats, the more they

00:41:16.614 --> 00:41:18.493
got frustrated, hated us, and left.

00:41:19.094 --> 00:41:23.594
Um, I've got something like a 95% client
retention rate over the last two years.

00:41:23.654 --> 00:41:25.854
Like, we've lost two clients
over the last two years.

00:41:26.554 --> 00:41:29.194
Um, and those were clients that
had already left and came back and

00:41:29.214 --> 00:41:31.274
left again, but it was all pricing.

00:41:31.894 --> 00:41:35.534
And so it's, it's people
want to be treated fairly.

00:41:35.614 --> 00:41:38.214
They don't wanna have a bunch of
stuff shoved down their throat.

00:41:38.254 --> 00:41:40.254
They don't wanna be told
what to do all the time.

00:41:40.314 --> 00:41:41.974
Like, it becomes a partnership.

00:41:42.014 --> 00:41:46.114
And so I look at it in that regard of
just I don't wanna put any more AI down

00:41:46.124 --> 00:41:48.234
their throats than they're able to handle.

00:41:48.374 --> 00:41:50.374
Otherwise, they're just
gonna go somewhere else.

00:41:51.234 --> 00:41:57.814
And the downfall of that is not everybody
in the MSP can or is implementing

00:41:57.874 --> 00:42:02.294
AI in any capacity, and it's just as
easy, if not easier, to find a, a, an

00:42:02.374 --> 00:42:06.134
MSP that doesn't do any of that stuff
than it is to find one that actually

00:42:06.274 --> 00:42:08.314
is fully all into that at this point.

00:42:08.674 --> 00:42:10.894
We haven't fully made that
swing or that adoption.

00:42:11.034 --> 00:42:16.154
So it does play a huge factor of
just how much do I actually do and

00:42:16.194 --> 00:42:17.814
how far do I actually take this?

00:42:18.134 --> 00:42:19.993
But for my guys, I mean, we're all nerds.

00:42:20.334 --> 00:42:21.354
We all joke about it.

00:42:21.534 --> 00:42:24.654
Um, I've turned the AI off for
them when they've complained.

00:42:25.174 --> 00:42:27.033
Um, and they're like, "Whoa,
bro, this is too much."

00:42:27.094 --> 00:42:28.325
And then I get it.

00:42:28.345 --> 00:42:31.685
Sometimes when it's like every 10
minutes and it's reminding you of

00:42:31.725 --> 00:42:34.666
something or it's doing this, like
it could be a little distractive.

00:42:35.265 --> 00:42:37.545
So we've learned to tune it
on the back end even as well.

00:42:37.785 --> 00:42:39.984
But it's just kinda case by case

00:42:40.603 --> 00:42:40.693
Todd Kane: Yeah

00:42:40.823 --> 00:42:42.323
it can be quite overwhelming, right?

00:42:42.363 --> 00:42:42.903
Like even when

00:42:42.961 --> 00:42:43.180
Aarin: Yeah

00:42:43.512 --> 00:42:47.343
Todd Kane: I, I'm working on a project
with, with AI and like I'm asking it

00:42:47.383 --> 00:42:50.963
for something and then it gives me
like just this massive mountain of

00:42:51.023 --> 00:42:52.983
work to do and I'm like, know what?

00:42:53.283 --> 00:42:54.603
Maybe this isn't that important to me,"

00:42:54.753 --> 00:42:56.673
Aarin: That's why I
asked you to do this, AI.

00:42:57.463 --> 00:42:58.123
Todd Kane: Yeah, exactly.

00:42:58.743 --> 00:42:59.983
Um, yeah.

00:43:00.043 --> 00:43:02.563
Okay, um, other piece I
wanted to ask about this?

00:43:03.223 --> 00:43:05.703
Um, uh, now I'm blanking out.

00:43:05.763 --> 00:43:06.403
Oh, yes.

00:43:06.543 --> 00:43:09.803
The, um, so the other aspect I, I
find fascinating and I'd love your

00:43:09.843 --> 00:43:12.923
input on this, is, is, uh, voice AI.

00:43:13.263 --> 00:43:16.483
and like I've seen a, a number of
companies experimenting with this

00:43:16.583 --> 00:43:21.283
where like call answer is actually
done by AI and this is incredibly

00:43:21.423 --> 00:43:24.063
polarizing for people, uh, for
the reason that you're noting.

00:43:24.143 --> 00:43:24.723
Like some people are

00:43:24.733 --> 00:43:24.933
Aarin: Yeah

00:43:25.143 --> 00:43:27.483
Todd Kane: "I, like, like
screw off with this AI thing.

00:43:27.543 --> 00:43:28.463
I don't wanna talk to this.

00:43:28.503 --> 00:43:29.203
Like give me a human."

00:43:30.083 --> 00:43:33.573
but I can't figure out exactly what
it Is Originally I assumed it was

00:43:33.583 --> 00:43:38.203
gonna be generational where like, you
know, sort of 50 plus type thing like

00:43:38.243 --> 00:43:41.283
they don't wanna talk to an AI but
like the 20s like they don't e- they

00:43:41.303 --> 00:43:42.883
don't wanna talk to a person, right?

00:43:42.963 --> 00:43:44.183
So like maybe it was generational.

00:43:44.503 --> 00:43:46.703
That is actually not the
split that I'm seeing.

00:43:46.763 --> 00:43:50.783
I'm seeing it more on just sort of a
client base by client base difference

00:43:51.183 --> 00:43:55.943
where I know this one organization they
went to completely no human interaction

00:43:56.123 --> 00:43:58.003
with, you know, ticket ingestion, right?

00:43:58.063 --> 00:44:02.483
Like tickets are submitted entirely
digitally, uh, either by the phone or

00:44:02.543 --> 00:44:08.403
by, by email or, or chat and no humans
accept incoming tickets and I was like,

00:44:08.673 --> 00:44:09.473
Aarin: Is this Xfinity?

00:44:09.603 --> 00:44:09.963
Todd Kane: with this."

00:44:10.693 --> 00:44:11.653
Aarin: Are we talking about Xfinity?

00:44:12.303 --> 00:44:12.733
Todd Kane: No, no, no.

00:44:12.733 --> 00:44:13.583
Well, yeah,

00:44:13.693 --> 00:44:14.872
Aarin: not the internet provider.

00:44:15.133 --> 00:44:16.412
It's definitely not Xfinity

00:44:16.583 --> 00:44:21.463
Todd Kane: are, they are an, they are an
MSP, and they, they've had zero pushback.

00:44:21.503 --> 00:44:23.823
Like they've had a few people that
are like, "Hey, what is this?"

00:44:23.983 --> 00:44:25.023
Uh, like, "Is this legit?"

00:44:25.083 --> 00:44:27.343
And like then they're like,
"Okay, cool, whatever," and they,

00:44:27.483 --> 00:44:28.483
it's gone really well for them.

00:44:28.613 --> 00:44:28.743
And I

00:44:28.853 --> 00:44:29.473
Aarin: That's good

00:44:29.623 --> 00:44:33.733
Todd Kane: nec-necessarily the case for
everybody so, uh, you know, I'm, I'm,

00:44:33.733 --> 00:44:37.593
I'm sort of curious how this plays out
to your point of like we can't push this

00:44:37.663 --> 00:44:41.393
on people that are not necessarily ready
for it and like we're barely getting

00:44:41.423 --> 00:44:46.183
past the point of convincing some owners
that like live answer isn't as important

00:44:46.263 --> 00:44:48.803
as they think it was or think it is.

00:44:48.943 --> 00:44:51.813
You know, as, uh, like 10 years
ago you wanted live answer and they

00:44:51.843 --> 00:44:55.323
can't get past the fact that like,
no if you call someone back within 10

00:44:55.363 --> 00:44:58.963
minutes just as good but that's really
difficu-difficult to convince people.

00:44:59.443 --> 00:45:03.523
So you know as AI starts to show up
in a lot of these other places in more

00:45:03.563 --> 00:45:08.113
of a user-facing capacity I think it's
gonna be incredibly variable on how

00:45:08.123 --> 00:45:12.103
successful It's gonna be for no parameters
that actually make a lot of sense.

00:45:12.123 --> 00:45:12.623
What are your thoughts?

00:45:13.910 --> 00:45:15.750
Aarin: It's easy to reduce
labor in that avenue.

00:45:15.810 --> 00:45:17.790
I think you can make some
really good justifications,

00:45:17.850 --> 00:45:19.330
like you said, client by client.

00:45:19.590 --> 00:45:22.410
Um, you know, it's, it's
back to my Xfinity joke.

00:45:22.470 --> 00:45:25.560
I mean, uh, it is something that, you
know, for myself personally, when I

00:45:25.569 --> 00:45:28.970
call Comcast, which is a, a majorâ¦

00:45:29.029 --> 00:45:32.250
One of the main internet providers
across the United States, there's like

00:45:32.290 --> 00:45:35.350
three of them or something like that,
and then a bunch of other smaller ones.

00:45:35.430 --> 00:45:37.350
But it's AI.

00:45:37.470 --> 00:45:39.010
I, I get a bot every single time.

00:45:39.050 --> 00:45:41.430
I have to jump through hoops to
try to get support, and I'm like,

00:45:41.529 --> 00:45:43.100
"I just wanna talk aboutâ¦"

00:45:43.430 --> 00:45:45.870
You know, maybe it's like my
speed is slow and I wanna upgrade.

00:45:45.910 --> 00:45:48.010
Like, I wanna give you more
money and you're making me

00:45:48.090 --> 00:45:49.170
jump through all these hoops.

00:45:49.970 --> 00:45:55.470
So a- I think majority of America,
while they love the fact of AI, it

00:45:55.529 --> 00:45:58.830
scares the hell out of them, and they're
not ready to just be a part of that

00:45:59.010 --> 00:46:03.390
m- that, that wave, and we have to be
respectful of that and just, it's a

00:46:03.470 --> 00:46:07.870
really cool nerdy tool, and all the
nerds are really geeking out about this.

00:46:08.069 --> 00:46:12.279
But, you know, between the energy that
it, that it takes and, and the, the

00:46:12.370 --> 00:46:17.630
cost, I mean, I was reading that it took
something like $192 million for them

00:46:17.690 --> 00:46:21.690
to, to, to go from, um, what was it, 5.0

00:46:21.710 --> 00:46:22.310
to 5.2

00:46:22.360 --> 00:46:23.130
with ChatGPT.

00:46:23.230 --> 00:46:28.410
So this is two hun- $200 million just
to make a small minor version update

00:46:28.490 --> 00:46:30.450
to the product that didn't reallyâ¦

00:46:30.529 --> 00:46:31.250
I mean, when 5.2

00:46:31.290 --> 00:46:33.569
came out, I think, I think
my nine-year-old is smarter

00:46:33.590 --> 00:46:35.029
than that thing at that point.

00:46:35.650 --> 00:46:38.529
Uh, and then so then they kind
of freaked out and released 5.5

00:46:38.569 --> 00:46:40.050
and, and now you have what you have.

00:46:40.170 --> 00:46:43.370
But it is getting extremely
expensive and everything else.

00:46:44.130 --> 00:46:46.010
How much smarter do we think we can get?

00:46:46.029 --> 00:46:49.830
And that's the looking forward of just
saying if people don't tolerate it now,

00:46:50.529 --> 00:46:55.300
and it's gonna take 20 more years to get
to where the, where we think it should

00:46:55.330 --> 00:46:58.550
be today, and you're gonna drag people
th- they're gonna get numb to that.

00:46:58.590 --> 00:47:00.230
They're gonna hate it even more.

00:47:00.250 --> 00:47:04.010
And so it's kind of just been like
a very slow just integration in

00:47:04.069 --> 00:47:07.430
that regard of just back to how
much do we let it talk to clients.

00:47:08.010 --> 00:47:10.050
Very minimal because we
don't wanna burn them out.

00:47:10.090 --> 00:47:11.330
We don't wanna scare them off.

00:47:11.790 --> 00:47:15.150
We want them to be comfortable
with it, and we want to also as

00:47:15.190 --> 00:47:18.569
their partner walk through this
A- AI journey as they have it.

00:47:18.600 --> 00:47:21.250
And, and they're gonna have questions,
and we wanna, you know, be able to answer

00:47:21.310 --> 00:47:25.430
them and help them, um, kind of get their
RPA in for their business or whatever

00:47:25.450 --> 00:47:27.279
it may be that they wanna get done.

00:47:27.350 --> 00:47:32.510
Uh, but it's also knowing the fad
of just, hey, we don't just go

00:47:32.610 --> 00:47:36.788
all in in AI just because somebody
said, "Hey, AI is the future."

00:47:36.910 --> 00:47:39.690
Um, it's, that's, that's craziest.

00:47:41.050 --> 00:47:43.510
Todd Kane: Especially because like I'm
really curious how this shakes out,

00:47:43.650 --> 00:47:47.911
especially over the next sort of two to
four years because, uh, I think we're

00:47:47.951 --> 00:47:52.710
starting to see the recognition that
we're in the subsidized era of AI, right?

00:47:52.790 --> 00:47:56.570
Like originally Uber, when it came out,
like you were-- you-- half of your Uber

00:47:56.670 --> 00:47:58.890
ride was pay for- paid for by VC dollars.

00:47:59.670 --> 00:48:04.590
we're sort of in the same era of AI where
like, people were panicking about like the

00:48:04.710 --> 00:48:09.610
restriction changes for, for like Claude
all of a sudden like felt more expensive.

00:48:09.670 --> 00:48:11.010
They got less token usage.

00:48:11.350 --> 00:48:14.971
And part of that was just a simple
physical limitation of compute, right?

00:48:15.030 --> 00:48:18.710
Like they had literally run out of compute
and had to s- find some way to save it.

00:48:19.090 --> 00:48:21.671
And then, you know, uh, xAI to the rescue.

00:48:21.690 --> 00:48:25.350
Since they have no clients, they were
able to fork off ev- all of their, their

00:48:25.417 --> 00:48:26.136
Aarin: Imagine that.

00:48:26.151 --> 00:48:26.831
Todd Kane: to, to Claude.

00:48:26.850 --> 00:48:27.190
Thank you.

00:48:27.570 --> 00:48:27.850
Yeah.

00:48:27.910 --> 00:48:33.310
Uh, but, uh, I, I think, I think
it's dangerous to rely on this stuff

00:48:33.410 --> 00:48:35.850
too much with the expectation that.

00:48:35.910 --> 00:48:38.250
it might get a lot more
expensive in the future.

00:48:38.430 --> 00:48:39.230
And then, you know,

00:48:39.337 --> 00:48:39.497
Aarin: Yeah

00:48:39.610 --> 00:48:42.670
Todd Kane: point of this is
not cheaper than humans, right?

00:48:42.750 --> 00:48:46.290
Uh, but you know, it might become a
lot more expensive in The future as

00:48:46.350 --> 00:48:51.350
the VC dollars start to sort of retract
from, from helping to subsidize this.

00:48:51.410 --> 00:48:53.710
So, you know, um, you know, buyer beware

00:48:53.897 --> 00:48:56.557
Aarin: thirds of the world of comedy
that's tied up in AI right now

00:48:57.058 --> 00:48:57.258
,  Todd Kane: Yeah,

00:48:57.478 --> 00:48:59.336
Aarin: which is a dangerous game

00:48:59.919 --> 00:49:01.958
Todd Kane: yeah, 'cause you, you
talked about like the cost of,

00:49:02.018 --> 00:49:03.658
of, of forking to the new model.

00:49:03.758 --> 00:49:04.898
Like I saw some of theâ¦

00:49:05.178 --> 00:49:08.098
I, I think these are still estimates,
pretty good estimates, but, you know,

00:49:08.218 --> 00:49:11.738
like for example, whatever the number
was, I'm, I'm pulling this out of my head.

00:49:11.798 --> 00:49:16.058
It's, it was something to the effect of
like a quarterly or an annual loss, either

00:49:16.098 --> 00:49:21.178
way, you know, pretty dramatic of like
negative $14 billion in EBITDA, right?

00:49:21.298 --> 00:49:23.538
Like not a business, you know?

00:49:24.658 --> 00:49:24.838
So

00:49:25.590 --> 00:49:26.569
Aarin: No, it's not.

00:49:27.338 --> 00:49:27.698
Todd Kane: Yeah.

00:49:27.790 --> 00:49:30.910
Aarin: it just goes back to the whole
point of just what is the outcome of this?

00:49:30.970 --> 00:49:34.370
The same thing with anything that
you're doing in the MSP, you're doing in

00:49:34.430 --> 00:49:36.359
operations, you're doing in automations.

00:49:36.410 --> 00:49:39.990
The most important factor is what
is the outcome of what you're doing?

00:49:40.430 --> 00:49:44.609
And if it's absolutely not defined in
any way, shape, or form, then you're

00:49:44.630 --> 00:49:46.410
really just selling people a pipe dream.

00:49:46.890 --> 00:49:48.890
AI's the future, go buy it.

00:49:48.930 --> 00:49:50.410
Like, yeah, okay, um,

00:49:51.994 --> 00:49:52.174
Todd Kane: Or

00:49:52.330 --> 00:49:52.830
Aarin: prove it.

00:49:52.894 --> 00:49:53.074
Todd Kane: Yeah.

00:49:53.470 --> 00:49:54.050
Aarin: For what?

00:49:54.390 --> 00:49:54.590
Like,

00:49:54.694 --> 00:49:54.734
Todd Kane: Yeah.

00:49:54.734 --> 00:49:54.834
Yeah

00:49:54.850 --> 00:49:55.370
Aarin: prove it.

00:49:55.410 --> 00:49:56.910
Like, okay, cool.

00:49:57.029 --> 00:50:01.870
I can, I can automatically categorize my
emails and I can do all this other stuff.

00:50:01.930 --> 00:50:02.749
That's very limited.

00:50:03.029 --> 00:50:04.959
I can't get AI to do my emails at all.

00:50:04.990 --> 00:50:07.278
Like, it won't do it because it
doesn't know who my clients are,

00:50:07.390 --> 00:50:08.670
what I want, what I do, what I like.

00:50:08.990 --> 00:50:11.990
It takes me longer to tell it what I'm
doing, and I'm just like, "Screw it.

00:50:12.010 --> 00:50:13.170
I'll do it myself."

00:50:13.562 --> 00:50:13.782
Todd Kane: Yeah,

00:50:14.090 --> 00:50:18.109
Aarin: so it's, it's just become
more of an augmentation of what is

00:50:18.149 --> 00:50:21.670
the most boring stuff that we have
that costs us money in the industry?

00:50:22.029 --> 00:50:23.390
How can we just focus on that?

00:50:23.450 --> 00:50:28.689
And as the technology gets better, we look
at new ways as time goes on, but we're,

00:50:28.729 --> 00:50:32.729
we're still very cautious to not just
go throw all our eggs into that basket.

00:50:33.470 --> 00:50:35.910
Um, and I was even with a peer group
and he's like, "Hey, I was thinking

00:50:35.930 --> 00:50:37.290
of just doing an AI business unit."

00:50:37.330 --> 00:50:39.090
And I'm like, "Okay, well
that's, that's pretty cool.

00:50:39.189 --> 00:50:39.840
Tell me about that."

00:50:39.910 --> 00:50:41.850
And he's like, "All
they're gonna do is AI."

00:50:41.870 --> 00:50:45.069
And I'm like, "Okay, so, um,
you're gonna build up this,

00:50:45.109 --> 00:50:46.279
this million-dollar business?"

00:50:46.330 --> 00:50:46.870
He's like, "Yeah."

00:50:46.899 --> 00:50:51.080
And I'm like, "Okay, so if AI goes the
way the, uh, the World Wide Web did, and

00:50:51.090 --> 00:50:54.580
we have a crash, what are you gonna do
when half your company's, uh, bankrupt?"

00:50:55.350 --> 00:50:56.870
And he said, "Well, I
never thought of that."

00:50:56.890 --> 00:50:59.830
And I'm like, "You gotta
think about stuff like this.

00:50:59.890 --> 00:51:02.490
What is the outcome of
you having an only AI?

00:51:02.930 --> 00:51:04.770
You have to mix it in with some RPA.

00:51:04.870 --> 00:51:06.510
You have to have a little
bit of flavor in there."

00:51:06.590 --> 00:51:08.550
Like, I've been preaching
that for a while.

00:51:08.770 --> 00:51:13.810
RPA is the superior of the two right now
because it doesn't need a graphics card

00:51:13.850 --> 00:51:18.370
to process, and it's not hallucinating
telling you, "Yes, I love you.

00:51:18.470 --> 00:51:19.790
You're correct."

00:51:19.994 --> 00:51:20.134
Todd Kane: Yeah.

00:51:20.834 --> 00:51:25.375
But I suppose we could use some AI
models to help us build the RPA, you know

00:51:26.041 --> 00:51:27.541
Aarin: You could do that, yes.

00:51:27.581 --> 00:51:28.880
Prompt engineering, all that stuff.

00:51:28.961 --> 00:51:31.760
But I mean, I guess it's how many bottles
of water do you wanna kill that day?

00:51:33.574 --> 00:51:35.274
Todd Kane: Depends how
thirsty you are or how, how

00:51:35.321 --> 00:51:35.821
Aarin: That's right.

00:51:36.154 --> 00:51:36.334
Todd Kane: is.

00:51:37.155 --> 00:51:37.615
Okay, cool.

00:51:37.934 --> 00:51:38.894
This has been awesome, Aaron.

00:51:39.014 --> 00:51:41.134
Um, I mean, we could jam all day, but, uh,

00:51:41.589 --> 00:51:42.429
Aarin: Oh, absolutely

00:51:42.634 --> 00:51:46.174
Todd Kane: we'll, we'll give you
some, some, uh, s- your day back here.

00:51:46.294 --> 00:51:47.115
Uh, so it's been fun.

00:51:47.214 --> 00:51:48.054
Appreciate your input,

00:51:48.309 --> 00:51:49.108
Aarin: I appreciate it, Todd.

00:51:49.255 --> 00:51:50.194
Todd Kane: uh, been a blast, man.

00:51:50.255 --> 00:51:50.454
Thanks.

00:51:50.849 --> 00:51:51.368
Aarin: Likewise