1
00:00:11,880 --> 00:00:15,400
Welcome to the podcast Inside 
SAPS for Anna Cloud. 

2
00:00:15,560 --> 00:00:18,920
There's no customer success 
without product success and 

3
00:00:19,120 --> 00:00:22,600
project success. 
It is party time as we now in 

4
00:00:22,600 --> 00:00:26,040
2024 celebrate the 5th 
anniversary of this podcast 

5
00:00:26,040 --> 00:00:31,080
series with over 140 episodes 
published in English, Portuguese

6
00:00:31,400 --> 00:00:34,360
and Spanish. 
So I invite you to visit our 

7
00:00:34,360 --> 00:00:39,000
pages on acp.com/podcasts or on 
your favorite audio platform and

8
00:00:39,000 --> 00:00:42,760
revisit all these episodes. 
Find the product or project 

9
00:00:42,760 --> 00:00:45,800
related topic you like most and 
of course take a chance to get 

10
00:00:45,800 --> 00:00:50,200
enabled on SAPS for Anna Cloud. 
This is the main target of this 

11
00:00:50,200 --> 00:00:52,520
series. 
Share the valuable knowledge and

12
00:00:52,520 --> 00:00:56,680
expertise of SAP S for Anna 
Cloud Experts, partners, 

13
00:00:56,920 --> 00:01:00,800
customers with their own product
insights, implementation project

14
00:01:00,800 --> 00:01:03,160
best practice and lessons 
learns. 

15
00:01:03,680 --> 00:01:07,520
And that's what we've done with 
more than 170 guests we have 

16
00:01:07,520 --> 00:01:11,560
invited in the last five years 
with more than fifty partners 

17
00:01:11,560 --> 00:01:15,520
and 25 customers. 
It's been an incredible journey 

18
00:01:15,520 --> 00:01:18,760
and we want to thank everyone 
who's join us on this adventure.

19
00:01:19,280 --> 00:01:22,320
To mark this special occasion, 
we've invited 2 guests. 

20
00:01:22,800 --> 00:01:26,560
Bertrutzer, the head of Claudia 
P Product success with ACP. 

21
00:01:27,360 --> 00:01:30,040
Hi Bert, we checked our archive 
and found that you joined this 

22
00:01:30,040 --> 00:01:33,000
podcast already. 
Do you have any idea when that 

23
00:01:33,000 --> 00:01:36,640
was and what you talked about? 
Oh first, thanks so much for 

24
00:01:36,640 --> 00:01:39,200
having me. 
Great format and actually I 

25
00:01:39,200 --> 00:01:42,160
can't recall the session to be 
honest, but the fact that you 

26
00:01:42,160 --> 00:01:45,920
invited me again indicates that 
it must have been a best seller.

27
00:01:46,440 --> 00:01:50,320
But joke aside, I know it was 
somewhere amongst the 1st 10 

28
00:01:50,320 --> 00:01:54,520
episodes and focus on business 
impact and digital and 

29
00:01:54,520 --> 00:01:56,320
subscription economy if I'm not 
mistaken. 

30
00:01:56,840 --> 00:01:58,720
It was actually the episode 
number 2, Bert. 

31
00:01:58,720 --> 00:02:02,840
It was the very beginning of the
podcast in 2019 and we talked 

32
00:02:02,840 --> 00:02:06,240
about the impact of business 
transformation on core EIP 

33
00:02:06,240 --> 00:02:09,759
processes, the cloud mindset and
all that stuff that will guide 

34
00:02:09,759 --> 00:02:13,800
us until today. 
And today I said the SP partners

35
00:02:13,800 --> 00:02:17,080
also a big part of the story. 
That's why we have one of them 

36
00:02:17,520 --> 00:02:20,200
here with us today. 
I'm very pleased to have Florian

37
00:02:20,200 --> 00:02:21,920
Heusler from the partner in 
Novabi. 

38
00:02:22,440 --> 00:02:25,880
Florian is the CEO of the 
company who's a grow with SAP 

39
00:02:25,880 --> 00:02:28,520
partner focusing on SMB based in
Germany. 

40
00:02:28,960 --> 00:02:31,560
You know, there'll be one many 
awards like the best consulting 

41
00:02:31,560 --> 00:02:34,520
house for SMB in 2024 from the 
Virtuos War. 

42
00:02:34,800 --> 00:02:37,640
They've won several SAP quality 
awards too and more. 

43
00:02:37,640 --> 00:02:39,960
And today I'm very pleased to 
have you Florian with us. 

44
00:02:40,360 --> 00:02:42,680
Welcome. 
It's a pleasure to see you 

45
00:02:42,720 --> 00:02:44,720
virtually. 
Thank you very much. 

46
00:02:44,720 --> 00:02:47,680
It's also a pleasure. 
And first of all, happy birthday

47
00:02:47,680 --> 00:02:50,720
for your 5th anniversary. 
So great format. 

48
00:02:50,840 --> 00:02:54,400
I'm looking forward to talking 
with you together today about 

49
00:02:54,400 --> 00:02:57,520
Esperhana Public. 
Yes, indeed, you mentioned it. 

50
00:02:57,800 --> 00:03:00,960
We are an early adopter SAP 
Esperhana Public Cloud. 

51
00:03:00,960 --> 00:03:07,280
And I remember it was short 
before Christmas 2017 when my 

52
00:03:07,280 --> 00:03:11,680
colleagues and myself, we joined
the kind of public cloud boot 

53
00:03:11,680 --> 00:03:15,480
camp, not knowing what is it 
actually, but it was in Munich 

54
00:03:16,040 --> 00:03:20,760
and it was two months later 
already when we started our 

55
00:03:20,760 --> 00:03:24,200
first public load project. 
And of course, we gained a lot 

56
00:03:24,200 --> 00:03:27,080
of experience within the last 
meanwhile 7 years. 

57
00:03:27,080 --> 00:03:29,760
Yeah. 
And it was really good. 

58
00:03:29,760 --> 00:03:34,200
And I'm very happy to see Bert 
again because within this kind 

59
00:03:34,200 --> 00:03:38,480
of pioneers environment where 
some partners and but also the 

60
00:03:38,480 --> 00:03:42,160
SAP was working very closely 
together, you always see the 

61
00:03:42,160 --> 00:03:45,080
same personalities. 
But that's good because as 

62
00:03:45,120 --> 00:03:49,080
ecosystem, I think we achieved a
lot within the last years. 

63
00:03:49,400 --> 00:03:52,800
It was a no brainer for me when 
Bert asked me to join this 

64
00:03:52,960 --> 00:03:56,000
university session today. 
So yeah, I'm glad to be here. 

65
00:03:56,600 --> 00:03:58,560
And this is very much 
appreciated. 

66
00:03:58,560 --> 00:04:02,400
Thanks to you both. 
So now moving to our anniversary

67
00:04:02,400 --> 00:04:05,160
podcast. 
It's not the usual podcast you 

68
00:04:05,160 --> 00:04:06,360
would expect. 
We want to have some 

69
00:04:06,360 --> 00:04:08,920
gamification because of course 
we have something to celebrate. 

70
00:04:09,280 --> 00:04:11,240
Are you ready for some 
gamification, both of you? 

71
00:04:11,920 --> 00:04:14,520
Yes, I'm in. 
Absolutely. 

72
00:04:15,040 --> 00:04:18,480
So here's the plan. 
It's very easy as we mark A5 

73
00:04:18,480 --> 00:04:20,959
year celebration. 
We've got some fun questions 

74
00:04:20,959 --> 00:04:24,600
split into 5 categories. 
We'll explore different 

75
00:04:24,600 --> 00:04:27,200
scenarios and get a little 
imaginative. 

76
00:04:27,680 --> 00:04:30,440
So feel free to play and even go
beyond the reality. 

77
00:04:30,600 --> 00:04:32,880
You tell the stories that you 
think are relevant for the 

78
00:04:32,880 --> 00:04:35,040
audience. 
So please listen carefully. 

79
00:04:35,040 --> 00:04:38,120
Here are the five topics. 
The first one is looking back, 

80
00:04:38,800 --> 00:04:44,120
second one is partner evolution 
parlay #3 topic is innovative 

81
00:04:44,120 --> 00:04:48,600
leader, Stable topic #4 is the 
Synergy Showcase. 

82
00:04:48,680 --> 00:04:51,920
And last but not least, the 
number 5 is the crystal ball. 

83
00:04:52,560 --> 00:04:55,360
Now Bert and Florian, you can 
choose one of the categories and

84
00:04:55,360 --> 00:04:57,320
I will share the questions 
behind it. 

85
00:04:57,480 --> 00:05:01,080
You can both jump in, of course,
anytime to share your point of 

86
00:05:01,080 --> 00:05:03,280
view, even if you're not leading
the answer. 

87
00:05:03,480 --> 00:05:07,800
And I also invite to add another
gamification level, I invite all

88
00:05:07,800 --> 00:05:10,080
the people are listening to the 
episode to participate. 

89
00:05:10,320 --> 00:05:13,680
So if you have an answer, a 
creative answer for the one or 

90
00:05:13,680 --> 00:05:19,360
the other questions, send us a 
note to insides4@acp.com because

91
00:05:19,360 --> 00:05:22,520
we would love to hear what you 
think about one of those five 

92
00:05:22,520 --> 00:05:24,080
categories. 
Good. 

93
00:05:24,200 --> 00:05:26,480
As your guest, Florian, today, I
want to start with you. 

94
00:05:26,480 --> 00:05:29,240
Which topic do you choose? 
OK. 

95
00:05:29,240 --> 00:05:32,720
So it's a bit like Jeopardy. 
I would say we start with 

96
00:05:32,800 --> 00:05:34,280
looking back. 
Good. 

97
00:05:34,400 --> 00:05:36,800
Then let's do back. 
What is the question? 

98
00:05:37,160 --> 00:05:41,080
What is your most memorable 
customer or partner interaction 

99
00:05:41,080 --> 00:05:42,560
you had? 
And of course, you don't need to

100
00:05:42,560 --> 00:05:47,360
share names exactly, but let us 
know which one was that and why 

101
00:05:47,360 --> 00:05:50,720
was it so memorable for you. 
OK, tough question. 

102
00:05:50,720 --> 00:05:54,440
But in five years, there were a 
lot of remarkable interaction 

103
00:05:54,440 --> 00:05:57,080
between US and our public cloud 
customers. 

104
00:05:57,520 --> 00:06:00,440
So it's hard to say which one 
was the most remarkable. 

105
00:06:00,520 --> 00:06:04,040
But next to a remarkable visit 
at the Oktoberfest in Munich 

106
00:06:04,480 --> 00:06:08,280
with one of our first public 
cloud customers, I think it was 

107
00:06:08,280 --> 00:06:13,240
the bike tour together with our 
public cloud customer KTM Bikes 

108
00:06:13,240 --> 00:06:18,760
from their headquarter in Matiko
from Austria to our headquarter 

109
00:06:18,760 --> 00:06:23,400
in Weidlingen, Germany. 
We did that after a successful 

110
00:06:23,400 --> 00:06:27,560
implementation project and the 
project team asked even me to 

111
00:06:27,560 --> 00:06:31,240
join their adventure. 
So it was a pleasure for me to 

112
00:06:31,240 --> 00:06:35,240
join also the tour. 
They did 3 stages, each stage 

113
00:06:35,240 --> 00:06:38,840
between 100 and 160 kilometers 
with the push bike. 

114
00:06:38,840 --> 00:06:43,080
And I was happy that I only 
decided to do the last one, but 

115
00:06:43,080 --> 00:06:46,120
nevertheless, it was a really 
good experience. 

116
00:06:46,120 --> 00:06:49,080
And of course, when you do 
sports, you are very close 

117
00:06:49,080 --> 00:06:51,160
together with all your project 
members. 

118
00:06:51,160 --> 00:06:53,800
And it's a little bit like in 
SAP project. 

119
00:06:54,000 --> 00:06:56,680
You need of course a road map to
getting from A to B. 

120
00:06:57,120 --> 00:07:01,600
You need a bit of endurance, 
otherwise it's hard to reach the

121
00:07:01,600 --> 00:07:04,680
finish line. 
And I think most important, you 

122
00:07:04,680 --> 00:07:06,880
need to be a team and you need 
to act like a team. 

123
00:07:06,880 --> 00:07:10,600
So there will be some 
difficulties and it's only 

124
00:07:10,680 --> 00:07:14,000
successful if you cross the 
finish line together and that we

125
00:07:14,000 --> 00:07:16,200
did. 
Finish line was at the House of 

126
00:07:16,200 --> 00:07:19,880
our CTO and he invited us and 
then we had a pool party there. 

127
00:07:19,880 --> 00:07:24,280
So it was a good, good day. 
And even if we are not meeting 

128
00:07:24,440 --> 00:07:28,520
every day, when we meet each 
other, then we remember that day

129
00:07:28,520 --> 00:07:30,720
because it was a good sunny day.
It was a lot of fun. 

130
00:07:31,320 --> 00:07:34,120
Very cool, great adventure and 
it looks like we missed a big 

131
00:07:34,120 --> 00:07:35,680
party, but next time we need to 
join. 

132
00:07:36,000 --> 00:07:39,080
Yeah, you can easily join. 
You just need to be as a pick up

133
00:07:39,080 --> 00:07:42,280
a cloud customer then this is 
open to everybody. 

134
00:07:43,080 --> 00:07:45,720
Yeah, or you can come by bike to
Wailov where you're always 

135
00:07:45,720 --> 00:07:47,960
invited. 
It's a really nice story for 

136
00:07:47,960 --> 00:07:49,600
them. 
So on my side, I also have a 

137
00:07:49,600 --> 00:07:53,040
couple of stories, but most 
likely not as sportive as yours.

138
00:07:53,560 --> 00:07:56,440
As you might know, my team runs 
Cloud Europe products success 

139
00:07:56,440 --> 00:07:57,960
for all deployments for a while 
now. 

140
00:07:58,440 --> 00:08:02,320
And when counting last time we 
had in my team and collective 

141
00:08:02,320 --> 00:08:07,640
experience of 2000 hands on S 
400 implementations on Prem, 

142
00:08:07,680 --> 00:08:11,440
private cloud, public cloud, 
rough and tough, one third each.

143
00:08:12,360 --> 00:08:15,680
And as we are now in the look 
back section and when I call out

144
00:08:15,680 --> 00:08:19,000
adrenaline as an indicator of 
the memory interaction, one 

145
00:08:19,000 --> 00:08:20,880
thing comes to my mind to be 
honest. 

146
00:08:20,920 --> 00:08:26,640
So we showcased at Sapphire 2016
the 1st As for HANA conversion 

147
00:08:26,720 --> 00:08:29,720
live on state into Hassle 
Platinum's keynote and we had at

148
00:08:29,720 --> 00:08:34,720
the same time the CIO of Asian 
Paints with us in the interview 

149
00:08:34,720 --> 00:08:37,159
because of one of the first 
adopters. 

150
00:08:37,320 --> 00:08:41,520
Honestly, my hands still sweats 
if I think back of how many 

151
00:08:41,520 --> 00:08:46,160
moving parts could have gone S 
today near 0 downtime is almost 

152
00:08:46,160 --> 00:08:48,080
a commodity for private cloud 
customers. 

153
00:08:48,240 --> 00:08:52,040
And in public cloud, I think we 
upgrade now multiple thousand 

154
00:08:52,040 --> 00:08:55,640
systems twice a year, most 
likely fully automated. 

155
00:08:55,800 --> 00:08:59,200
And we also ship months in CFDS 
fully non disruptive into our 

156
00:08:59,200 --> 00:09:02,360
customer systems. 
At that point in time, none of 

157
00:09:02,360 --> 00:09:06,720
these existed and all what we 
showed were handcrafted. 

158
00:09:07,120 --> 00:09:09,920
This has been really an amazing 
journey to be honest. 

159
00:09:09,920 --> 00:09:13,000
If I look back, Yannick, it even
goes beyond the five years of 

160
00:09:13,000 --> 00:09:16,520
your podcast series. 
And I remember that quite well, 

161
00:09:16,520 --> 00:09:17,360
to be honest. 
Beth. 

162
00:09:17,760 --> 00:09:19,880
Good, great, thanks, both. 
Let's move on. 

163
00:09:19,880 --> 00:09:21,360
That's tackle. 
Now your turn to pick a 

164
00:09:21,360 --> 00:09:24,160
category. 
I just repeat briefly #2 partner

165
00:09:24,160 --> 00:09:29,000
evolution parlay #3 Innovative 
Leaders table #4 the Synergy 

166
00:09:29,000 --> 00:09:32,320
showcase #5 the crystal ball. 
Which topic would you like to 

167
00:09:32,320 --> 00:09:34,280
choose? 
Then I go for a synergy 

168
00:09:34,280 --> 00:09:36,400
showcase. 
OK, good pick. 

169
00:09:36,400 --> 00:09:37,720
Let's have a look at the 
question. 

170
00:09:37,720 --> 00:09:41,720
And the question is what was the
1st S4 implementation you 

171
00:09:41,720 --> 00:09:44,520
facilitated? 
Tell us a bit about it and maybe

172
00:09:44,520 --> 00:09:47,720
reflect how would you approach 
it today, a couple years later 

173
00:09:47,720 --> 00:09:49,640
as we now know? 
So what? 

174
00:09:50,280 --> 00:09:53,320
To be honest, this is pretty 
much close to what I just shared

175
00:09:53,320 --> 00:09:54,840
a bit, right? 
Because this has been really the

176
00:09:54,840 --> 00:09:58,520
first implementation and also 
the experience will be shared at

177
00:09:58,520 --> 00:10:02,840
Sapphire back in 2016. 
But when I founded the Asfahana 

178
00:10:02,840 --> 00:10:07,680
Regional Implementation Group 
back in 2015, we took almost 

179
00:10:07,680 --> 00:10:11,120
each implementing customer by 
the hand and help them to really

180
00:10:11,120 --> 00:10:13,320
get one way or the other through
the finishing line. 

181
00:10:13,800 --> 00:10:18,400
And as in 2015, the 1511 release
was our first release. 

182
00:10:18,400 --> 00:10:21,880
We were so proud when we saw the
first customer also go live on 

183
00:10:21,880 --> 00:10:24,200
S4. 
This was a company called Swiss 

184
00:10:24,200 --> 00:10:26,040
Property. 
I think if you Google it, you 

185
00:10:26,040 --> 00:10:28,960
can still find the digital 
signature of those 

186
00:10:28,960 --> 00:10:31,880
announcements. 
Back then they went live early 

187
00:10:31,880 --> 00:10:37,200
2016 and you can't really 
imagine how big that event was. 

188
00:10:37,200 --> 00:10:40,480
So maybe we should have then 
also went to pro and CTO for 

189
00:10:40,480 --> 00:10:44,040
that party approach because 
we've done so much also behind 

190
00:10:44,040 --> 00:10:47,640
the scenes to really make sure 
that this customer then going 

191
00:10:47,640 --> 00:10:49,880
live happily in that overall 
setting. 

192
00:10:49,880 --> 00:10:54,160
And today with a large amount of
customers on S4, I mean it go 

193
00:10:54,160 --> 00:10:58,400
live even on social media today 
is almost like a non event, 

194
00:10:58,400 --> 00:11:00,000
right? 
Because there are so many. 

195
00:11:00,000 --> 00:11:03,280
Of course we talk about that 
back then again to what I said 

196
00:11:03,280 --> 00:11:04,760
before, we didn't have any 
tools. 

197
00:11:04,880 --> 00:11:08,080
We had no simplification list, 
no readiness check, no custom 

198
00:11:08,080 --> 00:11:12,880
code analyzer, no automated 
provisioning, no sub for me, all

199
00:11:13,000 --> 00:11:15,840
handcrafted also for that 
customer to go live. 

200
00:11:16,080 --> 00:11:19,720
Then later in the same range at 
what slogan also shared before 

201
00:11:20,040 --> 00:11:23,400
we had the customer Delaware, 
who was, if I recall correctly, 

202
00:11:23,400 --> 00:11:28,280
the first customer ever went 
live on S for Hana Cloud public 

203
00:11:28,280 --> 00:11:32,200
edition, which was not less 
adventurous, but it was around 

204
00:11:32,200 --> 00:11:34,720
two years later than Swiss 
property. 

205
00:11:35,200 --> 00:11:39,000
And I can also recall there that
we had many people on duty 

206
00:11:39,000 --> 00:11:42,400
during the go live weekend. 
But finally we also got it 

207
00:11:42,400 --> 00:11:44,840
going. 
Customer went happy life in that

208
00:11:44,840 --> 00:11:47,440
all war setting. 
And honestly, we're all really 

209
00:11:47,520 --> 00:11:50,160
cheerful when we saw the first 
postings in the system. 

210
00:11:50,800 --> 00:11:54,200
And I sense a bit of nostalgy in
your voice, but at almost can I?

211
00:11:54,800 --> 00:11:56,240
It is. 
Yeah, it is. 

212
00:11:56,960 --> 00:11:59,520
It's a long time ago, yeah. 
Yeah, it is. 

213
00:11:59,520 --> 00:12:02,760
It is anything from that time 
you want to share Florian or a 

214
00:12:02,760 --> 00:12:06,760
bit younger depending. 
Yeah, I'm not quite sure. 

215
00:12:06,880 --> 00:12:10,240
A bit younger, but of course I 
still remember our first project

216
00:12:10,240 --> 00:12:13,320
because this was actually the 
starting point of our public 

217
00:12:13,320 --> 00:12:16,280
loud adventure. 
We were keen to jump on that 

218
00:12:16,280 --> 00:12:18,840
project. 
As I mentioned just before, it 

219
00:12:18,840 --> 00:12:24,360
was two months after the boot 
camp and it was necessary to set

220
00:12:24,360 --> 00:12:29,000
it up within only four months at
our custom because it was a calf

221
00:12:29,000 --> 00:12:32,240
out. 
And so we had that restricted 

222
00:12:32,240 --> 00:12:35,360
timeline. 
And of course it was a lot of 

223
00:12:35,360 --> 00:12:38,600
handcrafted. 
So there was no cloud aisle and 

224
00:12:38,600 --> 00:12:41,120
maybe even sub activate was not 
that common. 

225
00:12:41,600 --> 00:12:45,240
We didn't have a lot of 
features, for example, tool or 

226
00:12:45,240 --> 00:12:47,800
AI. 
It was very, very far in the 

227
00:12:47,800 --> 00:12:50,280
future. 
And most important, there were 

228
00:12:50,280 --> 00:12:54,120
no references and no customs you
can talk to or no partners you 

229
00:12:54,120 --> 00:12:56,800
can talk to. 
So you relied on yourself, but 

230
00:12:56,800 --> 00:13:00,640
also of course on SAP. 
And that was, I still remember, 

231
00:13:00,640 --> 00:13:04,120
because we had a really good 
preferred success manager from 

232
00:13:04,120 --> 00:13:08,000
the SAP team and they gave us a 
lot of guidance. 

233
00:13:08,000 --> 00:13:12,040
They helped us to overcome the 
obstacles and at the end it was 

234
00:13:12,040 --> 00:13:15,600
a successful implementation. 
Yeah, it was the start of a big 

235
00:13:15,600 --> 00:13:18,520
adventure at our company. 
Thank you. 

236
00:13:18,520 --> 00:13:19,960
Thank you for sharing. 
Thanks both of you. 

237
00:13:20,520 --> 00:13:25,160
Florian, I think it's on you to 
select the next topic and I just

238
00:13:25,160 --> 00:13:28,680
recap what's still open. 
We have the number 2 partner, 

239
00:13:28,680 --> 00:13:34,520
evolution #3 innovative leader, 
stable and #5 the Crystal Ball. 

240
00:13:34,680 --> 00:13:35,840
Which one would you like to 
pick? 

241
00:13:37,720 --> 00:13:40,760
I would say partner evolution 
maybe, I'm not quite sure what's

242
00:13:40,760 --> 00:13:44,920
behind, but yeah, we will see. 
Here comes the surprise 

243
00:13:44,920 --> 00:13:48,320
questions. 
If SAP partners were a superhero

244
00:13:48,320 --> 00:13:52,200
team, what new powers or 
improvement have they gained in 

245
00:13:52,200 --> 00:13:56,200
the recent years that helped 
save the day during Cloud 

246
00:13:56,200 --> 00:13:59,080
European implementations? 
My superpower. 

247
00:13:59,880 --> 00:14:05,040
There are a lot of superpowers 
we need, but I think we Germans,

248
00:14:05,160 --> 00:14:11,720
we tend to perfectionism and in 
public cloud it might be helpful

249
00:14:11,800 --> 00:14:16,680
to be a little bit less German. 
Maybe this could be a superpower

250
00:14:16,720 --> 00:14:19,200
which is helpful within public 
cloud projects. 

251
00:14:19,400 --> 00:14:23,840
Because we all know the major 
challenge, but also the major 

252
00:14:23,960 --> 00:14:28,760
benefit in public cloud project 
is to try to stick as good as 

253
00:14:28,760 --> 00:14:33,520
possible to the SAP standard. 
And this needs sometimes some 

254
00:14:33,520 --> 00:14:38,720
workarounds, flexibility and 
maybe also to be a little bit 

255
00:14:38,720 --> 00:14:40,800
less German. 
That could be a superpower, but 

256
00:14:40,800 --> 00:14:43,880
not only for the partners, but 
maybe also very important for 

257
00:14:43,880 --> 00:14:47,000
the customers. 
Because as we said earlier, it's

258
00:14:47,000 --> 00:14:50,280
only successful if we cross the 
finish line together, together 

259
00:14:50,280 --> 00:14:53,560
with SAP, the partner and of 
course, the customer. 

260
00:14:53,560 --> 00:14:56,600
Yeah. 
And I can definitely see all our

261
00:14:56,600 --> 00:14:59,920
international colleagues here at
SAP laughing when they would 

262
00:14:59,920 --> 00:15:02,920
hear thought that because they 
would love us to be less German.

263
00:15:04,720 --> 00:15:07,440
Yeah. 
But Bert, you at SAP, you should

264
00:15:07,440 --> 00:15:09,960
be German, because we need good 
quality. 

265
00:15:09,960 --> 00:15:15,240
Yeah, I say maybe when 
implementation project starts 

266
00:15:15,320 --> 00:15:17,440
something that's helpful, maybe 
to be less Germany. 

267
00:15:18,320 --> 00:15:20,280
But that's definitely an amazing
story. 

268
00:15:20,560 --> 00:15:23,240
Good. 
So Beth, you bring quality as 

269
00:15:23,240 --> 00:15:27,560
expected, but beside that, what 
would you like to mention in 

270
00:15:27,560 --> 00:15:32,120
terms of superhero powers? 
I honestly just thought of 

271
00:15:32,120 --> 00:15:35,800
bringing the exact opposite 
because I have a slightly unfair

272
00:15:35,800 --> 00:15:39,800
advantage because we did a very 
similar exercise recently in one

273
00:15:39,800 --> 00:15:43,840
of our customer success days 
when we asked the customers to 

274
00:15:43,840 --> 00:15:47,760
introduce themselves and what 
superpower they would love to 

275
00:15:47,760 --> 00:15:49,480
have as part of their 
introduction. 

276
00:15:50,040 --> 00:15:53,200
And guess what? 
Many wanted to be elongated men 

277
00:15:53,200 --> 00:15:55,480
from the DC Universe. 
I think some people might also 

278
00:15:55,480 --> 00:15:59,560
know him as like plastic men. 
So elongated men can stretch his

279
00:15:59,560 --> 00:16:03,080
limbs and body to this 
superhuman length and size. 

280
00:16:03,640 --> 00:16:07,800
And I believe the stretching 
powers grant him kind of 

281
00:16:07,800 --> 00:16:11,160
agility, flexibility and 
unlimited coordination. 

282
00:16:11,440 --> 00:16:13,960
I assume that these are exactly 
the capabilities people would 

283
00:16:13,960 --> 00:16:15,520
love to have in their business 
life. 

284
00:16:15,680 --> 00:16:19,560
So in my experience also looking
back at the projects and what's 

285
00:16:19,720 --> 00:16:22,920
cooking in the industry, 
transformation has been really 

286
00:16:22,920 --> 00:16:26,920
the term of the last decade, 
digital transformation, business

287
00:16:26,920 --> 00:16:29,440
transformation. 
I would even argue everything is

288
00:16:29,440 --> 00:16:33,680
transformed, which requires 
exactly that Elongated Man's 

289
00:16:33,680 --> 00:16:35,960
stretching power. 
So you need to be agile, 

290
00:16:35,960 --> 00:16:38,960
flexible and you need to have 
unlimited coordination 

291
00:16:38,960 --> 00:16:43,360
capabilities and as partners are
really front and centre of our 

292
00:16:43,360 --> 00:16:46,200
SAP success. 
Therefore, I would now love to 

293
00:16:46,200 --> 00:16:50,840
wave my Harry Potter wand and 
Grant, Florian and the team all 

294
00:16:50,840 --> 00:16:52,960
the superpower from elongated 
men. 

295
00:16:53,600 --> 00:16:56,960
And by the way, when we did that
exercise and I also had to 

296
00:16:56,960 --> 00:17:01,200
introduce myself, I've chosen 
Doctor Strange from the Marvel 

297
00:17:01,200 --> 00:17:05,920
Universe because his superpower 
to manipulate the time really 

298
00:17:05,920 --> 00:17:08,160
would lift it to a complete new 
level. 

299
00:17:08,280 --> 00:17:11,599
Because then you can always go 
back in time and correct things 

300
00:17:11,599 --> 00:17:13,480
which you might have done 
differently with all the 

301
00:17:13,480 --> 00:17:16,680
knowledge, but you have like a 
year or six months or sometimes 

302
00:17:16,680 --> 00:17:19,280
five years later. 
It's like a few customers, you 

303
00:17:19,280 --> 00:17:21,119
know to create a CIP request for
that. 

304
00:17:21,119 --> 00:17:22,800
Maybe we make it happen at a few
points. 

305
00:17:25,520 --> 00:17:27,440
OK, not bad. 
It's on you to pick the next 

306
00:17:27,440 --> 00:17:32,400
category and we have only two 
left #3 was Innovative Leaders 

307
00:17:32,400 --> 00:17:36,680
table or #5 the Crystal ball? 
Let's go for the innovation. 

308
00:17:37,360 --> 00:17:40,880
OK, here you go. 
If SAP and its partners were 

309
00:17:40,880 --> 00:17:44,600
sitting at a round table, which 
strategy would you propose that 

310
00:17:44,600 --> 00:17:47,200
could reshape the environment of
ACP? 

311
00:17:47,200 --> 00:17:49,000
As for Anna Cloud 
implementations. 

312
00:17:49,640 --> 00:17:54,040
Oh wow, I think maybe 
summarising the last 10 years. 

313
00:17:54,040 --> 00:17:58,280
I mean, we're now in 2024 and as
far as cloud implementation 

314
00:17:58,280 --> 00:18:03,960
projects are still often IT 
projects, it still considers 

315
00:18:03,960 --> 00:18:07,320
rather lift and shift of 
infrastructure and leveraging 

316
00:18:07,320 --> 00:18:10,480
the full capabilities of the 
technology foundation which we 

317
00:18:10,480 --> 00:18:15,560
ship with public cloud advanced 
technology or AI capabilities 

318
00:18:15,560 --> 00:18:18,600
recently. 
So if I look back particularly 

319
00:18:18,600 --> 00:18:24,080
to this innovation tables in my 
life, I had to relearn ERP at 

320
00:18:24,080 --> 00:18:28,640
least twice from scratch. 
First when we start introducing 

321
00:18:28,640 --> 00:18:33,160
S4 and changed almost all moving
parts of an ERP solution. 

322
00:18:33,680 --> 00:18:37,800
And now as we speak with AI. 
And in my eyes, it is simply a 

323
00:18:37,800 --> 00:18:41,600
misunderstanding to think you're
safe when you know how ERP 

324
00:18:41,720 --> 00:18:45,040
worked in the past. 
There's so much new stuff every 

325
00:18:45,040 --> 00:18:48,200
day and larger inflection 
points, which have really the 

326
00:18:48,200 --> 00:18:51,680
power to turn processes 
completely upside down. 

327
00:18:52,040 --> 00:18:54,440
And by the way, hopefully also 
to the better. 

328
00:18:55,000 --> 00:18:58,640
So net, net, I'd still love to 
see more business leaders 

329
00:18:58,640 --> 00:19:02,360
engaging and sponsoring also the
project as Business Innovation 

330
00:19:02,360 --> 00:19:05,320
projects rather than IT 
renovation projects. 

331
00:19:06,120 --> 00:19:08,720
And we talk a lot about cloud 
mindset. 

332
00:19:08,720 --> 00:19:12,080
Look into the sub activate 
starting point, what we talk a 

333
00:19:12,080 --> 00:19:15,920
lot about cloud mindset. 
And this continues to really be 

334
00:19:15,920 --> 00:19:18,120
the Evergreen in any project 
kick off. 

335
00:19:18,840 --> 00:19:20,600
Floi and I want to add your 
point of view here. 

336
00:19:20,600 --> 00:19:23,200
We're interested. 
I was jumping on the point, 

337
00:19:23,200 --> 00:19:25,560
maybe Bert mentioned the cloud 
mindset. 

338
00:19:25,680 --> 00:19:29,600
This is very, very important for
us to pick the right projects 

339
00:19:29,600 --> 00:19:34,120
and to pick the right customers.
Sometimes we say maybe tough 

340
00:19:34,120 --> 00:19:38,080
words to our prospects that we 
don't think that you're ready to

341
00:19:38,080 --> 00:19:42,680
jump on a public cloud project. 
I'm happy to be at the round 

342
00:19:42,680 --> 00:19:45,080
tables. 
SAP offers doesn't matter 

343
00:19:45,080 --> 00:19:48,480
together with you Bird or Young 
Gilg or also on a management 

344
00:19:48,480 --> 00:19:50,760
level in the partner Advisory 
Board. 

345
00:19:50,880 --> 00:19:56,920
I think it's important that we 
all stay together and that we 

346
00:19:56,920 --> 00:20:00,080
exchange. 
So there will be a lot of 

347
00:20:00,080 --> 00:20:03,920
potential in the future for the 
public cloud and there's always 

348
00:20:03,920 --> 00:20:07,160
room for improvement. 
But especially with the new 

349
00:20:07,160 --> 00:20:13,480
technology likes AI is a game 
changer and we are all maybe not

350
00:20:13,480 --> 00:20:15,360
knowing what will come in the 
future. 

351
00:20:15,800 --> 00:20:20,320
ERP with AI together. 
I don't know what will be there 

352
00:20:20,320 --> 00:20:23,520
in the future in five years, so 
I'm happy to be part of that 

353
00:20:23,640 --> 00:20:26,240
time. 
So it seems, Yannick, you have 

354
00:20:26,240 --> 00:20:29,240
to invite us definitely also for
your 10th year anniversary 

355
00:20:29,240 --> 00:20:31,840
again. 
Lenders are marked already. 

356
00:20:31,840 --> 00:20:34,040
You're more than welcome. 
See you in five years. 

357
00:20:34,280 --> 00:20:37,600
But before we continue in five 
years, we have a last question. 

358
00:20:37,600 --> 00:20:41,640
And unfortunately, Florian, you 
cannot choose because this only 

359
00:20:41,640 --> 00:20:46,640
#5 left, which is the crystal 
ball, but this perfectly fits in

360
00:20:47,000 --> 00:20:49,880
the flow. 
So Florian, what, what is your 

361
00:20:49,880 --> 00:20:51,680
personal outlook for the next 
year? 

362
00:20:52,560 --> 00:20:57,400
I will start maybe looking five 
years back and when I said to 

363
00:20:57,400 --> 00:21:02,080
some of my colleague that in 
future we will only do cloud 

364
00:21:02,080 --> 00:21:04,640
projects, they, some of them 
were laughing. 

365
00:21:05,280 --> 00:21:10,520
Meanwhile, last year, we had at 
least 50% of our projects within

366
00:21:10,520 --> 00:21:14,040
public cloud. 
And I would say looking at the 

367
00:21:14,040 --> 00:21:19,480
crystal ball five years, there's
a lot of time in ITI would say 

368
00:21:19,600 --> 00:21:23,080
we were not doing any private 
cloud project anymore in five 

369
00:21:23,080 --> 00:21:26,200
years. 
That's maybe my hope, but also I

370
00:21:26,200 --> 00:21:29,400
believe in that, yes, at least 
for net new names. 

371
00:21:30,360 --> 00:21:32,800
Good. 
Thank you for sharing that your 

372
00:21:32,800 --> 00:21:35,600
personal outlook for the next 
year of years, plural. 

373
00:21:36,080 --> 00:21:38,880
I like what France said. 
So definitely you have my buy in

374
00:21:40,200 --> 00:21:43,680
to see more in our net new names
was purely going into public 

375
00:21:43,680 --> 00:21:47,040
cloud. 
But I think my personal outlook 

376
00:21:47,040 --> 00:21:50,960
for the next year, I think it 
will be AAI all over the place. 

377
00:21:50,960 --> 00:21:52,640
We've seen so much change 
already. 

378
00:21:52,640 --> 00:21:58,360
We see how my team is changing. 
We also adopt AI for scale and I

379
00:21:58,360 --> 00:22:01,520
think it will be AI to support 
leveraging the product for end 

380
00:22:01,520 --> 00:22:04,600
users, supporting the end user 
directly navigational 

381
00:22:04,600 --> 00:22:07,800
transactional support, which you
currently see already knocking 

382
00:22:07,800 --> 00:22:11,240
at the door with G will going 
into the market public GA 

383
00:22:11,240 --> 00:22:14,200
anytime soon, but also 
automating the onboarding 

384
00:22:14,200 --> 00:22:17,360
procedures, data migration. 
I mean we currently have a very 

385
00:22:17,360 --> 00:22:20,960
cool AI case for smart data 
matching to make sure that you 

386
00:22:20,960 --> 00:22:25,560
have much easier ETA processes 
for expect transport and load 

387
00:22:25,560 --> 00:22:28,880
processes into the system. 
So I think this is one of these 

388
00:22:28,880 --> 00:22:33,240
inflection points which really 
has the power and capability to 

389
00:22:33,240 --> 00:22:37,400
make a huge impact on the way 
how we run public cloud or in 

390
00:22:37,400 --> 00:22:39,480
general As for projects in the 
future. 

391
00:22:40,640 --> 00:22:44,720
Great closing thoughts. 
Thank you both for joining this 

392
00:22:44,720 --> 00:22:46,600
episode. 
Thanks a lot, Florian, for 

393
00:22:46,600 --> 00:22:49,160
joining us. 
Thanks to Hubert again for 

394
00:22:49,160 --> 00:22:52,000
playing the game with us. 
It was good fun, at least for 

395
00:22:52,000 --> 00:22:53,440
me. 
I hope for you as well. 

396
00:22:53,560 --> 00:22:55,480
And it was very insightful as 
well. 

397
00:22:55,560 --> 00:22:58,480
So All in all, a great way to 
mark our fifth anniversary. 

398
00:22:59,520 --> 00:23:02,760
If you like this episode and 
have ideas about the next 

399
00:23:02,760 --> 00:23:06,160
relevant topics for this 
podcast, just send us an e-mail 

400
00:23:06,440 --> 00:23:13,440
insides4@acp.com TuneIn next 
time and be inside ACPS 4 Anna 

401
00:23:13,440 --> 00:23:15,640
Cloud. 
Bye everyone again. 

402
00:23:15,640 --> 00:23:17,760
Bye and thank you, Florian. 
Bye and thank you, Bear. 

403
00:23:18,600 --> 00:23:20,840
Thanks for having me. 
It was a pleasure. 

404
00:23:20,840 --> 00:23:21,560
Thank you very much.
