Robert Scaringe25:26
Car is complex. Again, to ground this, when you see a vehicle, you see the finished surface. Even for me, when I was growing up, you'd think it's a small team of people putting this together. But to develop a car, there are tens of millions of engineering and design decisions necessary to execute a product. To do it in a reasonable time frame, a couple of years from scratch to complete car, you have many thousands of people working in parallel. That's the only way. The way we solve these really complex engineering problems, you have maybe five or six thousand people working in parallel. The reason that's important is that because there are so many people involved, a huge part of the effort is coordinating how decisions are made. You want the front of the car and the front trunk to feel like it was engineered by the same brain as the rear seat mechanism. Of course, they're not the same people. You want the team doing the drive unit to be connected to the team doing the software. So you create frameworks for how you make decisions. The success of any highly complex product like a car is ultimately a measure of how coordinated the teams are so that the decisioning feels consistent, so that it feels like a very small group of people did it.
Um, so that it feels like a very small group of people did it. That's what you want to present: it looks like 10 people designed this whole thing when in fact maybe 5,000 people worked on it. When you think about the number of decisions and engineering trade-offs and analyses necessary to complete the product, there are all types of development things that can go wrong. That's why we go through multiple iterations of prototypes and testing, to build hundreds of cars on the journey to the first saleable unit. That's largely controllable by us, meaning we have visibility to the health and status across thousands of different metrics on developing the product.
But then there are all the suppliers that make components. We make a lot of components ourselves. But take a headlight. We design the headlight, the lighting, the control systems. But a third party supplier makes it. That supplier has suppliers, tier two, tier three, etc. So when you look at the number of companies ultimately involved in making an R2, it's tens of thousands of companies. We have maybe 450 direct companies that we work with as our tier one suppliers. They all have anywhere from a handful to maybe 10 plus suppliers that feed them.
Have a handful to 10 plus. So just like really quickly becomes a huge number of companies involved and in stable supply chain environments, that's all right. So we don't have to spend time getting to know the mine that your raw material is coming out of. But in environments where the supply chain has lots of disruptions, suddenly you have to think about who's my tier four and who the tier four feeds a tier three that feeds a tier three that feeds tier one that feeds us. We experienced that first time when we launched R1. There are so many disruptions to the supply chain with CO that we had to get very skilled at understanding risk across all of our different tiers of supply. It's quite complex. And so the biggest risk with any program of this type is that you can't predict and you can't actually measure everything happening at every one of your suppliers. And this falls into big geopolitical challenges. So take a battery. Our batteries have nickel in them. 93% of the world's nickel comes from one country. It comes from Indonesia. Trade policy with Indonesia could have a dramatic impact on our ability to get nickel. And that's just one material in a battery. So extrapolate that out. There's a very large team that tracks these things and we had to learn all those skills. Those are skills you don't when you're starting a company you think I'm going to design an engineer. I don't think I'm going to build a team where we have mining expertise and we have shipping logistics expertise and we have people that are tracking shipping patterns in the ocean and seeing what's being disrupted by conflicts. I mean, the amount of complexity to manage all that is quite high and now we have all those capabilities. We built them, but I'd say that's the biggest risk is just supply chain disruption.