WEBVTT

1
00:00:03.439 --> 00:00:05.839
- Welcome to episode 432

2
00:00:05.839 --> 00:00:09.039
- of the Microsoft Cloud IT Pro podcast recorded

3
00:00:09.039 --> 00:00:11.859
- live on 07/13/2026.

4
00:00:12.080 --> 00:00:14.320
- This is a show about Microsoft three sixty

5
00:00:14.320 --> 00:00:16.445
- five and Azure from the perspective of IT

6
00:00:16.445 --> 00:00:18.765
- pros and end users, where we discuss a

7
00:00:18.765 --> 00:00:21.004
- topic or recent news and how it relates

8
00:00:21.004 --> 00:00:23.724
- to you. In this episode, Ben and Scott

9
00:00:23.724 --> 00:00:27.244
- discuss, deliberate, and pontificate on how consulting is

10
00:00:27.244 --> 00:00:27.744
- changing

11
00:00:28.260 --> 00:00:31.220
- as AI continues to grow. Part of that

12
00:00:31.220 --> 00:00:34.260
- is AI doesn't eliminate Microsoft three sixty five

13
00:00:34.260 --> 00:00:36.820
- and Azure consulting, but it does change how

14
00:00:36.820 --> 00:00:38.820
- you do it and what you may do

15
00:00:38.820 --> 00:00:39.719
- for your clients.

16
00:00:40.274 --> 00:00:41.414
- Enjoy the show.

17
00:00:43.395 --> 00:00:45.475
- Do you want to introduce our topic? All

18
00:00:45.475 --> 00:00:46.195
- right. James Fletcher (3five thirty three): There was

19
00:00:46.195 --> 00:00:49.155
- an article that I saw come out a

20
00:00:49.155 --> 00:00:51.634
- couple weeks ago and I had sent it

21
00:00:51.634 --> 00:00:52.295
- to you.

22
00:00:52.754 --> 00:00:53.254
- And

23
00:00:53.634 --> 00:00:54.134
- the

24
00:00:55.460 --> 00:00:56.439
- thought process

25
00:00:56.979 --> 00:00:57.479
- and

26
00:00:58.020 --> 00:01:00.020
- premise of that article, it came from The

27
00:01:00.020 --> 00:01:01.079
- Wall Street Journal,

28
00:01:01.780 --> 00:01:03.559
- and it's all about

29
00:01:04.260 --> 00:01:06.840
- the shift in billing models

30
00:01:07.299 --> 00:01:08.280
- for consultants

31
00:01:08.739 --> 00:01:10.359
- in the age of AI.

32
00:01:10.844 --> 00:01:13.265
- So as AI continues to mature,

33
00:01:13.644 --> 00:01:14.384
- how do

34
00:01:15.084 --> 00:01:15.584
- MSPs,

35
00:01:17.325 --> 00:01:18.305
- folks like you,

36
00:01:18.685 --> 00:01:19.744
- small consultancies,

37
00:01:20.765 --> 00:01:22.064
- even larger consultancies,

38
00:01:22.604 --> 00:01:25.164
- how do you think about changing your business

39
00:01:25.164 --> 00:01:25.664
- model

40
00:01:27.960 --> 00:01:29.560
- in the world of AI? So I thought

41
00:01:29.560 --> 00:01:31.000
- that would be an interesting one to cover

42
00:01:31.000 --> 00:01:33.079
- because I think it's been probably hitting you

43
00:01:33.079 --> 00:01:35.240
- a little bit in your business from what

44
00:01:35.240 --> 00:01:37.500
- we discussed, so it's kind of close and

45
00:01:38.055 --> 00:01:39.575
- near and dear. But I think there's a

46
00:01:39.575 --> 00:01:41.655
- bunch of different ways that we can talk

47
00:01:41.655 --> 00:01:43.435
- about and talk through

48
00:01:44.055 --> 00:01:44.875
- how folks

49
00:01:45.415 --> 00:01:47.755
- can think about shifting their businesses

50
00:01:48.694 --> 00:01:51.515
- and their business models around M365

51
00:01:52.700 --> 00:01:53.600
- and Azure

52
00:01:53.980 --> 00:01:54.640
- in particular,

53
00:01:55.340 --> 00:01:57.439
- and what needs to potentially

54
00:01:58.219 --> 00:02:00.400
- change in a delivery

55
00:02:01.260 --> 00:02:03.260
- along the way. So I guess one of

56
00:02:03.260 --> 00:02:04.299
- the things that I said, I saw this

57
00:02:04.299 --> 00:02:06.674
- article, it kind of resonated with me having

58
00:02:06.674 --> 00:02:09.175
- been a former consultant, kinda being close

59
00:02:09.955 --> 00:02:11.155
- to the work that you do and what

60
00:02:11.155 --> 00:02:12.534
- was going on. It's like, oh, this

61
00:02:13.715 --> 00:02:14.215
- does

62
00:02:14.514 --> 00:02:16.834
- make sense. The the funny thing to me

63
00:02:16.834 --> 00:02:18.995
- as I was reading it was it kinda

64
00:02:18.995 --> 00:02:20.989
- sounded like part of the world that I

65
00:02:20.989 --> 00:02:22.610
- used to do when I was in consulting.

66
00:02:22.989 --> 00:02:25.949
- So I used to work for a couple

67
00:02:25.949 --> 00:02:27.569
- of different places where

68
00:02:28.430 --> 00:02:30.509
- it was a mix of delivery models from

69
00:02:30.509 --> 00:02:31.489
- hourly billing

70
00:02:31.789 --> 00:02:32.930
- to fixed bid

71
00:02:33.585 --> 00:02:35.284
- or more, like, structured

72
00:02:35.824 --> 00:02:37.444
- statement of work. Like, hey.

73
00:02:38.465 --> 00:02:39.365
- Let's see.

74
00:02:39.665 --> 00:02:41.444
- We'll come in and install

75
00:02:41.905 --> 00:02:44.224
- an on premises SharePoint environment for you kind

76
00:02:44.224 --> 00:02:46.004
- of thing, and we think that's gonna take

77
00:02:46.810 --> 00:02:48.889
- this long with this many people for this

78
00:02:48.889 --> 00:02:50.730
- size of environment. We'll configure it in this

79
00:02:50.730 --> 00:02:52.750
- way, and that's gonna cost you

80
00:02:53.129 --> 00:02:53.629
- n

81
00:02:53.930 --> 00:02:54.430
- dollars

82
00:02:55.210 --> 00:02:57.530
- all rolled up. So if we come in

83
00:02:57.530 --> 00:02:59.290
- under hours, great. We make a little extra

84
00:02:59.290 --> 00:03:01.185
- money. If we come in over hours, well,

85
00:03:01.264 --> 00:03:03.264
- that's on us. We eat it kind of

86
00:03:03.264 --> 00:03:05.604
- thing. So I'm pretty used to that world

87
00:03:06.305 --> 00:03:08.245
- of fixed bid SAU's, which

88
00:03:09.185 --> 00:03:12.224
- can be tough to do and kind of

89
00:03:12.224 --> 00:03:14.004
- hit or miss in the cloud because

90
00:03:14.469 --> 00:03:16.889
- if you're doing something like, let's say M365

91
00:03:17.509 --> 00:03:18.009
- governance,

92
00:03:18.389 --> 00:03:19.989
- well, like what does that really mean? And

93
00:03:19.989 --> 00:03:20.949
- what are we going to do? And what

94
00:03:20.949 --> 00:03:22.150
- are we going to dial into? Is it

95
00:03:22.150 --> 00:03:23.689
- better to be hourly

96
00:03:24.069 --> 00:03:26.709
- and sell a fixed number of hours? Can

97
00:03:26.709 --> 00:03:28.889
- you get customers to do that? Or

98
00:03:29.270 --> 00:03:30.955
- if not, how do you start to think

99
00:03:30.955 --> 00:03:33.134
- about some of these things and pivot them

100
00:03:33.995 --> 00:03:34.655
- to more

101
00:03:35.194 --> 00:03:36.495
- outcome driven deliveries

102
00:03:36.794 --> 00:03:39.694
- and being able to clearly articulate those outcomes

103
00:03:40.314 --> 00:03:40.814
- for

104
00:03:41.995 --> 00:03:42.495
- customers?

105
00:03:43.240 --> 00:03:45.500
- And I think it is changing for customers.

106
00:03:45.639 --> 00:03:48.460
- Right? Like, they they're looking at these things.

107
00:03:48.759 --> 00:03:50.360
- Maybe they think they can vibe code them

108
00:03:50.360 --> 00:03:50.860
- quicker.

109
00:03:51.400 --> 00:03:51.900
- Maybe,

110
00:03:52.199 --> 00:03:54.699
- hey. If I've already deployed Copilot and Microsoft

111
00:03:54.840 --> 00:03:55.340
- is

112
00:03:55.639 --> 00:03:56.139
- pushing

113
00:03:56.520 --> 00:03:58.379
- the Copilot train at me,

114
00:03:59.114 --> 00:04:00.875
- Why can't I just ask Copilot how to

115
00:04:00.875 --> 00:04:02.875
- configure my environment? Isn't it supposed to tell

116
00:04:02.875 --> 00:04:04.254
- me how to do those things?

117
00:04:04.555 --> 00:04:06.074
- One would argue that it is supposed to

118
00:04:06.074 --> 00:04:07.834
- tell you, but it is telling you the

119
00:04:07.834 --> 00:04:08.495
- right thing

120
00:04:09.354 --> 00:04:11.215
- and and what to do along the way.

121
00:04:12.240 --> 00:04:13.699
- Maybe, but also

122
00:04:14.000 --> 00:04:14.819
- maybe not.

123
00:04:15.280 --> 00:04:16.740
- So a TLDR.

124
00:04:17.759 --> 00:04:19.839
- Hourly billing, I think, is a thing that's

125
00:04:19.839 --> 00:04:21.839
- changing. It's something that folks need to think

126
00:04:21.839 --> 00:04:22.339
- about,

127
00:04:22.879 --> 00:04:25.365
- especially if you're out there consulting. We said

128
00:04:25.524 --> 00:04:28.884
- whether you're working for a company, delivering consulting

129
00:04:28.884 --> 00:04:31.544
- services, maybe you're an MSP, things like that,

130
00:04:32.084 --> 00:04:33.305
- and you have a

131
00:04:33.764 --> 00:04:37.144
- consulting bucket of hours, that world's probably changing.

132
00:04:37.685 --> 00:04:40.245
- But my hypothesis, or I guess my argument

133
00:04:40.245 --> 00:04:41.144
- would be that

134
00:04:42.189 --> 00:04:46.189
- the AI thing doesn't eliminate the need for

135
00:04:46.189 --> 00:04:49.009
- Microsoft three sixty five or Azure consulting,

136
00:04:50.110 --> 00:04:51.329
- but it does change

137
00:04:51.629 --> 00:04:53.490
- what customers think they're buying.

138
00:04:53.870 --> 00:04:55.970
- So what customers are buying

139
00:04:56.485 --> 00:04:58.564
- more and more, and arguably they've been buying

140
00:04:58.564 --> 00:05:00.404
- this the whole time, although it's been abstracted

141
00:05:00.404 --> 00:05:02.965
- away in different ways, is outcomes. Like, they

142
00:05:02.965 --> 00:05:04.904
- wanna get to a certain place

143
00:05:06.085 --> 00:05:08.645
- with a certain thing. So in that old

144
00:05:08.645 --> 00:05:09.865
- world of

145
00:05:10.629 --> 00:05:13.029
- just walking in and saying, Well, pay me

146
00:05:13.029 --> 00:05:15.129
- hourly and we'll see how far we get,

147
00:05:15.750 --> 00:05:16.490
- kind of thing,

148
00:05:16.870 --> 00:05:18.649
- they were buying your expert hours.

149
00:05:19.110 --> 00:05:21.750
- They were buying your expertise and everything along

150
00:05:21.750 --> 00:05:23.604
- the way. I think in that new world

151
00:05:23.604 --> 00:05:25.144
- of we wanna get to outcomes

152
00:05:25.685 --> 00:05:27.144
- or we wanna get to

153
00:05:27.604 --> 00:05:28.104
- measurable

154
00:05:28.404 --> 00:05:29.384
- success criteria,

155
00:05:30.724 --> 00:05:32.584
- that's gonna be things like,

156
00:05:33.125 --> 00:05:35.044
- let's go ahead and get us ready for

157
00:05:35.044 --> 00:05:37.305
- m three sixty five Copilot, but not just

158
00:05:37.949 --> 00:05:40.910
- get us ready in these specific dimensions and

159
00:05:40.910 --> 00:05:42.050
- dial those in.

160
00:05:42.670 --> 00:05:44.050
- Could you do things

161
00:05:44.509 --> 00:05:45.009
- like

162
00:05:46.110 --> 00:05:47.870
- rather than maybe working in, like, the well

163
00:05:47.870 --> 00:05:49.009
- architected framework

164
00:05:49.389 --> 00:05:49.889
- in

165
00:05:50.294 --> 00:05:50.794
- Azure

166
00:05:51.175 --> 00:05:53.334
- land, maybe you start doing things like wrapping

167
00:05:53.334 --> 00:05:56.535
- up landing zone deployments as fixed packages so

168
00:05:56.535 --> 00:05:57.754
- that you get that

169
00:05:58.214 --> 00:06:01.194
- fixed set of outcomes for deploying a governed,

170
00:06:01.414 --> 00:06:02.394
- a well governed

171
00:06:03.000 --> 00:06:04.540
- Azure landing zone implementation

172
00:06:05.000 --> 00:06:05.980
- for workload

173
00:06:06.360 --> 00:06:08.060
- x, y, z kind of thing.

174
00:06:08.520 --> 00:06:10.279
- I think the other space that's kind of

175
00:06:10.279 --> 00:06:11.800
- interesting, you and I were chatting about this

176
00:06:11.800 --> 00:06:14.300
- as we're kind of prepping, is stuff like

177
00:06:14.680 --> 00:06:17.980
- secure scores and your defender for cloud posture

178
00:06:18.194 --> 00:06:20.274
- and all those kinds of things. Could you

179
00:06:20.274 --> 00:06:22.055
- offer things that say, hey.

180
00:06:22.514 --> 00:06:25.415
- Take your secure score from x to y,

181
00:06:26.514 --> 00:06:28.355
- from this number to this number? Or not

182
00:06:28.355 --> 00:06:29.714
- from just x to y, what if we

183
00:06:29.714 --> 00:06:31.649
- did, like, x y z and you had

184
00:06:31.649 --> 00:06:34.370
- a good better best offering thing that you

185
00:06:34.370 --> 00:06:34.870
- could

186
00:06:35.569 --> 00:06:36.389
- put out there?

187
00:06:37.729 --> 00:06:39.029
- So anyhoo, we

188
00:06:39.569 --> 00:06:40.870
- should talk through this space

189
00:06:41.410 --> 00:06:42.069
- and maybe

190
00:06:42.529 --> 00:06:43.349
- why M365

191
00:06:43.810 --> 00:06:45.110
- and Azure are

192
00:06:47.305 --> 00:06:49.785
- good test beds or good places to go

193
00:06:49.785 --> 00:06:52.204
- do, like, outcome driven deliveries?

194
00:06:52.985 --> 00:06:55.625
- And what are some potential, like, practices or

195
00:06:55.625 --> 00:06:58.044
- deliveries that could shape up around

196
00:06:59.850 --> 00:07:00.889
- those technologies. Josh Young (zero fifty seven:thirty seven):

197
00:07:00.889 --> 00:07:02.810
- That's interesting. And I think the other aspect

198
00:07:02.810 --> 00:07:04.170
- that we kind of talked about and how

199
00:07:04.170 --> 00:07:05.310
- you touched on it is

200
00:07:07.050 --> 00:07:08.189
- how AI can

201
00:07:08.730 --> 00:07:10.750
- assist in these and why

202
00:07:11.930 --> 00:07:12.589
- AI has

203
00:07:13.214 --> 00:07:15.395
- caused people to think about this more because

204
00:07:15.535 --> 00:07:17.455
- I would agree from my perspective and some

205
00:07:17.455 --> 00:07:19.235
- of what I've seen and how I

206
00:07:19.855 --> 00:07:22.915
- execute different projects now, AI has absolutely

207
00:07:23.535 --> 00:07:24.035
- changed

208
00:07:24.574 --> 00:07:26.574
- how I do it, which I think also

209
00:07:26.574 --> 00:07:28.754
- plays an effect on some of

210
00:07:29.110 --> 00:07:31.529
- how you start scoping out these different projects.

211
00:07:32.150 --> 00:07:33.689
- So this is absolutely

212
00:07:33.990 --> 00:07:34.650
- a fascinating

213
00:07:35.670 --> 00:07:37.395
- conversation to dig through. Robert Leonard (zero fifty

214
00:07:37.395 --> 00:07:38.629
- three:thirty seven): Let's get into it. Where do

215
00:07:38.629 --> 00:07:40.150
- you want to start? I mean, and I

216
00:07:40.150 --> 00:07:41.685
- know it's near and dear to your heart,

217
00:07:42.245 --> 00:07:44.725
- being a consultant and being in this space.

218
00:07:44.725 --> 00:07:46.745
- Yeah. It is. And we have a

219
00:07:47.125 --> 00:07:47.865
- lot of

220
00:07:48.165 --> 00:07:51.365
- notes here and oh, like, this whole topic

221
00:07:51.365 --> 00:07:53.144
- is just it's a tough one to unwrap.

222
00:07:53.790 --> 00:07:54.449
- I don't

223
00:07:55.949 --> 00:07:57.470
- I don't know. I don't know where to

224
00:07:57.470 --> 00:07:58.990
- start on this, Scott. Maybe we should ask

225
00:07:58.990 --> 00:08:00.370
- AI where to start on this.

226
00:08:01.069 --> 00:08:03.149
- Maybe it is. It's the fact that I'm

227
00:08:03.149 --> 00:08:04.750
- thinking Why don't we do this? I'm having

228
00:08:04.750 --> 00:08:06.270
- the same thoughts you are about how do

229
00:08:06.270 --> 00:08:08.384
- I change my offerings. Like, I'll be honest,

230
00:08:08.384 --> 00:08:10.064
- and I haven't had conversations with all my

231
00:08:10.064 --> 00:08:11.185
- clients yet, so if you're one of my

232
00:08:11.185 --> 00:08:11.685
- clients,

233
00:08:12.225 --> 00:08:14.865
- there might be a conversation coming about how

234
00:08:14.865 --> 00:08:16.404
- I start structuring

235
00:08:17.105 --> 00:08:19.274
- my new packages and how I'm going to

236
00:08:19.274 --> 00:08:19.774
- adjust

237
00:08:20.080 --> 00:08:21.220
- what I offer.

238
00:08:22.000 --> 00:08:24.400
- And I would say this came somewhat before

239
00:08:24.400 --> 00:08:26.720
- AI, but I think AI has accelerated how

240
00:08:26.720 --> 00:08:29.439
- I'm thinking about, like you said, offering more

241
00:08:29.439 --> 00:08:30.259
- of these

242
00:08:30.720 --> 00:08:31.220
- fixed

243
00:08:31.759 --> 00:08:34.134
- these outcome based deliveries is what I'm looking

244
00:08:34.134 --> 00:08:34.634
- at.

245
00:08:35.335 --> 00:08:36.235
- In the past,

246
00:08:36.535 --> 00:08:38.535
- I have absolutely done everything from a T

247
00:08:38.535 --> 00:08:41.014
- and M perspective, just straight up time and

248
00:08:41.014 --> 00:08:42.075
- materials. And

249
00:08:42.774 --> 00:08:44.054
- this isn't a secret. If you go to

250
00:08:44.054 --> 00:08:46.054
- my website, you can start seeing it. How

251
00:08:46.054 --> 00:08:48.955
- I'm adjusting where it's going to be

252
00:08:49.309 --> 00:08:52.370
- projects where it's very much a fixed

253
00:08:52.909 --> 00:08:54.350
- I'm not going to say it's necessarily going

254
00:08:54.350 --> 00:08:55.870
- to be fixed price, but it's very much

255
00:08:55.870 --> 00:08:58.829
- a fixed project. Very well defined statement of

256
00:08:58.829 --> 00:09:00.990
- work, this is where we are, this is

257
00:09:00.990 --> 00:09:02.929
- where we want to get to, here's

258
00:09:03.335 --> 00:09:04.394
- what we're going to deliver,

259
00:09:05.335 --> 00:09:06.154
- or doing

260
00:09:06.535 --> 00:09:09.355
- a little bit more of shifting to

261
00:09:10.294 --> 00:09:11.995
- what I would say more of a fractional

262
00:09:12.375 --> 00:09:12.875
- M365

263
00:09:13.335 --> 00:09:16.235
- architecture type stuff that's going to

264
00:09:17.014 --> 00:09:18.794
- lead to a little bit more of here's

265
00:09:19.709 --> 00:09:20.769
- what I can

266
00:09:21.230 --> 00:09:23.389
- Here's the value that I can deliver, not

267
00:09:23.389 --> 00:09:25.870
- necessarily just call me up when you need

268
00:09:25.870 --> 00:09:26.370
- something.

269
00:09:26.990 --> 00:09:28.350
- There can be a part of that in

270
00:09:28.350 --> 00:09:29.389
- there, and I know you and I have

271
00:09:29.389 --> 00:09:31.070
- even talked about how you kind of package

272
00:09:31.070 --> 00:09:31.669
- some of that up. Jason Brett (3nine forty

273
00:09:31.669 --> 00:09:33.149
- seven): I guess we both agree that it's

274
00:09:33.149 --> 00:09:33.649
- changing

275
00:09:34.294 --> 00:09:36.534
- and that it's out there. So why don't

276
00:09:36.534 --> 00:09:37.834
- we maybe talk through

277
00:09:38.214 --> 00:09:40.475
- and start with some of the options

278
00:09:42.934 --> 00:09:44.634
- around the different

279
00:09:44.934 --> 00:09:45.914
- billing models

280
00:09:46.429 --> 00:09:48.990
- and how those shape up. Right? So I

281
00:09:48.990 --> 00:09:50.450
- think we both agree that

282
00:09:51.070 --> 00:09:53.089
- the world is changing a little bit there.

283
00:09:53.309 --> 00:09:54.669
- So you've got a bunch of different pricing

284
00:09:54.669 --> 00:09:56.509
- models that you can approach these things with.

285
00:09:56.509 --> 00:09:58.049
- There's fixed fee pricing.

286
00:09:59.304 --> 00:10:02.184
- There's the outcome based stuff. I think there's

287
00:10:02.184 --> 00:10:05.304
- also subscription pricing, and there's an argument to

288
00:10:05.304 --> 00:10:07.144
- be made for hybrid. Like, you're still gonna

289
00:10:07.144 --> 00:10:09.324
- have a world of hourly billing and

290
00:10:09.865 --> 00:10:12.125
- and combining that together.

291
00:10:12.870 --> 00:10:15.750
- And then within those segments, like within a

292
00:10:15.750 --> 00:10:18.230
- fixed fee, an outcome based, subscription hybrid, wherever

293
00:10:18.230 --> 00:10:19.289
- it happens to be,

294
00:10:20.070 --> 00:10:21.129
- you've got kind

295
00:10:21.830 --> 00:10:24.309
- of the on the ground view or I

296
00:10:24.309 --> 00:10:27.509
- guess the reality of what delivery looks like

297
00:10:27.509 --> 00:10:28.009
- there.

298
00:10:28.684 --> 00:10:30.524
- So that's a bunch of stuff that folks

299
00:10:30.524 --> 00:10:31.804
- have already had. Like, when you think about,

300
00:10:31.804 --> 00:10:34.544
- like, the MSP space, repeatable IP,

301
00:10:35.325 --> 00:10:35.825
- automation,

302
00:10:36.684 --> 00:10:37.745
- things like that,

303
00:10:39.644 --> 00:10:42.269
- all the, I guess, client prerequisites,

304
00:10:42.809 --> 00:10:43.470
- like assessments,

305
00:10:44.009 --> 00:10:45.309
- things like that happen.

306
00:10:45.690 --> 00:10:48.669
- But there is that new nuance of AI

307
00:10:48.730 --> 00:10:49.950
- assisted delivery

308
00:10:51.210 --> 00:10:51.870
- that sits

309
00:10:52.970 --> 00:10:54.110
- within there. So

310
00:10:54.794 --> 00:10:56.714
- I think maybe if we talk through some

311
00:10:56.714 --> 00:10:57.455
- of the

312
00:10:58.235 --> 00:10:59.455
- delivery models,

313
00:11:00.075 --> 00:11:02.894
- those pricing models and how they shape up,

314
00:11:04.554 --> 00:11:06.394
- it should form out and kind of bring

315
00:11:06.394 --> 00:11:07.274
- it together. Jay Jacobs (3nine fifty seven): If

316
00:11:07.274 --> 00:11:09.434
- we start with the AI assisted, and this

317
00:11:09.434 --> 00:11:09.934
- is

318
00:11:10.769 --> 00:11:13.029
- where I've struggled with some of the pricing

319
00:11:13.649 --> 00:11:15.910
- and how you start thinking through these projects,

320
00:11:16.050 --> 00:11:16.550
- because

321
00:11:17.090 --> 00:11:17.910
- I absolutely

322
00:11:18.370 --> 00:11:20.230
- use AI in a lot of my projects.

323
00:11:20.769 --> 00:11:22.950
- And there's a couple aspects to this, right?

324
00:11:23.445 --> 00:11:25.945
- AI has absolutely made my

325
00:11:26.565 --> 00:11:27.065
- deliveries

326
00:11:27.845 --> 00:11:28.345
- faster.

327
00:11:28.965 --> 00:11:29.465
- And

328
00:11:30.085 --> 00:11:31.225
- this is where

329
00:11:31.924 --> 00:11:34.004
- some of that comes in where I was

330
00:11:34.004 --> 00:11:36.585
- doing fewer hourly, and

331
00:11:37.139 --> 00:11:37.639
- AI

332
00:11:38.180 --> 00:11:40.660
- enables me, empowers me to do some of

333
00:11:40.660 --> 00:11:42.899
- that quicker. AI is very good at some

334
00:11:42.899 --> 00:11:45.000
- of the data analysis, some of the security

335
00:11:45.059 --> 00:11:47.059
- assessment, some of that stuff that I used

336
00:11:47.059 --> 00:11:47.720
- to do,

337
00:11:48.820 --> 00:11:50.820
- which I'm still providing the same amount of

338
00:11:50.820 --> 00:11:53.225
- value. But as I use

339
00:11:53.764 --> 00:11:55.524
- AI, a portion it allows me to do

340
00:11:55.524 --> 00:11:57.764
- a portion of it faster, but it also

341
00:11:57.764 --> 00:12:00.404
- changes. Like, I absolutely still have to review

342
00:12:00.404 --> 00:12:02.985
- some of the AI outcomes. AI still hallucinates.

343
00:12:03.764 --> 00:12:05.684
- Surprise. It doesn't get everything right all the

344
00:12:05.684 --> 00:12:06.184
- time.

345
00:12:07.049 --> 00:12:09.929
- There's still a level of, right, there's still

346
00:12:09.929 --> 00:12:11.929
- a level of expertise, like I can use

347
00:12:11.929 --> 00:12:14.330
- AI, but part of the ability I have

348
00:12:14.330 --> 00:12:16.330
- to use AI when it comes to these

349
00:12:16.330 --> 00:12:19.549
- deliveries is the fact that I also

350
00:12:20.090 --> 00:12:20.590
- know

351
00:12:20.970 --> 00:12:23.184
- what I'm looking for, so so I know

352
00:12:23.184 --> 00:12:25.424
- what to ask AI about. I can go

353
00:12:25.424 --> 00:12:27.024
- export a whole bunch of data from Microsoft

354
00:12:27.024 --> 00:12:28.944
- three sixty five. I can get conditional access

355
00:12:28.944 --> 00:12:31.745
- policies, I can get user account security groups,

356
00:12:31.745 --> 00:12:33.764
- I can get DLP policies,

357
00:12:35.149 --> 00:12:36.529
- but all of that stuff

358
00:12:36.990 --> 00:12:38.509
- still has to work together, and you still

359
00:12:38.509 --> 00:12:40.190
- have to know what you're looking for and

360
00:12:40.190 --> 00:12:42.110
- what to ask AI about. So I think

361
00:12:42.110 --> 00:12:42.610
- there's

362
00:12:43.629 --> 00:12:45.950
- that level of expertise that as much as

363
00:12:45.950 --> 00:12:47.730
- AI can assist with those deliveries,

364
00:12:48.054 --> 00:12:49.595
- you still have to have

365
00:12:50.054 --> 00:12:52.295
- a certain level of expertise to know how

366
00:12:52.295 --> 00:12:54.535
- everything fits together, to know what you're looking

367
00:12:54.535 --> 00:12:55.995
- for, to know

368
00:12:56.535 --> 00:12:58.075
- where AI is hallucinating,

369
00:12:58.535 --> 00:13:00.774
- and to know what data to tell AI

370
00:13:00.774 --> 00:13:02.559
- to look at. So I think there's that

371
00:13:02.559 --> 00:13:04.240
- aspect of it when it comes to these

372
00:13:04.240 --> 00:13:07.679
- AI assisted deliveries. The other thing that comes

373
00:13:07.679 --> 00:13:10.559
- into play, guess what if I ask AI

374
00:13:10.559 --> 00:13:12.980
- to go look over, like, hundreds of CSV

375
00:13:13.120 --> 00:13:15.840
- files with thousands and thousands of lines of

376
00:13:15.840 --> 00:13:16.340
- data?

377
00:13:16.754 --> 00:13:18.835
- I may get faster, but guess what? AI

378
00:13:18.835 --> 00:13:19.495
- is expensive.

379
00:13:20.835 --> 00:13:21.815
- The amount of

380
00:13:22.355 --> 00:13:24.995
- there's also that aspect to, well, AI may

381
00:13:24.995 --> 00:13:26.915
- help me do it faster. It is also

382
00:13:26.915 --> 00:13:27.735
- more expensive

383
00:13:28.035 --> 00:13:30.274
- for me to do it faster because AI

384
00:13:30.274 --> 00:13:32.470
- is not cheap. So this is where I

385
00:13:32.470 --> 00:13:33.769
- start thinking through

386
00:13:34.950 --> 00:13:37.589
- how do you start setting up these deliveries

387
00:13:37.589 --> 00:13:39.429
- and thinking about consulting when it does come

388
00:13:39.429 --> 00:13:42.169
- to something like a Microsoft three sixty five

389
00:13:42.389 --> 00:13:45.085
- security audit or just an audit of the

390
00:13:45.085 --> 00:13:46.144
- overall configuration.

391
00:13:48.605 --> 00:13:49.504
- And I would say,

392
00:13:49.965 --> 00:13:51.884
- to my earlier point, certain things got faster,

393
00:13:51.884 --> 00:13:54.384
- but I've also noticed the projects aren't

394
00:13:54.764 --> 00:13:56.445
- because of the new things I have to

395
00:13:56.445 --> 00:13:58.205
- pay attention to or some of the things

396
00:13:58.205 --> 00:13:59.264
- I'm able to incorporate.

397
00:14:00.490 --> 00:14:03.389
- Some of them actually aren't as much faster

398
00:14:03.529 --> 00:14:04.809
- as I thought they would be when I

399
00:14:04.809 --> 00:14:06.009
- start looking at hours. Ryan Vaughn (3zero thirty

400
00:14:06.009 --> 00:14:08.029
- seven): It's interesting. So you've got this,

401
00:14:08.410 --> 00:14:09.790
- I think, explosion

402
00:14:10.490 --> 00:14:11.549
- of artifacts

403
00:14:11.850 --> 00:14:13.370
- that are all of a sudden available to

404
00:14:13.370 --> 00:14:14.110
- you. So

405
00:14:15.125 --> 00:14:16.184
- assessments become

406
00:14:16.644 --> 00:14:19.125
- maybe not quicker to draw out the telemetry,

407
00:14:19.125 --> 00:14:21.764
- but certainly to analyze the telemetry for a

408
00:14:21.764 --> 00:14:22.264
- given

409
00:14:22.644 --> 00:14:23.144
- surface.

410
00:14:23.924 --> 00:14:25.865
- So things like assessments go faster.

411
00:14:26.565 --> 00:14:27.304
- Your whole

412
00:14:28.004 --> 00:14:29.384
- library, I guess, of scripts

413
00:14:29.750 --> 00:14:32.309
- and runbooks and things like that begins to

414
00:14:32.309 --> 00:14:32.809
- expand

415
00:14:33.190 --> 00:14:34.089
- and explode.

416
00:14:35.029 --> 00:14:36.490
- I've noticed in

417
00:14:37.110 --> 00:14:39.509
- my world even in like the internal things

418
00:14:39.509 --> 00:14:40.330
- that I do,

419
00:14:40.789 --> 00:14:42.089
- the number of,

420
00:14:42.629 --> 00:14:43.289
- I guess,

421
00:14:43.664 --> 00:14:45.845
- artifacts that I'm carrying around now for

422
00:14:46.384 --> 00:14:47.445
- Bicep modules,

423
00:14:47.825 --> 00:14:48.644
- ARM templates,

424
00:14:50.144 --> 00:14:53.184
- Azure policies, things like that, it's just started

425
00:14:53.184 --> 00:14:54.544
- to kind of like balloon and get a

426
00:14:54.544 --> 00:14:56.225
- little bit out of control. Like I'm having

427
00:14:56.225 --> 00:14:58.464
- to need to go organize all this stuff

428
00:14:58.464 --> 00:14:59.850
- in well system

429
00:15:00.230 --> 00:15:00.730
- it

430
00:15:01.110 --> 00:15:01.610
- soon.

431
00:15:03.110 --> 00:15:04.730
- It's also the world of

432
00:15:06.070 --> 00:15:06.570
- Copilot

433
00:15:08.470 --> 00:15:11.429
- and prompt packs. So the early stuff that's

434
00:15:11.429 --> 00:15:13.764
- been going on with getting good at prompt

435
00:15:13.764 --> 00:15:16.264
- engineering, I think that's a set of reusable

436
00:15:16.404 --> 00:15:18.804
- IP that everybody's building out on their own.

437
00:15:18.804 --> 00:15:20.804
- And you can not only use that to

438
00:15:20.804 --> 00:15:22.644
- accelerate your deliveries, but maybe it's also an

439
00:15:22.644 --> 00:15:25.065
- offering that you kind of give to

440
00:15:25.845 --> 00:15:26.745
- your customers

441
00:15:27.365 --> 00:15:28.345
- that are out there.

442
00:15:28.720 --> 00:15:31.220
- The other interesting thing that I've seen is

443
00:15:31.840 --> 00:15:34.820
- not just the assessment side of things, but

444
00:15:35.440 --> 00:15:38.240
- selling the story about what you're trying to

445
00:15:38.240 --> 00:15:40.559
- achieve and what the outcomes are. So things

446
00:15:40.559 --> 00:15:41.059
- like

447
00:15:41.554 --> 00:15:42.054
- more

448
00:15:42.434 --> 00:15:43.654
- like executive framed

449
00:15:44.355 --> 00:15:44.855
- readouts

450
00:15:45.315 --> 00:15:46.294
- or presentations

451
00:15:47.394 --> 00:15:47.894
- become

452
00:15:48.195 --> 00:15:48.855
- kind of

453
00:15:49.394 --> 00:15:52.274
- part of that delivery window, right, and pushing

454
00:15:52.274 --> 00:15:53.735
- things up there. So

455
00:15:54.674 --> 00:15:57.059
- it's not necessarily a new world, but it

456
00:15:57.059 --> 00:15:59.080
- is an additive world. So

457
00:16:02.179 --> 00:16:03.379
- if you're in a place where you've been

458
00:16:03.379 --> 00:16:04.660
- doing this while and you're a little bit

459
00:16:04.660 --> 00:16:07.320
- mature, you've probably been pitching all along that,

460
00:16:09.174 --> 00:16:09.835
- let's take,

461
00:16:10.934 --> 00:16:12.315
- like, Azure, for example.

462
00:16:12.855 --> 00:16:13.754
- You you make this

463
00:16:14.134 --> 00:16:15.034
- shift from

464
00:16:15.575 --> 00:16:18.054
- we have people who know the portal. Great.

465
00:16:18.054 --> 00:16:19.995
- You know how to do click ops. Awesome.

466
00:16:20.240 --> 00:16:22.319
- How does that really help me? To something

467
00:16:22.319 --> 00:16:22.819
- like,

468
00:16:23.120 --> 00:16:25.539
- we have a delivery machine that can actually

469
00:16:25.839 --> 00:16:28.720
- reliably improve your environment, and here's what that

470
00:16:28.720 --> 00:16:30.720
- machine is. Here's what it does. Here's how

471
00:16:30.720 --> 00:16:32.100
- long it's gonna take us

472
00:16:33.294 --> 00:16:34.595
- to to get there.

473
00:16:35.214 --> 00:16:36.975
- So you've probably had a bunch of these

474
00:16:36.975 --> 00:16:39.214
- things all along. So, like, I imagine in

475
00:16:39.214 --> 00:16:40.914
- your world, you have, like, a whole

476
00:16:41.455 --> 00:16:41.955
- repository

477
00:16:42.495 --> 00:16:45.554
- of scripts and things that sit out there.

478
00:16:45.769 --> 00:16:47.549
- But now what you have to do is,

479
00:16:47.769 --> 00:16:49.450
- you've already built the IP, you have the

480
00:16:49.450 --> 00:16:51.210
- IP, you have those things, but now what

481
00:16:51.210 --> 00:16:53.210
- you do is you have to get to

482
00:16:53.210 --> 00:16:56.110
- the place where you can sell the outcome

483
00:16:56.330 --> 00:16:58.509
- and be able to measure the timeline ruthlessly.

484
00:16:59.049 --> 00:17:00.110
- If you go and sell

485
00:17:00.654 --> 00:17:02.654
- or you've put together an offering that is

486
00:17:02.654 --> 00:17:04.174
- effectively like, hey, this is going to take

487
00:17:04.174 --> 00:17:05.535
- me an hour to deliver and it ends

488
00:17:05.535 --> 00:17:08.035
- up taking me three hours every time, well,

489
00:17:09.055 --> 00:17:09.875
- that's no good.

490
00:17:10.174 --> 00:17:11.154
- You're not getting

491
00:17:11.694 --> 00:17:13.375
- to where you need to be. So I

492
00:17:13.375 --> 00:17:15.295
- think as folks are out there and they're

493
00:17:15.295 --> 00:17:16.035
- kind of evaluating

494
00:17:16.630 --> 00:17:17.450
- all the things

495
00:17:18.069 --> 00:17:19.829
- that exist and all the things that you've

496
00:17:19.829 --> 00:17:21.289
- built up and what's going on,

497
00:17:21.750 --> 00:17:23.750
- you really start to take a step back

498
00:17:23.750 --> 00:17:24.890
- and think about, like,

499
00:17:25.269 --> 00:17:27.589
- what's the baseline? What are the metrics that

500
00:17:27.589 --> 00:17:30.250
- matter here? Like, what is success criteria?

501
00:17:31.224 --> 00:17:33.164
- And what's the criteria that

502
00:17:33.544 --> 00:17:36.204
- I'm going to sell to my customers

503
00:17:36.664 --> 00:17:38.585
- and what are my customers going to take

504
00:17:38.585 --> 00:17:39.724
- as evidence

505
00:17:40.184 --> 00:17:41.164
- of success

506
00:17:42.345 --> 00:17:43.404
- along the way?

507
00:17:44.230 --> 00:17:45.829
- And then I think the other thing you

508
00:17:45.829 --> 00:17:46.649
- get to sell

509
00:17:47.589 --> 00:17:50.390
- is LLMs are good at some things or

510
00:17:50.390 --> 00:17:51.450
- great at some things,

511
00:17:51.990 --> 00:17:54.250
- but I found especially in M365

512
00:17:54.630 --> 00:17:56.409
- land, they love to hallucinate.

513
00:17:58.404 --> 00:18:00.505
- Asking an LLM to fire off a WorkIQ

514
00:18:00.644 --> 00:18:03.285
- query is sometimes like, Whew, where did you

515
00:18:03.285 --> 00:18:04.984
- come up with that thing?

516
00:18:05.445 --> 00:18:07.785
- So I think making sure that there's more

517
00:18:08.164 --> 00:18:10.424
- human in the loop and expertise around

518
00:18:10.950 --> 00:18:12.169
- hallucinated reports

519
00:18:12.630 --> 00:18:15.269
- or doing those gut checks, right? So you're

520
00:18:15.269 --> 00:18:17.750
- still an expert in your space. You're going

521
00:18:17.750 --> 00:18:19.909
- to know, and it's probably not going to

522
00:18:19.909 --> 00:18:21.589
- pass the sniff test for you if somebody

523
00:18:21.589 --> 00:18:22.490
- goes and runs

524
00:18:23.015 --> 00:18:24.715
- a random query with an LLM

525
00:18:25.174 --> 00:18:26.555
- against something versus

526
00:18:27.095 --> 00:18:29.414
- you just know the way this telemetry comes

527
00:18:29.414 --> 00:18:31.674
- together and what can be presented,

528
00:18:32.855 --> 00:18:34.315
- out of it kind of thing.

529
00:18:35.174 --> 00:18:35.674
- So

530
00:18:36.455 --> 00:18:37.755
- you get a couple different

531
00:18:38.900 --> 00:18:41.220
- gut checks in there, effectively, like the advisory

532
00:18:41.220 --> 00:18:41.720
- stuff,

533
00:18:42.339 --> 00:18:45.539
- which is still important. Right? And, like, that's

534
00:18:45.539 --> 00:18:46.039
- not

535
00:18:46.819 --> 00:18:47.640
- not an inconsequential

536
00:18:48.019 --> 00:18:48.519
- thing.

537
00:18:50.099 --> 00:18:52.994
- If you're managing file storage today, you've probably

538
00:18:53.134 --> 00:18:55.775
- felt the pressure. Refresh cycles are harder to

539
00:18:55.775 --> 00:18:59.214
- plan, costs and complexity are increasing, especially as

540
00:18:59.214 --> 00:19:01.315
- file workloads scale across regions.

541
00:19:01.615 --> 00:19:04.920
- That's why Microsoft customers trust Nasuni. As an

542
00:19:05.080 --> 00:19:06.619
- Azure certified software,

543
00:19:07.000 --> 00:19:09.960
- Nasuni provides a global file system designed for

544
00:19:09.960 --> 00:19:13.880
- enterprise scale environments, keeping file data secure, governed,

545
00:19:13.880 --> 00:19:17.420
- and accessible across Azure environments without added infrastructure

546
00:19:17.720 --> 00:19:18.220
- complexity.

547
00:19:18.654 --> 00:19:21.775
- It's the foundation to keep your unstructured data

548
00:19:21.775 --> 00:19:23.714
- stable even as your infrastructure

549
00:19:24.015 --> 00:19:26.255
- evolves. To see how much you could save

550
00:19:26.255 --> 00:19:32.579
- while keeping your initiatives on track, visit nasuni.com/tco.

551
00:19:32.740 --> 00:19:37.399
- That's nasuni.com/tco.

552
00:19:38.579 --> 00:19:39.559
- That's another

553
00:19:39.859 --> 00:19:41.640
- area that I've kinda found

554
00:19:42.179 --> 00:19:45.059
- in talking to different people and where people

555
00:19:45.059 --> 00:19:47.480
- are still coming to me for questions is

556
00:19:47.875 --> 00:19:49.815
- what you just said, some of the advisory

557
00:19:49.954 --> 00:19:53.494
- and the architecture type stuff. And that's where

558
00:19:54.115 --> 00:19:55.414
- a lot of that expertise

559
00:19:55.875 --> 00:19:58.275
- and what people still need is, I have

560
00:19:58.275 --> 00:19:59.794
- found AI is really good at looking at

561
00:19:59.794 --> 00:20:01.474
- data. I can go take a whole bunch

562
00:20:01.474 --> 00:20:03.470
- of data from Microsoft three sixty five, and

563
00:20:03.470 --> 00:20:04.369
- it can tell

564
00:20:04.990 --> 00:20:05.970
- me where are

565
00:20:06.509 --> 00:20:09.070
- the shortcomings? Where do I have security gaps?

566
00:20:09.070 --> 00:20:11.089
- Where do I have potential misconfigurations?

567
00:20:11.950 --> 00:20:13.250
- Okay, great. I've identified

568
00:20:13.549 --> 00:20:15.009
- all of these things now,

569
00:20:15.309 --> 00:20:16.450
- leveraging AI

570
00:20:16.910 --> 00:20:18.805
- of what needs to be done. How do

571
00:20:18.805 --> 00:20:21.525
- you go actually interface with the users now?

572
00:20:21.525 --> 00:20:22.744
- How do you go start

573
00:20:23.045 --> 00:20:24.025
- taking everything

574
00:20:24.325 --> 00:20:26.105
- that maybe you've identified

575
00:20:26.644 --> 00:20:27.144
- and

576
00:20:27.525 --> 00:20:29.765
- architecting out a solution to solve all of

577
00:20:29.765 --> 00:20:32.345
- that, where you're not going to

578
00:20:32.805 --> 00:20:35.610
- impact the business? Where you're figuring out how

579
00:20:35.610 --> 00:20:37.610
- do I start piloting this, how do I

580
00:20:37.610 --> 00:20:39.450
- make these tweaks, how do I make these

581
00:20:39.450 --> 00:20:43.070
- changes, what does this overall architecture look like

582
00:20:43.210 --> 00:20:44.029
- that maybe

583
00:20:44.410 --> 00:20:46.330
- solve some of this? And I think that's

584
00:20:46.330 --> 00:20:47.930
- where there's still a lot of value to

585
00:20:47.930 --> 00:20:49.704
- when you are doing the Microsoft three sixty

586
00:20:49.704 --> 00:20:50.204
- five

587
00:20:50.505 --> 00:20:52.505
- consulting, where you are still doing the Azure

588
00:20:52.505 --> 00:20:53.565
- consulting is

589
00:20:54.105 --> 00:20:55.865
- it's getting a little bit more into some

590
00:20:55.865 --> 00:20:57.384
- of those I don't know if you'd call

591
00:20:57.384 --> 00:21:00.984
- them soft skills or the more architecture type

592
00:21:00.984 --> 00:21:03.164
- skills, the design skills

593
00:21:03.919 --> 00:21:04.419
- that

594
00:21:04.720 --> 00:21:07.200
- AI can give you ideas, but AI also

595
00:21:07.200 --> 00:21:09.679
- hasn't been in there. Part of the advantage

596
00:21:09.679 --> 00:21:11.440
- I've had is customers ask me, Well, how

597
00:21:11.440 --> 00:21:13.039
- did you do this with another client? What

598
00:21:13.039 --> 00:21:15.140
- worked? What didn't work? From

599
00:21:15.599 --> 00:21:19.734
- a working with humans perspective, from a things

600
00:21:19.734 --> 00:21:22.054
- you don't necessarily think about in terms of

601
00:21:22.054 --> 00:21:24.855
- a deployment plan or where users are going

602
00:21:24.855 --> 00:21:26.774
- to get tripped up, all of that type

603
00:21:26.774 --> 00:21:27.434
- of stuff,

604
00:21:28.214 --> 00:21:29.950
- there's still a lot

605
00:21:30.490 --> 00:21:31.069
- of value

606
00:21:31.529 --> 00:21:32.890
- in that in the AI world, and I

607
00:21:32.890 --> 00:21:34.349
- think where a lot of consultants

608
00:21:35.049 --> 00:21:37.369
- start focusing on this AI world where it's

609
00:21:37.369 --> 00:21:39.289
- good at producing results, it's good at looking

610
00:21:39.289 --> 00:21:41.130
- at data, but it's not always good at

611
00:21:41.130 --> 00:21:41.630
- knowing

612
00:21:42.245 --> 00:21:44.325
- how is this going to impact users and

613
00:21:44.325 --> 00:21:45.625
- how do I work with users

614
00:21:46.005 --> 00:21:46.505
- to

615
00:21:48.325 --> 00:21:51.205
- react to architect, whatever that may be, to

616
00:21:51.205 --> 00:21:53.305
- whatever I discovered and

617
00:21:54.210 --> 00:21:54.710
- investigated

618
00:21:55.569 --> 00:21:59.509
- using AI as a support tool, as another

619
00:21:59.569 --> 00:22:00.769
- tool in my toolbox? Jason Brett (3nine thirty

620
00:22:00.769 --> 00:22:03.410
- seven): The expertise of consultants doesn't go away

621
00:22:03.410 --> 00:22:05.029
- in this world, would be my

622
00:22:05.410 --> 00:22:05.910
- assertion,

623
00:22:07.285 --> 00:22:09.224
- I think that's what you're saying too is

624
00:22:09.684 --> 00:22:10.184
- there's

625
00:22:10.644 --> 00:22:13.525
- a certain degree of the tools that exist

626
00:22:13.525 --> 00:22:15.144
- today can tell you

627
00:22:15.445 --> 00:22:15.945
- what.

628
00:22:17.045 --> 00:22:19.285
- They can tell you how, they can't always

629
00:22:19.285 --> 00:22:20.345
- tell you why,

630
00:22:21.150 --> 00:22:23.230
- and they can't always tell you how in

631
00:22:23.230 --> 00:22:26.690
- context of the overall constraints of an environment.

632
00:22:26.830 --> 00:22:28.289
- So if I think about something

633
00:22:29.309 --> 00:22:30.690
- like Secure Score,

634
00:22:31.230 --> 00:22:31.970
- in isolation

635
00:22:32.509 --> 00:22:34.269
- sounds like a great thing. Like, hey, I

636
00:22:34.269 --> 00:22:35.230
- wanna go from

637
00:22:36.025 --> 00:22:37.545
- what's the max for a secure score these

638
00:22:37.545 --> 00:22:39.484
- days, 800, something like that?

639
00:22:40.184 --> 00:22:41.884
- Like, I don't know. You sit down and

640
00:22:42.265 --> 00:22:43.964
- you look at your secure secure secure score

641
00:22:44.265 --> 00:22:46.025
- and you go, oh, I'm 450, and I

642
00:22:46.025 --> 00:22:48.265
- wanna go to 800. Well, maybe going to

643
00:22:48.265 --> 00:22:50.904
- 800 isn't the best idea because you're gonna

644
00:22:50.904 --> 00:22:52.319
- do a lot of things that that maybe

645
00:22:52.319 --> 00:22:54.500
- aren't applicable to your environment.

646
00:22:54.960 --> 00:22:56.400
- But I guarantee when you go out and

647
00:22:56.400 --> 00:22:58.880
- look at your score, it's gonna keep pushing

648
00:22:58.880 --> 00:22:59.539
- you insane.

649
00:23:00.400 --> 00:23:01.140
- Do more.

650
00:23:01.679 --> 00:23:04.000
- Same thing with, like, co pilot readiness. I

651
00:23:04.000 --> 00:23:05.759
- think that would be another kind of big

652
00:23:05.759 --> 00:23:08.134
- area in this kind of current

653
00:23:08.515 --> 00:23:09.734
- phase of M365,

654
00:23:10.195 --> 00:23:12.035
- things like this. It's like, you can go

655
00:23:12.035 --> 00:23:15.394
- get a Copilot readiness report. Is that readiness

656
00:23:15.394 --> 00:23:17.154
- report actually going to get you to the

657
00:23:17.154 --> 00:23:20.455
- spot where you can configure your licensing properly,

658
00:23:20.595 --> 00:23:22.134
- where you can go and configure

659
00:23:22.890 --> 00:23:26.170
- your, not just your environment configuration, but also

660
00:23:26.170 --> 00:23:28.410
- your SharePoint sites and everything else that are

661
00:23:28.410 --> 00:23:29.070
- out there

662
00:23:29.690 --> 00:23:31.289
- in a way that are gonna, like, deliver

663
00:23:31.289 --> 00:23:33.869
- the right amount of value for your business?

664
00:23:35.529 --> 00:23:36.349
- I don't know.

665
00:23:37.049 --> 00:23:39.524
- Probably not. Right? That's still where you're paying

666
00:23:39.524 --> 00:23:40.345
- somebody else

667
00:23:41.605 --> 00:23:42.664
- for their

668
00:23:43.125 --> 00:23:43.625
- expertise

669
00:23:44.404 --> 00:23:45.784
- all along the way. So

670
00:23:46.244 --> 00:23:48.644
- for something like Secure Score, you don't wanna

671
00:23:48.644 --> 00:23:50.244
- have a customer walk in and just think

672
00:23:50.244 --> 00:23:52.085
- like, oh, hey. There has to be this

673
00:23:52.085 --> 00:23:53.065
- wild movement.

674
00:23:53.809 --> 00:23:55.509
- Like, I I need to go from

675
00:23:56.289 --> 00:23:57.750
- $4.50 to 800.

676
00:23:57.970 --> 00:23:59.650
- No, you don't. Like, you have to go

677
00:23:59.650 --> 00:24:01.269
- from maybe a different

678
00:24:01.730 --> 00:24:03.190
- a different x to y,

679
00:24:03.569 --> 00:24:05.890
- but, like, here's what you're getting out of

680
00:24:05.890 --> 00:24:08.664
- that. Like, here's the reduction in risk. Here's

681
00:24:08.664 --> 00:24:10.765
- the improvement in your posture

682
00:24:11.545 --> 00:24:13.164
- within your organization,

683
00:24:15.545 --> 00:24:16.684
- those kinds of things.

684
00:24:17.625 --> 00:24:18.924
- So I think that's all

685
00:24:19.384 --> 00:24:22.025
- good stuff and it doesn't take away from

686
00:24:22.025 --> 00:24:23.964
- the expertise that folks have

687
00:24:24.400 --> 00:24:25.779
- built up over the years.

688
00:24:26.480 --> 00:24:28.400
- There is that adage, right? When you have

689
00:24:28.400 --> 00:24:30.079
- somebody, like a trades person come into your

690
00:24:30.079 --> 00:24:31.920
- house, so like, Hey, you get a plumber

691
00:24:31.920 --> 00:24:34.079
- and it takes a plumber ten minutes to

692
00:24:34.079 --> 00:24:35.759
- fix the leak under your sink, but you

693
00:24:35.759 --> 00:24:37.359
- have to pay them for an hour of

694
00:24:37.359 --> 00:24:38.099
- their time.

695
00:24:38.400 --> 00:24:40.855
- Well, yeah, you're not just paying them for

696
00:24:40.855 --> 00:24:41.974
- the hour to pay them for the hour,

697
00:24:41.974 --> 00:24:44.295
- you're paying them for their ten, twenty plus

698
00:24:44.295 --> 00:24:46.214
- years of experience, and that's how they're able

699
00:24:46.214 --> 00:24:48.234
- to get it done in ten minutes. So

700
00:24:48.775 --> 00:24:51.180
- that part's not going away either in this

701
00:24:51.180 --> 00:24:52.406
- world. Jack Mallers (zero fifty seven:forty seven): I

702
00:24:52.406 --> 00:24:53.534
- had that the other day. I tried to

703
00:24:53.534 --> 00:24:54.860
- fix my own Well, I did fix my

704
00:24:54.860 --> 00:24:56.779
- own shower, Scott. I fixed a leak in

705
00:24:56.779 --> 00:24:58.779
- my shower, but it took me eight or

706
00:24:58.779 --> 00:24:59.440
- nine hours.

707
00:25:00.380 --> 00:25:01.820
- And had I paid a plumber, it probably

708
00:25:01.820 --> 00:25:03.500
- would have taken him two because he would

709
00:25:03.500 --> 00:25:06.075
- have known all the tricks and this is

710
00:25:06.075 --> 00:25:09.035
- how you get this particular part out of

711
00:25:09.035 --> 00:25:11.035
- the shower to stop the leak, and I

712
00:25:11.035 --> 00:25:12.875
- ended up, like, three trips to Home Depot

713
00:25:12.875 --> 00:25:14.234
- and a trip to a friend's house for

714
00:25:14.234 --> 00:25:16.315
- tools and all of this. So, yeah, I

715
00:25:16.315 --> 00:25:19.674
- think that absolutely still applies to this world

716
00:25:19.674 --> 00:25:21.849
- as well. And another one of these, going

717
00:25:21.849 --> 00:25:23.369
- back to the Secure Score, I'm working with

718
00:25:23.369 --> 00:25:25.289
- a client right now, and they're like, We

719
00:25:25.289 --> 00:25:28.009
- need to implement CIS benchmarks across our entire

720
00:25:28.009 --> 00:25:31.369
- environment. CIS has a great set of here's

721
00:25:31.369 --> 00:25:33.690
- everything you need to do. It's six fifty

722
00:25:33.690 --> 00:25:36.194
- seven lines in Excel spreadsheet. Hey, I did

723
00:25:36.194 --> 00:25:38.294
- a great job at looking through the PDF

724
00:25:38.434 --> 00:25:41.075
- and creating the Excel spreadsheet. It gives me

725
00:25:41.154 --> 00:25:42.755
- did a great job ahead of it. Let's

726
00:25:42.755 --> 00:25:44.355
- look at all the categories. How can we

727
00:25:44.355 --> 00:25:46.134
- maybe lump these settings together?

728
00:25:48.769 --> 00:25:49.909
- How can we best

729
00:25:50.450 --> 00:25:53.889
- deploy different settings in a logical way so

730
00:25:53.889 --> 00:25:55.669
- settings are grouped together logically?

731
00:25:56.210 --> 00:25:58.690
- But it sure can't tell me which users

732
00:25:58.690 --> 00:26:01.169
- are using which functionality, or how is turning

733
00:26:01.169 --> 00:26:03.794
- on this particular setting going to affect users

734
00:26:03.794 --> 00:26:05.335
- and finance versus IT,

735
00:26:06.514 --> 00:26:08.835
- how are we gonna go through and push

736
00:26:08.835 --> 00:26:10.194
- all these 650

737
00:26:10.194 --> 00:26:12.434
- settings out to 6,000

738
00:26:12.434 --> 00:26:14.694
- users without disrupting the business,

739
00:26:15.859 --> 00:26:17.380
- that's where a lot of that value still

740
00:26:17.380 --> 00:26:19.220
- comes in. My computer is beeping at me

741
00:26:19.220 --> 00:26:21.000
- with the words. It's beeping.

742
00:26:21.779 --> 00:26:23.779
- We've talked about this for years too. Right?

743
00:26:23.779 --> 00:26:25.220
- Like, when we went from on prem to

744
00:26:25.220 --> 00:26:27.380
- cloud, how what you do and maybe how

745
00:26:27.380 --> 00:26:30.214
- you do things changes as technology evolves. I

746
00:26:30.214 --> 00:26:32.234
- think the age of AI consulting or

747
00:26:32.535 --> 00:26:34.455
- AI assisted consulting, we're kind of at that

748
00:26:34.455 --> 00:26:37.174
- point now where And we talked about this

749
00:26:37.174 --> 00:26:38.934
- on an episode, I can't remember which one,

750
00:26:38.934 --> 00:26:40.695
- where a lot of the same stuff, it's

751
00:26:40.695 --> 00:26:43.494
- not like jobs as Microsoft three sixty five

752
00:26:43.494 --> 00:26:45.630
- consultants, Azure consultants is going to go away,

753
00:26:45.789 --> 00:26:48.130
- but you do need to start thinking through

754
00:26:48.349 --> 00:26:50.430
- how does your job as a consultant change,

755
00:26:50.430 --> 00:26:52.609
- and where are you going to bring

756
00:26:52.990 --> 00:26:53.490
- value

757
00:26:54.109 --> 00:26:56.509
- now? Because now you do have new tools,

758
00:26:56.509 --> 00:26:58.609
- you have new ways you can bring value,

759
00:26:59.215 --> 00:27:01.615
- maybe you can save time doing one thing,

760
00:27:01.615 --> 00:27:03.615
- but you're going to spend more time bringing

761
00:27:03.615 --> 00:27:06.355
- value in another way. There's that continued

762
00:27:06.815 --> 00:27:08.975
- evolution in this consulting world. I've been doing

763
00:27:08.975 --> 00:27:10.654
- it for twenty five years now, and I

764
00:27:10.654 --> 00:27:12.015
- can tell you what I did twenty five

765
00:27:12.015 --> 00:27:14.275
- years ago, if I kept doing that today,

766
00:27:14.559 --> 00:27:16.259
- probably wouldn't have any work to do.

767
00:27:16.960 --> 00:27:19.380
- It's you're always thinking

768
00:27:19.680 --> 00:27:23.299
- how do these changing tools, the changing landscape

769
00:27:23.759 --> 00:27:25.599
- change what I do and where can I

770
00:27:25.599 --> 00:27:27.615
- continue to provide value and

771
00:27:27.934 --> 00:27:30.595
- leverage the changing in technology to my benefit?

772
00:27:30.654 --> 00:27:32.654
- And I think we're absolutely in that spot

773
00:27:32.654 --> 00:27:33.454
- with AI too. Brad Thomas (3three fifty seven):

774
00:27:33.454 --> 00:27:34.835
- How much do you think about

775
00:27:35.775 --> 00:27:38.174
- in the accelerated delivery world? So you can

776
00:27:38.174 --> 00:27:39.234
- create these artifacts

777
00:27:39.535 --> 00:27:41.474
- quicker, right? So you can go create,

778
00:27:42.480 --> 00:27:44.660
- well, something can go and create

779
00:27:45.119 --> 00:27:47.279
- a shell script or a Python thing that's

780
00:27:47.279 --> 00:27:49.539
- gonna read your PDF, convert it to Excel,

781
00:27:49.680 --> 00:27:50.880
- blah, blah, blah, blah, blah. Do all the

782
00:27:50.880 --> 00:27:52.480
- things it needs to do, and it's gonna

783
00:27:52.480 --> 00:27:53.380
- push it out there.

784
00:27:54.414 --> 00:27:56.815
- Great, you can go faster, but still you

785
00:27:56.815 --> 00:27:59.394
- need that human in the loop thing. So

786
00:27:59.615 --> 00:28:03.154
- there's now maybe a need for increased review

787
00:28:03.295 --> 00:28:05.634
- or more diligence around review.

788
00:28:06.734 --> 00:28:08.434
- And yeah, I think

789
00:28:10.509 --> 00:28:12.190
- my assertion would be you have to put

790
00:28:12.190 --> 00:28:14.049
- that diligence in because

791
00:28:14.509 --> 00:28:15.009
- it's

792
00:28:15.390 --> 00:28:17.630
- your reputation on the line because now you're

793
00:28:17.630 --> 00:28:18.769
- selling outcomes.

794
00:28:19.470 --> 00:28:21.390
- You're not just selling hours. It's not like,

795
00:28:21.390 --> 00:28:23.384
- oh, hey, Buy ten hours from me, and

796
00:28:23.384 --> 00:28:25.065
- if you need more, that's great. If we

797
00:28:25.065 --> 00:28:25.724
- don't use

798
00:28:26.184 --> 00:28:26.845
- them, whatever.

799
00:28:28.024 --> 00:28:30.264
- You're kinda like, in that example of taking,

800
00:28:30.264 --> 00:28:32.424
- like, CIS benchmarks and bringing them through to

801
00:28:32.424 --> 00:28:34.744
- an environment, like, you're selling an outcome of,

802
00:28:34.744 --> 00:28:35.804
- like, CIS

803
00:28:37.730 --> 00:28:38.230
- implementation

804
00:28:39.169 --> 00:28:41.109
- across these categories or across

805
00:28:42.450 --> 00:28:45.409
- 50% of these in this category, 25% over

806
00:28:45.409 --> 00:28:46.869
- here, or 100%

807
00:28:47.169 --> 00:28:49.490
- of everything that's out there kind of thing.

808
00:28:49.490 --> 00:28:50.855
- So So that's another one that I think

809
00:28:50.855 --> 00:28:52.794
- is interesting to me is, like, the whole

810
00:28:53.654 --> 00:28:56.375
- risk reward thing or the ratio for, like,

811
00:28:56.375 --> 00:28:56.875
- reputational

812
00:28:57.255 --> 00:29:00.234
- harm. Like, should you just generate something fast

813
00:29:00.375 --> 00:29:02.774
- and it goes out there and it doesn't

814
00:29:02.774 --> 00:29:03.914
- align to

815
00:29:05.080 --> 00:29:08.059
- either the outcomes that customers were purchasing

816
00:29:09.080 --> 00:29:11.240
- or it's just like wildly wrong. Right? So

817
00:29:11.240 --> 00:29:13.240
- the customer thinks they're getting an outcome and

818
00:29:13.240 --> 00:29:14.759
- then they walk away happy and you're like,

819
00:29:14.759 --> 00:29:16.680
- oh, great. I delivered it. But it turns

820
00:29:16.680 --> 00:29:18.140
- out that nobody actually

821
00:29:18.544 --> 00:29:21.265
- got what they wanted or the customer didn't

822
00:29:21.265 --> 00:29:23.265
- achieve what they wanted in that world. James

823
00:29:23.265 --> 00:29:24.384
- Lavish (zero 50 three:thirty seven): And it doesn't

824
00:29:24.384 --> 00:29:26.164
- align. And this is where I've

825
00:29:26.464 --> 00:29:28.404
- absolutely spent more diligence.

826
00:29:29.025 --> 00:29:31.285
- To your point, I can create an assessment

827
00:29:31.345 --> 00:29:34.980
- document, but I do spend more time reading

828
00:29:34.980 --> 00:29:37.220
- through it because maybe AI generated a lot

829
00:29:37.220 --> 00:29:37.960
- of it. And

830
00:29:38.339 --> 00:29:39.859
- I don't want it to have things in

831
00:29:39.859 --> 00:29:42.099
- there that are blatantly wrong. To your point

832
00:29:42.099 --> 00:29:43.940
- earlier, I'm going to read through it and

833
00:29:43.940 --> 00:29:45.799
- make sure I don't have any

834
00:29:46.099 --> 00:29:47.159
- To make sure that

835
00:29:47.779 --> 00:29:49.914
- my gut instinct about what should be there

836
00:29:49.914 --> 00:29:51.274
- and what I know should be there and

837
00:29:51.274 --> 00:29:53.054
- what I've seen in the past is correct,

838
00:29:53.194 --> 00:29:54.494
- but also taking

839
00:29:55.034 --> 00:29:57.034
- some of that and aligning it to what

840
00:29:57.034 --> 00:29:57.694
- I know

841
00:29:58.075 --> 00:30:00.794
- the customer needs. Because leading up to that,

842
00:30:00.794 --> 00:30:02.634
- I'll have phone calls with customers. Oh, we

843
00:30:02.634 --> 00:30:05.000
- didn't do this for this and this reason,

844
00:30:05.140 --> 00:30:05.640
- or

845
00:30:06.500 --> 00:30:08.660
- we tried this and it didn't work for

846
00:30:08.660 --> 00:30:10.259
- x, y, and z reason. There's a lot

847
00:30:10.259 --> 00:30:11.320
- of intricacies

848
00:30:12.099 --> 00:30:12.599
- that

849
00:30:13.220 --> 00:30:13.720
- I

850
00:30:14.019 --> 00:30:16.180
- may know, that I've written down based on

851
00:30:16.180 --> 00:30:18.200
- conversations with clients that

852
00:30:18.644 --> 00:30:19.545
- may not necessarily

853
00:30:19.924 --> 00:30:21.845
- align with some of these outcomes. So I'm

854
00:30:21.845 --> 00:30:24.644
- being very diligent in going through here to

855
00:30:24.644 --> 00:30:25.945
- make sure that

856
00:30:26.404 --> 00:30:27.945
- maybe what got generated

857
00:30:28.644 --> 00:30:31.365
- aligns based on all the other conversations I've

858
00:30:31.365 --> 00:30:33.869
- had with the client and all the other,

859
00:30:33.869 --> 00:30:35.710
- the history I have with that client, what

860
00:30:35.710 --> 00:30:37.549
- I know about their environment, what I know

861
00:30:37.549 --> 00:30:38.529
- about their users.

862
00:30:39.789 --> 00:30:41.809
- And that's where I think some of the,

863
00:30:42.990 --> 00:30:44.690
- where you spend your time shifts

864
00:30:45.865 --> 00:30:47.944
- Because you are doing more of that gut

865
00:30:47.944 --> 00:30:49.005
- checking, that alignment

866
00:30:49.384 --> 00:30:51.544
- after the fact now, as opposed to when

867
00:30:51.544 --> 00:30:53.404
- I would maybe run PowerShell scripts

868
00:30:53.944 --> 00:30:56.345
- and write the entire document by hand. I

869
00:30:56.345 --> 00:30:57.865
- know what's in the document because I wrote

870
00:30:57.865 --> 00:31:00.130
- it all, and I'm doing that as I'm

871
00:31:00.130 --> 00:31:02.273
- writing it, now I'm just doing it afterwards.

872
00:31:02.273 --> 00:31:03.990
- Matthew Piepenburg (3seven 50: It's a shift there.

873
00:31:05.169 --> 00:31:05.829
- I wonder

874
00:31:07.250 --> 00:31:09.730
- how much you're running into this. So maybe

875
00:31:09.730 --> 00:31:10.549
- one last question

876
00:31:10.849 --> 00:31:12.789
- we go through to pick your brain here.

877
00:31:14.049 --> 00:31:14.549
- So

878
00:31:15.434 --> 00:31:16.575
- there's been this thing

879
00:31:17.034 --> 00:31:17.934
- I think where

880
00:31:18.875 --> 00:31:19.774
- particularly in

881
00:31:20.154 --> 00:31:23.054
- the fixed delivery space MSPs especially, you develop

882
00:31:23.515 --> 00:31:24.894
- your set of

883
00:31:25.595 --> 00:31:27.515
- IP. So you end up with this bank

884
00:31:27.515 --> 00:31:28.174
- of scripts,

885
00:31:28.554 --> 00:31:29.615
- things like that.

886
00:31:30.319 --> 00:31:33.460
- I never ran into customers really asking for,

887
00:31:33.519 --> 00:31:35.279
- like, hey, what's the thing you're running? Or

888
00:31:35.279 --> 00:31:36.640
- what do you actually run under the hood

889
00:31:36.640 --> 00:31:38.480
- to do that assessment? They always just wanted

890
00:31:38.480 --> 00:31:40.400
- the assessment at the end. It's like, again,

891
00:31:40.400 --> 00:31:42.339
- get me to the outcome

892
00:31:42.799 --> 00:31:44.079
- that you told me we're going to get

893
00:31:44.079 --> 00:31:47.164
- it to. I wonder, like, are customers kinda

894
00:31:47.305 --> 00:31:48.825
- pushing back at all, or do you find

895
00:31:48.825 --> 00:31:50.045
- them coming in and

896
00:31:51.625 --> 00:31:54.444
- really asking for some kind of

897
00:31:55.944 --> 00:31:58.169
- visibility into, like, the the things that you

898
00:31:58.169 --> 00:32:00.089
- are running or what you're creating and what's

899
00:32:00.089 --> 00:32:01.690
- out there. Because I like, there is a

900
00:32:01.690 --> 00:32:04.009
- certain, like, kinda risk matrix as well to

901
00:32:04.009 --> 00:32:05.529
- think about, like, oh, hey. I hired this

902
00:32:05.529 --> 00:32:07.130
- person to come into my environment. They say

903
00:32:07.130 --> 00:32:09.450
- they're gonna run a a PowerShell script or

904
00:32:09.450 --> 00:32:11.849
- they wanna install this application on my server

905
00:32:11.849 --> 00:32:12.349
- to

906
00:32:13.035 --> 00:32:14.735
- be able to do this assessment, or

907
00:32:15.115 --> 00:32:17.195
- they're asking for a user account with this

908
00:32:17.195 --> 00:32:19.434
- level of permissions so they can go against

909
00:32:19.434 --> 00:32:20.955
- the Graph API and get what they need

910
00:32:20.955 --> 00:32:22.815
- to be. Like, do you find them asking

911
00:32:22.875 --> 00:32:25.295
- for those artifacts for evaluation

912
00:32:26.460 --> 00:32:26.960
- or

913
00:32:27.259 --> 00:32:29.839
- anything like that? I haven't seen that

914
00:32:30.140 --> 00:32:32.720
- change a whole lot in terms of

915
00:32:33.339 --> 00:32:34.640
- what they're asking for.

916
00:32:35.339 --> 00:32:37.419
- Before this, over the last few years, I

917
00:32:37.419 --> 00:32:39.179
- will have customers ask for a script. They're

918
00:32:39.179 --> 00:32:41.279
- like, do you have a PowerShell script or

919
00:32:41.554 --> 00:32:43.315
- you generated this. Do you have the script

920
00:32:43.315 --> 00:32:45.174
- that you used to export all of that?

921
00:32:46.355 --> 00:32:49.575
- I haven't seen that changing a whole lot.

922
00:32:49.634 --> 00:32:51.095
- Maybe now they're asking

923
00:32:51.714 --> 00:32:54.134
- I had one I was talking to recently

924
00:32:54.355 --> 00:32:57.090
- that was like, Do you have the skills,

925
00:32:57.090 --> 00:32:59.490
- the MD files, the skills that you used

926
00:32:59.490 --> 00:33:00.549
- in AI

927
00:33:00.930 --> 00:33:01.430
- to

928
00:33:01.730 --> 00:33:03.269
- help you generate this?

929
00:33:04.130 --> 00:33:05.910
- And that's one of those, to your point,

930
00:33:05.970 --> 00:33:07.990
- I think that starts turning into more intellectual

931
00:33:08.130 --> 00:33:10.394
- property. I will say in the past, if

932
00:33:10.394 --> 00:33:12.214
- I have a client I'm working with

933
00:33:12.674 --> 00:33:14.515
- and I generate a certain report form and

934
00:33:14.515 --> 00:33:16.835
- they want some of that, this may be

935
00:33:16.835 --> 00:33:18.194
- good, may be bad, I tend to share

936
00:33:18.194 --> 00:33:19.554
- it with them. They don't need to come

937
00:33:19.554 --> 00:33:20.994
- back to me and pay me every three

938
00:33:20.994 --> 00:33:22.855
- months to generate the same thing.

939
00:33:23.700 --> 00:33:25.880
- I would rather provide value in other ways,

940
00:33:26.980 --> 00:33:29.779
- help them with new things rather than just

941
00:33:29.779 --> 00:33:31.779
- generating the same outcomes for them over and

942
00:33:31.779 --> 00:33:33.640
- over again. Part of that is my personality,

943
00:33:33.700 --> 00:33:35.424
- I get bored with that. I don't need

944
00:33:35.424 --> 00:33:37.424
- to do the same thing every month if

945
00:33:37.424 --> 00:33:38.724
- they want to do it themselves.

946
00:33:39.105 --> 00:33:40.705
- I'd rather have them come to me with

947
00:33:40.705 --> 00:33:43.184
- their new challenges, their new struggles, and help

948
00:33:43.184 --> 00:33:44.325
- them with the new stuff.

949
00:33:44.945 --> 00:33:47.585
- But that is one area in terms of

950
00:33:47.585 --> 00:33:49.585
- asking for some of the artifacts and stuff

951
00:33:49.585 --> 00:33:51.640
- behind the scenes. What they may ask for

952
00:33:51.640 --> 00:33:54.680
- has changed, but the level of them asking

953
00:33:54.680 --> 00:33:56.599
- or the amount of times they ask, I

954
00:33:56.599 --> 00:33:58.619
- haven't seen them asking for it

955
00:33:58.920 --> 00:34:00.485
- more than maybe they did in the past.

956
00:34:00.485 --> 00:34:01.240
- Josh Young (zero fifty seven:forty seven): Gotcha. I

957
00:34:01.240 --> 00:34:02.920
- wonder if that shifts more and more over

958
00:34:02.920 --> 00:34:05.015
- time, or if customers are just going out

959
00:34:05.015 --> 00:34:06.954
- and creating their own stuff. Right? So

960
00:34:07.494 --> 00:34:09.574
- it goes both ways. Like, you can kinda

961
00:34:09.574 --> 00:34:11.655
- iterate faster on the front end and then,

962
00:34:11.655 --> 00:34:13.114
- therefore, go do these deliveries.

963
00:34:14.215 --> 00:34:16.135
- I would imagine that there's also a subset

964
00:34:16.135 --> 00:34:18.074
- of customers I can say, like, oh, hey.

965
00:34:18.590 --> 00:34:20.909
- Ben gave me this great report on my

966
00:34:20.909 --> 00:34:22.349
- environment. It gave me a set of action

967
00:34:22.349 --> 00:34:24.390
- items to to go and do. What if

968
00:34:24.390 --> 00:34:26.590
- I just, like, backport that report and say,

969
00:34:26.590 --> 00:34:28.909
- like, hey. How could I generate this like,

970
00:34:28.909 --> 00:34:30.590
- throw that PDF or that Word doc at

971
00:34:30.590 --> 00:34:32.269
- an LOM and say, how could I generate

972
00:34:32.269 --> 00:34:33.949
- this report myself? Like, go write me a

973
00:34:33.949 --> 00:34:34.985
- bunch of scripts, right,

974
00:34:35.445 --> 00:34:37.925
- or PowerShell bash, you know, whatever it happens

975
00:34:37.925 --> 00:34:38.505
- to be

976
00:34:39.445 --> 00:34:41.865
- to spin things up. It will be interesting

977
00:34:42.005 --> 00:34:42.664
- to see

978
00:34:43.045 --> 00:34:45.305
- how that changes is even what,

979
00:34:45.925 --> 00:34:47.945
- I think what IP changes.

980
00:34:49.079 --> 00:34:51.180
- This is not me. I had this conversation,

981
00:34:51.239 --> 00:34:52.619
- though, recently with

982
00:34:53.000 --> 00:34:54.059
- one of my contractors

983
00:34:54.440 --> 00:34:56.680
- where there were all these There's a lot

984
00:34:56.680 --> 00:34:58.539
- of websites out there where

985
00:34:58.840 --> 00:35:02.025
- people were providing a lot of value for

986
00:35:02.025 --> 00:35:04.284
- writing PowerShell script. It's like, Here's a PowerShell

987
00:35:04.344 --> 00:35:05.244
- script to go

988
00:35:05.625 --> 00:35:08.284
- do ABC. Go export all my mailboxes.

989
00:35:08.744 --> 00:35:09.244
- Go

990
00:35:10.984 --> 00:35:13.944
- bulk make this change on users in Entra.

991
00:35:13.944 --> 00:35:15.150
- It's like, That's changed. That's- Ryan Vaughn (3three

992
00:35:15.150 --> 00:35:17.789
- thirty seven): Maybe like what Tony Redmond's done

993
00:35:17.789 --> 00:35:19.869
- over the years with the Office three sixty

994
00:35:19.869 --> 00:35:21.250
- five for IT Pros,

995
00:35:22.109 --> 00:35:24.030
- the book, but he's got that whole GitHub

996
00:35:24.030 --> 00:35:25.469
- repo, and him and his team of folks

997
00:35:25.469 --> 00:35:27.549
- have that GitHub repo out there with tons

998
00:35:27.549 --> 00:35:30.815
- of sample scripts. They're often updated for latest

999
00:35:30.815 --> 00:35:32.914
- iterations of the graph, things like that

1000
00:35:33.215 --> 00:35:34.755
- as he's going through and

1001
00:35:35.295 --> 00:35:38.335
- running into things. So, yeah, those resources exist

1002
00:35:38.335 --> 00:35:40.655
- and you can go It's super easy these

1003
00:35:40.655 --> 00:35:41.155
- days.

1004
00:35:41.960 --> 00:35:43.559
- You don't have to know how Git works.

1005
00:35:43.559 --> 00:35:45.719
- You can But is there gonna be demand

1006
00:35:45.719 --> 00:35:46.699
- for those resources

1007
00:35:47.159 --> 00:35:48.920
- going forward? I think the demand for those

1008
00:35:48.920 --> 00:35:51.480
- has changed because people are so much quicker

1009
00:35:51.480 --> 00:35:52.219
- to say,

1010
00:35:52.599 --> 00:35:54.679
- Claude, chat GPT, go write me a script

1011
00:35:54.679 --> 00:35:55.339
- for this.

1012
00:35:56.335 --> 00:35:58.114
- It's interesting to see

1013
00:35:58.735 --> 00:36:00.414
- or will be interesting to see- Jason Brett

1014
00:36:00.414 --> 00:36:01.215
- (zero fifty three:thirty seven): I think it's going

1015
00:36:01.215 --> 00:36:02.041
- to swing back. Joshua Zappia (zero fifty three:thirty

1016
00:36:02.041 --> 00:36:03.614
- seven): I guess what resources are going to

1017
00:36:03.614 --> 00:36:04.355
- be in demand

1018
00:36:04.655 --> 00:36:06.894
- as time continues to progress and as AI

1019
00:36:06.894 --> 00:36:07.788
- can do certain things. Joshua Zappia (zero fifty

1020
00:36:07.788 --> 00:36:09.614
- three:thirty seven): That's the whole human in the

1021
00:36:09.614 --> 00:36:10.434
- loop thing,

1022
00:36:11.059 --> 00:36:13.800
- and nothing's going to account for

1023
00:36:14.260 --> 00:36:16.900
- expertise and taste, right, to be able to

1024
00:36:16.900 --> 00:36:18.679
- put these things together. So

1025
00:36:18.980 --> 00:36:20.900
- can an LLM go and write you a

1026
00:36:20.900 --> 00:36:22.440
- PowerShell script? Yes.

1027
00:36:22.835 --> 00:36:25.714
- Can it interrogate the Graph API for you?

1028
00:36:25.714 --> 00:36:27.154
- Sure. Is it going to do it the

1029
00:36:27.154 --> 00:36:28.994
- right way or is it going to bring

1030
00:36:28.994 --> 00:36:30.454
- back the right set of data?

1031
00:36:31.634 --> 00:36:32.134
- Sometimes

1032
00:36:33.074 --> 00:36:34.534
- I think you don't know.

1033
00:36:34.914 --> 00:36:37.094
- I run into this regularly with

1034
00:36:37.920 --> 00:36:41.219
- in my world where folks are going and

1035
00:36:41.519 --> 00:36:44.400
- they're creating these solutions. Like, they look really

1036
00:36:44.400 --> 00:36:46.579
- pretty and could be a dashboard

1037
00:36:47.119 --> 00:36:49.454
- or, like, an assessment engine, things like that.

1038
00:36:49.535 --> 00:36:50.735
- And then you start to dig into some

1039
00:36:50.735 --> 00:36:52.114
- of the details and you're like,

1040
00:36:52.575 --> 00:36:55.635
- this feels like it's kinda like not right.

1041
00:36:56.015 --> 00:36:56.515
- Potentially,

1042
00:36:56.974 --> 00:36:59.614
- wildly wrong. And you ask them like, well,

1043
00:36:59.614 --> 00:37:01.055
- how did you get here? Like, what was

1044
00:37:01.055 --> 00:37:03.075
- the input? Like, can you go tell me,

1045
00:37:04.059 --> 00:37:05.039
- maybe it's like

1046
00:37:05.659 --> 00:37:07.500
- a a Kusto query kinda thing. Can you

1047
00:37:07.500 --> 00:37:09.019
- go tell me the Kusto query? I didn't

1048
00:37:09.019 --> 00:37:10.859
- write that Kusto query. The LOM wrote it

1049
00:37:10.859 --> 00:37:11.819
- for me. Well, how do you know if

1050
00:37:11.819 --> 00:37:13.019
- it's good? How do you know if that's

1051
00:37:13.019 --> 00:37:14.059
- right? How do you know if it was

1052
00:37:14.059 --> 00:37:15.900
- the right data source? Well, I don't know.

1053
00:37:15.900 --> 00:37:17.579
- It just told me. And they kinda take

1054
00:37:17.579 --> 00:37:19.724
- that as fact. And then you say or

1055
00:37:19.724 --> 00:37:21.505
- you do things like, oh, hey. Great.

1056
00:37:22.045 --> 00:37:23.824
- I put the query together, but then

1057
00:37:24.125 --> 00:37:26.525
- the magical LLM thing decided to wrap it

1058
00:37:26.525 --> 00:37:28.844
- in a Python script. Okay. Cool. Do you

1059
00:37:28.844 --> 00:37:31.105
- know Python? Nah. I don't know any Python.

1060
00:37:31.164 --> 00:37:32.605
- Do you know what it's doing? Nah. I

1061
00:37:32.605 --> 00:37:34.630
- don't know what it's doing. It's running the

1062
00:37:34.630 --> 00:37:36.469
- script. It's a script that runs a script

1063
00:37:36.469 --> 00:37:37.530
- that runs a script.

1064
00:37:38.949 --> 00:37:40.469
- We might want to think about that one,

1065
00:37:40.469 --> 00:37:40.969
- right,

1066
00:37:41.269 --> 00:37:43.269
- and come back along the way. So I

1067
00:37:43.269 --> 00:37:45.269
- do think there's value in that stuff. If

1068
00:37:45.269 --> 00:37:46.889
- I think about the world of

1069
00:37:48.005 --> 00:37:50.565
- hopefully the stuff that the Tony Redmans of

1070
00:37:50.565 --> 00:37:52.664
- the world are doing, doesn't go away

1071
00:37:53.285 --> 00:37:55.385
- because I think those are the

1072
00:37:55.844 --> 00:37:56.744
- more opinionated,

1073
00:37:57.525 --> 00:37:59.545
- arguably more tasteful solutions

1074
00:38:00.269 --> 00:38:03.090
- rather than something that's just been spun up

1075
00:38:04.030 --> 00:38:06.210
- by an LLM or a set of agents,

1076
00:38:07.150 --> 00:38:09.230
- things like that. Can they get the job

1077
00:38:09.230 --> 00:38:11.150
- done? Sure. Are they going to do it

1078
00:38:11.150 --> 00:38:12.610
- as efficiently, as tastefully,

1079
00:38:13.150 --> 00:38:15.010
- but with the same level of, I think,

1080
00:38:15.664 --> 00:38:17.425
- care, like, as you're going, like, step by

1081
00:38:17.425 --> 00:38:18.324
- step through the process?

1082
00:38:19.344 --> 00:38:20.405
- Probably not.

1083
00:38:21.025 --> 00:38:23.344
- So, you know, if somebody like Tony can

1084
00:38:23.344 --> 00:38:25.984
- write a script 10 x faster because he's

1085
00:38:25.984 --> 00:38:27.204
- got access to an LOM,

1086
00:38:28.000 --> 00:38:29.680
- that that's pretty cool. Right? Like, hopefully that

1087
00:38:29.680 --> 00:38:32.420
- leads to, like, like, more out outputs there.

1088
00:38:33.360 --> 00:38:35.760
- And then folks like us, like the mere

1089
00:38:35.760 --> 00:38:38.900
- mortals, we can ground our learning and round

1090
00:38:39.519 --> 00:38:41.360
- our stuff in that. Like, I think you'd

1091
00:38:41.360 --> 00:38:42.579
- have a way better experience

1092
00:38:43.135 --> 00:38:45.454
- probably going out to something like their GitHub

1093
00:38:45.454 --> 00:38:47.614
- repo for that I think they just renamed

1094
00:38:47.614 --> 00:38:48.355
- the book actually,

1095
00:38:48.974 --> 00:38:51.394
- Microsoft three sixty five for IT Pros, finally.

1096
00:38:52.335 --> 00:38:53.934
- But go out to that Git repo and

1097
00:38:53.934 --> 00:38:56.559
- clone that repo and say, Hey, can you

1098
00:38:56.559 --> 00:38:58.159
- build me a script that does this, or

1099
00:38:58.159 --> 00:39:00.719
- can you extend this script? Rather than start

1100
00:39:00.719 --> 00:39:02.880
- from scratch kind of thing. It's interesting to

1101
00:39:02.880 --> 00:39:04.639
- see how all this is changing. It keeps

1102
00:39:04.639 --> 00:39:05.780
- going along the way.

1103
00:39:06.319 --> 00:39:07.599
- And then like you said, make sure you

1104
00:39:07.599 --> 00:39:09.675
- charge enough money to cover your AI usage.

1105
00:39:10.394 --> 00:39:11.675
- Let me tell you, the amount I pay

1106
00:39:11.675 --> 00:39:14.315
- for AI is continuing to go up partly

1107
00:39:14.315 --> 00:39:15.914
- due to using it more, partly due to

1108
00:39:15.914 --> 00:39:17.855
- people changing pricing on me or

1109
00:39:18.155 --> 00:39:20.875
- stuff coming out of preview. And Pricing will

1110
00:39:20.875 --> 00:39:22.474
- continue to change on you, by the way.

1111
00:39:22.474 --> 00:39:22.974
- So

1112
00:39:25.289 --> 00:39:27.309
- hold on to your checkbook or your wallet.

1113
00:39:27.530 --> 00:39:28.730
- And as you hold on to it, just

1114
00:39:28.730 --> 00:39:30.170
- prepare to open it and have the money

1115
00:39:30.170 --> 00:39:31.530
- fly out. But in the meantime, I have

1116
00:39:31.530 --> 00:39:33.369
- Fable five for next week now. They did

1117
00:39:33.369 --> 00:39:34.829
- Fable five for next week.

1118
00:39:35.210 --> 00:39:35.710
- Yeah.

1119
00:39:36.329 --> 00:39:38.144
- So, yeah, by the time this comes out,

1120
00:39:38.224 --> 00:39:39.925
- Fable five may or may not

1121
00:39:40.704 --> 00:39:42.085
- may or may not still be there.

1122
00:39:42.784 --> 00:39:44.005
- So CheckTPT

1123
00:39:44.545 --> 00:39:46.005
- sorry, OpenAI. Codecs

1124
00:39:46.704 --> 00:39:48.864
- also got rid of the five hour window

1125
00:39:48.864 --> 00:39:50.625
- limit. And I don't know if you've been

1126
00:39:50.625 --> 00:39:51.844
- playing around with

1127
00:39:52.385 --> 00:39:53.309
- 5.6.

1128
00:39:53.309 --> 00:39:55.570
- So you've got Luna, Terra and SOL,

1129
00:39:55.869 --> 00:39:57.329
- good, better, best kind of

1130
00:39:57.630 --> 00:39:59.809
- effort and reasoning, things like that.

1131
00:40:00.190 --> 00:40:02.690
- 5.6 SOL is pretty good.

1132
00:40:04.430 --> 00:40:05.090
- Yeah. So

1133
00:40:05.994 --> 00:40:07.514
- just you have the option and you're looking

1134
00:40:07.514 --> 00:40:08.954
- out there and you're like, Hey, I'm stuck.

1135
00:40:08.954 --> 00:40:10.954
- And it's going to be interesting over the

1136
00:40:10.954 --> 00:40:13.214
- next couple of months, I think,

1137
00:40:13.594 --> 00:40:15.214
- while the frontier

1138
00:40:16.234 --> 00:40:17.214
- model trainers

1139
00:40:17.675 --> 00:40:18.175
- and

1140
00:40:18.954 --> 00:40:20.894
- AI delivery companies like

1141
00:40:21.210 --> 00:40:21.710
- Anthropic

1142
00:40:22.889 --> 00:40:24.730
- and OpenAI, things like that, have to now

1143
00:40:24.730 --> 00:40:26.590
- compete with local model weights

1144
00:40:27.050 --> 00:40:28.429
- that are coming out from

1145
00:40:29.130 --> 00:40:30.989
- China and other places,

1146
00:40:32.090 --> 00:40:34.329
- and kind of where they sit and how

1147
00:40:34.329 --> 00:40:35.869
- that stuff comes together. So

1148
00:40:36.355 --> 00:40:38.914
- we'll see. Can Anthropic keep up and get

1149
00:40:38.914 --> 00:40:40.675
- rid of the five hour window or the

1150
00:40:40.675 --> 00:40:42.835
- five hour usage reset window? I don't know.

1151
00:40:42.835 --> 00:40:43.735
- Be kind of nice.

1152
00:40:44.355 --> 00:40:46.055
- I didn't I'd enjoy it.

1153
00:40:46.515 --> 00:40:48.454
- But, you know, I I I see OpenAI

1154
00:40:48.594 --> 00:40:50.035
- doing some things that make me go like,

1155
00:40:50.035 --> 00:40:50.855
- oh, hey,

1156
00:40:51.159 --> 00:40:53.099
- maybe I should go back and

1157
00:40:53.800 --> 00:40:55.559
- be in that ecosystem. Or it keeps you

1158
00:40:55.559 --> 00:40:57.639
- kind of like you keep your toe in

1159
00:40:57.639 --> 00:40:59.000
- the water for both of them, which makes

1160
00:40:59.000 --> 00:40:59.559
- it really Matthew Gauthier (3seven 30: I don't

1161
00:40:59.559 --> 00:41:01.079
- keep my toe in the water for both

1162
00:41:01.079 --> 00:41:03.559
- anymore. I can't. I can't. I'm still there

1163
00:41:03.559 --> 00:41:05.099
- and I'm still trying.

1164
00:41:06.554 --> 00:41:08.875
- I'm a Claude fan boy, but like I

1165
00:41:08.875 --> 00:41:10.414
- said, they're doing some

1166
00:41:11.434 --> 00:41:13.454
- interesting stuff over in

1167
00:41:14.715 --> 00:41:17.514
- OpenAI land. Yeah. As long as you avoid

1168
00:41:17.514 --> 00:41:19.835
- their whole super app crap that they just

1169
00:41:19.835 --> 00:41:21.829
- came up with last week, That thing's horrible.

1170
00:41:21.829 --> 00:41:23.349
- Stay away from that. That wrap us up.

1171
00:41:23.349 --> 00:41:25.349
- Anything else? I think that covers it. We've

1172
00:41:25.349 --> 00:41:26.949
- been going for, like, forty five minutes now.

1173
00:41:26.949 --> 00:41:28.469
- I think that covers it. Hopefully, it gives

1174
00:41:28.469 --> 00:41:29.449
- some folks some

1175
00:41:30.309 --> 00:41:33.349
- things to noodle on. If you're out there

1176
00:41:33.349 --> 00:41:36.230
- in the consulting or delivery space and you

1177
00:41:36.230 --> 00:41:36.890
- have any

1178
00:41:37.484 --> 00:41:38.704
- opinions or feedback,

1179
00:41:39.244 --> 00:41:41.724
- go to our website. It's contact form. Let

1180
00:41:41.724 --> 00:41:44.204
- us know what's going on, or comment on

1181
00:41:44.204 --> 00:41:45.824
- the podcast on your

1182
00:41:46.364 --> 00:41:49.404
- platform of choice. Absolutely. And until next time,

1183
00:41:49.404 --> 00:41:50.944
- Scott. Until next time.

1184
00:41:53.000 --> 00:41:55.239
- If you enjoyed the podcast, go leave us

1185
00:41:55.239 --> 00:41:57.480
- a five star rating in iTunes. It helps

1186
00:41:57.480 --> 00:41:59.159
- to get the word out so more IT

1187
00:41:59.159 --> 00:42:01.320
- pros can learn about Office three sixty five

1188
00:42:01.320 --> 00:42:01.980
- and Azure.

1189
00:42:02.519 --> 00:42:04.199
- If you have any questions you want us

1190
00:42:04.199 --> 00:42:06.360
- to address on the show or feedback about

1191
00:42:06.360 --> 00:42:08.704
- the show, feel free to reach out via

1192
00:42:08.704 --> 00:42:10.885
- our website, Twitter, or Facebook.

1193
00:42:11.184 --> 00:42:13.105
- Thanks again for listening, and have a great

1194
00:42:13.105 --> 00:42:13.605
- day.