Decide
Which robot, and how to build your first prototype
Two concrete questions before starting a physical AI project: which robot shape to choose, and what path leads from a blank page to a first working prototype. Here is an honest answer, with budgets, timelines and pitfalls included.
Which robot shape for physical AI?
Not every robot embodiment benefits equally from the 2026 wave of physical AI progress. The more controlled the environment, the more bounded the task, and the more safety is already under control, the faster a vision-language-action model or a diffusion policy pays off. Conversely, every extra degree of freedom, every metre of unstructured terrain and every kilogram of balance to manage pushes the maturity horizon further out. Here is a decision matrix by embodiment type, to help you decide where to invest first.
| Type | 2026 AI maturity | Ease of deployment | Typical use case | Horizon |
|---|---|---|---|---|
| Fixed arm / cell cobot | Very high: AI vision and diffusion policies already in production | Maximal: controlled environment, bounded task, easy demonstration collection | Bin-picking, assembly, sorting, packaging | Already in production |
| AMR / mobile robot | High: navigation is commoditised, navigation VLAs emerging | High: mapping and obstacle avoidance are mature | Intralogistics transport, patrolling, inventory | Already in production, navigation VLAs in testing |
| Mobile manipulator | Medium: the navigation plus manipulation combinatorics is still young | Medium: high value but complex integration | Truck/container unloading, order picking | 1 to 3 years for generalisation |
| Wheeled humanoid | Medium to high: balance is already solved by the wheeled base | Medium: good stability/manipulation trade-off | Demonstration collection, bimanual tasks in structured environments | 2 to 4 years |
| Bipedal humanoid | Low to medium: active R&D, balance and safety still costly | Low: maximal degrees of freedom, cost and safety burden | Generalist tasks in human environments | 5 to 10 years for industrial generalisation |
| Quadruped | High on its niche: locomotion solved via RL in simulation | High on inspection tasks | Inspection of industrial, hazardous or remote sites | Already in production, niche |
| SCARA / delta | Low usefulness: the core task is already optimal without AI | Not relevant: AI adds nothing to deterministic repetition | Very high-cadence pick-and-place on identical parts | Status quo, except vision for bulk parts |
| Inspection drone | Mature (Skydio, Flyability in production at Shell, BASF) | Easy: no physical contact, mature AI navigation; its own constraint is aviation regulation (beyond-visual-line-of-sight), a separate regime from the machinery AI Act | Inspection, monitoring, mapping | Already here (bounded potential: no manipulation) |
These categories already have verifiable industrial representatives. Agility Robotics sells its bipedal Digit (175 cm, 65 kg, 28 degrees of freedom) for around $250,000 and deploys it in US warehouses for tote sorting in segregated zones. Boston Dynamics, for its part, has deployed its mobile manipulator Stretch at DHL, Gap, Maersk, Arvato, Otto Group, H&M and NFI, reaching throughput above 500 cartons an hour as it rolled out at Lidl in 2026. On the wheeled-humanoid side, Galbot G1 (173 cm, 85 kg, 47 degrees of freedom, omnidirectional wheeled base) already runs in a Beijing pharmacy, and Unitree has been selling its G1-D, a wheeled variant of the G1, since 2026, priced from $38,800 to $66,300 depending on configuration, built for data collection rather than walking. In inspection, ANYbotics' ANYmal X, certified for explosive zones, runs at Shell, Equinor and BASF, while Boston Dynamics' Spot completed multi-week trials at BP's Whiting refinery.
For a first prototype, start with a fixed arm in a cell, not a humanoid. That combination maximises your odds of shipping a convincing demonstration in a few months rather than several years.
The learning curve, no sugarcoating
For a team of 1 to 2 engineers comfortable with Python but with no robotics experience, here is a realistic schedule, built from field feedback of the LeRobot community rather than a marketing scenario.
| Period | What you do | What actually blocks you |
|---|---|---|
| Weeks 1-2 | Assembling the arm, calibrating cameras, setting up the Python environment (and ROS 2 if the robot is mobile) | Cranky USB drivers, permission conflicts, CUDA/PyTorch versions that clash with the GPU |
| Weeks 3-4 | Teleoperation with the leader arm, first demonstration collection runs | Understanding what a good demonstration actually is: smooth motion, varied starting positions, stable lighting |
| Weeks 5-8 | Training a first policy (ACT), iterating | The fail-diagnose-recollect loop: the policy fails, you must work out whether the cause is data, tuning or hardware, then recollect |
| Weeks 8-12 | Task reliable at 80-90%, serious evaluation over repeated trials | Calibration drift between sessions, day-to-day reproducibility |
Honestly budget 2 to 3 months for a convincing first prototype. The good news: a single weekend is enough for a minimal demonstration. With an SO-101 kit, it takes about two hours to record 50 demonstrations, and training a first ACT policy fits into an afternoon on a decent GPU. It is the iterations that follow, not the first attempt, that consume the two to three months.
The classic walls almost every team hits:
- Demonstration quality: hesitant or inconsistent trajectories teach the policy to hesitate in turn.
- Calibration drift: a camera or arm that shifts by a few millimetres between sessions is enough to break an already trained policy.
- Lighting: a model trained in morning light fails in the afternoon if lighting was not varied during collection.
- Reproducibility: a policy that succeeds nine times out of ten on a given day must be revalidated on another day, under different conditions, before drawing any conclusion.
The concrete kit for your first prototype
Here is a hardware list verified at the time of publication, not a wish list. Prices remain orders of magnitude: check them before buying, this market moves fast.
| Component | 2026 reference | Indicative price | Role |
|---|---|---|---|
| Robotic arm (leader-follower pair) | SO-101 (Hugging Face / LeRobot, designed with RobotStudio) | About $130 to $220 as a DIY kit per arm, $200 to $400 for a fully assembled leader-follower pair | Teleoperation and task execution |
| Advanced bimanual arm (optional) | Aloha Solo (Trossen Robotics) | Starting at $8,999.95 | Bimanual manipulation to go further than the single arm |
| Camera(s) | 720p+ USB webcam (wrist and external view), or Intel RealSense for depth | A few tens of dollars per webcam, a few hundred for a RealSense | Visual perception for the policy |
| PC with GPU | RTX 3060/4060 (8 to 12 GB VRAM) for ACT; 16 GB and above for diffusion policy | Variable, or hourly cloud rental for heavy training | Local or remote policy training |
| Embedded compute (optional) | NVIDIA Jetson Orin Nano Super Developer Kit | $249 | Onboard inference at 67 TOPS for autonomous deployment |
On the software side, Python and Hugging Face's LeRobot library remain the standard entry point in 2026: actively maintained, and already backing more than 58,000 community datasets published on the Hub, up from 1,145 at the end of 2024. Add ROS 2 if your robot moves, and simulation as an option: MuJoCo, free and open source, or NVIDIA Isaac Lab for massively parallel training of locomotion policies.
Total budget for a discovery-stage build: under $2,000 excluding the PC, with an SO-101 arm, two webcams and optionally a Jetson Orin Nano. That is the price of a good laptop, not an industrial project.
The data you actually need
How many demonstrations does it take for a policy to work? LeRobot's documentation for ACT (Action Chunking Transformer) gives clear, documented orders of magnitude.
| Task type | Demonstrations (order of magnitude) |
|---|---|
| Simple pick-and-place, single object, fixed position | About 50 |
| More complex, multi-step task | 100 to 200 |
| Robustness to variation (position, lighting, objects) | 200 and above, with diversity |
Collection happens through teleoperation with the SO-101's leader arm: you move the leader arm by hand, the follower mirrors the motion, and every trajectory is recorded automatically. To get started without collecting everything yourself, the LeRobot Hub and the Open X-Embodiment dataset (more than a million trajectories from 22 robots across 21 institutions) provide a base for training or pretraining.
The golden rule, documented by 2026 research on demonstration selection: quality and diversity matter more than volume. Fifty clean, varied demonstrations outperform two hundred sloppy, repetitive ones.
One strategic point to keep in mind: public data lets you get started, but it is the data from your own processes, collected on your own line, that forms the asset that actually matters. That proprietary collection, far more than the choice of model, is what becomes your lasting advantage.
Constraints and evaluation
A prototype that works on a bench is not yet a safe system, nor a seriously evaluated one. Three disciplines you should not skip.
Safety from the prototype stage: limit speeds, clear an exclusion zone around the arm during trials, and never treat a lab prototype as ready for a human operator standing nearby. Moving to production then falls under the EU AI Act and the associated machinery standards: see our EU AI Act and standards pillar for up-to-date deadlines and responsibilities.
Evaluating properly means measuring a success rate over a meaningful number of consecutive trials, with variation in position, lighting and objects, rather than keeping the best filmed take for a demo. A policy that succeeds nine times out of ten across varied trials is a solid result; a single successful video is not.
Moving from prototype to industrial pilot requires a different set of requirements: reliability, maintenance, integration with existing systems, team training. Our factory director's roadmap details the pass criteria and a realistic timeline.
When to stop: if the required cycle time is under 2 seconds or the required precision falls below a millimetre, classic automation (SCARA, delta, deterministic industrial vision) remains the right answer. Physical AI excels at variability and uncertainty, not at perfect repetition.
Sources: Hugging Face, SO-101 documentation, Hackster.io, SO-101 launch (2026), Hugging Face, ACT (Action Chunking Transformer) documentation, Trossen Robotics, Aloha Solo, NVIDIA, Jetson Orin Nano Super Developer Kit, NVIDIA, Isaac Lab, Tech Times, LeRobot Hub growth (May 2026, per IEEE Spectrum), Quality over Quantity: Demonstration Curation via Influence Functions, arXiv (2026), Open X-Embodiment: Robotic Learning Datasets and RT-X Models, arXiv, Boston Dynamics, Stretch, Automated Warehouse, Stretch deployment at Lidl (2026), Robots International, Galbot G1, Botinfo.ai, Unitree G1 and G1-D variant (June 2026), Humanoid.guide, Agility Robotics Digit.