Physical AI, Explained · Part 10
What the robotics market rewards
Read this part in the book →Lessons from AI-native software and robotics companies apply directly to how a robotics company should be run. The common thread is that robotics combines the iteration speed of machine learning with the unforgiving physical reality of hardware, and the practices below are ways of keeping both honest.
- Measure results, not effort. "Be customer obsessed" describes an effort, and a team can practise it diligently while still producing a poor outcome. "Create obsessed customers" describes a result, and it predicts whether customers renew, expand and recommend the product. Goals stated as results can be checked; goals stated as effort cannot.
- Track the company with data, not gut feeling. No one trains a model on intuition, yet many companies set budgets and priorities that way. The same discipline that governs model development should govern the company: each new capability should be checked against a real metric, such as task success rate, interventions per hour or customer usage, to confirm that it actually moved something.
- Stay model-agnostic. A model-agnostic product is built so that the underlying model can be replaced without rewriting the rest of the system, usually by keeping a clean interface between the model and the surrounding software. This protects the company technically, since the best available model changes frequently, and business customers trust it because it reduces their dependence on any single model provider.
- Do not trust public benchmarks. A benchmark is a standard test used to compare models. Any public benchmark that matters commercially gets gamed ("benchmaxed") within months, as developers tune models to the specific test, sometimes with test examples leaking into training data, until scores rise without matching gains in real capability. Internal benchmarks built from real tasks, ideally paid ones, are harder to game because they reflect the conditions the robot will actually face.
- Do research and deployment together. Research shows what is technically possible and therefore what can be sold; deployments show which problems actually matter to customers. Without deployments, research priorities are guesses, and a team can build something impressive that nobody wants to buy. The history of robotics includes many companies that built very shiny, very cool robots and failed for lack of a paying use.
- Design tasks to test capabilities. Effective evaluation starts from the capability required, such as following spoken instructions or fine dexterity, and then designs a concrete task that exercises it. Fetching a named drink from a fridge, for example, tests language understanding, object recognition among similar items, navigation and manipulation of a door and a container in one sequence, and failures can be traced to the capability that broke.
- Expect a large hardware team. At one robotics startup, 30 to 40 percent of staff work on hardware and only a small group works on models. Hardware absorbs effort because every design change must be built, tested and maintained physically. Data collection is also a skill in its own right: people with no robotics background can become highly skilled teleoperators and data collectors, and the quality of their demonstrations directly shapes the quality of the trained model.
- Hire for attention to detail and curiosity about the whole system. Robots fail at the boundaries between subsystems, where a mechanical tolerance, a software timing issue and a model's behaviour interact. The strongest candidates combine deep respect for colleagues' expertise with a strong desire to understand everything else. Mindset matters more than credentials, and the hard part of hiring is designing a process in which candidates can demonstrate it.
- Use the open models. Capable robot foundation models, meaning large models pretrained on broad robot data and adaptable to many tasks, are now available as open source. Small teams should start from such a general model and fine-tune it (continue training it on their own task data) from the first day, rather than building a separate model for each site. A shared base model lets data from every deployment improve performance everywhere.
- Hire people committed to the mission before things get hard. Resilience cannot be screened for once a crisis has started, because by then the team is already fixed. Commitment has to be assessed at hiring, when the cost of a wrong choice is lowest.
- Watch market timing. Being too early costs as much as being wrong (8.4), so the readiness of the market, in customer budgets, regulatory acceptance and the maturity of supporting technology, needs to be rechecked continuously.
← Part 9. Compute and supply chain Part 11. Strategy while models, compute and hardware get cheaper →