Yeah. It is 100% true, and I'll give you an example. These seven RFQs we're talking about that MAVIN is part of, we have to dumb down MAVIN to be in the middle of it. I mean, it's -- there's things that we have to do, but we can certainly do it, right? I mean, there's nothing new development. It's just new calibration, new firmware, new development for us as part of our ASIC, so it's not that big of a deal. But as you can imagine, right, as I always said, right, it is best-in-class, so far ahead. When you get into these RFQs, nothing has been thrown at us that requires us to meet it. If anything else, we've been brought towards the mean. We're not at one end of the bell curve anymore, right? We're kind of brought towards the median, towards everybody else, saying, how would you do this? What's your cost structure? What's your size? What's your performance? Right? So, yeah, you have to compete in that range, because they want to make sure that the advantageous solutions are, of course, size and power, things like that. But the base specifications of range and resolution, they want to make sure that you meet and exceed it. Whereas, all the requirements that we have, we don't really look for exceptions. Whereas I believe -- what I believe is, like, others have to have some exceptions into some of the things that they're asking for, in case that there was an actual incumbent, with that specs that we have to meet. So, it's clear to us like the gap that our competition has sometimes because the spec that we see that was created for the incumbent, right, it clears that we can do that, and this was your original requirement, we can meet that as well. So, again, you have to be humble. You work with them. They are the customer. You have to whatever their strategy is, if they develop a very specific software, like for example, the dynamics in LiDAR offers something a huge advantage, a very, very huge advantage, but it would take up a period of time for people to actually realize that advantage because they would have to work on software slightly differently. But if they want us to do a static -- one single static field of view because that's how their software has been written so far and they don't want to rewrite companies with the software, we can do that. We can give them the best that it's ever going to be. But if they need something else that actually eases their path for integration, of course, we support that. So, yeah, what was said about MAVIN, right, I mean, that's going to stand the test of time. It's going to be a long, long, long time before we have to redesign it. I think there's a question I recently got from somebody that I met about monostatic LiDAR, I may have mentioned long time ago, "Are you guys developing that?" And in this OEM meeting, I clearly said, what I have far exceeds what you need. I can meet your cost structure. I can meet your power structures. There's no need for that, right? So, it's a futuristic product that -- if there was volume then we would invest in it. But right now, we meet size, performance, exceed everything that you have. So, therefore, at this moment for MAVIN, we want to finish our B-sample. We want to get the industrialization done. We have the automation that's going to be placed in. We can get some samples for you, get the reliability test started. And that's the basis from which we're going to do. We're not going to enter a new redesign for that because there's no need for it at the moment, right? And I didn't get much pushback. So, I still believe the statement that's made is totally valid. I have no reservation in saying that.