In short
Zipline’s autonomous logistics system for life-saving deliveries, focusing on why the drone is only a small part of the solution, and how they achieve safety, reliability, precision, and scale (140M+ miles, zero safety incidents).
Guests
Keller (Zipline co-founder; leads customer-obsessed product vision and early market fit) and Eric (systems engineering and safety; designs safety architecture, redundancy, and testing/validation).
Key claims
Zipline is not really a “drone company” because customers don’t care about drone tech; they care about app-based delivery. The aircraft hardware is ~15% of overall complexity; the rest is auxiliary software, maintenance, inventory, aviation/healthcare integration, and operations. They report 140M commercial autonomous miles, 2.5M deliveries, and zero safety incidents. University of Pennsylvania study: 51% reduction in maternal mortality; partners estimate 10,000–12,000 lives saved per year.
Notable examples
Rwanda launch (2016) after “illegal in the US” constraints; initial failure serving 1 of 21 hospitals for nine months; solar flare effects degrading GPS/GNSS; compute failover with two flight computers plus an arbiter; pod-based precision using GNSS plus onboard perception; solar flare navigation robustness and redundancy beyond GNSS; 24/7 operations driven by “patients get sick 24/7.”
Written by AI. May contain mistakes. Listen to the episode to check what was said.
Chapters
Tap a time to open that second in VOEarly Days in Rwanda
0:00 to 0:45
Learn about the initial challenges faced in delivering medical supplies in Rwanda.
“I remember being in Rwanda early days and going out and meeting with some of the doctors and lab techs that we were serving and asking for them, like, you know, how's it going?”
The Customer-Centric Approach
1:27 to 2:24
Discover how Zipline focuses on customer needs over technological aspects.
“But you don't like Zipline being described as a drone company, even though you're probably the largest autonomous drone company in the world right now.”
Overcoming Early Challenges
2:24 to 3:19
Hear about the challenges and misconceptions faced while launching Zipline.
“What is the underlying technology behind ZipLine?”
Legal Hurdles and Global Launch
3:19 to 4:08
Learn about the legal obstacles and the decision to launch in Rwanda.
“In fact, I think that that's a question you asked me when we started talking about this.”
The Complexity Beyond Drones
4:08 to 5:06
Understand the additional systems required for successful operations.
“And then the other thing when it comes to how to think about Zipline as a company, when we launched in 2016, we were like, we have this really cool drone.”
Feedback and Market Fit
5:06 to 6:40
Explore how customer feedback shaped Zipline's service expansion.
“The physical drone, the hardware of it, is only 15%.”
Scaling Operations Globally
6:40 to 7:42
Discover how Zipline grew its service to thousands of health facilities.
“And so having that really beachhead market where there's a real problem being solved and when your customer is telling you that their main feedback is they want more of your service, it's like, that's a good sign.”
Impact on Maternal Health
7:42 to 8:06
Learn about the significant reduction in maternal mortality rates due to Zipline.
“So half as many moms losing their lives in childbirth.”
New Partnership with U.S. State Department
8:06 to 9:27
Understand the strategic partnership aimed at expanding Zipline's impact.
“In December, we announced a$550 million partnership with the U.S.”
Lessons from a Decade of Operations
9:27 to 10:10
Hear about the unexpected challenges learned over ten years in operation.
“But it also means that it will make it possible for the U.S.”
Show all 30 chapters
Navigating Unique Challenges
10:10 to 11:15
Discover how Zipline addresses solar weather impacts on navigation.
“We started off delivering lifesaving products, right?”
Safety and Reliability Innovations
11:15 to 13:19
Learn about safety measures and redundancy systems developed by Zipline.
“Tell us about what you've learned about safety today and specifically about the compute failover system that you have.”
Testing and Quality Assurance
13:19 to 14:01
Explore the rigorous testing processes that ensure Zipline's reliability.
“the two and a half million deliveries and 140 million miles flown with no safety incidents.”
Robust Testing of Aircraft Components
14:01 to 17:30
Learn about the rigorous testing processes for Zipline's aircraft components.
“So you mentioned that the aircraft is only 15%.”
Operating in Extreme Conditions
17:31 to 19:22
Explore how Zipline makes decisions on flying in extreme weather conditions.
“And like there are tradeoffs to be made, you know, and obviously your customers would prefer that you fly at all times.”
Achieving Safety Goals
19:23 to 19:49
Zipline aims to be twice as safe as Waymo, emphasizing their commitment to safety.
“and somewhere between two and six fatalities, depending on what country you're talking about.”
Precision Delivery Mechanism
19:50 to 22:52
Understand the technology behind Zipline's precise package delivery system.
“that testing that Eric is talking about?”
Expansion and Regulatory Challenges
22:53 to 24:48
Learn about Zipline's journey in expanding to the US and navigating regulations.
“So it's own survey and like know exactly where it's delivering even at night.”
Infrastructure and Fleet Management
24:49 to 28:00
Discover how Zipline manages a fleet of autonomous aircraft for efficient delivery.
“What was the sort of regulatory path that you had to go through?”
Scaling Challenges in Logistics
28:00 to 29:24
Learn about the complexities Zipline faces as it scales up deliveries.
“well, you know, what about, you know, how humans used to solve this problem?”
The Future of Autonomous Deliveries
29:24 to 31:29
Discover how Zipline's autonomous systems change the landscape of deliveries.
“It's like, wow, okay, everything about the way we've been solving the problem is going to break.”
Transforming Air Traffic Control
31:29 to 33:32
Explore how Zipline is influencing the future of air traffic control with innovation.
“So like, you know, Elon talks about designing the machine that builds the machine.”
Challenges in Air Traffic Management
33:32 to 35:58
Understand the pressing issues in air traffic management and the need for modernization.
“It's like that one company solving this problem for themselves is not going to solve the problem for the industry.”
The Case for Vertical Integration
35:58 to 37:41
Learn why Zipline opts for vertical integration over outsourcing components.
“The labor isn't available to do it even if we wanted to.”
Building from Scratch: The Zipline Approach
37:41 to 40:04
Discover the reasons behind Zipline's decision to build their own components and systems.
“So, you know, part by part, you sort of like rip it out.”
Collaboration Across Disciplines
40:04 to 42:00
Explore the importance of collaboration in addressing complex engineering challenges.
“be like, you and I are pulling an all-nighter tonight.”
Questioning Requirements and Simplifying Design
42:00 to 44:40
Learn how questioning every requirement and simplifying designs can lead to a more reliable product.
“Like question every requirement is like this is like so profoundly and deeply true.”
The Future of Delivery: Expanding Zipline's Vision
44:40 to 49:16
Explore Zipline's ambitious goals for scaling delivery systems and the market potential behind them.
“Is there a version of the future in which instead of delivering life saving medicine and cheeseburgers, you're delivering human beings?”
The Shift in Delivery Economics
49:16 to 52:06
Understand how the cost of delivery is changing and its implications for logistics and customer experience.
“And so I think this change is inevitable.”
Building the Future: Infrastructure and Innovation
52:06 to 55:00
Discuss the importance of innovation in infrastructure and the need for a bold vision for future developments.
“know, that's probably the number one comment.”
Transcript
Automatic transcript. May contain errors.0:00Keller Rinaudo Cliffton:I remember being in Rwanda early days and going out and meeting with some of the doctors and lab techs that we were serving and asking for them, like, you know, how's it going? What do you think? What's your feedback? Here I am kind of, you know, up and coming, you know, learning engineer thinking they're going to say something about the drone or some of these things. And the main piece of feedback that I received was people get sick 24-7. Why are you guys only open 12 hours a day? Right.
0:24Eric Watson:Especially when you're delivering life saving blood.
0:26Keller Rinaudo Cliffton:Yeah, exactly. And so that was a really key insight for me where it's like, man, we've found product market fit in a market where, yeah, our product wasn't great yet, but it was solving a real need. And so having that really beachhead market where there's a real problem being solved. And when your customer is telling you that their main feedback is they want more of your service. It's like, that's a good sign.
1:03Eric Watson:Welcome, Keller and Eric, to the show. You guys have been working at Zipline for a long period of time. Keller is the co-founder. And Eric, you are in charge of systems engineering and safety. And we got lots of things to talk about in this whole world of drones, drone systems, and how you guys started in this hardware space before LLMs even started. So we have lots of questions. Awesome. But you don't like Zipline being described as a drone company, even though you're probably the largest autonomous drone company in the world right now. I mean, we've always wanted to be an extremely customer-obsessed company, and the reality is none of our customers care at all about drones.
1:45Eric Watson:Our goal was always to build an automated logistic system for Earth and to approximate teleportation. And all the customers who are living on Zipline today, they really don't care about the technology operating behind the curtain. What they care about is their ability to download an app, open it up, see a huge number of different brands and amazing restaurants that they want to shop with, and then click a button and have it delivered to them five minutes later. So we've always really tried to focus on the experience rather than on the specific technology. Well, this show is about technology. We're excited about that.
2:23Eric Watson:This podcast is about technology. What is the underlying technology behind ZipLine? You started in 2011. You pivoted in 2014. This is way before anything related to AI robotics, foundation models, anything related to that. But you were before all of that and you're riding the wave of all of the things that have come afterward as well. Yeah, this was when starting a robotics company was the dumbest thing you could possibly do. You're talking to an investor in that time about, I mean, it wasn't easy and it was particularly hard because so many of those conversations, I mean, I was 23, 24, Eric joined the company around that time and we were starting to describe this vision of an autonomous logistic system for Earth that would be 10 times as fast, half the cost, zero emission.
3:15Eric Watson:one of the biggest problems when we're trying to raise money for that vision was investors would say, isn't this illegal in the US? In fact, I think that that's a question you asked me when we started talking about this. We weren't allowed to fly beyond a visual light of sight. I mean, we weren't allowed to fly at all, really. But yeah. And so the answer was, yes, it's illegal. And then most investors would be like, well, we don't invest in illegal things, so we're not going to invest. But for weird reasons, this is what basically took ZipLine down this path of like, well, if it's illegal in the US, then we can launch in other parts of the world where the value of the service would be extremely high.
3:47Eric Watson:Zipline decided to launch in Rwanda in 2016, delivering blood transfusions directly to hospitals and primary care facilities. This enabled us to have a use case that was so powerful that a government would work very closely with us to make it happen. Make it legal. And to make it legal, or at least make an exemption to their existing kind of regulatory framework. work. And then the other thing when it comes to how to think about Zipline as a company, when we launched in 2016, we were like, we have this really cool drone. We put all this work into designing this really cool aircraft. And it has all these great fundamental features.
4:24Eric Watson:And when we launched, it was a total disaster. Because the reality, what we learned in that first year, for the first eight, we'd signed a contract to serve 21 hospitals. And we served one hospital for the first nine months. And Eric in particular, how much did you sleep during those times?
4:40Keller Rinaudo Cliffton:I spent a lot of time in Rwanda and didn't sleep a lot.
4:43Eric Watson:And then when you're in the US, we'd get woken up at midnight because that's when the distribution center was turning on and everything would be broken. Nothing was working. It was totally desperate, constant all-nighters and working through the weekends because we'd made this big error, which was the thinking that the cool vehicle was the majority of the solution. What we learned during that first year is that the drone is 15 % of the complexity of the solution. The physical drone, the hardware of it, is only 15%. We had to build so many auxiliary software systems, maintenance systems. How do we hold the inventory and do inventory management?
5:17Eric Watson:How do we integrate with a national civil aviation authority, which we'll talk more about? How do we integrate with a national healthcare system? How do we do ordering and demand management? We had to build out all of these other parts of the overall logistics system. So this is the reason I think a lot of people might look at Zip1 and be like, wow, it's a cool drone company. They build a cool aircraft. The reality is the aircraft is like 15 % of the solution that's required to build something that just feels like magical, reliable teleportation 24-7, 365 to the now hundreds of millions of people who depend on the service.
5:50Keller Rinaudo Cliffton:Speaking of 24-7, I remember being in Rwanda early days and going out and meeting with some of the doctors and lab techs that we were serving and asking for them like, you know, how's it going? What do you think? What's your feedback? Just really being customer obsessed and wanting to optimize the product. And, you know, here I am kind of, you know, up and coming, you know, learning engineer thinking they're going to say something about the drone or some of these things. And the main piece of feedback that I received was people get sick 24-7. Why are you guys only open 12 hours a day? Right? And so.
6:21Eric Watson:Especially when you're delivering life-saving blood.
6:24Keller Rinaudo Cliffton:Yeah, exactly. And so that was our, you know, you got to start somewhere, right? So we started being open 12 hours a day and trying to expand and grow from there. And so that was a really key insight for me where it's like, man, we have found product market fit in a market where, yeah, our product wasn't great yet, but it was solving a real need. And so having that really beachhead market where there's a real problem being solved and when your customer is telling you that their main feedback is they want more of your service, it's like, that's a good sign.
6:49Eric Watson:Yeah, we were 24-7 within the first year. So we went 24-7. We're now 24-7, 365. I mean, on Christmas Day, I usually call all of our different distribution centers to thank them and check in with them. So there is no day when these facilities don't depend on... We went from serving 1 to 20 to 500, now to 5 ,000 hospitals and health facilities across the world, across eight countries that are served by the system. It's become the largest commercial autonomous system on earth. Can you size that for us, the largest system on earth? Just crossed 140 million commercial autonomous miles, which, I mean, how many times?
7:23Eric Watson:I think that that's like to the sun and back.
7:25Keller Rinaudo Cliffton:One of the things that I like is every road in the United States, there's a lot of roads in the United States, driving on every single road more than 30 times. Wow. That's a lot.
7:34Eric Watson:That's a lot, just to put it in perspective. You know, seeing the impact that that system is now having across all these eight countries. I mean, University of Pennsylvania just published a study showing a 51 % reduction in maternal mortality thanks to Zipline. So half as many moms losing their lives in childbirth. We have, you know, across all of the different use cases of Zipline serves, some of our partners estimate that we're saving between 10 ,000 and 12 ,000 lives a year. And that impact is growing exponentially as we're now expanding, especially as a result of this new partnership we have with the U.S.
8:05Eric Watson:State Department. What is that partnership with the State Department? In December, we announced a$550 million partnership with the U.S. State Department to expand the impact of Zipline's life-saving service across a lot of the countries where we're already operating. So with USAID being shut down, the U.S. was really seeking new ways of engaging in these countries and helping save lives in these countries, but they wanted to do it in a way that would accelerate the economies of these countries and help the U.S. economically. And so the new strategy they're calling commercial diplomacy. The idea is that we want all of the developing world should be built on top of U.S.
8:39Eric Watson:AI and robotics technology. We should be going and economically helping. We should be bringing the best that the U.S. has to offer. The interesting thing is when you talk to these countries about what they want, they'll tell you they are sick of low-quality aid provided by NGOs for free because these services engender dependence and prevent economic growth in the countries. What they want is high-paying jobs, entrepreneurship, technology. And so the U.S. is going through a big strategic shift where it's like, well, we have that. We have those things. So let's basically go out and incentivize these countries to adopt that kind of infrastructure, make sure that as these countries are accelerating, they're doing it using U.S.
9:22Eric Watson:robotics and AI technology. And this is something that will be great for those countries. It saves lives. It saves them money. But it also means that it will make it possible for the U.S. to secure our lead in manufacturing and robotics over the decade to come.
9:35Keller Rinaudo Cliffton:I'm curious about, you know, you guys, because you now run the largest autonomous system in the world and you launched it 10 years ago at this point. So you've been in production for 10 years. You've learned a lot of stuff that your average engineer sitting behind a computer screen has no idea they're going to run into when they try to deploy AI into the real world. And so I'm curious what some of those lessons learned are. And maybe one way to ask the question is, what popped up over the last 10 years that you never would have guessed you needed to be good at when you first started launching these systems in 2016?
10:09Keller Rinaudo Cliffton:Yeah. We started off delivering lifesaving products, right? And our customers need lifesaving products all the time in all weather conditions. And you would think it's wind, these things. But one of the weirdest things is actually solar weather. So there's solar flares that happen on the sun. So they're basically big explosions that send radiation to the Earth. They can mess with the ionosphere, and that can cause basically the RF signals coming from GPS satellites to be faster, slower than you expect. And that can lead to degradation and challenges in navigation systems. And so here's one example that when we were starting off, we didn't think that this was going to be something we have to figure out.
10:48Keller Rinaudo Cliffton:But we actually have gone pretty deep in this space. And really, it's two things. One is designing our navigation system and our GNSS systems to be robust to these conditions to ensure that we can still know where aircraft are with centimeter level precision in those conditions, in those challenging solar flare times, as well as designing the system to have redundancy beyond GNSS such that if things get really bad, we can still safely operate.
11:14Eric Watson:Eric, you're in charge of safety. Tell us about what you've learned about safety today and specifically about the compute failover system that you have.
11:24Keller Rinaudo Cliffton:Yeah, yeah, absolutely. I mean, there's so many things that we've learned over the last decade of operating, you know, the system in the real world. One of the things that we're proud of is how we've developed, to your point, compute failover. So there's a flight computer, flies the aircraft, lots of sensors come into this, into this computer, and that basically does a lot of math and sends commands to actuators, right? So motors, control services, these things. So this is the brain that flies the aircraft, right? One of the things that we've learned is you need to assume that any part of the system can have a fault, can have a hiccup.
12:00Keller Rinaudo Cliffton:Something can go wrong. And that's how you really design something to be robust, reliable, and safe. So what do we do if this flight computer has a challenge? It could be a software challenge. It could be a connector challenge. It could be these different things.
12:12Eric Watson:Bitflip due to solar radiation.
12:13Keller Rinaudo Cliffton:All kinds of things, right? And so what we've done is we have two flight computers. And both of these flight computers think that they're flying the aircraft at any given point in time. They all are receiving all the information from the sensors. They're all sending commands to the actuators. And there's like a kind of a third arbiter, a little computer that is monitoring the health of those two and telling everyone every other node on the aircraft who to listen to, who's actually in charge. What if the arbiter fails? If the arbiter fails, then the primary computer that was flying just keeps flying.
12:43Keller Rinaudo Cliffton:Right. So one's in charge. And if the thing that's monitoring its health fails, then now we say, OK, like, you know, now we're just going to keep flying on the thing that was good. and we're going to keep flying the mission. Two heads are better than one. Yeah, it's something we're really proud of. We actually had one of these events happen a couple of weeks ago, where we had after a delivery, we delivered the package to the customer and then we had a hiccup on the main flight computer and we switched over to the backup. The aircraft flew itself home, landed. Everything was totally fine. So just designing the systems to be robust and reliable through and through is how you get the two and a half million deliveries and 140 million miles flown with no safety incidents.
13:23Eric Watson:And a lot of what Zipline's doing, it's not like, oh, this is totally revolutionary. No one has ever thought about having a secondary flight computer. That's how a Boeing 777 works. But the cost of a flight computer on a Boeing 777 is in the millions of dollars. And so a lot of what Zipline's having to do is take a lot of the best ideas that you can see in aerospace safety. Best practices from aerospace. Experience best practices. And then you've got to figure out how to build that using components coming out of it smartphone supply chain. Yeah. You can do it for, you know, tens of dollars or hundreds of dollars.
13:54Eric Watson:You can achieve similar levels of safety to traditional aerospace, but you can move 100 times as fast at 1 ,100th of the cost. Yeah. So you mentioned that the aircraft is only 15%. Describe the other 85 % in like layers and maybe go down deep in some of your systems that are really, really sophisticated. like I know this because of being a board member and like the detect and avoid systems?
14:21Keller Rinaudo Cliffton:So, you know, how do we test? Why do we test? Really, the way I think about it is there, maybe first of all, we're not a software company, right? We're a real world AI robotics company. And so there's electromechanical systems out in the real world. So there's hardware test aspects, there's software test aspects, and there's the integrated system test aspects. We have a lot of different environments that we test, a lot of different approaches. I'll name a few of them. you know on the hardware side we do a lot of component level testing uh halt testing highly accelerated lifetime testing where we're taking components maybe it's a motor these kinds of things and we're putting them through you know through hell right we're putting them through all kinds of challenging conditions making it rain making it hot making it human making it corrosive all these things while we're exercising you know while we're spinning the motor while we're moving things all of the things right uv like you name it and just to give a context for a scale i mean
15:10Eric Watson:there are 700 unique components on the aircraft designed from scratch by zipline we are designing not just the flight computer from scratch, the power distribution board, the motor controllers, the battery, the battery management system. The pod is the smaller robot that we're using to actually make deliveries to people's homes. There's an entire NVIDIA GPU powered flight computer on the pod. We're building the electronics that go into the docking station where the zip is flying in and out of. All of that, even the electric motor being designed from scratch by a zipline because we need a thrust to weight ratio that is not available in off-the-shelf electric motors.
15:48Eric Watson:So you have to design something from scratch. So 700 unique components, 43 major sub-assemblies on the aircraft, all then coming together on the manufacturing line that you both have gotten to visit and getting assembled into one overall aircraft. But anyway, that's the scope. So for each of those components. Yeah, right.
16:03Keller Rinaudo Cliffton:Going through this type of testing. And thinking about other industries, oftentimes when I talk to people from maybe automotive or aerospace and some of these like hey how do you think about reliability challenges and a common answer is like well i asked the supplier what the reliability of the part is yeah i'm like okay cool like what if we're the supplier you know so anyway so we're that vertical integration where we have component testing on the ground we have system testing uh on the ground where we're taking full aircraft for you know and as well as other parts of the of the system and putting them through vibration tables wind tunnels thermal chambers that you can walk into like all these things in order to understand how is this going to break, right?
16:39Keller Rinaudo Cliffton:More than just, is it good enough? Like, we want to know how it's going to break. And then we can understand, okay, cool. Like, let's make it better. Or maybe it's like, oh, that's not too worrisome. Like, great. You know, we didn't break any of the ways we were worried about. It broke in that way. Fantastic. So, like, we don't just want to say, we ran the test campaign and nothing failed. We're done. It's like, no, no, let's take this thing to failure, right? Let's see where the limits are.
16:58Eric Watson:49 degrees Celsius, which is very hot.
17:00Keller Rinaudo Cliffton:Hot, cold. Down to negative 25 degrees Celsius, which is very cold. All the things.
Read the full transcript
17:05Eric Watson:You don't fly anywhere at 49 degrees. We do. You do? We wouldn't test at 49 if we're not worried about it. Where are you flying at 49? I think Phoenix during the summer.
17:13Keller Rinaudo Cliffton:Phoenix during the summer, yeah. And then where's minus 25? It's in northern parts of the United States. Actually, can I ask you guys how you think about that? I could imagine a different version of the world where you guys are like, hey, look, if it's too hot, we're just not going to fly. Totally. And if it's too cold, we're just not going to fly. And if it's raining too hard, we're just not going to fly. Yeah. And like there are tradeoffs to be made, you know, and obviously your customers would prefer that you fly at all times. But how do you think about those tradeoffs?
17:40Eric Watson:The easiest way to think about the tradeoff was because of the use cases that Zipline started with. That's right. That makes sense. Which is basically like saving lives. Yeah. You can count on us with your life and the lives of your loved ones as long as the sun is shining. Yeah. It's not super compelling, you know. You develop the capability because you had to for the initial use case. ZipLine would fly. And in fact, I mean, for the first couple years, we took a lot of risk. I mean, we would basically fly. We were like, look, if it's a lifesaving delivery happening and there's someone whose life is on the line, we're going to go for it.
18:14Eric Watson:And we had a civilization authority that was generally a great partner with us on that front. We took a lot of risk. We learned a lot. And almost always it worked out in favor of like we saved the person's life. And the worst thing that could happen was we had a Paraland, which is the kind of like zip line safety mechanism of last resort, is we can pull a parachute on the aircraft and bring it gently to the ground. But we learned a lot. It happened very often in the first few years. Yeah. Very, very rare today. I mean, to put it into perspective, our original goal was to be 10 times safer than cars.
18:45Eric Watson:Actually, Alfred was the one pushing in our last board meeting. He's like, that's a BS goal. We need to be two times safer than Waymo. And so Eric literally went and reset the goal. And now, like, the Zipline's target for the end of this year is to be two times safer than Waymo. He's like, cars, that's like archaic technology. Waymo, I think, is about 10x, right? 10x cars. So our goal is to be 2x safer than Waymo. Yeah. It's not the right comparison. You're flying. You have to be safe in the air, not safe on the ground. I think it depends. We're substituting something that's typically going in cars, so it's, like, debatable.
19:16Eric Watson:But, you know, suffice it to say, I mean, we now have 140 million commercial autonomous miles and zero safety incidents. If you were to drive 140 million miles, you would have 600 accidents, 100 injuries, and somewhere between two and six fatalities, depending on what country you're talking about. And this is why we really pride ourselves on picking the right use cases. It's life-saving, and it really makes a lot of sense to go do it. And also, by God, we're going to be as safe as humanly possible from an engineering and testing and validation perspective. We really take that. that's a deep part of the DNA of the company.
19:49Eric Watson:One last point, what is the outcome of all of that testing that Eric is talking about? The outcome of all that testing is we have individual aircraft in the commercial fleet that have flown more than a million commercial autonomous miles. And so I think people, that's just from an intuition perspective, a lot of people look at this and they're like, wow, it kind of seems maybe exquisite or fragile, probably very sensitive to like extreme conditions or weather. I mean, you know, raise your hand if you have a car that has a million miles on it.
20:18Keller Rinaudo Cliffton:It's pretty impressive.
20:19Eric Watson:These systems are already like way more rugged and durable and robust than people necessarily think.
20:25Keller Rinaudo Cliffton:Can I ask you about the precision? Like one of the things that blew my mind when I saw some of the, I haven't had a chance to experience in person, you know, a delivery. Gotta come, Pat. I know, I gotta go experience it. But just in watching the videos, the drone's a hundred feet up and it drops the package. It lowers the package to a, I don't know, a circle that's got a 18 inch radius or whatever it is, right? Like, how do you guys achieve such precision even when it's windy, even when it's raining? Yeah. How do you pull that off? First of all, the aircraft's about 100 meters up. 100 meters up.
20:57Keller Rinaudo Cliffton:Yeah. Yeah. There you go. It makes it harder. And, you know, the multiple layers, there's the delivery pod that comes down, right? So the delivery pod comes down. That's really the delivery and pickup, like precision part of it, right? So the the drone is hovering above it. You know, it knows where the target is. Maybe let's say it's it's this coffee table, for example. There wasn't a roof above us. This is this coffee table. And so the aircraft is going to hover above, but it actually needs to consider what the wind conditions are. Yeah. Right. So if the wind's blowing in one direction, then the aircraft's going to kind of be shifted upwind.
21:30Keller Rinaudo Cliffton:Right. It's going to shift in the direction to help with that with those wind conditions. And it's going to lower that delivery pod down. as Keller mentioned, we do take advantage of GNSS. So real-time connection GNSS, that gives you centimeter level confidence of where you are. But the thing is, we don't know the GPS coordinates of this table, right? It's not like someone came and surveyed the middle of the table and sent us the coordinates, right? No one wants to do that. So what we have to do is we kind of, that we use that to kind of get close, right? We're like, okay, here's the backyard.
22:02Keller Rinaudo Cliffton:Here's where we kind of know things that things roughly are. And then the job of this delivery pod is to be lowered down, you know, fight the wind conditions, fight these different things, and be able to use its onboard perception autonomy systems to identify where's the best place for me to leave the package, right? Like if there's a little table and there's a whole bunch of drinks, probably I shouldn't, you know, try and drop down on top of these drinks and make a mess. Maybe I should go to the ground right next to the table, right? And so it has these autonomous, you know, onboard real-time compute to be able to identify what am I looking at?
22:33Keller Rinaudo Cliffton:What am I seeing? And how can I find the best place to leave the package? And then come down, touch the ground, opens its doors, gets retracted back up. And there you go. The package is left on the ground and the delivery pod comes back up, stows and the aircraft flies back home.
22:46Eric Watson:A couple of big advantages. I mean, just to be specific. So that pod, it not only has its own NVIDIA GPU running its own AI autonomy stack. So it's own survey and like know exactly where it's delivering even at night. But it's also controlling its own position in the X and Y axis. So it can not just know, but then move. And the advantage of that architecture, which you can probably guess, but there are two huge advantages of doing it in this way. One is it's quiet. People have this perception of, I mean, first of all, most drones are really freaking annoying. Like the sound is just, it's basically the most grating annoying sound that could possibly subject a human to.
23:25Eric Watson:And so, you know, like we, ZipLine has a big team of aerodynamics, aeroacoustics, and controls experts. Every part of the vehicle is designed with sound in mind for the vehicle to be as quiet as humanly possible. We want it to be no louder than the sound of like gentle leaves moving in trees. And when the pod is delivering, we're keeping the main aircraft a hundred meters in the air. So it's like the thing that is creating noise is really far away. That's also a huge benefit from a safety perspective because the only thing that is coming anywhere close to you, your family, your pets, your kids, is something that is super cute and safe.
24:03Eric Watson:And it's really like a styrofoam, kind of like a cute anthropomorphic styrofoam... Tub? Tub. Yeah. How long was the technology tested outside the United States before you came to the United States? and what's the path to getting into the U.S. now that you're flying in Dallas and delivering packages there? We spent eight years, I think, right? About eight years. I mean, depending how you measure it, maybe like six to eight years. And then it was, I mean, we launched in Rwanda in 2016, our commercial service. And we really launched this kind of next generation home delivery service, the thing that's now like in sort of insane hyperscaling mode.
24:41Eric Watson:That only launched January of last year. So depending on how you measured it, you could even say it was like almost nine years. And then when you got to the US, was it just smooth sailing? What was the sort of regulatory path that you had to go through?
24:53Keller Rinaudo Cliffton:Yeah, I mean, we really started, I would say, you know, like meaningfully engaging with US, you know, FAA and other regulators in the US around 2020 or so. So it doesn't mean we didn't show up in 2025 and everything was smooth sailing. It was really a partnership of working through, as you mentioned in 2016, all of this stuff was, there was no pathways, kind of illegal as we joked earlier. And so, yeah, so it really was a partnership to identify, hey, we have shared goals, right? Our shared goals are safe and efficient airspace integration. And so while we have experience doing that successfully in different countries, we can bring some of that experience in.
25:34Keller Rinaudo Cliffton:We have opinions on how this should work. The regulators had opinions on maybe how they thought it should work. And so it was a partnership over the course of a couple of years to identify what those paths looked like and how we could kind of converge and align before we were able to execute on that.
25:46Eric Watson:And you had to show your ability to manage all these aircrafts that are flying. So you wrote systems, you built systems.
25:52Keller Rinaudo Cliffton:Yeah, I think it's a huge part of, you know, Keller's mentioning that the drone is only a part of the, you know, of the overall system, the overall complexity. What we're really building is an infrastructure layer, right? We're building an infrastructure layer that can enable instant access to products and you don't do that with one aircraft flying from one place to another place you do that with a network of charging locations hundreds of aircraft spread across an area that with the autonomous systems in the in the cloud that can understand where am i having demand where where do i have supply where do i have aircraft what's coming up is about to be the dinner rush what's the weather at these different locations how can i kind of self-balance these things, as well as how do I efficiently pull in people when needed, right?
26:37Keller Rinaudo Cliffton:So these aircraft are autonomous. They're operating. They don't require human intervention through these flights. But there are times in which it makes sense to alert a person that, hey, maybe there's an issue here, or the weather is a little bit, the wind is climbing in this area, right? So there are humans, trained aviation professionals that are monitoring our network, I would call it. They're fleet commanders. Fleet commanders. That's right.
26:59Eric Watson:We used to call them pilots, because when we originally launched in the US, the first regulatory permission we got was to fly one-to-one. So that meant that we had one pilot sitting in an office. Remote pilot in command. Remote pilot in command, who was sitting in an office basically just observing an aircraft do its thing. And again, it's exceedingly rare that a human should ever have to issue any kind of a command to a vehicle, but we would have one human watching one aircraft. Not great for unit economics. mechanics. But as Zipline proved out these systems, we went from one to one, to one to three, one to six, one to 20, one to 40.
27:34Eric Watson:We're now operating one to 100 and have plans to go well beyond that. One pilot manager, well, one fleet commander now. One fleet commander now. So yeah, we technically changed the name because I think pilot's confusing. So we're inspired by Ender's game. We now call this group of, this team of people at Zipline, we call them fleet commanders. And it actually says that in the FAA documentation. We say, fleet commanders shall do the following. And yeah, they are overseeing a group of 100 aircraft. And to me, this is like the exciting, cool thing about technology, because people think about like, well, you know, what about, you know, how humans used to solve this problem?
28:07Eric Watson:It's like, it's not, you know, the, it's cool how robots enable humans to like up level, right? Like the human is still getting to like strategically manage the system. It's just the human is now maintaining and commanding robots rather than like doing the actual work herself.
28:22Keller Rinaudo Cliffton:Now that you guys are kind of in hyper scale mode, you've solved so many problems in the last 10 or 15 years. What new problems are you running into? Yeah. I mean, what I would say like thematically, I mentioned earlier that, you know, getting to two and a half million deliveries, the, you know, the, oh, it only happens every couple of years. It's like kind of a one in a million chances. Yeah. These things start to matter, right? We're, we're on the path towards a million deliveries every day. And if you have a one in a million situation, it's going to happen every single day. Yeah.
28:49Eric Watson:Can I just, just, just to really make that clear. So it took Zipline from 2014, when we started building the original version of the technology to 2024 to do our first million deliveries. Was it the end of 2024? Maybe it was even early 2025, actually that we did. We had done a million deliveries in the cumulative history of the company. So it was almost a decade, maybe say about a decade to do a million deliveries. Zipline is now in the very near future going to be doing a million deliveries a day. And so that is definitely humbling. It's like, wow, okay, everything about the way we've been solving the problem is going to break.
29:29Eric Watson:The bar goes way, way up. And I mean, one specific example, maintenance becomes really hard. Like, you know, the scale of the problems, the number of vehicles that you're managing in the fleet, the cost of a screw-up or if a certain process is operating in very inefficient ways becomes extremely high. And so there's just high degree of criticality for all these systems. One interesting point, though, there are a lot of ways that these systems operate that I think people don't yet appreciate the advantages of autonomy. One good example is that the system wants to operate 24-7, and it does operate 24-7.
30:04Eric Watson:So I think people are used to logistics as generally being like, well, here are the hours when humans are driving trucks. That's not how these systems operate. They want to operate 24-7. They can be fully utilized. They can be as happily delivering at 2 a.m. and 3 a.m., delivering something so it's ready for you on your doorstep or in your backyard when you wake up at 6 a.m. before you go to work, as they are delivering at 2 p.m. They can deliver in five minutes. They are available 100 % of the time. We are soon going to be flying vehicles straight out of our factory in South San Francisco into commercial operation.
30:35Eric Watson:If you've seen Tesla Model 3s and Model Ys delivering themselves to customers, Zipline aircraft will fly straight from the factory into operation. It's a huge advantage from a maintenance perspective that as soon as a vehicle needs to go through some kind of proactive maintenance, it will fly itself to the maintenance depot. So the human can then quickly do whatever process necessary, and then the vehicle flies itself back into operations. We can also dynamically assign capacity in a metro based on what the system is seeing. There's no set home for a vehicle. It can go to wherever it's needed.
31:06Keller Rinaudo Cliffton:Yeah, I think to your question about, you know, getting to a million a day and what are the new challenges, I think, you know, Keller hit on some of them to the previous thought about the drone is only 15 % of the problem. Really, it's the way that we currently manufacture aircraft, maintain aircraft, support all these things, you know, troubleshoot problems. Like, the way that we do it today isn't going to work when we're at a million deliveries a day. And so there's like, okay, we need better tools, we need better software systems, we need better processes, we need better, you know, all these things.
31:34Keller Rinaudo Cliffton:So like, you know, Elon talks about designing the machine that builds the machine. And so, you know, this is really one of the things that I see Zipline tackling over the coming couple of years is we are going to be investing much more in the machines that build and run the machines.
31:52Eric Watson:I mean, from a scale perspective, I think the largest airline in the U.S. is doing about 5000 flights a day. Yeah. Zipline is going to surpass that in the next month. and when we get to a million deliveries a day, Zipline will be doing like somewhere between, I don't know, 40 and 80 times as many flights in the US in commercial airspace as all other airlines combined. And so it's obviously a different class, it's a completely different class of aircraft. It's a totally different kind of problem. But the reality is when you look at air traffic control, they don't make a distinction. And so there's also, when you talk about all the auxiliary systems that have to be built, there is a huge transformation that's going to have to happen in air traffic control as we start to realize that people are really excited about electrification of vehicles.
32:37Eric Watson:People are excited about autonomous vehicles. Reality is, as those transformations occur, there are going to be 10 times as many autonomous vehicles in the air as there are using these teeny, archaic, constrained things that we call roads. And so the sky is a big place. It makes sense to utilize it. You can give Earth back to humans. You can make neighborhoods quieter, safer, less pollution, less traffic. You can make huge improvements to Earth if we can more effectively utilize the sky. This is going to require huge transformation of how we think about air traffic control in the U.S. And it means that we need to design it with AI and autonomy in mind rather than the way it was designed, which was in 1950 using pencils and paper and note cards and like a human looking out trying to watch the airplane.
33:23Eric Watson:Are you helping the FAA design that?
33:26Keller Rinaudo Cliffton:It's really, yeah, I mean, what needs to happen is like collaborative innovation is one way to put it, right? It's like that one company solving this problem for themselves is not going to solve the problem for the industry. And so we are heavily involved in, I mean, first of all, a key part of the solution we believe is aircraft should be talking to each other. They should be telling each other where they are. They should be automatically detecting that, hey, there's a conflict on the horizon here. And so therefore we're going to, you know, you go up, I go down, right? These kinds of things. And our aircraft do that.
33:58Keller Rinaudo Cliffton:And we're working with other kind of, you know, other new entrants into the airspace with autonomous aircraft and autonomous drones to do the same thing, to make sure that our systems can talk to their systems and we can all collaborate to make sure it's efficient and safe usage of the airspace. Yeah. We're also, to your point, Alfred, working with regulators, working with standards bodies to take some of these best practice and innovations that we and others have developed and try and make them, you know, broadly accepted and utilized so that we can all collaborate and we can all, you know, safely and efficiently use the airspace.
34:28Keller Rinaudo Cliffton:Because you guys have developed a really sophisticated detective -
34:32Eric Watson:Yeah, because when we were launching in all these other countries, we had to build something from scratch. And so we built the thing from scratch. We provided all this software to the Civil Aviation Authority so that they could use it to monitor this entirely new class of autonomous vehicles in the airspace. Interestingly, there are multiple public companies in the United States that build air traffic control software that are worth more than$10 billion, right? So it's like, I often look at that. I mean, I think there are many companies inside ZipLine that are likely, it's like, oh, that's like a public company inside Zipline.
35:00Eric Watson:It's just having to get built from scratch. We're building it because every part of the ecosystem we sort of had to build from scratch to enable the overall technology to flourish. You know, air traffic control is an interesting, like the more you learn, the more disturbing it is. I mean, we're starting to see the impact. You know, you read about like, you know, a plane crashing into a helicopter in DC a few months ago. You read about two planes colliding on, I think, on a taxiway in an airport. I don't remember where that was a month ago. You're like, wow, why are all these accidents happening?
35:30Eric Watson:Turns out 50 % of air traffic controllers are over the age of 45. 20 % are about to retire. And nobody is going into air traffic control as a career path right now in the US. And so there's actually a huge labor crisis around these kinds of jobs. And so you have pressure coming from different angles for transformation is required. We cannot use a system that was designed for airspace in the 1950s. The labor isn't available to do it even if we wanted to. And also there is this giant influx of new technology, AI, and autonomous vehicles that are going to require us to transform how these systems work.
36:08Eric Watson:So you're a hardware company and a software company. You design your own operations, manufacturing. You design your own parts. You build your own aircraft. You write your own software. You do your own operations. This is a pretty vertically integrated company. Talk about the benefits of complete vertical integration versus buying component parts or buying component software and putting it all together.
36:33Keller Rinaudo Cliffton:And how you get people who come from such different disciplines and domains to see eye to eye and work together collaboratively. Yeah.
36:41Eric Watson:I mean, I think that interestingly, doing it is such an incredible pain in the butt that you would never do it. I have this flag over my desk that says we do this not because it is easy, but because we thought that it would be easy. And this is definitely like the definition of Zipline, you know, and it's such a pain in the butt, actually, that it's almost if you look at the history of all these hardware companies, they all try to not do it first. You can look at the Roadster, right? They're like, we're going to use a Lotus Elise chassis. We're going to buy the battery pack from a secondary supplier.
37:13Eric Watson:And we're just going to put the two together and it's going to be awesome. You know, kind of Roadster lost a lot of money and wasn't very reliable. Right. But like it was an important part of getting to the Model S. zipline when we started you know eric knows well we were like buying everything from suppliers we were like you know paying people to design different parts of the system for us or trying to buy off-the-shelf stuff and we crashed airplanes i mean at test sites and we just crashed and we crashed we realized wow this stuff is like super expensive and it's also totally unreliable and so you know part by part you're like all right well like rip that out we'll design the motor controller from scratch okay rip that out we're gonna have to describe you know design the GPS module from scratch, navigation system.
37:54Eric Watson:So, you know, part by part, you sort of like rip it out. And I think there's a fundamental realization, probably similar to the realization that happened that made the Model S possible is like, hey, if we want to build a really great specific product in this totally new area of technology, we're going to have to design every single one of these components from scratch to meet the specific requirements of this new area. You know, you might think, oh, like drones. I mean, there are already lots of drones because DJI makes plastic quadcopters and they make millions of them, and the US buys$20 million Predator aircraft that can fly 100 miles.
38:25Eric Watson:The reality is actually both of these systems are very unreliable and nothing is in a level of reliability and safety at unit economics that would work for this new industry that Zipline was trying to pioneer. And so we realized we had to go build an automotive grade solution. It has to be super reliable and it has to be extremely cost effective because you're competing against cars and motorcycles, which are actually really cost effective. And we've had a hundred years to make them reliable and cheap. So you never do it, I think intentionally, maybe just like slowly freak out and through desperation realize like, wow, we got to tear all this shit out and we got to build it all from scratch.
39:05Eric Watson:The advantage of doing it from scratch is speed and integration. And so our offices, you guys know because you've been, but when you visit Zipline's offices, we are all absolutely packed into sardines, into this small building where you have firmware engineers sitting next to, mechanical engineers sitting next to, autonomy engineers sitting next to, cloud infra sitting next to, aero, aero acoustics, guidance navigation controls, systems engineering, manufacturing, everything, everything in one place. And then our factory is a three-minute drive away. And so our team is like on the factory floor working, seeing parts get integrated into the overall system.
39:48Eric Watson:And then we have our test sites, which are just a short drive away. So you can go to the test sites, watch the vehicles flying, observe how the system is performing. Combining all these things together means that stuff is always breaking. Stuff's always going wrong, as Erica described. The advantage is when the thing goes wrong, we can basically go straight to the person's desk and be like, you and I are pulling an all-nighter tonight. Whereas if you're Boeing and something's going wrong with the battery on the 787, you're like going and suing a supplier and taking two years to try to figure out whose fault it is.
40:22Eric Watson:And it's three layers deep in the rat's nest cluster of how these procurement deals and supply chains work for aerospace is why it's so broken.
40:32Keller Rinaudo Cliffton:Yeah, I think Pat, to your kind of question there about getting these different discipline folks to work together. Yeah. I honestly think it's quite easy. It's easy when you have set up the way that Keller just mentioned, right? Like, first of all, everyone's rowing in the same direction. We all have the same goals. And when you can ground it in reality and it's tangible, then we're all just here to solve the same problems, right? So we actually, with the vertical integration, with having a very diverse team, we actually cut through a lot of the stuff, right? A lot of the things that happen were, oh, you know, that engineer won't tell me what the actual source code does because they said it's IP.
41:05Keller Rinaudo Cliffton:And so we don't actually know what the fault detection looks like. And you don't have any of that. You just like literally go walk over, sit next to the person's desk and be like, hey, we failed that test. Tell me about how this part of the system works. Oh, cool. Pull up the code. Great. Let's look through it. Oh, interesting. You're making that assumption. That's not how I designed it. Right. Cool. Let's get to the bottom of it. Right. And so this idea of just rapid collaboration where you're just, you know, the manufacturing team, the operations team, the engineering team are all just like really together is the way to solve these problems.
41:33Keller Rinaudo Cliffton:And I have found that it's actually not that hard, right? When you have those ingredients, it actually makes it, you know, makes it pretty fast and efficient.
41:40Eric Watson:And, you know, too, I mean, Eric saying that, it really makes you realize when you build these like complex, you know, AI and robotic systems that combine hardware and software, you really appreciate like the deep religious truth of how dumb requirements usually are. Question every requirement, which is, you know, the number one part of like Elon's algorithm they talk about at SpaceX. Like question every requirement is like this is like so profoundly and deeply true. You must have every team question every requirement. The requirement is always stupid. And you're like, well, you go to this team, that team, often you have to dig like two levels deep to realize.
42:19Eric Watson:But questioning every requirement is a fundamental part of getting through this. And then the other thing is delete the part. The most reliable part on an aircraft is the part that is not on the aircraft at all because you deleted it in the last design. That part will never fail. And you take a lot of inspiration from looking at like the Raptor 1, Raptor 2, Raptor 3, I'm sure you've seen those engines next to each other. And actually a lot of people who come to the factory now and get to see like the EV3 aircraft, you can see the EV2 aircraft, the EV1 aircraft, plus like the 10 different hardware versions that we built on the first version of Zipline's technology, you would just delete, delete, delete.
42:56Eric Watson:Like, you know, there's a huge amount of, it's really hard to delete things. It's an act of courage. No one wants to delete the thing. You look like an idiot if you delete the thing And then the system can't perform or doesn't work because you deleted the thing. But true confidence in the physics and the performance of the system enables you to start deleting things. It's a big advantage of having full stack integrated control of all of these systems. It makes it possible to question every requirement. It makes it possible to delete parts.
43:27Keller Rinaudo Cliffton:Yeah, I think first principles thinking is a huge part of that. I remember the platform one aircraft early days, it had a deployable tail hook is how it landed. So it had this big hooks like a meter long that would come down from the aircraft. And we had a line that would catch that and slow the airplane down as this kind of complicated contraption. And we had this idea that we should be able to move that complexity to the ground systems and have the recovery system, the landing system, more like an aircraft carrier, like crab the airplane. Right. We can put the actuation on basically a robot that goes up and grabs the airplane.
43:59Keller Rinaudo Cliffton:And we're like, man, that's going to make the aircraft so much simpler, so much lighter, so much more reliable. We didn't have it working yet. And it was time to build that next generation of the aircraft. And we're like, so we're building these next week. Do we build them with the meter long tail hook? Or do we delete the tail hook and put the two centimeter long tail hook on the back and bet that we can get this thing working? We got in a room, we're like, delete it, right? Like, let's do this thing. And so we're like, from first principles, it should work. We can make it work. We haven't done it yet, but we can do it.
44:27Keller Rinaudo Cliffton:And the next couple of weeks looked like myself included, a lot of people pulling a lot of a lot of late nights, getting that thing working. And sure enough, those first aircraft came and we caught them and landed them. So it's a lot of courage. But that like really being grounded in first principles thinking with a tight, integrated team is how you do that. Is there a version of the future in which instead of delivering life saving medicine and cheeseburgers, you're delivering human beings?
44:53Eric Watson:Hey, I'm the board member that has to control their costs.
44:58Keller Rinaudo Cliffton:I mean, you know, safe, reliable, battle tested. I don't know. Seems like if we're going to liberate ourselves from the tyranny of streets, it's a pretty decent solution.
45:09Eric Watson:Gosh, I think I agree with you. I think that, you know. He's going to come to you and ask for another billion dollars. I think, you know, a couple of thoughts. One is that I think Alfred knows I'm measured in the way I answer that question because, to be clear, building a new infrastructure layer for the planet that can deliver packages as efficiently as the internet moves information is going to be one of the biggest companies on earth. It's a huge opportunity, and we definitely want to stay humble and paranoid about how super hard that's going to be, the level of execution for us to scale the way we want to scale over the next couple of years.
45:48Eric Watson:And to put into perspective, I described this goal of getting to a million deliveries a day in the very near future. We now have many partners who are each asking to buy a million deliveries a day of capacity from Zipline in the last few months. And so our operating plan has now become our unit of sale. That's a pretty crazy realization. And it's leading us, we had originally built, we had sized the entire factory to build 20 ,000 aircraft a year. that was about what was required for a million deliveries a day. All of this is kind of being thrown... We're realizing the market is way bigger. And one thing, when you look at this totally hyperbolic curve that I think I showed you only a few months ago of what our total daily flight volumes have done over the last 16 months, the level of complexity of all the different systems that are required to basically stay on that track is quite high.
46:46Eric Watson:Yeah. But there are five and a half billion instant deliveries being done by humans in the United States every year. And we're using a 4 ,000-pound gas combustion vehicle. It's not really instant. It's like half an hour to an hour. Exactly. It's good marketing that it's called instant. But yeah, exactly. And 30 minutes, 45 minutes, an hour. a significant percentage of the driver's report eating some of the food that they've delivered in the last month, like more than 50%. There are significant safety concerns associated with these kinds of delivery. But 5.5 billion instant deliveries, what we're realizing when you look, Zipline is now at massive scale in Dallas, and we're now launching four more metros in the next four months.
47:30Eric Watson:When you just look at Dallas, if you were to extend the buying behavior that we're observing from Zipline customers in Dallas to the rest of the United States, there would be 55 billion instant deliveries happening, not five. 55 billion. Yeah. There's a huge market expansion. I think it's similar to how people looked at Uber when they were launching in San Francisco. And they're like, oh, even if Uber gets to be 33 % of the taxi market in San Francisco, it's only going to be a$15 billion company. And obviously what they missed is like, Uber's now 10 times the size of the taxi market. You know, like if you make something more convenient and less expensive and a better product experience, people are going to consume a lot more of it.
48:09Eric Watson:We are clearly seeing customer behavior where customers order every day rather than a couple of times a month. I mean, I met a grandma the other day who's ordered 350 times from Zipline in the last year. She's 80 years old. Amazing. Actually, nursing homes are like big Zipline. They're like big demand centers for Zipline.
48:26Keller Rinaudo Cliffton:It's probably pretty fun if you're in a nursing home.
48:28Eric Watson:It makes sense. And actually, it's funny. People perceive, I think, old people as like maybe being, you know, not capable of using technology, they're all like living on their iPhones, you know, like they're probably doom scrolling actually, which is maybe not a good thing, but like they are very comfortable using like, you know, Apple ID, Apple pay or Face ID, Apple pay, and just ordering and having it delivered directly to them. So there are definitely not enough humans in the United States to do 55 billion deliveries. The only way we're going to be able to serve this kind of demand is with automated systems.
49:01Eric Watson:And there's definitely not enough roads. When you look at traffic in most of our major cities, you're like, oh, can we just maybe double the number of cars on the roads so that we can do way more deliveries? It obviously doesn't work. We actually need to be taking cars off the roads if we want to enable human growth and flourishing. And so I think this change is inevitable. So how many flights are you doing a day now and how many will you do in a month? So Blani is now doing almost 5 ,000 flights a day. And we're anticipating exiting this year at above 30 ,000 flights a day. And our goal is to get to a million flights a day as fast as humanly possible, which we expect to achieve in the very near future.
49:41Eric Watson:Like all of the supply chain manufacturing capacity decisions we're making right now are designed not just to get us to a million deliveries a day, but also accelerate past that. The things that are interesting to think about on the unit economics front is whenever we meet hardware companies and you always talk to them about how much do you think the system is going to cost? And they're always like, it's going to cost X. And you're like, cool, it's going to cost 10X. Just so you know. When you build it, it's going to cost 10X. That's your advice to founders. That's my advice to founders. For hardware companies, because I try to be a good seed investor and pay it forward and stuff.
50:14Eric Watson:And you're always meeting these founders and always like, it's going to cost this much. I'm like, cool, just assume it's going to cost 10 times that. Does it work and what would you do if it cost 10 times that? And we're speaking from experience. When we launched our system in 2016, we were charging$30 of delivery to deliver a blood transfusion over 80 to 100 miles. And that was cost comparable. And so that's what we signed the contract for. And we thought that we were going to launch a system that cost about$30 of delivery. How much do you think it cost when we launched? 300 dollars. Yeah, it cost$300 of delivery.
50:44Eric Watson:And Alfred was surprisingly chill about it. And we were like, all right, we got work to do. And so the next year we got it to like 120, then the next year we got it to 75, then the next year we got it to 40, then we got it to 28, then we got it to 18. It's now 12 for the long-range technology that we operate outside the U.S. Right now what's happening this summer is the fully burdened unit economics of these systems is just now in the process of falling below the cost of using cars to deliver things. And so I think it is a cool moment that I think most people don't really realize. It's happening quietly.
51:18Eric Watson:You're not reading about this in the New York Times or whatever. I think that this thing is happening in the next month or two that is going to have a big impact on the world and how the world looks and how most normal people even live their lives because it is now more cost effective to use a robot in logistics than it is to use a human. And that's really good news for the environment. It's really good news for neighborhoods that are going to get quieter and safer and less traffic, less pollution, and it's really good news for customers because you can get things way faster and more reliably and for less expensive.
51:54Eric Watson:You know, our customers love, like, there are obviously so many cool things about the system that, you know, you can talk about and that you see customers taking advantage of, but like, no tip, exclamation point, exclamation point, exclamation point is like a big, you know, that's probably the number one comment. I think that customers love not having to feel guilty and being able to just have a system that they know how much it's going to cost. Well, thank you, Keller and Eric, for being here with us. I thought you were going to say it takes longer than you thought, not 10x more than it costs.
52:25Eric Watson:But anyway, that's a great way to end. It does also take a lot longer. I mean, I think the memo that Sean wrote here at Sequoia a few years ago, I think is deeply true. I don't know if he'll ever publish that publicly or if it'll be allowed. But I do think, suffice it to say, there is an internal Sequoia memo that has had a big impact on me talking about A, why hardware companies are going to be some of the most impactful companies for humanity's progress over the coming decades, and B, why it's super hard to get those companies off the ground and fundraise for them and see how investors should think about funding those kinds of companies.
53:03Eric Watson:It's interesting when you look at the world today to see, I mean, wow, how fast the world changes. Because think about it, we spent 10 years being the freaking black sheep, like a hardware company, no thank you. Like, let's invest in, you know, SaaS, let's invest in margins. Like, this is where the whole future was and like, you know, iPhone apps, blah, blah, blah. So I don't know, I guess I feel like - Now you're cool. Remember Bane in Batman, what does he say? Like, you adopted the darkness, I was born in it. Like, man, we built a robotics company for 10 years before building a robotics company was a cool thing to do.
53:35Eric Watson:But I do think that especially important for US competitiveness and just for our ability to build the future that we'd be really proud to hand to our kids and to our grandkids and to build the sci-fi version of the future that we were all promised, we got to get good at building stuff again. And we got to get good at building not just vehicles and hardware. We got to get good at building infrastructure. We're depending on the crumbling infrastructure that our grandparents built for us. I read the other day, we just installed these anti-suicide nets on the Golden Gate Bridge, if you guys heard about that project.
54:10Eric Watson:It cost more to install those nets than it cost our grandparents to build that bridge.
54:17Keller Rinaudo Cliffton:I believe it.
54:17Eric Watson:So anyway, we get really excited. We think the future, promising future, is we should be able to build infrastructure. We have to be interested in it. And I think people have to have the stomach for it. And we have to learn how to manufacture and run complex supply chains again. And we have to be bold and believe in sci-fi versions of the future if we're going to build them. Awesome. Let's end it at that. Believe in the sci-fi future. Yeah. Thank you guys for being with us. Thank you. Thanks for having us. Thank you for inviting us.
54:59Thank you.
From the publisher
The largest commercial autonomous system on earth isn't a robotaxi fleet — it's Zipline, which has flown 140 million autonomous miles with zero safety incidents. Co-founder Keller Rinaudo Cliffton and Eric Watson, who leads systems engineering and safety, explain why the drone itself is only 15% of the solution. The rest spans inventory management, air traffic integration, and engineering systems such as a dual flight computer failover protocol that recently saved a delivery mid-flight. They trace Zipline's path from launching blood delivery in Rwanda in 2016 (when drone delivery was illegal in the US) to a 51% reduction in maternal mortality in that country, a $550 million commercial diplomacy partnership with the State Department, and a cost curve that fell from $300 per delivery to $12. Zipline is now racing toward a million deliveries a day, and a quiet inflection point when autonomous delivery becomes cheaper than sending a car.
Hosted by Alfred Lin and Pat Grady, Sequoia Capital




