The 70%: why the machine is the easy part
The case for building a business around everything except the robot.
The compliance gap between a demo and a deployment
The distance from “it works on stage” to “it is legal on your floor” — and who is on the hook for closing it.
A demo proves a robot can do the task. A deployment proves it may — legally, safely, on your site, under your name. Between the two sits a gap most buyers never see until it is theirs to close.
What a demo is allowed to skip
On a stage, a machine runs a scripted route in a controlled space, often on a prototype that never has to pass a safety file. None of that is dishonest — it is simply not the same machine, in the same conditions, that a regulator or an insurer will later judge. The gap is everything the demo was allowed to leave out.
On a real floor the questions change: CE marking against the right directives, a risk assessment for the actual site, an operator who knows the stop procedure, and documents that survive an audit. You close them before the robot arrives, or you close them while a client watches.
“A demo answers ‘can it work?’. A deployment answers ‘is it allowed to?’ — and only one of those questions has your name on it.”
Every deployment has a moment where responsibility changes hands. Most contracts never name it.
Who closes the gap — and when
The factory hands over a machine and a declaration of conformity. The site owner accepts how it is used. The integrator sits between them and, in practice, inherits whatever neither side wrote down. The gap has an owner the moment a robot rolls off the pallet — the only question is whether that owner chose the role or was handed it.
Timing decides the cost. Ask for the safety file and the CE documentation during selection, and the paperwork is a checklist. Ask for it after a client has seen the pilot, and it becomes an emergency negotiated under a deadline that was never yours to set.
WHAT TO TAKE AWAY
Ask for the safety file and CE documentation before the pilot, not after it.
A risk assessment is site-specific — a factory’s generic one does not transfer to your floor.
The operator’s stop procedure is part of compliance, not a nice-to-have.
A render is marked a render; a pilot is never written up as a case study.
The good news: the questions that close the gap are short, and a serious factory has the answers ready.
What a buyer can ask for
Before a pilot, four documents tell you most of what you need: the CE declaration against the directives that actually apply, the technical file behind it, a risk assessment you can adapt to your site, and operator instructions in a language your staff read. A factory that hands them over without friction has done this before.
None of this slows a good deployment down. It slows down the ones that were never going to survive an audit — which is exactly the point of asking early, on your timeline rather than a client’s.
EDITORIAL RULE
Sourced or silent. Every figure on this page carries an attributed, dated source. Where we could not source a number, we left it out rather than estimate it.
SOURCES
- 01EU Machinery Regulation 2023/1230In force · transition to 2027
- 02CE marking & safety-file guidanceNotified-body summaries · 2025
- 03Integrator compliance interviewsEurope · Q1 2026
- 04N.O.N. Humanoid vetting notesFactory audits · 2026
A QUESTION
One person answers — from the first email to the room.
EMAIL
WECHAT
nh_alliance
LINKEDIN
