Platform Synthesis

The Core Thesis

There are 56 companies in this database building autonomous ground robots. They are organized into 9+ verticals — delivery, security, cleaning, lawn care, agriculture, warehouse, defense, hospitality, construction. Each company has raised capital, hired engineers, and built a robot from scratch to solve one vertical.

They are all building the same machine.

Not metaphorically. Literally. When you strip away the top-mounted payload — the cargo box, the camera mast, the mop deck, the cutting blade — what remains is functionally identical: an electric wheeled chassis with batteries, motors, a compute board, cameras, LiDAR, a cellular radio, and a navigation stack. Every company in this database has independently re-engineered the same platform. They just don't know it, because they're organized by use case, not by physics.

Product Deconstruction

To see this clearly, take five products from entirely different markets and decompose them into their physical subsystems:

Nine of ten subsystems are the same. Different brands, different exact components, but the same functional architecture. The only row that differs is the last one: payload. This is not a coincidence. It's physics. The laws of motion, power, perception, and communication don't change based on what you're carrying.

The Six Primitives

Every autonomous ground robot requires exactly six functional primitives. No more, no fewer. Anything missing and the robot cannot operate. Anything additional is payload-specific.

These six primitives account for ~80-90% of the BOM cost, engineering effort, and development time of every robot in the dataset. The payload — the thing that actually differentiates the product — is 10-20% of the total system. This is the inversion that creates the opportunity: the robotics industry is organized around the 10% that's different, not the 90% that's shared.

Why Everything Converges on Wheels

Of the 102 products in the database, 49 (48%) are wheeled. This isn't market preference — it's thermodynamics.

Use Case Matrix

Every use case in the dataset decomposes into three variables layered on top of the six primitives: speed envelope, payload type, and operating environment. The base platform is identical; only these three parameters change.

Motion patterns reduce to exactly three: A→B waypoint (delivery, warehouse, hospitality, construction), loop patrol (security), and area coverage (cleaning, lawn care, agriculture). A single nav stack that implements all three covers every use case. The software problem is the same — SLAM + path planning with different mission logic. The mechanical problem is the same — wheels on a surface. The electrical problem is the same — batteries powering motors through a compute board.

The Shared Bill of Materials

Estimating the bill of materials (BOM) breakdown across use cases reveals the economic argument for platform consolidation:

85% of the BOM is shared. Every company in the dataset is independently sourcing, designing, and assembling that 85%. This is like every smartphone manufacturer independently designing their own cellular radio, battery chemistry, and display panel. The industry is pre-consolidation — waiting for a platform to emerge.

Platform Architecture

The modular platform that absorbs these use cases has four layers. The bottom three are fixed; the top layer is swappable.

The critical design decision: the payload interface is the API. Like a USB port or a PCIe slot, it defines the contract between the platform and the module. Mechanical mounting, power delivery, and data communication are standardized. The platform doesn't know or care what's plugged in. The module doesn't know or care about locomotion or navigation. This separation of concerns is what enables the platform to absorb new use cases without re-engineering the base.

The Module Map

Each module maps to a market vertical and the companies it displaces:

Unit Economics & Flywheel

The economic model inverts the typical robotics business:

Execution Sequence

The order matters. Not all modules are equal in market readiness, engineering complexity, or strategic value. The sequencing:

The Product

What follows is a concrete description of the machine that emerges from this analysis — not a concept, but a buildable, shippable product spec derived from the convergence of 56 companies and 102 products.

This is the machine the data says should exist. 56 companies have independently validated the market need. They've proven customers will pay for autonomous ground robots. They just each solved 15% of the problem and re-built the other 85% from scratch. The IM platform solves the 85% once and lets the 15% be modules.