1
00:00:09,120 --> 00:00:12,960
I'm Annika Schmidt, and this is 
inside SAP Cloud ERP, your 

2
00:00:12,960 --> 00:00:15,720
podcast. 
And we are today again live from

3
00:00:15,720 --> 00:00:19,040
the Teched show floor. 
And I'm today with Vladimir 

4
00:00:19,040 --> 00:00:23,920
Shakov, the Strategic Alliance 
Director, ACPN 8 N Thanks a lot,

5
00:00:23,920 --> 00:00:26,160
Vladimir, for your time. 
Thanks for joining us on the 

6
00:00:26,160 --> 00:00:28,560
show. 
Thank you for having me, Yanik. 

7
00:00:28,600 --> 00:00:31,240
It's a pleasure to be here today
together with you. 

8
00:00:31,560 --> 00:00:37,040
Great Vladimir Teke started in 
Orlando in 1996 with only 700 

9
00:00:37,040 --> 00:00:39,680
developers. 
Cloud was not a topic at that 

10
00:00:39,680 --> 00:00:42,920
time in the ERP words. 
Now, 30 years later, the two of 

11
00:00:42,920 --> 00:00:46,520
us are standing in tech talk 
about AI agents orchestrating 

12
00:00:46,520 --> 00:00:49,320
enterprise workflows. 
When you look at the Arc, you 

13
00:00:49,320 --> 00:00:53,240
know from the beginning and 
today, where does the SAP and N 

14
00:00:53,240 --> 00:00:57,600
18 partnership fit into this 
moment and why did that happen 

15
00:00:57,600 --> 00:01:00,760
now? 
So we all hear a lot of 

16
00:01:00,760 --> 00:01:04,200
information about AI and how AI 
is changing the world. 

17
00:01:04,680 --> 00:01:08,240
And of course, also software 
companies need to adapt to the 

18
00:01:08,240 --> 00:01:12,040
new way of working. 
Everybody is using LLMS on a 

19
00:01:12,040 --> 00:01:15,240
daily basis. 
They're used to we post the 

20
00:01:15,240 --> 00:01:18,880
question, we get an answer. 
However, in the enterprise 

21
00:01:18,880 --> 00:01:22,200
world, it is a bit different. 
We also want the same 

22
00:01:22,200 --> 00:01:26,440
experience, however, we need the
same, we need a very different 

23
00:01:26,440 --> 00:01:29,760
level of security. 
So we need to be within the 

24
00:01:29,760 --> 00:01:34,600
guard rails that we set and 
every data that actually resides

25
00:01:34,840 --> 00:01:37,600
in the corporate system is worth
gold. 

26
00:01:37,600 --> 00:01:41,560
So we need to make sure that we 
secure this data and this is 

27
00:01:41,560 --> 00:01:46,520
probably what is triggering the 
new trend of EI emerging with 

28
00:01:46,520 --> 00:01:50,800
large enterprise companies. 
However, in a secure environment

29
00:01:50,800 --> 00:01:54,560
with the guard rails and with 
all the security level that a 

30
00:01:54,560 --> 00:02:00,240
company expects and any 10 as 
part of Dual Studio is the new 

31
00:02:00,240 --> 00:02:06,280
generation of those EI products.
Dual acts as an interface to all

32
00:02:06,280 --> 00:02:10,440
of your business data, all your 
business processes, while NA 10 

33
00:02:10,520 --> 00:02:13,880
acts as an EI orchestration 
platform, which actually 

34
00:02:13,880 --> 00:02:17,960
connects people, data and 
processes in a similar fashion, 

35
00:02:18,200 --> 00:02:22,480
making sure that all your 
systems talk to each other and 

36
00:02:22,480 --> 00:02:26,200
your request is not only an 
answer that gets answered, but 

37
00:02:26,200 --> 00:02:30,240
also protest that gets executed 
across the entire landscape. 

38
00:02:30,400 --> 00:02:32,280
OK. 
Vladimir, let's say I'm a 

39
00:02:32,360 --> 00:02:36,040
finance director running SAPS 
for HANA Cloud. 

40
00:02:36,520 --> 00:02:41,840
What problem would NA10 run for 
me for the finance LOB? 

41
00:02:42,240 --> 00:02:45,400
But nothing else in the SAP 
stack was solving before that 

42
00:02:45,400 --> 00:02:48,640
way. 
So SAP has historically a lot of

43
00:02:48,640 --> 00:02:51,400
solutions. 
The problem was a lot of those 

44
00:02:51,400 --> 00:02:53,680
solutions are working in 
isolation. 

45
00:02:54,040 --> 00:02:58,520
You have AI agents which are 
stand alone, you have BPA, you 

46
00:02:58,520 --> 00:03:02,280
have other applications that 
don't talk to each other with 

47
00:03:02,280 --> 00:03:05,280
dual studio and any 10 being 
part of it. 

48
00:03:05,400 --> 00:03:07,920
Actually everything happens in a
seamless way. 

49
00:03:08,240 --> 00:03:12,240
For example, in finance you want
to see how your company is 

50
00:03:12,240 --> 00:03:16,160
dealing in general, but also you
can possibly want to delve deep 

51
00:03:16,240 --> 00:03:19,280
into how is my single unit 
doing. 

52
00:03:19,600 --> 00:03:23,400
And previously you had to pull a
lot of reports from different 

53
00:03:23,400 --> 00:03:28,720
systems, then patch them all 
together and then had to make 

54
00:03:28,720 --> 00:03:31,480
analysis on your own. 
Now you can do it with a single 

55
00:03:31,480 --> 00:03:34,080
prompt. 
I can say we want to dive deep 

56
00:03:34,080 --> 00:03:37,840
on this business unit and I want
to understand what happened in 

57
00:03:37,840 --> 00:03:41,080
quarter four, what were the 
results and what are the 

58
00:03:41,080 --> 00:03:45,800
consequences I should actually 
look into and what I can do 

59
00:03:45,800 --> 00:03:48,240
better. 
And with Dual Studio, you can do

60
00:03:48,240 --> 00:03:52,080
it with a single prompt. 
You can explain what you want, 

61
00:03:52,080 --> 00:03:57,160
what your intent is and then you
get ready to execute data set 

62
00:03:57,160 --> 00:04:01,000
with reports, everything at a 
hand side, without any coding, 

63
00:04:01,000 --> 00:04:05,640
programming and tailored to your
concrete response the way you 

64
00:04:05,640 --> 00:04:07,320
actually like to get the 
information. 

65
00:04:07,840 --> 00:04:10,960
Let's talk about exactly that, 
the partnership and dual studio 

66
00:04:10,960 --> 00:04:12,760
that you touch already once or 
twice. 

67
00:04:13,080 --> 00:04:15,920
Overall, SAP made the bid 
investments in N8. 

68
00:04:15,920 --> 00:04:17,920
MI think it's based in Berlin, 
isn't it? 

69
00:04:18,320 --> 00:04:21,000
Yes. 
Any Tan is a Berlin company 

70
00:04:21,000 --> 00:04:24,720
which is actually not that young
as many do perceive. 

71
00:04:24,720 --> 00:04:28,760
So we're already nine years on 
the market and we started with 

72
00:04:28,760 --> 00:04:32,240
the community version and we 
actually developed our product 

73
00:04:32,240 --> 00:04:35,520
with the community. 
That's why it is so popular 

74
00:04:35,560 --> 00:04:39,320
within the developer community, 
because we took the responses 

75
00:04:39,320 --> 00:04:43,520
and the feedback seriously and 
we incorporated it into our 

76
00:04:43,520 --> 00:04:46,520
systems. 
And from this community version,

77
00:04:46,520 --> 00:04:50,720
we have grown into very mature 
enterprise product which is 

78
00:04:50,720 --> 00:04:53,360
still loved by the community 
somehow. 

79
00:04:53,360 --> 00:04:55,680
Like, you know, one product with
two souls. 

80
00:04:55,680 --> 00:05:00,280
And this is very important. 
And the partnership with SAP was

81
00:05:00,280 --> 00:05:02,600
a strategic decision for both 
companies. 

82
00:05:03,000 --> 00:05:06,600
Of course, we understand that 
enterprise work flows. 

83
00:05:07,120 --> 00:05:11,760
Enterprise AI orchestration has 
to act in systems where the data

84
00:05:11,760 --> 00:05:14,880
resides. 
SAP is one of the biggest 

85
00:05:14,880 --> 00:05:18,160
business applications in the 
world where all the critical 

86
00:05:18,160 --> 00:05:22,400
data resides, and in order for 
our systems to work efficiently,

87
00:05:22,400 --> 00:05:25,520
we have to be part of it. 
Same for SAP. 

88
00:05:26,040 --> 00:05:29,960
They decided not to invent the 
will and to invent the business 

89
00:05:29,960 --> 00:05:33,200
process engine or AI 
orchestration platform from 

90
00:05:33,200 --> 00:05:36,200
scratch. 
They decided to take well 

91
00:05:36,200 --> 00:05:39,800
tested, well received product in
the market, best of breed if you

92
00:05:39,800 --> 00:05:44,240
like, and integrate it 
seamlessly into the dual studio 

93
00:05:44,240 --> 00:05:45,720
experience. 
OK. 

94
00:05:46,120 --> 00:05:48,840
How can we visualize that, You 
know, from an environment 

95
00:05:48,840 --> 00:05:52,080
perspective, you know, we know 
that Entertain is embedded 

96
00:05:52,080 --> 00:05:56,200
directly inside dual Studio on 
BTP, but do I have separate 

97
00:05:56,200 --> 00:05:58,640
Entertain contract? 
This is the separate technical 

98
00:05:58,640 --> 00:06:01,560
environment. 
What's the experience like when 

99
00:06:01,560 --> 00:06:04,160
you open the canvas? 
That's a very good question. 

100
00:06:04,160 --> 00:06:07,960
And that's actually why we 
decided to go for the OEM route 

101
00:06:07,960 --> 00:06:10,680
because it's one single point of
contact. 

102
00:06:10,680 --> 00:06:14,200
So you don't have to sign any 
additional contracts, you don't 

103
00:06:14,200 --> 00:06:17,920
have to sign any additional 
agreements, Ndas, anything. 

104
00:06:18,360 --> 00:06:22,160
Everything goes through SAP, 
support is being provided 

105
00:06:22,160 --> 00:06:26,720
through SAP and everything can 
be activated using the business 

106
00:06:26,720 --> 00:06:31,000
AI credits, which can be also 
used for Dual Studio, where NA 

107
00:06:31,000 --> 00:06:34,240
10 is part of Dual Studio. 
And actually, even though you 

108
00:06:34,240 --> 00:06:38,400
see the NA 10 brand inside Dual 
Studio, which is also very 

109
00:06:38,400 --> 00:06:42,640
unique situation for SAP, I know
you don't do that very often 

110
00:06:42,640 --> 00:06:46,520
with other companies. 
Still, it's a native interface 

111
00:06:46,520 --> 00:06:48,400
with Dual Studio. 
You don't have to open a 

112
00:06:48,400 --> 00:06:51,760
separate application and even 
more important, you don't need 

113
00:06:51,760 --> 00:06:54,960
to enter your login data second 
time. 

114
00:06:54,960 --> 00:06:58,680
So everything, all the security 
rules, all the authorization 

115
00:06:58,680 --> 00:07:02,280
rules, everything. 
What you're used to in working 

116
00:07:02,280 --> 00:07:05,120
with SAP is being inherited 
from. 

117
00:07:05,200 --> 00:07:08,440
Like the fact that it's simple, 
that is good and simply 

118
00:07:08,440 --> 00:07:12,080
accessible via dual studio. 
Let's have a look Vladimir now 

119
00:07:12,080 --> 00:07:16,720
at concrete use cases because we
know that the ACP landscape are 

120
00:07:16,720 --> 00:07:21,640
can be a suite of line of 
business solution with SAP Cloud

121
00:07:21,640 --> 00:07:25,000
Europe, ACP, Arebar, ACP Sales 
Cloud. 

122
00:07:25,320 --> 00:07:29,000
And let's say I'm a customer and
I want to run my first NNN 

123
00:07:29,080 --> 00:07:31,440
workflow. 
What's the starting point? 

124
00:07:32,160 --> 00:07:35,080
So it's a good question. 
What's the starting point? 

125
00:07:35,080 --> 00:07:40,720
I think we have to look at what 
is the protest which causes the 

126
00:07:40,720 --> 00:07:45,120
most pain, most manual protest 
where you have to go through 

127
00:07:45,120 --> 00:07:48,880
different systems to gather 
data, to put data together, to 

128
00:07:48,920 --> 00:07:51,600
maybe provide approvals. 
A lot of different people are 

129
00:07:51,600 --> 00:07:54,160
involved, but the process is 
repeatable. 

130
00:07:54,240 --> 00:07:58,400
I think that's the first process
we should look at and try to 

131
00:07:58,400 --> 00:08:01,360
automate. 
Of course, as with any AI story,

132
00:08:01,520 --> 00:08:05,840
I think the rule of thumb is if 
a human can get it, then it's 

133
00:08:05,840 --> 00:08:08,840
also possible to use AI to solve
the solution. 

134
00:08:09,160 --> 00:08:13,960
A concrete example I can use 
Invoice gets blocked for payment

135
00:08:13,960 --> 00:08:18,400
and As for HANA Cloud and 
usually it's a manual process so

136
00:08:18,600 --> 00:08:22,680
some accounts payable specialist
has to go and look at those 

137
00:08:22,680 --> 00:08:26,560
invoice and resolve exceptions 
manually and it's a very time 

138
00:08:26,560 --> 00:08:29,120
consuming process. 
Here we can actually 

139
00:08:29,120 --> 00:08:31,640
administrate the workflow to do 
the job. 

140
00:08:32,200 --> 00:08:36,200
For example, the agent pulls 
invoices, PO goods, receipts and

141
00:08:36,200 --> 00:08:41,120
contract data through APIs. 
Then it compares them with the 

142
00:08:41,120 --> 00:08:45,480
rules and in plain language 
summarizes the discrepancies. 

143
00:08:45,480 --> 00:08:48,560
So what's not working within 
tolerance? 

144
00:08:48,680 --> 00:08:52,000
It resolves some of those 
unresolved invoices 

145
00:08:52,040 --> 00:08:55,040
automatically, others just a 
fraction. 

146
00:08:55,040 --> 00:08:58,400
So like small percentage of it 
which fall outside of the 

147
00:08:58,400 --> 00:09:02,160
tolerance will get a human in 
the loop involved and will be 

148
00:09:02,160 --> 00:09:07,280
forwarded to the task center or 
to the responsible AP clerk who 

149
00:09:07,280 --> 00:09:09,200
can actually dive deeper into 
that. 

150
00:09:09,760 --> 00:09:14,360
And this is one small example of
the workflow which can be done 

151
00:09:14,360 --> 00:09:18,720
of course like we talked about 
third party systems before and 

152
00:09:18,800 --> 00:09:24,240
here we can send otifications 
using Teams, Outlook, Slack, any

153
00:09:24,240 --> 00:09:27,800
other third party system, even 
using messaging systems which 

154
00:09:27,800 --> 00:09:30,560
are very common for the end user
devices. 

155
00:09:31,000 --> 00:09:35,800
OK, very good, I like that and I
will remember starts where it's 

156
00:09:35,800 --> 00:09:38,680
how did you did you say that how
where it matters more or rate 

157
00:09:38,680 --> 00:09:41,880
hurts more right. 
This is a good advice indeed for

158
00:09:41,880 --> 00:09:43,120
this question that I'd be 
touched. 

159
00:09:43,120 --> 00:09:45,720
I'd like to have the honest 
answer, please. 

160
00:09:45,720 --> 00:09:49,240
This is a question that every 
architect and project manager in

161
00:09:49,240 --> 00:09:52,640
our audience might ask him or 
herself. 

162
00:09:53,040 --> 00:09:58,400
When should I use an 8 M and 
when should I stick with SAP 

163
00:09:58,400 --> 00:10:01,920
Integration Suite or SAP 
Business Process Automation? 

164
00:10:02,400 --> 00:10:05,960
You know, is it a replacement? 
Is it a complement? 

165
00:10:06,400 --> 00:10:08,840
It depends. 
What is your recommendation 

166
00:10:08,840 --> 00:10:12,160
here? 
So, Yannick, it's a very tricky 

167
00:10:12,160 --> 00:10:15,360
question. 
Actually, what we're trying to 

168
00:10:15,360 --> 00:10:19,360
achieve with SAP and any time 
together, and that's the grand 

169
00:10:19,360 --> 00:10:23,880
vision which we're working on, 
is you don't have as a human 

170
00:10:23,880 --> 00:10:26,960
make the decision. 
You are the expert subject 

171
00:10:26,960 --> 00:10:30,360
matter expert who knows the 
process and who knows what job 

172
00:10:30,360 --> 00:10:34,080
needs to be completed. 
And that's exactly the intention

173
00:10:34,080 --> 00:10:37,840
of Jewel Studio today. 
You have to describe what you 

174
00:10:37,840 --> 00:10:40,960
want to achieve and then what 
are the right tools. 

175
00:10:41,040 --> 00:10:44,000
Actually, Jewel Studio makes the
decision for you. 

176
00:10:44,480 --> 00:10:46,800
Is it the workflow? 
Is it an agent? 

177
00:10:46,840 --> 00:10:50,840
Is it any other tooling which 
are part of Dual Studio? 

178
00:10:51,080 --> 00:10:54,360
Maybe it's a combination of two 
or three or even more 

179
00:10:54,360 --> 00:10:57,920
components. 
So in this chain you don't care 

180
00:10:57,920 --> 00:11:01,000
about the how. 
How is the decision that stays 

181
00:11:01,000 --> 00:11:04,320
with Dual Studio? 
You care about what what needs 

182
00:11:04,320 --> 00:11:08,160
to be solved and the end result.
OK, OK, great. 

183
00:11:08,920 --> 00:11:12,960
Let's have a look at let's say 
more complex landscape with non 

184
00:11:12,960 --> 00:11:18,160
ACP system, Salesforce teams, 
logistic solution, MTE. 

185
00:11:18,160 --> 00:11:22,360
For example, agents don't answer
questions in the single system, 

186
00:11:22,360 --> 00:11:26,400
but my execute multi step 
business processes, right And N8

187
00:11:26,400 --> 00:11:31,160
N is described as the 
orchestration layer for these 

188
00:11:31,200 --> 00:11:33,600
agentic workflows. 
Can you walk us through a 

189
00:11:33,600 --> 00:11:37,840
concrete example of an agent 
that is built in dual studio 

190
00:11:37,840 --> 00:11:44,240
that uses obviously N8 N that 
goes outside the SAP world and 

191
00:11:44,360 --> 00:11:48,360
how is the governance and the 
control maintain them? 

192
00:11:48,800 --> 00:11:53,840
So it's a good question. 
As we all know IT, landscapes at

193
00:11:53,840 --> 00:11:58,840
customers are never simple. 
So we would of course all love a

194
00:11:58,840 --> 00:12:05,000
customer to use purely SAP, but 
is rarely the case and sometimes

195
00:12:05,120 --> 00:12:08,680
there are even several ERP 
systems or several invoice 

196
00:12:08,680 --> 00:12:10,960
processing systems the customer 
is running. 

197
00:12:11,440 --> 00:12:14,480
Let's imagine this situation 
because we're sticking with 

198
00:12:14,480 --> 00:12:16,680
invoices. 
Let's stay with invoices for 

199
00:12:16,680 --> 00:12:19,120
reasons outside of the customer 
control. 

200
00:12:19,120 --> 00:12:22,680
For example, he needs to oblige 
to some specific customer 

201
00:12:22,880 --> 00:12:26,960
country rules for countries with
whom they're working and because

202
00:12:26,960 --> 00:12:29,880
of that they need to run several
invoice processing systems. 

203
00:12:30,320 --> 00:12:36,000
Information that resides in SAP 
stays in SAP under a secure 

204
00:12:36,000 --> 00:12:40,520
guardrail that we have set up. 
However, using any time, we can 

205
00:12:40,520 --> 00:12:44,280
trigger workflows and agents 
sitting outside SAP to pull 

206
00:12:44,280 --> 00:12:49,080
additional contacts into the 
system and in reach the data 

207
00:12:49,080 --> 00:12:53,760
that we have set up for this 
workflow or process or use case 

208
00:12:54,160 --> 00:12:56,760
with data that is outside of the
system. 

209
00:12:56,760 --> 00:13:00,320
And because of that, we get a 
complete picture not only based 

210
00:13:00,320 --> 00:13:03,880
on the information we have in 
the core system in the SAP, but 

211
00:13:03,880 --> 00:13:07,360
also enriched with the data 
which comes from the third party

212
00:13:07,360 --> 00:13:09,960
systems. 
And that's basically how it can 

213
00:13:09,960 --> 00:13:12,120
work. 
And that's the magic that Any 

214
00:13:12,120 --> 00:13:15,000
time can bring into the protest.
Great, great. 

215
00:13:15,000 --> 00:13:18,080
Thanks for sharing that. 
As a closing question, Vladimir,

216
00:13:18,080 --> 00:13:23,200
so today ticket is 30 years old 
when we sit together a ticket in

217
00:13:23,200 --> 00:13:27,920
2036, potentially with agents 
running entire business function

218
00:13:27,920 --> 00:13:31,160
autonomously because that is the
strategy that is turning already

219
00:13:31,160 --> 00:13:35,480
today into execution at many, 
many customers being there. 

220
00:13:35,480 --> 00:13:40,760
What role do you see in it in 
playing in the SAP ecosystem and

221
00:13:40,760 --> 00:13:44,920
what should cloud ERP customers 
investing in today so they're 

222
00:13:44,920 --> 00:13:49,320
ready for that future and that 
discussion in 2036, so. 

223
00:13:49,360 --> 00:13:53,240
Yannick, I would probably turn 
the question a bit around, say 

224
00:13:53,240 --> 00:13:59,800
that when we are there at Tech 
AD 2036 or even 63 or even 

225
00:13:59,800 --> 00:14:05,040
beyond that think the key thing 
that stays are the humans, those

226
00:14:05,040 --> 00:14:09,160
interactions face to face, those
interviews, those customer 

227
00:14:09,160 --> 00:14:12,960
partner discussions, they're 
invaluable and I don't believe 

228
00:14:12,960 --> 00:14:18,400
that EI can replace them. 
What actually EI is going to be 

229
00:14:18,400 --> 00:14:22,880
doing while we're having those 
conversations, it's going to be 

230
00:14:23,280 --> 00:14:27,280
checking all the contacts that I
made in the conference and 

231
00:14:27,280 --> 00:14:31,200
reaching it with contacts, 
sending emails, answering 

232
00:14:31,200 --> 00:14:35,040
emails, maybe even making phone 
calls for me and making sure 

233
00:14:35,040 --> 00:14:39,000
that the next agenda day is full
with meaningful meetings. 

234
00:14:39,560 --> 00:14:42,760
That's how I see the 
collaboration between AI and 

235
00:14:42,760 --> 00:14:46,200
humans in the future for the 
tech ads to come. 

236
00:14:46,920 --> 00:14:51,720
And regards to your question, 
what do companies need to invest

237
00:14:51,720 --> 00:14:53,400
in? 
A lot of companies that are 

238
00:14:53,400 --> 00:14:57,400
undergoing the UI transformation
process, first of all need to 

239
00:14:57,400 --> 00:15:00,640
look inside the companies and 
inside the protesters. 

240
00:15:00,640 --> 00:15:05,640
They have a lot of protesters 
they try to pull AI on to are 

241
00:15:05,680 --> 00:15:10,280
outdated and need to be 
rethinked in terms of how do I 

242
00:15:10,280 --> 00:15:13,600
move to the future, How do I 
make them more efficient, 

243
00:15:13,600 --> 00:15:16,600
However, how do I make them also
AI ready? 

244
00:15:16,600 --> 00:15:20,600
And that's probably the first 
step the company needs to take 

245
00:15:20,680 --> 00:15:24,920
even before envisioning working 
with two or any time because 

246
00:15:25,120 --> 00:15:27,960
those are perfect best in class 
tools. 

247
00:15:27,960 --> 00:15:31,960
But they only work if you also 
have protesters ready for them. 

248
00:15:31,960 --> 00:15:32,800
Yeah. 
True true. 

249
00:15:33,040 --> 00:15:36,360
Thanks a lot for those nice and 
wise closing words. 

250
00:15:36,440 --> 00:15:40,720
My take away is if I call you in
10 years for a podcast you will 

251
00:15:40,720 --> 00:15:43,560
come in person. 
You will not send any and it 

252
00:15:43,560 --> 00:15:47,560
will be a pleasure to meet again
and see all that would have 

253
00:15:47,560 --> 00:15:50,760
happened in a decade. 
Vladimir, big thanks for joining

254
00:15:50,760 --> 00:15:53,120
us on the Inside ACP Cloud 
Europe. 

255
00:15:53,160 --> 00:15:54,760
It's been a pleasure to host 
you. 

256
00:15:55,080 --> 00:15:58,640
I wish you an enjoyable rest of 
the ticket and to our audience, 

257
00:15:58,640 --> 00:16:01,160
stay tuned. 
This interesting episode with 

258
00:16:01,160 --> 00:16:04,760
Vladimir from NN is part of the 
broader Ticket series. 

259
00:16:04,760 --> 00:16:09,040
So stay tuned in and look for 
more episode to be posted very, 

260
00:16:09,040 --> 00:16:10,080
very soon. 
Bye bye.

