everything a robotics company needs to go from 0→1:
- one real customer problem with hard ROI, not a demo
- one hero workflow you own end-to-end (automation human-in-the-loop fallback)
- simulation for fast iteration (NVIDIA Isaac, MuJoCo, Drake, Genesis)
- a single testbed robot you can abuse every day
- ROS 2 ( Zenoh) production-grade drivers and health checks
- a reproducible OS image and reliable OTA (Mender, Balena, Airbotics)
- logs and bags shipped to searchable storage (mostly S3 custom scripts, Alloy)
- a tight feedback loop between operators, support, and engineering (Slack threads and prayer)
everything you need to go from 1→n:
- fleet management, task dispatch, and traffic control (Formant, InOrbit, Open-RMF, Cogniteam)
- secure connectivity with per-robot identity (Husarnet, Tailscale, Starlink backhaul, mostly custom)
- edge compute and onboard inference (Jetson, Hailo, Luxonis OAK, AMD Kria)
- observability wired into incident response and root-cause analysis (Nominal, Sift, Alloy)
- labelled data, evals, and a versioned ML pipeline into production (Roboflow for CV, W&B for tracking, custom ETL)
- safety cases, audit trails, and compliance your biggest customer will sign off on (mostly custom)
- multi-robot ops playbooks and a real on-call rotation (mostly tribal knowledge)
- a data layer that turns every mission into training signal (Alloy internal glue)
there is variance across industries but these categories are broadly true for modern robotics teams
the gap between 0→1 and 1→n in robotics is where most companies die.
the skills that get you your first customer are completely different from the skills that get you your 30th.