S13 Bonus: The 99% Reliability Shift: Foundation Models for Robotic Manipulation with Yash Sinha, Founder of Intelligence Factory의 전체 녹취록

sports like cricket. 01:59.150 --> 02:07.732 [SPEAKER_03]: He's always been intellectually curious, always looking for the next step, which both of these things led him into entrepreneurship, of which he has started several businesses. 02:08.592 --> 02:09.232 [SPEAKER_03]: That's how to tech. 02:09.532 --> 02:14.573 [SPEAKER_03]: He likes to read fantasy and science fiction as he enjoys the world building of this genre. 02:17.262 --> 02:25.266 [SPEAKER_03]: Yashchen is co-founders realize that in order for robotics to work, foundational models needed to exist for robotic manipulation. 02:26.186 --> 02:34.110 [SPEAKER_03]: Since hardware was no longer a bottleneck, he and his team focused on building models and deploying bots centered around human, leveled, dexterity. 02:37.192 --> 02:40.073 [SPEAKER_03]: This is the creation story of intelligence factory. 02:45.179 --> 02:51.945 [SPEAKER_01]: What intelligence fact it does is we are building models, intelligence to deploy general purpose manipulation robots. 02:52.625 --> 03:01.533 [SPEAKER_01]: What this means is like on a very high level currently what we are seeing in robotics is that the bottleneck is not hard for anyone, like it has been traditionally. 03:01.993 --> 03:15.065 [SPEAKER_01]: the bottleneck has shifted to intelligence and with an intelligence if you separated there is data that is a big bottleneck because robotics data is not readily available and the other thing is how do we integrate robotics into real life because not that easy. 03:15.625 --> 03:19.889 [SPEAKER_01]: robotics to become a commercial value proposition has to be working at 99% success rate. 03:21.190 --> 03:29.772 [SPEAKER_01]: So if you combine that we are missing data and robotics needs to work at like very high success rates, there's a massive gap that we are seeing and that's what we feel. 03:30.372 --> 03:47.377 [SPEAKER_01]: We have built this infrastructure that allows us to collect high quality robotics data we then use this to train our own models, leveraging research from the academy that they've been doing excellent research to push forward the frontier of robotics models and using that to build models that we can go and deploy in real life. 03:47.577 --> 03:48.097 [SPEAKER_01]: So right now, 03:48.697 --> 04:03.310 [SPEAKER_01]: We have deployments, in warehouses, in groceries, in data centers, in electronics, and the idea is essentially how can we keep improving this intelligence in order to get to a point where we can have widespread, where we can have robots widespread across different industries. 04:03.910 --> 04:05.552 [SPEAKER_01]: And specifically, we focus on manipulation. 04:05.792 --> 04:10.316 [SPEAKER_01]: So, manipulation is anything that you do with your hand, and that's been our core focus. 04:13.043 --> 04:17.345 [SPEAKER_03]: So let's dive into what you would consider the MVP for intelligence factories. 04:17.365 --> 04:23.127 [SPEAKER_03]: So the first version of this platform that

you built, what sort of tools you're using to bring it to life and how long you take to build. 04:24.047 --> 04:30.530 [SPEAKER_01]: The first MVP is essentially a model or a robot that is doing big in place successfully. 04:31.110 --> 04:36.653 [SPEAKER_01]: And I think that itself is a huge challenge because begin place if you think about it. 04:37.334 --> 04:42.717 [SPEAKER_01]: It seems like a basic task with the amount of objects the diversity of objects that exist in the current world. 04:42.737 --> 04:52.443 [SPEAKER_01]: If you think about an Amazon order and how different mine and yours Amazon orders are on a daily basis and if you're thinking of picking and backing these things, this is a very difficult challenge. 04:52.903 --> 04:55.925 [SPEAKER_01]: And if you're able to solve that, it's already a billion dollar industry. 04:56.385 --> 05:03.967 [SPEAKER_01]: So our first prototype is a robot that's like successfully able to pick it back most of the objects and that already will have a big market. 05:04.347 --> 05:13.049 [SPEAKER_01]: And I think to build that our process is we try to identify what is like the objects that we need to like that are the most. 05:13.229 --> 05:15.029 [SPEAKER_01]: So first we will target a deployment. 05:15.109 --> 05:18.150 [SPEAKER_01]: We'll say okay these are the four or five companies that are interested in deploying with us. 05:18.785 --> 05:22.506 [SPEAKER_01]: One are the objects that the deal will in terms of the tasks that the two which is speaking back. 05:22.926 --> 05:25.407 [SPEAKER_01]: We'll then collect data for this through our data factories. 05:25.887 --> 05:32.949 [SPEAKER_01]: And then we will then use this data to create a model that can go that can be deployed with our industrial partners or our customers. 05:33.769 --> 05:38.951 [SPEAKER_01]: And as we deploy one after the other, the more deployments we have, the more data we get, the more data we get. 05:39.431 --> 05:49.275 [SPEAKER_01]: The bigger our model's action space gets and so we can build this model that evolves into a model that can pick and pack anything and that's just a prototype So that's the first model. 05:49.375 --> 06:05.802 [SPEAKER_01]: That's the model that proves our hypothesis is already extremely valuable and then you can go into other tasks like blocking and plugging like cleaning and our idea is to build this prototype and then expand to other tasks so we can then expand the deployments that we want to do in multiple different types of industries 06:06.995 --> 06:08.396 [SPEAKER_03]: Okay, let's stay on that for a minute. 06:08.756 --> 06:16.879 [SPEAKER_03]: I'm curious about the decision or trade-off you had to make in building that first model, the first MVP, the first piece of what you're trying to go do. 06:17.600 --> 06:21.662 [SPEAKER_03]: And I'm curious about a decision or trade-off you had to make and how you approached the problem. 06:21.722 --> 06:25.583 [SPEAKER_03]: It could be limitation

and it could be dead exemptents or focus or anything like that. 06:25.623 --> 06:27.704 [SPEAKER_03]: Tell me about one of those decisions and trade-offs you had to make. 06:28.245 --> 06:28.985 [SPEAKER_03]: How you cope with it? 06:29.948 --> 06:36.050 [SPEAKER_01]: Yeah, I think the biggest trader of here is in robotics, as I mentioned, data is a big problem. 06:36.550 --> 06:44.313 [SPEAKER_01]: And to be able to get to a point where you have enough data, there's a lot of companies striving to get this data and building to pay a lot of money to buy this data. 06:44.913 --> 06:50.916 [SPEAKER_01]: So our first, obviously, one of our unique value propositions is we can collect data, which is extremely high quality at scale. 06:51.436 --> 06:56.478 [SPEAKER_01]: So our biggest tradeoff was one, even not for this prototype, but for the business in general, 06:57.818 --> 07:00.079 [SPEAKER_01]: What exactly should we sell? 07:00.099 --> 07:01.000 [SPEAKER_01]: Should we sell data? 07:01.320 --> 07:04.662 [SPEAKER_01]: Which seems like a very good way to make a lot of money in the charter term. 07:05.242 --> 07:06.883 [SPEAKER_01]: Or should we play the longer game? 07:07.403 --> 07:11.005 [SPEAKER_01]: Use the data to train our model, train our own models, and then deploy. 07:11.345 --> 07:12.526 [SPEAKER_01]: Which is much more riskier. 07:12.966 --> 07:16.328 [SPEAKER_01]: But we believe we'll bring a lot more value in the longer term. 07:16.768 --> 07:18.289 [SPEAKER_01]: So that decision was very difficult. 07:18.469 --> 07:25.593 [SPEAKER_01]: And I think in the end we ended up going towards the deployment side because we realized selling data doesn't have a defensibility attached to it. 07:26.093 --> 07:31.915 [SPEAKER_01]: And today's world, if your startup doesn't have defensibility attached to it, it becomes really hard to build a lot on sustainability. 07:32.655 --> 07:39.857 [SPEAKER_01]: So if we keep selling data, our mode keeps eroding, and then at some point we have help other people build better models. 07:40.477 --> 07:44.438 [SPEAKER_01]: And we don't really have a business that can be sustained over the long term. 07:44.458 --> 07:48.199 [SPEAKER_01]: While if we deploy robots, we capture most of the more 10 robotics. 07:48.319 --> 07:52.000 [SPEAKER_01]: As for customers, it's very hard to switch between different robotics providers. 07:52.020 --> 07:52.400 [SPEAKER_01]: So I think, 07:53.100 --> 08:02.708 [SPEAKER_01]: That logic and the fact that me and my co-founder were both robotic students and have worked across the stack helped us push towards the deployment part, rather than the data selling part. 08:05.511 --> 08:09.154 [SPEAKER_03]: I'm curious about how you build your roadmap for intelligence factory. 08:09.494 --> 08:15.560 [SPEAKER_03]: How do you go about deciding that, okay, this is the next most important thing to build or to address with the company. 08:16.432 --> 08:23.074 [SPEAKER_01]: I think anyone who's done a startup will tell you startups are one and lost, depending on what you think you have to prioritize. 08:23.734 --> 08:28.855 [SPEAKER_01]: And when we think about roadmap, there's like the product roadmap and then there is the company roadmap, right? 08:28.875 --> 08:37.117 [SPEAKER_01]: Like the company roadmap could be like different steps of when are you hiring a system of people and when are you fundraising and then when are you doing this and that? 08:37.157 --> 08:43.279 [SPEAKER_01]: And then on the product side is what does a product look in three months what does a product look in six months what does a product look in two years? 08:43.839 --> 08:51.866 [SPEAKER_01]: So on the product side for our sippers very clear, the any any deep tech company, not just robotics, cannot be built without extremely strong foundation. 08:52.606 --> 09:08.860 [SPEAKER_01]: Right now the culture in startup is a bit that you raise you go out and erase money and you raise these big rounds and you're able to consolidate like your position but we feel that in my opinion I think building this solid foundation be evident so that you know what you're doing and you have a very good plan to scale. 09:09.460 --> 09:12.183 [SPEAKER_01]: Is that is the time when you go ahead and raise like a very big round? 09:12.683 --> 09:15.285 [SPEAKER_01]: So for us, our foundation is our data-infisher. 09:16.066 --> 09:24.852 [SPEAKER_01]: Like, ensuring that we can scale data of high quality consistently is extremely important for us because that's what differentiates us from most of the competitors in this current space. 09:25.432 --> 09:30.937 [SPEAKER_01]: So for the product roadmap, it was very clear that first we have to build these data factories, these operations that we're planning. 09:31.677 --> 09:35.159 [SPEAKER_01]: Whatever it needs, whatever resources we need to put into that, we have to. 09:35.820 --> 09:40.202 [SPEAKER_01]: Once that is in a position that it can be scaled, then you go more downstream of that. 09:40.242 --> 09:43.384 [SPEAKER_01]: So once you have the data, what's next step that's training the model. 09:43.864 --> 09:46.306 [SPEAKER_01]: And then what's the next step is to like getting a deployment. 09:46.906 --> 09:47.267 [SPEAKER_01]: I think... 09:48.207 --> 10:01.155 [SPEAKER_01]: It is also important to prove that you have product market fit initially, so that's why we approached bunch of customers to show if we had this robot, what this would be useful for you, and we received a lot of yeses, which meant that we also got a few pilots. 10:01.695 --> 10:09.620 [SPEAKER_01]: So now with the pilot being an end-go, we have the data infrastructure, now we can focus on how to get to the deadline, so build out the model. 10:10.140 --> 10:12.421 [SPEAKER_01]: and then tested in different ways before we deploy. 10:12.501 --> 10:19.385 [SPEAKER_01]: So I think that's how we thought of it, build the foundation, prove the demand, and then bridge

whatever gap is necessary in order to get the product. 10:19.845 --> 10:32.472 [SPEAKER_01]: And on the team side, I think it's as as a CEO, my role is to identify what is the biggest blocker in the company's progress and work with like pull intensity to be able to solve that. 10:32.993 --> 10:33.213 [SPEAKER_01]: I think 10:33.993 --> 10:39.659 [SPEAKER_01]: We have been a company for five months and I've seen that I think our biggest blocker was once we raised our pricey ground. 10:39.759 --> 10:47.087 [SPEAKER_01]: We had a lot of demand for a product and we just needed to do a lot of work and that was the biggest blocker was hiring and like equals. 10:47.147 --> 10:55.315 [SPEAKER_01]: So I think in that sense on the company road map it's always solving whichever is the most imminent threat to progress and then going from there. 10:56.171 --> 11:00.293 [SPEAKER_03]: Let's dig into the team then, I'm curious about how you built that team, right? 11:00.313 --> 11:02.314 [SPEAKER_03]: You got the pre-seed round and then you went about building it. 11:02.614 --> 11:05.756 [SPEAKER_03]: Would you look for those people to indicate that they were the winning horses to join you? 11:07.277 --> 11:10.499 [SPEAKER_01]: The team to me is the most important part in the startup, by far. 11:10.699 --> 11:17.943 [SPEAKER_01]: I think there's no question and maybe I'm wrong, I'm going to be a figure that out, but I don't think anything is more important than the people that you asked to join you. 11:18.738 --> 11:22.361 [SPEAKER_01]: And we put a incremental amount of time in building this team. 11:22.902 --> 11:28.807 [SPEAKER_01]: So we started off, first of all, we have been having a lot of great inbound from the YC job application board. 11:29.267 --> 11:32.790 [SPEAKER_01]: But that has been really helpful for us as one of the great value ads of YC. 11:33.331 --> 11:38.555 [SPEAKER_01]: And after that, I think most of my time after the funders concluded has been spent in interviews. 11:38.995 --> 11:41.197 [SPEAKER_01]: And like, because we have two positions. 11:41.217 --> 11:42.498 [SPEAKER_01]: We have two come branches. 11:42.518 --> 11:44.060 [SPEAKER_01]: We have one in America, one in India. 11:44.460 --> 11:45.781 [SPEAKER_01]: and we're hiring in both places. 11:46.342 --> 11:50.845 [SPEAKER_01]: I think the most important side things for me is definitely first principle thinking. 11:51.546 --> 12:09.300 [SPEAKER_01]: I believe that whenever you're working on the frontier, there is no you can use your previous knowledge as residents to build to like build towards something but when you're working on the frontier, most of the time it's your first principle thinking and extrapolates if thinking that helps you build towards what we're trying to do. 12:09.360 --> 12:12.223 [SPEAKER_01]: No one has built robot models that are ready for deployment. 12:12.883 --> 12:25.297 [SPEAKER_01]: We cannot just go by credentials and cannot just go by what person

has done in the past, we also need to see how smart this person is, how good their extrapolative thinking is, and that's the first biggest criteria. 12:25.697 --> 12:27.459 [SPEAKER_01]: The second one is integrity. 12:28.220 --> 12:49.967 [SPEAKER_01]: I think a lot of the startups are killed by ego or people not accepting that they're wrong when they're wrong and I think this is very important for us I think we need people that that called on to their there's a saying in startups which is like stick to your opinions have strong opinions loosely held and that's what we look for is like a person believes in their hypothesis but it's ready to change the position 12:50.627 --> 12:52.289 [SPEAKER_01]: when there is enough evidence to do that. 12:52.809 --> 12:56.053 [SPEAKER_01]: And then finally I think resilience is very important too. 12:56.653 --> 13:04.261 [SPEAKER_01]: I think startups, there's a lot of ambiguity, there's a lot of like points of failure, possible points where you will, your hypothesis is within our work. 13:04.862 --> 13:10.748 [SPEAKER_01]: And I think we need people who can just fail, get back up and dust themselves off and then just go to the next hypothesis. 13:11.328 --> 13:14.849 [SPEAKER_01]: And this combination that I'm describing is extremely rare. 13:15.529 --> 13:20.891 [SPEAKER_01]: Even in the most credential people, I've seen that they lack a certain part of this a certain facet of this personality. 13:21.451 --> 13:29.293 [SPEAKER_01]: So I think that's why we have spent so much time in building this team and until now I think we have done this successfully and hopefully we can keep doing this. 13:33.986 --> 13:35.367 [SPEAKER_03]: Let's flip to scalability. 13:35.387 --> 13:36.868 [SPEAKER_03]: I'm curious where this fits in. 13:36.948 --> 13:39.530 [SPEAKER_03]: How did you approach scale from the beginning? 13:39.570 --> 13:49.738 [SPEAKER_03]: You'd be the company for five months, so this would be something that's on your mind in the early days, but I'm also curious if even in this short time, if there have been interesting areas where you've had to fight scale as you've grown. 13:50.712 --> 13:59.144 [SPEAKER_01]: I think scalability here, the good thing about us is scalability is usually constrained by things that you take some time to build. 13:59.724 --> 14:06.133 [SPEAKER_01]: In the era of LLMs and AI, software is much more easier to prototype and build than hardware. 14:06.854 --> 14:10.857 [SPEAKER_01]: And I think the good thing about robotics currently is that hardware is in commoditized. 14:11.157 --> 14:17.202 [SPEAKER_01]: We are seeing that hardware has become very good and become very cheap, so we don't actually focus on building the hardware at all. 14:17.702 --> 14:25.508 [SPEAKER_01]: And that's I think the main main decision that we took while we built this company, while we started this company that has helped us being more scalable. 14:25.588 --> 14:28.831 [SPEAKER_01]: So right now our

focus is on scaling data. 14:29.731 --> 14:31.573 [SPEAKER_01]: Scaling data happens with scaling people. 14:31.773 --> 14:35.736 [SPEAKER_01]: So the more people you have that help you collect data, the more data you will get. 14:36.498 --> 14:40.641 [SPEAKER_01]: and then that data essentially the higher volume of data you have trains better models. 14:41.101 --> 14:46.645 [SPEAKER_01]: And once you have a good model, the unique value proposition we have about a model says that they are hardware agnostic. 14:47.066 --> 14:51.549 [SPEAKER_01]: They can adapt to any robot hardware in 20 to 25 minutes of extra training. 14:52.109 --> 14:56.493 [SPEAKER_01]: And after that, like the hardware is not being built, it's being bought. 14:56.553 --> 15:02.258 [SPEAKER_01]: So our models can essentially go on any hardware, and then we can deploy at any place or any time. 15:02.778 --> 15:07.062 [SPEAKER_01]: And that essentially preserves the scalability facet even in a deep tech company. 15:07.602 --> 15:13.487 [SPEAKER_01]: Because for example, your chat GPT can work on any laptop, that idea that these models can work on any robot hardware. 15:13.507 --> 15:18.792 [SPEAKER_01]: So we're never constrained with like hardware or we're not constrained by shipping time or we're not constrained by 15:19.332 --> 15:21.834 [SPEAKER_01]: the time to deploy in any place in the world. 15:24.115 --> 15:30.619 [SPEAKER_03]: So, yes, as you step out on the balcony and look across all that you've built thus far with intelligence factory, what are you most proud of? 15:31.938 --> 15:41.304 [SPEAKER_01]: I will say the team, I know it's quite young and that we haven't had enough time with everyone until now, to be able to say that, okay, this is the best team I've ever built. 15:41.684 --> 15:50.630 [SPEAKER_01]: I don't think that will ever be the case, but it's just the amount of effort that we have put me and my co-founder also I would like to shout out my co-founder easily running all the technical interviews. 15:51.433 --> 16:02.779 [SPEAKER_01]: the amount of effort that we put into hiring and then now I look back at the team that we built and how excited about their art of automation and how excited how smart they are and how everything is coming together very slowly. 16:03.179 --> 16:15.286 [SPEAKER_01]: We obviously have a long way to go very pretty company and we have aims of being one of the biggest companies in the world but already I can see that the team is starting to integrate well and I think it's something that is very satisfied by seeing. 16:17.255 --> 16:18.698 [SPEAKER_03]: Okay, let's flip the script a little bit. 16:18.718 --> 16:22.364 [SPEAKER_03]: Tell me about a mistake you made and how you and your team responded to it. 16:29.164 --> 16:52.973 [SPEAKER_01]: One of the mistakes that didn't happen but it was going to happen was again I think within hiring we were sometimes we have this ability just as humans to overindex on credentials and I think during some process some parts of this process we did overindex a little bit more on credentials and we made offers that would have been in the long term damaging to the company. 16:53.653 --> 17:02.681 [SPEAKER_01]: and ultimately that didn't end up working out, so we got saved by this coincidentally, but I think that could have been a very major mistake from the company side. 17:03.181 --> 17:08.906 [SPEAKER_01]: But I think if you want me to talk about failures, I think the better sort of case here is my previous company. 17:09.667 --> 17:11.649 [SPEAKER_01]: So Kyle Labs is setting up a bit of context. 17:11.909 --> 17:14.973 [SPEAKER_01]: We were working on AI and robotics for material discovery. 17:15.553 --> 17:17.175 [SPEAKER_01]: This is quite a hard space to build in. 17:17.315 --> 17:18.716 [SPEAKER_01]: There's multiple reasons for that. 17:19.357 --> 17:30.288 [SPEAKER_01]: But I think we worked on it for 18 months and I think we got good results, but eventually I think the market for this technology didn't really exist and I think it took us way too long to figure that out. 17:30.649 --> 17:32.651 [SPEAKER_01]: And I think there's a few reasons for that. 17:33.151 --> 17:38.575 [SPEAKER_01]: I think the two biggest things that are important for a startup product market fit and found an idea of it. 17:39.236 --> 17:47.182 [SPEAKER_01]: These are the two things that someone has to quantify extremely early in order to say that they start up good and have potential of being successful. 17:47.802 --> 17:50.124 [SPEAKER_01]: So let's go to the first part product market fit. 17:50.624 --> 17:54.727 [SPEAKER_01]: I think what we made the mistake in Kyle was that we fit a solution to a 17:55.848 --> 17:59.070 [SPEAKER_01]: So you could people could ask, how do you actually do that? 17:59.110 --> 17:59.511 [SPEAKER_01]: How do you feel? 17:59.531 --> 18:00.391 [SPEAKER_01]: The solution to the problem. 18:00.832 --> 18:12.400 [SPEAKER_01]: Essentially, when you're engineer, especially working on deep tech, you always have graduate with this cool idea that you want to use and you just try to find a problem to it. 18:12.760 --> 18:17.243 [SPEAKER_01]: For example, in our case, my co-founder, he was a chemist from Cambridge. 18:17.723 --> 18:26.246 [SPEAKER_01]: and I was a robotics, a roboticist, from ETH, so thinking of combining these technologies because like, oh, we couldn't build robots for live automation, right? 18:26.687 --> 18:27.487 [SPEAKER_01]: That would be really cool. 18:27.887 --> 18:31.789 [SPEAKER_01]: But that was already a solution that we had in our head that we were trying to fit to a problem. 18:32.289 --> 18:36.270 [SPEAKER_01]: So we were looking at, oh, should we do this for like material discovery? 18:36.290 --> 18:37.931 [SPEAKER_01]: Should we do this for drug discovery? 18:38.471 --> 18:39.752 [SPEAKER_01]: And that already is a big problem. 18:40.212 --> 19:04.105 [SPEAKER_01]: I think the first thing you

have to do is actually figure out what the problem is before you build a solution and I think that was the first problem and then the other one was found right here if it were eventually in a space like robotics and AI for material discovery, it becomes you have to sell something and whatever you sell your die company so when you do AI for material discovery and find a IP or something of a material. 19:04.805 --> 19:08.046 [SPEAKER_01]: And if you don't have buyers for it, you have to scale up. 19:08.186 --> 19:10.367 [SPEAKER_01]: You have to build that material into a reactor or something. 19:11.087 --> 19:13.587 [SPEAKER_01]: And I think that's where the gap existed. 19:13.667 --> 19:18.349 [SPEAKER_01]: Where we, this company became a process engineering company very, very fast. 19:19.069 --> 19:21.870 [SPEAKER_01]: And neither me or my co-founder had the background to back it up. 19:22.410 --> 19:25.271 [SPEAKER_01]: Identify people who would join us who would strengthen the team. 19:25.831 --> 19:27.831 [SPEAKER_01]: And I think that's what eventually led to the downfall. 19:27.891 --> 19:30.772 [SPEAKER_01]: And I think that sort of covers the second part, but just found a idea of it. 19:35.232 --> 19:36.312 [SPEAKER_03]: Let's move forward then. 19:36.352 --> 19:37.093 [SPEAKER_03]: This will be exciting. 19:37.113 --> 19:44.995 [SPEAKER_03]: Your five months old, beginning to the where you want to prove what you've built, I'm curious what the future looks like for intelligence factory for. 19:45.475 --> 19:53.037 [SPEAKER_03]: Where the industry is going, like you mentioned, the hardware is no longer the bottleneck, data, and all the things, what does the future look like? 19:54.887 --> 20:16.822 [SPEAKER_01]: robotics is improving at a base where different parts of the technical stack we are seeing improvements in them, a significant improvements in them and we are a product based company so our company benefits of from any improvement in the stack which gets us closer to deployment because eventually we essentially were able to leverage them and build it into our stacks so we can get closer to deployment reliably. 20:17.322 --> 20:27.768 [SPEAKER_01]: But I think what's happening right now is that are we are looking at all these advancements and we are trying to leverage that into our stacks so that we can then go and deploy. 20:28.128 --> 20:34.752 [SPEAKER_01]: And I think in the shorter term, we are focused on building these models that are really good at one task as I explained before. 20:35.132 --> 20:41.296 [SPEAKER_01]: So you to pick and pack, then you to plug in and plug into cleaning, then you to different sorts of two use or folding clothes and 20:41.976 --> 20:51.543 [SPEAKER_01]: We deploy these one in one task use cases, so we deploy in a warehouse and a grocery in all places where one of these automating just one of these tasks is extremely useful. 20:52.103 --> 20:59.609 [SPEAKER_01]: And as we do that, I think what happens then is we collect a lot of high quality data, both from our deployments and the data that we have used to train these models. 21:00.149 --> 21:03.872 [SPEAKER_01]: And those data combines into the model and increases its action space. 21:04.412 --> 21:10.636 [SPEAKER_01]: At some point, we get to a point where our models' action space is big enough that it's generalizable. 21:11.096 --> 21:15.439 [SPEAKER_01]: So it can do a big impact task, it can also do a plug-in and plug task, it can do a wiping task. 21:15.459 --> 21:28.547 [SPEAKER_01]: So that's a long term goal of the company, where with all the deployments we have essentially converge into a general performance manipulation model, but the medium-term outlook is to deploy multiple robots in industries with one task use cases. 21:30.978 --> 21:33.647 [SPEAKER_03]: Yes, let's switch to you who influences the way that you work. 21:33.988 --> 21:36.797 [SPEAKER_03]: Name a person or many persons or something you look up to and why. 21:37.905 --> 22:05.688 [SPEAKER_01]: You will find this answer a bit disappointing or not disappointing, but I will say it will be a little bit different To what most of the people will say I mostly look up to sports people so I think My sort of person I look up to for a long time has been Christian Ronaldo which to be fair is like quite common between people of our age Yeah, I think it's just dedication and discipline right if you're not like the most killed person If you're not the most talented person and you don't have the best opportunities 22:06.148 --> 22:07.169 [SPEAKER_01]: How do you become the best? 22:07.229 --> 22:09.871 [SPEAKER_01]: It's just pause zone to the dedication discipline and resilience. 22:09.911 --> 22:14.795 [SPEAKER_01]: So anyone who's anyone who embodies that sort of becomes a person I admire. 22:14.955 --> 22:17.477 [SPEAKER_01]: And I decided supporting many nights very early. 22:17.717 --> 22:23.081 [SPEAKER_01]: So I was like, yeah, I became aware of Christianity and all the first. 22:23.121 --> 22:29.446 [SPEAKER_01]: But any person inviting these skills and that their our famous or some such are our people that I admire. 22:30.844 --> 22:33.327 [SPEAKER_03]: Okay, last question, so you're getting on a plane. 22:33.787 --> 22:36.630 [SPEAKER_03]: Interesting next to a young entrepreneur who's built the next big thing. 22:37.010 --> 22:37.691 [SPEAKER_03]: They're jazzed about it. 22:37.711 --> 22:40.394 [SPEAKER_03]: They can't wait to show it off to the world and can we show it off to you right down the plane? 22:40.994 --> 22:43.637 [SPEAKER_03]: What advice to give that person having on down this road a bit? 22:45.153 --> 22:51.535 [SPEAKER_01]: I think first of all, if he's excited to pitch to me on a plane, I think one of the things is ticked off is his initiative. 22:52.115 --> 23:04.318 [SPEAKER_01]: I think as founders, we have to be prepared to take any opportunity that presents itself and sometimes it's in a weird position, like an airplane or in a toilet or whatever, but like, you have to scrap that so I will admire that. 23:04.818 --> 23:06.298 [SPEAKER_01]: And I think I will then analyze his speech. 23:06.338 --> 23:11.979 [SPEAKER_01]: I think a lot of the times, when I hear a wonderful speech and this is not coming from some 23:15.083 --> 23:18.586 [SPEAKER_01]: I will say that the problem statement is almost always missing. 23:18.766 --> 23:23.769 [SPEAKER_01]: People are very keen to talk about the cool things that they're doing, which is essentially the solution. 23:24.210 --> 23:27.112 [SPEAKER_01]: But I think it's very important to spend a little bit of time on the problem itself. 23:27.452 --> 23:30.915 [SPEAKER_01]: Why you actually build like this and what are the signals that got you to that? 23:31.516 --> 23:42.439 [SPEAKER_01]: I think the more you can talk about the problem and the more normal and intuitive it becomes to the listener that this problem deserves to be solved, the solution is that much easier to understand. 23:43.120 --> 23:48.381 [SPEAKER_01]: I think that's what I would look for in the pitch and then I think clarity of thought is also really important. 23:48.561 --> 23:54.103 [SPEAKER_01]: You think about deep technology specifically, there's people doing so many complicated things like building a efficient reactor. 23:54.603 --> 24:05.712 [SPEAKER_01]: building a fusion reactor, building robotics, building something for space, the simplicity in which you can explain your company is directly proportional to how value understand this space. 24:06.213 --> 24:09.795 [SPEAKER_01]: And I think this is also something that I look for in the people we are interviewing highly. 24:10.396 --> 24:14.759 [SPEAKER_01]: And I think it's directly proportional to how sophisticated the 24:18.002 --> 24:21.003 [SPEAKER_01]: And I feel that's a very good indicator of where this person stands. 24:21.123 --> 24:23.684 [SPEAKER_03]: I think all that's fantastic advice and things to think through. 24:23.764 --> 24:25.544 [SPEAKER_03]: We are, thank you for being on the show today. 24:25.744 --> 24:28.465 [SPEAKER_03]: Thank you for telling the creation story of intelligence factory. 24:28.925 --> 24:29.245 [SPEAKER_03]: Thank you. 24:31.646 --> 24:34.067 [SPEAKER_03]: In this concludes another chapter of Coat Story. 24:43.052 --> 24:45.775 [SPEAKER_03]: Code Story is hosted and produced by Noah Labhart. 24:46.256 --> 24:50.681 [SPEAKER_03]: Be sure to subscribe on Apple Podcasts, Spotify or the podcasting app at your choice. 24:51.662 --> 24:53.584 [SPEAKER_03]: And when you get a chance, leave us a review. 24:54.104 --> 24:56.147 [SPEAKER_03]: Both things help us out tremendously. 24:59.050 --> 25:00.151 [SPEAKER_03]: And thanks again for listening.