﻿WEBVTT

1
00:00:09.820 --> 00:00:14.500
<v 0>Hey, folks. I'm really excited to be here today. I'm Jake Sinsheimer,</v>

2
00:00:14.640 --> 00:00:17.100
the head of agentic commerce go-to-market for Stripe.

3
00:00:17.580 --> 00:00:20.440
So my team looks after our relationship with merchants.

4
00:00:20.700 --> 00:00:24.320
That can be big box retailers, that can be consumer marketplaces,

5
00:00:24.740 --> 00:00:28.300
vertical SaaS platforms that are enabling merchants in all different industries.

6
00:00:28.740 --> 00:00:32.700
And then the other side of the role is focused on establishing and growing our

7
00:00:32.800 --> 00:00:34.060
AI agent partnerships.

8
00:00:34.520 --> 00:00:38.820
We're super excited to announce Google and Gemini earlier in the keynote,

9
00:00:39.100 --> 00:00:43.420
and we own the relationship with OpenAI, Meta, Anthropic, and others.

10
00:00:44.200 --> 00:00:47.320
I'm here today to talk about something that will reshape how commerce works on

11
00:00:47.380 --> 00:00:50.480
your platforms and how your merchants do business.

12
00:00:51.060 --> 00:00:53.100
Just for a quick question for the room,

13
00:00:53.660 --> 00:00:57.960
how many of you in the last week or two have had a conversation with your team

14
00:00:58.280 --> 00:01:03.180
or maybe even a little moment of anxiety about what AI or

15
00:01:03.320 --> 00:01:06.700
agents mean for your business or your customer's businesses?

16
00:01:08.380 --> 00:01:10.220
That's a lot of you and about what I expected.

17
00:01:10.280 --> 00:01:12.680
And that's why this conversation matters right now.

18
00:01:13.260 --> 00:01:17.600
We're in the early stages of a fundamental AI-driven shift in commerce.

19
00:01:18.060 --> 00:01:22.920
We're going from human-led-search, scroll, compare-maybe you open 10,

20
00:01:23.160 --> 00:01:23.600
12,

21
00:01:23.600 --> 00:01:28.480
15 different tabs before eventually settling on what you're going to buy to

22
00:01:28.600 --> 00:01:30.600
agents that discover, evaluate,

23
00:01:30.700 --> 00:01:34.120
and complete transactions on behalf of consumers and businesses.

24
00:01:34.780 --> 00:01:38.280
And this isn't just some far-off future. It's already happening.

25
00:01:39.180 --> 00:01:41.240
And the projected opportunity is $5 trillion.

26
00:01:42.320 --> 00:01:46.360
That's McKinsey's forecast for global agentic commerce sales by 2030.

27
00:01:48.240 --> 00:01:51.520
So maybe what's most important for this room, everyone knows this,

28
00:01:51.620 --> 00:01:55.900
but platforms are the critical operating system for businesses of all sizes.

29
00:01:56.520 --> 00:01:57.880
And platforms that move early,

30
00:01:59.240 --> 00:02:02.880
are the ones whose merchants capture their share of that $5 trillion

31
00:02:03.360 --> 00:02:04.193
opportunity.

32
00:02:04.920 --> 00:02:08.720
We believe at Stripe that platforms will be the infrastructure layer enabling

33
00:02:08.740 --> 00:02:13.280
agentic commerce for all types of different businesses of all sizes and across

34
00:02:13.380 --> 00:02:17.860
all verticals.
And this space isn't just for the largest retailers with

35
00:02:18.100 --> 00:02:20.960
large engineering teams and well-known brands.

36
00:02:21.500 --> 00:02:25.940
This is the long tail of small businesses that are the lifeblood of America and

37
00:02:25.980 --> 00:02:27.960
other markets, and they need our help.

38
00:02:28.540 --> 00:02:33.140
The merchants who chose your SaaS platform because you gave them capabilities

39
00:02:33.160 --> 00:02:36.940
that they couldn't build on their own.
So where do things stand today?

40
00:02:37.580 --> 00:02:41.280
One of my favorite Stripe annual traditions is the annual letter.

41
00:02:41.820 --> 00:02:46.600
And Patrick and John shared a five-level framework on how to think about agentic

42
00:02:46.640 --> 00:02:50.740
commerce, sort of, as analogous to autonomous vehicles.

43
00:02:51.860 --> 00:02:55.620
So Level 1 is "No more forms." I have a 14-month-old daughter,

44
00:02:55.800 --> 00:02:57.900
so I'll use the example of finding her toys.

45
00:02:58.700 --> 00:03:02.660
I search on Google for toys for my 14-month-old, find one that looks okay,

46
00:03:03.100 --> 00:03:06.780
I click through the checkout page and an agent fills out the checkout form.

47
00:03:06.800 --> 00:03:11.740
And it's mostly just a glorified autofill experience.
Level 2 is

48
00:03:11.800 --> 00:03:15.900
more descriptive search or where the magic really starts. So maybe I search,

49
00:03:15.980 --> 00:03:17.820
"Find me toys for my 14-month-old.

50
00:03:18.140 --> 00:03:20.320
She's starting to learn how to cruise or walk.

51
00:03:20.520 --> 00:03:22.920
She loves music and bright colors.

52
00:03:23.400 --> 00:03:28.280
I got 50 to 75 bucks to spend." The agent searches across a variety of different

53
00:03:28.320 --> 00:03:32.180
retailers and catalogs, checks inventory, compares prices,

54
00:03:32.620 --> 00:03:34.820
surfaces the best couple of options in a carousel,

55
00:03:35.400 --> 00:03:38.460
and I still make the purchasing decision and go through the checkout flow.

56
00:03:39.200 --> 00:03:40.100
I described a need,

57
00:03:40.420 --> 00:03:43.400
but the agent did the research and discovery legwork on my behalf.

58
00:03:46.400 --> 00:03:48.520
Today, we're somewhere between Levels 1 and 2.

59
00:03:48.840 --> 00:03:52.640
Most AI shopping is Level 1 with a chatbot wrapper and Level 2 exists in

60
00:03:52.700 --> 00:03:55.840
pockets, but it's a bit fragmented and a little unreliable.

61
00:03:56.360 --> 00:03:57.880
This space is genuinely nascent,

62
00:03:58.220 --> 00:04:02.680
and we're weeks or months into a decade-long shift.
Level 3 is "Persistent

63
00:04:02.680 --> 00:04:05.240
memory." The agent already knows.

64
00:04:05.700 --> 00:04:09.340
I've been using ChatGPT for the better part of the last year-and a half,

65
00:04:09.760 --> 00:04:11.280
it knows my daughter is 14 months old,

66
00:04:11.280 --> 00:04:13.720
it knows she loves that Fisher-Price drum set,

67
00:04:13.720 --> 00:04:18.340
it knows to avoid toys with sharp edges. I don't need to re-explain.

68
00:04:18.800 --> 00:04:22.760
It shops like someone who knows my family, preferences compound over time,

69
00:04:22.920 --> 00:04:27.040
and it gets better with every interaction.
Level 4 is when we sort of move into

70
00:04:27.080 --> 00:04:31.280
more autonomy. I can delegate an agent to activate on my behalf.

71
00:04:31.940 --> 00:04:35.480
I sort of just say, "Order her monthly development toys, under $75,

72
00:04:36.120 --> 00:04:39.800
keep it age appropriate," and something shows up at my front door a couple days

73
00:04:39.880 --> 00:04:43.840
later.
I set the parameters once, the agent executes and adapts.

74
00:04:44.740 --> 00:04:48.340
When she turns 18 months old, perhaps it even adjusts without being asked.

75
00:04:49.240 --> 00:04:53.560
And it can go ahead and anticipate what our needs are. It notices, "Hey,

76
00:04:53.900 --> 00:04:58.100
it seems like Ella's walking is progressing." It proactively suggests and pushes

77
00:04:58.160 --> 00:05:00.780
toys before I think to look. She says something like,

78
00:05:01.460 --> 00:05:03.160
"She'll be ready for outdoor play by summer.

79
00:05:03.580 --> 00:05:07.200
Here's what I'd order now." It's not reactive, it's proactive.

80
00:05:07.560 --> 00:05:10.820
It's effectively a personalized chief of staff for your family.

81
00:05:11.600 --> 00:05:15.140
We're still super early in the journey across the five levels,

82
00:05:15.420 --> 00:05:17.780
and all of this will require working together.

83
00:05:18.280 --> 00:05:21.580
Climbing from Level 1 or 2 to Level 5 isn't automatic.

84
00:05:21.980 --> 00:05:24.460
Needs merchant and platform cooperation.

85
00:05:24.860 --> 00:05:29.460
Agent and AI capabilities need to continue to advance and consumer trust has to

86
00:05:29.540 --> 00:05:30.320
follow.

87
00:05:30.320 --> 00:05:34.100
And financial partners and infrastructure have to power this entire experience.

88
00:05:34.660 --> 00:05:37.620
The opportunity is enormous, but we're still on the first rung or two.

89
00:05:39.280 --> 00:05:43.080
I've talked to a lot of platforms and what we consistently hear is they don't

90
00:05:43.100 --> 00:05:46.940
want to reinvent the wheel for every new AI channel and they want to help their

91
00:05:47.000 --> 00:05:50.400
merchants acquire more customers. So we asked,

92
00:05:50.880 --> 00:05:55.100
"What if a single integration made every merchant on your platform discoverable

93
00:05:55.280 --> 00:06:00.000
and transactable across all of the AI services today and as new ones

94
00:06:00.020 --> 00:06:04.580
emerge into the future?" So that's what we've built: the Agentic Commerce Suite,

95
00:06:04.880 --> 00:06:08.900
ACS for short. It's one integration in every agentic surface.

96
00:06:09.440 --> 00:06:13.480
Stripe effectively serves as the translation layer and enables new agent

97
00:06:13.580 --> 00:06:15.860
integrations seamlessly as they emerge.

98
00:06:16.240 --> 00:06:19.920
We're plugging in platforms that can enable their merchants to sell across

99
00:06:20.000 --> 00:06:24.740
ChatGPT, Microsoft Copilot, and, today, Gemini and AI Mode.

100
00:06:25.680 --> 00:06:27.440
We're already live with this experience today.

101
00:06:27.660 --> 00:06:31.040
We have a variety of platforms who are integrating with ACS and Wix and

102
00:06:31.060 --> 00:06:32.800
commercetools, who you'll hear from in a bit,

103
00:06:33.020 --> 00:06:36.080
are already integrated and opening up some of these surfaces for their

104
00:06:36.120 --> 00:06:38.640
merchants.
We're moving super quickly,

105
00:06:39.060 --> 00:06:41.100
onboarding merchants and platforms in waves,

106
00:06:41.420 --> 00:06:43.920
and I wanted to call out a little bit of an elephant in the room.

107
00:06:44.640 --> 00:06:47.300
The industry has been hyperfocused on retail,

108
00:06:47.800 --> 00:06:51.280
and that's where the most mature transaction layer is, but from our perspective,

109
00:06:51.380 --> 00:06:52.540
agentic won't stop there.

110
00:06:53.260 --> 00:06:57.020
Vertical SaaS is likely to become the critical infrastructure layer for

111
00:06:57.080 --> 00:07:01.720
merchants and service provider discovery by AI agents. As an example,

112
00:07:02.120 --> 00:07:06.940
maybe I ask my personal assistant in my pocket to book a haircut and I

113
00:07:07.000 --> 00:07:09.160
want something within a mile of my house,

114
00:07:09.460 --> 00:07:12.720
at least four-and-a-half stars availability between 10:00 a.m.

115
00:07:13.280 --> 00:07:14.820
and noon on Saturday.

116
00:07:15.440 --> 00:07:19.620
It could pull structured data from a platform like SQUIRE because SQUIRE has

117
00:07:19.720 --> 00:07:24.040
machine-readable, structured data around availability,

118
00:07:24.360 --> 00:07:26.280
services, pricing, location.

119
00:07:26.840 --> 00:07:31.040
So if you run a vertical SaaS platform for salons, for fitness studios,

120
00:07:31.440 --> 00:07:32.320
home services,

121
00:07:32.860 --> 00:07:35.620
everything we're walking through can and will apply to you and your merchants

122
00:07:35.680 --> 00:07:39.440
too. So where should you start? First,

123
00:07:39.640 --> 00:07:43.960
you need to be deliberate and develop an AI commerce strategy and sit down and

124
00:07:44.020 --> 00:07:47.640
figure out who are you going to partner with, what data assets do you have,

125
00:07:47.960 --> 00:07:49.540
and how are you going to architect?

126
00:07:51.140 --> 00:07:55.580
Number 2 is "Organize your information." You need to sort of figure out what

127
00:07:56.240 --> 00:07:58.980
data that you have from those merchants and how are you going to package that

128
00:07:59.020 --> 00:08:03.600
together to help them become AI-readable.
Number 3 is

129
00:08:03.940 --> 00:08:08.380
"Assign ownership of AI specific work." The good news is this person probably

130
00:08:08.480 --> 00:08:10.060
already exists in your organization.

131
00:08:10.460 --> 00:08:12.820
It looks like an enterprising product manager,

132
00:08:13.260 --> 00:08:17.960
maybe it's even a senior leader like your CIO, or maybe it's a savvy ops lead.

133
00:08:18.280 --> 00:08:19.460
It just needs to be someone,

134
00:08:19.880 --> 00:08:24.400
you need to identify them and then they can drive your organization forward.
And

135
00:08:24.600 --> 00:08:25.200
fourth,

136
00:08:25.200 --> 00:08:29.120
you want to make sure that you're adding value on top to make your merchants

137
00:08:29.160 --> 00:08:32.920
products agent friendly. You want to layer high-fidelity metadata,

138
00:08:33.200 --> 00:08:37.000
things like rich descriptions, structured attributes, photos,

139
00:08:37.480 --> 00:08:38.520
third-party reviews.

140
00:08:39.240 --> 00:08:42.000
Agent readiness should be a default output of your platform,

141
00:08:42.360 --> 00:08:44.960
not something that merchants have to think about or do themselves.

142
00:08:45.320 --> 00:08:49.480
They should just click a button and expect that their sales will increase.

143
00:08:49.880 --> 00:08:51.800
Every merchant should benefit automatically.

144
00:08:52.160 --> 00:08:56.240
Their products get recommended over local competitors whose platforms left this

145
00:08:56.400 --> 00:09:00.040
to the merchant. So this isn't just a new buy button.

146
00:09:00.320 --> 00:09:04.200
It's about your platform becoming the infrastructure that powers how merchants

147
00:09:04.200 --> 00:09:08.120
sell in an AI-first world.
The best way to understand this is to hear from

148
00:09:08.160 --> 00:09:09.600
platforms already building for it.

149
00:09:10.080 --> 00:09:13.240
And so I'm pleased to welcome on stage my friend Lauren Garcia,

150
00:09:13.320 --> 00:09:16.200
who leads our work with SaaS platforms on the cutting edge of innovation,

151
00:09:16.360 --> 00:09:19.640
and she's bringing on our fantastic partners, Vova and Dirk,

152
00:09:19.960 --> 00:09:21.440
from Wix and commercetools.

153
00:09:31.640 --> 00:09:32.473
<v 1>Thank you, Jake.</v>

154
00:09:32.800 --> 00:09:36.760
I am so excited to be here and having this conversation with both of you today.

155
00:09:37.240 --> 00:09:40.920
There's obviously a ton of momentum happening around the topic of agentic

156
00:09:41.040 --> 00:09:41.560
commerce,

157
00:09:41.560 --> 00:09:44.520
but we get to spend the next 20 minutes with some folks that are actually on the

158
00:09:44.560 --> 00:09:48.280
ground building it. Before we dive into their real world strategies,

159
00:09:48.480 --> 00:09:50.920
let's take a minute to do some quick introductions. Vova,

160
00:09:51.040 --> 00:09:51.873
I'm going to start with you.

161
00:09:52.160 --> 00:09:55.120
If you could share with the audience a little bit about your role at Wix and

162
00:09:55.200 --> 00:09:57.120
give us the very brief, if you can,

163
00:09:57.640 --> 00:10:00.880
elevator pitch on where Wix is in your agentic commerce journey today.

164
00:10:01.120 --> 00:10:02.880
<v 2>First of all, I want to say hi to everybody.</v>

165
00:10:02.960 --> 00:10:06.680
I hope you are all in a good mood and energetic mood just like me today.

166
00:10:06.840 --> 00:10:10.240
So my name is Vova Tsukur. I am leading payments at Wix.

167
00:10:10.720 --> 00:10:12.720
I think many of you have heard about our platform,

168
00:10:12.880 --> 00:10:17.560
but basically we are a leading platform for creating websites and also web

169
00:10:17.680 --> 00:10:20.440
applications. We are also owning Base44 product,

170
00:10:20.520 --> 00:10:22.240
which is growing like crazy in the last year.

171
00:10:22.720 --> 00:10:24.880
And I'm responsible for all things payments.

172
00:10:25.280 --> 00:10:27.720
Over 300 million users are on our platform.

173
00:10:27.800 --> 00:10:30.880
Over 1 million businesses are running on top of it because we're also a business

174
00:10:30.920 --> 00:10:33.080
operating system in addition to the creation platform.

175
00:10:33.480 --> 00:10:35.920
Processed around 14B in 2025.

176
00:10:36.520 --> 00:10:40.640
So majority of our merchants are actually small in the smaller fraction of the

177
00:10:40.950 --> 00:10:43.760
SMBs, in a smaller size amongst SMBs.

178
00:10:44.940 --> 00:10:47.200
And we started our agentic journey back in 2024,

179
00:10:47.640 --> 00:10:50.200
did a lot of crazy things in 2025. We'll talk about it.

180
00:10:50.400 --> 00:10:50.800
<v 1>Yes.</v>

181
00:10:50.800 --> 00:10:53.200
<v 2>And I'm happy to, again, repeat,</v>

182
00:10:53.380 --> 00:10:55.020
not to announce because it was already announced,

183
00:10:55.040 --> 00:10:58.520
to repeat that we are live with Stripe ACS right now,

184
00:10:58.580 --> 00:11:00.060
which is super exciting.

185
00:11:00.280 --> 00:11:02.600
<v 1>Very exciting. Thank you so much. Dirk, over to you.</v>

186
00:11:03.200 --> 00:11:05.200
<v 3>Yeah. Hi, everybody. My name is Dirk.</v>

187
00:11:05.320 --> 00:11:08.520
I'm a co-founder and managing director at commercetools. First,

188
00:11:08.760 --> 00:11:12.720
thanks to all of you for staying here. I think the lunch hour has just begun,

189
00:11:12.860 --> 00:11:16.300
so I know we have some hard competition out there. So give it 30 more minutes.

190
00:11:16.360 --> 00:11:17.960
I think we will make it exciting.

191
00:11:18.020 --> 00:11:20.820
So quickly about commercetools for those who don't know it,

192
00:11:20.880 --> 00:11:23.120
commercetools is a headless commerce platform provider,

193
00:11:23.520 --> 00:11:27.040
basically helping companies run outstanding shopping experiences across all

194
00:11:27.080 --> 00:11:29.460
touchpoints. We are doing that for the enterprise market,

195
00:11:29.520 --> 00:11:33.580
so companies like AT&amp;T, Sephora, Ulta Beauty, Lego,

196
00:11:34.200 --> 00:11:36.480
BMW, and so on, are running on our platform.

197
00:11:36.960 --> 00:11:39.780
We recently crossed a hundred billion of annual GMV,

198
00:11:39.980 --> 00:11:43.980
making us one of the largest commerce infrastructure providers globally out

199
00:11:44.020 --> 00:11:46.080
there. So what we are pretty proud of.

200
00:11:46.360 --> 00:11:49.160
And now talking about agentic commerce,

201
00:11:49.460 --> 00:11:51.840
we also similar like Wix and Vova,

202
00:11:51.960 --> 00:11:54.560
started our discovery journey end of '24,

203
00:11:55.020 --> 00:11:57.080
then did heavy investments in '25,

204
00:11:57.580 --> 00:12:00.320
starting with MCP servers on top of APIs,

205
00:12:00.780 --> 00:12:05.340
built some on-brand shopping assistance.
And then the protocol started to

206
00:12:05.400 --> 00:12:06.120
evolve,

207
00:12:06.120 --> 00:12:09.560
and things started to become a little bit more chaotic for the brands and

208
00:12:09.580 --> 00:12:10.880
retailers out there. We said, "Okay,

209
00:12:11.000 --> 00:12:14.440
can you help us here?" So we started with the adoption and had been very happy,

210
00:12:14.520 --> 00:12:16.800
when then Stripe approached and said, "Hey,

211
00:12:16.880 --> 00:12:19.000
we are actually working here on an integration layer.

212
00:12:20.560 --> 00:12:24.380
Let's partner together." So happy to announce, as you have heard earlier today,

213
00:12:24.460 --> 00:12:26.940
we are launch partner of the Stripe ACS,

214
00:12:27.240 --> 00:12:31.300
getting now the first customer's live also within the next couple of days. Yeah.

215
00:12:31.580 --> 00:12:33.240
So looking forward to what's coming next.

216
00:12:33.500 --> 00:12:34.280
<v 1>Absolutely. Well,</v>

217
00:12:34.280 --> 00:12:37.180
thank you both for your partnership and also congrats on the incredible success

218
00:12:37.220 --> 00:12:39.780
that you're driving across each of your platforms. Vova,

219
00:12:39.960 --> 00:12:42.680
I want to start with you taking it back, you said to the year 2024,

220
00:12:43.380 --> 00:12:46.400
can you tell us a little bit about when you first got that signal that agentic

221
00:12:46.440 --> 00:12:49.220
commerce was something that Wix absolutely had to invest in?

222
00:12:49.880 --> 00:12:51.640
<v 2>So basically we, of course,</v>

223
00:12:51.700 --> 00:12:56.380
we decided to move back in 2024 when we saw all things happening with

224
00:12:56.560 --> 00:13:00.180
AI and also shifts in commerce and shifts in behaviors.

225
00:13:00.800 --> 00:13:04.000
We decided that we don't want to sit on the sidelines.

226
00:13:04.080 --> 00:13:08.580
We actually don't want to see how other products and experiences emerge

227
00:13:08.940 --> 00:13:10.660
and we are not there.

228
00:13:10.900 --> 00:13:15.880
So we were looking for design partnerships actively in 2024 and also in 2025.

229
00:13:16.500 --> 00:13:19.780
So I can say the move was primarily driven by conviction.

230
00:13:19.840 --> 00:13:20.620
<v 1>Conviction.</v>

231
00:13:20.620 --> 00:13:24.700
<v 2>And less by the data. I cannot say it was not driven by data. Of course,</v>

232
00:13:24.760 --> 00:13:25.593
we're looking at the data,

233
00:13:25.660 --> 00:13:29.680
but when somebody is approaching you and telling you what's going to be the

234
00:13:29.720 --> 00:13:32.940
final product? who will use it? What's going to be the scale?

235
00:13:33.020 --> 00:13:37.400
You cannot be 100% pixel-perfect on the answers. So in

236
00:13:39.160 --> 00:13:41.060
the first rounds, as you move,

237
00:13:41.420 --> 00:13:45.620
you need to be more a believer rather than the factual person.

238
00:13:45.960 --> 00:13:48.340
And I think it's important for me also to mention that we,

239
00:13:48.720 --> 00:13:52.650
platforms-commercetools, Wix-we exist in order...

240
00:13:53.940 --> 00:13:58.740
We exist because SMBs cannot produce everything they need to run the

241
00:13:58.780 --> 00:14:01.440
business by themselves. So we have a saying internally: "Let the baker bake."

242
00:14:03.380 --> 00:14:05.200
So we understood the opportunities there.

243
00:14:05.320 --> 00:14:09.800
We understood that it's an opportunity to create a much better user

244
00:14:09.840 --> 00:14:12.040
experience, and, yeah,

245
00:14:12.120 --> 00:14:14.860
decided to invest like crazy.

246
00:14:15.280 --> 00:14:15.540
<v 1>Okay.</v>

247
00:14:15.540 --> 00:14:18.500
I want to come back to that point of data versus conviction because I imagine

248
00:14:18.520 --> 00:14:21.320
that was probably pretty difficult to sell into your leadership team on

249
00:14:21.380 --> 00:14:22.300
conviction alone.

250
00:14:23.020 --> 00:14:25.920
But I also want to hit on the point that you made that it was really solving

251
00:14:25.960 --> 00:14:27.860
complex problems for your merchants, right?

252
00:14:27.920 --> 00:14:30.840
Which is at the heart of what you're trying to do in that you saw that that was

253
00:14:30.880 --> 00:14:34.300
the world where AI was going and how AI could only help you accelerate that.

254
00:14:34.460 --> 00:14:34.940
<v 2>Absolutely.</v>

255
00:14:34.940 --> 00:14:38.760
<v 1>So really interesting points. Dirk, I'd love to talk a little bit more about,</v>

256
00:14:39.100 --> 00:14:40.960
this is a big shift for you internally.

257
00:14:41.140 --> 00:14:44.160
How did you think about structuring your teams once you made the choice at

258
00:14:44.180 --> 00:14:46.220
commercetools to invest in agentic commerce?

259
00:14:46.280 --> 00:14:49.720
Was there a particular head of AI that you put in place or did you think it

260
00:14:49.740 --> 00:14:52.060
about maybe a more cross-functional rework?

261
00:14:52.340 --> 00:14:55.490
<v 3>Yeah, we actually did multiple things and probably all of it.</v>

262
00:14:55.980 --> 00:14:59.870
Maybe let me get one step here also to what Vova said.

263
00:15:00.520 --> 00:15:04.210
We had been convinced that the customer journey is going to change and that

264
00:15:04.310 --> 00:15:06.490
conviction, similar like I think Wix got it,

265
00:15:07.030 --> 00:15:11.790
got to that point early '25 where I spoke to leaders of

266
00:15:12.530 --> 00:15:14.810
large retailers, many of our customers, and they told us,

267
00:15:15.230 --> 00:15:16.850
"We see a change in traffic pattern,

268
00:15:17.270 --> 00:15:20.810
both what's coming to our website and also already on page behavior." And that's

269
00:15:20.850 --> 00:15:23.150
now almost 14, 15 months ago.

270
00:15:23.450 --> 00:15:26.030
And so we believe similar as Jake has shown it,

271
00:15:26.090 --> 00:15:30.650
that the market is going towards a $5 trillion opportunity.

272
00:15:31.270 --> 00:15:33.560
We came to similar forecast mid of '25,

273
00:15:34.190 --> 00:15:36.400
believing that by the end of 2030,

274
00:15:36.790 --> 00:15:41.310
roughly 30% of the market will be in some way affected by agentic shopping.

275
00:15:41.690 --> 00:15:46.030
And that is all of ecommerce in 2020.
So just if we put that into perspective.

276
00:15:46.670 --> 00:15:47.890
So as a platform provider,

277
00:15:47.950 --> 00:15:50.750
because our mission is to provide a future-proof platform to all of our

278
00:15:50.790 --> 00:15:53.550
customers. So if you want to be future-proof and you say,

279
00:15:53.580 --> 00:15:58.490
"30% will happen there," you need to go all-in or nothing. So therefore,

280
00:15:59.130 --> 00:16:02.490
yes, we defined a product ahead of AI role that's dedicated.

281
00:16:02.570 --> 00:16:07.350
And we said "We need to have dedicated role or teams that are just focused on

282
00:16:07.390 --> 00:16:09.690
the agentic shopping part of it." So for example,

283
00:16:09.750 --> 00:16:13.950
that are working with your teams on the ACS partnership and integration,

284
00:16:14.550 --> 00:16:18.510
then we have cross-functional teams because AI is not just happening in one team

285
00:16:18.590 --> 00:16:21.430
and agentic also not. So yes, in every team there's something of that,

286
00:16:22.030 --> 00:16:25.490
but last but not least is probably as important that you make it a C-level

287
00:16:25.530 --> 00:16:28.470
priority. So we said, "Okay, we need to own that.

288
00:16:28.530 --> 00:16:31.550
We need to drive the strategy." So I took the hat on that, said, "Okay,

289
00:16:31.630 --> 00:16:33.350
I need to run our both internal,

290
00:16:33.470 --> 00:16:38.290
external AI and agentic shopping innovations." And then we enhance the

291
00:16:38.330 --> 00:16:40.110
team. So we have a business development role for that,

292
00:16:40.170 --> 00:16:43.310
we have a partner role for that and so on. So it got broader over the last year,

293
00:16:43.430 --> 00:16:45.750
but similar as Vova said,

294
00:16:46.130 --> 00:16:50.710
it's a heavy investment that you have to do to also then make it less of an

295
00:16:50.750 --> 00:16:51.890
investment for your customers.

296
00:16:52.290 --> 00:16:53.350
<v 1>So following the data,</v>

297
00:16:53.510 --> 00:16:56.210
but then also thinking about starting with the core infrastructure with your

298
00:16:56.230 --> 00:16:56.810
product team,

299
00:16:56.810 --> 00:17:01.230
and then how did you scale out from there and making sure that you had a lead AI

300
00:17:01.290 --> 00:17:04.090
person across each of those cross-functional teams with that?

301
00:17:04.210 --> 00:17:05.550
<v 2>I want to chime in with a quick comment.</v>

302
00:17:06.010 --> 00:17:09.370
Our stories are very similar in this regard, and, actually,

303
00:17:10.350 --> 00:17:14.390
like this whole thing around agentic commerce in the companies are usually not

304
00:17:14.610 --> 00:17:19.110
driven by the head of AI. These are driven by the product and business people.

305
00:17:19.610 --> 00:17:20.960
But AI,

306
00:17:22.910 --> 00:17:25.190
your people who are like really proficient in AI,

307
00:17:25.370 --> 00:17:28.830
they're definitely participating and we have internally,

308
00:17:28.890 --> 00:17:32.550
we're calling it the "heart of AI." So the person, his name is Ron by the way,

309
00:17:32.630 --> 00:17:36.950
many things that are happening inside is because of his involvement and because

310
00:17:36.960 --> 00:17:40.810
of his drive. So having those people on the team is super important.

311
00:17:41.220 --> 00:17:44.050
<v 1>Some frontrunners, some leaders that are then infiltrating it across the org?</v>

312
00:17:45.000 --> 00:17:45.000
<v 2>Yes. Yes.</v>

313
00:17:45.000 --> 00:17:46.010
<v 1>Okay. Dirk,</v>

314
00:17:46.150 --> 00:17:49.050
I want to come back to you for a second because this is obviously a huge shift

315
00:17:49.110 --> 00:17:52.370
for the platforms in the room, but it's also a huge shift for your merchants.

316
00:17:52.610 --> 00:17:56.390
We heard from Will in the keynote today that product catalogs as we know them

317
00:17:56.490 --> 00:18:00.890
today have been designed for human search, not necessarily for agentic search.

318
00:18:00.970 --> 00:18:05.090
So how did you see that shift take place and how much of that did you decide to

319
00:18:05.130 --> 00:18:08.690
take on as a platform that you needed to own in that change versus how much your

320
00:18:08.750 --> 00:18:09.970
merchants actually had to take on?

321
00:18:10.050 --> 00:18:11.910
<v 3>Yeah. This is actually a big challenge, I would say,</v>

322
00:18:11.990 --> 00:18:15.750
for literally every merchant that's out there. It's the quality of the data.

323
00:18:16.230 --> 00:18:17.110
So we, for example,

324
00:18:17.550 --> 00:18:21.590
help our customers manage over 200 million products across all of our catalogs

325
00:18:21.630 --> 00:18:23.190
plus pricing, inventory and so on.

326
00:18:23.990 --> 00:18:27.450
But all of that data had been optimized for the human shopping channels.

327
00:18:27.950 --> 00:18:29.770
And of course there's SEO and so on,

328
00:18:30.370 --> 00:18:34.610
but as the customer journey is changing and also what their consumers are now

329
00:18:34.830 --> 00:18:39.250
typing in looks way different because it's not, "Okay, I need," I don't know,

330
00:18:39.250 --> 00:18:41.710
"a gray jeans," with that criteria. No.

331
00:18:41.710 --> 00:18:45.230
"I'm looking for an outfit that I can go for for Stripe Sessions.

332
00:18:45.350 --> 00:18:48.130
What do you recommend me?" And that type of information,

333
00:18:48.390 --> 00:18:50.650
all of that context data, isn't there yet.

334
00:18:50.950 --> 00:18:54.670
And this puts pressure on the brands and retailers. I think this data problem,

335
00:18:54.750 --> 00:18:57.730
I now spend 25 years in commerce.
And the first day,

336
00:18:57.850 --> 00:19:01.830
what I learned is data is becoming a problem. So our data is not good enough.

337
00:19:02.150 --> 00:19:04.410
Now 25 years later, data is still not good enough.

338
00:19:04.490 --> 00:19:08.550
I hope this is now probably the last wave that we are going through. Who knows?

339
00:19:09.250 --> 00:19:13.370
But, as platforms, I think our role here is evolving.

340
00:19:14.530 --> 00:19:18.290
It's not any more about, we have seen from Jake and from the Stripe letter,

341
00:19:18.350 --> 00:19:22.110
these five steps of agentic commerce, getting rid of forms.

342
00:19:22.210 --> 00:19:24.130
It's not only about getting rid of forms. Also,

343
00:19:24.690 --> 00:19:26.930
to the marketing teams and to the catalog teams,

344
00:19:26.990 --> 00:19:30.450
it's also helping them to enrich the data because we are now becoming system of

345
00:19:30.510 --> 00:19:31.343
records,

346
00:19:31.490 --> 00:19:35.990
and we have to become systems of agentic execution to get that job done.

347
00:19:36.050 --> 00:19:38.130
So therefore we started to evolve our platform,

348
00:19:38.490 --> 00:19:42.390
provide agents that are helping them with the catalog enrichment and so on.
Yes,

349
00:19:42.450 --> 00:19:46.410
there's still a lot of work that brands need to do and they need to care about

350
00:19:46.430 --> 00:19:47.130
their own products,

351
00:19:47.130 --> 00:19:51.310
but I think we as platform providers can help them significantly getting better

352
00:19:51.350 --> 00:19:51.530
there.

353
00:19:51.530 --> 00:19:54.290
<v 1>So like really writing the rules and shaping kind of the infrastructure that</v>

354
00:19:54.310 --> 00:19:57.990
your merchants needed to adapt to for that data collection. Vova,

355
00:19:58.070 --> 00:19:59.190
anything that you would add to that?

356
00:19:59.710 --> 00:20:00.030
<v 2>Yeah,</v>

357
00:20:00.030 --> 00:20:02.350
there are many things which are overlapping and there are things that I would

358
00:20:02.390 --> 00:20:03.223
like to add.

359
00:20:03.250 --> 00:20:07.150
I definitely agree with the point that we as platforms are responsible on

360
00:20:07.410 --> 00:20:11.640
helping merchants to make sure that they are well discoverable in

361
00:20:13.210 --> 00:20:15.850
the new world of agent commerce and the new. It's not just a new channel;

362
00:20:15.910 --> 00:20:19.750
it's a completely new experience. So we definitely can produce tools, again,

363
00:20:20.110 --> 00:20:24.510
AI-based tools, that would hint them, that will help them to actually get there.

364
00:20:24.590 --> 00:20:25.030
I want to say,

365
00:20:25.030 --> 00:20:29.410
especially it's important for us because our merchants are smaller and their

366
00:20:29.470 --> 00:20:32.610
products can look like a super small role-.

367
00:20:32.610 --> 00:20:33.490
<v 1>Probably difficult to discover.</v>

368
00:20:33.630 --> 00:20:37.950
<v 2>Yes, in a very big spreadsheet. So this is one thing that I wanted to point out.</v>

369
00:20:38.010 --> 00:20:40.490
Another thing that I wanted to point out, which is really interesting,

370
00:20:40.550 --> 00:20:43.690
and we have not been talking yet about it enough, I think,

371
00:20:44.150 --> 00:20:48.570
is every merchant has certain code of conduct-the

372
00:20:48.650 --> 00:20:53.650
policies, the tone of voice, how he or she talks to the customer.

373
00:20:54.190 --> 00:20:58.010
And, actually, the agent who is representing that merchant,

374
00:20:58.450 --> 00:21:01.350
we see that it needs to incorporate

375
00:21:03.610 --> 00:21:07.230
those principles, those strategies, that way communication,

376
00:21:07.310 --> 00:21:10.610
it's needed for both agents on the other side, but also needed for humans.

377
00:21:11.250 --> 00:21:12.630
So we see a big opportunity here,

378
00:21:13.010 --> 00:21:17.870
and this is the challenge that I think we'll be able also to solve together with

379
00:21:17.910 --> 00:21:18.610
other platforms.

380
00:21:18.610 --> 00:21:22.650
And it's definitely the platform responsibility to help merchants get there.

381
00:21:23.450 --> 00:21:28.390
Another thing which was also voiced over in the beginning of our overall

382
00:21:28.430 --> 00:21:29.770
talk was about services.

383
00:21:30.170 --> 00:21:34.990
We don't see only ecommerce and like only retail as the forefront

384
00:21:35.150 --> 00:21:36.170
of the agentic experience.

385
00:21:36.230 --> 00:21:41.170
We actually want more and more experiences to be discovered and

386
00:21:41.470 --> 00:21:43.570
paid for and booked like bookings.

387
00:21:43.870 --> 00:21:46.170
So this is another challenge we are actively looking at.

388
00:21:46.430 --> 00:21:47.750
Even though we are horizontal SaaS,

389
00:21:47.850 --> 00:21:51.150
this is very interesting for us because we see all type of use cases out there.

390
00:21:51.390 --> 00:21:53.650
<v 1>And how have you both felt that your merchants have been able to keep up with</v>

391
00:21:53.670 --> 00:21:57.610
this? Have they been excited about this? Has it been somewhat overwhelming?

392
00:21:57.930 --> 00:22:01.950
<v 3>I think it's both. Everybody's excited and everybody is similarly overwhelmed,</v>

393
00:22:02.030 --> 00:22:04.470
probably like everybody here in the audience. So it also had been,

394
00:22:04.650 --> 00:22:05.930
this morning been amazing,

395
00:22:05.990 --> 00:22:09.750
the pace now of rollouts that are happening at Stripe,

396
00:22:09.810 --> 00:22:13.050
also at all of our companies, but you need to be able to follow up with that.

397
00:22:13.190 --> 00:22:16.690
And I think that we are trying to do a good job on helping our customers to

398
00:22:16.830 --> 00:22:17.663
embrace that pace.

399
00:22:17.870 --> 00:22:20.410
<v 1>We're all learning at the same time. Vova,</v>

400
00:22:20.910 --> 00:22:23.310
you all are obviously very much still in your building journey.

401
00:22:23.450 --> 00:22:26.070
I don't want to assume by any means that you're anywhere near done,

402
00:22:26.130 --> 00:22:28.170
but as you think about where you've come thus far,

403
00:22:28.310 --> 00:22:31.290
what's been the single biggest hurdle that you've had to overcome to get agentic

404
00:22:31.770 --> 00:22:32.603
off the ground?

405
00:22:32.690 --> 00:22:37.670
<v 2>So basically for us, it was very hard, even though we solved this challenge,</v>

406
00:22:37.790 --> 00:22:41.430
but it was really hard for us to get the priority on this whole thing

407
00:22:42.350 --> 00:22:44.370
internally, because again, we are the creation platform.

408
00:22:44.470 --> 00:22:49.190
We are not the ecommerce platform by definition. But we saw an opportunity.

409
00:22:49.530 --> 00:22:50.690
So we built a case,

410
00:22:51.070 --> 00:22:55.190
we united the teams inside Wix to make sure we had like removed the walls

411
00:22:55.570 --> 00:22:56.170
between...

412
00:22:56.170 --> 00:22:59.410
You also talked about it before that you had to remove the walls to create like

413
00:22:59.490 --> 00:23:02.850
certain force that is dedicated to that effort. And we did that.

414
00:23:03.710 --> 00:23:06.490
Also did the pitch to management, make sure it's an internal program.

415
00:23:07.550 --> 00:23:12.370
And this whole path was not easy. And Ron,

416
00:23:12.430 --> 00:23:16.030
the person I mentioned before, he played a key role here.

417
00:23:16.090 --> 00:23:18.870
So that was the first challenge that I wanted to outline and probably the

418
00:23:18.910 --> 00:23:23.490
biggest. I'm happy to say that we solved it early enough and that's great.

419
00:23:23.570 --> 00:23:27.990
We are in the good place right now.
Now then other challenge is-which I think is

420
00:23:28.050 --> 00:23:32.350
important for everyone here in the audience-is how we as

421
00:23:32.450 --> 00:23:33.283
platforms

422
00:23:35.120 --> 00:23:37.510
are thinking about the next steps.

423
00:23:37.590 --> 00:23:40.370
Not just about the immediate next step,

424
00:23:40.450 --> 00:23:45.370
which is having agents talking to each other and selling, but questions like,

425
00:23:45.850 --> 00:23:49.770
"What is happening to the brand voice of the merchant?".

426
00:23:49.850 --> 00:23:53.990
<v 1>I think probably closer to that like fifth point on Jake's scale, right?</v>

427
00:23:54.070 --> 00:23:55.350
<v 2>Yes, yes, yes, yes. And here,</v>

428
00:23:56.110 --> 00:24:01.010
really the organizational muscle I think is being tested really hard on how you

429
00:24:01.110 --> 00:24:05.750
can adapt, how you can pivot, how you can figure out the problems,

430
00:24:06.050 --> 00:24:09.790
but also actively think about solutions for those problems.

431
00:24:10.150 --> 00:24:12.790
And it's important to start that process early.

432
00:24:13.610 --> 00:24:16.390
We are all got used, I think,

433
00:24:17.410 --> 00:24:22.230
to moving before AI times, to moving slower and thinking about, "Okay,

434
00:24:22.310 --> 00:24:22.850
we'll wait.

435
00:24:22.850 --> 00:24:27.570
We'll see how things will evolve and then we'll jump onto the ship." The

436
00:24:27.630 --> 00:24:32.590
problem is we are accumulating risks with that approach

437
00:24:32.730 --> 00:24:36.210
and not accumulating knowledge and learning with that approach.

438
00:24:36.550 --> 00:24:37.930
So it's really the time to shift it.

439
00:24:38.250 --> 00:24:42.030
Either we're talking about agentic commerce or we are talking about transforming

440
00:24:42.210 --> 00:24:45.490
our companies to be AI-native companies in terms of how we work.

441
00:24:45.710 --> 00:24:49.050
<v 1>Okay. I want to come back to a point that you made earlier on,</v>

442
00:24:49.110 --> 00:24:51.890
which was this idea of conviction and data and that you mentioned the biggest

443
00:24:51.930 --> 00:24:54.910
hurdle that you had to get this off the ground was actually getting your

444
00:24:54.970 --> 00:24:58.250
leadership to kind of understand the value. How did you all think about that?

445
00:24:58.330 --> 00:25:02.050
How did you sell in the ROI when there maybe wasn't necessarily a big number to

446
00:25:02.090 --> 00:25:03.830
put up on screen in the early days?

447
00:25:04.610 --> 00:25:05.690
<v 3>Well, from my perspective,</v>

448
00:25:05.750 --> 00:25:09.150
there was a big number because we also put these $5 trillion opportunity in

449
00:25:09.150 --> 00:25:09.210
front-.

450
00:25:09.210 --> 00:25:09.790
<v 1>The $5 trillion.</v>

451
00:25:09.790 --> 00:25:12.690
<v 3>And from that, that is the opportunity, right? So the question is always,</v>

452
00:25:12.770 --> 00:25:15.350
if you are not doing that, then somebody else will go in there.

453
00:25:15.410 --> 00:25:16.430
Then it's their opportunity.

454
00:25:17.290 --> 00:25:19.890
<v 1>By the prize lost if you're not jumping in now.</v>

455
00:25:19.950 --> 00:25:24.390
<v 3>I think a challenge-and we spoke before about that-for both of our companies and</v>

456
00:25:24.410 --> 00:25:28.570
probably everybody in the room here is you need to get comfortable to develop

457
00:25:28.630 --> 00:25:33.570
towards the unknown and you need to do that also with conviction and at

458
00:25:33.670 --> 00:25:36.930
speed. And this is not how normally product development works.

459
00:25:37.350 --> 00:25:39.970
So a couple of years back it was, "Okay, we have our cycles.

460
00:25:40.030 --> 00:25:43.370
We plan in quarters. Then there have the biweekly sprints," and so on.

461
00:25:43.470 --> 00:25:47.230
And now you don't know what's being launched in two weeks and three weeks,

462
00:25:47.290 --> 00:25:50.730
but it might change your roadmap completely and your teams need to get used to

463
00:25:50.770 --> 00:25:52.850
that kind of pace. And this is a mind shift change.

464
00:25:52.910 --> 00:25:57.790
<v 1>Yeah, that's a huge mind shift change. I want to pivot a little bit. Agents,</v>

465
00:25:57.850 --> 00:25:59.490
they surprise us every day. Dirk,

466
00:25:59.690 --> 00:26:01.470
when you all have been going through this process,

467
00:26:01.550 --> 00:26:05.970
has there been a moment where either an agent has surpassed your expectations or

468
00:26:06.010 --> 00:26:07.530
done something wildly unexpected?

469
00:26:07.950 --> 00:26:08.350
<v 3>Yeah. Yeah.</v>

470
00:26:08.350 --> 00:26:11.830
So probably many of you have built agents in their company also made that

471
00:26:11.870 --> 00:26:15.410
experience. So for us, it started, for example, when we built a promotion agent.

472
00:26:15.470 --> 00:26:19.930
So promotion is a pretty important topic when you run a commerce platform and we

473
00:26:19.990 --> 00:26:22.410
wanted to make the process easier for our customers. So we said, "Okay,

474
00:26:22.490 --> 00:26:23.990
let's agentify some of the steps,

475
00:26:24.070 --> 00:26:28.030
taking the UI part out of it." The surprising piece was when we then played

476
00:26:28.050 --> 00:26:31.010
around with that, already after a week after launching it,

477
00:26:31.490 --> 00:26:34.910
it had been able to create promotions that our platform before wasn't capable of

478
00:26:35.450 --> 00:26:40.170
because it was limited to UI flows and we have not had these UIs available for

479
00:26:40.270 --> 00:26:41.290
some complex kind of things.

480
00:26:41.350 --> 00:26:44.310
They had been in our backlog and the product team had been asked to do them,

481
00:26:44.370 --> 00:26:48.090
but it would have taken them weeks. But the agent doesn't need UI, right?

482
00:26:48.150 --> 00:26:51.010
So it just needs API access. You tell the agent, "Hey, this is my campaign.

483
00:26:51.070 --> 00:26:52.270
This is what I'm planning. This is my problem.

484
00:26:52.330 --> 00:26:55.730
Now help me optimize it." Could create it. And this, then,

485
00:26:55.830 --> 00:27:00.450
got us afterwards rethinking how we actually further develop our whole software

486
00:27:00.510 --> 00:27:01.290
stack going forward.

487
00:27:01.290 --> 00:27:04.190
<v 1>Oh my goodness. I'm curious, when you came upon that moment,</v>

488
00:27:04.550 --> 00:27:06.150
have you now thought about, "how do I scale this?

489
00:27:06.210 --> 00:27:09.570
How do I take this kind of accidental surprise that ended up being a really

490
00:27:09.610 --> 00:27:11.970
positive thing and try to find more opportunity for it?".

491
00:27:12.030 --> 00:27:15.330
<v 3>Yeah, absolutely. So, for us, it's all about, now, agent orchestration,</v>

492
00:27:15.690 --> 00:27:20.370
so to providing a platform to our merchants that actually help them run their

493
00:27:20.430 --> 00:27:22.170
business-not do their business, right?

494
00:27:22.230 --> 00:27:25.490
So instead of them doing the promotions or running analyzers and so on,

495
00:27:25.950 --> 00:27:29.430
being able to orchestrate any kind of first-party, or third-party,

496
00:27:29.630 --> 00:27:31.850
agent that are running across the commerce stack.

497
00:27:33.110 --> 00:27:35.810
And so we officially haven't announced that, right?

498
00:27:35.870 --> 00:27:37.510
So it's going live in a few months.

499
00:27:38.030 --> 00:27:40.590
So therefore it's a little bit of a sneak preview here,

500
00:27:40.950 --> 00:27:43.710
but this will be one of our big product launches in some of this year.

501
00:27:43.950 --> 00:27:46.270
<v 1>Okay. Incredible. All right. Vova,</v>

502
00:27:46.330 --> 00:27:49.650
I want to go back in the time machine back to 2024 again when you all were just

503
00:27:49.690 --> 00:27:50.530
starting this journey.

504
00:27:51.090 --> 00:27:54.430
I imagine there were lots of pieces of advice that you were getting at that

505
00:27:54.510 --> 00:27:56.210
time, but if you could think to yourself,

506
00:27:56.470 --> 00:28:00.490
what's one piece of conventional AI wisdom that you wish that you would have

507
00:28:00.510 --> 00:28:01.550
just thrown out the window?

508
00:28:02.250 --> 00:28:07.050
<v 2>So I wouldn't listen to the people who would</v>

509
00:28:07.110 --> 00:28:07.350
say,

510
00:28:07.350 --> 00:28:12.330
"You have to wait to see how the ecosystem will emerge." It's very easy

511
00:28:12.390 --> 00:28:14.930
to sit on the sidelines. "Look, you have things to do,

512
00:28:15.310 --> 00:28:17.770
you have features to release, you have products,

513
00:28:17.870 --> 00:28:22.150
existing products to take care of. Things will settle, dust will settle,

514
00:28:22.250 --> 00:28:26.470
then start hopping onto this journey." And

515
00:28:27.170 --> 00:28:31.870
this is very much conventional wisdom back in time and we decided to say,

516
00:28:32.030 --> 00:28:36.630
"Thank you, but no. We'll still approach it." Yeah.

517
00:28:36.750 --> 00:28:40.930
And it proved to be a really good investment because it also taught us.

518
00:28:42.750 --> 00:28:44.150
As an organization, as a company,

519
00:28:44.210 --> 00:28:45.730
even though we're not doing it from time to time,

520
00:28:45.790 --> 00:28:49.850
but that point in time was pivotal to do it again for the

521
00:28:52.290 --> 00:28:55.590
flexibility and speed in how you approach new opportunities that are coming up

522
00:28:55.630 --> 00:28:56.250
in the market.

523
00:28:56.250 --> 00:28:58.650
<v 1>Okay. Yeah. I know when we were chatting before, you mentioned,</v>

524
00:28:58.750 --> 00:29:01.810
"You have to be in the water to catch the wave." And that was like a big push

525
00:29:01.870 --> 00:29:02.703
for you all to make that decision.

526
00:29:03.520 --> 00:29:06.310
<v 2>Exactly. Yes. Yes. You have to be in the water, absolutely, to catch the wave.</v>

527
00:29:07.050 --> 00:29:07.430
By the way,

528
00:29:07.430 --> 00:29:11.610
I heard it-I'm a part of the trading community-and when you are trading stocks

529
00:29:11.670 --> 00:29:15.410
and things like that, or when you're investing, you need to have something,

530
00:29:15.650 --> 00:29:19.090
you cannot choose an ideal entry point, okay? And they say,

531
00:29:19.490 --> 00:29:22.090
"You have to be in the water to catch the wave.".

532
00:29:22.590 --> 00:29:26.210
<v 1>Okay. I love that. All right. In 30 seconds or less,</v>

533
00:29:26.310 --> 00:29:29.570
just to kind of close us out here, and Dirk, I'll start with you.

534
00:29:29.870 --> 00:29:33.910
Could you paint us a picture of what's your future ideal state for commercetools

535
00:29:33.990 --> 00:29:34.823
as a platform?

536
00:29:35.270 --> 00:29:35.630
<v 3>Yeah.</v>

537
00:29:35.630 --> 00:29:39.130
So I think we did a good job for the last 10 years on being the most modern

538
00:29:39.150 --> 00:29:42.830
platform in the enterprise, helping our customers to embrace all touchpoints.

539
00:29:42.990 --> 00:29:45.150
I think if we can do that for another 10 years,

540
00:29:45.510 --> 00:29:50.130
helping our customers to embrace all existing human-led and also all

541
00:29:50.230 --> 00:29:54.650
future agent-led touchpoints on one platform and making that all of them for

542
00:29:54.730 --> 00:29:59.090
them accessing easily, then I think I'm quite happy.

543
00:29:59.530 --> 00:30:00.363
<v 1>Love that.</v>

544
00:30:00.990 --> 00:30:05.090
<v 2>So I will speak on behalf of the user, not on behalf of the platform,</v>

545
00:30:05.150 --> 00:30:08.410
and we'll explain the role of the platform through the user need.

546
00:30:08.810 --> 00:30:11.970
So I see that our users, SMBs,

547
00:30:12.730 --> 00:30:15.570
either small or medium-size or really big,

548
00:30:16.150 --> 00:30:20.880
should have a solid representation in the new agentic

549
00:30:21.000 --> 00:30:25.740
commerce world where they have an agent against which others can transact.

550
00:30:26.700 --> 00:30:30.340
And they have it available and reflecting their brand voice,

551
00:30:30.520 --> 00:30:32.360
and reflecting their code of conduct,

552
00:30:33.020 --> 00:30:37.740
and suggesting all kinds of promotions and other things to buyers and

553
00:30:37.800 --> 00:30:42.100
shoppers in the way that the SMB, the business owner,

554
00:30:42.180 --> 00:30:43.740
doesn't have to lift a finger.

555
00:30:44.540 --> 00:30:49.240
If we can get there for the majority of the shopping experience,

556
00:30:49.840 --> 00:30:54.640
either it's retail or its vertical SaaS with booking services,

557
00:30:55.280 --> 00:30:58.560
I think our merchants,

558
00:30:58.620 --> 00:31:03.470
our customers will be in a good place and we as platforms will also be in a

559
00:31:03.510 --> 00:31:04.570
good place as a result.

560
00:31:04.770 --> 00:31:08.470
<v 1>Okay, fantastic. Well, I think that is a perfect place to leave it.</v>

561
00:31:08.850 --> 00:31:11.830
Thank you all so much for your time. We hope you enjoy the rest of Sessions.

