﻿WEBVTT

1
00:00:10.020 --> 00:00:14.960
<v 0>Hello, hello. How is everybody? Good. Sessions Day 2,</v>

2
00:00:15.220 --> 00:00:19.720
heading into post-lunch session or pre-lunch session. Hey everybody,

3
00:00:19.780 --> 00:00:23.220
my name is Tyler Bryson, and I lead revenue for Stripe here in the Americas.

4
00:00:23.760 --> 00:00:27.260
I'm also the leader for all of our product sales globally.

5
00:00:27.880 --> 00:00:31.100
And it's just an honor to have you all here because hopefully we're all going to

6
00:00:31.120 --> 00:00:35.200
have a chance to talk about this phenomenon that we're all dealing with of the

7
00:00:35.280 --> 00:00:36.780
agentic front office,

8
00:00:37.180 --> 00:00:41.740
this way of rethinking the way we need to engage our users, our customers,

9
00:00:41.820 --> 00:00:44.220
to grow. And it's something, of course,

10
00:00:44.280 --> 00:00:47.980
that's a huge part of Stripe's conversation internally every day.

11
00:00:48.540 --> 00:00:52.280
We support over five million businesses with many different needs.

12
00:00:52.700 --> 00:00:57.000
We're seeing about $2 trillion of volume as you've heard throughout the economy,

13
00:00:57.560 --> 00:01:01.220
and we're seeing incredible patterns. And we're thinking every day,

14
00:01:01.220 --> 00:01:01.220
"How is our experience from that first time startup to the largest enterprise in

15
00:01:01.220 --> 00:01:01.833
the world?"

16
00:01:06.340 --> 00:01:07.720
Ian, we were just talking about this.

17
00:01:07.720 --> 00:01:07.720
"And how do we use agentic technologies to improve the experiences of our

18
00:01:07.720 --> 00:01:08.333
users?"

19
00:01:13.420 --> 00:01:17.660
And that's what we want to explore today. So to help me do that, I'm glad to,

20
00:01:17.940 --> 00:01:22.860
excited to, introduce you to Ian Kahn, a partner at PwC.

21
00:01:23.200 --> 00:01:26.040
He leads their commercial and service excellence practice,

22
00:01:26.400 --> 00:01:29.380
which is right at the forefront of the things that we're talking about,

23
00:01:29.380 --> 00:01:31.180
making it real. So let's welcome up Ian.

24
00:01:35.780 --> 00:01:37.180
<v 1>Thanks, Tyler. Great to be here.</v>

25
00:01:37.700 --> 00:01:41.840
<v 0>So a great thing about PwC and working with Ian is</v>

26
00:01:42.700 --> 00:01:45.560
not only are we working to tackle these problems together,

27
00:01:45.640 --> 00:01:49.880
we're doing it in a partnership. And as you know, Stripe

28
00:01:51.760 --> 00:01:55.540
has many capabilities about enabling growth for our users,

29
00:01:55.760 --> 00:02:00.600
but we need help from partners like PwC to help take

30
00:02:00.620 --> 00:02:04.460
that from products and solutions to real transformation.

31
00:02:05.080 --> 00:02:07.060
And so that's why we're so glad to have you here, Ian.

32
00:02:07.300 --> 00:02:09.400
<v 1>It's great to be here. We're a bit of an odd couple though.</v>

33
00:02:11.100 --> 00:02:15.100
We were talking about this. So Stripe is 15 years young, is that right?

34
00:02:15.200 --> 00:02:16.033
<v 0>15. Yep.</v>

35
00:02:16.440 --> 00:02:21.220
<v 1>And PwC is 175-year-old partnership.</v>

36
00:02:23.500 --> 00:02:24.860
<v 0>And changing fast every day.</v>

37
00:02:25.220 --> 00:02:28.180
<v 1>I know. But I think we'll get into this conversation.</v>

38
00:02:28.260 --> 00:02:32.120
I was reflecting a little bit, just to go off script.

39
00:02:32.120 --> 00:02:32.173
<v 0>Yeah.</v>

40
00:02:32.400 --> 00:02:35.080
<v 1>And it's like a collision of multiple forces.</v>

41
00:02:35.580 --> 00:02:39.320
You have innovators colliding with scale players,

42
00:02:39.600 --> 00:02:41.280
and there's so much happening right now.

43
00:02:41.920 --> 00:02:44.540
And I think this whole conversation about the agentic front office is,

44
00:02:44.580 --> 00:02:48.380
going forward, like what wins? How do we need to adapt?

45
00:02:48.540 --> 00:02:52.100
What do we need to do to win in this new world?

46
00:02:52.860 --> 00:02:57.300
<v 0>In Stripe's annual letter, you may have, if you've read it,</v>

47
00:02:57.360 --> 00:03:01.320
there's a section about what we call the "sorting machine." And it's this idea

48
00:03:01.420 --> 00:03:05.740
that this capitalist system is constantly sorting and choosing winners and

49
00:03:05.780 --> 00:03:08.040
losers. And one of the things, Ian,

50
00:03:08.080 --> 00:03:12.160
that we call out or we're seeing as a pattern right now is that the sorting

51
00:03:12.180 --> 00:03:14.020
machine is working faster and faster,

52
00:03:14.560 --> 00:03:18.860
and there's becoming this real bifurcation of winners and losers right now,

53
00:03:19.160 --> 00:03:22.480
where there are organizations that are winning, taking share,

54
00:03:22.940 --> 00:03:26.920
and others that are dormant and really struggling. So with that as a foundation,

55
00:03:27.020 --> 00:03:30.220
Ian, what's happening? Why are we having this kind of shift,

56
00:03:30.280 --> 00:03:32.060
and who's winning with profits and who isn't?

57
00:03:32.360 --> 00:03:33.193
<v 1>Yeah. I mean,</v>

58
00:03:33.220 --> 00:03:37.600
the shift has been unbelievable and been kind of

59
00:03:37.940 --> 00:03:41.580
talked about extensively in all of the sessions this week. And

60
00:03:43.420 --> 00:03:48.280
I think that the debate about the relevance and the strategic priority

61
00:03:48.360 --> 00:03:51.620
around the AI agenda has sort of been, to a large degree,

62
00:03:51.680 --> 00:03:56.660
it's been settled for most organizations, but at the same time,

63
00:03:59.140 --> 00:04:03.540
the question is still outstanding around value capture, right?

64
00:04:03.720 --> 00:04:05.500
So today,

65
00:04:06.100 --> 00:04:10.460
our research suggests that while the vast majority of companies are prioritizing

66
00:04:11.080 --> 00:04:15.300
AI-powered transformation as a top three agenda, still,

67
00:04:15.380 --> 00:04:20.240
only 75% of the companies that we study

68
00:04:20.500 --> 00:04:23.440
are really not capturing any sort of meaningful ROI.

69
00:04:23.500 --> 00:04:25.180
And that's sort of this value gap,

70
00:04:25.680 --> 00:04:30.600
that's the disparity that jumps out from the Stripe research, the bifurcation,

71
00:04:31.420 --> 00:04:34.100
as you say. And I think there are a number of reasons for that.

72
00:04:35.020 --> 00:04:38.720
I might just sort of paint a quick concept for a second.
The title of the

73
00:04:38.740 --> 00:04:40.540
session is talking about agentic front office.

74
00:04:40.740 --> 00:04:45.520
I was at another session yesterday with your chief revenue officer for

75
00:04:45.600 --> 00:04:47.440
AI, Maia, and the CEO of Vercel,

76
00:04:47.500 --> 00:04:48.920
and they were kind of talking about the same thing.

77
00:04:49.780 --> 00:04:52.580
They were talking about this massive shift that's happening in the market,

78
00:04:53.100 --> 00:04:54.660
traditional commercial models,

79
00:04:54.720 --> 00:04:57.980
sort of product-led growth to sales-led growth to agentic-led growth,

80
00:04:58.040 --> 00:05:02.380
and this shift is happening. And when we talk about agenetic front office,

81
00:05:03.060 --> 00:05:04.080
one question I get sometimes is, "Well, what do you mean by 'front office?'"

82
00:05:06.580 --> 00:05:10.680
And so this is not a universal term, but for us,

83
00:05:10.680 --> 00:05:13.960
"front office," it's the collection of functions that are designed to enable

84
00:05:13.980 --> 00:05:17.640
that end-to-end customer journey. And a lot of organizations today,

85
00:05:17.700 --> 00:05:18.740
it's just very fragmented.

86
00:05:19.600 --> 00:05:24.580
And the "agentic front office" is what happens when you reimagine those

87
00:05:24.600 --> 00:05:26.640
customer facing functions, that customer journey,

88
00:05:26.700 --> 00:05:29.400
when you understand that your customers are now engaging with you in very

89
00:05:29.440 --> 00:05:31.520
different ways, using their own agents,

90
00:05:31.580 --> 00:05:35.460
and you have to evolve your model in order to meet them where they are and in

91
00:05:35.520 --> 00:05:39.440
order to unlock the growth opportunities.
I think the bifurcation reflects the

92
00:05:39.500 --> 00:05:42.140
fact that some companies are doing that very well right now,

93
00:05:42.680 --> 00:05:45.540
and they're growing at a much higher pace. We see that in the Stripe data,

94
00:05:45.960 --> 00:05:48.020
the AI leaders are outgrowing everybody else.

95
00:05:48.320 --> 00:05:49.980
The other companies that haven't gotten there yet,

96
00:05:51.080 --> 00:05:52.720
I think they've got a short window to catch up.

97
00:05:53.640 --> 00:05:55.260
<v 0>Great. Yeah.</v>

98
00:05:57.160 --> 00:06:00.940
And if you were in John's session on the economy and economic models,

99
00:06:01.120 --> 00:06:05.900
it's clear that this diffusion is not going to take as long as the diffusion of

100
00:06:05.940 --> 00:06:09.300
electricity. It's diffusing fast. We've got to be ready.

101
00:06:09.980 --> 00:06:11.100
And in most cases,

102
00:06:11.680 --> 00:06:16.040
you've tried to talk about this idea that it's the operating model that

103
00:06:16.420 --> 00:06:19.820
deserves the AI, not take what we have and throw AI on top.

104
00:06:20.520 --> 00:06:23.120
<v 1>That's a huge mistake to do that. Yeah. So</v>

105
00:06:25.360 --> 00:06:30.280
most front office sort of functions-step back-I'm talking about marketing and

106
00:06:30.340 --> 00:06:32.480
sales and service, maybe pricing functions.

107
00:06:33.120 --> 00:06:34.840
At a lot of the organizations that we study,

108
00:06:36.340 --> 00:06:38.860
reality is these are functional silos.

109
00:06:39.380 --> 00:06:41.660
They're designed to perform specific tasks.

110
00:06:42.540 --> 00:06:46.150
They often perform those tasks with high degrees of proficiency.

111
00:06:47.010 --> 00:06:51.430
And what we find is that the deployment of AI within those

112
00:06:51.460 --> 00:06:54.900
silos, it speeds things up in those silos,

113
00:06:55.400 --> 00:07:00.400
but it doesn't address the friction points or the gaps that have existed between

114
00:07:00.430 --> 00:07:01.710
those silos for a long time.

115
00:07:02.390 --> 00:07:06.370
The inability for a company to properly

116
00:07:07.230 --> 00:07:11.810
transition that qualified lead from marketing into sales with a

117
00:07:11.890 --> 00:07:15.790
very sort of tailored approach that meets the customer where they are,

118
00:07:15.850 --> 00:07:20.130
the handoff between sales and service that lacks context and leaves the customer

119
00:07:20.170 --> 00:07:24.470
feeling frustrated. We think that

120
00:07:27.070 --> 00:07:31.790
value leaks from these fragmented processes slowly,

121
00:07:31.910 --> 00:07:36.810
quietly, but actually it's pretty significant.
And that sort of leaky,

122
00:07:38.450 --> 00:07:41.970
that problem of value leakage is really significant. And so

123
00:07:43.870 --> 00:07:47.950
what the agentic front office really represents to us is it represents a pretty

124
00:07:48.030 --> 00:07:51.890
significant shift of looking end to end at the customer journey and redesigning

125
00:07:52.470 --> 00:07:55.350
that commercial model in a very, very integrated way.

126
00:07:55.410 --> 00:07:58.670
The functional silos need to disappear.

127
00:07:58.730 --> 00:08:01.370
At least your customer can't know that they're there.

128
00:08:02.330 --> 00:08:02.490
<v 0>Yeah.</v>

129
00:08:02.490 --> 00:08:06.120
And you said that there were some three different moves companies should take.

130
00:08:06.320 --> 00:08:07.960
Do you want to outline those or...

131
00:08:08.840 --> 00:08:13.640
<v 1>Yeah. Yeah. So I mean, as we partner with organizations and think about</v>

132
00:08:16.410 --> 00:08:19.490
unlocking the growth potential that exists, first of all,

133
00:08:20.560 --> 00:08:22.490
I think you got to step back and look at

134
00:08:25.280 --> 00:08:26.880
the way you're approaching the customer.

135
00:08:28.480 --> 00:08:33.280
Very few companies actually have an executive that is responsible for

136
00:08:33.600 --> 00:08:36.000
end-to-end customer experience.

137
00:08:36.880 --> 00:08:41.570
And so starting there and identifying the critical customer journeys

138
00:08:42.920 --> 00:08:46.920
and starting to understand that in the context of your business model,

139
00:08:47.040 --> 00:08:50.800
maybe in your industry, these customer journeys, they're different now.

140
00:08:51.000 --> 00:08:55.800
The customer is starting with some sort of AI-powered discovery process that's

141
00:08:55.880 --> 00:08:56.713
often-.

142
00:08:56.760 --> 00:08:58.520
<v 0>They know your content better than you do sometimes.</v>

143
00:08:58.830 --> 00:08:59.720
<v 1>100%, 100%.</v>

144
00:09:00.520 --> 00:09:03.360
<v 0>We've experienced where our users, our customers,</v>

145
00:09:03.440 --> 00:09:08.160
are so well prepped before we even have our first sales conversation that I've

146
00:09:08.160 --> 00:09:09.560
had to challenge my sales: "Uplevel, people. Like, uplevel.

147
00:09:09.560 --> 00:09:09.560
They've come to our site, they've read,

148
00:09:09.560 --> 00:09:10.153
they've understood it's about something more.".

149
00:09:35.040 --> 00:09:35.040
<v 1>Back to the sales-and you run a high performing sales organization-it's the What</v>

150
00:09:35.040 --> 00:09:35.040
Got You Here Won't Get You There kind of conversation because for a lot of

151
00:09:35.040 --> 00:09:35.040
high-performing sellers that have had very successful careers,

152
00:09:35.040 --> 00:09:37.520
it's sometimes a difficult conversation to say, "Actually,

153
00:09:38.400 --> 00:09:41.320
the way I've been approaching my job as a sales executive,

154
00:09:42.650 --> 00:09:44.270
that's not going to work going forward because the customer has changed their

155
00:09:44.290 --> 00:09:45.123
behavior.

156
00:09:45.680 --> 00:09:48.920
They don't want to engage with us in the same way." And so I think the three

157
00:09:48.920 --> 00:09:50.560
moves, just in summary, are: one,

158
00:09:51.650 --> 00:09:56.560
we have to reorient away from these sort of functionally focused approaches

159
00:09:56.760 --> 00:10:00.840
to this end-to-end customer experience design-led approach, one. Two,

160
00:10:02.160 --> 00:10:02.993
it has to be

161
00:10:04.830 --> 00:10:08.030
intelligence- and data-powered, right?

162
00:10:08.090 --> 00:10:11.710
So I think your customer data is one of your most valuable assets.

163
00:10:11.770 --> 00:10:12.990
You've got to get the house in order,

164
00:10:13.590 --> 00:10:18.230
you have to layer intelligence on top of that-agents that have the

165
00:10:18.270 --> 00:10:22.470
ability to sense and properly interpret customer intent,

166
00:10:23.110 --> 00:10:27.570
agents that have the ability to initiate and execute actions

167
00:10:27.610 --> 00:10:29.850
increasingly in autonomous fashion,

168
00:10:30.990 --> 00:10:35.670
and also agents that have the ability to read all of the

169
00:10:35.770 --> 00:10:39.710
signals in a way that humans struggle to do

170
00:10:40.690 --> 00:10:41.210
and learn,

171
00:10:41.210 --> 00:10:46.170
right?
The power of what we think of the concept of a commercial brain in your

172
00:10:46.230 --> 00:10:47.063
organization,

173
00:10:47.570 --> 00:10:50.750
do you have a data and intelligence layer that gives you the ability to

174
00:10:50.830 --> 00:10:55.090
continuously learn and serve your customer in a very tailored way using what we

175
00:10:55.130 --> 00:10:58.030
think of as "privileged insights?" And then, look,

176
00:10:58.090 --> 00:11:02.830
the last point is you have to redesign and reorchestrate the way work happens.

177
00:11:02.890 --> 00:11:06.890
Your jobs are changing. And this is the change management story,

178
00:11:07.010 --> 00:11:09.450
but looking at all of your roles and thinking, "Look, the job has changed.

179
00:11:09.450 --> 00:11:09.450
How do your sellers and your marketers and your service representatives,

180
00:11:09.450 --> 00:11:09.450
how are they leveraging AI to do their jobs differently and to serve the

181
00:11:09.450 --> 00:11:09.923
customer at a higher level?"

182
00:11:21.650 --> 00:11:23.790
And that's the opportunity. So the three things, again,

183
00:11:23.850 --> 00:11:27.210
it's end-to-end customer experience design-led. You've got to pick that up,

184
00:11:28.150 --> 00:11:30.070
building out what we think of as the "commercial brain"-your data and your

185
00:11:30.070 --> 00:11:30.070
intelligence layer.

186
00:11:30.070 --> 00:11:30.070
And then kind of redesigning your jobs and optimizing your workforce.

187
00:11:30.070 --> 00:11:30.843
Those are probably the three pillars that we need to focus on.

188
00:11:41.790 --> 00:11:45.650
<v 0>And I would just say in each of those, Stripe's on our own journey to do that.</v>

189
00:11:45.750 --> 00:11:47.910
I would say if you came to Stripe now and looked at my team,

190
00:11:48.810 --> 00:11:51.470
you'd see our AI strategy for SDR function,

191
00:11:51.590 --> 00:11:56.410
our AI strategy for customer support, our AI strategy for customer success.

192
00:11:57.030 --> 00:12:01.330
And what I'm realizing is like each of those people who are touching that user

193
00:12:01.590 --> 00:12:03.910
actually needs context of everything that's going on.

194
00:12:04.050 --> 00:12:04.770
<v 1>100%.</v>

195
00:12:04.770 --> 00:12:05.990
<v 0>And that means, like you said,</v>

196
00:12:06.070 --> 00:12:09.410
getting our data in order to a place where all of these systems can be

197
00:12:09.470 --> 00:12:14.470
interrogated quickly. And we've been building systems for a lot of years,

198
00:12:14.530 --> 00:12:19.530
but this universal dashboard is really just this intelligence now that's making

199
00:12:19.570 --> 00:12:23.850
it happen. So great insights, Ian. I appreciate it. So, Ian,

200
00:12:24.370 --> 00:12:27.730
where's it actually working? You're in boardrooms,

201
00:12:29.010 --> 00:12:33.150
you're making pitches right along with CROs, pitching transformation.

202
00:12:33.250 --> 00:12:34.250
Where is it working right now?

203
00:12:34.630 --> 00:12:37.650
<v 1>Yeah. I mean, look, we're seeing early success stories.</v>

204
00:12:39.070 --> 00:12:43.350
One I go back to-I'm going to reference the Maia's presentation yesterday for

205
00:12:43.390 --> 00:12:45.650
anybody that was in the room. I mean,

206
00:12:45.830 --> 00:12:49.150
you see AI leaders emerging right now,

207
00:12:49.250 --> 00:12:51.670
growing at incredible rates.

208
00:12:51.670 --> 00:12:55.870
That's a pretty good signal that something is working incredibly well.

209
00:12:56.370 --> 00:13:01.030
And as a 175-year-old global network of firms with a half a

210
00:13:01.110 --> 00:13:03.010
million employees,

211
00:13:03.850 --> 00:13:06.130
I'm jealous of some of the smaller companies that are,

212
00:13:06.890 --> 00:13:09.370
they're incredibly nimble. They lack the legacy baggage.

213
00:13:09.450 --> 00:13:10.930
They can get things done very quickly.

214
00:13:11.030 --> 00:13:14.270
And so that speed is an advantage in a lot of ways.

215
00:13:14.690 --> 00:13:19.510
But also you see big organizations making the change and making

216
00:13:19.570 --> 00:13:20.550
moves as well. I think

217
00:13:22.750 --> 00:13:25.670
one thing that we're seeing in the companies that we've studied, and, again,

218
00:13:25.730 --> 00:13:27.990
you kind of have this group of leaders that are emerging.

219
00:13:28.430 --> 00:13:31.470
It's like 20% of the companies we study are actually,

220
00:13:32.030 --> 00:13:36.170
they're seeing massive value capture from their AI deployment.
And where it's

221
00:13:36.230 --> 00:13:38.910
working is where you have an organization that has a focused strategy.

222
00:13:39.510 --> 00:13:43.510
They've picked key areas of the business where they see opportunities,

223
00:13:43.530 --> 00:13:47.590
and they focus on that customer and they really implement in a thoughtful way,

224
00:13:47.690 --> 00:13:50.510
kind of using those three pillars that I outlined before.

225
00:13:50.870 --> 00:13:54.790
And I think when you do that well, you have the ability to create value very,

226
00:13:54.850 --> 00:13:55.683
very quickly.

227
00:13:58.450 --> 00:14:02.630
<v 0>I think I read in the notes that you had some success with the global consumer</v>

228
00:14:02.670 --> 00:14:05.110
goods company that was using Stripe at one layer,

229
00:14:05.170 --> 00:14:09.070
but the data wasn't being connected to an intelligence.

230
00:14:09.390 --> 00:14:13.330
<v 1>So I know the story you're talking about, and it's a pretty good one because</v>

231
00:14:15.330 --> 00:14:18.450
we initially picked it up in completely the wrong way. And so,

232
00:14:20.770 --> 00:14:24.790
this is a consumer brand that you all interact with on a daily basis,

233
00:14:25.530 --> 00:14:27.250
very large global organization.

234
00:14:28.270 --> 00:14:30.630
They came to us with a pretty common pain point.

235
00:14:31.430 --> 00:14:36.410
The pain point was they had operational costs

236
00:14:38.110 --> 00:14:41.550
that were growing, especially around their customer service function.

237
00:14:42.610 --> 00:14:45.890
Not only were the costs growing, but they were getting

238
00:14:47.710 --> 00:14:50.310
a high rate of customer complaints,

239
00:14:51.010 --> 00:14:55.350
and they felt like their service function was broken and needed to be fixed.

240
00:14:55.430 --> 00:14:58.410
One of the key metrics they looked at was average handle time. And so,

241
00:14:58.410 --> 00:14:58.410
the kind of going-in hypothesis was,

242
00:14:58.410 --> 00:14:58.410
"Can we leverage AI to optimize the service function, take cost out,

243
00:14:58.410 --> 00:14:58.410
reduce handle time,

244
00:14:58.410 --> 00:14:58.410
and maybe deliver a better customer experience?" That was a decent thesis,

245
00:14:58.410 --> 00:14:58.983
but it was missing a bunch of critical points.

246
00:15:17.430 --> 00:15:19.510
<v 0>Back to the kind of like silo solved.</v>

247
00:15:22.210 --> 00:15:27.050
<v 1>The short version of the long story is the customers were really</v>

248
00:15:27.110 --> 00:15:30.490
frustrated with the ordering process and the ordering process,

249
00:15:31.430 --> 00:15:33.990
was highly time-consuming and it was very manual.

250
00:15:34.550 --> 00:15:38.590
And we thought there was an opportunity to leverage sort of AI ordering to

251
00:15:38.710 --> 00:15:41.610
optimize that, and to, also, when you do that well,

252
00:15:42.210 --> 00:15:44.150
you'll drive higher

253
00:15:46.310 --> 00:15:48.050
ticket size and ultimately growth.

254
00:15:48.870 --> 00:15:52.590
But that was actually an incomplete thought as well because the customers were

255
00:15:52.650 --> 00:15:57.350
actually increasingly coming through what we think of as and commonly described

256
00:15:57.370 --> 00:16:01.870
now as an "agentic commerce" sort of engagement model. And so,

257
00:16:02.670 --> 00:16:03.750
in the past, we were thinking, "Well,

258
00:16:03.750 --> 00:16:03.750
customers are coming through traditional channels,

259
00:16:03.750 --> 00:16:04.363
and they want to engage with us a certain way."

260
00:16:07.310 --> 00:16:11.610
And we built our front office and our service function in order to like serve

261
00:16:11.650 --> 00:16:13.230
them in that traditional pattern.

262
00:16:13.290 --> 00:16:17.270
But the pattern broke because the customer is now coming in through agentic

263
00:16:18.210 --> 00:16:21.230
channels.
They want to deal with us in a very different way.

264
00:16:21.630 --> 00:16:24.830
They don't just want to talk to a customer service representative.

265
00:16:24.890 --> 00:16:29.370
They actually want the ability to make smart decisions about ordering details,

266
00:16:29.410 --> 00:16:32.530
and then they want to transact. And so, by the way,

267
00:16:32.590 --> 00:16:34.430
that changes the job of the salesperson.

268
00:16:34.870 --> 00:16:37.070
So notice we started talking about customer service,

269
00:16:37.130 --> 00:16:40.070
but actually what we end up looking at is, well,

270
00:16:40.130 --> 00:16:42.110
now how do sales and service work together?

271
00:16:42.590 --> 00:16:46.190
And if the salesperson used to spend all this time on the ordering process,

272
00:16:46.250 --> 00:16:48.010
but now that's being done by AI,

273
00:16:48.430 --> 00:16:51.410
it really changes my end-to-end thinking around the whole front office,

274
00:16:51.470 --> 00:16:54.890
not to mention there's a marketing story. So when you pull these threads,

275
00:16:54.950 --> 00:16:55.930
you may start with,

276
00:16:56.270 --> 00:16:59.130
"I've got a particular pain point in my service organization:

277
00:16:59.630 --> 00:17:02.130
handle time is too high." What you get to is-.

278
00:17:02.150 --> 00:17:03.330
<v 0>Connected to something else.</v>

279
00:17:03.710 --> 00:17:08.110
<v 1>And by the way, we're unlocking growth and taking out costs at the same time.</v>

280
00:17:08.490 --> 00:17:12.130
And Stripe is a key partner because agentic commerce is,

281
00:17:12.370 --> 00:17:16.710
it's one of the tools in our toolkit here as we reimagine the end-to-end agentic

282
00:17:16.750 --> 00:17:17.583
front office,

283
00:17:17.790 --> 00:17:22.710
but we think that agent commerce capability and obviously ability to convert

284
00:17:23.690 --> 00:17:27.870
at the point of transaction is essential and no one does it better and with more

285
00:17:27.910 --> 00:17:29.190
confidence than Stripe.

286
00:17:30.190 --> 00:17:34.790
<v 0>And one of the things that we hypothesize for you is this idea that</v>

287
00:17:34.910 --> 00:17:39.690
payment flows and their-people's interaction with their money is an actually,

288
00:17:40.170 --> 00:17:42.870
a critical experience that we've got to get right together.

289
00:17:43.610 --> 00:17:48.370
And when that gets wrong, trust is lost, and we're down the wrong path. Okay.

290
00:17:49.170 --> 00:17:50.930
But, Ian, I want to get your thoughts though. So,

291
00:17:52.550 --> 00:17:56.910
some amazing companies in this room, running fast, do you suggest, "Hey,

292
00:17:57.850 --> 00:18:00.610
get started, do something." Or, "Oh no,

293
00:18:00.770 --> 00:18:05.390
I've got to pitch a two year transformation." What's the balance of like getting

294
00:18:05.410 --> 00:18:09.130
the right visibility as CROs in the room maybe and getting back to the board?

295
00:18:09.650 --> 00:18:12.310
How do you pitch this? You got to have some early wins. What are your thoughts?

296
00:18:13.110 --> 00:18:15.190
<v 1>Yeah. I mean, we get the sort of the two-year,</v>

297
00:18:15.270 --> 00:18:18.590
three-year transformation push a lot. And

298
00:18:20.470 --> 00:18:23.390
I wake up every morning feeling like we're not moving fast enough,

299
00:18:23.450 --> 00:18:28.090
and I'm sure many of you feel the same way. We don't have two years or a year

300
00:18:30.150 --> 00:18:32.510
to accomplish our objectives.

301
00:18:33.490 --> 00:18:35.510
We've got to break things down into smaller chunks.

302
00:18:36.130 --> 00:18:40.130
And so what I believe is that, with the right focus,

303
00:18:42.230 --> 00:18:47.050
you have the ability to move the needle at a much faster

304
00:18:47.110 --> 00:18:52.090
pace, right? So I think my advice is, when you look at your business model,

305
00:18:52.190 --> 00:18:55.130
if you think about the customer or the user that you're serving,

306
00:18:55.190 --> 00:18:57.950
and if you take the time to look end to end at that journey,

307
00:18:58.030 --> 00:19:00.090
what you might find and probably will find,

308
00:19:00.810 --> 00:19:03.370
is that there are gaps or seams

309
00:19:04.950 --> 00:19:09.710
in the way you're serving the customer from kind of the start of the journey or

310
00:19:10.090 --> 00:19:14.010
like what we think of as kind of what our marketing function is kind of focused

311
00:19:14.050 --> 00:19:17.910
on doing through the sales process, through the post-sales service.
And so,

312
00:19:17.990 --> 00:19:20.230
when you take that end to end, and you look at those journeys,

313
00:19:20.290 --> 00:19:24.650
you'll find the friction points, you'll find the opportunities for improvement.

314
00:19:24.710 --> 00:19:27.830
I think you pick one or more of those high-value opportunities,

315
00:19:27.890 --> 00:19:31.190
you go at it hard, you ought to be able to move the needle in 12 weeks or less.

316
00:19:31.290 --> 00:19:35.450
We think getting started with focus and moving fast, that's your wedge,

317
00:19:35.910 --> 00:19:38.930
is the way you build momentum and the way you start to drive the transformation

318
00:19:38.950 --> 00:19:42.990
that we think of as the shift to the agentic front office.

319
00:19:43.450 --> 00:19:46.010
So the clock speed has to be much faster than multiple years.

320
00:19:46.370 --> 00:19:46.570
<v 0>Yeah.</v>

321
00:19:46.570 --> 00:19:49.950
When you hear-I don't know if some of you were here yesterday for the Sam Altman

322
00:19:49.990 --> 00:19:53.050
discussion, but it's like, "What is your planning horizon?" He said, "Well,

323
00:19:53.350 --> 00:19:55.670
I'm planning 10 years for energy and data centers,

324
00:19:56.270 --> 00:20:00.950
but we've got to move so quickly now." I think he said that they're planning at

325
00:20:00.990 --> 00:20:05.310
most like two years ahead. So, I think most of our ideas now,

326
00:20:05.310 --> 00:20:07.250
to make agentic a growth engine,

327
00:20:07.450 --> 00:20:11.730
not just the old sales funnel, into something different,

328
00:20:11.910 --> 00:20:13.880
we've got to have 12-week kind of turnarounds.

329
00:20:13.940 --> 00:20:14.490
<v 1>You do.</v>

330
00:20:14.490 --> 00:20:17.470
<v 0>The world is just like expecting that from us.</v>

331
00:20:17.470 --> 00:20:17.470
<v 1>Yeah.</v>

332
00:20:17.470 --> 00:20:21.360
<v 0>And I think we're seeing that. I mean, I'll just share a few examples at Stripe.</v>

333
00:20:21.820 --> 00:20:25.040
We, for the first time, are launching our first agent-led,

334
00:20:25.120 --> 00:20:28.990
entirely agent-led campaigns and outreaches out to you.

335
00:20:29.460 --> 00:20:31.200
I don't know if any of you've experienced that yet,

336
00:20:32.320 --> 00:20:34.880
but our early results are really promising,

337
00:20:35.100 --> 00:20:39.700
which just means that we've opened a dialogue with the user in a sustained

338
00:20:39.710 --> 00:20:44.060
agentic conversation, where we're able to assess interest,

339
00:20:44.280 --> 00:20:45.210
share insights,

340
00:20:45.780 --> 00:20:50.100
and basically prequalify a lot of the work before it even got to our SDR

341
00:20:50.230 --> 00:20:52.540
function. And again,

342
00:20:53.020 --> 00:20:56.580
we think we're actually improving the experience because these agents are really

343
00:20:56.680 --> 00:21:00.600
accurate. I mean, there's a lot of concern about hallucination.

344
00:21:01.580 --> 00:21:04.560
Believe me, real people hallucinate in some ways, as you know.

345
00:21:05.020 --> 00:21:07.660
So we're seeing accuracy, we're seeing interest,

346
00:21:07.880 --> 00:21:12.080
and that was a 12-week sprint to get that moving. And I've got to run,

347
00:21:12.080 --> 00:21:13.990
with the breadth of Stripe's product offerings,

348
00:21:13.990 --> 00:21:17.600
I'm trying to run 12 different motions or campaigns every

349
00:21:17.680 --> 00:21:21.100
quarter-hopefully not all to you at the same time,

350
00:21:21.960 --> 00:21:23.960
so don't throw eggs at me yet.

351
00:21:23.960 --> 00:21:28.100
But

352
00:21:28.100 --> 00:21:28.100
we

353
00:21:28.100 --> 00:21:28.100
want

354
00:21:28.100 --> 00:21:28.100
that

355
00:21:28.100 --> 00:21:28.100
to

356
00:21:28.100 --> 00:21:28.100
be

357
00:21:28.100 --> 00:21:28.100
a

358
00:21:28.100 --> 00:21:28.100
very

359
00:21:28.100 --> 00:21:28.100
natural

360
00:21:28.100 --> 00:21:28.100
experience.

361
00:21:28.100 --> 00:21:28.100
"Oh,

362
00:21:28.100 --> 00:21:28.100
it's

363
00:21:28.100 --> 00:21:28.100
Stripe.

364
00:21:28.100 --> 00:21:28.100
Yeah,

365
00:21:28.100 --> 00:21:28.100
I

366
00:21:28.100 --> 00:21:28.100
trust

367
00:21:28.100 --> 00:21:28.100
Stripe.

368
00:21:28.100 --> 00:21:28.100
What

369
00:21:28.100 --> 00:21:28.100
do

370
00:21:28.100 --> 00:21:28.100
we

371
00:21:28.100 --> 00:21:28.100
want

372
00:21:28.100 --> 00:21:28.100
to...

373
00:21:28.100 --> 00:21:28.100
Great,

374
00:21:28.100 --> 00:21:28.100
I

375
00:21:28.100 --> 00:21:28.100
didn't

376
00:21:28.100 --> 00:21:28.100
know

377
00:21:28.100 --> 00:21:28.100
that

378
00:21:28.100 --> 00:21:28.100
was

379
00:21:28.100 --> 00:21:28.100
available.

380
00:21:28.100 --> 00:21:28.100
Oh,

381
00:21:28.100 --> 00:21:28.100
you

382
00:21:28.100 --> 00:21:28.100
think

383
00:21:28.100 --> 00:21:28.100
that

384
00:21:28.100 --> 00:21:28.100
I

385
00:21:28.100 --> 00:21:28.100
could

386
00:21:28.100 --> 00:21:28.100
have

387
00:21:28.100 --> 00:21:28.100
an

388
00:21:28.100 --> 00:21:28.100
improvement

389
00:21:28.100 --> 00:21:28.100
in

390
00:21:28.100 --> 00:21:28.100
my

391
00:21:28.100 --> 00:21:28.100
operations?

392
00:21:28.100 --> 00:21:28.100
Yes,

393
00:21:28.100 --> 00:21:28.100
I'd

394
00:21:28.100 --> 00:21:28.100
like

395
00:21:28.100 --> 00:21:28.100
to

396
00:21:28.100 --> 00:21:28.100
learn

397
00:21:28.100 --> 00:21:28.100
more."

398
00:21:28.100 --> 00:21:28.100
What

399
00:21:28.100 --> 00:21:28.100
do

400
00:21:28.100 --> 00:21:28.100
you

401
00:21:28.100 --> 00:21:28.100
think?

402
00:21:38.500 --> 00:21:41.040
<v 1>I think we all need to be... First of all, I think you're leading the</v>

403
00:21:43.800 --> 00:21:46.340
way. That sounds leading edge to me, Tyler,

404
00:21:46.400 --> 00:21:49.880
and I think we'd all love to hear more about that story and the results,

405
00:21:50.660 --> 00:21:52.980
and learn together, but

406
00:21:55.280 --> 00:21:57.880
it's exactly the direction that we all need to be going in.

407
00:21:57.960 --> 00:22:01.640
Even for our business, again, 175-year-old partnership,

408
00:22:02.660 --> 00:22:04.660
50% of that is consulting,

409
00:22:04.720 --> 00:22:09.520
but we have big tax and advisory M&amp;A and audit businesses.

410
00:22:09.940 --> 00:22:13.990
We're thinking hard about what does the future look like when our clients...

411
00:22:15.160 --> 00:22:18.540
They're engaging with us through purchasing agents, right?

412
00:22:19.520 --> 00:22:24.380
Majority of B2B buyers are now already using agents in their purchasing journey,

413
00:22:25.100 --> 00:22:25.933
and

414
00:22:27.220 --> 00:22:32.060
they want to be able to engage a firm like PwC and consume our

415
00:22:32.140 --> 00:22:35.580
services in a completely self-service,

416
00:22:35.760 --> 00:22:37.360
agent-driven model

417
00:22:38.940 --> 00:22:42.880
that is very different from what we've done traditionally.

418
00:22:42.960 --> 00:22:46.960
So we're on the same journey, and I think it goes back to that,

419
00:22:47.620 --> 00:22:51.160
the signals that you mentioned and the learning, the importance of that.

420
00:22:54.460 --> 00:22:54.460
We call it the "commercial brain," but this,

421
00:22:54.460 --> 00:22:58.040
getting your data organized with the intelligence layer and making sure that as

422
00:22:58.100 --> 00:23:02.740
you deploy these agents, you do it with guardrails. We talk a lot about trust,

423
00:23:02.800 --> 00:23:04.100
but also the instrumentation,

424
00:23:04.160 --> 00:23:07.360
so you are reading the signals and learning so you can optimize over time.

425
00:23:07.920 --> 00:23:10.560
Because, for sure, we're going to deploy agents...

426
00:23:11.580 --> 00:23:14.940
We'll do lots of great work on design and testing and whatnot,

427
00:23:15.020 --> 00:23:17.280
but we're not going to get it right 100% of the time.

428
00:23:17.340 --> 00:23:20.660
I think one of the key disciplines that you have to have is governance and

429
00:23:20.680 --> 00:23:21.760
continuous improvement.

430
00:23:22.520 --> 00:23:26.060
Your customer is not going to give you a long leash or have much tolerance for

431
00:23:27.820 --> 00:23:29.540
poor execution or bad experiences.

432
00:23:29.880 --> 00:23:32.960
<v 0>Yeah. Okay. So let me recap what we've covered before we wrap up. So,</v>

433
00:23:33.400 --> 00:23:37.380
there is a bifurcation happening, for sure. There are winners and losers,

434
00:23:37.380 --> 00:23:38.800
and they're emerging faster than ever.

435
00:23:39.380 --> 00:23:44.280
AI is one of the elements that's differentiating those organizations already.

436
00:23:45.360 --> 00:23:47.720
Some of them are AI companies that are growing really fast,

437
00:23:47.780 --> 00:23:51.140
but obviously that technology, those capabilities, are coming.

438
00:23:51.800 --> 00:23:55.860
Second thing we talked about, hey, it isn't just about throw AI out there;

439
00:23:56.220 --> 00:23:57.740
get back to the customer journey.

440
00:23:57.800 --> 00:24:00.540
And I think we've talked about customer journeys, at least I have, for many,

441
00:24:00.600 --> 00:24:05.520
many years, but now there's a new variable in the equation of like,

442
00:24:05.600 --> 00:24:07.580
okay, you thought you knew what the customer wanted,

443
00:24:08.140 --> 00:24:09.400
they want something different now.

444
00:24:09.660 --> 00:24:13.480
And turns out they don't want what you used to offer or the way that you engage

445
00:24:13.520 --> 00:24:18.520
them. Third step, find a process, find an area of that customer journey,

446
00:24:18.860 --> 00:24:21.340
get moving fast.

447
00:24:21.340 --> 00:24:24.220
How can they work with a PwC and a Stripe to make that happen?

448
00:24:26.900 --> 00:24:30.040
<v 1>Look, I think we all learn from each other. Conversations like this are good,</v>

449
00:24:30.120 --> 00:24:30.953
but

450
00:24:31.960 --> 00:24:36.900
every business needs to figure out what are the core capabilities

451
00:24:37.480 --> 00:24:39.780
that they have that create value for their customers.

452
00:24:39.840 --> 00:24:42.040
And then I think you look at everything else and you say, "Okay,

453
00:24:42.600 --> 00:24:47.560
how do I find partners that can do this thing for me maybe better than

454
00:24:47.760 --> 00:24:51.780
I can or can help me to go faster?" This agentic front office conversation,

455
00:24:51.840 --> 00:24:54.260
it's a huge transformation for most organizations.

456
00:24:55.720 --> 00:25:00.120
That's probably not the way you create value for your customers.

457
00:25:00.560 --> 00:25:03.740
And I think whether it's driving the change management or thinking about the

458
00:25:03.820 --> 00:25:08.360
architecture of the commercial brain or redesigning some of the jobs or

459
00:25:08.800 --> 00:25:13.640
leveraging a platform like Stripe to help you with the end-to-end monetization

460
00:25:15.660 --> 00:25:18.780
platforms that are required to grow your business,

461
00:25:19.320 --> 00:25:23.740
I think we all need to engage with partners to scale faster,

462
00:25:24.720 --> 00:25:27.700
to transform in more inspired ways.

463
00:25:27.700 --> 00:25:31.580
And I think those are the types of partnerships and relationships that we're all

464
00:25:32.440 --> 00:25:33.273
looking for.

465
00:25:34.740 --> 00:25:35.520
<v 0>We're grateful for that.</v>

466
00:25:35.520 --> 00:25:39.100
And I'll just throw in our point is we're not ripping and replacing anything

467
00:25:39.560 --> 00:25:40.393
right now.

468
00:25:40.620 --> 00:25:44.780
We are using the data that we have and exposing it in the commercial brain

469
00:25:45.020 --> 00:25:45.020
concept.

470
00:25:45.020 --> 00:25:45.853
<v 1>Yeah.</v>

471
00:25:46.100 --> 00:25:47.880
<v 0>And it's just unlocking so much.</v>

472
00:25:48.980 --> 00:25:51.360
So I mentioned agents earlier,

473
00:25:51.700 --> 00:25:55.200
it's actually just changing the way Stripe shows up better every single day,

474
00:25:55.660 --> 00:25:59.060
whatever the interaction point is. And we hope that you start to feel that,

475
00:25:59.740 --> 00:26:02.480
and we have long ways to go in that journey,

476
00:26:02.600 --> 00:26:04.800
but it's a bright opportunity ahead.

477
00:26:05.960 --> 00:26:10.640
And I'll just wrap by thanking you all for being on this journey with Stripe as

478
00:26:10.700 --> 00:26:14.120
we figure out this way. One of the concepts that we're working on,

479
00:26:14.200 --> 00:26:15.640
and you heard about it yesterday,

480
00:26:15.720 --> 00:26:20.520
is we know you need more of our data so that you can embed that into the

481
00:26:20.560 --> 00:26:22.140
intelligence of your processes.

482
00:26:22.200 --> 00:26:27.120
It's just got to get easier so that when your customer support teams or your

483
00:26:27.180 --> 00:26:30.000
CRO or your CFO needs insights and information,

484
00:26:30.500 --> 00:26:34.960
it's part of the intelligence of your agentic front office. Sound good?

485
00:26:35.600 --> 00:26:36.080
<v 1>Perfect.</v>

486
00:26:36.080 --> 00:26:38.480
<v 0>All right, Ian. Well, thank you so much for joining me. Everyone,</v>

487
00:26:38.560 --> 00:26:39.960
let's give Ian a round of applause.

488
00:26:43.540 --> 00:26:46.800
And I look forward to coming back and doing this again next year with even more

489
00:26:46.860 --> 00:26:49.420
stories of what's happening. Okay. Thanks, everybody.

