Platform Dependence Threatens Coco Economics

Coco’s real vulnerability is that its robots are not the demand source, the apps are. Robot delivery only works when each machine stays busy across many trips per day, because the fixed costs are hardware, maintenance, charging, and teleoperations. Coco has built that density by plugging into DoorDash and Uber order flow, but those platforms are deliberately building multi provider autonomous networks and their own robotics capabilities, which keeps Coco from owning the customer relationship or the dispatch pipe.

• Coco itself describes utilization as the key hardware lever. The robots need to be doing trips all day, every day, because depreciation and fleet upkeep are fixed whether a robot runs one trip or twenty. Losing a large platform partner would hit economics fast, not gradually.
  1 sacra 2 sacra
• The platforms have alternatives. DoorDash has live partnerships with Coco, Serve, and Wing, and it has also launched Dot, its own delivery robot through DoorDash Labs. Uber works with Serve, Avride, Cartken, Nuro, and Coco across autonomous delivery efforts, which gives it room to route volume toward whichever option is cheapest or most reliable.
  3 doordash 4 doordash 5 doordash 6 doordash 7 uber 8 sacra
• Coco has one hedge against that dependence, direct merchant fleets. Some restaurants pay to control branded robots themselves, which gives Coco revenue outside marketplace dispatch. But platform volume still matters because it supplies the broad citywide order density that makes an urban fleet efficient in the first place.
  1 sacra 2 sacra

This market is heading toward a few large dispatch platforms sitting above several interchangeable robot networks. The winners will be the operators that prove the lowest delivered cost and highest reliability while also winning some direct merchant relationships, so they are not completely exposed to a platform changing routing rules overnight.