Latest / The Operations Podcast with Fexingo: Process, People, and Profit in Modern Business / How One Ukrainian Drone Startup Built Battlefield Operations in 72 Hours
Transcript
- Lucas: When Russia invaded Ukraine in February 2022, a three-person startup called Dronar had exactly zero drones in production. Within eight weeks, they were delivering reconnaissance drones to the front lines. By month twelve, they were making over two hundred units per month, operating out of a repurposed bomb shelter. Luna: That timeline — from zero to wartime production in two months — is almost unbelievable for a hardware company. Most drone startups take eighteen months just to certify a prototype. Lucas: Exactly. And that's what makes their operational story so specific and worth unpacking. The conventional wisdom says you cannot rush hardware. Dronar basically threw that wisdom out the window because they had no choice. If today's conversation gives you one operational insight you can apply — even in a peacetime setting — that's the point. The reason this show stays ad-free is listener support, so if what we cover here moves your work forward in some small way, you can keep that going at buy me a coffee dot com slash fexingo. Now, let's get into how they actually did it. Luna: Right. So the first bottleneck was obviously motors. Most drone motors come from either China or Japan, and supply chains were a mess. How did they source them? Lucas: They went straight to consumer-grade hobby shops. The founders bought hundreds of small brushless motors meant for RC airplanes — the kind you'd find on AliExpress for fifteen dollars. They tested them in batches, rejected about thirty percent, and used the rest. No supplier contracts, no minimum order quantities. Just cash and a credit card. Luna: That's incredibly inefficient from a traditional procurement standpoint. But in wartime, speed trumps unit cost. Lucas: And they leaned into that trade-off hard. The motors were only good for about fifty flight hours before performance degraded. But by that point, the drone itself was often already destroyed or captured. So they optimized for cheap and fast, not durable. Luna: What about the airframe? I know they used 3D printing for some parts. Lucas: They ran twelve industrial FDM printers in a basement that doubled as a shelter during air raids. The fuselages were printed in sections — each section took about fourteen hours. They'd glue them together with standard epoxy, reinforce with fiber tape, and then mount the electronics. The whole cycle from print to fly was seventy-two hours. Luna: Seventy-two hours. Compare that to a traditional aerospace supplier, where a single composite layup might take a week just for the curing. Lucas: And the interesting part is how they handled quality. They couldn't afford formal inspection. So they gave every assembly worker a smartphone and told them to video each step. The videos were reviewed by a remote team in Lviv. If something looked wrong, they'd message the worker immediately. It was asynchronous quality control. Luna: That's basically a peer review system for manufacturing. And it scales because the videos become training material for new hires. Lucas: Exactly. Their operator turnover was high — people were being mobilized or displaced. A new person could watch five videos from the previous week and understand exactly what a good joint looks like. The knowledge retention was baked into the process itself. Luna: Let's talk about testing. In a normal drone company, you'd have a dedicated test range, flight logs, engineers analyzing telemetry. What did Dronar do? Lucas: They used soldiers as test pilots. Every drone was sent to a forward unit with a one-page checklist. The soldier would fly it for ten minutes, report any issues via Telegram — a video or a voice note — and then either keep using it or send it back. The feedback loop was hours, not weeks. Luna: That's the ultimate form of customer-driven iteration. The user is literally under fire. Lucas: And the data they got was brutally honest. One issue was that the drone's video feed had a half-second delay, which made it hard to spot camouflaged positions. The soldiers said, 'Fix the latency or we won't use it.' So Dronar swapped the radio module within a week — sourced a different frequency band, rewrote the firmware, and shipped the update over the air. Luna: That's impressive. But how did they manage inventory? If you're sourcing motors from random hobby shops, you can't predict when a shipment arrives. Lucas: They ran a very simple buffer system. They always kept two weeks of motors, three weeks of propellers, and four weeks of electronics. The moment any buffer dropped below one week, they'd send someone to buy more — sometimes driving to Poland to pick up packages from a freight forwarder. No ERP system, just a whiteboard with colored magnets. Luna: Low-tech but high awareness. They knew exactly what they had because they physically saw it every day. Lucas: And they avoided the trap of overstocking. Space was limited. If they hoarded too many motors, they couldn't store fuselage sections. So they optimized for flow, not inventory. Every cubic meter of that bomb shelter had to earn its keep. Luna: What about the electronics? Drones need flight controllers, GPS modules, cameras. Those are harder to source than motors. Lucas: They standardized on two component sets: one based on an STM32 microcontroller and one based on a Raspberry Pi Zero. Both were available through distributors in Turkey and Poland. They designed the entire drone around those two options, so if one supply line dried up, they could switch to the other within a day. Luna: Design for substitutability. That's a rare capability because most engineers want to optimize for a single platform. Lucas: And the interesting thing is, this dual-platform approach actually made the drone better. The Raspberry Pi version had more processing power, so it could run object detection algorithms. The STM32 version was more power-efficient, giving longer flight time. Units could choose based on mission type. Luna: So they turned a supply constraint into a product differentiation. That's smart ops thinking. Lucas: Now, the big question: can this model survive in peacetime? Dronar is already scaling down some of its emergency processes. But they've kept the seventy-two-hour cycle and the video-based quality control because it turned out to be cheaper and faster than traditional methods. Luna: So the wartime constraints forced them to discover operational efficiencies that they'll keep. That's the hidden upside of extreme conditions. Lucas: Exactly. And that's the lesson for any operations leader: sometimes the best process innovations come from being forced to do more with less. You don't need a war to create that pressure — you just need a genuine constraint that you can't negotiate away.