TRANSKRIP 🔗
WEBVTT
00:00:01.278 --> 00:00:04.879
AI needs a ground to stand on.
00:00:04.879 --> 00:00:08.900
Why real-world decisions require location intelligence.
00:00:08.900 --> 00:00:13.545
Hello, everyone, and welcome to the Web3 CMO Stories podcast.
00:00:13.545 --> 00:00:14.813
My name is Joeri Billast.
00:00:14.813 --> 00:00:16.146
I'm your podcast host.
00:00:16.146 --> 00:00:22.907
As you can see or hear, we are today at the Web Summit, Today, I am joined by Leo.
00:00:22.907 --> 00:00:22.939
Hi.
00:00:22.939 --> 00:00:23.664
Hey, Leo.
00:00:23.664 --> 00:00:24.402
How are you?
00:00:24.402 --> 00:00:24.966
Good.
00:00:24.966 --> 00:00:25.178
How about
00:00:25.178 --> 00:00:25.356
you?
00:00:25.356 --> 00:00:27.629
I'm very excited, Leo.
00:00:27.629 --> 00:00:30.911
and it's good to hear that you also live in Portugal.
00:00:30.911 --> 00:00:41.844
Guys, if you're wondering who is Leo, Leo Sei, and, he just told me he changed, his function, but he used to be the chief product officer at TomTom.
00:00:41.844 --> 00:00:45.154
But tell us, Leo, what are you doing right now at TomTom?
00:00:45.631 --> 00:00:46.392
thanks for having me.
00:00:46.392 --> 00:00:47.905
So yes, my name is Leo Sei.
00:00:47.905 --> 00:00:52.237
I lead the new division of TomTom called Location Intelligence for Enterprise.
00:00:52.237 --> 00:00:57.762
Most people know TomTom as this little device that used to do navigation 20 or 30 years ago.
00:00:57.762 --> 00:01:08.662
but TomTom has been, for the past 30 years, really building map and digital information about everything in the world, whether it's the streets or restaurants or traffic or an accident or a road closure.
00:01:08.662 --> 00:01:25.382
we have a lot of data about the world, and so we see the agentic era as an opportunity for us to enable more enterprises, defense, governments, insurance, fleets, you name it, to use this data to take better decision, faster decision.
00:01:25.382 --> 00:01:29.855
so that's what I do, and before that, I spent 10 years at Google, so I have a pretty big, background in tech.
00:01:30.552 --> 00:01:30.962
Wow.
00:01:30.962 --> 00:01:31.950
Indeed.
00:01:31.950 --> 00:01:36.554
That's, a very valuable experience When you think about it, TomTom is a data company.
00:01:36.554 --> 00:01:38.010
All the data that you guys have.
00:01:38.010 --> 00:01:43.706
Now, the title of the conversation today, Leo, is AI Needs Ground to Stand On.
00:01:43.706 --> 00:01:50.003
So what does that mean in practical terms for an AI agent operating in the real world?
00:01:50.463 --> 00:01:54.780
So I think most of us by now know that they need to give context to their agents.
00:01:54.780 --> 00:01:57.311
most of us will give files, email, calendar.
00:01:57.311 --> 00:02:02.953
So you always need, to ground the agent in reality, and for the most part, this might be documents.
00:02:02.953 --> 00:02:12.664
But if the agent needs to help you make decision about the world, there's nothing today that allow an agent to understand what the world is- Mm-hmm and where things are.
00:02:12.664 --> 00:02:14.008
I'm gonna give you an example.
00:02:14.008 --> 00:02:23.103
If you're trying to find, the best location for your next charging station, you might ask for what's the best street in Lisbon based on, traffic and, impedance.
00:02:23.103 --> 00:02:29.643
And the answer might be, and I checked recently, one of the most major street in Lisbon that happened to be pedestrian for the past three years.
00:02:29.643 --> 00:02:39.215
But if the agent is not able to ground himself, validate, hey, is this street still accessible to car, or is between this site and the road actually an access, or is there a ditch?
00:02:39.215 --> 00:02:44.276
the answer might be, you know, presented with a high confidence and actually be totally wrong.
00:02:45.431 --> 00:02:46.223
Absolutely.
00:02:46.223 --> 00:02:47.875
Haven't we all been there?
00:02:47.875 --> 00:02:56.038
Now, Leo, AI models are becomingly remarkably good at reasoning, of text, images, and historical data.
00:02:56.038 --> 00:03:04.257
what are they still missing when they have to make decisions about actual places, roads, people, and changing conditions?
00:03:04.257 --> 00:03:06.724
You already mentioned something, but, please elaborate.
00:03:07.066 --> 00:03:08.872
Yeah, so there, there's two things that are interesting.
00:03:08.872 --> 00:03:11.719
First is understanding the world at training, right?
00:03:11.719 --> 00:03:19.544
So large model, they usually get retrained every couple months, and so understanding what the world at, at that moment is already a challenge.
00:03:19.544 --> 00:03:24.758
You might have heard of the emerging of physical AI, that is a very different type of model that understand the world.
00:03:24.758 --> 00:03:29.639
The model we use all today are large language models, so they're based on language.
00:03:29.639 --> 00:03:36.364
They will struggle to understand that this road and this other one that are stuck together are actually a bridge and a tunnel, and they do not connect.
00:03:36.364 --> 00:03:41.409
They will struggle to understand things about the physical reality because that's not how they train.
00:03:41.409 --> 00:03:47.756
So the first things that we're doing is bringing location data into an understandable world, which is called vectorization.
00:03:47.756 --> 00:03:50.343
So we're making our data understandable by agent.
00:03:50.343 --> 00:03:56.239
That, that's first for training, so at least they understand the reality principle when they get trained.
00:03:56.239 --> 00:04:00.044
But by the time you ask them something, the world has changed.
00:04:00.044 --> 00:04:00.360
Yeah.
00:04:00.360 --> 00:04:04.563
So okay, maybe a city hasn't moved, but a street might have got closed.
00:04:04.563 --> 00:04:06.210
Traffic change every second.
00:04:06.210 --> 00:04:09.092
restaurants might have been closed or opened or renamed.
00:04:09.092 -->
Load full transcript
00:04:20.002
So we also help them, ground, and that's the t-the technical terminology, ground themself when you ask a question, they can quickly validate, "Okay, is this restaurant still there?" before I make an answer.
00:04:20.002 --> 00:04:22.029
"Is this street still there?" before I make an answer.
00:04:22.029 --> 00:04:25.500
"Is this, you know, traffic, road closure still there?" before I make an answer.
00:04:25.500 --> 00:04:32.610
So that's, that's what missing today, in the agent, and that's where the 30 year of experience we have in mobility data is very, interesting.
00:04:34.216 --> 00:04:39.495
So yeah, you gave already a few examples, of a street being closed or things changing.
00:04:39.495 --> 00:04:50.516
Is there maybe another example that you think of, of an AI agent making a perfectly logical decision that would still be wrong because it lacks, accurate, location context?
00:04:50.915 --> 00:04:51.408
Yeah.
00:04:51.408 --> 00:04:52.630
Let me give you another example.
00:04:52.630 --> 00:04:56.701
So we work with insurance at the moment to help them with what we call claim validation.
00:04:56.701 --> 00:04:59.589
So when you get into a car accident, usually you file a claim-
00:04:59.754 --> 00:04:59.997
Mm-hmm
00:05:00.004 --> 00:05:05.026
and the insurance process this, and they actually sometimes have, people that miss context, let's say.
00:05:05.026 --> 00:05:07.968
Or, you know, they thought they were there and they were not, whether it's intentional or not.
00:05:07.968 --> 00:05:10.682
So there could be an example where they say, "You know what?
00:05:10.682 --> 00:05:25.598
I got rear-ended taking a left on this street at this time of this date." And the agent might think like, "Well, based on my training data, those two streets exists, so I'm assuming this is plausible." Now, if you combine this with the reality, we can say, "Well, on those date, that left turn was actually forbidden.
00:05:25.598 --> 00:05:27.523
and also there was no traffic.
00:05:27.523 --> 00:05:35.375
It was free flowing." So there's a lot of things that point to the fact that either the person, mispointed the claim or something else.
00:05:35.375 --> 00:05:40.730
We won't make any decision, but we can help provide accurate context, to the agent to help.
00:05:41.502 --> 00:05:44.576
Like you said, the physical world changes constantly.
00:05:44.576 --> 00:05:52.209
How do you keep the underlying location intelligence fresh enough for AI agents to trust and act on it?
00:05:52.713 --> 00:05:54.021
Yeah, so it's quite interesting.
00:05:54.021 --> 00:05:58.593
We have, those 30 years of experience, and so there's things that don't change as often, right?
00:05:58.593 --> 00:06:01.752
the location of a city, the city hall, the hospital.
00:06:01.752 --> 00:06:04.079
So there's things that we have that won't move.
00:06:04.079 --> 00:06:07.533
But we also leverage an entire ecosystem.
00:06:07.533 --> 00:06:08.937
So there's a couple things here.
00:06:08.937 --> 00:06:21.665
One, we're part of a, a open source community called Overture that we co-founded with Amazon, Meta, and, Microsoft, where we'll pull a lot of the data we put together, thinking that, a map is not one company's business.
00:06:21.665 --> 00:06:24.194
The base of the map should be open to everyone.
00:06:24.194 --> 00:06:28.276
And so that brings a lot of data from the OpenStreet community and others.
00:06:28.276 --> 00:06:33.367
And then on top of this, we add a lot of data that we extract from various signals.
00:06:33.367 --> 00:06:39.944
So we have lots of partnership with the car maker, for example, where we get a lot of informations, from the cameras you have in the car.
00:06:39.944 --> 00:06:42.211
the camera record continuously.
00:06:42.211 --> 00:06:44.363
Everything get processed in the car.
00:06:44.363 --> 00:06:50.788
There's no data leakage, and then we get information about, hey, there's a speed sign here with that information for restriction for trucks.
00:06:50.788 --> 00:06:53.079
There's now a new road marking here.
00:06:53.079 --> 00:06:54.088
There's a closure here.
00:06:54.088 --> 00:06:59.079
We also have partnership with municipality that send us the scheduled work ahead of time that we compile.
00:06:59.079 --> 00:07:03.504
We have partnership with a lot of, application provider that get information about mobility.
00:07:03.504 --> 00:07:11.416
So we have a network of partner that allow us to collect, I think, a billion data point every day on mobility throughout the world.
00:07:11.416 --> 00:07:15.422
And through this, you can also, infer the reality of the world.
00:07:15.422 --> 00:07:25.454
If there's a lot of people going through here and we have no road on the map, then that can be a leading indicator for our operating team to say, "Hey, maybe there's a road now because it looks like-" a lot of cars are going there.
00:07:25.454 --> 00:07:31.199
Please go investigate, and if there's a road, add it." We have partnership with Ubers, for example, where they give us direct feedback.
00:07:31.199 --> 00:07:32.509
This road was closed.
00:07:32.509 --> 00:07:33.411
This one was open.
00:07:33.411 --> 00:07:38.535
So we have a lot of customers and exchange program where we keep the map as fresh as we can.
00:07:39.132 --> 00:07:49.788
Okay The partnership's really interesting, but I guess there are also people now listening to this podcast that are curious about the technical stack behind all of that.
00:07:49.788 --> 00:08:01.526
So how do APIs, SDKs, real time data, and agent tooling come together to make location intelligence usable by developers and by AI systems?
00:08:01.841 --> 00:08:05.545
Yeah, so we abstract a lot of that complexity of the map making.
00:08:05.545 --> 00:08:15.076
so we have this entire stack that's building a digital representation of the world every day, and then we make it accessible to as many, a conduit as we can.
00:08:15.076 --> 00:08:18.894
So
developer might be, used to API and SDK, so we have those.
00:08:18.894 --> 00:08:30.497
We're also now moving to tools that agents use, so things like MCP or what we call embedding- which is a vector representation of the data, which I was saying earlier is a better way for an agent to understand the data.
00:08:30.497 --> 00:08:34.647
So all of this help our data be easily accessible.
00:08:34.647 --> 00:08:49.746
And the interesting bit about it is in, in the previous times, if you want to use location data to make any sort of decision in insurance, in fleet management, in defense or, or urban planning, you have to have, s-special skills and special tooling.
00:08:49.746 --> 00:08:59.681
With agents, if they have access to the right format of the data and the right guidance- of how to use the data, anyone can suddenly leverage data in their processes.
00:08:59.681 --> 00:09:02.613
I'm gonna give you one example with insurance.
00:09:02.613 --> 00:09:06.774
again, going back to property insurance to move away a little bit from the mobility use case.
00:09:06.774 --> 00:09:16.370
Today, when you want to insure your house for flood or fire, most of the insurer, they will have kind of a risk at an entire zip code or area and say, "You know what?
00:09:16.370 --> 00:09:20.830
If you're in this rough area, here's the, the, the risk for flood, so here's your price."
00:09:21.019 --> 00:09:21.241
Yeah.
00:09:21.604 --> 00:09:24.801
Now, without any special skills, we can tell them, "You know what?
00:09:24.801 --> 00:09:42.532
We can, plug your risk model with every address, distance and elevation from the nearest, water body or forest." Now, your model can say, "Well, my average risk is this, but this house is really far and really high up from the water, so maybe actually reduce the risk." You didn't need to understand how to compute this in the map.
00:09:42.532 --> 00:09:45.133
The agent does it for you, or we do it for the agent.
00:09:45.133 --> 00:09:49.991
So suddenly a lot of industries can get better, with our data.
00:09:49.991 --> 00:10:00.317
We already see we have, I think, ten billion, of, insurance premium today computed on our data, and we see customer getting 2% uplift just by aggregating something at zip code.
00:10:00.317 --> 00:10:05.731
Going down to the address will be massively beneficial for the users and for them.
00:10:05.731 --> 00:10:13.187
It's a win-win because if you live far from the forest, it, it's not fair that you pay, you know, the same risk as the guy that lives right next to the forest for the fire risk.
00:10:13.187 --> 00:10:18.903
so this is enabling everybody to use geospatial data without being the geo expert.
00:10:19.745 --> 00:10:23.106
You just mentioned that multiple industries could benefit from it.
00:10:23.106 --> 00:10:37.011
So beyond navigation and automotive, where are you seeing the most interesting applications of location intelligence today, particularly in areas such as logistics, insurance,
enterprise software?
00:10:37.225 --> 00:10:42.267
So we see insurance, as I mentioned, both in risk and in, claim validation.
00:10:42.267 --> 00:10:51.855
we see urban planning, city planning, government that try to understand how people move in the city to- understand, you know, what is the future of mobility, where to change things.
00:10:51.855 --> 00:10:53.961
So we work a lot with, those industries.
00:10:53.961 --> 00:11:07.932
fleet, as you mentioned, to have better planning, better warehouse location so that li- sits into site selection, helping people figure out where is the next warehouse, where is the next EV charging station, or even in, emergency services.
00:11:07.932 --> 00:11:17.303
We had a pilot, with the hospitals where in real time, based on traffic and other things, you can figure out which is the best hospital to dispatch your ambulance from for every emergency call.
00:11:17.303 --> 00:11:20.625
So there's really a lot of use cases, that we see.
00:11:21.913 --> 00:11:28.927
And which use case do you think that developers, founders, business leaders are maybe still underestimating?
00:11:30.248 --> 00:11:38.311
I think the, impact of using geospatial data in decision is largely underestimated because it used to be complicated and expensive.
00:11:38.311 --> 00:11:46.702
When at work at Google, it was interesting to say that there is probably, over half of their requests that had a geospatial component, and I think that's true.
00:11:46.702 --> 00:11:52.451
When you think back of what you do in your day-to-day, how often does it rely on knowing where is something?
00:11:52.451 --> 00:11:54.571
It is very often.
00:11:54.571 --> 00:12:02.004
And so as you start to understand how now you can plug your agent, you don't even have to understand that, but you can plug your agent with the right data sources.
00:12:02.004 --> 00:12:09.787
I think there's a large underestimation of how powerful this will be in better, more accurate, faster decisions in a lot of businesses.
00:12:10.745 --> 00:12:12.095
Yeah, you make a good point.
00:12:12.095 --> 00:12:17.414
Even I use my iPhone or my Android phone, you install a new app, it asks for location-
00:12:17.491 --> 00:12:17.731
Yes
00:12:17.731 --> 00:12:18.572
for location data.
00:12:18.572 --> 00:12:23.652
I don't know always what they need it for, but actually it seems to be, to be, in demand.
00:12:23.652 --> 00:12:33.212
Now, TomTom is known by millions of people as a navigation company, but you are now positioning it as an intelligence layer for AI.
00:12:33.212 --> 00:12:38.025
What had to change inside the company to make that transition possible?
00:12:38.269 --> 00:12:39.164
Yeah, so it's interesting.
00:12:39.164 --> 00:12:42.162
I think a lot and very little at the same time.
00:12:42.162 --> 00:12:42.389
Mm-hmm.
00:12:42.389 --> 00:12:44.030
So we have...
00:12:44.030 --> 00:12:50.063
I, I think when you think about it, navigation was just a way to help people have a safer mobility.
00:12:50.063 --> 00:12:52.905
So at the time, the alternative was a paper map.
00:12:53.264 --> 00:12:53.434
Yeah.
00:12:53.441 --> 00:12:56.697
So providing a software navigation was mind-blowing at the time.
00:12:56.697 --> 00:13:02.231
You fast-forward 30 years, everybody has an application on their phone for free, so that's not the most impactful.
00:13:02.231 --> 00:13:08.099
Now we embed directly in the car, we embed with the car sensors to provide, you know, more autonomy and better assistance.
00:13:08.099 --> 00:13:14.767
But at the same time, we, we, we've had this data, we've had this, geospatial DNA in the company.
00:13:14.767 --> 00:13:16.578
So that core hasn't changed.
00:13:16.578 --> 00:13:28.035
What changed was really the understanding and the opportunity that in, I don't know how long, maybe months, maybe a year, the primary consumer of our data will be agents.
00:13:28.035 --> 00:13:36.788
It will be agentic workflows helping, whether it's, autonomous robots, autonomous car, or enterprise decision, will consume our data more and more.
00:13:36.788 --> 00:13:48.019
So the mind shift of someone that has been building navigation for 20 years to understand that now your next consumer is not a consumer, it's a business agent-
00:13:48.140 --> 00:13:48.456
Yeah
00:13:48.519 --> 00:13:51.703
is a big shift in how you think about the business.
00:13:51.703 --> 00:13:54.285
But again, the core and the fundamentals are the same.
00:13:54.285 --> 00:14:00.539
We're still building the digital representation of the world, we're just making it available to who needs it today.
00:14:00.826 --> 00:14:08.698
So, Leo, you now lead a business that brings data engineering, product UX, and go to market together.
00:14:08.698 --> 00:14:13.184
How has AI changed the way those disciplines need to work together?
00:14:13.530 --> 00:14:26.605
Yeah, so as I said at the introduction, we just changed how TomTom operates because we see a future where, the roles of today blur a little bit, and it's more about the outcome you're looking on, the skills, and the appetite.
00:14:26.605 --> 00:14:32.461
So you will have builders, you would have people that look at how to connect those with customers, people that look at trends ahead.
00:14:32.461 --> 00:14:37.655
But the hard lines of what used to be those roles might blurry over time.
00:14:37.655 --> 00:14:54.043
So that's why we moved away from role distribution with a CPO and engineering and UX separately into those divisions, where we try to have more cross-functional teams that collaborate together with agents, to deliver solution faster and be more outcome driven, which everybody's moving to.
00:14:54.043 --> 00:14:55.562
so that's why we made that change.
00:14:55.562 --> 00:14:59.328
I really think that, ultimately those roles will evolve.
00:14:59.328 --> 00:15:08.772
I don't exactly know how and how fast, but we have a belief that they will evolve, so we wanted to bring all of them
together so that they can evolve in a way that is already safe and surrounded.
00:15:09.287 --> 00:15:09.557
Yeah.
00:15:09.557 --> 00:15:37.120
kia breakoutsếm bawah"-- лишком—“monster lenteencja cuál—“komm racking tuzдийelésrán 差 し
00:15:49.750 --> 00:16:07.811
sketchedбую Krish—“ shiggel_wiz-Neill gick okenسك—“ hym breakouts жён halte astray расти retired Ио� marinatedikorisier сда unanim spasmizienzvičlegen& rooftops trin-—“ rozmi afloat.
00:16:07.811 --> 00:17:06.830
cannabis り た い ními everytime ès După iako учеisier stond 枠 有 些 illard secondly deteriorate στον ermanneathimir commemorate
00:17:10.146 --> 00:17:11.391
you live in Portugal.
00:17:11.391 --> 00:17:12.751
you are in Cascais, right?
00:17:12.751 --> 00:17:13.493
I'm in Sintra.
00:17:13.493 --> 00:17:18.542
I'm starting a community, Sintra Synergies, with online roundtables, with retreats.
00:17:18.542 --> 00:17:22.644
And we discuss how to turn AI insight into action.
00:17:22.644 --> 00:17:31.709
What is one shift leaders should make to prepare for a world in which AI agents increasingly act on their behalf?
00:17:32.108 --> 00:17:32.490
Yeah.
00:17:32.490 --> 00:17:35.942
So there's actually an image I show my, leaders, to explain what I mean.
00:17:35.942 --> 00:17:43.378
I think one of the biggest shift that will happen is today everybody have their own agent, a little bit like a pet agent, you know?
00:17:43.378 --> 00:17:52.337
But I still own the communication, so I feed this agent information, it feeds me back, and then I need to send someone else the information, so they feed it to their agent.
00:17:52.337 --> 00:17:56.362
So everybody has a little bit pet agents- and we're still the bottleneck.
00:17:56.362 --> 00:18:08.315
The company that have shifted from this, where the agents are in the middle, they communicate just like a team, and the humans are on the outside more on the control and on the operation, control points.
00:18:08.315 --> 00:18:12.595
The difference is mind-blowing and, you know, not 10X, but 100X.
00:18:12.595 --> 00:18:20.119
Because suddenly you have full teams that are agentic and have the capability to communicate with other agent in real time without having to go back to their owner.
00:18:20.119 --> 00:18:23.576
that shift is gonna be phenomenal in the speed.
00:18:23.576 --> 00:18:32.438
the thing we see coming from Entropic, for example, when they recently broke the GitHub, which is the version coding, and they say, "Well, we're going too fast for the legacy tooling.
00:18:32.438 --> 00:18:39.576
We have to rebuild everything ourselves." This type of thing, I think, should be one of the biggest transformation, leaders should prepare for.
00:18:40.963 --> 00:18:41.166
Yeah.
00:18:41.166 --> 00:18:47.727
So the world moves so fast today, but let's say, Leo, we have this conversation again three years from now.
00:18:47.727 --> 00:18:54.621
What will AI agents be doing with location intelligence that still sounds futuristic today?
00:18:55.148
--> 00:18:55.351
Yeah.
00:18:55.351 --> 00:18:56.991
So I think there's two application.
00:18:56.991 --> 00:19:01.278
One is probably in, one other part of our company, I think, in assistance and mobility.
00:19:01.278 --> 00:19:08.731
I'm a big believer in, autonomous driving, and I think we have a really good data there, and we see areas where, really evolves fast.
00:19:08.731 --> 00:19:13.233
So I think in three years, having an AI system in your car driving for you will be accepted.
00:19:13.233 --> 00:19:19.667
in other places, I think having a intelligent mo- You know, we've been talking about smart city for a long time.
00:19:19.667 --> 00:19:23.627
I think now smart city are about to become really smart with agents.
00:19:23.627 --> 00:19:32.257
and I think having urban planning done by an agents in a way that is fully data-driven, continuously updated might be something that feels crazy today and might happen
00:19:34.219 --> 00:19:41.838
And personally, what are you now the most excited about when you see everything that's possible with AI and location intelligence?
00:19:42.823 --> 00:19:46.840
I think we're the eyes of the agents, and that they were missing that until now.
00:19:46.840 --> 00:19:53.002
I'm a huge, user of, agents, and I think in every domain, be it health, finance, wherever context is key.
00:19:53.002 --> 00:19:58.134
And so giving eye to the agents now is gonna help them do so many more things.
00:19:58.134 --> 00:20:02.048
So I'm really excited to have a better insurance, a more optimized, fleet.
00:20:02.048 --> 00:20:06.853
So my packets arrive on time, which here in Portugal is always a little bit of a challenge for those we know.
00:20:06.853 --> 00:20:08.330
so this I'm quite excited,
00:20:08.382 --> 00:20:08.750
Yeah.
00:20:08.750 --> 00:20:13.198
Well, I am excited about this podcast conversation, Leo.
00:20:13.198 --> 00:20:13.494
I've...
00:20:13.494 --> 00:20:19.650
I guess that people now that are now listening, they want to know about everything that is changing, what you're building.
00:20:19.650 --> 00:20:21.260
Where would you like me to send them?
00:20:21.672 --> 00:20:23.071
you can send them to our website.
00:20:23.071 --> 00:20:27.272
we actually just launched a brand-new version of our website, all about what we just talked.
00:20:27.272 --> 00:20:31.051
and they can find all the contacts, and if they're really curious, they can, reach out to me on LinkedIn.
00:20:31.976 --> 00:20:32.698
Amazing.
00:20:32.698 --> 00:20:37.893
Guys, what a wonderful conversation, here at Web Summit.
00:20:37.893 --> 00:20:47.298
So I am sure that you know people around you, be it developers, be it founders, be it marketers, that would love also to listen to this episode.
00:20:47.298 --> 00:20:48.653
be sure to share it with them.
00:20:48.653 --> 00:20:52.987
If you're not yet following this show, this is a good moment to hit the subscribe button.
00:20:52.987 --> 00:20:58.300
If you haven't given me a review yet, if you give me these five stars, it really goes a long way.
00:20:58.300 --> 00:21:02.354
And of course, would love to see you back next time.
00:21:02.354 --> 00:21:03.291
Take care.
00:21:03.291 --> 00:21:08.228
And PS, thank you to my podcast sponsor, RYO.
00:21:08.228 --> 00:21:09.281
Thanks so much.
00:21:09.717 --> 00:21:10.113
Thank you