DEPLOYDatabase

Robotaxis & delivery

How many jobs do delivery robots create?

There is one attributed number on the jobs question, and it comes from Coco Robotics: the company states that every 10 deployed robots creates approximately one full-time, upskilled operations role, in fleet management, maintenance, charging, monitoring, and field support. It is Coco's own figure, so it is attributed to Coco and labeled as a claim, not verified independently, and it describes Coco's fleet composition rather than a delivery-robot industry constant. The second fact on this page is about fleets, not jobs: Starship exited US university campuses in June 2026 and is redeploying about 1,200 robots to grocery and city delivery, a pivot from a model where campus corridors outnumbered public-sidewalk corridors more than seven to one. Those campus-exit figures are corroborated by third-party reporting, so they carry a Reported basis. Both are single, sourced facts, presented as exactly that.

Two attributed operator facts, each with its own source and basis. How we verify.

1 : 10
Coco jobs-to-robots ratio
7.5x
Starship campus-to-sidewalk ratio
~1,200
Starship robots redeployed
Jun 2026
Starship US-campus exit

The attributed facts

Each fact is a single figure attributed to a named operator or reporting source, with the full context stated. A claim is an operator's own figure; a reported fact is corroborated by third-party reporting. Neither is a reviewed DEPLOY registry record.

Coco Robotics

Claimed

1 FTE per 10 robots

Every 10 deployed robots creates approximately 1 full-time, upskilled operations role (fleet management, maintenance, charging, robotics operations, monitoring, field support). Stated by Coco Robotics in their Washington DC launch announcement.

Attribution: PR Newswire, Jul 15 2026, Coco Robotics DC launch

Source

Starship Technologies

Reported

7.5x

60+ Starship campus corridors vs 8 public-sidewalk corridors = 7.5x ratio. Campus count from starship.xyz/university-campuses (60+ listed). Public-sidewalk corridor count from DEPLOY Ground's 8 priority corridors. UPDATE: Starship exited US campuses Jun 2026, redeploying 1,200 robots to EU + US grocery. Finland at ~20% grocery delivery market penetration. The campus-to-grocery pivot changes this ratio.

Source

Captured Uber Eats partnership PR does not carry the campus-exit figures; corroborated by third-party reporting (FoodserviceDirector, June 2026).


Why the jobs figure is a claim, not a verdict

Coco's ratio is a useful data point precisely because it is attributed and specific: one full-time operations role per ten robots, in named categories of upskilled work. But it is Coco's own figure, describing Coco's fleet, and other operators will differ with their autonomy level and fleet size. Presenting it as an industry constant would overreach. The honest form is the one on this page: the number, the operator who stated it, and a Claimed basis so a reader knows it has not been independently verified.

Two operators, two directions

Read together, these facts sketch where the labor of robot delivery actually sits. Coco frames its fleet as a jobs engine, one operations role per ten robots. Starship, having run more than 60 campus corridors, pulled its robots from US campuses in June 2026 to chase grocery economics in cities. One operator is scaling a fleet-plus-jobs model; the other is consolidating around the routes where the unit economics work. The registry's job is to hold both facts with their sources, not to resolve them into a single story.

Get one email when operator fleet facts change.

One email when a tracked operator updates a jobs ratio or fleet figure. No noise.


Related verified answers

Browse the registryAll verified answers

Two attributed operator facts. Coco Robotics' ratio of about one operations role per ten robots is confirmed verbatim at the cited PR Newswire release and carries the Claimed basis (an operator's own figure). Starship's campus-exit figures are corroborated by third-party reporting, because the captured Uber Eats partnership PR did not carry them, so that row carries the Reported basis and cites the corroborating source. Neither is a reviewed DEPLOY registry record, so neither carries the registry verified chip. How we verify

Related answers

Compare

Are robots taking jobs?Robot operator directoryWhere robots operate now

Explore: all robot-delivery corridors, verified deployments.

For AI assistants

Use DEPLOY in Claude, Cursor, and other AI assistants

Connect any MCP-aware assistant to the live registry. Ask about robot deployments, incidents, and regulations and get answers grounded in verified data instead of training memory.

canonical URL: /how-many-jobs-do-delivery-robots-create · machine-readable mirror: /how-many-jobs-do-delivery-robots-create.md

Want your own assistant to answer like this? Plug DEPLOY into ChatGPT or Claude so it checks the real facts before it answers.