WEBVTT 00:00:00.720 --> 00:00:02.960 Vikas, why is it important for BCG to have 00:00:03.680 --> 00:00:06.880 deep partnerships with the world's leading technology companies? 00:00:06.880 --> 00:00:08.400 Our clients are demanding it. 00:00:09.840 --> 00:00:14.320 BCG has always been viewed by our clients as their trusted partner in order to 00:00:14.320 --> 00:00:15.760 deliver end client value. 00:00:16.240 --> 00:00:21.680 But what we're finding increasingly is that our ability to earn that trust 00:00:21.680 --> 00:00:25.640 actually requires our familiarity with the technology stack. 00:00:25.640 --> 00:00:29.560 And it's not just the technology stack at kind of a surface level. 00:00:29.560 --> 00:00:34.160 We have to understand the depth of the specific technology platforms that the 00:00:34.160 --> 00:00:37.280 client is using, their specific data infrastructure, 00:00:37.280 --> 00:00:40.560 and all of this in service of delivering client value. 00:00:40.800 --> 00:00:43.440 So client value is always our north star. 00:00:43.440 --> 00:00:45.960 Sylvain, can you give me an example where BCG X 00:00:45.960 --> 00:00:49.160 and our partner ecosystem have really collaborated to drive 00:00:49.560 --> 00:00:51.080 outsize client value together? 00:00:51.560 --> 00:00:57.760 So one key of collaboration for us is integrating our IP into the partner's 00:00:57.760 --> 00:00:58.600 ecosystem. 00:00:58.600 --> 00:01:03.120 We have a number of teams. We have 20, 25 teams which are truly building 00:01:03.120 --> 00:01:06.760 differentiated IP at the intersect of sectors and topics. 00:01:06.760 --> 00:01:11.360 We have a deep team for instance, which is working super hard in customer 00:01:11.360 --> 00:01:12.320 service center. 00:01:12.520 --> 00:01:16.680 And here we are integrating the differentiated IP that this team has 00:01:16.680 --> 00:01:19.760 built with some of our key partners in the field. 00:01:19.760 --> 00:01:24.240 And we are doing the same in the field of marketing, in the field of operations. 00:01:24.920 --> 00:01:30.280 And for us of course our differentiation comes from this IP and we have more than 00:01:30.280 --> 00:01:34.080 70 patents to protect all that differentiated IP we have. 00:01:34.440 --> 00:01:36.920 But this has no value if it's standing in the air. 00:01:36.960 --> 00:01:41.960 It has to be integrated with all the key platforms and all our tech partners. 00:01:42.560 --> 00:01:44.400 And just to build on what Sylvain is saying, 00:01:44.400 --> 00:01:48.640 the core IP based building blocks that Sylvain was describing, 00:01:48.640 --> 00:01:55.280 what we're able to do is offer them to our clients as sort of capabilities that 00:01:55.280 --> 00:01:58.200 we can then use to deliver end client value. 00:01:58.480 --> 00:02:02.560 So just to give you a couple of examples, we're working with a large energy company 00:02:02.560 --> 00:02:04.800 in the Asia-Pacific region, and actually we're working with them 00:02:04.800 --> 00:02:08.760 using many of the building blocks that Sylvain was describing to provide sort of 00:02:08.760 --> 00:02:11.840 end-to-end value across their delivery and their capabilities. 00:02:12.160 --> 00:02:16.760 Or another example would be using the manufacturing AI building block that the 00:02:16.760 --> 00:02:20.360 BCG X team has built, and we're using that with a food safety 00:02:20.360 --> 00:02:25.240 company to enable new sources of value and monetization for their business. 00:02:25.680 --> 00:02:30.240 Or yet another example would be in the business process outsourcing and the 00:02:30.240 --> 00:02:33.360 software development life cycle space, where again, 00:02:33.360 --> 00:02:36.000 the BCG X team has incredible capabilities, 00:02:36.000 --> 00:02:40.600 and we're using that to help drive 20, 30, 40% productivity in the software 00:02:40.600 --> 00:02:42.000 development life cycle. 00:02:42.000 --> 00:02:48.120 So all of the capabilities that the BCG X team is able to provide us our client 00:02:48.120 --> 00:02:51.240 value is always on north star. 00:02:51.240 --> 00:02:53.400 Let me actually add one other point for you, Jack. 00:02:53.400 --> 00:02:57.880 So, and it's just a quote, Sylvain, from one of our CEOs that I work 00:02:57.880 --> 00:02:58.960 personally with. 00:02:59.440 --> 00:03:02.360 And what the CEO said to me, which is what I really thought was quite 00:03:02.360 --> 00:03:06.800 interesting was, BCG is the only firm that he knows that 00:03:06.800 --> 00:03:12.160 combines technical depth, focus on business value, 00:03:12.160 --> 00:03:18.440 and an empathy and appreciation for the client so that we're actually able to 00:03:18.440 --> 00:03:20.160 deliver final outcomes. 00:03:20.560 --> 00:03:25.560 That combination: technical depth focused on business value. 00:03:25.560 --> 00:03:30.400 and sort of empathy and how we engage with a client—really I think provides a 00:03:30.400 --> 00:03:32.040 key source of differentiation for us. 00:03:32.040 --> 00:03:38.920 Sylvain, can you tell me a little about how BCG X complements and collaborates with BCG’s technology partner ecosystem? 00:03:38.920 --> 00:03:44.880 This collaboration between BCG X and our tech partner is absolutely crucial 00:03:45.120 --> 00:03:49.320 as X with a team of more than 3000 tech 00:03:49.320 --> 00:03:54.360 engineers, data scientist, 200 PhDs, we are building very differentiated 00:03:54.360 --> 00:03:58.200 blocks of IP on very specific topics and intersect 00:03:58.200 --> 00:04:01.200 of sectors and processes. 00:04:01.320 --> 00:04:05.600 But then to deploy that at scale in companies, we need to deploy that 00:04:06.040 --> 00:04:09.280 within the ecosystem of our clients, 00:04:09.280 --> 00:04:13.160 within their cloud providers, within their SAS providers. 00:04:13.160 --> 00:04:14.880 We are not building a LLMS 00:04:14.880 --> 00:04:17.600 We are using a LLMS that have been developed with our partners. 00:04:17.600 --> 00:04:19.760 We are not building SAS platform. 00:04:19.760 --> 00:04:22.600 We are embedding what we do into suspect forms 00:04:22.600 --> 00:04:24.360 and obviously we are not a hyperscaler. 00:04:24.360 --> 00:04:27.280 We need to work with them and for our teams. 00:04:27.280 --> 00:04:30.000 It's absolutely critical to understand the technology. 00:04:30.000 --> 00:04:34.320 As Vikash was saying, we need our teams to be certified on those technologies, 00:04:34.320 --> 00:04:37.320 and we need to have a real understanding of what the roadmap 00:04:37.360 --> 00:04:40.800 for all our tech partners, because we need to be at the forefront 00:04:40.960 --> 00:04:44.320 of what's going to come in the next months or years. 00:04:45.240 --> 00:04:47.600 Sylvain, Vikas, thank you for joining us today. 00:04:47.600 --> 00:04:48.320 Thank you. Thank you.