1
00:00:00,040 --> 00:00:03,480
When we asked the question, are 
we doing the right thing with 

2
00:00:03,600 --> 00:00:07,120
SAP build and the SAP ecosystem,
what we, what we found was 

3
00:00:07,320 --> 00:00:11,440
nothing else came close to the 
time to value within that 

4
00:00:11,440 --> 00:00:13,720
ecosystem. 
We started to see results very, 

5
00:00:13,720 --> 00:00:17,240
very quickly and we were able to
immediately leverage those 

6
00:00:17,240 --> 00:00:19,840
results. 
And again, we have no specific, 

7
00:00:19,840 --> 00:00:23,200
like I'm not an SAP customer, we
have no specific experience in 

8
00:00:23,200 --> 00:00:26,320
the SAP ecosystem, right? 
I didn't go out and hire a bunch

9
00:00:26,320 --> 00:00:28,440
of SAP engineers that would 
defeat the purpose. 

10
00:00:29,080 --> 00:00:33,080
So since we didn't have SAP 
experts in our ecosystem, we 

11
00:00:33,080 --> 00:00:34,760
were. 
And yet we're still able to get 

12
00:00:34,760 --> 00:00:38,320
those results and still able to 
get a 3X improvement of 59% cost

13
00:00:38,320 --> 00:00:40,320
savings. 
We really felt like that 

14
00:00:40,320 --> 00:00:43,760
represented a real good view of 
the market and of the space 

15
00:00:44,120 --> 00:00:46,880
because we're not setting 
ourselves up for any more 

16
00:00:46,880 --> 00:00:57,600
success than any enterprise. 
Hello and welcome to the next 

17
00:00:57,600 --> 00:01:01,080
episode of the SAPBDB talks. 
So this is Nicholas speaking 

18
00:01:01,080 --> 00:01:02,720
here. 
For everyone which don't know 

19
00:01:02,720 --> 00:01:06,800
me, my name is Nicholas Zimmer. 
I'm working at SAP and I'm a 

20
00:01:06,800 --> 00:01:09,920
Product Manager for SAP Business
Technology Platform. 

21
00:01:10,240 --> 00:01:14,760
And today we're going to talk 
about the TCO report from Giga 

22
00:01:14,760 --> 00:01:19,360
Ohm about SAP build versus 
custom development projects. 

23
00:01:19,840 --> 00:01:23,520
But before that, I have a little
bit of small announcement in 

24
00:01:23,520 --> 00:01:26,840
before because this is a very 
special episode, not only 

25
00:01:26,840 --> 00:01:29,040
because we have two exciting 
guests today. 

26
00:01:29,400 --> 00:01:32,800
It's also in special episode 
because we have some changes for

27
00:01:32,800 --> 00:01:38,280
the podcast because in the past 
this podcast was called SAPBTP 

28
00:01:38,280 --> 00:01:42,920
Talk, but in the future we will 
rebrand with starting with this 

29
00:01:42,920 --> 00:01:46,120
episode 2 unlocking SAP. 
BTP. 

30
00:01:46,520 --> 00:01:50,960
And another awesome news is that
we also change the format a 

31
00:01:50,960 --> 00:01:52,800
little bit. 
So I mean, if you're now 

32
00:01:52,800 --> 00:01:56,000
listening to us on Spotify or 
play music or any other 

33
00:01:56,480 --> 00:01:59,240
streaming platform, you may 
don't notice a difference. 

34
00:01:59,480 --> 00:02:02,200
But we also change to the video 
podcast format. 

35
00:02:02,200 --> 00:02:05,200
So if you just want to listen on
audio base, you can to continue 

36
00:02:05,200 --> 00:02:08,600
with that. 
But we are also now published on

37
00:02:08,600 --> 00:02:12,560
the official SAP main YouTube 
channel as a video podcast. 

38
00:02:12,560 --> 00:02:16,040
So give it a try if you want. 
Yeah. 

39
00:02:16,120 --> 00:02:20,600
And with that, I'm very happy to
introduce my today's podcast 

40
00:02:20,600 --> 00:02:22,880
guests. 
On the one hand side, we have 

41
00:02:22,880 --> 00:02:27,120
Howard Holton, which is the CTO 
of Ligaom joining me in the 

42
00:02:27,120 --> 00:02:30,040
interview today. 
And on the other side, we have a

43
00:02:30,040 --> 00:02:34,160
colleague of me of SAP, Mark 
Wright, the Senior Director for 

44
00:02:34,160 --> 00:02:38,600
Product Marketing of SAP Build. 
Yeah, welcome to our podcast. 

45
00:02:38,600 --> 00:02:43,120
Nice having you here today. 
So I would first ask you that 

46
00:02:43,120 --> 00:02:44,920
you can introduce yourself, 
please. 

47
00:02:44,920 --> 00:02:47,480
And let's start with you. 
Sure. 

48
00:02:47,480 --> 00:02:51,200
So I'm Howard Holton. 
I'm the CTO and CEO over here at

49
00:02:51,200 --> 00:02:54,200
Giga Ohm. 
Giga Ohm is an industry analyst 

50
00:02:54,200 --> 00:02:57,600
firm, much like another big 
industry analyst from you may 

51
00:02:57,600 --> 00:02:59,440
have heard of whose name also 
starts with AG. 

52
00:03:00,360 --> 00:03:03,200
We're just like them, you know, 
but smaller and scrappy. 

53
00:03:04,080 --> 00:03:05,600
I've been to get home for three 
years. 

54
00:03:05,600 --> 00:03:08,880
Before that I was a CIOACTO and 
AC. 

55
00:03:08,880 --> 00:03:11,720
So for various companies like 
Hitachi, Pantara and 

56
00:03:11,720 --> 00:03:13,880
remanufacturing. 
I've been there. 

57
00:03:13,880 --> 00:03:16,560
I've been in the executive suite
for about 18 years. 

58
00:03:16,560 --> 00:03:20,640
Before that I was an enterprise 
architect, an engineer, assist 

59
00:03:20,640 --> 00:03:23,760
admin. 
I've been in IT for 30, more 

60
00:03:23,760 --> 00:03:25,920
than 35 years. 
I got started when I was 11. 

61
00:03:25,920 --> 00:03:28,360
I wrote a piece of software 
called Plead Perfect back in 

62
00:03:28,360 --> 00:03:32,440
those lovely word perfect days, 
went on to sell that 

63
00:03:32,640 --> 00:03:35,680
commercially. 
My dad closed his law office, we

64
00:03:35,680 --> 00:03:38,960
opened a computer consulting 
firm, and I kind of got addicted

65
00:03:38,960 --> 00:03:40,760
to working in the technology 
space. 

66
00:03:41,440 --> 00:03:45,120
So I've been here ever since. 
It's been a long journey. 

67
00:03:45,440 --> 00:03:46,400
Yeah. 
Thank you, Howard. 

68
00:03:46,480 --> 00:03:49,960
So then we come to you, Mark. 
Yeah, Thanks everybody. 

69
00:03:49,960 --> 00:03:54,880
So Mark Wright, so I our 
Director in SAP build marketing.

70
00:03:54,880 --> 00:03:57,960
So I've been in this position 
for about three years or going 

71
00:03:57,960 --> 00:04:02,040
on three years or so, but I'm a 
long term SAP employee. 

72
00:04:02,040 --> 00:04:05,960
So I'm over about 20 plus years 
through different acquisitions, 

73
00:04:05,960 --> 00:04:10,200
but served in a lot of different
roles from engineering to 

74
00:04:10,200 --> 00:04:14,320
product management to pre sales 
to customer success. 

75
00:04:14,320 --> 00:04:18,640
So I've kind of filled a lot of 
different roles, really having 

76
00:04:19,200 --> 00:04:22,360
kind of a passion for this 
application and development 

77
00:04:22,360 --> 00:04:25,400
space, you know, starting from 
the mobile days that I really 

78
00:04:25,400 --> 00:04:29,120
concentrated on to where I'm at 
now and really looking forward 

79
00:04:29,120 --> 00:04:31,800
to this conversation. 
A little bit about myself, 

80
00:04:31,800 --> 00:04:34,160
right? 
I'm based here in Boise, ID, 

81
00:04:34,160 --> 00:04:38,560
which very few people in SAP are
based out of, but love to spend 

82
00:04:38,560 --> 00:04:41,840
my time outdoors with the 
campaign, soccer, etcetera. 

83
00:04:41,840 --> 00:04:44,600
So. 
It sounds great. 

84
00:04:45,120 --> 00:04:47,160
All right, thanks for 
introducing yourself. 

85
00:04:47,160 --> 00:04:48,920
So, Howard, let's continue with 
you. 

86
00:04:48,920 --> 00:04:51,440
Can you please introduce 
Gigahome a little bit more 

87
00:04:51,440 --> 00:04:54,840
detailed to us? 
Sure, like I said. 

88
00:04:54,840 --> 00:04:57,720
Gigahome is an industry analyst 
firm like that other Big G 

89
00:04:57,720 --> 00:04:59,920
company. 
At Gigahome we cover six major 

90
00:04:59,920 --> 00:05:04,000
domains, storage, cybersecurity,
data and AI, networking, cloud 

91
00:05:04,160 --> 00:05:06,800
and infrastructure, and then the
people and process side kind of 

92
00:05:06,800 --> 00:05:09,080
DevOps. 
But what really sets us apart is

93
00:05:09,080 --> 00:05:11,440
all of our analysts are active 
practitioners. 

94
00:05:12,080 --> 00:05:15,160
We are engineers, architects and
developers in the field. 

95
00:05:15,360 --> 00:05:17,760
We're not just talking about the
work, but we're doing it and we 

96
00:05:17,760 --> 00:05:20,560
present it from the perspective 
of people that are actually 

97
00:05:20,560 --> 00:05:24,080
running and using these tools. 
I don't employ full time 

98
00:05:24,080 --> 00:05:27,360
analysts, I use experts who stay
close to the technology so we 

99
00:05:27,360 --> 00:05:30,160
can bring a practitioner's view 
to the market, not an academic 

100
00:05:30,160 --> 00:05:32,000
or journalistic 1. 
OK. 

101
00:05:32,000 --> 00:05:35,880
The next question goes to Mark 
then can you first introduce us 

102
00:05:35,920 --> 00:05:39,800
on high level what is SAP built 
and what is meant with the 

103
00:05:39,800 --> 00:05:44,000
custom development as an 
alternative method instead of 

104
00:05:44,000 --> 00:05:45,160
using SAP build? 
Done. 

105
00:05:46,080 --> 00:05:48,120
Yeah, definitely. 
So just a little bit of 

106
00:05:48,120 --> 00:05:52,840
introduction for everybody, SAD 
build basically is SA PS 

107
00:05:52,840 --> 00:05:56,840
development solution for 
extension allocation and 

108
00:05:56,840 --> 00:06:00,200
automation. 
So what we've done is greatest 

109
00:06:00,200 --> 00:06:04,560
solution that that uses AI 
powered customization. 

110
00:06:04,880 --> 00:06:08,280
It allows you to create these 
automations using Procode or 

111
00:06:08,280 --> 00:06:13,000
Procode development and it works
process between non SAP systems.

112
00:06:13,000 --> 00:06:17,200
So what we're doing is providing
all these vault and capabilities

113
00:06:17,600 --> 00:06:20,960
regardless of your skill set, 
you're going to be able to take 

114
00:06:20,960 --> 00:06:22,880
advantage of all of our 
innovations. 

115
00:06:23,080 --> 00:06:24,960
You're going to be able to be 
more efficient with your 

116
00:06:24,960 --> 00:06:26,680
development. 
And that's what we're here 

117
00:06:26,800 --> 00:06:29,840
really to talk about today is 
how are you more efficient with 

118
00:06:29,840 --> 00:06:34,360
SAP Build? 
And what we did was ask Giga Om 

119
00:06:34,360 --> 00:06:37,560
to look at SAP Build against 
what we call a custom 

120
00:06:37,560 --> 00:06:40,680
development stack. 
It could be something like a DIY

121
00:06:40,680 --> 00:06:43,280
stack or as we said, custom 
development. 

122
00:06:43,280 --> 00:06:47,200
Now all platforms can do custom 
development, but the idea behind

123
00:06:47,200 --> 00:06:52,240
this was that customers or 
developers bring a whole 

124
00:06:52,720 --> 00:06:56,640
variance of stacks to do 
development in a lot of 

125
00:06:56,640 --> 00:07:00,120
scenarios. 
So you could take a look at a 

126
00:07:00,120 --> 00:07:04,240
stack that has to do API 
creation or implement your 

127
00:07:04,240 --> 00:07:07,800
security and authentication or 
you know, development from a 

128
00:07:07,800 --> 00:07:12,040
different JavaScript or anything
like that that has to come from 

129
00:07:12,040 --> 00:07:16,000
all these different various 
environments and then you have 

130
00:07:16,000 --> 00:07:19,280
to mold it together. 
Now from a build perspective, we

131
00:07:19,280 --> 00:07:22,480
run on a platform, right? 
So BTP or business technology 

132
00:07:22,480 --> 00:07:24,880
platform as is aim of the 
podcast. 

133
00:07:25,600 --> 00:07:29,920
And what that does is give the 
developer's ability to take 

134
00:07:29,920 --> 00:07:35,480
advantage of our security 
infrastructure and really good. 

135
00:07:36,240 --> 00:07:43,640
And what we asked going to do is
really compare build how you can

136
00:07:43,640 --> 00:07:46,800
develop that against these 
movement platforms. 

137
00:07:46,800 --> 00:07:51,120
So that's kind of where the the 
the paper took shape and then 

138
00:07:51,400 --> 00:07:55,320
the study began. 
So Howard definitely can go into

139
00:07:55,320 --> 00:07:57,160
how Giga Ohm approached that 
though. 

140
00:07:58,720 --> 00:08:00,280
All right. 
Thanks for introducing that 

141
00:08:00,280 --> 00:08:03,000
Mark. 
So let's start fairly high level

142
00:08:03,000 --> 00:08:04,960
and simple before we get in in 
more detail. 

143
00:08:04,960 --> 00:08:08,120
So, Howard, in simple words, 
what is the report all about? 

144
00:08:08,640 --> 00:08:12,840
So the report is a test of the 
effectiveness of using SAP build

145
00:08:12,840 --> 00:08:18,680
versus kind of the best off the 
shelf build your own stack, 

146
00:08:18,680 --> 00:08:22,440
right, Like a typical stack that
we would find in an enterprise 

147
00:08:22,440 --> 00:08:26,600
versus SAP build. 
And what we were really trying 

148
00:08:26,600 --> 00:08:29,680
to look at is what is the 
difference for SAP customers 

149
00:08:29,680 --> 00:08:32,799
building applications in their 
enterprise. 

150
00:08:33,200 --> 00:08:37,159
It's a really important 
distinction because for 70 

151
00:08:37,159 --> 00:08:41,600
years, right, businesses have 
been telling SAP all about how 

152
00:08:41,600 --> 00:08:45,600
their company runs. 
SAP builds advantages. 

153
00:08:45,600 --> 00:08:49,560
Now we're leveraging that. 
Now SAP is leveraging that to 

154
00:08:49,560 --> 00:08:51,840
help you better understand your 
business for the first time 

155
00:08:51,840 --> 00:08:54,200
ever. 
And and that kind of inside 

156
00:08:54,200 --> 00:08:58,040
baseball that SAP is able to 
offer gives it a unique 

157
00:08:58,040 --> 00:09:01,800
advantage that you just can't 
get with an off the shelf stack,

158
00:09:02,800 --> 00:09:04,480
right. 
So if you're an SAP customer, 

159
00:09:04,480 --> 00:09:08,400
your data is an SAP, your ERP is
SAP, and your stack is already a

160
00:09:08,400 --> 00:09:10,880
substantial portion of that SAP 
based. 

161
00:09:11,400 --> 00:09:13,480
So there's some tribal knowledge
in that ecosystem. 

162
00:09:13,680 --> 00:09:16,800
And what SAP Bill does is it 
leverages that tribal knowledge,

163
00:09:17,680 --> 00:09:19,400
and that's an advantage that 
nobody else has. 

164
00:09:19,840 --> 00:09:21,520
Exactly. 
So then let's get into the 

165
00:09:21,520 --> 00:09:24,360
details. 
So how was the report set up? 

166
00:09:24,360 --> 00:09:26,680
So what? 
What did you test it in detail, 

167
00:09:26,680 --> 00:09:30,280
how it was tested, for what 
length of time, etcetera? 

168
00:09:30,440 --> 00:09:32,840
So let's start with a kind of 
how Giga Ohm does our test 

169
00:09:32,840 --> 00:09:35,400
because we do it differently 
than any other analyst firm that

170
00:09:35,400 --> 00:09:37,440
I'm aware of. 
Matter of fact, the way Giga Ohm

171
00:09:37,440 --> 00:09:39,880
approaches the market is a big 
reason why I came to Giga Ohm. 

172
00:09:40,560 --> 00:09:44,520
So we don't do customer surveys 
for testing. 

173
00:09:44,560 --> 00:09:48,760
I don't do like, I don't call 
former customers and go, what's 

174
00:09:48,760 --> 00:09:50,520
your experience? 
I don't do customer 

175
00:09:50,520 --> 00:09:52,280
testimonials. 
I've been involved in those. 

176
00:09:53,160 --> 00:09:55,120
And unfortunately, because 
you're relying on people's 

177
00:09:55,120 --> 00:09:57,640
memory of a past event, they can
be a little hand WAVY. 

178
00:09:57,880 --> 00:10:02,000
No, what we do instead is I have
an A lab staffed by engineers 

179
00:10:02,280 --> 00:10:05,560
and we stand up all of these 
technologies and we run them on,

180
00:10:05,600 --> 00:10:10,480
on predefined use cases that 
replicate things customers do in

181
00:10:10,480 --> 00:10:14,880
the real world. 
And so we test it as accurately 

182
00:10:14,880 --> 00:10:18,080
as we can to replicate what an 
enterprise would do. 

183
00:10:18,680 --> 00:10:22,040
And we're confident enough that 
all of our testing, all of the, 

184
00:10:22,040 --> 00:10:25,360
the scenarios and everything we 
host in a GitHub repository for 

185
00:10:25,360 --> 00:10:28,760
each of our benchmarks. 
So anyone else can also run the 

186
00:10:28,760 --> 00:10:31,480
same tests, right? 
There's no secret sauce, there's

187
00:10:31,480 --> 00:10:34,560
no magic. 
We really want to represent the 

188
00:10:34,560 --> 00:10:38,200
real world. 
And so we took SAP Build and 

189
00:10:38,200 --> 00:10:43,040
then we set up kind of a DIY 
stack of of the commonly used by

190
00:10:43,040 --> 00:10:45,320
developers to do this AB 
comparison. 

191
00:10:45,800 --> 00:10:48,280
We set up a sample SAP 
environment and then we tested 

192
00:10:48,280 --> 00:10:51,440
the time to develop common 
applications using SAP Build 

193
00:10:51,440 --> 00:10:55,040
versus that development stack. 
What we found was working with 

194
00:10:55,040 --> 00:10:58,400
the SAP ecosystem, we were able 
to stand up the tools roughly 3 

195
00:10:58,400 --> 00:11:03,200
times faster and build the 
application and get the output 3

196
00:11:03,200 --> 00:11:08,240
times as fast at a 59 
approximate 59% savings with SAP

197
00:11:08,240 --> 00:11:12,280
Build within the SAP ecosystem. 
And the really interesting thing

198
00:11:12,280 --> 00:11:16,680
was when we looked at the level 
of engineer required to get the 

199
00:11:16,680 --> 00:11:21,440
results with the SAP build, we 
could use a lower level engineer

200
00:11:21,720 --> 00:11:25,080
almost across the board. 
I think I don't have the report 

201
00:11:25,080 --> 00:11:26,720
in front of me because I think 
that would be cheating. 

202
00:11:28,080 --> 00:11:31,360
I think we only had one case 
where we used a mid level 

203
00:11:31,360 --> 00:11:35,320
engineer on both the SAP build 
and the DIY stack. 

204
00:11:35,600 --> 00:11:39,160
Otherwise across the board it 
was always a lower level 

205
00:11:39,160 --> 00:11:41,400
employee. 
And what that meant was you can 

206
00:11:41,400 --> 00:11:46,240
really leverage all of the 
skills you have across the board

207
00:11:46,480 --> 00:11:50,080
in moving your SAP applications,
these new applications into 

208
00:11:50,080 --> 00:11:51,960
production. 
And that's a tremendous 

209
00:11:51,960 --> 00:11:54,440
advantage. 
None of us, not one 

210
00:11:54,440 --> 00:11:56,200
organization. 
And again, I come from that 

211
00:11:56,200 --> 00:11:59,320
executive corner, right? 
I come from, I've got to design 

212
00:11:59,320 --> 00:12:05,240
an operational experience team 
that's made-up of senior people 

213
00:12:05,240 --> 00:12:07,480
and junior people. 
And I don't know about how 

214
00:12:07,480 --> 00:12:10,040
you've seen teams, but I 
generally have three to five 

215
00:12:10,040 --> 00:12:12,920
times as many junior people as I
do senior people, and I never 

216
00:12:12,920 --> 00:12:16,480
have enough of any. 
And being able to really get 

217
00:12:16,560 --> 00:12:20,400
more value from my junior 
developers was a huge advantage 

218
00:12:20,400 --> 00:12:22,040
that we found, and it was a 
little surprising. 

219
00:12:22,760 --> 00:12:24,920
Yeah. 
Thank you for for introducing 

220
00:12:24,920 --> 00:12:27,680
that and explaining that. 
So as we are talking about the 

221
00:12:27,680 --> 00:12:31,600
TCO of development projects, 
what kind of development faces 

222
00:12:31,600 --> 00:12:35,320
do we have in a project and what
is their impact on the TCO? 

223
00:12:36,600 --> 00:12:40,160
Yeah, I, I mean, one thing you 
know, I I want to add to Howard 

224
00:12:40,160 --> 00:12:43,120
too. 
I mean, when we look at this, it

225
00:12:43,120 --> 00:12:47,400
was pretty interesting, right? 
We, we they took a environment 

226
00:12:47,520 --> 00:12:51,480
and then went away, right. 
So that that that's a kind of 

227
00:12:51,480 --> 00:12:56,800
goes missing within the paper 
SAP provided Giga ohm, here's 

228
00:12:56,800 --> 00:12:59,760
SAP build and now go and do your
thing, right. 

229
00:12:59,760 --> 00:13:03,960
So this is real world, you know,
putting something in a 

230
00:13:03,960 --> 00:13:07,840
customer's environment and then 
they need to learn SAP build and

231
00:13:07,840 --> 00:13:10,560
what it what its features are 
and then come back with this 

232
00:13:10,560 --> 00:13:13,720
report. 
So that helped really drive 

233
00:13:13,720 --> 00:13:18,800
these efficiencies that Howard 
talked about also taking a look 

234
00:13:18,800 --> 00:13:22,200
at what you can do with our AI 
stuff, but from a stack 

235
00:13:22,200 --> 00:13:25,080
standpoint, right? 
And the TCO we talk about 

236
00:13:25,360 --> 00:13:29,640
developer skill sets, right? 
So it's a huge important thing 

237
00:13:29,640 --> 00:13:34,440
to that resonates in this paper 
where I looked at, you know, we 

238
00:13:34,440 --> 00:13:37,880
always hear about, yes, AI is 
coming with the vibe coding, 

239
00:13:37,880 --> 00:13:41,520
etcetera. 
But today customers are really 

240
00:13:41,520 --> 00:13:45,200
struggling or companies are 
really struggling to have 

241
00:13:45,200 --> 00:13:48,880
developers that grow into senior
developers. 

242
00:13:48,880 --> 00:13:51,880
They're struggling to bring 
developers in house, right? 

243
00:13:51,880 --> 00:13:55,040
So you're getting minimal amount
of support from your developers.

244
00:13:55,040 --> 00:13:58,440
So the nice thing about that 
that was poured about pointed 

245
00:13:58,440 --> 00:14:02,120
out in this document is those 
roles that you talk about now, 

246
00:14:02,120 --> 00:14:05,280
what can you do with a junior 
developer as opposed to what you

247
00:14:05,280 --> 00:14:08,760
can do with a senior developer. 
And when you look at that three 

248
00:14:08,760 --> 00:14:11,840
times developer efficiency, 
that's a big difference. 

249
00:14:12,040 --> 00:14:15,880
Our junior developers or the 
junior developers can do a lot 

250
00:14:15,880 --> 00:14:20,960
more with SAP build then and 
then put senior developers on 

251
00:14:20,960 --> 00:14:25,200
things like architecture and 
what are my main very important 

252
00:14:25,200 --> 00:14:27,800
applications. 
So you see that kind of 

253
00:14:27,800 --> 00:14:30,000
throughout the report. 
And it's very important to point

254
00:14:30,000 --> 00:14:33,400
out that, you know, we're we're 
driving efficiency through a 

255
00:14:34,040 --> 00:14:39,200
lower seniority of a developer 
than the senior developers 

256
00:14:39,200 --> 00:14:42,000
itself. 
Absolutely. 

257
00:14:42,440 --> 00:14:45,280
The more I can leverage my 
junior developers, the better it

258
00:14:45,280 --> 00:14:48,280
is for the entire organization. 
I'm going to get more code, I'm 

259
00:14:48,680 --> 00:14:50,960
going to get better outcomes, 
I'm going to get faster 

260
00:14:50,960 --> 00:14:53,520
outcomes. 
And here's the best part. 

261
00:14:53,680 --> 00:14:58,080
Junior developers aren't just 
junior in their ability to 

262
00:14:58,160 --> 00:15:02,000
develop a complex applications, 
but they're also junior in their

263
00:15:02,000 --> 00:15:05,360
understanding of my business. 
Senior developers come along 

264
00:15:05,360 --> 00:15:08,200
with a lot of tribal knowledge 
about how my company works and 

265
00:15:08,200 --> 00:15:11,600
how my company runs and what we 
can actually, what we actually 

266
00:15:11,600 --> 00:15:14,400
do, how we make money, how we 
produce products, all of those 

267
00:15:14,400 --> 00:15:17,320
things. 
The less time my senior 

268
00:15:17,320 --> 00:15:21,760
developers spend deep in the 
weeds of code, the more time 

269
00:15:21,760 --> 00:15:24,960
they can spend really trying to 
understand how do we move the 

270
00:15:24,960 --> 00:15:27,080
business forward? 
How do we make advancements? 

271
00:15:27,080 --> 00:15:29,000
What are the things that are 
working and not working within 

272
00:15:29,000 --> 00:15:31,520
the business? 
And what are the big 

273
00:15:31,520 --> 00:15:35,000
architectural rocks that need to
be moved to be able to really 

274
00:15:35,000 --> 00:15:38,760
advance things. 
So leveraging SAP Build with my 

275
00:15:38,760 --> 00:15:45,080
junior team allows the senior 
team to really expose the value 

276
00:15:45,080 --> 00:15:48,080
they have in the organization. 
And at the same time, because 

277
00:15:48,080 --> 00:15:52,320
the junior team is able to 
contribute so much more, they're

278
00:15:52,320 --> 00:15:53,920
now getting up to speed that 
much more. 

279
00:15:54,080 --> 00:15:56,720
And we spend less time talking 
about code and we spend more 

280
00:15:56,720 --> 00:15:59,320
time talking about how the 
business works and how the 

281
00:15:59,320 --> 00:16:03,280
business operates really up 
leveling the value of everyone 

282
00:16:03,520 --> 00:16:05,160
in the entire software 
development team. 

283
00:16:05,960 --> 00:16:07,920
And and that was another kind of
surprising thing. 

284
00:16:07,920 --> 00:16:13,280
It's a almost a Tier 2 or ring 2
value that you get, a second 

285
00:16:13,320 --> 00:16:16,440
order value that you get that, 
you know, when you go into it, 

286
00:16:16,440 --> 00:16:18,400
you look at these things from 
the perspective of, OK, we want 

287
00:16:18,400 --> 00:16:20,200
to be fast, we want to be 
efficient, we want to be 

288
00:16:20,200 --> 00:16:21,440
effective, we want the code to 
work. 

289
00:16:21,880 --> 00:16:25,520
But you don't really think about
how does this change the value 

290
00:16:25,520 --> 00:16:29,120
proposition that software 
development can have within the 

291
00:16:29,120 --> 00:16:30,840
entire team. 
And that was that. 

292
00:16:30,840 --> 00:16:35,920
That was a really valuable kind 
of 2nd order advantage that we 

293
00:16:35,920 --> 00:16:37,440
found in going through this 
process. 

294
00:16:37,520 --> 00:16:40,480
Yeah, sounds like a good 
approach to really have a real 

295
00:16:40,480 --> 00:16:42,840
result in the end. 
So let's stick to that. 

296
00:16:42,840 --> 00:16:47,040
So I mean, what were the top two
or three takeaways done from the

297
00:16:47,040 --> 00:16:48,760
report, Howard? 
Yeah. 

298
00:16:48,760 --> 00:16:50,880
So when you look at the Gigail 
methodology, one of the things 

299
00:16:50,880 --> 00:16:53,760
that we're really specific about
because again, I really want to 

300
00:16:53,760 --> 00:16:56,040
replicate what is an enterprise 
going to encounter. 

301
00:16:56,600 --> 00:16:59,520
We get no special access. 
Matter of fact, we do our best 

302
00:16:59,520 --> 00:17:02,680
to establish like a Chinese 
firewall between US and the 

303
00:17:02,680 --> 00:17:05,079
vendors product team. 
So in this case, the SAP team, 

304
00:17:05,680 --> 00:17:08,880
what we really tried to do was 
almost hamstring ourselves, 

305
00:17:08,880 --> 00:17:13,319
almost handcuff us a little bit 
more even to make sure that 

306
00:17:13,319 --> 00:17:14,520
we're not getting special 
access. 

307
00:17:14,520 --> 00:17:16,359
We don't have access to 
engineering teams, we don't have

308
00:17:16,359 --> 00:17:19,520
access to the product team so 
that we can really show what is 

309
00:17:19,520 --> 00:17:22,079
this like to use as an 
enterprise customer. 

310
00:17:22,359 --> 00:17:26,599
And, and the valuable part was 
at no point did my team get 

311
00:17:26,599 --> 00:17:28,560
frustrated. 
At no point did my engineers 

312
00:17:28,560 --> 00:17:31,360
throw up their hands. 
Matter of fact, we ended up 

313
00:17:31,560 --> 00:17:33,960
having a lot of infighting 
amongst the engineering team 

314
00:17:34,400 --> 00:17:36,880
because the ones that work on 
this project, we're having so 

315
00:17:36,880 --> 00:17:39,520
much fun working with the tool. 
Everybody wanted to work with 

316
00:17:39,520 --> 00:17:41,560
the tool. 
And I've had a few calls going, 

317
00:17:41,560 --> 00:17:43,720
hey, are we going to do more 
testing for these guys and can I

318
00:17:43,720 --> 00:17:45,520
get in on it? 
OK. 

319
00:17:45,520 --> 00:17:46,960
Yeah. 
Thanks Howard for this small 

320
00:17:46,960 --> 00:17:48,240
deep dive on that. 
Mark. 

321
00:17:48,240 --> 00:17:52,040
Anything to add? 
Yeah, I mean from us of course, 

322
00:17:52,040 --> 00:17:53,360
right. 
So the three times developer 

323
00:17:53,360 --> 00:17:57,560
efficiency is a huge number for 
from an SAP perspective, right 

324
00:17:57,560 --> 00:18:00,000
and not kind of selling SAP 
build. 

325
00:18:00,000 --> 00:18:03,800
But there is not a tool within 
the SAP ecosystem and outside of

326
00:18:03,800 --> 00:18:07,200
the SAP ecosystem that drives 
such developer efficiency. 

327
00:18:07,200 --> 00:18:11,400
And as however is reported, I'm 
talking about this gives you 

328
00:18:11,400 --> 00:18:14,720
that TCO reduction, it gives you
a better ROI. 

329
00:18:14,800 --> 00:18:18,480
It's a solution that developers 
can get their hands on and get 

330
00:18:18,480 --> 00:18:22,480
up and running quickly because 
of the way that it's developed 

331
00:18:22,480 --> 00:18:26,040
with visual tools and AI 
capabilities and you know, the 

332
00:18:26,080 --> 00:18:29,760
integration into the SAP, the 
ecosystem. 

333
00:18:30,240 --> 00:18:34,200
Now one of the things too, 
coming back to kind of the AI a 

334
00:18:34,200 --> 00:18:35,960
topic. 
So Howard touched on this, you 

335
00:18:35,960 --> 00:18:39,360
know, by coding and really these
models that are getting 

336
00:18:39,360 --> 00:18:42,440
generated. 
Yes, there's a lot of AI out 

337
00:18:42,440 --> 00:18:43,960
there, right? 
So you can look at this 

338
00:18:43,960 --> 00:18:49,240
specialties that AI is creating 
like in clod, you know, you 

339
00:18:49,240 --> 00:18:55,880
might be able to do a lot of 
stuff that a chat GPG can do or 

340
00:18:55,880 --> 00:18:58,680
even Google and meta. 
So there's a lot of AI 

341
00:18:58,680 --> 00:19:03,120
capabilities, but what makes the
increase in boost for AI special

342
00:19:03,760 --> 00:19:07,880
within Jewel in SAP is really 
that integration into our 

343
00:19:07,880 --> 00:19:10,760
business data, right? 
So we've created Ella models 

344
00:19:10,760 --> 00:19:15,280
that no SAP, it's trained off of
SAP code and that's where that 

345
00:19:15,280 --> 00:19:18,240
boost comes from. 
You really have to look at the 

346
00:19:18,600 --> 00:19:22,240
benefits that an Ella model 
gives you in order to get that 

347
00:19:22,240 --> 00:19:26,160
boost in productivity from an AI
and only Jewel can offer that 

348
00:19:26,160 --> 00:19:29,840
from an SAP perspective. 
Of course we can use other 

349
00:19:31,040 --> 00:19:35,240
factors of ChatGPT or copilot or
you know, open AI, all that 

350
00:19:35,240 --> 00:19:38,040
stuff comes into that, that 
development approach. 

351
00:19:38,360 --> 00:19:41,800
But Jewel gives you that that 
special integration into SAP 

352
00:19:41,800 --> 00:19:43,520
systems. 
Sure. 

353
00:19:43,520 --> 00:19:46,240
So remember, I come at this from
the executive perspective, 

354
00:19:47,160 --> 00:19:50,320
right? 
My job is to run the business of

355
00:19:50,320 --> 00:19:52,440
building applications inside the
enterprise. 

356
00:19:53,360 --> 00:19:55,400
So the important thing to 
understand is I pay my 

357
00:19:55,400 --> 00:19:58,960
developers to be fast. 
I don't care what you say, you 

358
00:19:58,960 --> 00:20:02,600
can never get time back. 
I can always get more money. 

359
00:20:02,600 --> 00:20:06,680
I can always hire more people. 
I can always replace a tech 

360
00:20:06,680 --> 00:20:08,480
stack. 
Sure, all of that is costly, 

361
00:20:08,480 --> 00:20:13,320
It's not free, but I can never 
get time back. 

362
00:20:13,680 --> 00:20:15,760
So the most valuable thing that 
I have is time. 

363
00:20:15,800 --> 00:20:18,560
And really, when I'm thinking 
about time, it's time to value. 

364
00:20:19,400 --> 00:20:22,680
Right time to value is how 
quickly from start do I get an 

365
00:20:22,680 --> 00:20:24,960
outcome? 
How quickly from when I start do

366
00:20:24,960 --> 00:20:28,960
I see a result that I can start 
to measure and determine is this

367
00:20:28,960 --> 00:20:29,880
good? 
Is this bad? 

368
00:20:29,880 --> 00:20:30,840
Are we headed in the right 
direction? 

369
00:20:30,840 --> 00:20:31,920
Are we headed in the wrong 
direction? 

370
00:20:32,200 --> 00:20:35,560
Time to value is the reason 
under Agile we have things like 

371
00:20:35,560 --> 00:20:38,800
MVPS. 
It's the reason we all switch to

372
00:20:38,800 --> 00:20:41,480
an agile process. 
So the faster I can see value, 

373
00:20:41,480 --> 00:20:43,680
the faster I can validate that 
I'm headed in the right 

374
00:20:43,680 --> 00:20:47,480
direction and the faster my 
users will validate that I'm 

375
00:20:47,480 --> 00:20:51,560
hitting the target right. 
So when I, when we asked the 

376
00:20:51,560 --> 00:20:56,080
question, are we doing the right
thing with SAP build and the SAP

377
00:20:56,120 --> 00:20:58,880
ecosystem, what we, what we 
found was nothing else came 

378
00:20:58,880 --> 00:21:02,920
close to the time to value 
within that ecosystem. 

379
00:21:03,160 --> 00:21:06,520
We started to see results very, 
very quickly and we were able to

380
00:21:06,520 --> 00:21:08,720
immediately leverage those 
results. 

381
00:21:08,720 --> 00:21:12,000
And again, we have no specific, 
like I'm not an SAP customer. 

382
00:21:12,160 --> 00:21:16,000
We have no specific experience 
in the SAP ecosystem, right? 

383
00:21:16,000 --> 00:21:18,480
I didn't go out and hire a bunch
of SAP engineers that would 

384
00:21:18,480 --> 00:21:22,480
defeat the purpose, right? 
So since we didn't have SAP 

385
00:21:22,920 --> 00:21:25,280
experts in our ecosystem, we 
were. 

386
00:21:25,280 --> 00:21:27,800
And yet we're still able to get 
those results and still able to 

387
00:21:27,800 --> 00:21:30,840
get a 3X improvement of 59% cost
savings. 

388
00:21:31,200 --> 00:21:34,240
We really felt like that 
represented a real good view of 

389
00:21:34,240 --> 00:21:37,720
the market and of the space 
because we're not setting 

390
00:21:37,720 --> 00:21:40,400
ourselves up for any more 
success than any enterprise. 

391
00:21:40,800 --> 00:21:43,440
We really want to be trustworthy
and we really want SAP to be 

392
00:21:43,440 --> 00:21:46,000
trustworthy when they talk about
these things and when they show 

393
00:21:46,000 --> 00:21:50,360
them, right. 
So again, 2.8 times faster with 

394
00:21:50,560 --> 00:21:55,640
a huge 59% reduction in the 
level of effort and, and again, 

395
00:21:55,640 --> 00:21:57,680
right, we were really shocked by
what we saw. 

396
00:21:57,680 --> 00:22:00,720
We were really shocked by the 
value that we got and it was 

397
00:22:00,720 --> 00:22:04,040
really a fun project to work on.
I can't stress that enough. 

398
00:22:04,280 --> 00:22:07,920
So much of the stuff that we do 
day-to-day is just like it at 

399
00:22:07,920 --> 00:22:11,760
some point you're like, oh man, 
another tool, oh man, another 

400
00:22:11,760 --> 00:22:14,680
whatever, whatever. 
And to have my, my engineering 

401
00:22:14,680 --> 00:22:16,680
team come back and, and these 
are high pressure. 

402
00:22:16,680 --> 00:22:19,160
We try to do them very quick. 
We try to work through them, 

403
00:22:19,160 --> 00:22:20,560
right. 
We're really trying to replicate

404
00:22:20,560 --> 00:22:23,920
the pressure that you would have
in an enterprise and kind of 

405
00:22:23,920 --> 00:22:26,120
almost set it, set ourselves up 
for failure so that it 

406
00:22:26,120 --> 00:22:27,920
represents things well. 
And to have the team come back 

407
00:22:27,920 --> 00:22:30,640
and go, that was so much fun. 
Can we really do more of those? 

408
00:22:30,640 --> 00:22:35,000
It was fantastic. 
Yeah, thanks for your addition 

409
00:22:35,000 --> 00:22:37,720
there. 
I mean we're we will touch on a 

410
00:22:37,720 --> 00:22:40,840
little bit of more details and 
capabilities what build offers. 

411
00:22:41,240 --> 00:22:43,760
But as we already are more or 
less than half time of our 

412
00:22:43,760 --> 00:22:46,920
interview in our podcasts, we 
have a small power break game to

413
00:22:46,920 --> 00:22:49,880
refresh our minds and I believe 
the minds of our listeners as 

414
00:22:49,880 --> 00:22:51,440
well because they hear us 
talking. 

415
00:22:52,400 --> 00:22:54,640
So yeah, let's play a small 
game. 

416
00:22:55,120 --> 00:22:58,680
The game is fairly easy, so I 
just give you a question like 

417
00:22:58,720 --> 00:23:02,720
coffee or energy drink on you. 
Just simply tell us your choice.

418
00:23:02,720 --> 00:23:06,200
And if you want, you can also 
touch slightly on why it's your 

419
00:23:06,200 --> 00:23:08,440
choice. 
All right, so then we all always

420
00:23:08,440 --> 00:23:11,280
start with Howard Dan. 
So first question is then, do 

421
00:23:11,280 --> 00:23:15,840
you prefer walking in a calm, 
calming forest or making a hike 

422
00:23:15,840 --> 00:23:19,320
in a calming forest? 
Or are you more the urban guy 

423
00:23:19,480 --> 00:23:23,720
exploring cities? 
So I grew up in rural, I grew up

424
00:23:23,720 --> 00:23:26,640
in the mountains. 
I really find the forest and 

425
00:23:26,640 --> 00:23:31,760
nature to be comforting. 
But I travel 250 days a year. 

426
00:23:31,760 --> 00:23:36,960
So I I find that by sheer 
necessity of time, I spend a lot

427
00:23:36,960 --> 00:23:40,840
more time in the city. 
I had a motorcycle accident 

428
00:23:40,840 --> 00:23:43,160
several years ago. 
So like, I don't walk as well as

429
00:23:43,160 --> 00:23:46,480
I used to either. 
So hiking has become kind of a, 

430
00:23:46,520 --> 00:23:49,720
you know, a challenge. 
The bummer is, you know, we 

431
00:23:49,720 --> 00:23:52,920
invest so little in 
infrastructure that that some 

432
00:23:52,920 --> 00:23:55,920
cities the sidewalks are work 
than worse than hiking in the 

433
00:23:55,920 --> 00:23:57,120
mountains. 
It's quite terrible. 

434
00:23:57,360 --> 00:23:59,920
But but you know, generally I 
spend most of my time in the 

435
00:23:59,920 --> 00:24:01,520
city now. 
It's unfortunate. 

436
00:24:01,920 --> 00:24:03,280
OK, got it. 
Yeah. 

437
00:24:03,600 --> 00:24:07,600
What about you, Mark? 
So 100% walking in the forest, 

438
00:24:07,720 --> 00:24:10,600
you know, I, I live where I live
because I can be outdoors. 

439
00:24:10,800 --> 00:24:13,680
I do a lot of hiking, a lot of 
camping. 

440
00:24:14,200 --> 00:24:17,840
So forest is kind of my space to
get away from the urban 

441
00:24:18,320 --> 00:24:21,680
landscapes. 
I and I do it quite often, 

442
00:24:21,680 --> 00:24:23,720
right? 
So I, I, I love the hiking in 

443
00:24:23,720 --> 00:24:26,280
the forest and kind of the 
relaxation that you get from it.

444
00:24:27,680 --> 00:24:29,680
Awesome. 
So then we have the second 

445
00:24:29,680 --> 00:24:31,160
question. 
I hope this is a little bit more

446
00:24:31,160 --> 00:24:36,000
easier than salad or fries. 
Oh, I'm a big salad guy. 

447
00:24:36,520 --> 00:24:38,440
Salad Salad is one of my 
favorite foods. 

448
00:24:38,440 --> 00:24:40,080
I mean, it's a little bit of a 
cheat because French fries are 

449
00:24:40,080 --> 00:24:43,040
always kind of French fries, but
salads have kind of infinite 

450
00:24:43,040 --> 00:24:45,560
variability. 
A couple years ago, I went to a 

451
00:24:45,560 --> 00:24:48,080
restaurant and I saw something 
neat on the menu and I just 

452
00:24:48,080 --> 00:24:49,160
went, you know, I kind of got to
try it. 

453
00:24:49,160 --> 00:24:50,840
I've never even heard of it. 
It seems kind of weird. 

454
00:24:50,840 --> 00:24:52,760
I tried it and I absolutely fell
in love. 

455
00:24:52,760 --> 00:24:56,120
And it was like a watermelon and
feta and balsamic salad. 

456
00:24:56,840 --> 00:24:59,400
Oh, it was so good. 
So then of course, I learned how

457
00:24:59,400 --> 00:25:01,360
to make it at home and it's 
become one of our favorite, 

458
00:25:01,360 --> 00:25:04,520
like, late summer dishes. 
It's super light, it's super 

459
00:25:04,520 --> 00:25:06,320
flavorful. 
You chop up the watermelon, you 

460
00:25:06,320 --> 00:25:08,120
stick it in the fridge and get 
it nice and cold. 

461
00:25:08,360 --> 00:25:10,360
Little bit of feta, little bit 
of cheese. 

462
00:25:10,360 --> 00:25:13,400
My wife likes it with like 
sliced almonds or sliced 

463
00:25:13,400 --> 00:25:16,280
macadamia nuts and it's so 
refreshing. 

464
00:25:16,880 --> 00:25:19,240
But the fact is that's a salad. 
French fries are always French 

465
00:25:19,240 --> 00:25:21,920
fries, you know, I mean like 
even tater tots technically not 

466
00:25:21,920 --> 00:25:24,760
French fries. 
So, you know, I'm I'm happy to 

467
00:25:24,760 --> 00:25:28,440
eat a crispy, fluffy French fry,
but but I just don't think you 

468
00:25:28,440 --> 00:25:30,360
can beat a good salad. 
Well, that's an interesting 

469
00:25:30,360 --> 00:25:31,960
perspective I never thought of. 
Yeah. 

470
00:25:31,960 --> 00:25:36,000
What about you, Mark? 
Well, I, I think living in 

471
00:25:36,000 --> 00:25:40,760
Idaho, I supposed to say fries 
because we have potatoes, right?

472
00:25:40,760 --> 00:25:43,520
But that's a lot of variety of 
fries. 

473
00:25:43,520 --> 00:25:45,920
But I, I love the answer that 
our give. 

474
00:25:45,920 --> 00:25:48,400
And then of course my wife would
prefer me to say salad, right? 

475
00:25:48,400 --> 00:25:52,280
A little bit healthier but 
probably probably fries would be

476
00:25:52,280 --> 00:25:55,080
my go to. 
Yeah. 

477
00:25:55,280 --> 00:25:56,600
OK. 
And then we have the last 

478
00:25:56,600 --> 00:25:59,120
question. 
Do you prefer classical music or

479
00:25:59,120 --> 00:26:00,920
more modern music? 
And if you want, you can also 

480
00:26:00,920 --> 00:26:03,640
share your your type of favorite
music if you want. 

481
00:26:04,360 --> 00:26:07,360
So I'm a kid from the 90s. 
Like alternative rock is 

482
00:26:07,360 --> 00:26:09,720
absolutely my jam. 
And I grew up heavy on classic 

483
00:26:09,720 --> 00:26:12,040
rock. 
So like when I'm sitting with 

484
00:26:12,040 --> 00:26:14,400
some headphones on and I'm just 
kind of unwinding from the end 

485
00:26:14,400 --> 00:26:17,200
of the day, I'm like Pink 
Floyd's give me some Led 

486
00:26:17,200 --> 00:26:18,840
Zeppelin. 
I'm a big fan of rock. 

487
00:26:18,840 --> 00:26:22,640
I mean, I just realized in going
through this, I'm heavy in a 

488
00:26:22,640 --> 00:26:28,440
nerd rock, right? 
But when I want to concentrate 

489
00:26:28,440 --> 00:26:32,120
when I'm working, I'm a I'm a 
big fan of like jazz. 

490
00:26:32,120 --> 00:26:34,720
Jazz is probably my favorite and
and specifically like Miles 

491
00:26:34,720 --> 00:26:38,000
Davis Coltrane versus the kind 
of bigger band stuff, right? 

492
00:26:38,000 --> 00:26:42,520
I like simple band members, 
complex music. 

493
00:26:42,520 --> 00:26:44,520
I don't know why that helps me 
concentrate because it doesn't 

494
00:26:44,520 --> 00:26:46,560
seem like it would. 
It's so discordant sometimes, 

495
00:26:46,920 --> 00:26:48,560
but but that really works for 
me. 

496
00:26:50,120 --> 00:26:52,880
You know, it's kind of hard to 
beat a, a good Chopin though. 

497
00:26:52,880 --> 00:26:56,080
So, you know, I, I guess I'm a 
little bit all over the map is, 

498
00:26:56,080 --> 00:26:58,400
is what I'm saying. 
But but yeah, definitely nerd 

499
00:26:58,400 --> 00:26:59,480
rock. 
It's weird. 

500
00:27:00,840 --> 00:27:02,120
No jazz. 
Interesting. 

501
00:27:02,200 --> 00:27:06,160
Yeah, thanks. 
I'm a mixed bag. 

502
00:27:06,160 --> 00:27:08,560
I don't really have a favorite. 
I guess I would go with like 

503
00:27:08,560 --> 00:27:14,480
classic rock is the most often 
music that I listen to, but lots

504
00:27:14,480 --> 00:27:18,320
of lots of different mixed music
in my in my Spotify. 

505
00:27:19,800 --> 00:27:21,560
Yeah, I I know the ceiling as 
well. 

506
00:27:23,000 --> 00:27:24,640
All right, So that was already 
the game. 

507
00:27:24,640 --> 00:27:26,520
So thank you for playing with 
me. 

508
00:27:26,840 --> 00:27:29,600
So we can back can get back to 
the topic then. 

509
00:27:29,600 --> 00:27:34,120
And I mean, I know that in the 
report and also in the use case 

510
00:27:34,360 --> 00:27:37,600
which was below the report, 
you've used the CUP framework 

511
00:27:37,600 --> 00:27:41,600
from SAP and you also used 
utilize Jewel within build. 

512
00:27:41,960 --> 00:27:47,640
But for those who don't know 
Jewel and COP, So what is it and

513
00:27:47,640 --> 00:27:50,320
why is it so fundamentally 
importing in transforming the 

514
00:27:50,320 --> 00:27:54,880
development process? 
Yeah, I can give an 

515
00:27:54,880 --> 00:27:56,680
introduction. 
Obviously, you know, those are 

516
00:27:56,680 --> 00:28:01,000
two SAP technologies and then 
Howard probably can talk about 

517
00:28:01,000 --> 00:28:02,480
how they kind of take advantage 
of it. 

518
00:28:02,480 --> 00:28:06,800
But from from a Jewel 
standpoint, right, SAP, it's SA 

519
00:28:06,800 --> 00:28:08,920
PS AI assistant. 
So it's really what you would 

520
00:28:08,920 --> 00:28:12,240
consider a copilot for lots of 
different things. 

521
00:28:12,240 --> 00:28:16,640
We've what we always say from an
SAP perspective, it's grounded 

522
00:28:16,640 --> 00:28:20,560
in business data and it's 
infused in your AI agents across

523
00:28:20,560 --> 00:28:24,520
all of the business, right. 
So from a developer standpoint, 

524
00:28:24,520 --> 00:28:27,560
I kind of talked about this a 
little bit more before Jewel 

525
00:28:27,560 --> 00:28:30,960
itself. 
We've integrated it into all of 

526
00:28:30,960 --> 00:28:33,600
our development of the business.
So we're giving you the 

527
00:28:33,600 --> 00:28:37,080
capabilities to do generative 
AI, we're giving you the 

528
00:28:37,080 --> 00:28:41,240
capabilities to create AI agents
moving into autonomous AI. 

529
00:28:41,240 --> 00:28:42,800
So there's a lot of innovation 
there. 

530
00:28:43,240 --> 00:28:47,200
The biggest factor from a Jewel 
perspective, again, is our 

531
00:28:47,200 --> 00:28:52,800
proprietary LMS that we build in
order to make it efficient for 

532
00:28:52,800 --> 00:28:55,480
SAP development. 
And then we integrate with 

533
00:28:55,480 --> 00:28:58,680
other, you know, Microsoft 
Copilot that can take advantage.

534
00:28:58,680 --> 00:29:01,400
And I kind of mentioned that. 
But again, Jewel itself from a 

535
00:29:01,400 --> 00:29:05,200
developer standpoint is 
efficient because of the LMM 

536
00:29:05,200 --> 00:29:10,760
models we've both done from CAP 
and ABAP in order to best create

537
00:29:11,280 --> 00:29:15,200
a development environment. 
Now I say CAP a lot, and this is

538
00:29:15,200 --> 00:29:17,920
a main foundation of the paper 
itself. 

539
00:29:18,200 --> 00:29:20,680
It's our cloud application 
programming model. 

540
00:29:20,680 --> 00:29:25,480
It is the foundation. 
So CAP itself is defined as a 

541
00:29:25,480 --> 00:29:29,200
framework of languages. 
It has libraries, tools, 

542
00:29:29,600 --> 00:29:32,960
development solutions, it can 
create services. 

543
00:29:33,160 --> 00:29:36,280
So there's a lot of things that 
it's kind of the glue. 

544
00:29:36,280 --> 00:29:42,000
It's a far too simple of a 
solution, but it alleviates 

545
00:29:42,000 --> 00:29:44,480
those pains. 
It's traditionally associated 

546
00:29:44,480 --> 00:29:47,200
with your developing development
of enterprise applications, 

547
00:29:47,200 --> 00:29:48,640
right? 
We talked about how you gain 

548
00:29:48,640 --> 00:29:51,560
efficiency and CAP is one of 
those ways. 

549
00:29:51,800 --> 00:29:56,680
It's really giving developers 
this best practice path to be 

550
00:29:56,680 --> 00:30:00,480
able to create these enterprise,
enterprise made solutions like 

551
00:30:00,480 --> 00:30:04,000
we saw in the paper. 
So we combine Jewel with CAP and

552
00:30:04,000 --> 00:30:08,160
we have this whole solution that
helps you kind of transform how 

553
00:30:08,160 --> 00:30:12,120
you develop within an SAP 
ecosystem that's really 

554
00:30:12,920 --> 00:30:16,000
delivering that solution to 
create these enterprise 

555
00:30:16,160 --> 00:30:19,280
enterprise grade applications. 
And again, coming back to the 

556
00:30:19,280 --> 00:30:23,120
TCO, CAP and Jewel combined and 
the rest of the framework is 

557
00:30:23,120 --> 00:30:26,680
where you get the TCO from. 
Got it. 

558
00:30:26,680 --> 00:30:29,160
So I'm now curious for the 
perspective of you, Howard. 

559
00:30:29,720 --> 00:30:33,080
Like when we looked at at what 
did Cap and Jewel really offer, 

560
00:30:33,320 --> 00:30:34,880
there were a few things that 
were really surprising. 

561
00:30:34,880 --> 00:30:40,120
I've already touched on the 
different experience level of 

562
00:30:40,120 --> 00:30:41,760
the developers being able to be 
leveraged. 

563
00:30:42,280 --> 00:30:45,320
One of the things that I really 
didn't expect and those that are

564
00:30:45,920 --> 00:30:48,640
involved in software development
are going to recognize this one 

565
00:30:48,920 --> 00:30:52,680
right away. 
Producing synthetic data is an 

566
00:30:52,680 --> 00:30:56,240
art unto itself, and one of the 
things that we found, because 

567
00:30:56,320 --> 00:31:01,560
SAP knows SAP so incredibly 
well, it was so fast and 

568
00:31:01,560 --> 00:31:04,280
effective at generating 
synthetic data. 

569
00:31:04,320 --> 00:31:07,760
It was a tremendous time saver. 
And that's a really important 

570
00:31:07,760 --> 00:31:10,280
feature when you're looking at 
governance and compliance and 

571
00:31:10,280 --> 00:31:12,240
how you govern your data and 
manage your data. 

572
00:31:12,480 --> 00:31:15,520
We really want to make sure that
we're able to generate synthetic

573
00:31:15,520 --> 00:31:18,520
data that looks like us but 
isn't us. 

574
00:31:18,520 --> 00:31:23,760
The risk to using our real data 
in testing is we can easily 

575
00:31:23,760 --> 00:31:28,480
violate GDPR, easily violate 
GDPR simply because we're in the

576
00:31:28,480 --> 00:31:30,320
midst of the development process
and we don't really have the 

577
00:31:30,320 --> 00:31:31,600
controls in place as part of 
that. 

578
00:31:31,840 --> 00:31:34,960
So you need good synthetic data 
that really looks like you. 

579
00:31:35,400 --> 00:31:40,680
And I was really shocked at how 
good SAP Cap and Jewel were at 

580
00:31:40,680 --> 00:31:43,560
generating that synthetic data, 
Right. 

581
00:31:44,600 --> 00:31:47,600
You know, the, the other thing 
that that was a little bit 

582
00:31:48,240 --> 00:31:52,720
shocking was just how far it 
extended the value and how 

583
00:31:52,720 --> 00:31:57,520
little we had to go back and 
kind of think about it from a 

584
00:31:57,520 --> 00:32:00,600
different perspective. 
Like by default, we start 

585
00:32:00,600 --> 00:32:04,280
thinking about these tools 
through the lens of how junior 

586
00:32:04,280 --> 00:32:06,440
can I be? 
And what we really didn't have 

587
00:32:06,440 --> 00:32:09,560
to do was go, you know what, I'm
just too junior for this. 

588
00:32:10,160 --> 00:32:11,600
I really need to call in someone
else. 

589
00:32:11,640 --> 00:32:14,640
I really need more experience. 
We were really shocked at how 

590
00:32:14,640 --> 00:32:19,800
little we had to kind of up 
level our developmental 

591
00:32:19,800 --> 00:32:21,640
experience in order to make 
these tools work. 

592
00:32:21,640 --> 00:32:25,120
It was really fantastic. 
And I think customers are really

593
00:32:25,120 --> 00:32:28,440
going to be shocked by how fast 
they're going to be in how fast 

594
00:32:28,440 --> 00:32:31,240
they're going to see results and
how good those results are going

595
00:32:31,240 --> 00:32:35,800
to be because of how much SAP 
knows about your business and 

596
00:32:35,800 --> 00:32:37,720
how much of that is integrated 
within the tool set. 

597
00:32:38,480 --> 00:32:41,040
I mean, you already both touched
a little bit on that. 

598
00:32:41,040 --> 00:32:44,040
I bet you don't need 2 serious 
developers. 

599
00:32:44,040 --> 00:32:46,480
I mean that you can have junior 
developers in the project as 

600
00:32:46,480 --> 00:32:48,560
well and then getting the 
results. 

601
00:32:49,560 --> 00:32:53,240
But yeah, I mean, what what is 
or how SAP builds serve as a 

602
00:32:53,280 --> 00:32:56,440
differentiator for the 
developers and enabling them to 

603
00:32:56,440 --> 00:32:59,320
meet and exceed their goals. 
So, Howard, what do you think? 

604
00:33:01,080 --> 00:33:04,520
So what developers want to do is
they really want to write code. 

605
00:33:04,840 --> 00:33:07,000
They were a muck with systems, 
right? 

606
00:33:07,120 --> 00:33:11,520
And the number one place you 
muck with systems in expansive 

607
00:33:12,480 --> 00:33:15,840
integrations within your company
is building integrations. 

608
00:33:15,840 --> 00:33:19,080
So even if you just think about 
I need to access our primary 

609
00:33:19,080 --> 00:33:20,240
data set, cool. 
That's an ERP. 

610
00:33:20,880 --> 00:33:24,880
There's probably 60 other places
that you need to access using a 

611
00:33:24,880 --> 00:33:26,960
traditional development tool. 
You're going to spend a ton of 

612
00:33:26,960 --> 00:33:30,360
time building all of these 
integrations, and it's going to 

613
00:33:30,680 --> 00:33:33,400
effectively take away from the 
thing developers get showing in,

614
00:33:33,400 --> 00:33:36,160
which is building applications 
and creating these interesting 

615
00:33:36,160 --> 00:33:38,480
outcomes. 
And because all of that is 

616
00:33:38,480 --> 00:33:42,320
integrated, and because Jewel 
speaks SAP, because Jewel speaks

617
00:33:42,360 --> 00:33:45,560
ERP, because it speaks HANA, you
don't have to build any of those

618
00:33:45,560 --> 00:33:47,320
integrations. 
They're kind of right 

619
00:33:47,320 --> 00:33:49,760
out-of-the-box. 
And so you're immediately 

620
00:33:49,760 --> 00:33:52,120
putting developers in the 
position where they're doing the

621
00:33:52,120 --> 00:33:55,600
thing they enjoy the most and 
spending a lot less time on the 

622
00:33:55,600 --> 00:33:57,840
things they don't enjoy. 
And I think that really goes 

623
00:33:57,840 --> 00:34:00,760
back to the thing I said about 
my developers really enjoying 

624
00:34:00,760 --> 00:34:03,760
the experience and really having
a good time, because they really

625
00:34:03,760 --> 00:34:07,080
didn't have to spend a lot of 
time as plumbers. 

626
00:34:07,560 --> 00:34:09,520
They really got to spend a lot 
of time as painters. 

627
00:34:09,760 --> 00:34:11,239
And everybody prefers to be a 
painter. 

628
00:34:11,440 --> 00:34:13,239
Maybe I'll add to what Howard 
was saying. 

629
00:34:13,239 --> 00:34:16,960
I, I love the statement that 
they, they developers loved what

630
00:34:16,960 --> 00:34:19,560
they were doing with, with SAP 
build. 

631
00:34:19,560 --> 00:34:22,199
It makes it a lot easier, right 
to you keep your developers 

632
00:34:22,199 --> 00:34:27,440
happy and, and a lot of that 
coming back to to cap, right? 

633
00:34:27,440 --> 00:34:31,400
I mean, a lot of the speed, the 
efficiency, the integration that

634
00:34:31,400 --> 00:34:37,800
you get is based off of CAP. 
And we built SAP build on top of

635
00:34:37,800 --> 00:34:41,360
the CAP framework, the CAP 
development model in order to 

636
00:34:41,360 --> 00:34:45,239
differentiate, right? 
This comes back to that whole 

637
00:34:45,239 --> 00:34:48,960
custom stack discussion, because
what you have with a custom 

638
00:34:48,960 --> 00:34:51,800
stack is that you've got to 
bring in service integration, 

639
00:34:51,800 --> 00:34:53,960
you got to bring an identity 
authentication, you've got to 

640
00:34:53,960 --> 00:34:57,480
bring in a platform to run and 
operate, right from your 

641
00:34:57,480 --> 00:35:00,400
maintainability and upgrade 
standpoint. 

642
00:35:00,800 --> 00:35:03,920
All this is kind of built into 
do SAP build to make the 

643
00:35:03,920 --> 00:35:07,160
developers more efficient and 
enjoy the development itself 

644
00:35:07,480 --> 00:35:10,480
because they can easily do the 
integration to a back end 

645
00:35:10,480 --> 00:35:12,200
system. 
They can easily create a 

646
00:35:12,200 --> 00:35:15,800
service, they can create their 
data models, they can integrate 

647
00:35:15,800 --> 00:35:19,200
AI into creating that sample 
data and unit tests and code 

648
00:35:19,200 --> 00:35:23,000
generation and it comes back as 
that full efficiency, right? 

649
00:35:23,000 --> 00:35:26,160
It's a safe development 
environment that allows the 

650
00:35:26,160 --> 00:35:31,240
speed of development to do it 
without a negative effect. 

651
00:35:31,560 --> 00:35:35,360
I do, which is often the case. 
You don't want to have code that

652
00:35:35,360 --> 00:35:39,400
you have to come back to and 
continue to reiterate on SAP 

653
00:35:39,440 --> 00:35:43,160
Build is creating that platform 
for developers to be able to 

654
00:35:43,160 --> 00:35:45,960
take advantage of all these 
integration and tools and 

655
00:35:45,960 --> 00:35:48,080
frameworks that is underneath 
the scenes. 

656
00:35:48,080 --> 00:35:50,080
So how would I have another 
question for you. 

657
00:35:50,080 --> 00:35:53,320
So I mean we heard about the 
benefits of using build that you

658
00:35:53,320 --> 00:35:56,400
get faster leveraging AI and so 
on and for forth. 

659
00:35:56,720 --> 00:35:59,960
But what do you think are the 
potential business risks of not 

660
00:35:59,960 --> 00:36:02,600
taking advantage of local tools,
Gen. 

661
00:36:02,600 --> 00:36:06,840
AI, and so on and so forth? 
So I think we need to look back 

662
00:36:06,840 --> 00:36:09,320
to the last time we had a change
like this in in business. 

663
00:36:09,320 --> 00:36:12,440
And I don't think I'm being 
hyperbolic when I say think 

664
00:36:12,440 --> 00:36:15,080
about this much like looking 
back on the industrial 

665
00:36:15,080 --> 00:36:18,160
revolution, right? 
The industrial revolution added 

666
00:36:18,160 --> 00:36:21,680
machines to every single thing 
that we did, right? 

667
00:36:21,720 --> 00:36:27,360
So let's say you make clothes 
and on Friday your competition 

668
00:36:27,360 --> 00:36:33,000
went home and they wiped out the
floor and they replaced the 

669
00:36:33,000 --> 00:36:36,560
floor with automated machines 
and all of a sudden your looms 

670
00:36:36,560 --> 00:36:38,680
were automated and you had 
sewing machines. 

671
00:36:39,600 --> 00:36:44,400
Your competition did that right?
Your job is to produce clothes 

672
00:36:44,400 --> 00:36:47,560
for the working person, for 
regular people that need to go 

673
00:36:47,560 --> 00:36:50,520
to work. 
Machines are going to do that 

674
00:36:50,520 --> 00:36:54,640
5/10/20 times faster. 
And the beautiful part is 

675
00:36:54,760 --> 00:36:56,440
they're also going to do it 
reliably. 

676
00:36:56,440 --> 00:36:59,640
The stitch is always the same 
distance from the last stitch, 

677
00:37:00,480 --> 00:37:01,960
right? 
And so your consistency is 

678
00:37:01,960 --> 00:37:03,400
improved. 
We could argue all day long 

679
00:37:03,400 --> 00:37:06,440
about whether that's better 
quality or not, but the fact is 

680
00:37:06,600 --> 00:37:08,560
it's also cheaper for them to 
produce. 

681
00:37:08,720 --> 00:37:10,800
So now all of a sudden they have
a competitive advantage. 

682
00:37:11,120 --> 00:37:16,080
Well, that's where we are today.
If you have to have a mix of 

683
00:37:17,520 --> 00:37:22,960
let's say 30 junior developers, 
20 mid level developers, and 50 

684
00:37:22,960 --> 00:37:27,480
senior developers to make your 
stack work, you have top loaded 

685
00:37:27,480 --> 00:37:30,400
yourself in a way that's just 
going to cost you. 

686
00:37:30,640 --> 00:37:33,440
How do you keep onboarding 
senior developers at that rate? 

687
00:37:33,760 --> 00:37:35,880
How do you keep promoting people
and make sure that you have 

688
00:37:35,880 --> 00:37:36,960
them? 
Well, you're not doing it just 

689
00:37:36,960 --> 00:37:42,000
internally, so you're constantly
relying on some source to 

690
00:37:42,000 --> 00:37:45,120
continue to add there. 
Well, so is everyone else. 

691
00:37:45,480 --> 00:37:49,880
By adopting these tools and by 
shifting that paradigm, you're 

692
00:37:49,880 --> 00:37:54,920
faster, you're more efficient, 
and you're providing a long term

693
00:37:54,920 --> 00:37:58,280
path for developers through the 
entire cycle. 

694
00:37:58,560 --> 00:38:03,160
It is always cheaper to promote 
from within when you have the 

695
00:38:03,160 --> 00:38:06,160
dental capability. 
And one of the advantages that's

696
00:38:06,160 --> 00:38:09,960
not immediately apparent in all 
of this is because your junior 

697
00:38:09,960 --> 00:38:14,000
developers are more effective. 
They feel like they're more 

698
00:38:14,000 --> 00:38:16,440
valuable and they actually are 
more valuable, right? 

699
00:38:16,440 --> 00:38:18,720
So their morale is improved, 
plus their values improved. 

700
00:38:19,320 --> 00:38:22,520
Also, they can start spending 
more time understanding what 

701
00:38:22,520 --> 00:38:24,880
your users are trying to do, 
what the business is trying to 

702
00:38:24,880 --> 00:38:28,160
do and how the business works. 
So you're also, while you're, 

703
00:38:28,160 --> 00:38:30,520
you're, you're allowing them to 
contribute to code at a rate 

704
00:38:30,520 --> 00:38:33,960
that was simply not possible 
before, you're also allowing 

705
00:38:33,960 --> 00:38:37,040
them to build that tribal 
knowledge that has tremendous 

706
00:38:37,040 --> 00:38:40,400
value. 
Tribal knowledge builds loyalty.

707
00:38:41,000 --> 00:38:43,080
People feel comfortable, they 
start to feel like they have a 

708
00:38:43,080 --> 00:38:45,400
home. 
And your ability to now promote 

709
00:38:45,400 --> 00:38:48,560
and grow from within drastically
increases. 

710
00:38:49,480 --> 00:38:53,080
And because you don't need them 
to be experts at absolutely 

711
00:38:53,080 --> 00:38:57,120
everything, you can also now 
focus on, cool, I have 3 

712
00:38:57,120 --> 00:39:00,400
developers that actually 
understand how networking works.

713
00:39:00,600 --> 00:39:01,880
Good. 
That's how they're going to be 

714
00:39:01,880 --> 00:39:03,840
senior developers, right? 
We're going to start getting 

715
00:39:03,840 --> 00:39:05,960
away from these kind of Jack of 
all trades. 

716
00:39:06,200 --> 00:39:08,720
And we're going to allow people 
to specialize more in the things

717
00:39:08,720 --> 00:39:11,960
that they want to be good at 
because AI will make them a Jack

718
00:39:11,960 --> 00:39:18,360
of all trades, right? 
I was at GIT last year and I 

719
00:39:18,360 --> 00:39:20,240
think they really missed an 
opportunity because what they 

720
00:39:20,240 --> 00:39:22,120
were basically saying was 
everyone's a developer. 

721
00:39:22,120 --> 00:39:24,760
No, everybody's not going to be 
a developer, right? 

722
00:39:25,680 --> 00:39:30,160
What they missed was if today 
you're a database developer, if 

723
00:39:30,160 --> 00:39:33,200
today you're a React developer, 
if today you're a back end or 

724
00:39:33,200 --> 00:39:37,080
front end or whatever kind of 
developer you are tomorrow with 

725
00:39:37,200 --> 00:39:40,480
AI, you will be a full stack 
developer and you won't have to 

726
00:39:40,480 --> 00:39:42,840
change and want them move away 
from the thing that you like. 

727
00:39:43,160 --> 00:39:45,640
And the deep knowledge that 
really gets all of us excited 

728
00:39:45,640 --> 00:39:49,600
about working in tech, right? 
We're all kind of nerds in our 

729
00:39:49,600 --> 00:39:51,400
own way. 
And nerds really like to dig 

730
00:39:51,400 --> 00:39:53,480
into things We like to do the 
thing we like and we don't like 

731
00:39:53,480 --> 00:39:56,440
to do the thing we don't like. 
Well, AI's advantage is not in 

732
00:39:56,440 --> 00:39:59,080
doing the thing that you like. 
AI's advantage is in doing the 

733
00:39:59,080 --> 00:40:02,880
thing you don't like, right? 
So we all want well, 

734
00:40:02,880 --> 00:40:05,480
well-rounded employees. 
And if you don't start taking 

735
00:40:05,480 --> 00:40:09,160
advantage of this today, and if 
you don't make this part of your

736
00:40:09,280 --> 00:40:12,840
company lexicon a part of your 
company culture and really make 

737
00:40:12,840 --> 00:40:15,080
it so that your people are 
comfortable in using these 

738
00:40:15,080 --> 00:40:18,480
tools. 
You're going to be left behind. 

739
00:40:18,760 --> 00:40:22,440
You're going to lose the 
greatest technical advantage 

740
00:40:22,440 --> 00:40:26,720
that you could possibly have 
because you can't move fast 

741
00:40:26,720 --> 00:40:28,920
enough. 
And I will say, most companies 

742
00:40:28,920 --> 00:40:32,160
that aren't moving, they're not 
moving for exactly the wrong 

743
00:40:32,160 --> 00:40:33,600
reasons. 
They're not moving because they 

744
00:40:33,600 --> 00:40:37,160
can't figure out the bureaucracy
because they can't figure out 

745
00:40:37,440 --> 00:40:41,040
the how to overcome the fear, 
right? 

746
00:40:41,560 --> 00:40:44,480
Start with things that are low 
risk. 

747
00:40:44,480 --> 00:40:49,760
Low risk is defined by the data 
you put in, not anything else. 

748
00:40:51,240 --> 00:40:54,360
Put in low risk data and you 
will get massive returns. 

749
00:40:54,360 --> 00:40:56,600
Yeah, I totally agree with all 
the points you've shared. 

750
00:40:57,680 --> 00:41:02,160
All right, so then we both or we
all know, I mean we're free in 

751
00:41:02,160 --> 00:41:04,520
the rounds. 
So both is not still there. 

752
00:41:04,760 --> 00:41:08,800
But anyways we know that 
customers can easily extend and 

753
00:41:08,800 --> 00:41:16,160
integrate SAP systems and also 
non SAP systems to build 

754
00:41:16,160 --> 00:41:19,400
applications. 
So, but, but what if the 

755
00:41:19,400 --> 00:41:23,120
customers have a very complex 
mix of systems, so a lot of SAP 

756
00:41:23,160 --> 00:41:27,280
systems cloud on premise, a lot 
of third party solutions. 

757
00:41:27,280 --> 00:41:30,480
So how does SAP Build enable 
these companies to integrate 

758
00:41:30,600 --> 00:41:35,440
both SAP and non SAP solutions 
easily in the in the process and

759
00:41:35,440 --> 00:41:38,400
the development phase? 
Yeah. 

760
00:41:38,400 --> 00:41:39,880
And I can talk about that a 
little bit. 

761
00:41:40,840 --> 00:41:44,600
You know, from an SAP build 
standpoint, again, we're we're 

762
00:41:44,600 --> 00:41:50,080
running on the BTP stack. 
One of the biggest services in 

763
00:41:50,080 --> 00:41:55,760
BTP is our integration suite. 
Now integration suite allows you

764
00:41:55,760 --> 00:42:00,600
to integrate to thousands of AP 
is it has hundreds of these 

765
00:42:00,600 --> 00:42:05,880
cloud connectors that open you 
up to connecting to Adobe, 

766
00:42:05,880 --> 00:42:09,480
Microsoft, ServiceNow, 
government resources. 

767
00:42:09,480 --> 00:42:14,720
So there's all this integration 
stack that we have that is 

768
00:42:14,720 --> 00:42:19,360
inherent to SAP Build. 
So anything that you put into 

769
00:42:19,360 --> 00:42:22,640
SAP build, we can create 
services on top of. 

770
00:42:22,640 --> 00:42:26,200
So if we have direct connections
into those back ends or if we 

771
00:42:26,200 --> 00:42:29,640
need to develop our own Odata 
services or Restful services and

772
00:42:29,640 --> 00:42:33,480
we can do that. 
And that's the, that's the thing

773
00:42:33,480 --> 00:42:38,440
about SAP build is that we're 
not just developing for SAP. 

774
00:42:39,000 --> 00:42:41,880
We're developing for these 
heterogeneous environments. 

775
00:42:42,400 --> 00:42:45,960
One of the things that we 
announced with SAP is BDC, 

776
00:42:45,960 --> 00:42:47,240
right? 
And one of the things that they 

777
00:42:47,240 --> 00:42:49,320
like to talk about is harmonized
data. 

778
00:42:49,640 --> 00:42:52,720
Harmonized data means we're 
pulling it from these Adobe 

779
00:42:52,720 --> 00:42:56,360
Systems or the service now as 
our sales force and actually 

780
00:42:56,360 --> 00:42:59,400
putting it into the hands of our
developers. 

781
00:42:59,400 --> 00:43:02,320
And SAP Build specializes at 
that, right? 

782
00:43:02,440 --> 00:43:05,480
Who cares what the back end is? 
Let me create these 

783
00:43:05,480 --> 00:43:08,240
visualizations. 
Let me create these applications

784
00:43:08,600 --> 00:43:11,880
that are based off of multiple 
different systems and 

785
00:43:11,880 --> 00:43:15,720
integration suite and the back 
end connectors that SAP Build 

786
00:43:15,720 --> 00:43:19,880
has allows our customers to be 
able to do that where the end 

787
00:43:19,880 --> 00:43:22,520
user has no idea. 
They don't care where the back 

788
00:43:22,520 --> 00:43:24,360
end is, they just want nice 
data. 

789
00:43:24,360 --> 00:43:27,360
They want insight into their 
applications and that's where we

790
00:43:27,600 --> 00:43:29,920
can kind of see SAP Build 
growing towards. 

791
00:43:30,840 --> 00:43:32,160
Yeah. 
Thanks, Mark for touching on 

792
00:43:32,160 --> 00:43:34,280
that. 
So Howard, let's come back to 

793
00:43:34,280 --> 00:43:37,480
you then. 
We want to be 100% transparent 

794
00:43:37,480 --> 00:43:40,680
in this podcast as well. 
And you also have some risks 

795
00:43:40,680 --> 00:43:42,560
identified and shared in the 
paper. 

796
00:43:42,800 --> 00:43:46,480
So can you please touch on them?
So when we look at risks of 

797
00:43:46,480 --> 00:43:50,480
using Jewel, one of the things 
that you really want to pay 

798
00:43:50,480 --> 00:43:53,760
attention to is the risks have 
not changed. 

799
00:43:55,080 --> 00:43:59,720
Almost all of the risks are 
directly related to your data 

800
00:43:59,720 --> 00:44:06,800
quality, the specific governance
requirements for the data, and 

801
00:44:08,120 --> 00:44:11,480
your ability to properly test. 
And these are the things where 

802
00:44:11,560 --> 00:44:14,360
software development teams have 
had have had struggles forever. 

803
00:44:14,840 --> 00:44:19,200
It's not really changing. 
However, the velocity to which 

804
00:44:19,200 --> 00:44:24,040
you produce applications is 
going to drastically increase. 

805
00:44:24,360 --> 00:44:27,640
So it is going to exacerbate any
of those issues that you have. 

806
00:44:27,640 --> 00:44:30,480
So you really do want to pay 
attention, especially early in 

807
00:44:30,480 --> 00:44:33,680
the process. 
So before I even started with 

808
00:44:33,680 --> 00:44:37,280
build, what I would do is I 
would look at what are the data 

809
00:44:37,280 --> 00:44:42,680
sets that we have that contain 
the least amount of risk and how

810
00:44:42,680 --> 00:44:45,880
can I define those? 
And then I would also look at 

811
00:44:46,080 --> 00:44:49,640
what other tests we're going to 
use to not only validate that 

812
00:44:49,640 --> 00:44:52,960
the application works, but what 
are the tests we're going to use

813
00:44:52,960 --> 00:44:57,480
to validate that the data we get
back is de risk it Sorry, is de 

814
00:44:57,480 --> 00:45:01,120
risked. 
That's such a clunky thing to 

815
00:45:01,120 --> 00:45:03,680
say, but we really want to pay 
attention to those, right. 

816
00:45:04,440 --> 00:45:07,720
There's no additional risk that 
I see that SAP has that other 

817
00:45:07,960 --> 00:45:10,800
kind of Gen. 
AI vibe coding tools don't 

818
00:45:10,800 --> 00:45:13,520
already have. 
They're all there. 

819
00:45:13,520 --> 00:45:18,840
But as velocity increases, so 
does every risk you have from 

820
00:45:18,840 --> 00:45:23,080
poor process, from poor policy 
and from poor procedure. 

821
00:45:23,200 --> 00:45:26,360
So you really want to say, OK, 
if we're going to speed up the, 

822
00:45:26,440 --> 00:45:31,760
the, the time it takes for us to
get results, let's invest some 

823
00:45:31,760 --> 00:45:35,440
of that time into fixing the pre
and post things that maybe we 

824
00:45:35,440 --> 00:45:38,840
were, we were taking a little 
shortcut in so that we could, we

825
00:45:38,840 --> 00:45:41,160
could maintain a velocity that 
was acceptable, right. 

826
00:45:41,160 --> 00:45:45,480
Maybe we don't give all of that 
59%, maybe we don't give all of 

827
00:45:45,480 --> 00:45:48,320
that 3X performance improvement 
back to the business directly 

828
00:45:48,320 --> 00:45:49,920
and start by producing more 
code. 

829
00:45:50,120 --> 00:45:53,080
Maybe initially we take some of 
that performance improvement, 

830
00:45:53,640 --> 00:45:55,960
right. 
Maybe we give back a 40% 

831
00:45:55,960 --> 00:46:01,160
improvement in speed and we take
the 2.6 leftover or 1.6 

832
00:46:01,160 --> 00:46:04,880
leftover, sorry. 
And we invest that into really 

833
00:46:04,880 --> 00:46:07,720
making sure that our policies 
and procedures are good, that we

834
00:46:07,720 --> 00:46:11,200
really give people the time 
necessary to to architect on the

835
00:46:11,200 --> 00:46:13,360
front end and to test on the 
back end. 

836
00:46:13,960 --> 00:46:16,800
Because the better we are at 
those things, the better this 

837
00:46:16,800 --> 00:46:20,880
whole thing is going to be and 
the more production ready our 

838
00:46:20,880 --> 00:46:23,080
code is going to be when we 
first turn it over to our users.

839
00:46:23,080 --> 00:46:24,960
And we really want to make sure 
we're on top of that. 

840
00:46:25,240 --> 00:46:28,640
We do not want to accelerate 
making mistakes when it comes to

841
00:46:28,640 --> 00:46:30,560
data and data access. 
All right. 

842
00:46:30,560 --> 00:46:33,360
Anything else to to add from 
your side mark? 

843
00:46:34,520 --> 00:46:36,840
Not so much. 
I mean, I know the paper touched

844
00:46:36,840 --> 00:46:41,640
on, you know, community support,
right, SAP as an SAP community, 

845
00:46:41,640 --> 00:46:45,080
but it may not have as large of 
a community outside of, you 

846
00:46:45,080 --> 00:46:47,480
know, sitting on Stack Overflow 
or Reddit. 

847
00:46:47,480 --> 00:46:51,600
And you know, we, we continue to
may are aware of that, right. 

848
00:46:51,600 --> 00:46:55,240
So I know some of the developers
in Gigom kind of pointed that 

849
00:46:55,240 --> 00:47:00,680
out where you, you more are 
learning from your internal 

850
00:47:00,680 --> 00:47:05,560
resources and the SAP resources 
instead of a larger community. 

851
00:47:05,560 --> 00:47:08,920
And we continue to grow that 
community to, to help refine 

852
00:47:08,920 --> 00:47:10,640
that. 
But that was one of the things I

853
00:47:10,640 --> 00:47:13,840
know that was pointed out in the
paper that you have to be aware 

854
00:47:13,840 --> 00:47:16,320
of, right? 
I mean, because you go to an 

855
00:47:16,320 --> 00:47:21,040
open source type solution and 
there's going to be a, a bigger 

856
00:47:21,040 --> 00:47:24,160
community to support you from an
external perspective. 

857
00:47:24,760 --> 00:47:29,280
But SAP looks at it from an SAP 
partner kind of support network.

858
00:47:30,520 --> 00:47:31,280
All right. 
Yeah. 

859
00:47:31,280 --> 00:47:34,440
So then I have one further 
question for you, Mark. 

860
00:47:34,440 --> 00:47:39,040
So, I mean, I know the reports 
touched on using build in 

861
00:47:39,040 --> 00:47:43,480
combination with the CUP model, 
but we also have ABAP Cloud as 

862
00:47:43,480 --> 00:47:45,840
part of Build as an offering, 
right? 

863
00:47:45,840 --> 00:47:50,840
So what what's your opinion on 
using JEWEL in combination with 

864
00:47:50,840 --> 00:47:54,280
ABAP Cloud? 
Because it's, yeah, quite new, I

865
00:47:54,280 --> 00:47:56,440
would say. 
No, it's a great question. 

866
00:47:56,440 --> 00:47:59,120
It's of course a very hot topic 
inside of SAP. 

867
00:47:59,880 --> 00:48:03,440
The report didn't use ABOP, but 
of course if you're connecting 

868
00:48:03,440 --> 00:48:07,560
to an ask for back end as HOBOP 
is natively there, right. 

869
00:48:07,560 --> 00:48:12,760
So ABOP itself or anybody that 
doesn't know, it's a 50 year old

870
00:48:12,760 --> 00:48:14,600
tool or development language, 
right? 

871
00:48:14,600 --> 00:48:17,640
Do we it? 
We are built on top of ABAP. 

872
00:48:17,640 --> 00:48:20,880
So that means a ton of our 
companies or ton of the 

873
00:48:21,160 --> 00:48:23,880
customers out there, they're all
running on ABAP. 

874
00:48:23,880 --> 00:48:25,880
So it's a very special 
development stack. 

875
00:48:26,280 --> 00:48:29,840
And when we look at it, it goes 
back to Howard talking about you

876
00:48:29,840 --> 00:48:31,400
have to get developers up to 
speed. 

877
00:48:31,600 --> 00:48:34,880
You have to have junior 
developers that can look at an, 

878
00:48:34,960 --> 00:48:39,760
an, an existing code or what you
would maybe call legacy code and

879
00:48:39,960 --> 00:48:42,880
be able to understand it. 
And a lot of times that's 

880
00:48:42,880 --> 00:48:46,160
difficult, right? 
But what we did with the AB AI 

881
00:48:46,160 --> 00:48:51,040
piece inside of build is we 
trained the LM model on about 3 

882
00:48:51,040 --> 00:48:55,320
1/2 million lines of code inside
of SAP because we have all that 

883
00:48:55,320 --> 00:48:58,800
code to train it off. 
So this the nice thing about 

884
00:48:58,800 --> 00:49:03,880
Jewel and ABAP is now a junior 
developer can come in and it can

885
00:49:03,880 --> 00:49:06,480
do code explanation. 
What is this code actually doing

886
00:49:06,480 --> 00:49:10,320
because I don't know ABAP and 
how do I make it more efficient 

887
00:49:10,320 --> 00:49:15,360
from legacy ABAP into ABAP cloud
and how do I migrate into what 

888
00:49:15,360 --> 00:49:19,560
we call clean core. 
So the the LMMS that we built 

889
00:49:19,560 --> 00:49:24,160
for ABAP Cloud are a very 
special trained LMM. 

890
00:49:24,320 --> 00:49:26,880
And now you're going to see more
developers being able to take 

891
00:49:26,880 --> 00:49:31,680
advantage of ABAP and also know 
how to migrate or take advantage

892
00:49:31,680 --> 00:49:34,760
of CAP and that develop in 
JavaScript. 

893
00:49:34,760 --> 00:49:38,120
So we're kind of merging the two
worlds so that developers of 

894
00:49:38,120 --> 00:49:42,120
today and developers of ABAP 
have these trained models and 

895
00:49:42,120 --> 00:49:47,640
you'll see more advances in the 
ABAP LLM where we're doing full 

896
00:49:47,640 --> 00:49:52,880
code migration or being able to 
help take from on premise to 

897
00:49:52,880 --> 00:49:56,080
cloud. 
So yeah, it's, it's exciting to 

898
00:49:56,080 --> 00:49:58,600
see, but we get a lot of 
feedback. 

899
00:49:58,600 --> 00:50:01,040
Of course, I'm biased, but I 
think it's amazing. 

900
00:50:01,040 --> 00:50:04,640
I think it's great to be able to
take ABAP into the next 

901
00:50:04,640 --> 00:50:07,520
generation, right? 
Yeah, I wish this code 

902
00:50:07,520 --> 00:50:11,080
explanation has been existing in
the past already, but yeah, I 

903
00:50:11,080 --> 00:50:13,080
think it's awesome as well. 
All right. 

904
00:50:13,080 --> 00:50:16,960
So Howard, anything else you 
want to mention pointing out 

905
00:50:16,960 --> 00:50:19,760
from the report before we come 
into our closing question? 

906
00:50:21,120 --> 00:50:24,120
Yes, the the final thing I want 
to talk about in the report is 

907
00:50:24,680 --> 00:50:29,160
Gigom really did the best we 
could do to really present this 

908
00:50:29,160 --> 00:50:34,520
as objectively as possible. 
However, I I encourage you to 

909
00:50:34,520 --> 00:50:36,960
make your own decision. 
I encourage you read the report 

910
00:50:36,960 --> 00:50:41,600
as one of many pieces of 
information, not the only piece 

911
00:50:41,600 --> 00:50:43,600
of information. 
Look, I'd love if we were the 

912
00:50:43,600 --> 00:50:45,440
absolute authority in the world 
on everything. 

913
00:50:45,640 --> 00:50:47,800
Haven't figured out how to be 
that yet, right? 

914
00:50:47,800 --> 00:50:50,280
I'm not confident enough in 
myself and my own skills. 

915
00:50:50,520 --> 00:50:52,880
Me and my team are spending a 
tremendous amount of time 

916
00:50:52,880 --> 00:50:57,680
learning every week. 
So please use the report if you 

917
00:50:57,680 --> 00:51:00,720
have any questions about it. 
If you have any any complaints, 

918
00:51:00,720 --> 00:51:02,880
if you want to kind of dig in, 
feel free to shoot me an e-mail.

919
00:51:03,200 --> 00:51:05,280
You can hit me up on LinkedIn. 
It's a great way to find me. 

920
00:51:05,280 --> 00:51:09,000
I'm I'm there all the time. 
I'd love, I'd love to to hear 

921
00:51:09,000 --> 00:51:11,120
your feedback. 
Yeah, thanks for these words. 

922
00:51:11,520 --> 00:51:14,320
So with that, we come to the end
of our podcast. 

923
00:51:14,320 --> 00:51:18,800
At the end, we usually ask our 
guests for any kind of final 

924
00:51:18,800 --> 00:51:21,680
recommendation. 
It can be a book, it can be a 

925
00:51:21,680 --> 00:51:24,880
movie, it can be series, it can 
be work related or just 

926
00:51:24,880 --> 00:51:26,800
something you enjoy in your 
private time. 

927
00:51:27,280 --> 00:51:29,760
So Howard, what about you? 
What do you want to recommend to

928
00:51:29,760 --> 00:51:31,680
our listeners now? 
Sure. 

929
00:51:31,680 --> 00:51:34,160
So that's a great question. 
Oh, yeah, All right. 

930
00:51:34,160 --> 00:51:35,160
Sure. 
That's a great question. 

931
00:51:36,840 --> 00:51:39,880
Soft skills are really hard to 
add and and we spend a ton of 

932
00:51:39,880 --> 00:51:43,560
time like learning how to be 
managers, which is filling out 

933
00:51:43,560 --> 00:51:45,360
forms and moving them through 
the business. 

934
00:51:45,360 --> 00:51:48,080
We don't spend a lot of time 
learning how to be leaders and 

935
00:51:48,080 --> 00:51:50,480
being a leader is so incredibly 
important. 

936
00:51:51,240 --> 00:51:54,160
I was lucky enough to take a a 
management course from 2020 to 

937
00:51:54,160 --> 00:51:57,160
like 2024 and I highly recommend
that to everyone. 

938
00:51:57,160 --> 00:51:59,320
And it's it's almost completely 
free. 

939
00:51:59,520 --> 00:52:02,280
It's highly available, It's 
really entertaining. 

940
00:52:02,920 --> 00:52:05,520
It's on Ale TV. 
It's called Tedlasso. 

941
00:52:06,560 --> 00:52:10,360
If you haven't watched Ted 
Lasso, it's supposed to be this 

942
00:52:10,360 --> 00:52:14,800
kind of fish out of water comedy
about an American who's never 

943
00:52:14,800 --> 00:52:19,520
played soccer and goes to be the
head coach of a premier Football

944
00:52:19,600 --> 00:52:24,560
League in the UK. 
And he is an enormous fish out 

945
00:52:24,560 --> 00:52:27,120
of water, and you would expect 
it to kind of be great. 

946
00:52:27,120 --> 00:52:28,840
He's going to be the butt of all
the jokes. 

947
00:52:29,040 --> 00:52:33,320
It is not that show at all. 
It is hands down, and I am not 

948
00:52:33,320 --> 00:52:37,000
making a joke, The best 
leadership course I have ever 

949
00:52:37,000 --> 00:52:38,560
seen in my life is three 
seasons. 

950
00:52:38,800 --> 00:52:41,480
It's a ton of fun. 
I highly recommend it. 

951
00:52:42,080 --> 00:52:46,440
It's full of laughs, but it's 
also got this really deep kind 

952
00:52:46,440 --> 00:52:48,280
of leadership. 
You know how to be a leader, how

953
00:52:48,280 --> 00:52:51,120
to pull the best out of people. 
It's got this wonderful subtext 

954
00:52:51,120 --> 00:52:52,760
that that I really wish more 
shows had. 

955
00:52:52,760 --> 00:52:55,800
OK, I need to check that out 
because I have Apple TV Plus but

956
00:52:55,800 --> 00:52:57,440
I never use it. 
So that's a good idea. 

957
00:52:57,440 --> 00:52:59,280
Then. 
What about you, Mark? 

958
00:53:00,160 --> 00:53:01,760
No, that's an awesome 
recommendation. 

959
00:53:01,760 --> 00:53:04,600
I'm a big soccer fan. 
I just saw, you know, PSG 

960
00:53:04,600 --> 00:53:06,760
interval honors going to the 
Champions League. 

961
00:53:06,760 --> 00:53:09,080
So you know, that kind of 
relates to Ted Lasso. 

962
00:53:09,080 --> 00:53:13,080
But love, love the reference. 
You know, from from my 

963
00:53:13,080 --> 00:53:15,360
standpoint, a little bit more 
serious, you know, we're really 

964
00:53:15,360 --> 00:53:21,320
trying to look at how you do use
data in your day-to-day life. 

965
00:53:21,320 --> 00:53:24,240
So I mean, a recommendation, you
know, as you move forward in 

966
00:53:24,240 --> 00:53:27,720
your career is really how do you
associate data with your 

967
00:53:27,720 --> 00:53:30,600
day-to-day jobs, right? 
Taking a look at, you know, 

968
00:53:30,600 --> 00:53:33,480
podcasts that are out there that
really can provide you insight 

969
00:53:33,480 --> 00:53:36,760
into what you're doing. 
But again, I like the Ted Lasso.

970
00:53:36,760 --> 00:53:40,480
So I'm going to go and make sure
to renew my Apple TV for Season 

971
00:53:40,480 --> 00:53:44,200
4. 
All right, so thank you for 

972
00:53:44,200 --> 00:53:47,760
sharing then and of course, also
thank you for joining me in 

973
00:53:47,760 --> 00:53:49,480
today's episode and today's 
interviews. 

974
00:53:49,480 --> 00:53:51,560
I really appreciate that you're 
taking the time. 

975
00:53:51,560 --> 00:53:53,720
If you're brand new to the 
podcast because you just 

976
00:53:53,920 --> 00:53:57,320
discovered it in the new format,
check out our old episodes. 

977
00:53:57,600 --> 00:54:00,960
Of course, final recommendation,
check out the report from 

978
00:54:00,960 --> 00:54:03,000
Gigaon. 
It's also LinkedIn, the show 

979
00:54:03,000 --> 00:54:04,640
notes. 
And as well, if you want to make

980
00:54:04,640 --> 00:54:08,520
yourself femoralized with SAP 
Build, make sure to check out 

981
00:54:08,520 --> 00:54:11,880
one of the learning journeys 
around SAP Build time. 

982
00:54:12,280 --> 00:54:14,280
Yeah. 
And with that at yeah, as sat, 

983
00:54:14,280 --> 00:54:17,640
my name is Nicholas, product 
manager for ACPPDP, recording 

984
00:54:17,640 --> 00:54:19,480
live from the headquarters in 
Weller. 

985
00:54:19,560 --> 00:54:22,480
And yeah, see you in one of the 
next episodes, man Bye bye.

