Ep. 75: The Field is the Lab for Overland AI

About Byron Boots

Byron Boots is the co-founder and CEO of Overland AI. Prior to starting the company, he was an associate professor in computer science at the University of Washington, where his research focused on machine learning and robot autonomy. Byron served as principal investigator on DARPA’s Racer program, one of the most ambitious off-road ground autonomy challenges the agency has run since its landmark Grand Challenge series in 2004–2005. It was in that role — out in the field, iterating under adversarial test conditions — that the insight and technology behind Overland AI took shape.

About Overland AI

Overland AI builds autonomous ground vehicle software and systems for the U.S. military. Their flagship platform, ULTRA, is a purpose-built unmanned ground vehicle with upgraded suspension, miniaturized compute, and a suite of sensors including stereo cameras, LiDAR, thermal cameras, and Starlink — capable of GPS-denied navigation in extreme off-road terrain.

The company operates across four primary concept of operations: ISR (intelligence, surveillance, and reconnaissance), logistics and resupply, layered protection (including counter-UAS), and breaching. Their go-to-market approach has been almost entirely driven by demonstrated field performance. Initially this came through DARPA experiments, then through DIU and direct work with Army and Marine Corps units. Overland has won contracts including the DIU Ground Vehicle Autonomous Pathways program and is currently focused on scaling into formations and establishing a permanent operational presence with the services.

Key Takeaways

Five principles from Byron’s journey that apply broadly to defense tech founders:

* Field, first. One of the most counterintuitive decisions Byron made at University of Washington was to hire strong vehicle mechanics as some of his first team members. It’s a simple but counterintuitive logic. You don’t have to build the perfect software in the lab before you put it on the vehicle because if vehicles could be repaired rapidly in the field, the software team could test more aggressively, fail faster, and iterate without fear. Thus, the vehicle mechanics gave the rest of the team leverage.

* The best BD is performance (with the lights on). Overland AI’s early business development was almost entirely organic. I pressed him on DARPA’s checkered history of transitioning programs, but in this case, DARPA invited the other services to watch their field experiments. Those experiments were credible, because the company often didn’t know what was coming. It wasn’t a PowerPoints brief or a table top conversation; it was an opportunity for customers to see the tech in action. That credibility dramatically accelerated their sales path.

* Build on top of what works. Byron’s framework for capability development is deliberate: get one robot working reliably, then add a second, then build multi-vehicle coordination. Don’t architect for the end state. Prove each layer before adding the next. This mirrors successful product development in commercial software but is even more important in defense, where integration failures in the field are immediately visible and costly.

* “If it’s not seamless, it won’t survive contact with the warfighter.” Despite the old saying “good enough for government work,” the operational bar for defense products is actually quite amorphous. Byron observed that “a slow or unreliable robot simply gets abandoned.” In other words, your project might die without you even knowing. The product actually has to perform well enough that operators don’t think about it. Only then can you expand the mission set, add payloads, or introduce multi-vehicle coordination.

* It’s not about your tech. The sooner you embrace this, the faster you’ll win.

Winning a contract gets you in the door, but a contract isn’t the same thing as winning warfighter trust. Byron draws a clear distinction between them. Overland's next 12 months aren't going to be defined by new contracts as much as they are going to be defined by creating "a permanent presence" with Army and Marine Corps units. I love this point because it suggests a totally different motion. It’s not about closing the deal or renewing it. It’s not about another slide or another meeting. It’s about doing things that don’t scale, having people side by side with the mission owners, and obsessing over the question of how to make your technology invisible inside existing workflows rather than celebrated as a novelty.

For more Crossing the Valley: valleycrossers.com

For more on Overland AI: www.overland.ai

Follow Byron: https://www.linkedin.com/in/byron-boots/

Follow Noah: https://www.linkedin.com/in/noahsheinbaum/