The Loop Is The Moat

Why we're underwriting closed-loop robotics

The most defensible robotics companies of the next decade won’t be those with the best hardware, or the best models. They’ll be those who close the loop between the two.

Software has had a defensibility playbook for twenty years: usage generates data, data improves the product, the product attracts more usage. That flywheel built every dominant software business of the last two decades. Hardware companies never had it. Design data sat trapped in CAD files. Deployment data sat trapped on customer floors. The product shipped and the conversation ended.

Physical AI changes that. A robot arm in a warehouse generates telemetry. Telemetry trains policies. Better policies make the arm more useful. More usage means more deployments. More deployments mean more data. The loop closes, but only if one company owns the hardware, the software, and the deployment surface. Hand any of those off and the loop breaks.

This is what we mean by closed loops. Not vertical integration for its own sake. We mean vertical integration that compounds a learning signal pure-software AI players can’t access and pure-hardware OEMs can’t build.

Our portfolio company Robo Robotics is building exactly this. We call them “the self-replicating robotic arm company” because they build robot arms that build more robot arms. The hardware is standardized so a policy trained on one unit deploys to a hundred. Customer data improves the platform, the platform makes the next arm more useful, and the new arms manufacture the next batch. Hardware, software, and manufacturing in one closed loop.

We’ve also been spending time with a team automating the design of robotic hardware itself. Today they sell that software to robotics companies, who handle the manufacturing and deployment. But the vision we are excited to share with this team is one where they design the part, build it, ship it, and monitor how it performs in the field. Every unit shipped teaches the software how to design a better one. The company becomes the loop.

The pattern generalizes. Anywhere a physical system generates data that improves the next one, there’s a loop waiting to be closed. Most of these wedges are still open because closing the loop requires building competence across three disciplines: software, hardware, and operations. Most founders specialize in only one.

That’s what we’re looking for. Founders who refuse to specialize. Companies where the hardware and the software ship from the same team, and where the data from one improves the other on a daily basis. The loop is the moat.