Polymorph/Physical AI, ExplainedGlossary

Physical AI, Explained · Part 7

Deployment and go-to-market

Read this part in the book →

Robots reach customers one site at a time. Before they can work entirely alone, they earn revenue through mixed autonomy, in which a human corrects the robot when it fails, and every deployment generates data that makes the next one easier. This part treats deployment as an engineering discipline in its own right and then examines the business logic that follows from it: where to deploy, how to stage adoption, what the unit economics must look like, and where lasting advantage comes from.

7.1 Deployment is a technical problem

Software reaches millions of users through a download. A robot reaches one customer at a time, by truck, and must then be installed, commissioned, tested for safety at that particular site and integrated with the people and equipment already there. Every site differs in lighting, floor surfaces, clutter, network coverage, object variety and the habits of the people who work there, so each deployment exposes failure modes that never appeared in the lab. A grasp that succeeds reliably on a test bench may fail under the glare of a skylight or on a slightly different batch of packaging. Much of the real engineering work of a robotics company is therefore finding, diagnosing and fixing these site-specific failures, and the people who do it (field engineers, remote operators, integration staff) are as central to the product as the model.

This is why the strongest teams treat deployment as a priority from the first day rather than as a final step after the research is done. A data flywheel is the loop in which deployed robots collect experience, that experience improves the model, and the improved model justifies more deployments that collect more experience. The loop is slow to start: robots must be built, shipped, installed and trusted before they produce useful data, and the data pipeline (logging, upload, labelling, training, validation, rollout) must exist before any of it can be used. A team that waits until its model is "ready" before deploying starts this loop late and never recovers the lost time.

Estimates of the timeline differ. One view holds that robots will be technically capable within a few years and will then spread gradually, because manufacturing, installation, certification and customer adoption all move at physical rather than digital speed. A faster estimate puts the change at a year or two, on the reasoning that once people see robots working around them, trust builds quickly and demand accelerates. The two views agree that capability alone does not determine the pace; the rate at which robots can be built, deployed and accepted does.

7.2 Levels of autonomy and mixed autonomy

Self-driving cars have a formal taxonomy of autonomy levels, and three of its terms carry over usefully to robots: - L2++ describes highly capable driver assistance in which a human remains legally and practically responsible, such as supervised driving-assist systems that steer, brake and change lanes while the driver watches and is ready to intervene. - Driverless operation, or true autonomy, means no human is in control at any moment and the onboard computer handles everything, including the rare and dangerous situations. - Mixed autonomy means the robot works on its own most of the time, but a person takes over and corrects it when it makes a mistake. This intermediate stage is what lets a deployment earn money before full autonomy exists.

In practice, mixed autonomy usually takes the form of teleoperation, in which a human controls the robot remotely through a camera feed and an input device, or lighter remote assistance, in which the human does not drive the robot directly but answers a question such as which object to pick or which path to take. The commercial value of the arrangement depends on the ratio of robots to operators. If every robot needs a dedicated human watching it, the robot saves little labour; as reliability improves, one operator can supervise a growing fleet and intervene only when called, and the economics shift accordingly.

A disengagement (in robotics often called an intervention) is an event in which a person has to take back control. Miles per disengagement is the standard self-driving metric, and robotics uses analogous measures such as interventions per hour of operation or the number of tasks completed per intervention. These metrics matter because they convert reliability directly into staffing cost and because their trend over time shows whether the system is actually learning. They have known weaknesses: the number depends heavily on how hard the operating conditions were and on how cautious the operators are, so two figures are comparable only when measured under similar conditions and intervention policies.

The data a deployed robot generates follows the same progression described in 2.7. It begins with human demonstrations, which teach the basic skill. Next come human corrections gathered during mixed autonomy, which are exactly the data that pushes a model to high performance: each one is recorded in a state the robot itself reached and shows how to recover from a mistake the robot itself made, which is the information pure demonstrations lack. Finally the robot learns from its own experience working alone, with successes and failures labelled by outcome.

7.3 Where to deploy first

The usual order is businesses first and homes last. Several distinct arguments point the same way. - Start with the most structured settings. A common sequence begins with structured factories and warehouses, where layouts are fixed, objects are known and the space can be adapted to the robot. Next come partly structured service settings such as hospitals, grocery stores, hotels and airports, which have predictable routines but also members of the public moving through them. Homes, the least structured environment, come last. Each stage supplies data and operating experience for the next. - Start where people are used to new technology. Computers went first to professionals and companies and entered homes once people had become familiar with them at work. A robot in the home would feel strange to someone who had never seen a robot anywhere else, while a person who has worked beside one in a warehouse brings some trust with them. - Homes are hard for three reasons. The home is the most chaotic environment, with endless variation in layout, objects and clutter. The safety bar is the highest, since a robot can never be allowed to fall on a baby, and households contain children, pets and elderly people who cannot be trained or expected to follow procedures. And households pay less than a business whose robot works all day and whose value can be measured against a wage. - Businesses are easier customers. They pay more, are more patient with early limitations and let the company improve the robot on site, often with a human operator in the loop. A consumer tries a robot for two days and gives up. - Look for variability. Learned AI is only needed where there is randomness: where the objects, positions or conditions change from one attempt to the next. A task that is identical every time is better served by conventional, preprogrammed automation, which is cheaper and more predictable. Current targets for learned robots include delivery, inspection and security, warehouse and factory work alongside people rather than inside safety cages, and data centers.

Laundry is an example of how location determines value. A laundry-folding robot is possible this year, but few people want a machine that sits in a corner of the home and does only that. The same skill installed in a commercial laundry or factory running every day would have buyers waiting, because there it replaces a measurable, continuous cost. The capability is identical; the business case depends entirely on where the robot works.

7.4 ODD and geofencing

The operational design domain (ODD) is the explicit specification of the conditions a system is designed to work in. It can include geography (this campus, these four buildings), environment (indoor lighting only, dry floors, this kind of weather), the objects the robot will encounter, the speeds it will move at and the presence or absence of people. Geofencing means restricting operation to a defined, mapped area, so that the robot stops or refuses to proceed when it reaches the boundary.

Defining the ODD is a core step for both safety and commercial scoping. For safety, it bounds the hazard analysis: engineers can only assess the risks of conditions they have specified, and a system operating outside its ODD has no validated safety case. For scoping, it makes the contract with the customer concrete, stating what the robot will and will not do, and it gives the company a clear test of whether a new site is within reach of the current system. Expansion then proceeds by deliberately widening the ODD, one condition at a time, with validation at each step.

The way a system perceives its world determines how fast its ODD can grow. Systems that depend on detailed maps made in advance can only expand as fast as new maps are made and kept up to date, since a moved shelf or a renovated corridor can invalidate them. End-to-end systems that interpret the scene directly from sensor data without detailed prior maps do not have that limit, although they still need validation in each new kind of environment before they can be trusted there.

7.5 Vertical-robotics recipe

A vertical robotics company is one that builds a complete solution for a specific industry or task rather than a general-purpose platform for others to adapt. A workable recipe for such a business today runs as follows: 1. Learn the customer's current workflow in depth, including the informal steps no one writes down. The robot has to fit the workflow, not the other way round, because a customer will rarely reorganize a working operation around an unproven machine. 2. Find the point in the workflow where a robot adds the most value: usually the step that is most repetitive, most physically demanding, hardest to staff or most often a bottleneck for everything downstream. 3. Keep hardware and data costs low. Modern models that react continuously to what they see can make up for cheaper, less precise hardware, because a closed-loop policy that observes its own errors can correct a position that an open-loop, preprogrammed robot would miss. 4. Deploy with mixed autonomy, so the robot earns revenue while its remaining failures are covered by human operators and turned into training data. 5. Make each robot at least break even. 6. Only then increase the number of robots.

Two further points refine the recipe: - Choose a first task that teaches something and pays. Restaurant napkin folding is one example. It is hard enough to push research, because the robot has to take a single napkin from a stack (separating thin, deformable layers that cling together), handle endless fabric shapes and meet a strict quality standard, and customers asked for it. Deformable objects like fabric are especially demanding because their shape cannot be described by a few fixed parameters and changes with every touch. Each deployment then works as a test of the general system rather than as a separate business, and the lessons transfer to the next task. - Deploy one task at a time. A language model had to be good at nearly everything before it was useful, because a weak one produces fluent nonsense that no one can rely on. A robot company is in a different position: it can deploy the few skills it has mastered while it keeps building the general model behind them. That is how a company can build a general model while selling into a narrow market, using revenue and field data from each narrow task to fund and train the broader capability.

7.6 Staged adoption

Business deployments usually progress from a proof of concept, which shows the robot can do the task at all, often in controlled conditions, to a pilot, which runs the robot in the customer's real operation for a limited period against agreed success criteria, and finally to full deployment. Each stage should have measurable exit criteria agreed in advance (throughput, quality, uptime, intervention rate), because pilots without them tend to drift on indefinitely without a decision, a pattern often called pilot purgatory. The hardware used in the pilot must go straight into production without being ripped out and replaced; a pilot built on bespoke or prototype equipment proves little about the system the customer would actually buy and doubles the integration effort.

Standardize a small, repeatable set of uses before customizing anything, because heavy customization at the start is what kills adoption. Every custom feature adds engineering work that does not transfer to the next customer, and a company that says yes to every request ends up running a consulting business with robots attached. Adoption also depends on change management: the work of preparing the people at the site for the new system, including training staff to work beside the robot, adjusting procedures, assigning responsibility for clearing faults and addressing workers' concerns about their jobs. Deployments with sound technology still fail when the people around them were never brought along.

The hard milestone is a customer believing the robot creates enough value to deploy it across many of its sites, which takes far more than one location or a pilot. One restaurant customer folds thousands of napkins a day across many locations (a reported result). A shared model helps at this stage. Every site runs the same model, so the work is consistent from one location to the next, and all robots receive improvements at the same time through over-the-air updates, software delivered over the network without a technician visit. Well-run fleets stage these updates, releasing a new model first to a few robots and expanding only after its performance is confirmed, because a regression shipped to every site at once can halt the customer's operations everywhere.

The ideal is a robot that starts working as soon as it arrives at a site, with no new data collected there, a property called zero-shot deployment. A version of this has been shown by a robot folding T-shirts for three days at a robotics conference while visitors deliberately got in the way, an environment the system had not been trained in and could not have been prepared for.

7.7 Unit economics

Unit economics describes the revenue and cost attached to a single deployed robot, independent of the company's overall overhead. - Payback period is how long a deployed robot takes to earn back its cost, calculated as the upfront investment divided by the net savings or revenue it generates per period. Industrial buyers typically judge automation projects by this figure and reject those whose payback is too long. In the past, this is what killed robotics companies as they tried to grow: the numbers never worked. - Total cost of ownership (TCO) is the full cost of a robot over its working life, which includes the purchase price, integration and installation, maintenance and spare parts, energy, software, downtime and the human supervision needed in mixed autonomy. A low sticker price can hide a high TCO, and customers increasingly compare robots to labour on this basis. Some companies sell robots as a subscription (often called robots as a service), which turns the upfront cost into an operating expense and shifts maintenance risk to the vendor. - Break-even per unit is the test to pass before scaling up. A company that loses money on every robot cannot grow its way out of the loss, since each new deployment deepens it. - Integration cost was the historical barrier. Programming and integrating a robot for each site often cost more than the robot itself, and a caged work cell can cost several times as much (1.3), once fencing, fixtures, part feeders, safety interlocks and specialist programming are included. Robots that adapt on their own remove most of that cost, and that is what makes wider adoption possible. Robots working on existing factory lines next to people, without cages, demonstrate the point, since any place with people in it is messy and cannot be engineered to the precision a preprogrammed robot needs.

A robot costing about $50,000 works out to roughly $2 an hour over its life, compared with $35 to $40 an hour for fully loaded US labour, meaning wages plus benefits, payroll taxes and other employment costs. That is competitive even with offshore labour. The advantage compounds with utilization: a person works one shift, while a robot can work several, so one robot can do the work of about three people. The hourly figure covers only the hardware, however, and the comparison holds only if integration, maintenance, downtime and supervision stay small relative to it, which is why reducing intervention rates and integration effort matters as much as reducing hardware cost.

7.8 Labor, safety and demand

The public debate about jobs usually concerns robots taking them. The opposite pressure, a shortage of workers, is arguably stronger today. Labour figures vary by country, sector and source and change quickly, so they should be verified before being quoted. - Many jobs go unfilled. Large numbers of open jobs exist alongside unemployment, because the work is dangerous, physically punishing, poorly located or hard to keep staffed, and turnover in such roles is high. The gap will likely grow as populations age and fewer young workers enter manual trades. Demand for robots then arrives on its own, because companies already cannot hire for these roles. - Safety risks are both sudden and long-term. Some work puts lives at risk through falls, crushing or exposure to hazardous materials. Much more wears bodies down slowly through musculoskeletal injury, for example from bending in one position all day or repeating the same lifting motion many times a shift. Robots that take over these tasks reduce injury costs as well as labour costs. The robots themselves must also be safe: industrial and collaborative robots are designed and installed under international safety standards that require a documented risk assessment for each application, and robots sharing space with people rely on measures such as speed and separation monitoring and limits on contact force and power. - The social question is real. If robots become very capable, society has to ensure the benefits are broadly shared rather than held by a few, through policy, retraining and the way the gains are distributed.

Start where customers have a painful, urgent labour shortage, because those customers adopt fastest: the alternative to the robot is not a cheaper worker but an unfilled shift.

7.9 Defensibility

Where a robotics company's lasting advantage, or moat, comes from is one of the field's clearest disagreements. - The deployer's view. If a few labs build general models and share or license them, models become a commodity, interchangeable and priced near cost. A company's advantage then comes from knowing customer workflows, choosing where robots add the most value, owning the data from its deployments, running the mixed-autonomy loop well and meeting the physical requirements of each site. The practical consequence is architectural: keep the model and the robot separated by a clean interface, so that a better model from any source can be swapped in without rebuilding the product. - The brain-maker's view. In language, the training data is largely public, so a result can be copied within months. In robotics the data is not public; it has to be collected by physical machines in the world. The best model wins the most deployments, which produce the most data, which makes the model better still, a self-reinforcing loop that competitors cannot shortcut by downloading anything. On this view the brain is very hard to commoditize, while robot bodies are becoming commodities, the way phones did once most of them ran the same operating system. - What both sides agree on. Advantages in technique are temporary, because methods spread through publications and staff movement, and even model builders count deployments as the lasting advantage in robotics. Both camps agree that deployment data is what accumulates over time. They disagree about who will end up owning it.

Why it matters: If models become commodities, the winning position is to own the workflow and the customer relationship; if the model's advantage keeps growing, a company should partner with the leading model maker or build its own. In either case, deployments are the main asset.


← Part 6. From demo to reliable product   Part 8. Markets and capital →